Frequency domain resource allocation type determination method and device, equipment and storage medium

Abstract

The invention discloses a frequency domain resource allocation type determination method and device, equipment and a storage medium, and belongs to the technical field of mobile communication. The method comprises: a terminal device receiving configuration information about a resource allocation type (S301); the configuration information of the resource allocation type is used for determining frequency domain resource allocation types of N channels, the N channels are scheduled by first downlink control information (DCI), and the N channels correspond to N serving cells; n is greater than or equal to 1, and N is an integer.

Description

Method, device, equipment and storage medium for determining frequency domain resource allocation type Technical Field

[0001] The present application relates to the field of mobile communication technology, and in particular to a method, apparatus, device and storage medium for determining a frequency domain resource allocation type. Background Art

[0002] In the 5G mobile communication system, both uplink and downlink channels support two types of frequency domain resource allocation, namely Type 0 frequency domain resource allocation type and Type 1 frequency domain resource allocation type.

[0003] In related technologies, network equipment configures the frequency domain resource allocation type used by terminal equipment through high-layer signaling; specifically, the network equipment can indicate frequency domain resource allocation type 0 (Type0), frequency domain resource allocation type 1 (Type 1) or dynamic switching (dynamic switch) through high-layer parameters. When "dynamic switching" is indicated through high-layer parameters, the frequency domain resource allocation type used by the terminal is further indicated as Type 0 or Type 1 through a specific field in the downlink control information (Downlink Control Information, DCI).

[0004] Summary of the Invention

[0005] The present invention provides a method, apparatus, device, and storage medium for determining a frequency domain resource allocation type. The technical solution is as follows:

[0006] On the one hand, an embodiment of the present application provides a method for determining a frequency domain resource allocation type, the method comprising:

[0007] The terminal device receives configuration information of the resource allocation type;

[0008] The configuration information of the resource allocation type is used to determine the frequency domain resource allocation type of N channels, the N channels are scheduled by the first downlink control information DCI, and the N channels correspond to N service cells; N is greater than or equal to 1, and N is an integer.

[0009] On the one hand, an embodiment of the present application provides a method for determining a frequency domain resource allocation type, the method comprising:

[0010] The network device sends configuration information of resource allocation type to the terminal device;

[0011] The configuration information of the resource allocation type is used to determine the frequency domain resource allocation type of N channels, the N channels are scheduled by the first downlink control information DCI, and the N channels correspond to N service cells; N is greater than or equal to 1, and N is an integer.

[0012] On the other hand, an embodiment of the present application provides a device for determining a frequency domain resource allocation type, the device comprising:

[0013] A receiving module, configured to receive configuration information of a resource allocation type;

[0014] The configuration information of the resource allocation type is used to determine the frequency domain resource allocation type of N channels, the N channels are scheduled by the first downlink control information DCI, and the N channels correspond to N service cells; N is greater than or equal to 1, and N is an integer.

[0015] On the other hand, an embodiment of the present application provides a device for determining a frequency domain resource allocation type, the device comprising:

[0016] A sending module, configured to send configuration information of resource allocation types to a terminal device;

[0017] The configuration information of the resource allocation type is used to determine the frequency domain resource allocation type of N channels, the N channels are scheduled by the first downlink control information DCI, and the N channels correspond to N service cells; N is greater than or equal to 1, and N is an integer.

[0018] On the other hand, an embodiment of the present application provides a terminal device, the terminal device including a processor, a memory, and a transceiver;

[0019] A computer program is stored in the memory, and the processor executes the computer program so that the terminal device implements the above-mentioned method for determining the frequency domain resource allocation type.

[0020] On the other hand, an embodiment of the present application provides a network device, the network device including a processor, a memory, and a transceiver;

[0021] The memory stores a computer program, and the processor executes the computer program to enable the network device to implement the above-mentioned method for determining the frequency domain resource allocation type.

[0022] On the other hand, an embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored. The computer program is loaded and executed by a processor to implement the above-mentioned method for determining the frequency domain resource allocation type.

[0023] On the other hand, the present application also provides a chip, which is used to run in a communication device so that the communication device executes the above-mentioned method for determining the frequency domain resource allocation type.

[0024] In another aspect, the present application provides a computer program product, comprising computer instructions stored in a computer-readable storage medium. A processor of a communication device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the communication device to perform the above-described method for determining a frequency domain resource allocation type.

[0025] On the other hand, the present application provides a computer program, which is executed by a processor of a communication device to implement the above-mentioned method for determining the frequency domain resource allocation type.

[0026] Through the technical solution provided by the embodiments of the present application, for the case where at least one channel is scheduled through a DCI, the terminal device determines the frequency domain resource allocation type corresponding to one or more channels through the received configuration information of the resource allocation type, thereby improving the determination scheme of the frequency domain resource allocation type when one or more channels are scheduled through a single DCI and improving the efficiency of resource scheduling. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] In order to more clearly illustrate the technical solutions in the embodiments of the present application, 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 application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0028] FIG1 is a schematic diagram of the architecture of a communication system provided by an embodiment of the present application;

[0029] FIG2 is a schematic diagram of two types of frequency domain resource allocation involved in this application;

[0030] FIG3 is a flowchart of a method for determining a frequency domain resource allocation type provided by an embodiment of the present application;

[0031] FIG4 is a flowchart of a method for determining a frequency domain resource allocation type provided by an embodiment of the present application;

[0032] FIG5 is a flowchart of a method for determining a frequency domain resource allocation type provided by an embodiment of the present application;

[0033] FIG6 is a block diagram of an apparatus for determining a frequency domain resource allocation type according to an embodiment of the present application;

[0034] FIG7 is a block diagram of an apparatus for determining a frequency domain resource allocation type according to an embodiment of the present application;

[0035] FIG8 is a schematic structural diagram of a communication device provided in one embodiment of the present application. DETAILED DESCRIPTION

[0036] In order to make the objectives, technical solutions and advantages of this application clearer, the implementation methods of this application will be further described in detail below with reference to the accompanying drawings.

[0037] The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. A person skilled in the art will appreciate that, with the evolution of the network architecture and the emergence of new business scenarios, the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.

[0038] 1 shows a schematic diagram of a communication system according to an exemplary embodiment of the present application, which includes a network device 110 and a terminal device 120, and / or a terminal device 120 and a terminal device 130, which are not limited in the present application.

[0039] The network device 110 in the present application provides wireless communication functions, and the network device 110 includes but is not limited to: Evolved Node B (eNB), Radio Network Controller (RNC), Node B (NB), Base Station Controller (BSC), Base Transceiver Station (BTS), Home Base Station (e.g., Home Evolved Node B, or Home Node B, HNB), Baseband Unit (BBU), Access Point (AP) in Wireless Fidelity (Wi-Fi) system, Wireless Relay Node, Wireless Backhaul Node, Transmission Point (TP) or Transmission and Reception Point (TRP), etc., and can also be the Next Generation Node B (NGNB) in the 5th Generation (5G) mobile communication system. The term "gNB" refers to a base station (B, gNB) or a transmission point (TRP or TP), or one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, or a network node constituting a gNB or a transmission point, such as a baseband unit (BBU) or a distributed unit (DU), or a base station in a Beyond Fifth Generation (B5G) or a 6th Generation (6G) mobile communication system, or a core network (CN), fronthaul, backhaul, radio access network (RAN), network slicing, or a serving cell, primary cell (PCell), primary secondary cell (PSCell), special cell (SpCell), secondary cell (SCell), or neighboring cell of a terminal device.

[0040] The terminal device 120 and / or terminal device 130 in this application are also called user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, and user device. The terminals include, but are not limited to, handheld devices, wearable devices, vehicle-mounted devices, and Internet of Things devices, such as mobile phones, tablet computers, e-book readers, laptop computers, desktop computers, televisions, game consoles, mobile Internet devices (MIDs), augmented reality (AR) terminals, virtual reality (VR) terminals, and mixed reality (MR) terminals, wearable devices, handles, electronic tags, controllers, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical care, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, wireless terminals in remote medical surgery, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loops (WLANs), and wireless terminals in industrial control. Loop (WLL) stations, personal digital assistants (PDA), TV set-top boxes (STB), customer premises equipment (CPE), etc.

[0041] The network device 110 and the terminal device 120 communicate with each other via some air interface technology, such as a Uu interface.

[0042] Exemplarily, there are two communication scenarios between the network device 110 and the terminal device 120: an uplink communication scenario and a downlink communication scenario. Uplink communication refers to sending signals to the network device 110; downlink communication refers to sending signals to the terminal device 120.

[0043] The terminal device 120 and the terminal device 130 communicate with each other via some air interface technology, such as a Uu interface.

[0044] In some embodiments, there are two communication scenarios between terminal device 120 and terminal device 130: a first sideline communication scenario and a second sideline communication scenario. The first sideline communication refers to sending signals to terminal device 130, while the second sideline communication refers to sending signals to terminal device 120.

[0045] Terminal device 120 and terminal device 130 are both within the network coverage and located in the same cell, or terminal device 120 and terminal device 130 are both within the network coverage but located in different cells, or terminal device 120 is within the network coverage but terminal device 130 is outside the network coverage.

[0046] The technical solutions provided in the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) system, Advanced Long Term Evolution (LTE-A) system, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, 5G mobile communication system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-U) system, NR on unlicensed spectrum (NR-based access to unlicensed spectrum) system. Unlicensed spectrum, NR-U) system, terrestrial communication network (Terrestrial Networks, NTN) system, non-terrestrial communication network (Non-Terrestrial Networks, NTN) system, wireless local area network (Wireless Local Area Networks, WLAN), wireless fidelity (Wireless Fidelity, Wi-Fi), cellular Internet of Things system, cellular passive Internet of Things system, can also be applied to the subsequent evolution system of 5G NR system, and can also be applied to B5G, 6G and subsequent evolution systems. In some embodiments of the present application, "NR" may also be referred to as 5G NR system or 5G system. Among them, the 5G mobile communication system may include non-standalone networking (NSA) and / or standalone networking (SA).

[0047] The technical solutions provided in the embodiments of the present application can also be applied to machine type communication (MTC), long term evolution technology for machine-to-machine communication (LTE-M), device-to-device (D2D) network, machine-to-machine (M2M) network, Internet of Things (IoT) network or other networks. Among them, the IoT network can include, for example, the Internet of Vehicles. Among them, the communication mode in the Internet of Vehicles system is collectively referred to as vehicle to other devices (Vehicle to X, V2X, X can represent anything), for example, the V2X can include: vehicle to vehicle (V2V) communication, vehicle to infrastructure (V2I) communication, vehicle to pedestrian communication (V2P) or vehicle to network (V2N) communication, etc.

[0048] In related technologies, both uplink and downlink support two frequency domain resource allocation types: (frequency domain) resource allocation type 0 and (frequency domain) resource allocation type 1. Network devices configure the frequency domain resource allocation type used by terminals through the high-level parameter resourceAllocation. The high-level parameter resourceAllocation is configured in the PDSCH-Config Information Element (IE) or PUSCH-Config IE and is configured per bandwidth part (BWP).

[0049] If the BWP indicator field is not configured in the scheduling DCI, or the terminal does not support BWP switching or change based on DCI, then the resource block index (RB indexing) of the frequency domain resource allocation Type 0 and Type 1 is determined in the active BWP of the terminal (the BWP activated by the UE at a certain moment in the radio resource control (RRC) connection state); if the terminal supports BWP change based on DCI and the BWP indicator field is configured in the scheduling DCI, then the RB indexing of the frequency domain resource allocation Type 0 and Type 1 is determined based on the BWP indicated by the BWP indicator in the DCI. The terminal needs to first determine the BWP through PDCCH detection, and then determine the frequency domain resource allocation in the BWP. Please refer to Figure 2, which shows a schematic diagram of two types of frequency domain resource allocation involved in this application.

[0050] (1) Resource Allocation Type 0:

[0051] As shown in part (a) of Figure 2, the granularity of frequency domain resource allocation Type 0 is resource block group (RBG). RBG is a combination of a series of consecutive virtual RBs. The number of virtual RBs included in each RBG is determined by the size of the BWP and the RRC configuration parameter rbg-Size. rbg-Size is used to configure 'configuration 1' or 'configuration 2' in Table 1 below. rbg-Size is also configured in PDSCH-Config or PUSCH-Config and is configured per BWP.

[0052] Table 1

[0053] BWP Sizeconfiguration 1configuration 21-362437-724873-144816145-2751616

[0054] Frequency domain resource allocation Type 0 uses a bitmap to indicate the RBGs allocated to the terminal. 1 indicates that the RBG is allocated to the terminal, and 0 indicates that the RBG is not allocated to the terminal. This allows for flexible distribution of frequency domain resources within the BWP, supports discontinuous resource allocation, and can combat frequency selective fading using discrete frequency domain transmission. However, the disadvantages are: (1) the number of bits in the bitmap is large, and it needs to cover every RBG in the entire BWP; (2) the granularity of resource allocation is coarse, because an RBG contains 2 to 16 RBs, and resources cannot be selected RB by RB (or RB by RB).

[0055] For a containing The BWP of PRBs contains the total number of RBGs N RBG for:

[0056] in:

[0057] The size of the first RBG is:

[0058] The size of the last RBG is:

[0059] if but

[0060] otherwise,

[0061] The size of the remaining RBG is P;

[0062] in, Indicates rounding up *, mod is the modulo operator, and P is the number of RBs contained in RBG; The number of the starting RB of the BWP.

[0063] (2) Resource Allocation Type 1:

[0064] As shown in part (b) of Figure 2, frequency domain resource allocation Type 1 can indicate a series of continuous virtual RBs to the terminal, using a resource indication value (RIV) to indicate the allocated starting RB (RB start ) and the number of RBs (L RBs ) for joint coding. The advantage of Type 1 is that it can indicate RB-level resources with fewer bits, but its disadvantage is that it can only allocate continuous frequency domain resources. When the number of resources is small, the frequency diversity is limited and it is easily affected by frequency selective fading.

[0065] Starting RB (RB start ) and the number of RBs (LRBs) are jointly coded as follows:

[0066] if but

[0067] otherwise,

[0068] Among them, L RBs Greater than or equal to 1, and no more than above Indicates rounding down to the nearest integer.

[0069] NR supports the terminal to perform blind detection of the Physical Downlink Control Channel (PDCCH) in the Search Space Sets (SSS) configured on the network side. The reason for "blind detection" is that the terminal does not know the DCI format and other information before detecting the DCI carried by the PDCCH. Therefore, it is necessary to use some fixed DCI sizes to perform blind detection on the PDCCH candidates in the search space set. In order to reduce the complexity of the terminal's blind detection of PDCCH, in the related technology, after completing the DCI size alignment step, the terminal does not expect the total DCI size to be greater than 4, and the total DCI size scrambled by the Cell-Radio Network Temporary Identifier (C-RNTI) is greater than 3.

[0070] Since the terminal only attempts to use some fixed DCI sizes to detect PDCCH, it is necessary for the terminal to know the DCI size of different DCI formats before blind detection of PDCCH. In other words, it is necessary to know the number of bits contained in each information field contained in the DCI. Taking the Frequency Domain Resource Assignment (FDRA) field as an example, the number of bits is determined as follows:

[0071] If only resource allocation type 0 is configured, the indication field contains N RBG Bit;

[0072] If only resource allocation type 1 is configured, the indicator domain contains bits; where log2(*) means taking the logarithm of *; The number of RBs included in the downlink BWP;

[0073] If both type 0 and type 1 are configured, the indication field contains: bits, where max is the maximum value symbol; the most significant bit is used to indicate the resource allocation type used by the terminal, 0 indicates type 0, and 1 indicates type 1.

[0074] The current Multi-Carrier work project supports the feature of one DCI field scheduling multiple cell channels. The following types of DCI fields are under discussion for the design of DCI fields scheduling multiple cell channels:

[0075] For discussing field design of DCI format 0_X / 1_X which schedules more than one cell, reformulate the types of DCI fields as below:

[0076] – Type-1 field, with emphasis on single field:

[0077] Type-1A field: A single field indicating common information to all the co-scheduled cells. Co-scheduled cells are cells that can be scheduled simultaneously by a DCI, also known as a serving cell combination.

[0078] Type-1 B field: A single field indicating separate information to each of co-scheduled cells via joint indication;

[0079] Type-1 C field: A single field indicating an information to only one of co-scheduled cells.

[0080] – The Type-2 field emphasizes the separate field: a separate field for each of the co-scheduled cells. For example, the Type-2 field contains multiple separate fields, each of which indicates information about a cell in the co-scheduled cells.

[0081] – Type 3 field: Based on the explicit configuration, the Type 3 field can be a common field or a separate field; when configured as a common field, the Type 3 field indicates the common information of all co-scheduled cells; when configured as a separate field, each single field in the Type 3 field corresponds to each cell in the co-scheduled cells, or corresponds to each sub-group in each sub-group of the co-scheduled cells (Type-3 field: Common or separate to each of the co-scheduled cells, or separate to each sub-group, dependent on explicit configuration).

[0082] A subgroup is a subset of all co-scheduled cells, and a single field in the Type 3 field is shared by the co-scheduled cells belonging to the same sub-group. (Note: One sub-group comprises a subset of co-scheduled cells where a single field is commonly applied to the co-scheduled cell(s) belonging to a same sub-group.) Whether the Type 3 field is a common field or a single field depends on the signaling configuration.

[0083] – Note: Handling of any parameters applicable to multi-cell scheduling where corresponding fields are not included in DCI format 0_X / 1_X (if any) will be separately discussed.

[0084] However, when the related technology supports the feature of scheduling channels of multiple cells with one DCI, the DCI needs to include resource allocation indicators for multiple channels. Taking the frequency domain resource allocation (FDRA) indicator field as an example, it is not clear whether the FDRAs of multiple channels share the same indicator field or have independent indicator fields. The advantage of sharing the same indicator field is that it can save DCI overhead, but resource allocation is not flexible enough, especially for inter-band carrier aggregation (inter-band CA), where there is no correlation between the channels of each carrier, or for cells with different configured resource allocation types, if the same FDRA indicator is shared, the scheduling algorithm will become very complicated and the spectrum efficiency will be reduced. The advantage of an independent indicator field is that resource allocation is more flexible and can achieve higher spectrum efficiency, but because of the independent indication, the number of bits required for the FDRA indicator field increases exponentially, thereby increasing DCI overhead and reducing PDCCH reliability.

[0085] The subsequent solutions of this application focus on the configuration and indication methods of frequency domain resource allocation types, and are applicable to the working modes of shared indication domains and independent indication domains. They can better balance scheduling flexibility and DCI overhead, and can simplify the scheduling algorithm on the network side.

[0086] Please refer to FIG3 , which shows a flowchart of a method for determining a frequency domain resource allocation type provided by one embodiment of the present application. The method may be performed by a terminal device, wherein the terminal device may be the terminal device 120 or the terminal device 130 in the network architecture shown in FIG1 . The method may include the following steps:

[0087] In step 301, the terminal device receives configuration information of the resource allocation type; the configuration information of the resource allocation type is used to determine the frequency domain resource allocation type of N channels, the N channels are scheduled by the first downlink control information DCI, and the N channels correspond to N service cells; N is greater than or equal to 1, and N is an integer.

[0088] Among them, the above-mentioned first DCI can simultaneously schedule N channels corresponding to a service cell combination; for example, the first DCI can simultaneously schedule the respective channels of N service cells, and the N service cells can be regarded as a service cell combination, and a service cell combination can include one or more service cells.

[0089] To sum up, the scheme shown in the embodiment of the present application, for the case where at least one channel is scheduled through a DCI, the terminal device determines the frequency domain resource allocation type corresponding to N channels through the received configuration information of the resource allocation type, thereby improving the scheme for determining the frequency domain resource allocation type when one or more channels are scheduled through a single DCI, and improving the efficiency of resource scheduling.

[0090] Please refer to Figure 4, which shows a flowchart of a method for determining a frequency domain resource allocation type provided by an embodiment of the present application. The method can be performed by a network device, wherein the network device can be the network device 110 in the network architecture shown in Figure 1. The method can include the following steps:

[0091] In step 401, the network device sends configuration information of the resource allocation type to the terminal device; the configuration information of the resource allocation type is used to determine the frequency domain resource allocation type of N channels, the N channels are scheduled by the first downlink control information DCI, and the N channels correspond to N service cells; N is greater than or equal to 1, and N is an integer.

[0092] To sum up, the scheme shown in the embodiment of the present application is that for the case where at least one channel is scheduled through a DCI, the network device sends configuration information of the resource allocation type to the terminal device, and the terminal device determines the frequency domain resource allocation type corresponding to N channels through the received configuration information of the resource allocation type, thereby improving the determination scheme of the frequency domain resource allocation type when one or more channels are scheduled through a single DCI, and improving the efficiency of resource scheduling.

[0093] Based on the embodiments shown in Figures 3 and / or 4 above, please refer to Figure 5, which shows a flowchart of a method for determining a frequency domain resource allocation type provided by an embodiment of the present application. The method can be interactively executed by a terminal device and a network device; wherein the terminal device and the network device can be the terminal device 120 and the network device 110 in the network architecture shown in Figure 1; or, the terminal device and the network device can be the terminal device 130 and the network device 110 in the network architecture shown in Figure 1. As shown in Figure 5, the method can include the following steps:

[0094] Step 501: The network device sends configuration information of resource allocation type to the terminal device; the terminal device receives the configuration information of resource allocation type.

[0095] In some embodiments, the network device can configure or indicate the configuration information of the above resource allocation type through high-level parameters, specifically through high-level parameters resourceAllocation, which can be carried through high-level signaling (such as RRC signaling).

[0096] In other embodiments, the network device may configure the configuration information of the resource allocation type specifically used for scheduling at least one channel through a DCI through independent signaling or parameters other than the high-level parameter resourceAllocation.

[0097] In step 502, the network device sends a first DCI to the terminal device; the terminal device receives the first DCI; the first DCI is used to schedule N channels, and the N channels correspond to N service cells; N is greater than or equal to 1, and N is an integer.

[0098] In some embodiments, the N channels may be N data channels; each of the N channels corresponds to one of the N serving cells.

[0099] In some embodiments, the above-mentioned N data channels may include N physical downlink shared channels (PDSCH) and / or physical uplink shared channels (PUSCH), that is, the N channels scheduled by the above-mentioned first DCI may all be PDSCH, or all PUSCH, or part PDSCH + part PUSCH.

[0100] The network device does not limit whether the value of N is the same in each scheduling / configuration.

[0101] In this application, the concepts of "serving cell" and "carrier" may be the same and may be used interchangeably.

[0102] Step 503: The terminal device determines the frequency domain resource allocation type of N channels according to the configuration information of the resource allocation type.

[0103] In the embodiments provided in this application, the configuration / indication of the frequency domain resource allocation types of N channels through the above configuration information can be divided into the following two schemes:

[0104] Option 1:

[0105] In some embodiments, the first configuration information is used to configure the frequency domain resource allocation type of the serving cell; or, the first configuration information is used to configure the frequency domain resource allocation type of the channel corresponding to the serving cell.

[0106] In some embodiments, the configuration information of the above-mentioned resource allocation type includes first configuration information corresponding to each of N service cells; the first configuration information is used to configure the frequency domain resource allocation type of the service cell corresponding to the first configuration information; or, the first configuration information is used to configure the frequency domain resource allocation type of the channel of the service cell corresponding to the first configuration information.

[0107] The first configuration information can be configured or indicated by the network device through a high-level parameter, specifically a high-level parameter resourceAllocation, which can be carried by high-level signaling (such as RRC signaling).

[0108] The above-mentioned first configuration information may be information for configuring the frequency domain resource allocation type of the serving cell.

[0109] Alternatively, the first configuration information may also be information for configuring the frequency domain resource allocation type of a channel of the serving cell. For example, the first configuration information may be information for configuring the frequency domain resource allocation type of the PDSCH of the serving cell, or the first configuration information may be information for configuring the frequency domain resource allocation type of the PUSCH of the serving cell.

[0110] In some embodiments, when the configuration information of the resource allocation type includes first configuration information corresponding to N serving cells, the N serving cells may correspond to M serving cell sub-combinations, and the number of cells included in each of the M serving cell sub-combinations may be the same or different. The N serving cells corresponding to the M serving cell sub-combinations may mean that the N serving cells are divided into M serving cell sub-combinations, where 1≤M≤N, and M is an integer.

[0111] Through the above-mentioned first configuration information, the same frequency domain resource allocation type can be configured for N serving cells or channels in N serving cells. In other words, the frequency domain resource allocation type can be configured at the granularity of all N serving cells / all channels in N serving cells. This can unify the frequency domain resource allocation type of at least one channel scheduled in a DCI, reducing the overhead of the frequency domain resource allocation type indication.

[0112] For example, in some embodiments, the frequency domain resource allocation type corresponding to each of the N serving cells is the same; or,

[0113] The first configuration information corresponding to each serving cell in the N serving cells is the same; or,

[0114] The frequency domain resource allocation type corresponding to each channel in the N channels is the same; or,

[0115] The first configuration information corresponding to each channel in the N channels is the same.

[0116] That is to say, the above-mentioned N service cells correspond to the same frequency domain resource allocation type; or, the above-mentioned N service cells correspond to the same first configuration information, for example, each of the N service cells corresponds to one first configuration information, and the contents of the first configuration information configurations of the N service cells are the same; or, the above-mentioned N channels correspond to the same frequency domain resource allocation type; or, the above-mentioned N channels correspond to the same first configuration information, for example, each of the N channels corresponds to one first configuration information, and the contents of the first configuration information configurations of the N channels are the same.

[0117] That is to say, the N channels scheduled by the above-mentioned first DCI, or the N service cells corresponding to the N channels, are channels / service cells configured with the same frequency domain resource allocation type. Accordingly, when the network device schedules the channels of the terminal device, it can select the channels of N service cells with the same frequency domain resource allocation type to be scheduled in the first DCI, or select N channels with the same frequency domain resource allocation type to be scheduled in the first DCI.

[0118] Alternatively, the N channels scheduled by the above-mentioned first DCI can be configured with the same frequency domain resource allocation type, that is, when the network device schedules the channels of the terminal device through the first DCI, it can schedule N channels corresponding to the same or identical frequency domain resource allocation type through the first DCI.

[0119] That is to say, when the terminal device subsequently determines the resources of the channel scheduled by the network device through the first DCI, it can determine that the frequency domain resource allocation types of the N channels are the same.

[0120] For another example, in some embodiments, the terminal device does not expect that the frequency domain resource allocation types corresponding to the N serving cells are different or partially the same; or,

[0121] The terminal device does not expect that the first configuration information corresponding to each serving cell in the N serving cells is different or partially the same; or,

[0122] The terminal device does not expect that the frequency domain resource allocation types corresponding to each of the N channels are different or partially the same; or,

[0123] The terminal device does not expect that the first configuration information corresponding to each channel in the N channels is different or partially the same.

[0124] Correspondingly, when the network device performs resource scheduling through the first DCI, it can schedule N service cells with the same frequency domain resource allocation type / first configuration information through the first DCI, or schedule N channels with the same frequency domain resource allocation type / first configuration information through the first DCI.

[0125] There are many ways to describe the terminal device's "unexpected" behavior, for example:

[0126] Description 1: The terminal device does not expect the first DCI to schedule N serving cells, and the N serving cells are configured with different frequency domain resource allocation types (i.e., this scheduling behavior is not expected);

[0127] Description 2: The terminal device receives a first DCI, which schedules N service cells. The terminal device does not expect the N service cells to be configured with different frequency domain resource allocation types (that is, it "does not expect" this configuration behavior).

[0128] For example, the above-mentioned unexpected behavior of the terminal device means that the terminal device does not expect the first DCI received to meet a certain condition (i.e., the frequency domain resource allocation types corresponding to the N service cells are different or partially the same; or, the first configuration information corresponding to the N service cells are different or partially the same; or, the frequency domain resource allocation types corresponding to the N channels are different or partially the same; or, the first configuration information corresponding to the N channels is different or partially the same).

[0129] Alternatively, in some other embodiments, the above-mentioned terminal device may not expect to receive the first DCI that meets the above-mentioned conditions, that is, the terminal device does not expect to receive the first DCI whose frequency domain resource allocation types corresponding to the N scheduled service cells are different or partially the same; or, the terminal device does not expect to receive the first DCI whose first configuration information corresponding to the N scheduled service cells is different or partially the same; or, the terminal device does not expect to receive the first DCI whose frequency domain resource allocation types corresponding to the N scheduled channels are different or partially the same; or, the terminal device does not expect to receive the first DCI whose first configuration information corresponding to the N scheduled channels is different or partially the same.

[0130] The same applies to the subsequent description of "not expecting", which will not be repeated in this application.

[0131] In some embodiments, if the network device sends the first DCI according to a behavior that the terminal does not expect, the terminal device may regard the received first DCI as an erroneous DCI and discard the first DCI.

[0132] The N serving cells may also be divided into at least one serving cell sub-combination. The first configuration information may be used to configure the same frequency domain resource allocation type for the serving cells or channels in each serving cell sub-combination. Alternatively, the frequency domain resource allocation type may be configured based on the granularity of the serving cell sub-combination / all channels in the serving cell sub-combination. Compared to configuring the same frequency domain resource allocation type for all N serving cells or channels in N serving cells, this solution enables scheduling of multiple channels with different frequency domain resource allocation types using a single DCI, thereby achieving more flexible DCI scheduling.

[0133] For example, in some embodiments, the frequency domain resource allocation type corresponding to each serving cell belonging to the same serving cell sub-group is the same; the serving cell sub-group includes part of the N serving cells; or,

[0134] The first configuration information corresponding to each serving cell belonging to the same serving cell sub-group is the same; or,

[0135] The frequency domain resource allocation types corresponding to the channels belonging to the same serving cell sub-combination are the same; or,

[0136] The first configuration information corresponding to each channel belonging to the same serving cell sub-group is the same.

[0137] Among them, the N channels of the above-mentioned first DCI scheduling can belong to at least two service cell sub-combinations, and the service cells in each service cell sub-combination are configured with the same frequency domain resource allocation type, or in other words, the channels of the service cells in each service cell sub-combination are configured with the same frequency domain resource allocation type. The service cells in each service cell sub-combination are configured with the same frequency domain resource allocation type, and the N channels correspond to at least two service cell combinations. Therefore, the channels in different service cell sub-combinations scheduled by the first DCI can correspond to different frequency domain resource allocation types, thereby improving the flexibility of DCI scheduling.

[0138] When the terminal device subsequently determines the resources of the channel scheduled by the network device through the first DCI, for the N channels, the channels of the service cells belonging to the same service cell sub-combination can determine the same frequency domain resource allocation type; correspondingly, for the N channels, the channels of the service cells that do not belong to the same service cell sub-combination can determine different frequency domain resource allocation types.

[0139] That is to say, when the network device schedules the channel of the terminal device through the first DCI, it can schedule two or more groups of channels through the first DCI, and each group of channels corresponds to the same frequency domain resource allocation type.

[0140] For another example, in some embodiments, the terminal device does not expect that the frequency domain resource allocation types corresponding to the serving cells belonging to the same serving cell sub-combination are different or partially the same; the serving cell sub-combination includes part of the N serving cells; or,

[0141] The terminal device does not expect that the first configuration information corresponding to each serving cell belonging to the same serving cell sub-group is different or partially the same; or,

[0142] The terminal device does not expect that the frequency domain resource allocation types corresponding to the channels belonging to the same serving cell sub-combination are different or partially the same; or,

[0143] The terminal device does not expect that the first configuration information corresponding to each channel belonging to the same service cell sub-combination is different or partially the same.

[0144] Correspondingly, when the network device performs resource scheduling through the first DCI, it can determine that the frequency domain resource allocation type / first configuration information corresponding to each service cell belonging to the same service cell sub-combination is the same, or it can determine that the frequency domain resource allocation type / first configuration information corresponding to each channel belonging to the same service cell sub-combination is the same.

[0145] Similarly, in other embodiments, the terminal device does not expect to receive the first DCI in which the frequency domain resource allocation types corresponding to the service cells belonging to the same service cell sub-combination are different or partially the same; or, the terminal device does not expect to receive the first DCI in which the first configuration information corresponding to the service cells belonging to the same service cell sub-combination is different or partially the same; or, the terminal device does not expect to receive the first DCI in which the frequency domain resource allocation types corresponding to the channels belonging to the same service cell sub-combination are different or partially the same; or, the terminal device does not expect to receive the first DCI in which the first configuration information corresponding to the channels belonging to the same service cell sub-combination is different or partially the same.

[0146] In some embodiments, the configuration information of the resource allocation type includes second configuration information; wherein the second configuration information is used to configure the frequency domain resource allocation type of the bandwidth part BWP of the service cell; or, the second configuration information is used to configure the frequency domain resource allocation type corresponding to the channel of the BWP.

[0147] That is to say, the above configuration information includes the second configuration information corresponding to the partial bandwidths BWP of the N service cells; the second configuration information is used to configure the frequency domain resource allocation type of the BWP corresponding to the second configuration information; or, the second configuration information is used to configure the frequency domain resource allocation type of the channel of the BWP corresponding to the second configuration information.

[0148] The second configuration information can be configured or indicated by the network device through a high-level parameter, specifically a high-level parameter resourceAllocation, which can be carried by high-level signaling (such as RRC signaling).

[0149] The second configuration information may be information for configuring the frequency domain resource allocation type of the BWP in the serving cell.

[0150] Alternatively, the second configuration information may also be information for configuring the frequency domain resource allocation type of the BWP channel. For example, the second configuration information may be information for configuring the frequency domain resource allocation type of the PDSCH of the BWP, or the second configuration information may be information for configuring the frequency domain resource allocation type of the PUSCH of the BWP of the serving cell.

[0151] The second configuration information allows the same frequency domain resource allocation type to be configured for the BWPs of N serving cells or for the channels in the BWPs of N serving cells. Alternatively, the frequency domain resource allocation type can be configured based on the granularity of all BWPs in N serving cells or all channels in all BWPs in N serving cells. This also unifies the frequency domain resource allocation type for at least one channel scheduled in a DCI, reducing the overhead of indicating the frequency domain resource allocation type.

[0152] For example, in some embodiments, the frequency domain resource allocation type corresponding to each BWP of the N serving cells is the same; or,

[0153] The second configuration information corresponding to each BWP of the N serving cells is the same; or,

[0154] The frequency domain resource allocation types corresponding to the channels of the BWPs of the N serving cells are the same; or,

[0155] The second configuration information corresponding to the channels of the BWPs of the N serving cells is the same.

[0156] The phrase "each BWP in the N serving cells" may refer to all BWPs in the N serving cells. For example, assuming that the N serving cells are two serving cells, and each serving cell is configured with four BWPs, then the phrase "each BWP in the N serving cells corresponds to the same frequency domain resource allocation type" means that the frequency domain resource allocation types corresponding to the eight BWPs in the two serving cells are all the same. Similar descriptions in the embodiments are to be understood in the same manner and will not be elaborated upon.

[0157] Among them, all BWPs of the N service cells corresponding to the N channels scheduled by the above-mentioned first DCI can be configured with the same frequency domain resource allocation type. That is to say, when the network device schedules the channels of the terminal device through the first DCI, it can schedule the channels to which the BWPs of the N service cells corresponding to the same frequency domain resource allocation type through the first DCI.

[0158] Alternatively, all BWPs in the service cell where the N channels scheduled by the above-mentioned first DCI are located can be configured with the same frequency domain resource allocation type, that is, when the network device schedules the channels of the terminal device through the first DCI, it can schedule the N channels in the BWP corresponding to the same frequency domain resource allocation type through the first DCI.

[0159] That is to say, when the terminal device subsequently determines the resources of the channel scheduled by the network device through the first DCI, the same frequency domain resource allocation type can be determined for the N channels.

[0160] For another example, in some embodiments, the terminal device does not expect that the frequency domain resource allocation types corresponding to the BWPs of the N serving cells are different or partially the same; or,

[0161] The terminal device does not expect that the second configuration information corresponding to each BWP of the N serving cells is different or partially the same; or,

[0162] The terminal device does not expect that the frequency domain resource allocation types corresponding to the channels of each BWP of the N serving cells are different or partially the same; or,

[0163] The terminal device does not expect that the second configuration information corresponding to the channels of each BWP of the N serving cells is different or partially the same.

[0164] Accordingly, when the network device performs resource scheduling through the first DCI, it can determine that the frequency domain resource allocation type / second configuration information corresponding to each BWP of the N service cells is the same, or it can determine that the frequency domain resource allocation type / second configuration information corresponding to the channel of each BWP of the N service cells is the same.

[0165] In other embodiments, the terminal device does not expect to receive a first DCI in which the frequency domain resource allocation types corresponding to the various BWPs of the scheduled N service cells are different or partially the same; or, the terminal device does not expect to receive a first DCI in which the second configuration information corresponding to the various BWPs of the scheduled N service cells is different or partially the same; or, the terminal device does not expect to receive a first DCI in which the frequency domain resource allocation types corresponding to the channels of the various BWPs of the scheduled N service cells are different or partially the same; or, the terminal device does not expect to receive a first DCI in which the second configuration information corresponding to the channels of the various BWPs of the scheduled N service cells is different or partially the same.

[0166] In the case where the N serving cells can also be divided into at least one serving cell sub-combination, the second configuration information can be used to configure the same frequency domain resource allocation type for each BWP of each serving cell in a single serving cell sub-combination, or for each channel of each BWP of each serving cell in a single serving cell sub-combination. In other words, the frequency domain resource allocation type can be configured based on the granularity of all BWPs in each serving cell in the serving cell sub-combination, or all channels in all BWPs in each serving cell in the serving cell sub-combination. In this way, multiple channels with different frequency domain resource allocation types can be scheduled using a single DCI, thereby achieving more flexible DCI scheduling.

[0167] For example, in some embodiments, the frequency domain resource allocation type corresponding to each BWP of each serving cell belonging to the same serving cell sub-group is the same; the serving cell sub-group includes part of the N serving cells; or,

[0168] The second configuration information corresponding to each BWP of each serving cell belonging to the same serving cell sub-group is the same; or,

[0169] The frequency domain resource allocation type corresponding to the channels of the BWPs of the serving cells belonging to the same serving cell sub-group is the same; or,

[0170] The second configuration information corresponding to the channels of the BWPs of the serving cells belonging to the same serving cell sub-group is the same.

[0171] Among them, the N channels scheduled by the above-mentioned first DCI can belong to at least two service cell sub-combinations, and all BWPs of the service cells in each service cell sub-combination are configured with the same frequency domain resource allocation type, or in other words, the channels to which all BWPs of the service cells in each service cell sub-combination belong are configured with the same frequency domain resource allocation type.

[0172] Among them, the BWPs of each service cell in the same service cell sub-combination may refer to all BWPs in all service cells in the same service cell sub-combination; for example, assuming that the service cell sub-combination includes cell1 and cell2, cell1 includes BWP1 and BWP2, and cell2 includes BWP3 and BWP4, then the BWPs of each service cell in the service cell sub-combination refer to BWP1 in cell1, BWP2 in cell1, BWP3 in cell2, and BWP4 in cell2.

[0173] When the terminal device subsequently determines the resources of the channel scheduled by the network device through the first DCI, the same frequency domain resource allocation type can be determined for the channels of the BWP of the service cell belonging to the same service cell sub-combination among the N channels; correspondingly, different frequency domain resource allocation types can be determined for the channels of the BWP of the service cell that do not belong to the same service cell sub-combination among the N channels.

[0174] That is to say, when the network device schedules the channel of the terminal device through the first DCI, it can schedule two or more groups of channels through the first DCI, and the BWP of the service cell corresponding to each group of channels has the same frequency domain resource allocation type.

[0175] For another example, in some embodiments, the terminal device does not expect that the frequency domain resource allocation types corresponding to the respective BWPs of the serving cells belonging to the same serving cell sub-combination are different or partially the same; the serving cell sub-combination includes part of the N serving cells; or,

[0176] The terminal device does not expect that the second configuration information corresponding to each BWP of each serving cell belonging to the same serving cell sub-group is different or partially the same; or,

[0177] The terminal device does not expect that the frequency domain resource allocation types corresponding to the channels of the various BWPs of the various serving cells belonging to the same serving cell sub-combination are different or partially the same; or,

[0178] The terminal device does not expect that the second configuration information corresponding to the channels of the BWPs of the service cells belonging to the same service cell sub-group is different or partially the same.

[0179] Accordingly, when the network device performs resource scheduling through the first DCI, it can determine that the frequency domain resource allocation type / second configuration information corresponding to each BWP of each service cell belonging to the same service cell sub-combination is the same, or it can determine that the frequency domain resource allocation type / second configuration information corresponding to the channel of each BWP of each service cell belonging to the same service cell sub-combination is the same.

[0180] In other embodiments, the terminal device does not expect to receive a first DCI in which the frequency domain resource allocation types corresponding to the various BWPs of each service cell belonging to the same service cell sub-combination are different or partially the same; or, the terminal device does not expect to receive a first DCI in which the second configuration information corresponding to the various BWPs of each service cell belonging to the same service cell sub-combination is different or partially the same; or, the terminal device does not expect to receive a first DCI in which the frequency domain resource allocation types corresponding to the channels of the various BWPs of each service cell belonging to the same service cell sub-combination are different or partially the same; or, the terminal device does not expect to receive a first DCI in which the second configuration information corresponding to the channels of the various BWPs of each service cell belonging to the same service cell sub-combination is different or partially the same.

[0181] Alternatively, the second configuration information can be used to configure the same frequency domain resource allocation type for the BWP combination or the channels in the BWP combination. In other words, the frequency domain resource allocation type can be configured at the granularity of the BWP combination or all channels in the BWP combination. This can also unify the frequency domain resource allocation type of at least one channel scheduled in a DCI, reducing the overhead of the frequency domain resource allocation type indication.

[0182] For example, in some embodiments, in the N serving cells, the frequency domain resource allocation types corresponding to the BWP combinations that can be scheduled by the first DCI are the same; or,

[0183] In the N serving cells, the second configuration information corresponding to the BWP combination that can be scheduled by the first DCI is the same; or,

[0184] In the N serving cells, the second configuration information corresponding to the channels of the BWP combination that can be scheduled by the first DCI is the same; or,

[0185] In the N serving cells, the second configuration information corresponding to the channels of the BWP combination that can be scheduled by the first DCI is the same.

[0186] The BWP combination that can be scheduled by the first DCI may refer to a BWP combination that is allowed to be scheduled by the first DCI, or a BWP combination that can be scheduled by the first DCI.

[0187] The above-mentioned BWP combination refers to a combination of multiple BWPs that can be scheduled by the same DCI.

[0188] Among them, among the BWPs of the N service cells corresponding to the N channels scheduled by the above-mentioned first DCI, the BWP combination scheduled by the first DCI is allowed to be configured with the same frequency domain resource allocation type, that is, when the network device schedules the channel of the terminal device through the first DCI, it can schedule the channel in the BWP corresponding to the same frequency domain resource allocation type through the first DCI.

[0189] Alternatively, among all the BWPs in the serving cell where the N channels scheduled by the first DCI are located, some BWPs may be configured with the same frequency domain resource allocation type.

[0190] For another example, in some embodiments, the terminal device does not expect that the frequency domain resource allocation types corresponding to the BWP combination that can be scheduled by the first DCI in the N serving cells are different or partially the same; or,

[0191] The terminal device does not expect that the second configuration information corresponding to the BWP combination that can be scheduled by the first DCI in the N serving cells is different or partially the same; or,

[0192] The terminal device does not expect that the frequency domain resource allocation types corresponding to the channels of the BWP combination that can be scheduled by the first DCI in the N serving cells are different or partially the same; or,

[0193] The terminal device does not expect that the second configuration information corresponding to the channels of the BWP combination that can be scheduled by the first DCI in N serving cells is different or partially the same.

[0194] The BWP combination in the above-mentioned N serving cells refers to a combination composed of some BWPs in each BWP in the N serving cells.

[0195] Accordingly, when the network device performs resource scheduling through the first DCI, it can determine that the frequency domain resource allocation type / second configuration information corresponding to the BWP combination that can be scheduled by the first DCI in N service cells is the same, or it can determine that the frequency domain resource allocation type / second configuration information corresponding to the channel of the BWP combination that can be scheduled by the first DCI in N service cells is the same.

[0196] In other embodiments, the terminal device does not expect to receive a first DCI whose frequency domain resource allocation type corresponding to the BWP combination that is allowed / can / can be scheduled by the first DCI in the N scheduled service cells is different or partially the same; or, the terminal device does not expect to receive a first DCI whose second configuration information corresponding to the BWP combination that is allowed / can / can be scheduled by the first DCI in the N scheduled service cells is different or partially the same; or, the terminal device does not expect to receive a first DCI whose second configuration information corresponding to the channel of the BWP combination that is allowed / can / can be scheduled by the first DCI in the N scheduled service cells is different or partially the same; or, the terminal device does not expect to receive a first DCI whose second configuration information corresponding to the channel of the BWP combination that is allowed / can / can be scheduled by the first DCI in the N scheduled service cells is different or partially the same.

[0197] In the case where the N serving cells can also be divided into at least one serving cell sub-combination, the second configuration information can also be used to configure the same frequency domain resource allocation type for a single BWP combination in a single serving cell sub-combination, or for the channels included in a single BWP combination in a single serving cell sub-combination; in other words, the frequency domain resource allocation type can be configured with a single BWP combination in a serving cell sub-combination, or with all channels included in a single BWP combination in a serving cell sub-combination as the granularity. In this way, multiple channels with different frequency domain resource allocation types can be scheduled using one DCI, thereby achieving more flexible DCI scheduling.

[0198] For example, in some embodiments, in each serving cell belonging to the same serving cell sub-group, the frequency domain resource allocation type corresponding to the BWP combination that can be scheduled by the first DCI is the same; the serving cell sub-group includes part of the N serving cells; or,

[0199] In each serving cell belonging to the same serving cell sub-group, the second configuration information corresponding to the BWP combination that can be scheduled by the first DCI is the same; or,

[0200] In each serving cell belonging to the same serving cell sub-group, the frequency domain resource allocation type corresponding to the channels of the BWP combination that can be scheduled by the first DCI is the same; or,

[0201] In each serving cell belonging to the same serving cell sub-group, the second configuration information corresponding to the channels of the BWP combination that can be scheduled by the first DCI is the same.

[0202] The above-mentioned BWP combination in each serving cell belonging to the same serving cell sub-combination refers to a combination consisting of some BWPs in each BWP of each serving cell belonging to the same serving cell sub-combination.

[0203] Among them, the N channels scheduled by the above-mentioned first DCI can belong to at least two service cell sub-combinations, and the frequency domain resource allocation type of all BWP combinations of service cells in each service cell sub-combination is the same, or in other words, the channels of all BWP combinations of service cells in each service cell sub-combination are configured with the same frequency domain resource allocation type.

[0204] When the terminal device subsequently determines the resources of the channel scheduled by the network device through the first DCI, the same frequency domain resource allocation type can be determined for the channels of the BWP combination belonging to the same serving cell sub-combination among the N channels.

[0205] That is to say, when the network device schedules the channel of the terminal device through the first DCI, it can schedule two or more groups of channels through the first DCI, and each group of channels belongs to a BWP combination in a service cell sub-combination.

[0206] For another example, in some embodiments, the terminal device does not expect that the frequency domain resource allocation types corresponding to the BWP combinations that can be scheduled by the first DCI in each serving cell belonging to the same serving cell sub-combination are different or partially the same; the serving cell sub-combination includes part of the N serving cells; or,

[0207] The terminal device does not expect that the second configuration information corresponding to the BWP combination that can be scheduled by the first DCI in each serving cell belonging to the same serving cell sub-combination is different or partially the same; or,

[0208] The terminal device does not expect that, in each serving cell belonging to the same serving cell sub-combination, the frequency domain resource allocation types corresponding to the channels of the BWP combination that can be scheduled by the first DCI are different or partially the same; or,

[0209] The terminal device does not expect that, in each service cell belonging to the same service cell sub-combination, the second configuration information corresponding to the channels of the BWP combination that can be scheduled by the first DCI is different or partially the same.

[0210] Accordingly, when the network device performs resource scheduling through the first DCI, it can determine that in each service cell belonging to the same service cell sub-combination, the frequency domain resource allocation type / second configuration information corresponding to the BWP combination that can be scheduled by the first DCI is the same, or it can determine that in each service cell belonging to the same service cell sub-combination, the frequency domain resource allocation type / second configuration information corresponding to the channel of the BWP combination that can be scheduled by the first DCI is the same.

[0211] In other embodiments, the terminal device does not expect to receive a first DCI in which the frequency domain resource allocation type corresponding to the BWP combination that is allowed / can / can be scheduled by the first DCI in the service cell belonging to the same service cell sub-combination is different or partially the same; or, the terminal device does not expect to receive a first DCI in which the second configuration information corresponding to the BWP combination that is allowed / can / can be scheduled by the first DCI in the service cell belonging to the same service cell sub-combination is different or partially the same; or, the terminal device does not expect to receive a first DCI in which the frequency domain resource allocation type corresponding to the channel of the BWP combination that is allowed / can / can be scheduled by the first DCI in the service cell belonging to the same service cell sub-combination is different or partially the same; or, the terminal device does not expect to receive a first DCI in which the second configuration information corresponding to the channel of the BWP combination that is allowed / can / can be scheduled by the first DCI in the service cell belonging to the same service cell sub-combination is different or partially the same.

[0212] Among them, in solution 1 of the embodiment of the present application, the terminal device receives configuration information 1 sent by the network device, and the configuration information 1 is used to configure the frequency domain resource allocation type of N serving cells. The configuration information 1 is configured per cell or per BWP. The terminal device determines the frequency domain resource allocation type corresponding to the N channels in the following manner:

[0213] Method 1: The terminal device does not expect that the frequency domain resource allocation types configured for the N service cells or the service cells of each subgroup are different, or in other words, the corresponding configuration information 1 (corresponding to the above-mentioned first configuration information) is different; Corresponding positive description: The frequency domain resource allocation types configured for the N service cells or the service cells of each subgroup are the same, or the corresponding configuration information 1 (corresponding to the above-mentioned first configuration information) is the same.

[0214] Method 2: The terminal device does not expect that all BWPs of N service cells or service cells of each subgroup are configured with different frequency domain resource allocation types, or that the corresponding configuration information 1 (corresponding to the above-mentioned first configuration information) is different; Corresponding positive description: All BWPs of N service cells or service cells of each subgroup are configured with the same frequency domain resource allocation type, or that the corresponding configuration information 1 (corresponding to the above-mentioned first configuration information) is the same.

[0215] Method three: The terminal device does not expect that the frequency domain resource allocation types configured for the BWP (sub) groups corresponding to the N service cells or the service cells of each subgroup (which can be scheduled together with 1-mode multiple DCI) are different, or in other words, the corresponding configuration information 1 (corresponding to the above-mentioned second configuration information) is different; Corresponding positive description: The frequency domain resource allocation types configured for the BWP (sub) groups corresponding to the N service cells or the service cells of each subgroup (which can be scheduled together with 1-mode multiple DCI) are the same, or the corresponding configuration information 1 (corresponding to the above-mentioned second configuration information) is the same.

[0216] The above “corresponding frequency domain resource allocation types are different” means that the configured configuration information 1 is different. If the configuration information 1 is all configured as Type 0, or all configured as Type 1, or all configured as dynamic switch, then the “corresponding frequency domain resource allocation types are the same”.

[0217] Option 2:

[0218] In some embodiments, the configuration information of the resource allocation type includes third configuration information; wherein, the third configuration information is used to configure the frequency domain resource allocation type of all service cell combinations or service cell sub-combinations of the terminal device; the above-mentioned service cell combination includes at least one service cell that can be jointly scheduled by the first DCI, and the service cell sub-combination includes a part of at least one service cell that can be scheduled by the first DCI.

[0219] The at least one serving cell that can be co-scheduled by the first DCI can be understood as N serving cells that can be co-scheduled by the first DCI. The above-mentioned "co-scheduled" can be understood as "simultaneous scheduling", that is, a serving cell combination can be a combination of N serving cells that can be simultaneously scheduled by the first DCI.

[0220] In other words, the configuration information of the above-mentioned resource allocation type includes third configuration information corresponding to all service cell combinations or service cell sub-combinations of the terminal device; the third configuration information is used to configure the frequency domain resource allocation type of all service cell combinations or service cell sub-combinations of the terminal device; the above-mentioned service cell combination is a set of N service cells that can be scheduled by the first DCI, and the service cell sub-combination is a set of some of the N service cells that can be scheduled by the first DCI.

[0221] Among them, each of the above-mentioned service cell combinations is a combination of multiple service cells that can be scheduled by the first DCI; this combination can be further divided into multiple sub-combinations; if the terminal has 3 cells cell 1 to cell 3, the first DCI can schedule N=2 or N=3 cells, then all service cell combinations that can be scheduled by the first DCI may include: {cell 1+cell 2}, {cell 2+cell 3}, {cell1+cell 3}, {cell 1+cell 2+cell 3}, "all" refers to the above 4 service cell combinations, among which N service cells are {cell 1+cell 2} or {cell 2+cell 3} or {cell1+cell 3} or {cell 1+cell 2+cell 3}. Optionally, taking the service cell combination {cell 1+cell 2+cell 3} as an example, it can also be divided into two service cell sub-combinations: {(cell 1+cell 2), (cell 3)}, where cell 1+cell 2 is one service cell sub-combination, and cell 3 independently constitutes another service cell sub-combination.

[0222] The network device may configure the third configuration information for all serving cell combinations or serving cell subcombinations in the terminal device. That is, one piece of third configuration information may be configured for all serving cell combinations or serving cell subcombinations in the terminal device. In this case, one piece of third configuration information may configure the frequency domain resource allocation type for all serving cell combinations or serving cell subcombinations in the terminal device.

[0223] In some embodiments, all serving cell combinations or serving cell subcombinations refer to all serving cell combinations or serving cell subcombinations in a Physical Uplink Control Channel (PUCCH) group; a PUCCH group is a group of serving cells.

[0224] In some embodiments, the configuration information of the resource allocation type includes fourth configuration information; wherein the fourth configuration information is used to configure the frequency domain resource allocation type of the service cell combination or the service cell sub-combination; the above-mentioned service cell combination includes at least one service cell that can be jointly scheduled by the first DCI, and the service cell sub-combination includes a part of at least one service cell that can be scheduled by the first DCI.

[0225] In other words, the configuration information includes the fourth configuration information corresponding to each service cell combination or service cell sub-combination of the terminal device; the fourth configuration information is used to configure the frequency domain resource allocation type of the service cell combination or service cell sub-combination corresponding to the fourth configuration information.

[0226] The network device may configure the fourth configuration information for a serving cell combination or serving cell subcombination in the terminal device. That is, a piece of fourth configuration information may be configured for each serving cell combination or serving cell subcombination of the terminal device. In this case, one piece of fourth configuration information may configure the frequency domain resource allocation type for a serving cell combination or serving cell subcombination of the terminal device.

[0227] In some embodiments, the configuration information of the resource allocation type includes fifth configuration information; wherein the fifth configuration information is used to configure the frequency domain resource allocation type of the BWP combination in the service cell combination or the service cell sub-combination; the above-mentioned service cell combination includes at least one service cell that can be jointly scheduled by the first DCI, and the service cell sub-combination includes a part of at least one service cell that can be scheduled by the first DCI.

[0228] In other words, the configuration information of the resource allocation type includes the fifth configuration information corresponding to each service cell combination or each BWP combination in the service cell sub-combination of the terminal device; the fifth configuration information is used to configure the frequency domain resource allocation type of the BWP combination corresponding to the fifth configuration information; the above-mentioned service cell combination is a set composed of N service cells scheduled by the first DCI, and the service cell sub-combination is a set composed of some of the N service cells scheduled by the first DCI.

[0229] The network device may configure the third configuration information for the BWP combination in the terminal device, that is, for each BWP group in each serving cell combination or serving cell subcombination of the terminal device, a third configuration information may be configured. In this case, a third configuration information may configure the frequency domain resource allocation type of a BWP group in a serving cell combination or serving cell subcombination of the terminal device.

[0230] In solution 2 of the embodiment of the present application, the terminal device receives configuration information 2 sent by the network device, and the configuration information 2 is used to configure a frequency domain resource allocation type dedicated to one-to-many modulation; specifically, the N service cells can be regarded as a service cell combination that can be scheduled by the first DCI, and the M subgroups can be regarded as M service cell sub-combinations that can be scheduled by the first DCI.

[0231] Mode 1: Configuration information 2 (corresponding to the third configuration information) is applicable to / corresponds to all possible serving cell combinations corresponding to the first DCI, or all possible serving cell sub-combinations, which means that configuration information 2 is configured per-UE, per-PUCCH group (for each PUCCH group), or per-cell group (for each cell group);

[0232] Mode 2: Configuration information 2 (corresponding to the fourth configuration information) is applicable to / corresponds to a single serving cell combination or a single serving cell sub-combination corresponding to the first DCI; this means that configuration information 2 is configured per-serving cell combination / per-serving cell sub-combination;

[0233] Mode 3: Configuration information 2 (corresponding to the fifth configuration information) is applicable to / corresponds to a single group of BWPs of a single serving cell combination corresponding to the first DCI, or a single group of BWPs of a single serving cell sub-combination; this means that configuration information 2 is configured for a per-BWP group.

[0234] The relationships among the concepts of User Equipment (UE), cell group, PUCCH group, serving cell combination, and serving cell sub-combination are as follows:

[0235] The network device can configure up to two cell groups for the terminal device, such as the Master Cell Group (MCG) and / or the Secondary Cell Group (SCG);

[0236] Each cell group may contain one or two PUCCH groups.

[0237] Each cell group or each PUCCH group may include one or more serving cell combinations, and the cells in each serving cell combination can be scheduled simultaneously by the first DCI;

[0238] Each serving cell combination may include one or more serving cell sub-combinations.

[0239] The technical effects of the above-mentioned schemes 1 and 2 include: limiting the N channels scheduled by the first DCI, or the channels in a subgroup to correspond to the same frequency domain resource allocation type. This can save DCI overhead on the one hand, and on the other hand, when N channels or channels in a subgroup share the FDRA indication domain, it can minimize the complexity of the scheduling algorithm.

[0240] Solution 1 can reuse the existing frequency domain resource allocation configuration mechanism to the greatest extent possible, saving additional signaling overhead and standardization work; while Solution 2 offers more flexible scheduling and configuration.

[0241] In some embodiments, the frequency domain resource allocation type of the first channel is a first type, the first type including frequency domain resource allocation type 0 (which may be referred to as type 0) or frequency domain resource allocation type 1 (which may be referred to as type 1); the first channel is any one of the N channels;

[0242] The first type is indicated by configuration information of the resource allocation type; or, the first type is determined based on the configuration information of the resource allocation type and the first DCI.

[0243] For example, when the first type is indicated by the configuration information of the resource allocation type, the terminal device can directly determine that the resource allocation type of the first channel is type 0 or type 1 based on the configuration content corresponding to the first channel in the configuration information of the above resource allocation type; that is, the resource allocation type of the first channel is explicitly indicated by the configuration information of the above resource allocation type.

[0244] For another example, when the first type is determined based on the configuration information of the resource allocation type and the first DCI, the configuration information of the resource allocation type configures the first channel to be dynamically switched. At this time, the terminal device can determine, based on the first indication field in the first DCI, that the frequency domain resource allocation type corresponding to the first channel is type 0 or type 1. In other words, the resource allocation type of the first channel is indirectly indicated by the configuration information of the resource allocation type.

[0245] In some embodiments, the first indication field in the above-mentioned first DCI may be a part of the FDRA field; or, the above-mentioned first indication field may be a dedicated indication field outside the FDRA field, for example, the dedicated indication field is used to indicate the frequency domain resource allocation type of one or more channels scheduled by a DCI.

[0246] For example, if the configuration information 1 or configuration information 2 of the corresponding resource allocation type is configured as Type-0 or Type-1, the frequency domain resource allocation type of the channel corresponding to the N service cells or the service cells in each sub-combination is Type-0 or Type-1; if the configuration information of the corresponding resource allocation type is configured as dynamic switch, the first indication field in the first DCI indicates that the frequency domain resource allocation type of the channel corresponding to the N service cells or the service cells in each sub-combination is indicated by the DCI, for example, the first indication field is 0, corresponding to Type-0, the first indication field is 1, corresponding to Type-1, and the first indication field can be part of the FDRA field, or a dedicated indication field.

[0247] The following describes several solutions involved in the above embodiments of the present application using different embodiments:

[0248] Example 1 (corresponding to the second method in the above solution 1):

[0249] The network device configures a cell group for the terminal device, such as MCG. The MCG contains one PUCCH group. The MCG contains four serving cells, cell 1 to cell 4. Each cell contains two BWPs, BWP 1 and BWP2.

[0250] The network device configures the terminal device with a co-scheduled cell combination that can be scheduled together with the DCI of one modulation through high-layer signaling configuration or protocol pre-defined method, including: 1) cell 1 + cell 2; 2) cell 3 + cell 4; or, according to another working method, the protocol stipulates the use of a bitmap in the DCI to indicate the cells that can be scheduled simultaneously with the DCI of one modulation, for example, 4 cells correspond to 4 bits. If the protocol does not make an agreement, the DCI of one modulation can schedule any 1 / 2 / 3 / 4 cells of the 4 cells. The protocol can also stipulate which cells can be scheduled together, such as the previous: 1) cell 1 + cell 2; 2) cell 3 + cell 4.

[0251] For example, DCI can only schedule two cell combinations: 1) cell 1 + cell 2; 2) cell 3 + cell 4, and does not restrict the BWP used by the cells scheduled together.

[0252] The terminal device receives configuration information 1 of the base station. Configuration information 1 is used to configure the frequency domain resource allocation type. If it is per-BWP configuration, the terminal device does not expect cell 1, BWP1, cell 2, BWP1, cell 1, BWP2, cell 2, BWP 2, and the corresponding frequency domain resource allocation types are different; similarly, the terminal device does not expect cell 3, BWP1, cell 4, BWP1, cell 3, BWP2, cell 4, BWP 2, and the corresponding frequency domain resource allocation types are different.

[0253] Example 2 (corresponding to the third method in the above solution 1):

[0254] The configuration of the network device is the same as that in the first embodiment. The only difference is that the network device configuration or protocol agreement limits: BWP1 of cell 1 can only be scheduled together with BWP1 of cell 2, BWP2 of cell 1 can only be scheduled together with BWP2 of cell 2, and the same applies to cells 3 / 4.

[0255] According to the above solution one method three:

[0256] The terminal device receives configuration information 1 from the base station. Configuration information 1 is used to configure the frequency domain resource allocation type. If per-BWP is configured, the terminal device does not expect cell 1, BWP1, or cell 2, BWP1, as the corresponding frequency domain resource allocation types are different. The terminal device does not expect cell 1, BWP2, or cell 2, BWP2, as the corresponding frequency domain resource allocation types are different. Similarly, the terminal device does not expect cell 3, BWP1, or cell 4, BWP1, as the corresponding frequency domain resource allocation types are different. It does not expect cell 3, BWP2, or cell 4, BWP2, as the corresponding frequency domain resource allocation types are different.

[0257] Example 3 (corresponding to the method 1 in the above solution 2):

[0258] The configuration and scheduling methods of the network equipment are the same as those in the first embodiment.

[0259] The terminal device receives configuration information 2, which is used to configure the frequency domain resource allocation type of all possible service cell combinations corresponding to the first DCI. For example, if configuration information 2 is configured as Type 0, no matter whether the first DCI is used to schedule cell 1+cell 2 or cell 3+cell 4, and no matter which BWPs of the above cells are scheduled, the frequency domain resource allocation type corresponding to the scheduled channel is Type 0.

[0260] Example 4 (corresponding to the second method in the above-mentioned solution 2):

[0261] The configuration and scheduling methods of the network equipment are the same as those in the first embodiment.

[0262] The terminal device receives configuration information 2, which is a per-service cell combination configuration. For example, the configuration information 2 corresponding to cell 1+cell 2 is Type 0, and the configuration information 2 corresponding to cell 3+cell 4 is dynamic switch. When the first DCI schedules cell 1+cell 2, the frequency domain resource allocation type corresponding to the scheduled channel is Type 0. When the first DCI schedules cell 3+cell 4, the frequency domain resource allocation type corresponding to the scheduled channels is the same and is indicated by the DCI.

[0263] Example 5 (corresponding to the third method in the above-mentioned solution 2):

[0264] The configuration and scheduling methods of the network devices are the same as those in the second embodiment.

[0265] The terminal device receives configuration information 2, which is configured per-BWP group. For example, the configuration information 2 corresponding to cell 1 BWP1+cell 2 BWP1 is Type 0; the configuration information 2 corresponding to cell 1 BWP2+cell 2 BWP2 is Type 1; the configuration information 2 corresponding to cell 3 BWP1+cell 4 BWP1 is dynamic switch; and the configuration information 2 corresponding to cell 3 BWP2+cell 4 BWP2 is dynamic switch.

[0266] When the first DCI schedules cell 1 BWP1+cell 2 BWP1, the frequency domain resource allocation type corresponding to the scheduled channel is Type0; when the first DCI schedules cell 1 BWP2+cell 2 BWP2, the frequency domain resource allocation type corresponding to the scheduled channel is Type1; when the first DCI schedules cell 3 BWP1+cell 4 BWP1, or cell 3 BWP2+cell 4 BWP2, the frequency domain resource allocation type corresponding to the scheduled channels is the same and is indicated by the DCI.

[0267] To sum up, the scheme shown in the embodiment of the present application, for the case where at least one channel is scheduled through one DCI, the terminal device determines the frequency domain resource allocation type corresponding to N channels through the received configuration information of the resource allocation type, or through the configuration information and the received DCI, thereby improving the scheme for determining the frequency domain resource allocation type when scheduling one or more channels through a single DCI and improving the efficiency of resource scheduling.

[0268] Among them, the above scheme can use a shared indication domain to carry the configuration information of the frequency domain resource allocation type, or can use an independent indication domain to carry the configuration information of the frequency domain resource allocation type, and can realize scheduling of multiple channels with the same frequency domain resource allocation type through one DCI, without the need to indicate each channel separately. Therefore, regardless of whether a shared indication domain or an independent indication domain is used, the DCI overhead can be reduced and the scheduling algorithm on the network side can be simplified to a certain extent.

[0269] Please refer to Figure 6, which shows a block diagram of a device for determining a frequency domain resource allocation type provided by an embodiment of the present application. The device for determining a frequency domain resource allocation type has the function of implementing the method shown in Figure 3 or Figure 5 above, which is performed by the terminal device. As shown in Figure 6, the device may include:

[0270] Receiving module 601, configured to receive configuration information of resource allocation type;

[0271] The configuration information of the resource allocation type is used to determine the frequency domain resource allocation type of N channels, the N channels are scheduled by the first downlink control information DCI, and the N channels correspond to N service cells; N is greater than or equal to 1, and N is an integer.

[0272] In some embodiments, the apparatus further comprises a determination module configured to determine the frequency domain resource allocation type of the N channels according to the configuration information of the resource allocation type.

[0273] In some embodiments, the configuration information of the resource allocation type includes first configuration information;

[0274] The first configuration information is used to configure the frequency domain resource allocation type of the serving cell; or

[0275] The first configuration information is used to configure the frequency domain resource allocation type of the channel corresponding to the serving cell.

[0276] In some embodiments, the frequency domain resource allocation type corresponding to each serving cell in the N serving cells is the same; or,

[0277] The first configuration information corresponding to each serving cell in the N serving cells is the same; or,

[0278] The frequency domain resource allocation type corresponding to each channel in the N channels is the same; or,

[0279] The first configuration information corresponding to each channel in the N channels is the same.

[0280] In some embodiments, the frequency domain resource allocation type corresponding to each serving cell belonging to the same serving cell sub-combination is the same; the serving cell sub-combination includes part of the N serving cells; or,

[0281] The first configuration information corresponding to each serving cell belonging to the same serving cell sub-group is the same; or,

[0282] The frequency domain resource allocation types corresponding to the channels belonging to the same serving cell sub-combination are the same; or,

[0283] The first configuration information corresponding to each channel belonging to the same serving cell sub-combination is the same.

[0284] In some embodiments, the terminal device does not expect that the frequency domain resource allocation types corresponding to the N serving cells are different or partially the same; or,

[0285] The terminal device does not expect that the first configuration information corresponding to each serving cell in the N serving cells is different or partially the same; or,

[0286] The terminal device does not expect that the frequency domain resource allocation types corresponding to the N channels are different or partially the same; or,

[0287] The terminal device does not expect that the first configuration information corresponding to each channel in the N channels is different or partially the same.

[0288] In some embodiments, the terminal device does not expect that the frequency domain resource allocation types corresponding to the serving cells belonging to the same serving cell sub-combination are different or partially the same; the serving cell sub-combination includes part of the N serving cells; or,

[0289] The terminal device does not expect that the first configuration information corresponding to each serving cell belonging to the same serving cell sub-group is different or partially the same; or,

[0290] The terminal device does not expect that the frequency domain resource allocation types corresponding to the channels belonging to the same serving cell sub-combination are different or partially the same; or,

[0291] The terminal device does not expect that the first configuration information corresponding to each channel belonging to the same service cell sub-combination is different or partially the same.

[0292] In some embodiments, the configuration information of the resource allocation type includes second configuration information;

[0293] The second configuration information is used to configure the frequency domain resource allocation type of the bandwidth part BWP of the serving cell; or, the second configuration information is used to configure the frequency domain resource allocation type corresponding to the channel of the BWP.

[0294] In some embodiments, the frequency domain resource allocation type corresponding to each BWP of the N serving cells is the same; or,

[0295] The second configuration information corresponding to each BWP of the N serving cells is the same; or,

[0296] The frequency domain resource allocation types corresponding to the channels of the BWPs of the N serving cells are the same; or,

[0297] The second configuration information corresponding to the channels of the BWPs in the N serving cells is the same.

[0298] In some embodiments, the frequency domain resource allocation type corresponding to each BWP of each serving cell belonging to the same serving cell sub-combination is the same; the serving cell sub-combination includes part of the N serving cells; or,

[0299] The second configuration information corresponding to each BWP of each serving cell belonging to the same serving cell sub-group is the same; or,

[0300] The frequency domain resource allocation type corresponding to the channels of the BWPs of the serving cells belonging to the same serving cell sub-group is the same; or,

[0301] The second configuration information corresponding to the channels of the BWPs of the serving cells belonging to the same serving cell sub-group is the same.

[0302] In some embodiments, the terminal device does not expect that the frequency domain resource allocation types corresponding to the respective BWPs of the N serving cells are different or partially the same; or,

[0303] The terminal device does not expect that the second configuration information corresponding to each BWP of the N serving cells is different or partially the same; or,

[0304] The terminal device does not expect that the frequency domain resource allocation types corresponding to the channels of the respective BWPs of the N serving cells are different or partially the same; or,

[0305] The terminal device does not expect that the second configuration information corresponding to the channels of each BWP of the N serving cells is different or partially the same.

[0306] In some embodiments, the terminal device does not expect that the frequency domain resource allocation types corresponding to the respective BWPs of the serving cells belonging to the same serving cell subcombination are different or partially the same; the serving cell subcombination includes part of the N serving cells; or,

[0307] The terminal device does not expect that the second configuration information corresponding to each BWP of each serving cell belonging to the same serving cell sub-combination is different or partially the same; or,

[0308] The terminal device does not expect that the frequency domain resource allocation types corresponding to the channels of the various BWPs of the various serving cells belonging to the same serving cell sub-group are different or partially the same; or,

[0309] The terminal device does not expect that the second configuration information corresponding to the channels of each BWP of each service cell belonging to the same service cell sub-combination is different or partially the same.

[0310] In some embodiments, in the N serving cells, the frequency domain resource allocation types corresponding to the BWP combinations that can be scheduled by the first DCI are the same; or,

[0311] In the N serving cells, the second configuration information corresponding to the BWP combinations that can be scheduled by the first DCI is the same; or,

[0312] In the N serving cells, the second configuration information corresponding to the channels of the BWP combination that can be scheduled by the first DCI is the same; or,

[0313] In the N serving cells, the second configuration information corresponding to the channels of the BWP combination that can be scheduled by the first DCI is the same.

[0314] In some embodiments, in each serving cell belonging to the same serving cell sub-group, the frequency domain resource allocation type corresponding to the BWP combination that can be scheduled by the first DCI is the same; the serving cell sub-group includes part of the N serving cells; or,

[0315] In each serving cell belonging to the same serving cell sub-group, the second configuration information corresponding to the BWP combination that can be scheduled by the first DCI is the same; or,

[0316] In each serving cell belonging to the same serving cell sub-group, the frequency domain resource allocation type corresponding to the channels of the BWP combination that can be scheduled by the first DCI is the same; or,

[0317] In each serving cell belonging to the same serving cell sub-group, the second configuration information corresponding to the channels of the BWP combination that can be scheduled by the first DCI is the same.

[0318] In some embodiments, the terminal device does not expect that the frequency domain resource allocation types corresponding to the BWP combinations that can be scheduled by the first DCI in the N serving cells are different or partially the same; or,

[0319] The terminal device does not expect that the second configuration information corresponding to the BWP combination that can be scheduled by the first DCI in the N serving cells is different or partially the same; or,

[0320] The terminal device does not expect that the second configuration information corresponding to the channels of the BWP combination that can be scheduled by the first DCI in the N serving cells is different or partially the same; or,

[0321] The terminal device does not expect that the second configuration information corresponding to the channels of the BWP combination that can be scheduled by the first DCI in the N serving cells is different or partially the same.

[0322] In some embodiments, the terminal device does not expect that the frequency domain resource allocation types corresponding to the BWP combinations that can be scheduled by the first DCI are different or partially the same in each serving cell belonging to the same serving cell subcombination; the serving cell subcombination includes part of the N serving cells; or,

[0323] The terminal device does not expect that, in each serving cell belonging to the same serving cell sub-combination, the second configuration information corresponding to the BWP combination that can be scheduled by the first DCI is different or partially the same; or,

[0324] The terminal device does not expect that, in each serving cell belonging to the same serving cell sub-combination, the frequency domain resource allocation types corresponding to the channels of the BWP combination that can be scheduled by the first DCI are different or partially the same; or,

[0325] The terminal device does not expect that, in each service cell belonging to the same service cell sub-combination, the second configuration information corresponding to the channels of the BWP combination that can be scheduled by the first DCI is different or partially the same.

[0326] In some embodiments, the configuration information of the resource allocation type includes third configuration information;

[0327] In which, the third configuration information is used to configure the frequency domain resource allocation type of all service cell combinations or service cell sub-combinations of the terminal device; the above-mentioned service cell combination includes at least one service cell that can be jointly scheduled by the first DCI, and the service cell sub-combination includes a part of at least one service cell that can be scheduled by the first DCI.

[0328] In some embodiments, the all serving cell combinations or serving cell sub-combinations refer to all serving cell combinations or serving cell sub-combinations in a physical uplink control channel PUCCH group; the PUCCH group is a group of serving cells.

[0329] In some embodiments, the configuration information of the resource allocation type includes fourth configuration information;

[0330] Among them, the fourth configuration information is used to configure the frequency domain resource allocation type of the service cell combination or the service cell sub-combination; the above-mentioned service cell combination includes at least one service cell that can be jointly scheduled by the first DCI, and the service cell sub-combination includes a part of at least one service cell that can be scheduled by the first DCI.

[0331] In some embodiments, the configuration information of the resource allocation type includes fifth configuration information;

[0332] Among them, the fifth configuration information is used to configure the frequency domain resource allocation type of the BWP combination in the service cell combination or the service cell sub-combination; the above-mentioned service cell combination includes at least one service cell that can be jointly scheduled by the first DCI, and the service cell sub-combination includes a part of at least one service cell that can be scheduled by the first DCI.

[0333] In some embodiments, the frequency domain resource allocation type of the first channel is a first type, the first type includes frequency domain resource allocation type 0 or frequency domain resource allocation type 1; the first channel is any one of the N channels;

[0334] The first type is indicated by configuration information of the resource allocation type; or, the first type is determined based on the configuration information of the resource allocation type and the first DCI.

[0335] Please refer to Figure 7, which shows a block diagram of a device for determining a frequency domain resource allocation type provided by an embodiment of the present application. The device for determining a frequency domain resource allocation type has the function of implementing the method shown in Figure 4 or Figure 5 above, which is performed by a network device. As shown in Figure 7, the device may include:

[0336] A sending module 701 is configured to send configuration information of a resource allocation type to a terminal device;

[0337] The configuration information of the resource allocation type is used to determine the frequency domain resource allocation type of N channels, the N channels are scheduled by the first downlink control information DCI, and the N channels correspond to N service cells; N is greater than or equal to 1, and N is an integer.

[0338] In some embodiments, the apparatus further includes: a determination module configured to determine configuration information of a resource allocation type of a terminal device.

[0339] In some embodiments, the configuration information of the resource allocation type includes first configuration information;

[0340] The first configuration information is used to configure the frequency domain resource allocation type of the serving cell; or

[0341] The first configuration information is used to configure the frequency domain resource allocation type of the channel corresponding to the serving cell.

[0342] In some embodiments, the frequency domain resource allocation type corresponding to each serving cell in the N serving cells is the same; or,

[0343] The first configuration information corresponding to each serving cell in the N serving cells is the same; or,

[0344] The frequency domain resource allocation type corresponding to each channel in the N channels is the same; or,

[0345] The first configuration information corresponding to each channel in the N channels is the same.

[0346] In some embodiments, the frequency domain resource allocation type corresponding to each serving cell belonging to the same serving cell sub-combination is the same; the serving cell sub-combination includes part of the N serving cells; or,

[0347] The first configuration information corresponding to each serving cell belonging to the same serving cell sub-group is the same; or,

[0348] The frequency domain resource allocation types corresponding to the channels belonging to the same serving cell sub-combination are the same; or,

[0349] The first configuration information corresponding to each channel belonging to the same serving cell sub-combination is the same.

[0350] In some embodiments, the configuration information of the resource allocation type includes second configuration information;

[0351] The second configuration information is used to configure the frequency domain resource allocation type of the bandwidth part BWP of the serving cell; or, the second configuration information is used to configure the frequency domain resource allocation type corresponding to the channel of the BWP.

[0352] In some embodiments, the frequency domain resource allocation type corresponding to each BWP of the N serving cells is the same; or,

[0353] The second configuration information corresponding to each BWP of the N serving cells is the same; or,

[0354] The frequency domain resource allocation types corresponding to the channels of the BWPs of the N serving cells are the same; or,

[0355] The second configuration information corresponding to the channels of the BWPs in the N serving cells is the same.

[0356] In some embodiments, the frequency domain resource allocation type corresponding to each BWP of each serving cell belonging to the same serving cell sub-combination is the same; the serving cell sub-combination includes part of the N serving cells; or,

[0357] The second configuration information corresponding to each BWP of each serving cell belonging to the same serving cell sub-group is the same; or,

[0358] The frequency domain resource allocation type corresponding to the channels of the BWPs of the serving cells belonging to the same serving cell sub-group is the same; or,

[0359] The second configuration information corresponding to the channels of the BWPs of the serving cells belonging to the same serving cell sub-group is the same.

[0360] In some embodiments, in the N serving cells, the frequency domain resource allocation types corresponding to the BWP combinations that can be scheduled by the first DCI are the same; or,

[0361] In the N serving cells, the second configuration information corresponding to the BWP combinations that can be scheduled by the first DCI is the same; or,

[0362] In the N serving cells, the second configuration information corresponding to the channels of the BWP combination that can be scheduled by the first DCI is the same; or,

[0363] In the N serving cells, the second configuration information corresponding to the channels of the BWP combination that can be scheduled by the first DCI is the same.

[0364] In some embodiments, in each serving cell belonging to the same serving cell sub-group, the frequency domain resource allocation type corresponding to the BWP combination that can be scheduled by the first DCI is the same; the serving cell sub-group includes part of the N serving cells; or,

[0365] In each serving cell belonging to the same serving cell sub-group, the second configuration information corresponding to the BWP combination that can be scheduled by the first DCI is the same; or,

[0366] In each serving cell belonging to the same serving cell sub-group, the frequency domain resource allocation type corresponding to the channels of the BWP combination that can be scheduled by the first DCI is the same; or,

[0367] In each serving cell belonging to the same serving cell sub-group, the second configuration information corresponding to the channels of the BWP combination that can be scheduled by the first DCI is the same.

[0368] In some embodiments, the configuration information of the resource allocation type includes third configuration information;

[0369] In which, the third configuration information is used to configure the frequency domain resource allocation type of all service cell combinations or service cell sub-combinations of the terminal device; the above-mentioned service cell combination includes at least one service cell that can be jointly scheduled by the first DCI, and the service cell sub-combination includes a part of at least one service cell that can be scheduled by the first DCI.

[0370] In some embodiments, the all serving cell combinations or serving cell sub-combinations refer to all serving cell combinations or serving cell sub-combinations in a physical uplink control channel PUCCH group; the PUCCH group is a group of serving cells.

[0371] In some embodiments, the configuration information of the resource allocation type includes fourth configuration information;

[0372] Among them, the fourth configuration information is used to configure the frequency domain resource allocation type of the service cell combination or the service cell sub-combination; the above-mentioned service cell combination includes at least one service cell that can be jointly scheduled by the first DCI, and the service cell sub-combination includes a part of at least one service cell that can be scheduled by the first DCI.

[0373] In some embodiments, the configuration information of the resource allocation type includes fifth configuration information;

[0374] Among them, the fifth configuration information is used to configure the frequency domain resource allocation type of the BWP combination in the service cell combination or the service cell sub-combination; the above-mentioned service cell combination includes at least one service cell that can be jointly scheduled by the first DCI, and the service cell sub-combination includes a part of at least one service cell that can be scheduled by the first DCI.

[0375] In some embodiments, the frequency domain resource allocation type of the first channel is a first type, the first type includes frequency domain resource allocation type 0 or frequency domain resource allocation type 1; the first channel is any one of the N channels;

[0376] The first type is indicated by configuration information of the resource allocation type; or, the first type is determined based on the configuration information of the resource allocation type and the first DCI.

[0377] It should be noted that the device provided in the above embodiment only uses the division of the above-mentioned functional modules as an example to implement its functions. In actual applications, the above-mentioned functions can be assigned to different functional modules according to actual needs, that is, the content structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0378] Regarding the apparatus in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0379] Please refer to FIG8 , which shows a schematic diagram of the structure of a communication device 800 provided in one embodiment of the present application. The communication device 800 may include: a processor 801 , a receiver 802 , a transmitter 803 , a memory 804 , and a bus 805 .

[0380] The processor 801 includes one or more processing cores. The processor 801 executes various functional applications and information processing by running software programs and modules.

[0381] The receiver 802 and the transmitter 803 may be implemented as a communication component, which may be a communication chip, which may also be called a transceiver.

[0382] The memory 804 is connected to the processor 801 via a bus 805 .

[0383] The memory 804 may be used to store a computer program, and the processor 801 may be used to execute the computer program to implement each step in the above method embodiment.

[0384] In addition, the memory 804 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, including but not limited to: magnetic disk or optical disk, electrically erasable programmable read-only memory, erasable programmable read-only memory, static random access memory, read-only memory, magnetic memory, flash memory, and programmable read-only memory.

[0385] In an exemplary scenario, when the communication device 800 is implemented as the above-mentioned terminal device, the processor executes the computer program so that the terminal device implements each step performed by the terminal device in the method shown in either Figure 3 or Figure 5.

[0386] For example, the transceiver (which may correspond to the receiving module 601 in FIG. 6 ) is configured to receive configuration information of a resource allocation type, wherein the configuration information of the resource allocation type is used to determine frequency domain resource allocation types for N channels, where the N channels are scheduled by first downlink control information (DCI), and the N channels correspond to N serving cells; where N is greater than or equal to 1 and is an integer. The processor (which may correspond to the determination module involved in the embodiment shown in FIG. 6 ) is configured to determine the frequency domain resource allocation types for the N channels based on the configuration information of the resource allocation type.

[0387] In an exemplary scenario, when the communication device 800 is implemented as a network device, the processor executes the computer program to enable the network device to implement the various steps performed by the network device in the method shown in either FIG. 4 or FIG. 5 .

[0388] For example, the transceiver (which may correspond to the sending module 701 in FIG. 7 ) is configured to send configuration information of the resource allocation type to the terminal device. The processor (which may correspond to the determining module involved in the embodiment shown in FIG. 7 ) is configured to determine the configuration information of the resource allocation type of the terminal device.

[0389] An embodiment of the present application also provides a computer-readable storage medium, which stores a computer program. The computer program is loaded and executed by a processor to implement all or part of the steps performed by the terminal device or network device in the method shown in Figure 3, Figure 4 or Figure 5 above.

[0390] The present application also provides a chip, which is used to run in a communication device so that the communication device executes all or part of the steps performed by the terminal device or network device in the method shown in Figure 3, Figure 4 or Figure 5 above.

[0391] The present application also provides a computer program product, which includes computer instructions stored in a computer-readable storage medium. A processor of a communication device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the communication device to perform all or part of the steps performed by the terminal device or network device in the method shown in Figures 3, 4, or 5 above.

[0392] The present application also provides a computer program, which is executed by a processor of a communication device to implement all or part of the steps performed by a terminal device or a network device in the method shown in Figure 3, Figure 4 or Figure 5 above.

[0393] Those skilled in the art will appreciate that in one or more of the above examples, the functions described in the embodiments of the present application can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any media that facilitates the transmission of computer programs from one place to another. The storage medium can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0394] The above description is merely an exemplary embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A method for determining a frequency domain resource allocation type, characterized in that: The method comprises: The terminal device receives configuration information of the resource allocation type; The configuration information of the resource allocation type is used to determine the frequency domain resource allocation type of N channels, the N channels are scheduled by the first downlink control information DCI, and the N channels correspond to N service cells; N is greater than or equal to 1, and N is an integer.

2. The method according to claim 1, characterized in that The configuration information of the resource allocation type includes first configuration information; The first configuration information is used to configure the frequency domain resource allocation type of the serving cell; or The first configuration information is used to configure the frequency domain resource allocation type of the channel corresponding to the serving cell.

3. The method according to claim 2, characterized in that The frequency domain resource allocation type corresponding to each serving cell in the N serving cells is the same; or, The first configuration information corresponding to each serving cell in the N serving cells is the same; or, The frequency domain resource allocation type corresponding to each channel in the N channels is the same; or, The first configuration information corresponding to each channel in the N channels is the same.

4. The method according to claim 2, characterized in that The frequency domain resource allocation type corresponding to each serving cell belonging to the same serving cell sub-combination is the same; the serving cell sub-combination includes part of the N serving cells; or, The first configuration information corresponding to each serving cell belonging to the same serving cell sub-group is the same; or, The frequency domain resource allocation types corresponding to the channels belonging to the same serving cell sub-combination are the same; or, The first configuration information corresponding to each channel belonging to the same serving cell sub-combination is the same.

5. The method according to claim 2, characterized in that The terminal device does not expect that the frequency domain resource allocation types corresponding to the N serving cells are different or partially the same; or, The terminal device does not expect that the first configuration information corresponding to each serving cell in the N serving cells is different or partially the same; or, The terminal device does not expect that the frequency domain resource allocation types corresponding to the N channels are different or partially the same; or, The terminal device does not expect that the first configuration information corresponding to each channel in the N channels is different or partially the same.

6. The method according to claim 2, characterized in that The terminal device does not expect that the frequency domain resource allocation types corresponding to the serving cells belonging to the same serving cell sub-combination are different or partially the same; the serving cell sub-combination includes part of the N serving cells; or, The terminal device does not expect that the first configuration information corresponding to each serving cell belonging to the same serving cell sub-group is different or partially the same; or, The terminal device does not expect that the frequency domain resource allocation types corresponding to the channels belonging to the same serving cell sub-combination are different or partially the same; or, The terminal device does not expect that the first configuration information corresponding to each channel belonging to the same service cell sub-combination is different or partially the same.

7. The method according to claim 1, characterized in that The configuration information of the resource allocation type includes second configuration information; The second configuration information is used to configure the frequency domain resource allocation type of the bandwidth part BWP of the serving cell; or, the second configuration information is used to configure the frequency domain resource allocation type corresponding to the channel of the BWP.

8. The method according to claim 7, characterized in that The frequency domain resource allocation types corresponding to the BWPs of the N serving cells are the same; or, The second configuration information corresponding to each BWP of the N serving cells is the same; or, The frequency domain resource allocation type corresponding to the channels of the BWPs of the N serving cells is the same; or, The second configuration information corresponding to the channels of the BWPs in the N serving cells is the same.

9. The method according to claim 7, characterized in that The frequency domain resource allocation type corresponding to each BWP of each serving cell belonging to the same serving cell sub-combination is the same; the serving cell sub-combination includes part of the N serving cells; or, The second configuration information corresponding to each BWP of each serving cell belonging to the same serving cell sub-group is the same; or, The frequency domain resource allocation type corresponding to the channels of the BWPs of the serving cells belonging to the same serving cell sub-group is the same; or, The second configuration information corresponding to the channels of the BWPs of the serving cells belonging to the same serving cell sub-group is the same.

10. The method according to claim 7, characterized in that The terminal device does not expect that the frequency domain resource allocation types corresponding to the BWPs of the N serving cells are different or partially the same; or, The terminal device does not expect that the second configuration information corresponding to each BWP of the N serving cells is different or partially the same; or, The terminal device does not expect that the frequency domain resource allocation types corresponding to the channels of the respective BWPs of the N serving cells are different or partially the same; or, The terminal device does not expect that the second configuration information corresponding to the channels of each BWP of the N serving cells is different or partially the same.

11. The method according to claim 7, characterized in that The terminal device does not expect that the frequency domain resource allocation types corresponding to the respective BWPs of the serving cells belonging to the same serving cell sub-combination are different or partially the same; the serving cell sub-combination includes part of the N serving cells; or, The terminal device does not expect that the second configuration information corresponding to each BWP of each serving cell belonging to the same serving cell sub-combination is different or partially the same; or, The terminal device does not expect that the frequency domain resource allocation types corresponding to the channels of the various BWPs of the various serving cells belonging to the same serving cell sub-group are different or partially the same; or, The terminal device does not expect that the second configuration information corresponding to the channels of each BWP of each service cell belonging to the same service cell sub-combination is different or partially the same.

12. The method according to claim 7, characterized in that In the N serving cells, the frequency domain resource allocation types corresponding to the BWP combinations that can be scheduled by the first DCI are the same; or, In the N serving cells, the second configuration information corresponding to the BWP combinations that can be scheduled by the first DCI is the same; or, In the N serving cells, the second configuration information corresponding to the channels of the BWP combination that can be scheduled by the first DCI is the same; or, In the N serving cells, the second configuration information corresponding to the channels of the BWP combination that can be scheduled by the first DCI is the same.

13. The method according to claim 7, characterized in that In each serving cell belonging to the same serving cell sub-combination, the frequency domain resource allocation type corresponding to the BWP combination that can be scheduled by the first DCI is the same; the serving cell sub-combination includes part of the N serving cells; or, In each serving cell belonging to the same serving cell sub-group, the second configuration information corresponding to the BWP combination that can be scheduled by the first DCI is the same; or, In each serving cell belonging to the same serving cell sub-group, the frequency domain resource allocation type corresponding to the channels of the BWP combination that can be scheduled by the first DCI is the same; or, In each serving cell belonging to the same serving cell sub-group, the second configuration information corresponding to the channels of the BWP combination that can be scheduled by the first DCI is the same.

14. The method according to claim 7, wherein: The terminal device does not expect that the frequency domain resource allocation types corresponding to the BWP combinations that can be scheduled by the first DCI in the N serving cells are different or partially the same; or, The terminal device does not expect that the second configuration information corresponding to the BWP combination that can be scheduled by the first DCI in the N serving cells is different or partially the same; or, The terminal device does not expect that the second configuration information corresponding to the channels of the BWP combination that can be scheduled by the first DCI in the N serving cells is different or partially the same; or, The terminal device does not expect that the second configuration information corresponding to the channels of the BWP combination that can be scheduled by the first DCI in the N serving cells is different or partially the same.

15. The method according to claim 7, characterized in that The terminal device does not expect that the frequency domain resource allocation types corresponding to the BWP combinations that can be scheduled by the first DCI are different or partially the same in each serving cell belonging to the same serving cell sub-combination; the serving cell sub-combination includes part of the N serving cells; or The terminal device does not expect that, in each serving cell belonging to the same serving cell sub-combination, the second configuration information corresponding to the BWP combination that can be scheduled by the first DCI is different or partially the same; or, The terminal device does not expect that, in each serving cell belonging to the same serving cell sub-combination, the frequency domain resource allocation types corresponding to the channels of the BWP combination that can be scheduled by the first DCI are different or partially the same; or, The terminal device does not expect that, in each service cell belonging to the same service cell sub-combination, the second configuration information corresponding to the channels of the BWP combination that can be scheduled by the first DCI is different or partially the same.

16. The method according to claim 1, wherein The configuration information of the resource allocation type includes third configuration information; In which, the third configuration information is used to configure the frequency domain resource allocation type of all service cell combinations or service cell sub-combinations of the terminal device; the service cell combination includes at least one service cell that can be jointly scheduled by the first DCI, and the service cell sub-combination includes a part of at least one service cell that can be scheduled by the first DCI.

17. The method according to claim 16, characterized in that The all serving cell combinations or serving cell sub-combinations refer to all serving cell combinations or serving cell sub-combinations in a physical uplink control channel PUCCH group; the PUCCH group is a group of serving cells.

18. The method according to claim 1, wherein The configuration information of the resource allocation type includes fourth configuration information; The fourth configuration information is used to configure the frequency domain resource allocation type of the service cell combination or the service cell sub-combination; the service cell combination includes at least one service cell that can be jointly scheduled by the first DCI, and the service cell sub-combination includes a part of at least one service cell that can be scheduled by the first DCI.

19. The method according to claim 1, wherein The configuration information of the resource allocation type includes fifth configuration information; The fifth configuration information is used to configure the frequency domain resource allocation type of the BWP combination in the service cell combination or the service cell sub-combination; the service cell combination includes at least one service cell that can be jointly scheduled by the first DCI, and the service cell sub-combination includes a part of at least one service cell that can be scheduled by the first DCI.

20. The method according to any one of claims 1 to 19, characterized in that The frequency domain resource allocation type of the first channel is a first type, where the first type includes frequency domain resource allocation type 0 or frequency domain resource allocation type 1; the first channel is any one of the N channels; The first type is indicated by configuration information of the resource allocation type; or The first type is determined based on configuration information of the resource allocation type and the first DCI.

21. A method for determining a frequency domain resource allocation type, characterized in that: The method comprises: The network device sends configuration information of resource allocation type to the terminal device; The configuration information of the resource allocation type is used to determine the frequency domain resource allocation type of N channels, the N channels are scheduled by the first downlink control information DCI, and the N channels correspond to N service cells; N is greater than or equal to 1, and N is an integer.

22. The method according to claim 21, characterized in that The configuration information of the resource allocation type includes first configuration information; The first configuration information is used to configure the frequency domain resource allocation type of the serving cell; or The first configuration information is used to configure the frequency domain resource allocation type of the channel corresponding to the serving cell.

23. The method according to claim 22, characterized in that The frequency domain resource allocation type corresponding to each serving cell in the N serving cells is the same; or, The first configuration information corresponding to each serving cell in the N serving cells is the same; or, The frequency domain resource allocation type corresponding to each channel in the N channels is the same; or, The first configuration information corresponding to each channel in the N channels is the same.

24. The method according to claim 22, characterized in that The frequency domain resource allocation type corresponding to each serving cell belonging to the same serving cell sub-combination is the same; the serving cell sub-combination includes part of the N serving cells; or, The first configuration information corresponding to each serving cell belonging to the same serving cell sub-group is the same; or, The frequency domain resource allocation types corresponding to the channels belonging to the same serving cell sub-combination are the same; or, The first configuration information corresponding to each channel belonging to the same serving cell sub-combination is the same.

25. The method according to claim 21, characterized in that The configuration information of the resource allocation type includes second configuration information; The second configuration information is used to configure the frequency domain resource allocation type of the bandwidth part BWP of the serving cell; or, the second configuration information is used to configure the frequency domain resource allocation type corresponding to the channel of the BWP.

26. The method according to claim 25, characterized in that The frequency domain resource allocation types corresponding to the BWPs of the N serving cells are the same; or, The second configuration information corresponding to each BWP of the N serving cells is the same; or, The frequency domain resource allocation type corresponding to the channels of the BWPs of the N serving cells is the same; or, The second configuration information corresponding to the channels of the BWPs in the N serving cells is the same.

27. The method according to claim 25, characterized in that The frequency domain resource allocation type corresponding to each BWP of each serving cell belonging to the same serving cell sub-combination is the same; the serving cell sub-combination includes part of the N serving cells; or, The second configuration information corresponding to each BWP of each serving cell belonging to the same serving cell sub-group is the same; or, The frequency domain resource allocation type corresponding to the channels of the BWPs of the serving cells belonging to the same serving cell sub-group is the same; or, The second configuration information corresponding to the channels of the BWPs of the serving cells belonging to the same serving cell sub-group is the same.

28. The method according to claim 25, characterized in that In the N serving cells, the frequency domain resource allocation types corresponding to the BWP combinations that can be scheduled by the first DCI are the same; or, In the N serving cells, the second configuration information corresponding to the BWP combinations that can be scheduled by the first DCI is the same; or, In the N serving cells, the second configuration information corresponding to the channels of the BWP combination that can be scheduled by the first DCI is the same; or, In the N serving cells, the second configuration information corresponding to the channels of the BWP combination that can be scheduled by the first DCI is the same.

29. The method according to claim 25, characterized in that In each serving cell belonging to the same serving cell sub-combination, the frequency domain resource allocation type corresponding to the BWP combination that can be scheduled by the first DCI is the same; the serving cell sub-combination includes part of the N serving cells; or, In each serving cell belonging to the same serving cell sub-group, the second configuration information corresponding to the BWP combination that can be scheduled by the first DCI is the same; or, In each serving cell belonging to the same serving cell sub-group, the frequency domain resource allocation type corresponding to the channels of the BWP combination that can be scheduled by the first DCI is the same; or, In each serving cell belonging to the same serving cell sub-group, the second configuration information corresponding to the channels of the BWP combination that can be scheduled by the first DCI is the same.

30. The method according to claim 21, wherein The configuration information of the resource allocation type includes third configuration information; In which, the third configuration information is used to configure the frequency domain resource allocation type of all service cell combinations or service cell sub-combinations of the terminal device; the service cell combination includes at least one service cell that can be jointly scheduled by the first DCI, and the service cell sub-combination includes a part of at least one service cell that can be scheduled by the first DCI.

31. The method according to claim 30, wherein The all serving cell combinations or serving cell sub-combinations refer to all serving cell combinations or serving cell sub-combinations in a physical uplink control channel PUCCH group; the PUCCH group is a group of serving cells.

32. The method according to claim 21, wherein The configuration information of the resource allocation type includes fourth configuration information; The fourth configuration information is used to configure the frequency domain resource allocation type of the service cell combination or the service cell sub-combination; the service cell combination includes at least one service cell that can be jointly scheduled by the first DCI, and the service cell sub-combination includes a part of at least one service cell that can be scheduled by the first DCI.

33. The method according to claim 21, wherein The configuration information of the resource allocation type includes fifth configuration information; The fifth configuration information is used to configure the frequency domain resource allocation type of the BWP combination in the service cell combination or the service cell sub-combination; the service cell combination includes at least one service cell that can be jointly scheduled by the first DCI, and the service cell sub-combination includes a part of at least one service cell that can be scheduled by the first DCI.

34. The method according to any one of claims 21 to 33, characterized in that The frequency domain resource allocation type of the first channel is a first type, where the first type includes frequency domain resource allocation type 0 or frequency domain resource allocation type 1; the first channel is any one of the N channels; The first type is indicated by configuration information of the resource allocation type; or The first type is determined based on configuration information of the resource allocation type and the first DCI.

35. A device for determining a frequency domain resource allocation type, characterized in that: The device comprises: A receiving module, configured to receive configuration information of a resource allocation type; The configuration information of the resource allocation type is used to determine the frequency domain resource allocation type of N channels, the N channels are scheduled by the first downlink control information DCI, and the N channels correspond to N service cells; N is greater than or equal to 1, and N is an integer.

36. A device for determining a frequency domain resource allocation type, characterized in that: The device comprises: A sending module, configured to send configuration information of resource allocation types to a terminal device; The configuration information of the resource allocation type is used to determine the frequency domain resource allocation type of N channels, the N channels are scheduled by the first downlink control information DCI, and the N channels correspond to N service cells; N is greater than or equal to 1, and N is an integer.

37. A terminal device, characterized in that: The terminal device includes a processor, a memory and a transceiver; A computer program is stored in the memory, and the processor executes the computer program so that the terminal device implements the method for determining the frequency domain resource allocation type as described in any one of claims 1 to 20 above.

38. A network device, characterized in that: The network device includes a processor, a memory and a transceiver; The memory stores a computer program, and the processor executes the computer program to enable the network device to implement the method for determining the frequency domain resource allocation type as described in any one of claims 21 to 34 above.

39. A computer-readable storage medium, characterized in that The storage medium stores a computer program, which is used to be executed by a processor to implement the configuration method for frequency domain resource allocation type as described in any one of claims 1 to 20, or to implement the determination method for frequency domain resource allocation type as described in any one of claims 21 to 34.

40. A chip, characterized in that: The chip is used to run in a communication device so that the communication device executes the method for determining the frequency domain resource allocation type as described in any one of claims 1 to 20, or implements the method for determining the frequency domain resource allocation type as described in any one of claims 21 to 34.

41. A computer program product, characterized in that The computer program product includes computer instructions, which are stored in a computer-readable storage medium; the processor of the communication device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, so that the communication device performs the method for determining the frequency domain resource allocation type as described in any one of claims 1 to 20, or implements the method for determining the frequency domain resource allocation type as described in any one of claims 21 to 34.

42. A computer program, characterized in that The computer program is executed by a processor of a communication device to implement the method for determining the frequency domain resource allocation type as described in any one of claims 1 to 20, or to implement the method for determining the frequency domain resource allocation type as described in any one of claims 21 to 34.

Images