WO2024060241A1 - Procédé et appareil de détermination de type d'attribution de ressources de domaine fréquentiel, et dispositif et support d'enrgistrement - Google Patents

Procédé et appareil de détermination de type d'attribution de ressources de domaine fréquentiel, et dispositif et support d'enrgistrement Download PDF

Info

Publication number
WO2024060241A1
WO2024060241A1 PCT/CN2022/121072 CN2022121072W WO2024060241A1 WO 2024060241 A1 WO2024060241 A1 WO 2024060241A1 CN 2022121072 W CN2022121072 W CN 2022121072W WO 2024060241 A1 WO2024060241 A1 WO 2024060241A1
Authority
WO
WIPO (PCT)
Prior art keywords
resource allocation
serving cell
same
configuration information
frequency domain
Prior art date
Application number
PCT/CN2022/121072
Other languages
English (en)
Chinese (zh)
Inventor
张轶
Original Assignee
Oppo广东移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to PCT/CN2022/121072 priority Critical patent/WO2024060241A1/fr
Publication of WO2024060241A1 publication Critical patent/WO2024060241A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems

Definitions

  • the present application relates to the field of mobile communication technology, and in particular to a method, device, equipment and storage medium for determining a frequency domain resource allocation type.
  • both uplink and downlink channels support two frequency domain resource allocation types, namely Type 0 frequency domain resource allocation type and Type 1 frequency domain resource allocation type.
  • the network device configures the frequency domain resource allocation type used by the terminal device through high-level signaling; specifically, the network device can indicate frequency domain resource allocation type 0 (Type0) or frequency domain resource allocation type 1 through high-level parameters. (Type 1) or dynamic switching (dynamicswitch), when "dynamic switching" is indicated through high-level parameters, the frequency domain resource allocation type used by the terminal is further indicated through a specific field in the downlink control information (Downlink Control Information, DCI). Type0 or Type 1.
  • DCI Downlink Control Information
  • Embodiments of the present application provide a method, device, equipment and storage medium for determining a frequency domain resource allocation type.
  • the technical solutions are as follows:
  • inventions of the present application provide a method for determining a frequency domain resource allocation type.
  • the method includes:
  • 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 serving cells; N Greater than or equal to 1, and N is an integer.
  • inventions of the present application provide a method for determining a frequency domain resource allocation type.
  • the method includes:
  • 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.
  • inventions of the present application provide a device for determining a frequency domain resource allocation type.
  • the device includes:
  • the receiving module is used to receive configuration information of 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 serving cells; N Greater than or equal to 1, and N is an integer.
  • inventions of the present application provide a device for determining a frequency domain resource allocation type.
  • the device includes:
  • the sending module is used to send 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 serving cells; N Greater than or equal to 1, and N is an integer.
  • embodiments of the present application provide a terminal device, which 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 above method for determining the frequency domain resource allocation type.
  • embodiments of the present application provide a network device, which 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 network device implements the above method for determining the frequency domain resource allocation type.
  • embodiments of the present application also provide a computer-readable storage medium.
  • a computer program is stored in the storage medium.
  • the computer program is loaded and executed by a processor to implement the above method for determining the frequency domain resource allocation type. .
  • the present application also provides a chip, which is used to run in a communication device, so that the communication device performs the above method for determining the frequency domain resource allocation type.
  • the present application provides a computer program product including computer instructions stored in a computer-readable storage medium.
  • the processor of the communication device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the communication device performs the above method for determining the frequency domain resource allocation type.
  • the present application provides a computer program, which is executed by a processor of a communication device to implement the above method for determining a frequency domain resource allocation type.
  • 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, which improves the The determination scheme of the frequency domain resource allocation type when one or more channels are scheduled by a single DCI improves the efficiency of resource scheduling.
  • Figure 1 is a schematic architectural diagram of a communication system provided by an embodiment of the present application.
  • FIG. 2 is a schematic diagram of two frequency domain resource allocation types involved in this application.
  • Figure 3 is a flow chart of a method for determining a frequency domain resource allocation type provided by an embodiment of the present application
  • Figure 4 is a flow chart of a method for determining a frequency domain resource allocation type provided by an embodiment of the present application
  • Figure 5 is a flow chart of a method for determining a frequency domain resource allocation type provided by an embodiment of the present application
  • FIG6 is a block diagram of a device for determining a frequency domain resource allocation type provided by an embodiment of the present application.
  • Figure 7 is a block diagram of a device for determining a frequency domain resource allocation type provided by an embodiment of the present application.
  • Figure 8 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 1 shows a schematic diagram of a communication system related to an exemplary embodiment of the present application.
  • the communication system 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 this application.
  • the network device 110 in this application provides wireless communication functions.
  • the network device 110 includes but is not limited to: Evolved Node B (Evolved Node B, eNB), Radio Network Controller (Radio Network Controller, RNC), Node B (Node B). , NB), base station controller (Base Station Controller, BSC), base transceiver station (Base Transceiver Station, BTS), home base station (for example, Home Evolved Node B, or Home Node B, HNB), baseband unit (Baseband Unit, BBU), Access Point (AP), wireless relay node, wireless backhaul node, transmission point (Transmission Point, TP) or sending and receiving point ( Transmission and Reception Point (TRP), etc., can also be the next generation node B (Next Generation Node B, gNB) or transmission point (TRP or TP) in the fifth generation (5th Generation, 5G) mobile communication system, or, for One or a group (including multiple antenna panels) antenna panels of a base station in a 5G system,
  • the terminal device 120 and/or the terminal device 130 in the present 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 equipment, user agent, user device.
  • the terminal includes but is 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 (MID), augmented reality (AR) terminals, virtual reality (VR) terminals and mixed reality (MR) terminals, wearable devices, handles, electronic tags, controllers, wireless terminals in industrial control (Industrial Control), wireless terminals in self-driving (Self Driving), wireless terminals in remote medical care (Remote Medical), wireless terminals in smart grid (Smart Grid) and so on.
  • MID mobile Internet devices
  • AR augmented reality
  • VR virtual reality
  • MR mixed reality
  • Wireless terminals in transportation safety wireless terminals in smart city, wireless terminals in smart home, wireless terminals in remote medical surgery, cellular phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistant (PDA), TV set-top box (STB), Customer Premise Equipment (CPE), etc.
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • STB TV set-top box
  • CPE Customer Premise Equipment
  • the network device 110 and the terminal device 120 communicate with each other through some air interface technology, such as the Uu interface.
  • uplink communication refers to sending signals to the network device 110
  • downlink communication refers to sending signals to the terminal device 120.
  • the terminal device 120 and the terminal device 130 communicate with each other through some air interface technology, such as Uu interface.
  • first side communication scenario refers to sending signals to the terminal device 130
  • second side communication refers to sending signals to the terminal device 120.
  • the terminal device 120 and the terminal device 130 are both within the network coverage and located in the same cell, or the terminal device 120 and the terminal device 130 are both within the network coverage but located in different cells, or the terminal device 120 is within the network coverage but the terminal Device 130 is outside network coverage.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • LTE-A Advanced Long Term Evolution
  • UMTS Universal Mobile Telecommunication System
  • WiMAX Global Internet Microwave Access
  • 5G mobile communication system New Radio (NR) system, evolution system of NR system, LTE on unlicensed spectrum (LTE-based access to unlicensed spectrum, LTE-U) systems, NR-based access to unlicensed spectrum (NR-U) systems on unlicensed spectrum
  • NR New Radio
  • NR may also be called 5G NR system or 5G system.
  • the 5G mobile communication system may include non-standalone networking (Non-Standalone, NSA) and/or standalone networking (Standalone, SA).
  • the technical solutions provided by the embodiments in this application can also be applied to Machine Type Communication (MTC), Long Term Evolution-Machine (LTE-M), and Device to Device. D2D) network, Machine to Machine (M2M) network, Internet of Things (IoT) network or other networks.
  • MTC Machine Type Communication
  • LTE-M Long Term Evolution-Machine
  • D2D Machine to Machine
  • M2M Machine to Machine
  • IoT Internet of Things
  • the IoT network may include, for example, the Internet of Vehicles.
  • the communication methods in the Internet of Vehicles system are collectively called Vehicle to X (V2X, X can represent anything).
  • the V2X can include: Vehicle to Vehicle (V2V) communication, vehicle and Infrastructure (Vehicle to Infrastructure, V2I) communication, communication between vehicles and pedestrians (Vehicle to Pedestrian, V2P) or vehicle and network (Vehicle to Network, V2N) communication, etc.
  • V2V Vehicle to Vehicle
  • V2I Vehicle to Infrastructure
  • V2P vehicle and Infrastructure
  • V2N Vehicle and network
  • both uplink and downlink support two frequency domain resource allocation types: (frequency domain) resource allocation type Type 0 and (frequency domain) resource allocation type Type 1.
  • the network device configures the frequency used by the terminal through the high-level parameter resourceAllocation. Domain resource allocation type.
  • the high-level parameter resourceAllocation is configured in the PDSCH-Config information element (Information Element, IE) or PUSCH-Config IE, and is configured for each bandwidth part (Bandwidth Part, BWP) (per BWP).
  • the frequency domain resource allocation Type0 and Type1 resource block indexing (Resource Block indexing, RB indexing) is determined in the terminal's active BWP (the BWP activated by the UE at a certain moment in the Radio Resource Control (RRC) connection state); if the terminal supports DCI-based BWP change, and the scheduling DCI is configured BWP indicator domain, then the RB indexing of frequency domain resource allocation Type 0 and Type 1 is determined based on the BWP indicated by the BWP indicator in 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 frequency domain resource allocation types involved in this application.
  • the granularity of frequency domain resource allocation Type 0 is Resource Block Group (RBG).
  • RBG is a combination of a series of continuous virtual RBs. Each RBG includes virtual RBs. The number is determined based on the BWP size (Size) 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 In PUSCH-Config, it is configured per BWP.
  • BWP Size configuration 1 configuration 2 1-36 2 4 37-72 4 8 73-144 8 16 145-275 16 16
  • Frequency domain resource allocation Type 0 uses a bitmap to indicate the RBG allocated to the terminal. 1 means to allocate this RBG to the terminal, 0 means not to allocate this RBG to the terminal, which can achieve flexible distribution of frequency domain resources within the BWP. , supports discontinuous resource allocation and can use discrete frequency domain transmission to combat frequency selective fading. But the disadvantages are: (1) the bitmap has a large number of bits and needs to cover every RBG in the entire BWP; (2) the resource allocation granularity is relatively coarse, because one RBG contains 2 to 16 RBs and cannot be allocated RB by RB (or Press RB to select resources one by one;
  • the total number of RBGs it contains N RBGs is:
  • the size of the first RBG is:
  • the size of the last RBG is:
  • the size of the remaining RBGs is P;
  • frequency domain resource allocation Type 1 can indicate a series of continuous virtual RBs to the terminal, using a resource indication value (Resource Indication Value, RIV) to the allocated starting RB (RB start ) and the number of RBs (L RBs ) are jointly encoded.
  • RIV Resource Indication Value
  • the advantage of Type 1 is that a smaller number of bits can be used to indicate RB-level resources, but the disadvantage is that it can only allocate continuous frequency domain resources. When the number of resources is small, frequency diversity is limited and it is susceptible to frequency selective fading.
  • the starting RB (RB start ) and the number of RBs (LRBs) are jointly encoded as follows:
  • L RBs is greater than or equal to 1, and does not exceed above Indicates rounding * down.
  • 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 why it is a "blind detection" is that the terminal detects the PDCCH bearer.
  • the DCI does not know the DCI format (format) and other information before, so it is necessary to use some fixed DCI size (size) to blindly detect the candidate PDCCH (PDCCH candidate) in the search space set.
  • the terminal does not expect the total DCI size number to be greater than 4, and the Cell-Radio Network Temporary Identifier (Cell-Radio Network Temporary Identifier, C-RNTI)
  • C-RNTI Cell-Radio Network Temporary Identifier
  • the terminal Since the terminal only tries to use some fixed DCI sizes to detect the PDCCH, this requires the terminal to know the DCI sizes of different DCI formats before blind detection of the PDCCH. In other words, it needs to know the size of each DCI contained in the DCI. What is the number of bits contained in each information field? Taking the frequency domain resource allocation indication field (Frequency Domain Resource Assignment, FDRA) as an example, the number of bits is determined as follows:
  • the indication field contains N RBG bits
  • the indication domain contains bits; where, log 2 (*) means taking the logarithm of *; is the number of RBs included in the downlink BWP;
  • the indication field contains: bits, max is the maximum value symbol; the highest bit is used to indicate the resource allocation type used by the terminal, 0 indicates type 0, and 1 indicates type 1.
  • Multi-Carrier Multi-Carrier
  • Type-1A field A single field indicating common information to all the co-scheduled cells (Type-1A field: A single field indicating common information to all the co-scheduled cells); where, the above-mentioned co-scheduled cells (co-scheduled cells) refers to cells that can be scheduled simultaneously by a DCI, which can also be called a serving cell combination;
  • Type-1B field A single field indicating separate information to each of co-scheduled cells via joint indication (Type-1B field: A single field indicating separate information to each of co-scheduled cells via joint indication);
  • Type-1C field A single field indicating an information to only one of co-scheduled cells.
  • Type-2 field the emphasis is on the separate field: the separate field corresponds to each cell in the co-scheduled cells (Separate field for each of the co-scheduled cells).
  • the Type 2 field contains multiple single fields, and each single field indicates information about one of the co-scheduled cells.
  • Type 3 field Based on the display 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 of the sub-groups composed of 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).
  • a sub-group is a subset of all co-scheduled cells, where a single field in the type 3 field is shared by 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). Among them, whether the type 3 field is a common field or a single field depends on the signaling configuration.
  • the DCI needs to contain resource allocation instructions for multiple channels.
  • FDRA frequency domain resource allocation
  • the advantage of sharing the same indication domain is that it can save DCI overhead, but resource allocation is not flexible enough, especially for inter-band Carrier Aggregation (inter-band CA), there is no correlation between the channels of each carrier, or For cells with different configured resource allocation types, if they share the same FDRA indication, the scheduling algorithm will become very complicated and the spectral efficiency will be reduced; the advantage of the independent indication domain is that resource allocation is more flexible and can achieve a more efficient High spectral efficiency, but due to independent indication, the number of bits required in the FDRA indication field increases exponentially, so DCI overhead increases and PDCCH reliability decreases.
  • inter-band CA inter-band Carrier Aggregation
  • the follow-up solution of this application focuses on the configuration and indication methods of frequency domain resource allocation types. It is applicable to the working methods of shared indication domain and independent indication domain. It can better balance the scheduling flexibility and DCI overhead, and can also simplify the network side. Scheduling Algorithm.
  • FIG 3 shows a flow chart of a method for determining a frequency domain resource allocation type provided by an embodiment of the present application.
  • This method can be executed by a terminal device, wherein the terminal device can be the network shown in Figure 1 Terminal device 120 or terminal device 130 in the architecture; the method may include the following steps:
  • Step 301 The terminal device receives the 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 serving cells; N is greater than or equal to 1, and N is an integer.
  • 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.
  • the terminal device determines the frequency domain resource allocation type corresponding to N channels through the received configuration information of the resource allocation type, which improves the This method provides a solution for determining the frequency domain resource allocation type when one or more channels are scheduled through a single DCI, thereby improving the efficiency of resource scheduling.
  • FIG 4 shows a flow chart of a method for determining a frequency domain resource allocation type provided by an embodiment of the present application.
  • This method can be executed by a network device, wherein the network device can be the network shown in Figure 1 Network devices 110 in the architecture.
  • This method can include the following steps:
  • 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, and the N channels are scheduled by the first downlink control information DCI.
  • Channels correspond to N serving cells; N is greater than or equal to 1, and N is an integer.
  • the network device when 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 uses the received configuration information of the resource allocation type. Determining the frequency domain resource allocation type corresponding to N channels improves the solution for determining the frequency domain resource allocation type when one or more channels are scheduled through a single DCI, and improves the efficiency of resource scheduling.
  • Figure 5 shows a flow chart of a method for determining a frequency domain resource allocation type provided by an embodiment of the present application.
  • This method can be performed by a terminal device and Network devices perform interactive execution; wherein, the above-mentioned terminal device and the network device may be the terminal device 120 and the network device 110 in the network architecture shown in Figure 1; or, the above-mentioned terminal device and the network device may be the terminal device and the network device in the network architecture shown in Figure 1. terminal equipment 130 and network equipment 110.
  • this method may include the following steps:
  • Step 501 The network device sends configuration information of the resource allocation type to the terminal device; the terminal device receives the configuration information of the resource allocation type.
  • the network device can configure or indicate the configuration information of the above resource allocation type through high-level parameters. Specifically, it can be configured or indicated through high-level parameters resourceAllocation.
  • the high-level parameters can be carried through high-level signaling (such as RRC signaling). .
  • the network device may configure configuration information dedicated to the resource allocation type when at least one channel is scheduled through one DCI through independent signaling or parameters other than the high-level parameter resourceAllocation.
  • Step 502 The network device sends the 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 serving cells; N is greater than or equal to 1, and N is an integer.
  • the above-mentioned N channels may be N data channels; each of the N channels corresponds to one of the N serving cells.
  • the above-mentioned N data channels may include N physical downlink shared channels (Physical Downlink Shared Channel, PDSCH) and/or physical uplink shared channel (Physical Uplink Shared Channel, PUSCH). That is to say, the above-mentioned first
  • the N channels scheduled by DCI can all be PDSCH, or all PUSCH, or part of PDSCH + part of PUSCH.
  • the network device does not limit whether the value of N is the same in each scheduling/configuration.
  • serving cell and “carrier” may be the same and may be replaced with each other.
  • Step 503 The terminal device determines the frequency domain resource allocation types of N channels according to the configuration information of the resource allocation types.
  • the method of configuring/instructing the frequency domain resource allocation type of N channels through the above configuration information can be divided into the following two solutions:
  • 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.
  • the configuration information of the resource allocation type includes the first configuration information corresponding to each of the N serving cells; the first configuration information is used to configure the frequency domain resource allocation type of the serving 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 serving cell corresponding to the first configuration information.
  • the above-mentioned first configuration information can be configured or indicated by the network device through a high-layer parameter, specifically, it can be configured or indicated through a high-layer parameter resourceAllocation.
  • the high-layer parameter can be carried through high-layer signaling (such as RRC signaling).
  • the above-mentioned first configuration information may be information configuring the frequency domain resource allocation type of the serving cell.
  • the above first configuration information may also be information configuring the frequency domain resource allocation type of the channel of the serving cell.
  • the first configuration information may be information that configures the frequency domain resource allocation type of the PDSCH of the serving cell, or the first configuration information may be information that configures the frequency domain resource allocation type of the PUSCH of the serving cell.
  • 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 correspond to the M serving cell sub-combinations, which may mean that the N serving cells are divided into M serving cell sub-combinations, 1 ⁇ M ⁇ N, and M is an integer.
  • the same frequency domain resource allocation type can be configured for N service cells or channels in N service cells; or, in other words, the frequency domain resource allocation type is configured with all N service cells/all channels in N service cells as the granularity. In this way, the frequency domain resource allocation type of at least one channel scheduled in a DCI can be unified, and the overhead of the frequency domain resource allocation type indication can be reduced.
  • the frequency domain resource allocation types corresponding to each of the N serving cells are the same; or,
  • the first configuration information corresponding to each of the N serving cells is the same; or,
  • the frequency domain resource allocation types corresponding to each of the N channels are the same; or,
  • the first configuration information corresponding to each channel among the N channels is the same.
  • the above-mentioned N serving cells correspond to the same frequency domain resource allocation type; or in other words, the above-mentioned N serving cells correspond to the same first configuration information.
  • each of the N serving cells corresponds to a first first configuration information. configuration information, and the contents of the first configuration information of each of the N serving cells are the same; or in other words, the above N channels correspond to the same frequency domain resource allocation type; or in other words, the above N channels correspond to the same first configuration Information, for example, each of the N channels corresponds to a piece of first configuration information, and the content of the first configuration information of each of the N channels is the same.
  • the N channels scheduled by the first DCI, or the N serving cells corresponding to the N channels are channels/serving cells configured with the same frequency domain resource allocation type.
  • the network device is configured with the terminal device When scheduling channels, you can select channels of N serving cells with the same frequency domain resource allocation type for scheduling in the first DCI, or select N channels with the same frequency domain resource allocation type for scheduling in the first DCI. Scheduling.
  • the N channels scheduled by the first DCI can be configured with the same frequency domain resource allocation type. That is to say, when the network device schedules the channel of the terminal device through the first DCI, it can schedule the same frequency domain resource allocation type through the first DCI. or N channels corresponding to the same frequency domain resource allocation type.
  • the terminal device when the terminal device subsequently determines the resources of the channels 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.
  • the terminal equipment does not expect that the frequency domain resource allocation types corresponding to each of the N serving cells are different or partially the same; or,
  • the terminal equipment does not expect that the first configuration information corresponding to each of the N serving cells is different or partially the same; or,
  • the terminal equipment does not expect that the frequency domain resource allocation types corresponding to each of 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 among the N channels is different or partially the same.
  • the network device 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.
  • the terminal device "not expecting” can be described in various ways, for example:
  • 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 (that is, the terminal device "does not expect” this scheduling behavior);
  • the terminal device receives the first DCI, and the first DCI schedules N serving cells.
  • the terminal device does not expect the N serving cells to be configured with different frequency domain resource allocation types (that is, it "does not expect” this configuration behavior).
  • the above-mentioned unexpected behavior of the terminal device means that the terminal device does not expect the first DCI received to satisfy a certain condition (that is, the frequency domain resource allocation types corresponding to 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 N channels are different or partially the same; or, the first configuration information corresponding to N channels is different or partially the same).
  • a certain condition that is, the frequency domain resource allocation types corresponding to 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 N channels are different or partially the same; or, the first configuration information corresponding to N channels is different or partially the same).
  • the terminal device may not expect to receive the first DCI that meets the above conditions. That is to say, the terminal device does not expect to receive the frequency domain resource allocation types corresponding to the scheduled N serving cells. or partially the same first DCI; or the terminal equipment does not expect to receive the first DCI with different or partially identical first configuration information corresponding to the scheduled N serving cells; or the terminal equipment does not expect to receive the scheduled N channels.
  • the first DCI whose corresponding frequency domain resource allocation types 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 scheduled N channels is different or partially the same.
  • the terminal device may regard the received first DCI as incorrect DCI and discard the first DCI.
  • the above-mentioned N serving cells can also be divided into at least one serving cell sub-combination, and the same frequency domain resource allocation type can be configured for the serving cells or channels in each serving cell sub-combination through the above-mentioned first configuration information; or in other words, to serve All channels in the cell subcombination/serving cell subcombination are granular, and the frequency domain resource allocation type is configured.
  • this solution can schedule channels of multiple different frequency domain resource allocation types through one DCI, thereby achieving more efficient Flexible DCI scheduling.
  • the frequency domain resource allocation types corresponding to each serving cell belonging to the same serving cell sub-combination are the same; the serving cell sub-combination includes some of the N serving cells; or,
  • the first configuration information corresponding to each serving cell belonging to the same serving cell sub-combination is the same; or,
  • the frequency domain resource allocation types corresponding to each channel 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.
  • the N channels scheduled by the first DCI can belong to at least two serving cell sub-combinations, and the serving cells in each serving cell sub-combination are configured with the same frequency domain resource allocation type, or in other words, each serving cell
  • the channels of the serving cells in the sub-combination are configured with the same frequency domain resource allocation type.
  • the serving cells in each serving cell subcombination are configured with the same frequency domain resource allocation type, and the N channels correspond to at least two serving cell combinations. Therefore, the channels in different serving cell subcombinations scheduled by the first DCI can correspond to Different frequency domain resource allocation types, thereby improving the flexibility of DCI scheduling.
  • the same frequency domain resource allocation type can be determined for the channels of the serving cells belonging to the same serving cell sub-combination among the N channels; accordingly, for the N channels Among the channels, channels of serving cells that do not belong to the same serving cell sub-combination may determine different frequency domain resource allocation types.
  • the network device 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.
  • the terminal equipment does not expect that the frequency domain resource allocation types corresponding to each serving cell belonging to the same serving cell sub-combination are different or partially the same; the serving cell sub-combination includes some of the N serving cells; or,
  • the terminal equipment does not expect that the first configuration information corresponding to each serving cell belonging to the same serving cell sub-combination is different or partially the same; or,
  • the terminal equipment 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 equipment does not expect that the first configuration information corresponding to each channel belonging to the same serving cell sub-combination is different or partially the same.
  • the network device 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 serving cell belonging to the same serving cell sub-combination is the same, or it can determine that the serving cells belonging to the same serving cell sub-combination have the same frequency domain resource allocation type/first configuration information.
  • the frequency domain resource allocation type/first configuration information corresponding to each combined channel is the same.
  • the terminal equipment does not expect to receive the first DCI with different or partially identical frequency domain resource allocation types corresponding to the serving cells belonging to the same serving cell sub-combination; or, the terminal equipment does not expect to receive the first DCI.
  • the first configuration information corresponding to each serving cell belonging to the same serving cell sub-combination is different or partially the same first DCI; or the terminal device does not expect to receive different frequency domain resource allocation types corresponding to each channel belonging to the same serving cell sub-combination. or a partially identical first DCI; or, the terminal equipment does not expect to receive a first DCI with different or partially identical first configuration information corresponding to channels belonging to the same serving cell sub-combination.
  • 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 serving cell; or the second configuration information is used to configure the BWP The frequency domain resource allocation type corresponding to the channel.
  • the above configuration information includes second configuration information corresponding to each partial bandwidth BWP of 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.
  • the above-mentioned second configuration information can be configured or indicated by the network device through a high-level parameter, specifically, it can be configured or indicated through a high-level parameter resourceAllocation, and the high-level parameter can be carried through high-level signaling (such as RRC signaling).
  • a high-level parameter specifically, it can be configured or indicated through a high-level parameter resourceAllocation
  • the high-level parameter can be carried through high-level signaling (such as RRC signaling).
  • the above-mentioned second configuration information may be information configuring the frequency domain resource allocation type of the BWP in the serving cell.
  • the above second configuration information may also be information configuring the frequency domain resource allocation type of the BWP channel.
  • the above second configuration information may be information that configures the frequency domain resource allocation type of the PDSCH of the BWP, or the second configuration information may be information that configures the frequency domain resource allocation type of the PUSCH of the BWP of the serving cell. .
  • the same frequency domain resource allocation type can be configured for the BWPs of N serving cells or the channels in the BWPs of N serving cells; or in other words, with all BWPs in the N serving cells, or with All channels in all BWPs in N serving cells are granular, and frequency domain resource allocation types are configured.
  • the frequency domain resource allocation type of at least one channel scheduled in a DCI can be unified, and the overhead of frequency domain resource allocation type indication can be reduced.
  • the frequency domain resource allocation types corresponding to each BWP of 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 types corresponding to the channels of each BWP of the N serving cells are the same; or,
  • the second configuration information corresponding to the channels of each BWP of the N serving cells is the same.
  • each BWP of the N serving cells may refer to all BWPs in the N serving cells.
  • the N serving cells are 2 serving cells, and each serving cell is configured with 4 BWPs, then the above "the frequency domain resource allocation type corresponding to each BWP of the N serving cells is the same" refers to these 2 serving cells.
  • a total of 8 BWPs in the serving cell all have the same frequency domain resource allocation type.
  • all BWPs of the N serving cells corresponding to the N channels scheduled by the first DCI can be configured with the same frequency domain resource allocation type. That is to say, when the network device schedules the channel of the terminal device through the first DCI, , the channels to which the BWPs of N serving cells corresponding to the same frequency domain resource allocation type can be scheduled through the first DCI.
  • all BWPs of the serving cell where the N channels scheduled by the first DCI are located can be configured with the same frequency domain resource allocation type. That is to say, when the network device schedules the channel of the terminal device through the first DCI, it can N channels in the BWP corresponding to the same frequency domain resource allocation type are scheduled through the first DCI.
  • the terminal device when it subsequently determines the resources of the channels scheduled by the network device through the first DCI, it can determine the same frequency domain resource allocation type for the N channels.
  • the terminal equipment does not expect that the frequency domain resource allocation types corresponding to each BWP of the N serving cells are different or partially the same; or,
  • the terminal equipment 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 equipment 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,
  • the terminal equipment 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.
  • the network device 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 serving cells is the same, or it can determine that the frequency domain resource allocation type/second configuration information of each BWP of the N serving cells is the same.
  • the frequency domain resource allocation types/second configuration information corresponding to the channels are the same.
  • the terminal device does not expect to receive the first DCI with different or partially identical frequency domain resource allocation types corresponding to the BWPs of the N scheduled serving cells; or the terminal device does not expect to receive the scheduled N first DCIs.
  • the second configuration information corresponding to each BWP of the serving cell is different or partially the same first DCI; or the terminal device does not expect to receive the frequency domain resource allocation types corresponding to the channels of each BWP of the N serving cells scheduled to be different or partially the same. the first DCI; or, the terminal device does not expect to receive the first DCI whose second configuration information corresponding to the channels of each BWP of the scheduled N serving cells is different or partially the same.
  • the same frequency domain resource allocation type can be configured for each BWP of each service cell of a single service cell sub-combination, or for each channel of each BWP of each service cell of a single service cell sub-combination through the second configuration information; in other words, the frequency domain resource allocation type is configured with all BWPs in each service cell of the service cell sub-combination, or with all channels in all BWPs in each service cell of the service cell sub-combination as the granularity. In this way, multiple channels with different frequency domain resource allocation types can be scheduled through one DCI, thereby achieving more flexible DCI scheduling.
  • the frequency domain resource allocation types corresponding to each BWP of each serving cell belonging to the same serving cell sub-combination are the same; the serving cell sub-combination includes some 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-combination is the same; or,
  • the frequency domain resource allocation types corresponding to the channels of each BWP of each serving cell belonging to the same serving cell sub-combination are the same; or,
  • the second configuration information corresponding to the channels of each BWP of each serving cell belonging to the same serving cell sub-combination is the same.
  • the N channels scheduled by the first DCI may belong to at least two serving cell sub-combinations, and all BWPs of the serving cells in each serving cell sub-combination are configured with the same frequency domain resource allocation type, or in other words, each serving cell sub-combination is configured with the same frequency domain resource allocation type.
  • the channels to which all BWPs of the serving cells in each serving cell subcombination belong are configured with the same frequency domain resource allocation type.
  • 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.
  • the terminal device When the terminal device subsequently determines the resources of the channel scheduled by the network device through the first DCI, it can determine the same frequency domain resource allocation type for the BWP channels of the serving cells among the N channels that belong to the same serving cell sub-combination; correspondingly , for the channels among the N channels that do not belong to the BWP of the serving cells of the same serving cell sub-combination, different frequency domain resource allocation types can be determined.
  • the network device 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 serving cell corresponding to each group of channels has the same frequency domain. Resource allocation type.
  • the terminal device does not expect that the frequency domain resource allocation types corresponding to the BWPs of the service cells belonging to the same service cell sub-combination are different or partially the same; the service cell sub-combination includes part of the N service cells; or,
  • the terminal equipment 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 equipment does not expect that the frequency domain resource allocation types corresponding to the channels of each BWP of each serving cell belonging to the same serving cell sub-combination are different or partially the same; or,
  • the terminal equipment does not expect that the second configuration information corresponding to the channels of each BWP of each serving cell belonging to the same serving cell sub-combination is different or partially the same.
  • the network device 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 serving cell belonging to the same serving cell sub-combination is the same, or it can determine that the frequency domain resource allocation type/second configuration information corresponding to each serving cell sub-combination belongs to the same.
  • the frequency domain resource allocation type/second configuration information corresponding to the channels of each BWP of each serving cell sub-combination is the same.
  • the terminal device does not expect to receive the first DCI with different or partially identical frequency domain resource allocation types corresponding to the BWPs of the serving cells belonging to the same serving cell sub-combination; or, the terminal device does not expect to receive the first DCI.
  • the second configuration information corresponding to the BWPs of each serving cell belonging to the same serving cell sub-combination is different or partially the same first DCI; or the terminal device does not expect to receive the BWPs of each serving cell belonging to the same serving cell sub-combination.
  • the frequency domain resource allocation types corresponding to the channels are different or partially the same first DCI; or, the terminal equipment does not expect to receive the second configuration information corresponding to the channels of each BWP of each serving cell belonging to the same serving cell sub-combination, which is different or partially the same.
  • the first DCI is different or partially the same.
  • the same frequency domain resource allocation type can be configured for the BWP combination or the channels in the BWP combination; or in other words, the frequency domain resource allocation type can be configured based on the BWP combination or all channels in the BWP combination as granularity. Configuration of resource allocation types. In this way, the frequency domain resource allocation type of at least one channel scheduled in a DCI can be unified, and the overhead of frequency domain resource allocation type indication can be reduced.
  • the frequency domain resource allocation types corresponding to the BWP combinations that can be scheduled by the first DCI are the same; or,
  • the second configuration information corresponding to the BWP combination that can be scheduled by the first DCI is the same; or,
  • the second configuration information corresponding to the channels of the BWP combination that can be scheduled by the first DCI is the same; or,
  • the second configuration information corresponding to the channels of the BWP combination that can be scheduled by the first DCI is the same.
  • 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.
  • the above BWP combination refers to a combination of multiple BWPs that can be scheduled by the same DCI.
  • the BWP combinations allowed to be scheduled by the first DCI can be configured with the same frequency domain resource allocation type. That is to say, the network device passes through the first DCI.
  • the channel in the BWP corresponding to the same frequency domain resource allocation type can be scheduled through the first DCI.
  • some BWPs may be configured with the same frequency domain resource allocation type.
  • the terminal equipment does not expect that among the N serving cells, 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; or,
  • the terminal equipment 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 equipment does not expect that among the N serving cells, 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 equipment does not expect that the second configuration information corresponding to the channels of the BWP combination that can be scheduled by the first DCI among the N serving cells is different or partially the same.
  • the above BWP combination in the N serving cells refers to a combination consisting of part of the BWPs in each BWP in the N serving cells.
  • the network device when performing resource scheduling through the first DCI, can determine that among the N serving cells, the frequency domain resource allocation types/second configuration information corresponding to the BWP combinations that can be scheduled by the first DCI are the same, or it can determine that the N serving cells have the same frequency domain resource allocation type/second configuration information. In each serving cell, 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.
  • the terminal device does not expect to receive first DCIs with different or partially identical frequency domain resource allocation types corresponding to BWP combinations that are allowed/can/can be scheduled by the first DCI among the scheduled N serving cells; Or, the terminal device does not expect to receive a first DCI with different or partially identical second configuration information corresponding to the BWP combinations that are allowed/can/can be scheduled by the first DCI among the N scheduled serving cells; or, the terminal equipment does not expect to receive a first DCI that is different or partially the same.
  • the second configuration information corresponding to the channel of the BWP combination that is allowed/can/can be scheduled by the first DCI is different or partially the same as the first DCI; or the terminal device does not expect to receive the scheduled Among the N serving cells, the second configuration information corresponding to the channels of the BWP combination that is allowed/can/can be scheduled by the first DCI is different or partially the same as the first DCI.
  • the above N serving cells can also be divided into at least one serving cell sub-combination, through the above-mentioned second configuration information, it is also possible to combine a single BWP in a single serving cell sub-combination, or to combine a single BWP in a single serving cell sub-combination.
  • Channels included in a single BWP combination are configured with the same frequency domain resource allocation type; or in other words, taking a single BWP combination in a serving cell subcombination, or taking all channels included in a single BWP combination in a serving cell subcombination as the granularity, Configure the frequency domain resource allocation type. In this way, channels with multiple different frequency domain resource allocation types can also be scheduled through one DCI, thereby achieving more flexible DCI scheduling.
  • 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 some of the N serving cells; or,
  • the second configuration information corresponding to the BWP combination that can be scheduled by the first DCI is the same; or,
  • the frequency domain resource allocation type corresponding to the channel of the BWP combination that can be scheduled by the first DCI is the same; or,
  • the second configuration information corresponding to the channel of the BWP combination that can be scheduled by the first DCI is the same.
  • the above-mentioned BWP combination in each serving cell belonging to the same serving cell sub-combination refers to a combination composed of some BWPs in each BWP of each serving cell belonging to the same serving cell sub-combination.
  • the N channels scheduled by the first DCI can belong to at least two serving cell sub-combinations, and the frequency domain resource allocation types of all BWP combinations of the serving cells in each serving cell sub-combination are the same, or in other words, each serving cell sub-combination has the same frequency domain resource allocation type.
  • the channels of all BWP combinations of the serving cells in the serving cell sub-combination are configured with the same frequency domain resource allocation type.
  • the same frequency domain resource allocation type can be determined for the channels of the BWP combination belonging to the same service cell sub-combination among the N channels.
  • the network device 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 serving cell sub-combination. .
  • the terminal equipment 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 N serving cells; or,
  • the terminal equipment 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 equipment 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 equipment does not expect that in each serving cell belonging to the same serving cell sub-combination, the second configuration information corresponding to the channel of the BWP combination that can be scheduled by the first DCI is different or partially the same.
  • the network device when it performs resource scheduling through the first DCI, it can determine that in each serving cell belonging to the same serving 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 may be determined that in each serving cell belonging to the same serving 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.
  • the terminal device does not expect to receive the second frequency domain resource allocation type corresponding to the BWP combination that is allowed/can/can be scheduled by the first DCI in the serving cells belonging to the same serving cell sub-combination, or is partially the same.
  • the terminal equipment does not expect to receive a first DCI that is different or partially the same as the second configuration information corresponding to the BWP combination that is allowed/can/can be scheduled by the first DCI in the serving cells belonging to the same serving cell sub-combination; Or, the terminal equipment does not expect to receive a first DCI with different or partially identical frequency domain resource allocation types corresponding to channels of BWP combinations that are allowed/can/can be scheduled by the first DCI in the serving cells belonging to the same serving cell sub-combination; Alternatively, the terminal device does not expect to receive a first DCI that has different or partially identical second configuration information corresponding to channels of BWP combinations that are allowed/can/can be scheduled by the first DCI in serving cells belonging to the same serving cell sub-combination.
  • the terminal device receives configuration information 1 sent by the network device.
  • the configuration information 1 is used to configure the frequency domain resource allocation type of N serving cells.
  • the configuration information 1 is a per cell or per BWP configuration.
  • the way for the terminal device to determine the frequency domain resource allocation type corresponding to N channels can be as follows:
  • Method 1 The terminal device does not expect that the N serving cells or the serving 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; the corresponding front description : The N serving cells or the serving cells of each subgroup are configured with the same frequency domain resource allocation type, or the corresponding configuration information 1 (corresponding to the above-mentioned first configuration information) is the same.
  • Method 2 The terminal device does not expect that all BWPs of the N serving cells or the serving 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; correspondingly Positive description: All BWPs of the N serving cells or the serving cells of each subgroup are configured with the same frequency domain resource allocation type, or the corresponding configuration information 1 (corresponding to the above-mentioned first configuration information) is the same.
  • Method 3 The terminal device does not expect that the N serving cells or the BWP (sub) groups corresponding to the serving cells of each subgroup (which can be scheduled together with multiple DCIs) are configured with different frequency domain resource allocation types, or in other words, corresponding The configuration information 1 (corresponding to the above-mentioned second configuration information) is different; the corresponding front description: N serving cells or the BWP (sub) group corresponding to the serving cells of each subgroup (which can be scheduled by 1 and multiple DCIs together) is configured
  • the frequency domain resource allocation types are the same, or the corresponding configuration information 1 (corresponding to the above-mentioned second configuration information) is the same.
  • corresponding frequency domain resource allocation types are different. If the configuration information 1 is all configured as Type0, or both are configured as Type1, or both are configured as dynamic switch, then the "corresponding The frequency domain resource allocation type is the same.”
  • 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 serving cell combinations or serving cell sub-combinations of the terminal device; the above-mentioned serving cell combinations It includes at least one serving cell that the first DCI can schedule together, and the serving cell sub-combination includes a part of the at least one serving cell that the first DCI can schedule.
  • the above-mentioned 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 to say, a serving cell combination may be a combination of N serving cells that can be scheduled simultaneously by the first DCI.
  • the configuration information of the above resource allocation type includes third configuration information corresponding to all serving cell combinations or serving cell subcombinations of the terminal device; the third configuration information is used to configure all serving cell combinations or serving cell subcombinations of the terminal device.
  • Frequency domain resource allocation type the above serving cell combination is a set of N serving cells that can be scheduled by the first DCI, and the serving cell subcombination is a set of parts of the N serving cells that can be scheduled by the first DCI.
  • the serving cell combination ⁇ cell 1+cell 2+cell 3 ⁇ can also be divided into two serving cell sub-combinations: ⁇ (cell 1+cell 2), (cell 3) ⁇ , where , cell 1+cell 2 is a serving cell sub-combination, and cell 3 independently constitutes another serving cell sub-combination.
  • the network device can configure the third configuration information for all serving cell combinations or serving cell sub-combinations in the terminal device. That is to say, a third configuration information can be configured for all serving cell combinations or serving cell sub-combinations of the terminal device. Configuration information. At this time, a third configuration information can configure the frequency domain resource allocation types of all serving cell combinations or serving cell sub-combinations in the terminal device.
  • 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; a PUCCH group is a group of serving cells .
  • PUCCH Physical Uplink Control Channel
  • 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 serving cell combination or serving cell subcombination; the above serving cell combination includes the first DCI At least one serving cell that can be scheduled together, and the serving cell sub-combination includes a part of at least one serving cell that can be scheduled by the first DCI.
  • the configuration information includes fourth configuration information corresponding to each serving cell combination or serving cell subcombination of the terminal device; the fourth configuration information is used to configure the serving cell combination or serving cell subcombination corresponding to the fourth configuration information.
  • Frequency domain resource allocation type is used to configure the serving cell combination or serving cell subcombination corresponding to the fourth configuration information.
  • the network device may configure the fourth configuration information for the service cell combination or service cell sub-combination in the terminal device, that is, for each service cell combination or service cell sub-combination of the terminal device, one fourth configuration information may be configured. At this time, one fourth configuration information may configure the frequency domain resource allocation type of one service cell combination or service cell sub-combination of the terminal device.
  • 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 serving cell combination or the serving cell sub-combination; the above-mentioned serving cell combination It includes at least one serving cell that the first DCI can schedule together, and the serving cell sub-combination includes a part of the at least one serving cell that the first DCI can schedule.
  • the configuration information of the resource allocation type includes the fifth configuration information corresponding to each serving cell combination or each BWP combination in the serving cell subcombination of the terminal device; the fifth configuration information is used to configure the configuration information corresponding to the fifth configuration information.
  • Frequency domain resource allocation type of BWP combination is a set of N serving cells scheduled by the first DCI, and the serving cell subcombination is a set of parts of the N serving cells scheduled by the first DCI.
  • the network device can configure the third configuration information for the BWP combination in the terminal device. That is to say, for each BWP group in each serving cell combination or serving cell sub-combination of the terminal device, a third configuration information can be configured. Configuration information. At this time, a third configuration information may configure the frequency domain resource allocation type of a BWP group in a serving cell combination or serving cell sub-combination of the terminal device.
  • the terminal device receives the configuration information 2 sent by the network device.
  • the configuration information 2 is used to configure a frequency domain resource allocation type dedicated to one modulation and multiple modulation.
  • N serving cells can be regarded as A combination of serving cells that can be scheduled by the first DCI
  • M subgroups are regarded as M subcombinations of serving cells that can be scheduled by the first DCI.
  • Configuration information 2 (corresponding to the above-mentioned 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 per-UE, Or configured per-PUCCH group (for each PUCCH group) or per-cell group (for each cell group);
  • Configuration information 2 (corresponding to the fourth configuration information mentioned above) is applicable to/corresponds to a single serving cell combination corresponding to the first DCI, or a single serving cell sub-combination; meaning that configuration information 2 is per-serving cell combination/per- Configured by serving cell sub-combination;
  • Configuration information 2 (corresponding to the fifth configuration information mentioned above) 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 subcombination; meaning that configuration information 2 is per -BWP group configured.
  • UE User Equipment
  • cell group PUCCH group
  • serving cell combination serving cell subcombination
  • Network equipment can configure up to 2 cell groups for terminal equipment, such as the master cell group (Master Cell Group, MCG) and/or the secondary cell group (Secondary Cell Group, SCG);
  • MCG Master Cell Group
  • SCG Secondary Cell Group
  • For each cell group it can contain 1 or 2 PUCCH groups;
  • each cell group or each PUCCH group it can contain one or more serving cell combinations, and the cells in each serving cell combination can be scheduled simultaneously by the first DCI;
  • one or more serving cell sub-combinations may be included.
  • the technical effects of the above solutions one and two include: limiting the N channels scheduled by the first DCI, or the channels in a subgroup corresponding to the same frequency domain resource allocation type. This can save DCI overhead on the one hand, and on the other hand when N When channels or channels in a subgroup share the FDRA indication field, the complexity of the scheduling algorithm can be minimized.
  • Option 1 can reuse the existing frequency domain resource allocation type configuration mechanism to the greatest extent, saving additional signaling overhead and standardization work; while Option 2 is more flexible in scheduling and configuration.
  • the frequency domain resource allocation type of the first channel is a first type.
  • the first type includes 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 N channels;
  • the first type is indicated by the 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.
  • the terminal device may directly determine that the resource allocation type of the first channel is type based on the configuration content corresponding to the first channel in the configuration information of the resource allocation type. 0 or type 1; that is, the resource allocation type of the first channel is explicitly indicated by the configuration information of the above resource allocation type.
  • the configuration information of the resource allocation type configures the first channel to be dynamically switched.
  • the terminal device can configure the first channel according to the first DCI.
  • the first indication field determines that the frequency domain resource allocation type corresponding to the first channel is type 0 or type 1. That is to say, the resource allocation type of the first channel is indirectly indicated by the configuration information of the resource allocation type.
  • the first indication field in the first DCI may be a part of the FDRA field; or, the first indication field may be a dedicated indication field outside the FDRA field.
  • the dedicated indication field is used for Indicates the frequency domain resource allocation type of one or more channels scheduled by a DCI.
  • the frequency domain resource allocation type of the channel corresponding to the N serving cells or the serving 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 the channels corresponding to the N serving cells or the serving cells in each subcombination.
  • the frequency domain resource allocation type is indicated by DCI.
  • the first indication field is 0, corresponding to Type-0, and the first indication field is 1, corresponding to Type-1.
  • the first indication field can be part of the FDRA field, or a dedicated indication field.
  • Embodiment 1 (corresponding to Method 2 in Solution 1 above):
  • the network device configures a cell group for the terminal device, such as MCG.
  • the MCG contains 1 PUCCH group.
  • the MCG contains 4 serving cells, cell 1 to cell 4.
  • Each cell contains 2 BWP, BWP 1 and BWP2.
  • Network devices configure co-scheduled cell combinations for terminal devices through high-level signaling configuration or protocol predefined methods.
  • Multiple DCIs can be scheduled together, including: 1) cell 1+cell 2; 2) cell 3 +cell 4;
  • the protocol stipulates that the bitmap form in DCI is used to indicate the cells that can be scheduled with multiple DCIs at the same time. For example, 4 cells correspond to 4 bits. In the case where the agreement does not specify Under 1-scheduled DCI, any 1/2/3/4 cells of 4 cells can be scheduled.
  • the protocol can also stipulate which cells can be scheduled together, such as the previous one: 1) cell 1+cell 2; 2) cell 3+cell 4.
  • 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.
  • 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 configured per-BWP, the terminal device does not expect cell 1, BWP1, cell 2, BWP1, cell 1, BWP2, cell 2. , BWP 2, 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, the corresponding frequency domain resource allocation types are different .
  • Embodiment 2 (corresponding to the method 3 in the above-mentioned solution 1):
  • the configuration method of the network device is the same as that of 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, and BWP2 of cell 1 can only be scheduled together with BWP2 of cell 2, and the same applies to cells 3/4.
  • 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 configured per-BWP, the terminal device does not expect cell 1, BWP1, cell 2, BWP1, the corresponding frequency domain resource allocation type. Different; the terminal equipment does not expect cell 1, BWP2, cell 2, BWP2, and the corresponding frequency domain resource allocation types are different. In the same way, the terminal device does not expect cell 3, BWP1, cell 4, BWP1, and the corresponding frequency domain resource allocation types are different. It does not expect cell 3, BWP2, cell 4, and BWP2, and the corresponding frequency domain resource allocation types are different.
  • Embodiment 3 (corresponding to the method 1 in the above-mentioned solution 2):
  • the terminal device receives configuration information 2.
  • the configuration information 2 is used to configure the frequency domain resource allocation types of all possible serving cell combinations corresponding to the first DCI. For example, if the configuration information 2 is configured as Type0, then regardless of whether the first DCI is used to schedule cell 1 +cell 2, or used to schedule cell3+cell4, regardless of which BWP of the above cells is scheduled, the frequency domain resource allocation type corresponding to the scheduled channel is Type0.
  • Embodiment 4 (corresponding to Method 2 in Option 2 above):
  • the terminal device receives configuration information 2, which is configured per-serving cell combination.
  • the configuration information 2 corresponding to cell 1+cell 2 is Type0
  • the configuration information 2 corresponding to cell 3+cell 4 is dynamic switch.
  • the frequency domain resource allocation type corresponding to the scheduled channel is Type0.
  • the frequency domain resource allocation type corresponding to the scheduled channel is the same, and Directed by DCI.
  • Embodiment 5 (corresponding to Method 3 in Option 2 above):
  • the terminal device receives configuration information 2, which is configured by the per-BWP group.
  • the configuration information 2 corresponding to cell 1 BWP1+cell 2 BWP1 is Type0; the configuration information 2 corresponding to cell 1 BWP2+cell 2 BWP2 is Type1; cell 3 BWP1+cell 4
  • the configuration information 2 corresponding to BWP1 is dynamic switch; the configuration information 2 corresponding to cell 3 BWP2+cell 4 BWP2 is dynamic switch.
  • 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 Type0.
  • the domain resource allocation type 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 channel is the same and is indicated by the DCI.
  • the terminal device determines the resource allocation type through the received configuration information, or through the configuration information and the received DCI.
  • the frequency domain resource allocation type corresponding to N channels improves the determination scheme of the frequency domain resource allocation type when scheduling one or multiple channels through a single DCI, and improves the efficiency of resource scheduling.
  • the above solution 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 devices with the same frequency domain through one DCI.
  • Frequency domain resource allocation type channels do not require separate indication for each channel. Therefore, whether the shared indication domain or independent indication domain is used, DCI overhead can be reduced and the scheduling algorithm on the network side can be simplified to a certain extent.
  • FIG. 6 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 the frequency domain resource allocation type has the function of being executed by the terminal device in implementing the method shown in FIG. 3 or FIG. 5 .
  • the device may include:
  • the receiving module 601 is used to receive configuration information of 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 serving cells; N Greater than or equal to 1, and N is an integer.
  • the above-mentioned apparatus further includes a determination module, configured to determine the frequency domain resource allocation type of the N channels according to the configuration information of the above-mentioned resource allocation type.
  • 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.
  • the frequency domain resource allocation types corresponding to each of the N serving cells are the same; or,
  • the first configuration information corresponding to each of the N serving cells is the same; or,
  • the frequency domain resource allocation types corresponding to each of the N channels are the same; or,
  • the first configuration information corresponding to each of the N channels is the same.
  • the frequency domain resource allocation types corresponding to each serving cell belonging to the same serving cell sub-combination are the same; the serving cell sub-combination includes some of the N serving cells; or,
  • the first configuration information corresponding to each serving cell belonging to the same serving cell sub-combination is the same; or,
  • the frequency domain resource allocation types corresponding to each channel 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-group is the same.
  • the terminal equipment does not expect that the frequency domain resource allocation types corresponding to each of 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 of the N serving cells is different or partially the same; or,
  • the terminal equipment does not expect that the frequency domain resource allocation types corresponding to each of 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.
  • the terminal equipment 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 some of the N serving cells; or ,
  • the terminal equipment does not expect that the first configuration information corresponding to 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 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.
  • 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.
  • the frequency domain resource allocation types corresponding to each BWP 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 types corresponding to the channels of each BWP of the N serving cells are the same; or,
  • the second configuration information corresponding to the channels of each BWP in the N serving cells is the same.
  • the frequency domain resource allocation types corresponding to each BWP of each serving cell belonging to the same serving cell sub-combination are the same; the serving cell sub-combination includes some 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-combination is the same; or,
  • the frequency domain resource allocation types corresponding to the channels of each BWP of each serving cell belonging to the same serving cell sub-combination are the same; or,
  • the second configuration information corresponding to the channels of each BWP of each serving cell belonging to the same serving cell sub-combination is the same.
  • the terminal equipment 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,
  • the terminal equipment 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 equipment 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,
  • the terminal device does not expect that the second configuration information corresponding to the channels of the respective BWPs of the N serving cells is different or partially the same.
  • the terminal equipment does not expect that the frequency domain resource allocation types corresponding to each BWP of each serving cell belonging to the same serving cell sub-combination are different or partially the same; the serving cell sub-combination includes N serving cells. part; or,
  • the terminal equipment 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 equipment does not expect that the frequency domain resource allocation types corresponding to the channels of each BWP of each serving cell belonging to the same serving cell sub-combination are different or partially the same; or,
  • the terminal equipment does not expect that the second configuration information corresponding to the channels of each BWP of each serving cell belonging to the same serving cell sub-combination is different or partially the same.
  • the frequency domain resource allocation types corresponding to the BWP combinations that can be scheduled by the first DCI are the same; or,
  • the second configuration information corresponding to the BWP combination that can be scheduled by the first DCI is the same; or,
  • the second configuration information corresponding to the channels of the BWP combination that can be scheduled by the first DCI is the same; or,
  • the second configuration information corresponding to the channels of the BWP combination that can be scheduled by the first DCI is the same.
  • 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 N serving cells. part; or,
  • the second configuration information corresponding to the BWP combination that can be scheduled by the first DCI is the same; or,
  • the frequency domain resource allocation type corresponding to the channel of the BWP combination that can be scheduled by the first DCI is the same; or,
  • the second configuration information corresponding to the channels of the BWP combination that can be scheduled by the first DCI is the same.
  • the terminal equipment does not expect that among the N serving cells, 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; or,
  • the terminal equipment does not expect that the second configuration information corresponding to the BWP combination that can be scheduled by the first DCI among the N serving cells is different or partially the same; or,
  • the terminal equipment does not expect that the second configuration information corresponding to the channels of the BWP combination that can be scheduled by the first DCI among the N serving cells is different or partially the same; or,
  • the terminal equipment does not expect that the second configuration information corresponding to the channels of the BWP combination that can be scheduled by the first DCI among the N serving cells is different or partially the same.
  • the terminal equipment 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 cells The sub-combination includes part of the N serving cells; or,
  • the terminal equipment 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,
  • the terminal equipment 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 equipment 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 each serving cell belonging to the same serving cell sub-combination is different or partially the same.
  • the configuration information of the resource allocation type includes third configuration information
  • the third configuration information is used to configure frequency domain resource allocation types of all serving cell combinations or serving cell sub-combinations of the terminal device;
  • the above-mentioned serving cell combinations include at least one serving cell that can be jointly scheduled by the first DCI, serving The cell sub-combination includes a portion of at least one serving cell that the first DCI can schedule.
  • the 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; the PUCCH group is a group of serving cells.
  • 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 serving cell combination or the serving cell sub-combination; the above-mentioned serving cell combination includes at least one serving cell that can be co-scheduled by the first DCI, and the serving cell sub-combination includes the first Part of at least one serving cell that the DCI can schedule.
  • 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 serving cell combination or serving cell sub-combination;
  • the above-mentioned serving cell combination includes at least one serving cell that can be jointly scheduled by the first DCI, and the serving cell sub-combination
  • the combination includes a portion of at least one serving cell that the first DCI can schedule.
  • 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;
  • the first type is indicated by the 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.
  • FIG. 7 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 the frequency domain resource allocation type has the function of being executed by the network device in implementing the method shown in FIG. 4 or FIG. 5 .
  • the device may include:
  • the sending module 701 is used to send 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 serving cells; N Greater than or equal to 1, and N is an integer.
  • the apparatus further includes: a determining module configured to determine configuration information of the resource allocation type of the terminal device.
  • 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.
  • the first configuration information is used to configure the frequency domain resource allocation type of the channel corresponding to the serving cell.
  • the frequency domain resource allocation types corresponding to each of the N serving cells are the same; or,
  • the first configuration information corresponding to each of the N serving cells is the same; or,
  • the frequency domain resource allocation types corresponding to each of the N channels are the same; or,
  • the first configuration information corresponding to each of the N channels is the same.
  • the frequency domain resource allocation types corresponding to each serving cell belonging to the same serving cell sub-combination are the same; the serving cell sub-combination includes some of the N serving cells; or,
  • the first configuration information corresponding to each serving cell belonging to the same serving cell sub-combination is the same; or,
  • the frequency domain resource allocation types corresponding to each channel 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.
  • 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.
  • the frequency domain resource allocation types corresponding to each BWP 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 types corresponding to the channels of each BWP of the N serving cells are the same; or,
  • the second configuration information corresponding to the channels of each BWP in the N serving cells is the same.
  • the frequency domain resource allocation types corresponding to each BWP of each serving cell belonging to the same serving cell sub-combination are the same; the serving cell sub-combination includes some 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 types corresponding to the channels of the BWPs of the service cells belonging to the same service cell sub-group are the same; or,
  • the second configuration information corresponding to the channels of each BWP of each serving cell belonging to the same serving cell sub-combination is the same.
  • the frequency domain resource allocation types corresponding to the BWP combinations that can be scheduled by the first DCI are the same; or,
  • the second configuration information corresponding to the BWP combination that can be scheduled by the first DCI is the same; or,
  • the second configuration information corresponding to the channels of the BWP combination that can be scheduled by the first DCI is the same; or,
  • the second configuration information corresponding to the channels of the BWP combination that can be scheduled by the first DCI is the same.
  • 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 N serving cells. part; or,
  • the second configuration information corresponding to the BWP combination that can be scheduled by the first DCI is the same; or,
  • the frequency domain resource allocation type corresponding to the channel of the BWP combination that can be scheduled by the first DCI is the same; or,
  • the second configuration information corresponding to the channel of the BWP combination that can be scheduled by the first DCI is the same.
  • the configuration information of the resource allocation type includes third configuration information
  • 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.
  • the 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; the PUCCH group is a group of serving cells.
  • 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 serving cell combination or the serving cell sub-combination; the above-mentioned serving cell combination includes at least one serving cell that can be jointly scheduled by the first DCI, and the serving cell sub-combination includes the first Part of at least one serving cell that the DCI can schedule.
  • 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 serving cell combination or serving cell sub-combination;
  • the above-mentioned serving cell combination includes at least one serving cell that can be jointly scheduled by the first DCI, and the serving cell sub-combination
  • the combination includes a portion of at least one serving cell that the first DCI can schedule.
  • 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;
  • the first type is indicated by the 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.
  • the device provided in the above embodiment implements its functions, only the division of the above functional modules is used as an example. In practical applications, the above functions can be allocated to different functional modules according to actual needs. That is, the content structure of the device is divided into different functional modules to complete all or part of the functions described above.
  • FIG. 8 shows a schematic structural diagram of a communication device 800 provided by an 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.
  • 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.
  • the receiver 802 and the transmitter 803 can be implemented as a communication component, and the communication component can be a communication chip.
  • This communication chip can also be called a transceiver.
  • Memory 804 is connected to processor 801 through bus 805.
  • the memory 804 can be used to store a computer program, and the processor 801 is used to execute the computer program to implement various steps in the above method embodiments.
  • memory 804 may be implemented by any type of volatile or non-volatile storage device, or combination thereof, including but not limited to: magnetic or optical disks, electrically erasable programmable Read-only memory, erasable programmable read-only memory, static ready-access memory, read-only memory, magnetic memory, flash memory, programmable read-only memory.
  • the processor executes the computer program, so that the terminal device implements the method shown in either Figure 3 or Figure 5, and the terminal device the various steps performed.
  • the above-mentioned transceiver (which may correspond to the receiving module 601 in Figure 6) is used to receive configuration information of the resource allocation type; wherein 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 serving cells; N is greater than or equal to 1, and N is an integer.
  • the above-mentioned processor (which may correspond to the determination module involved in the embodiment shown in FIG. 6) is used to determine the frequency domain resource allocation type of the N channels according to the configuration information of the resource allocation type.
  • the processor executes the computer program, so that the network device implements the method shown in either of the above-mentioned Figure 4 or Figure 5, Various steps performed by network devices.
  • the above-mentioned transceiver (which may correspond to the sending module 701 in Figure 7 above) is used to send configuration information of the resource allocation type to the terminal device.
  • the above-mentioned processor (which may correspond to the determination module involved in the embodiment shown in FIG. 7) is used to determine the configuration information of the resource allocation type of the terminal device.
  • Embodiments of the present application also provide a computer-readable storage medium.
  • a computer program is stored in the storage medium.
  • the computer program is loaded and executed by a processor to implement the method shown in Figure 3, Figure 4 or Figure 5. , all or part of the steps performed by the terminal device or network device.
  • This application also provides a chip, which is used to run in a communication device, so that the communication device performs all or part of the methods shown in Figure 3, Figure 4 or Figure 5, which are performed by the terminal device or the network device. step.
  • the present application also provides a computer program product, the computer program product or computer program includes computer instructions, and the computer instructions 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 the processor executes the computer instructions, so that the communication device executes all or part of the steps executed by the terminal device or the network device in the method shown in Figure 3, Figure 4 or Figure 5 above.
  • 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.
  • Computer-readable media includes computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • Storage media can be any available media that can be accessed by a general purpose or special purpose computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Procédé et appareil de détermination de type d'attribution de ressources de domaine fréquentiel, et dispositif et support d'enregistrement, qui appartiennent au domaine technique des communications mobiles. Le procédé consiste à : recevoir, par un équipement terminal, des informations de configuration d'un type d'attribution de ressources (S301), les informations de configuration du type d'attribution de ressources étant utilisées pour déterminer des types d'attribution de ressources de domaine fréquentiel de N canaux, les N canaux étant planifiés au moyen de premières informations de commande de liaison descendante (DCI), et les N canaux correspondant à N cellules de desserte, N étant supérieur ou égal à 1, et N étant un nombre entier.
PCT/CN2022/121072 2022-09-23 2022-09-23 Procédé et appareil de détermination de type d'attribution de ressources de domaine fréquentiel, et dispositif et support d'enrgistrement WO2024060241A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/121072 WO2024060241A1 (fr) 2022-09-23 2022-09-23 Procédé et appareil de détermination de type d'attribution de ressources de domaine fréquentiel, et dispositif et support d'enrgistrement

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/121072 WO2024060241A1 (fr) 2022-09-23 2022-09-23 Procédé et appareil de détermination de type d'attribution de ressources de domaine fréquentiel, et dispositif et support d'enrgistrement

Publications (1)

Publication Number Publication Date
WO2024060241A1 true WO2024060241A1 (fr) 2024-03-28

Family

ID=90453774

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/121072 WO2024060241A1 (fr) 2022-09-23 2022-09-23 Procédé et appareil de détermination de type d'attribution de ressources de domaine fréquentiel, et dispositif et support d'enrgistrement

Country Status (1)

Country Link
WO (1) WO2024060241A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111757501A (zh) * 2019-03-29 2020-10-09 北京三星通信技术研究有限公司 用户设备、基站及数据传输的方法
CN111836378A (zh) * 2019-08-15 2020-10-27 维沃移动通信有限公司 一种频域资源分配方法、网络侧设备及终端
CN113630874A (zh) * 2020-05-08 2021-11-09 维沃移动通信有限公司 频域资源分配方法及设备
CN113630873A (zh) * 2020-05-08 2021-11-09 维沃移动通信有限公司 频域资源分配方法及设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111757501A (zh) * 2019-03-29 2020-10-09 北京三星通信技术研究有限公司 用户设备、基站及数据传输的方法
CN111836378A (zh) * 2019-08-15 2020-10-27 维沃移动通信有限公司 一种频域资源分配方法、网络侧设备及终端
CN113630874A (zh) * 2020-05-08 2021-11-09 维沃移动通信有限公司 频域资源分配方法及设备
CN113630873A (zh) * 2020-05-08 2021-11-09 维沃移动通信有限公司 频域资源分配方法及设备

Similar Documents

Publication Publication Date Title
US11425697B2 (en) Dynamic management of uplink control signaling resources in wireless network
US10631296B2 (en) Resource allocation method, apparatus, and wireless access system
CN108347778B (zh) 通信方法及装置
US20200068610A1 (en) Resource scheduling method, network device, and communications device
EP3917256B1 (fr) Procédé, dispositif et produit de programme informatique pour rapporter une capacité de prise en charge de multiples informations de commande de liaison descendante
WO2018192015A1 (fr) Procédé et dispositif de configuration d'une direction de transmission de ressources temps-fréquence
CN109831827B (zh) 数据传输方法、终端和基站
WO2020113996A1 (fr) Procédé de détermination d'autorisation configurée, terminal et dispositif côté réseau
CN110999147B (zh) 相等大小码块的传输块大小确定
US20230038936A1 (en) Control information transmission method
US20240030964A1 (en) Communication method and apparatus
CN112740813B (zh) 一种通信方法及装置
US20220312459A1 (en) Enhanced Configured Grants
WO2022206346A1 (fr) Procédé et appareil d'accès aléatoire
CN114071745A (zh) 一种无线接入的方法以及装置
US9491725B2 (en) User equipment and methods for device-to-device communication over an LTE air interface
CN114451017A (zh) 一种激活和释放非动态调度传输的方法及装置
WO2024060241A1 (fr) Procédé et appareil de détermination de type d'attribution de ressources de domaine fréquentiel, et dispositif et support d'enrgistrement
US20220304042A1 (en) Enhanced Configured Grants
US20220304013A1 (en) Super-slot based data transmission in wireless communication
WO2022077352A1 (fr) Technologies pour réception fiable de canal physique de données dans des communications sans fil
CN114826537A (zh) 一种通信方法及装置
CN111193581B (zh) 发送和接收物理下行控制信道的方法以及通信装置
WO2024011632A1 (fr) Procédé et appareil de configuration de ressources, dispositif et support de stockage
WO2024092673A1 (fr) Procédé et appareil de planification de canal de données, et dispositif et support de stockage

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22959244

Country of ref document: EP

Kind code of ref document: A1