Method and device in node for multi-cell scheduling in wireless communication

Abstract

The present application discloses a method and device in a node for multi-cell scheduling in wireless communication. A node first receives a first parameter list and a second parameter list, and then receives first DCI, wherein the first DCI is used for scheduling a first cell set, and the first cell set comprises a plurality of cells; a first field comprised in the first DCI indicates a given entry from a target parameter list; the target parameter list is one of the first parameter list and the second parameter list; the given entry comprises a configuration for each cell comprised in the first cell set; and whether the target parameter list is the first parameter list or the second parameter list depends on whether subcarrier spacings used by active BWPs respectively corresponding to all the cells comprised in the first cell set are the same. The present application enhances uplink and downlink transmission configuration under multi-cell scheduling, thereby improving performance.

Description

A method and apparatus for multi-cell scheduling in nodes used in wireless communication

[0001] This application claims priority to Chinese Patent Application No. 202411441805.X, filed on October 15, 2024, entitled "A Method and Apparatus for Multi-Cell Scheduling in a Node for Wireless Communication", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to signal transmission methods and apparatus in wireless communication systems, and more particularly to methods and apparatus for multi-cell scheduling. Background Technology

[0003] The application scenarios of future wireless communication systems are becoming increasingly diversified, and different application scenarios place different performance requirements on the system. In order to meet the different performance requirements of various application scenarios, the 3GPP (3rd Generation Partner Project) RAN (Radio Access Network) #105 plenary meeting decided to enhance multi-carrier technology in New Radio (NR) (or 5G) Phase 2. One important enhancement is to enable multiple cells that are simultaneously scheduled to support different SCS (Subcarrier Spacing) / carrier types.

[0004] In existing NR systems, Release 18 already supports multiple different carriers being scheduled by the same DCI (Downlink Control Information) to improve transmission bandwidth and efficiency. However, in Release 18, multiple co-scheduled cells need to maintain the same SCS (Search Channel Classification). The new WID (Work Item Description) "Multi-carrier Enhancement for NR Phase 2," agreed upon at RAN#105 for Release 19, builds upon Release 18 to achieve more flexible single-DCI multi-cell scheduling. Summary of the Invention

[0005] In multi-carrier communication processes, such as carrier aggregation (CA), the system supports cross-carrier scheduling. In networks supported by existing standards, such as Rel-18 and earlier versions of 5G NR, for multiple scheduled cells, it is necessary to ensure that the subcarrier spacing of multiple cells is the same. In the relevant discussions of Rel-19, the above-mentioned restriction that multiple cells need to have the same subcarrier spacing will not exist.

[0006] To address the problem of simultaneously scheduling multiple cells with different subcarrier spacings using the same PDCCH in NR multi-cell scheduling scenarios, this application discloses a solution. It should be noted that although this application is initially intended for multi-cell scheduling scenarios, it can also be applied to other non-multi-cell scheduling scenarios. Furthermore, adopting a unified design scheme for different scenarios (such as other non-multi-cell scheduling scenarios, including but not limited to capacity enhancement systems, short-range communication systems, unlicensed spectrum communication, IoT (Internet of Things), URLLC (Ultra-Reliable Low Latency Communication) networks, and vehicle-to-everything (V2X) networks) helps reduce hardware complexity and cost. Where there is no conflict, the embodiments and features in any node of this application can be applied to any other node. Where there is no conflict, the embodiments and features in the embodiments of this application can be arbitrarily combined with each other.

[0007] In particular, the interpretation of terms, nouns, functions, and variables in this application (unless otherwise specified) can be found in the definitions of the TS38 and TS37 series of 3GPP (3rd Generation Partnership Project) Technical Specifications (TS). Where necessary, reference can be made to TS38.211, TS38.212, TS38.213, TS38.214, TS38.215, TS38.300, TS38.304, TS38.305, TS38.321, TS38.331, TS37.355, and TS38.423 in the 3GPP technical specifications to aid in understanding this application.

[0008] As an example, the interpretation of terms in this application is based on the definitions in the 3GPP specification protocol TS38 series.

[0009] As an example, the interpretation of terms in this application is based on the definitions in the 3GPP specification protocol TS37 series.

[0010] As an example, the interpretation of the terms in this application is based on the definitions in the 3GPP specification protocol TS40 series.

[0011] As an example, the interpretation of terms in this application is based on the definitions in the 3GPP specification protocol TS39 series.

[0012] As an example, the interpretation of the terms used in this application is based on the definitions in 3GPP specification protocol Rel-17.

[0013] As an example, the interpretation of the terms used in this application is based on the definitions in 3GPP specification protocol Rel-18.

[0014] This application discloses a method for a first node used in multi-cell scheduling for wireless communication, comprising:

[0015] Receive the first parameter list and the second parameter list;

[0016] Receive the first DCI (Downlink Control Information), the first DCI schedules the first set of cells, the first set of cells includes multiple cells;

[0017] Wherein, the first field included in the first DCI indicates a given entry from the target parameter list, the target parameter list being one of the first parameter list or the second parameter list, the given entry including the configuration for each cell included in the first cell set; whether the target parameter list is the first parameter list or the second parameter list depends on whether the subcarrier spacing used by the active BWP (Bandwidth Part) corresponding to all cells included in the first cell set is the same.

[0018] As an example, the problem to be solved by this application includes: the interpretation of the corresponding domains in the DCI when multiple scheduled cells, i.e., cells in the first cell set, use different subcarrier intervals.

[0019] As an example, the features of this application include: when multiple scheduled cells share the first domain in a DCI, the interpretation of the first domain depends on whether the cells in the first cell set use the same subcarrier spacing; and thus, the interpretation of the first domain is different for the two scenarios of using the same subcarrier spacing and using different subcarrier spacing.

[0020] As an example, the features of this application include: for scenarios where cells in the first cell set use different subcarrier intervals, adding new higher-layer parameters, namely the second parameter list, to adapt to the scheduling requirements corresponding to different subcarrier intervals, thereby further increasing flexibility and improving the overall system performance.

[0021] As an example, the features of this application include: In the traditional Release-18 scenario of single DCI scheduling of multiple cells, a Type 1B DCI field is designed for different cells, that is, an index list is configured for all scheduled cells through RRC signaling, and an entry in an index list corresponds to an indication value of a DCI field, and an entry includes the configuration of all cells corresponding to the indication value of the DCI field; while this application adds a new index list for scenarios with different subcarrier spacings, so that, with the indication value of a DCI field unchanged, different configurations can be corresponding to whether the subcarriers of the scheduled cells are completely the same, thereby increasing flexibility and adaptability.

[0022] According to one aspect of this application, the above method is characterized in that both the first parameter list and the second parameter list include configurations for the first cell set.

[0023] As an example, the features of this application include: using the configuration method of Release-18 without increasing the signaling complexity too much.

[0024] According to one aspect of this application, the method is characterized in that, when the active BWPs corresponding to all cells included in the first cell set use the same subcarrier spacing, the target parameter list is the first parameter list; when the active BWPs corresponding to all cells included in the first cell set do not use the same subcarrier spacing, the target parameter list is the second parameter list.

[0025] As an example, the features of this application include: for the first set of cells to be scheduled, different parameter lists are designed for two scenarios, namely the first parameter list and the second parameter list, to adapt to the scheduling requirements corresponding to different subcarrier intervals, thereby further increasing flexibility and improving the overall system performance.

[0026] According to one aspect of this application, the method is characterized in that the first domain included in the first DCI is a TDRA domain, the first domain indicating the location of the time domain resources occupied by the channel in each cell included in the first cell set, and the target parameter list is an index list for the TDRA (Time domain Resource Assignment) domain.

[0027] As an example, the features of this application include: when the first domain indicates the time domain resources to be scheduled, the processing delay will also be different because the subcarrier intervals of the cells in the first set of cells to be scheduled are different; while in the traditional single DCI scheduling multi-cell scenario in Release-17, the subcarrier intervals of multiple cells are the same, and the above problem will not occur; therefore, a new list for TDRA needs to be designed to meet the different delay requirements caused by different cells using different subcarrier intervals.

[0028] According to one aspect of this application, the above method is characterized in that the first DCI is a downlink grant, the first field included in the first DCI is a rate matching indicator, the first field determines the rate matching of at least one downlink BWP in each cell included in the first cell set, and the target parameter list is a list of rate matches.

[0029] As an example, the features of this application include: when the first domain indicates rate matching, because the subcarrier intervals of the cells in the first set of scheduled cells are different, the corresponding rate matching will also be different; while in the traditional Release-17 single DCI scheduling multi-cell scenario, the subcarrier intervals of multiple cells are the same, and the above problem will not occur; therefore, a new timing list needs to be designed to meet the different delay requirements caused by different cells using different subcarrier intervals.

[0030] According to one aspect of this application, the above method is characterized in that the first DCI is a downlink grant, the first domain included in the first DCI is a ZP CSI-RS (Zero Power Channel State Information Reference Signal) trigger, the first domain is a set of ZP CSI-RS resources in at least one downlink BWP of the cells included in the first cell set, and the target parameter list is a list of ZP CSI-RS.

[0031] As an example, the features of this application include: when the first domain triggers ZP CSI-RS, because the subcarrier intervals of the cells in the first set of scheduled cells are different, the corresponding appropriate ZP CSI-RS configurations will also be different; while in the traditional single DCI scheduling multi-cell scenario in Release-17, the subcarrier intervals of multiple cells are the same, and the above problem will not occur; therefore, a new timing list needs to be designed to meet the different delay requirements caused by different cells using different subcarrier intervals.

[0032] According to one aspect of this application, the above method is characterized in that the first DCI is a downlink grant, the first field included in the first DCI is a TCI (Transmission Configuration Indication), the first field determines the TCI index of each cell included in the first cell set, and the target parameter list is a TCI list.

[0033] As an example, the features of this application include: when the first field indicates TCI, because the subcarrier spacings of the cells in the first set of cells being scheduled are different, the corresponding spatial transmission characteristics will also be different; while in the traditional Release-17 single DCI scheduling multi-cell scenario, the subcarrier spacings of multiple cells are the same, and the above-mentioned problem will not occur; therefore, a new timing list needs to be designed to meet the requirements of different cells using different frequency hopping parameters.

[0034] According to one aspect of this application, the above method is characterized in that the first field included in the first DCI is an SRS (Sounding Reference Signal) request, the first field determines the SRS request index of each cell included in the first cell set, and the target parameter list is an SRS request list.

[0035] According to one aspect of this application, the above method is characterized in that the first field included in the first DCI is an SRS offset indicator, the first field determines the SRS offset indicator index of each cell included in the first cell set, and the target parameter list is an SRS offset list.

[0036] As an example, the features of this application include: when the first field indicates SRS-related configuration, because the subcarrier intervals of the cells in the first set of scheduled cells are different, the transmission characteristics of the corresponding SRS and SRS resource (set) configurations will also be different; while in the traditional single DCI scheduling multi-cell scenario in Release-17, the subcarrier intervals of multiple cells are the same, and the above problem will not occur; therefore, a new timing list needs to be designed to meet the requirements of different cells using different frequency hopping parameters.

[0037] According to one aspect of this application, the above method is characterized by comprising:

[0038] The channel is received in at least one cell included in the first set of cells.

[0039] According to one aspect of this application, the above method is characterized by comprising:

[0040] Transmit the channel in at least one cell included in the first set of cells.

[0041] According to one aspect of this application, the method is characterized in that the first parameter list depends on the DCI format adopted by the first DCI, and the second parameter list depends on the DCI format adopted by the first DCI.

[0042] According to one aspect of this application, the above method is characterized in that the first node is a user equipment.

[0043] According to one aspect of this application, the above method is characterized in that the first node is a relay node.

[0044] According to one aspect of this application, the above method is characterized in that the first node is a terminal.

[0045] This application discloses a method for multi-cell scheduling in a second node used in wireless communication, comprising:

[0046] Send the first parameter list and the second parameter list;

[0047] Send the first DCI, the first DCI schedules a first set of cells, the first set of cells includes multiple cells;

[0048] Wherein, the first field included in the first DCI indicates a given entry from the target parameter list, the target parameter list being one of the first parameter list or the second parameter list, the given entry including the configuration for each cell included in the first cell set; whether the target parameter list is the first parameter list or the second parameter list depends on whether the subcarrier spacing used by the active BWPs corresponding to all cells included in the first cell set is the same.

[0049] According to one aspect of this application, the above method is characterized in that both the first parameter list and the second parameter list include configurations for the first cell set.

[0050] According to one aspect of this application, the method is characterized in that, when the active BWPs corresponding to all cells included in the first cell set use the same subcarrier spacing, the target parameter list is the first parameter list; when the active BWPs corresponding to all cells included in the first cell set do not use the same subcarrier spacing, the target parameter list is the second parameter list.

[0051] According to one aspect of this application, the method is characterized in that the first domain included in the first DCI is a TDRA domain, the first domain indicating the location of the time-domain resources occupied by the channel in each cell included in the first cell set, and the target parameter list is an index list for the TDRA domain.

[0052] According to one aspect of this application, the above method is characterized in that the first DCI is a downlink grant, the first field included in the first DCI is a rate matching indication, the first field determines the rate matching of at least one downlink BWP in each cell included in the first cell set, and the target parameter list is a list of rate matches.

[0053] According to one aspect of this application, the above method is characterized in that the first DCI is a downlink grant, the first domain included in the first DCI is a ZP CSI-RS trigger, the first domain is a ZP CSI-RS resource set in at least one downlink BWP of the cells included in the first cell set, and the target parameter list is a list of ZP CSI-RS.

[0054] According to one aspect of this application, the above method is characterized in that the first DCI is a downlink grant, the first field included in the first DCI is a TCI, the first field determines the TCI index of each cell included in the first cell set, and the target parameter list is a TCI list.

[0055] According to one aspect of this application, the above method is characterized in that the first field included in the first DCI is an SRS request, the first field determines the SRS request index of each cell included in the first cell set, and the target parameter list is an SRS request list.

[0056] According to one aspect of this application, the above method is characterized in that the first field included in the first DCI is an SRS offset indicator, the first field determines the SRS offset indicator index of each cell included in the first cell set, and the target parameter list is an SRS offset list.

[0057] According to one aspect of this application, the above method is characterized by comprising:

[0058] The channel is transmitted in each cell included in the first set of cells.

[0059] According to one aspect of this application, the above method is characterized by comprising:

[0060] Access channels are provided in each cell included in the first set of cells.

[0061] According to one aspect of this application, the method is characterized in that the first parameter list depends on the DCI format adopted by the first DCI, and the second parameter list depends on the DCI format adopted by the first DCI.

[0062] According to one aspect of this application, the method described above is characterized in that the second node is a base station.

[0063] According to one aspect of this application, the above method is characterized in that the second node is a TRP (Transmitter Receiver Point).

[0064] This application discloses a device for use as a first node in wireless communication, comprising:

[0065] The first receiver receives the first parameter list and the second parameter list;

[0066] The first receiver receives a first DCI, and the first DCI schedules a first cell set, which includes multiple cells.

[0067] Wherein, the first field included in the first DCI indicates a given entry from the target parameter list, the target parameter list being one of the first parameter list or the second parameter list, the given entry including the configuration for each cell included in the first cell set; whether the target parameter list is the first parameter list or the second parameter list depends on whether the subcarrier spacing used by the active BWPs corresponding to all cells included in the first cell set is the same.

[0068] This application discloses a device for a second node used in wireless communication, comprising:

[0069] The second transmitter sends the first parameter list and the second parameter list;

[0070] The second transmitter sends a first DCI, which schedules a first set of cells, which includes multiple cells.

[0071] Wherein, the first field included in the first DCI indicates a given entry from the target parameter list, the target parameter list being one of the first parameter list or the second parameter list, the given entry including the configuration for each cell included in the first cell set; whether the target parameter list is the first parameter list or the second parameter list depends on whether the subcarrier spacing used by the active BWPs corresponding to all cells included in the first cell set is the same.

[0072] As an example, compared with conventional solutions, this application has the following advantages, but is not limited to:

[0073] For scenarios where cells in the first cell set use different subcarrier intervals, new higher-layer parameters, namely the second parameter list, are added to adapt to the scheduling requirements corresponding to different subcarrier intervals, thereby further increasing flexibility and improving the overall system performance.

[0074] To ensure signaling compatibility, no new bits were added to the current DCI format, thus reducing signaling overhead and improving spectrum efficiency. Attached Figure Description

[0075] Other features, objects, and advantages of this application will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings:

[0076] Figure 1 illustrates a flowchart of the first node transmission according to an embodiment of this application;

[0077] Figure 2 shows a schematic diagram of a network architecture according to an embodiment of this application;

[0078] Figure 3 illustrates a schematic diagram of an embodiment of a wireless protocol architecture for the user plane and control plane according to an embodiment of this application;

[0079] Figure 4 shows a schematic diagram of a first communication device and a second communication device according to an embodiment of this application;

[0080] Figure 5 illustrates a flowchart of the transmission between a first node and a second node according to an embodiment of this application;

[0081] Figure 6 illustrates a flowchart of the first node receiving data according to an embodiment of this application;

[0082] Figure 7 illustrates a flowchart of the first node transmission according to an embodiment of this application;

[0083] Figure 8 shows a schematic diagram of a target parameter list according to an embodiment of this application;

[0084] Figure 9 shows a schematic diagram of a first cell set according to an embodiment of this application;

[0085] Figure 10 shows a structural block diagram of a processing apparatus for a first node according to an embodiment of the present application;

[0086] Figure 11 shows a structural block diagram of a processing apparatus for a second node according to an embodiment of the present application. Detailed Implementation

[0087] The technical solutions of this application will be further described in detail below with reference to the accompanying drawings. It should be noted that, unless otherwise specified, the embodiments and features in the embodiments of this application can be arbitrarily combined with each other. Considering performance, flexibility, complexity, overhead, and compatibility, those skilled in the art are motivated to flexibly combine the embodiments in different drawings without conflict, including but not limited to the embodiments in Figure 1 and the embodiments in Figures 5-9, the embodiments in Figure 5 and the embodiments in Figures 6-9, etc.

[0088] Example 1

[0089] Example 1 illustrates a flowchart of the first node transmission according to an embodiment of this application, as shown in Figure 1. In Figure 1, each block represents a step. In particular, the order of the steps in the blocks does not represent a specific temporal relationship between the steps.

[0090] In step 101, the first node receives a first parameter list and a second parameter list; in step 102, it receives a first DCI, which schedules a first cell set, the first cell set including multiple cells;

[0091] In Embodiment 1, the first field included in the first DCI indicates a given entry from the target parameter list, which is one of the first parameter list or the second parameter list, and the given entry includes the configuration for each cell included in the first cell set; whether the target parameter list is the first parameter list or the second parameter list depends on whether the subcarrier spacing used by the active BWPs corresponding to all cells included in the first cell set is the same.

[0092] As one example, the first parameter list includes higher-layer signaling.

[0093] As an example, the first parameter list includes higher-level parameters.

[0094] As an example, the first parameter list includes one or more RRC IEs (Information Element(s)).

[0095] As an example, the first parameter list includes one or more fields in an RRC IE.

[0096] As an example, the first parameter list is indicated by ServingCellConfig IE.

[0097] As an example, the first parameter list is indicated by mc-DCI-SetOfCellsToAddModList.

[0098] As an example, the first parameter list is indicated by mc-DCI-SetOfCellsToAddModList-r18.

[0099] As an example, the first parameter list is indicated by mc-DCI-SetOfCellsToAddModList-r19.

[0100] As an example, the first parameter list is indicated by MC-DCI-SetOfCells.

[0101] As an example, the first parameter list is indicated by MC-DCI-SetOfCells-r18.

[0102] As an example, the first parameter list is indicated by MC-DCI-SetOfCells-r19.

[0103] As an example, the parameters included in the first parameter list are arranged in ascending order.

[0104] As a sub-implementation of this embodiment, the ascending order corresponds to the serving cell index ascending order, or the BWP-ID ascending order, or both ascending order.

[0105] As one example, the second parameter list includes higher-layer signaling.

[0106] As one example, the second parameter list includes higher-level parameters.

[0107] As an example, the second parameter list includes one or more RRC IEs.

[0108] As an example, the second parameter list includes one or more fields in an RRC IE.

[0109] As an example, the second parameter list is indicated by the ServingCellConfig IE.

[0110] As an example, the second parameter list is indicated by mc-DCI-SetOfCellsToAddModList.

[0111] As an example, the second parameter list is indicated by mc-DCI-SetOfCellsToAddModList-r18.

[0112] As an example, the second parameter list is indicated by mc-DCI-SetOfCellsToAddModList-r19.

[0113] As an example, the second parameter list is indicated by MC-DCI-SetOfCells.

[0114] As an example, the second parameter list is indicated by MC-DCI-SetOfCells-r18.

[0115] As an example, the second parameter list is indicated by MC-DCI-SetOfCells-r19.

[0116] As an example, the parameters included in the second parameter list are arranged in ascending order.

[0117] As a sub-implementation of this embodiment, the ascending order corresponds to the serving cell index ascending order, or the BWP-ID ascending order, or both ascending order.

[0118] As an example, the first parameter list and the second parameter list are transmitted via an RRC IE.

[0119] As an example, the first parameter list and the second parameter list are transmitted through a field in an RRC IE.

[0120] As an example, the DCI format of the first DCI is format 1_3.

[0121] As an example, the DCI format of the first DCI is format 0_3.

[0122] As an example, the first DCI is used to schedule the transmission of PDSCH in at least one cell in the first cell set.

[0123] As an example, the first DCI is used to schedule the transmission of PUSCH in at least one cell in the first cell set.

[0124] As an example, the first DCI is used to schedule the transmission of PDSCH in each cell of the first cell set.

[0125] As an example, the first DCI is used to schedule the transmission of PUSCH in each cell of the first cell set.

[0126] As an example, any cell in the first cell set belongs to the cell indicated by scheduledCellListDCI-1-3-r18.

[0127] As an example, any cell in the first cell set belongs to the cell indicated by scheduledCellListDCI-1-3-r19.

[0128] As an example, any cell in the first cell set belongs to the cell indicated by scheduledCellListDCI-0-3-r18.

[0129] As an example, any cell in the first cell set belongs to the cell indicated by scheduledCellListDCI-0-3-r19.

[0130] As an example, any cell in the first cell set belongs to the cell indicated by scheduledCellComboListDCI-1-3-r18.

[0131] As an example, any cell in the first cell set belongs to the cell indicated by scheduledCellComboListDCI-1-3-r19.

[0132] As an example, any cell in the first cell set belongs to the cell indicated by scheduledCellComboListDCI-0-3-r18.

[0133] As an example, any cell in the first cell set belongs to the cell indicated by scheduledCellComboListDCI-0-3-r19.

[0134] As an example, the first cell set corresponds to the set of cells indicated by ScheduledCellCombo-r18.

[0135] As an example, the first DCI is an uplink grant, and the active BWP is an uplink BWP.

[0136] As an example, the first DCI is a downlink license, and the active BWP is a downlink BWP.

[0137] As an example, the DCI format of the first DCI is format 0_3, and the active BWP is an uplink BWP.

[0138] As an example, the DCI format of the first DCI is format 1_3, and the active BWP is a downlink BWP.

[0139] As an example, the first DCI schedules the plurality of cells included in the first cell set.

[0140] As a sub-implementation of this embodiment, the first DCI schedules a target wireless signal, which includes multiple sub-signals, and the multiple sub-signals are respectively transmitted by the first node in the multiple cells.

[0141] As a sub-example of this embodiment, the first DCI schedules the target wireless signal, and the physical layer channel occupied by the target wireless signal includes PUSCH (Physical Uplink Shared Channel).

[0142] As a sub-example of this embodiment, the first DCI schedules the target wireless signal, and the transmission channel occupied by the target wireless signal includes UL-SCH (UpLink-Shared Channel).

[0143] As a sub-implementation of this embodiment, the first DCI schedules the target radio signal, and the plurality of sub-signals are respectively transmitted in a plurality of active UL (Uplink) BWPs in the plurality of cells.

[0144] As a sub-implementation of this embodiment, the plurality of sub-signals correspond to a plurality of transmission blocks respectively.

[0145] As a sub-implementation of this embodiment, the plurality of sub-signals correspond to a plurality of bit blocks respectively.

[0146] As a sub-implementation of this embodiment, the first DCI schedules a target wireless signal, which includes multiple sub-signals, and the multiple sub-signals are received by the first node in the multiple cells respectively.

[0147] As a sub-example of this embodiment, the first DCI schedules the target radio signal, and the physical layer channel occupied by the target radio signal includes PDSCH (Physical Downlink Shared Channel).

[0148] As a sub-example of this embodiment, the first DCI schedules the target wireless signal, and the transmission channel occupied by the target wireless signal includes DL-SCH (Downlink-Shared Channel).

[0149] As a sub-example of this embodiment, the first DCI schedules the target radio signal, and the plurality of sub-signals are received in a plurality of active DL (Downlink) BWPs in the plurality of cells respectively.

[0150] As one embodiment, the first DCI schedules multiple channels, which are transmitted in the multiple cells respectively.

[0151] As one embodiment, the first DCI schedules multiple channels, which are transmitted in multiple active BWPs in the multiple cells respectively.

[0152] As one example, the plurality of cells are multiple serving cells.

[0153] As an example, the multiple cells each correspond to multiple ServCellIndex.

[0154] As an example, the multiple cells each correspond to multiple servCellIds.

[0155] As an example, the multiple cells each correspond to multiple scheduledCellIds.

[0156] As an example, the plurality of cells correspond to a plurality of CIFs (Carrier Indicator Fields).

[0157] As an example, the plurality of cells correspond to a plurality of PhysCellIds.

[0158] As one example, the plurality of cells are each a plurality of CCs (Component Carriers).

[0159] As one example, the plurality of cells are each a plurality of carriers.

[0160] Example 2

[0161] Example 2 illustrates a schematic diagram of a network architecture according to an embodiment of this application, as shown in Figure 2.

[0162] Figure 2 illustrates network architecture 200. Network architecture 200 is the network architecture for LTE (Long-Term Evolution), LTE-A (Long-Term Evolution Advanced), 5G systems, 5G-Advanced, and future 6G systems. The network architecture for LTE, LTE-A, 5G systems, 5G-Advanced, and future 6G systems is referred to as EPS (Evolved Packet System). The 5G NR or LTE network architecture may be referred to as 5GS (5G System) / EPS or some other suitable terminology; the 6G network architecture may be referred to as 6GS (6G System) / EPS or some other suitable terminology. Network architecture 200 may include one or more UEs 201, RAN (Next Generation Radio Access Network) 202, core network 210, HSS (Home Subscriber Server) / UDM (Unified Data Management) 220, and Internet services 230. Network architecture 200 can interconnect with other access networks, but these entities / interfaces are not shown for simplicity. As shown in Figure 2, network architecture 200 provides packet-switched services; however, those skilled in the art will readily understand that the various concepts presented throughout this application can be extended to networks providing circuit-switched services. RAN 202 includes node B 203 and other nodes 204. Node 203 provides user and control plane protocol termination toward UE 201. Node 203 can be connected to other nodes 204 via an Xn interface (e.g., backhaul). Node 203 may also be referred to as a base station, base transceiver station, wireless base station, wireless transceiver, transceiver function, Basic Service Set (BSS), Extended Service Set (ESS), TRP (Transmitter Receiver Point), or some other suitable term. Node 203 provides UE 201 with an access point to core network 210; core network 210 is 5GC (5G Core Network) / EPC (Evolved Packet Core), or core network 210 is 6GC.Examples of UE 201 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, GPS devices, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, drones, aircraft, narrowband physical network devices, machine-type communication devices, land vehicles, automobiles, wearable devices, or any other similar functional devices. Those skilled in the art may also refer to UE 201 as a mobile station, subscriber station, mobile unit, subscriber unit, radio unit, remote unit, mobile device, radio communication device, remote device, mobile subscriber station, access terminal, mobile terminal, radio terminal, remote terminal, handheld device, user agent, mobile client, client, or any other suitable term. Node 203 is connected to core network 210 via an S1 / NG interface. The core network 210 includes the MME (Mobility Management Entity) / AMF (Authentication Management Field) / SMF (Session Management Function) 211, other MMEs / AMFs / SMFs 214, the S-GW (Service Gateway) / UPF (User Plane Function) 212, and the P-GW (Packet Data Network Gateway) / UPF 213. The MME / AMF / SMF 211 is the control node that handles signaling between the UE 201 and the 5G-CN / EPC 210. Generally, the MME / AMF / SMF 211 provides bearer and connection management. All user IP (Internet Protocol) packets are transmitted through the S-GW / UPF 212, which is itself connected to the P-GW / UPF 213. The P-GW provides UE IP address allocation and other functions. The P-GW / UPF 213 connects to Internet service 230. Internet service 230 includes carrier-compliant Internet protocol services, specifically including the Internet, intranet, IMS (IP Multimedia Subsystem), and packet switching services.

[0163] As an example, the first node in this application includes the UE 201.

[0164] As an example, the second node in this application includes the node 203.

[0165] As an example, node 203 is a macrocell base station.

[0166] As an example, node 203 is a microcell base station.

[0167] As an example, node 203 is a pico cell base station.

[0168] As an example, node 203 is a femtocell.

[0169] As an example, node 203 is a base station device that supports large latency differences.

[0170] As an example, node 203 is a flight platform device.

[0171] As one example, node 203 is a satellite device.

[0172] As one embodiment, the node 203 is a test device (e.g., a transceiver device simulating part of the functions of a base station, a signaling tester).

[0173] As an example, the UE 201 includes a mobile phone.

[0174] As an example, the UE 201 includes a terminal.

[0175] As an example, the UE 201 is a vehicle including a car.

[0176] As an example, the wireless link from the UE 201 to the node 203 is an uplink, which is used to perform uplink transmissions.

[0177] As an example, the radio link from node 203 to UE 201 is a downlink, which is used to perform downlink transmissions.

[0178] As an example, the wireless link between the node 203 and the UE 201 includes a cellular link.

[0179] As an example, the node 203 and the UE 201 are connected via the Uu air interface.

[0180] As an example, the sender of the first DCI includes the gNB 203.

[0181] As an example, the recipient of the first DCI includes the UE 201.

[0182] As an example, the sender of the channel in each cell includes the gNB 203.

[0183] As an example, the receiver of the channel in each cell includes the UE 201.

[0184] As an example, the receiver of the channel in each cell includes the gNB 203.

[0185] As an example, the sender of the channel in each cell includes the UE 201.

[0186] As an example, the UE 201 supports a 5G system.

[0187] As one example, the node 203 supports a 5G system.

[0188] As an example, the UE 201 supports at least a 6G system.

[0189] As an example, the node 203 supports at least a 6G system.

[0190] As an example, the UE 201 supports at least single DCI multi-cell scheduling.

[0191] As an example, the node 203 supports at least single DCI multi-cell scheduling.

[0192] As an example, the UE 201 supports at least single DCI multi-cell scheduling, and the subcarrier spacing used by the multi-carrier is different.

[0193] As an example, the node 203 supports at least single DCI multi-cell scheduling, and the subcarrier spacing used by the multi-carrier is different.

[0194] Example 3

[0195] Example 3 illustrates a schematic diagram of an embodiment of a wireless protocol architecture for the user plane and control plane according to an embodiment of this application, as shown in Figure 3.

[0196] Figure 3 is a schematic diagram illustrating an embodiment of the wireless protocol architecture for the user plane 350 and the control plane 300. Figure 3 shows the wireless protocol architecture for the control plane 300 between a first communication node device (UE or RSU in V2X, onboard equipment or onboard communication module) and a second node device (gNB, RSU in UE or V2X, onboard equipment or onboard communication module), or between two UEs, using three layers: Layer 1 (L1), Layer 2 (L2), and Layer 3 (L3). L1 is the lowest layer and implements various PHY (Physical layer) signal processing functions. L1 will be referred to herein as PHY 301. L2 305 is above PHY 301 and is responsible for the link between the first node device and the second node device, or between two UEs, through PHY 301. L2 305 includes a MAC (Medium Access Control) sublayer 302, an RLC (Radio Link Control) sublayer 303, and a PDCP (Packet Data Convergence Protocol) sublayer 304, which terminate at the second node device. The PDCP sublayer 304 provides multiplexing between different radio bearers and logical channels. It also provides security through encrypted data packets and supports cross-cell mobility between the second communication node devices and the first communication node device. The RLC sublayer 303 provides upper-layer packet segmentation and reassembly, retransmission of lost packets, and packet reordering to compensate for out-of-order reception due to HARQ (Hybrid Automatic Repeat reQuest). The MAC sublayer 302 provides multiplexing between logical and transport channels. It is also responsible for allocating various radio resources (e.g., resource blocks) within a cell between the first communication node devices. The MAC sublayer 302 is also responsible for HARQ operations. The RRC (Radio Resource Control) sublayer 306 in L3 of the control plane 300 is responsible for obtaining radio resources (i.e., radio bearers) and using RRC signaling between the second communication node device and the first communication node device to configure the lower layer.The wireless protocol architecture of user plane 350 includes Layer 1 (L1) and Layer 2 (L2). The wireless protocol architecture for the first and second communication node devices in user plane 350 is largely the same as the corresponding layers and sublayers in control plane 300 for Physical Layer 351, PDCP sublayer 354 in L2 355, RLC sublayer 353 in L2 355, and MAC sublayer 352 in L2 355. However, PDCP sublayer 354 also provides header compression for upper-layer packets to reduce wireless transmission overhead. L2 355 in user plane 350 also includes SDAP (Service Data Adaptation Protocol) sublayer 356. SDAP sublayer 356 is responsible for mapping between QoS (Quality of Service) streams and Data Radio Bearers (DRBs) to support service diversity. Although not illustrated, the first communication node device may have several upper layers above L2 355, including a network layer (e.g., IP (Internet Protocol) layer) terminating at the P-GW on the network side and an application layer terminating at the other end of the connection (e.g., remote UE, server, etc.).

[0197] As an example, the wireless protocol architecture in Figure 3 is applicable to the first node in this application.

[0198] As an example, the wireless protocol architecture in Figure 3 is applicable to the second node in this application.

[0199] As an example, in this application, the first DCI is generated in the PHY 301 or the PHY 351.

[0200] As an example, in this application, the second DCI is generated in the PHY 301 or the PHY 351.

[0201] As an example, the channel in each cell of this application is generated in the RRC 306.

[0202] As an example, the channel in each cell in this application is generated by MAC 302 or MAC 352.

[0203] As an example, the higher layer mentioned in this application refers to the layer above the physical layer.

[0204] As an example, the first parameter list in this application is generated in RRC 306.

[0205] As an example, the second parameter list in this application is generated in RRC 306.

[0206] As an example, the higher layer described in this application includes the MAC layer.

[0207] As an example, the higher layer described in this application includes the RRC layer.

[0208] Example 4

[0209] Example 4 illustrates a schematic diagram of a first communication device and a second communication device according to an embodiment of this application, as shown in Figure 4. Figure 4 is a block diagram of a first communication device 410 and a second communication device 450 communicating with each other in an access network.

[0210] The first communication device 410 includes a controller / processor 475, a memory 476, a receiver processor 470, a transmitter processor 416, a multi-antenna receiver processor 472, a multi-antenna transmitter processor 471, a transmitter / receiver 418, and an antenna 420.

[0211] The second communication device 450 includes a controller / processor 459, a memory 460, a data source 467, a transmitting processor 468, a receiving processor 456, a multi-antenna transmitting processor 457, a multi-antenna receiving processor 458, a transmitter / receiver 454, and an antenna 452.

[0212] In the transmission from the first communication device 410 to the second communication device 450, at the first communication device 410, upper-layer data packets from the core network are provided to the controller / processor 475. The controller / processor 475 implements L2 functionality. In the DL, the controller / processor 475 provides header compression, encryption, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocation to the second communication device 450 based on various priority metrics. The controller / processor 475 is also responsible for HARQ operation, retransmission of lost packets, and signaling to the second communication device 450. The transmit processor 416 and the multi-antenna transmit processor 471 implement various signal processing functions for L1 (i.e., the physical layer). Transmit processor 416 performs encoding and interleaving to facilitate forward error correction (FEC) at the second communication device 450, and mapping of signal clusters based on various modulation schemes (e.g., Binary Phase Shift Keying (BPSK), Quadrature Phase Shift Keying (QPSK), M-PSK, and M-Quadrature Amplitude Modulation (M-QAM)). Multi-antenna transmit processor 471 performs digital spatial precoding on the encoded and modulated symbols, including codebook-based precoding and non-codebook-based precoding, and beamforming processing, generating one or more parallel streams. The transmit processor 416 then maps each parallel stream to a subcarrier, multiplexes the modulated symbols with a reference signal (e.g., a pilot) in the time and / or frequency domains, and then uses an inverse fast fourier transform (IFFT) to generate a physical channel carrying the time-domain multicarrier symbol stream. The multi-antenna transmit processor 471 then performs transmit analog precoding / beamforming operations on the time-domain multicarrier symbol stream. Each transmitter 418 converts the baseband multicarrier symbol stream provided by the multi-antenna transmit processor 471 into an RF stream, which is then provided to a different antenna 420.

[0213] In the transmission from the first communication device 410 to the second communication device 450, at the second communication device 450, each receiver 454 receives a signal through its corresponding antenna 452. Each receiver 454 recovers the information modulated onto the radio frequency carrier and converts the radio frequency stream into a baseband multicarrier symbol stream, which is then provided to the receiver processor 456. The receiver processor 456 and the multi-antenna receiver processor 458 implement various L1 signal processing functions. The multi-antenna receiver processor 458 performs receive analog precoding / beamforming operations on the baseband multicarrier symbol stream from the receiver 454. The receiver processor 456 uses a Fast Fourier Transform (FFT) to convert the baseband multicarrier symbol stream after the receive analog precoding / beamforming operations from the time domain to the frequency domain. In the frequency domain, the physical layer data signal and the reference signal are demultiplexed by the receiver processor 456, where the reference signal is used for channel estimation, and the data signal is recovered in the multi-antenna receiver processor 458 after multi-antenna detection to recover any parallel stream destined for the second communication device 450. Symbols on each parallel stream are demodulated and recovered in the receive processor 456, generating soft decisions. The receive processor 456 then decodes and deinterleaves the soft decisions to recover the upper-layer data and control signals transmitted by the first communication device 410 over the physical channel. The upper-layer data and control signals are then provided to the controller / processor 459. The controller / processor 459 implements L2 functionality. The controller / processor 459 may be associated with a memory 460 storing program code and data. The memory 460 may be referred to as computer-readable media. In the DL, the controller / processor 459 provides multiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transmission and logical channels to recover upper-layer packets from the core network. The upper-layer packets are then provided to all protocol layers above L2. Various control signals may also be provided to L3 for L3 processing. The controller / processor 459 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0214] In the transmission from the second communication device 450 to the first communication device 410, at the second communication device 450, a data source 467 is used to provide upper-layer data packets to the controller / processor 459. The data source 467 represents all protocol layers above L2. Similar to the transmission functions at the first communication device 410 described in the DL, the controller / processor 459 implements header compression, encryption, packet segmentation and reordering, and multiplexing between logical and transport channels based on the radio resource allocation of the first communication device 410, implementing L2 functions for the user plane and control plane. The controller / processor 459 is also responsible for HARQ operations, retransmission of lost packets, and signaling to the first communication device 410. Transmit processor 468 performs modulation mapping and channel coding processing, while multi-antenna transmit processor 457 performs digital multi-antenna spatial precoding, including codebook-based and non-codebook-based precoding, and beamforming processing. Subsequently, transmit processor 468 modulates the generated parallel stream into a multi-carrier / single-carrier symbol stream. After analog precoding / beamforming operations in multi-antenna transmit processor 457, the stream is provided to different antennas 452 via transmitter 454. Each transmitter 454 first converts the baseband symbol stream provided by multi-antenna transmit processor 457 into a radio frequency symbol stream before providing it to antenna 452.

[0215] In the transmission from the second communication device 450 to the first communication device 410, the function at the first communication device 410 is similar to the receiving function at the second communication device 450 described in the transmission from the first communication device 410 to the second communication device 450. Each receiver 418 receives radio frequency signals through its corresponding antenna 420, converts the received radio frequency signals into baseband signals, and provides the baseband signals to the multi-antenna receiving processor 472 and the receiving processor 470. The receiving processor 470 and the multi-antenna receiving processor 472 jointly implement the L1 function. The controller / processor 475 implements the L2 function. The controller / processor 475 may be associated with a memory 476 storing program code and data. The memory 476 may be referred to as computer-readable media. The controller / processor 475 provides multiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transmission and logical channels to recover upper-layer data packets from the second communication device 450. The upper-layer data packets from the controller / processor 475 may be provided to the core network. The controller / processor 475 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0216] As one embodiment, the second communication device 450 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used with the at least one processor. The second communication device 450 receives at least a first parameter list and a second parameter list; and receives a first DCI, the first DCI scheduling a first cell set, the first cell set including a plurality of cells; a first field included in the first DCI indicates a given entry from a target parameter list, the target parameter list being one of the first parameter list or the second parameter list, the given entry including configuration for each cell included in the first cell set; whether the target parameter list is the first parameter list or the second parameter list depends on whether the subcarrier spacing used by the active BWPs corresponding to all cells included in the first cell set is the same.

[0217] As one embodiment, the second communication device 450 includes: receiving a first parameter list and a second parameter list; and receiving a first DCI.

[0218] As one embodiment, the first communication device 410 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used with the at least one processor. The first communication device 410 transmits at least a first parameter list and a second parameter list; and transmits a first DCI, the first DCI scheduling a first cell set, the first cell set including a plurality of cells; a first field included in the first DCI indicates a given entry from a target parameter list, the target parameter list being one of the first parameter list or the second parameter list, the given entry including configuration for each cell included in the first cell set; whether the target parameter list is the first parameter list or the second parameter list depends on whether the subcarrier spacing used by the active BWPs corresponding to all cells included in the first cell set is the same.

[0219] As one embodiment, the first communication device 410 includes: a memory storing a computer-readable instruction program that produces actions when executed by at least one processor, the actions including: sending a first parameter list and a second parameter list; and sending a first DCI.

[0220] As an example, the first node in this application includes the second communication device 450.

[0221] As an example, the second node in this application includes the first communication device 410.

[0222] As an example, at least one of {the antenna 420, the transmitter 418, the transmitter processor 416, the multi-antenna transmitter processor 471, the controller / processor 475, and the memory 476} is used to transmit a first parameter list and a second parameter list; at least one of {the antenna 452, the receiver 454, the receiver processor 456, the multi-antenna receiver processor 458, the controller / processor 459, the memory 460, and the data source 467} is used to receive the first parameter list and the second parameter list.

[0223] As an example, at least one of {the antenna 420, the transmitter 418, the transmitter processor 416, the multi-antenna transmitter processor 471, the controller / processor 475, and the memory 476} is used to transmit the first DCI; at least one of {the antenna 452, the receiver 454, the receiver processor 456, the multi-antenna receiver processor 458, the controller / processor 459, the memory 460, and the data source 467} is used to receive the first DCI.

[0224] As an example, at least one of {the antenna 420, the transmitter 418, the transmission processor 416, the multi-antenna transmission processor 471, the controller / processor 475, and the memory 476} is used to receive the channel in each cell included in the first cell set; at least one of {the antenna 452, the receiver 454, the receiving processor 456, the multi-antenna receiving processor 458, the controller / processor 459, the memory 460, and the data source 467} is used to transmit the channel in at least one cell included in the first cell set.

[0225] As an example, at least one of {the antenna 452, the transmitter 454, the transmission processor 468, the multi-antenna transmission processor 457, the controller / processor 459, the memory 460, and the data source 467} is used to transmit the channel in each cell included in the first cell set; at least one of {the antenna 420, the receiver 418, the receiving processor 470, the multi-antenna receiving processor 472, the controller / processor 475, and the memory 476} is used to receive the channel in at least one cell included in the first cell set.

[0226] Example 5

[0227] Example 5 illustrates a flowchart of transmission between a first node and a second node according to an embodiment of this application, as shown in Figure 5. In Figure 5, the first node U1 and the second node N2 communicate via a wireless link. It should be noted that the order in this embodiment does not limit the signal transmission order or the order of implementation in this application.

[0228] For the first node U1, in step S510, the first parameter list and the second parameter list are received; in step S511, the first DCI is received.

[0229] For the second node N2, the first parameter list and the second parameter list are sent in step S520; the first DCI is sent in step S521.

[0230] In Embodiment 5, the first DCI schedules a first set of cells, which includes multiple cells; the first field included in the first DCI indicates a given entry from a target parameter list, which is either the first parameter list or the second parameter list, and the given entry includes the configuration for each cell included in the first set of cells; whether the target parameter list is the first parameter list or the second parameter list depends on whether the subcarrier spacing used by the active BWPs corresponding to all cells included in the first set of cells is the same.

[0231] As an example, the first node U1 is the first node in this application.

[0232] As an example, the second node N2 is the second node in this application.

[0233] As an example, the first node U1 is the terminal in this application.

[0234] As an example, the second node N2 is the base station in this application.

[0235] Typically, both the first parameter list and the second parameter list include configurations for the first set of cells.

[0236] As an example, the first parameter list includes M1 index configurations, and any one of the M1 index configurations includes K1 index indications. When the target parameter list is the first parameter list, the first field included in the first DCI indicates a given index configuration from the M1 index configurations. The given index configuration includes the configuration of each cell in the first cell set. M1 is a positive integer greater than 1, and K1 is a positive integer greater than 1.

[0237] As a sub-implementation of this embodiment, the value of M1 is fixed, or the value of M1 is predefined.

[0238] As a sub-implementation of this embodiment, the value of M1 depends on the number of bits occupied by the first field.

[0239] As a sub-example of this embodiment, the value of K1 depends on the number of cells included in the first cell set.

[0240] As a sub-example of this embodiment, the value of K1 depends on the maximum number of cells that the first cell set can include.

[0241] As a sub-example of this embodiment, the value of K1 is equal to the maximum number of BWPs configured for a set of cells for multi-cell scheduling.

[0242] As a sub-example of this embodiment, the value of K1 is equal to the maximum number of active BWPs configured for a set of cells for multi-cell scheduling.

[0243] As a sub-example of this embodiment, the configuration for each cell in the first cell set in the given index configuration is arranged in ascending order of the serving cell index, and the configuration of all BWPs for a cell is arranged in ascending order of BWP-Id.

[0244] As a sub-implementation of this embodiment, when the target parameter list is the first parameter list, the given entry is one of the M1 index configurations included in the first parameter list.

[0245] As an example, the second parameter list includes M1 index configurations, and any index configuration in the M1 index configurations includes K1 index indications. When the target parameter list is the second parameter list, the first field included in the first DCI indicates a given index configuration from the M1 index configurations. The given index configuration includes the configuration of each cell in the first cell set. M1 is a positive integer greater than 1, and K1 is a positive integer greater than 1.

[0246] As a sub-implementation of this embodiment, the value of M1 is fixed, or the value of M1 is predefined.

[0247] As a sub-implementation of this embodiment, the value of M1 depends on the number of bits occupied by the first field.

[0248] As a sub-example of this embodiment, the value of K1 depends on the number of cells included in the first cell set.

[0249] As a sub-example of this embodiment, the value of K1 depends on the maximum number of cells that the first cell set can include.

[0250] As a sub-example of this embodiment, the value of K1 is equal to the maximum number of BWPs configured for a set of cells for multi-cell scheduling.

[0251] As a sub-example of this embodiment, the value of K1 is equal to the maximum number of active BWPs configured for a set of cells for multi-cell scheduling.

[0252] As a sub-example of this embodiment, the configuration for each cell in the first cell set in the given index configuration is arranged in ascending order of the serving cell index, and the configuration of all BWPs for a cell is arranged in ascending order of BWP-Id.

[0253] As a sub-example of this embodiment, when the target parameter list is the second parameter list, the given entry is one of the M1 index configurations included in the second parameter list.

[0254] Typically, when the active BWPs corresponding to all cells in the first cell set use the same subcarrier spacing, the target parameter list is the first parameter list; when the active BWPs corresponding to all cells in the first cell set do not use the same subcarrier spacing, the target parameter list is the second parameter list.

[0255] As an example, all active BWPs corresponding to the cells included in the first cell set use the same subcarrier spacing, and the target parameter list is the first parameter list.

[0256] As an example, the active BWPs of all cells included in the first cell set do not use the same subcarrier spacing, and the target parameter list is the second parameter list.

[0257] As an example, the fact that the active BWPs corresponding to all the cells included in the first cell set do not all use the same subcarrier spacing means that at least two cells in the first cell set have two active BWPs that use different subcarrier spacings.

[0258] As an example, the fact that the active BWPs corresponding to all the cells included in the first cell set do not all use the same subcarrier spacing means that the active BWPs corresponding to any two cells in the first cell set use different subcarrier spacings.

[0259] Typically, the first domain included in the first DCI is the TDRA domain, which indicates the location of the time-domain resources occupied by the channel in each cell included in the first cell set, and the target parameter list is an index list for the TDRA domain.

[0260] As an example, the channel in each cell includes PDSCH.

[0261] As an example, the channel in each cell includes DL-SCH.

[0262] As an example, the channel in each cell includes PUSCH.

[0263] As an example, the channel in each cell includes UL-SCH.

[0264] As an example, the first DCI is a downlink authorization, and the target parameter list includes tdra-FieldIndexListDCI-1-3.

[0265] As an example, the first DCI is an uplink grant, and the target parameter list includes tdra-FieldIndexListDCI-0-3.

[0266] As an example, the name of the target parameter list includes tdra.

[0267] As an example, the name of the target parameter list includes FieldIndexList.

[0268] As an example, the first parameter list consists of RRC parameters for releases prior to R-19, and the second parameter list consists of RRC parameters for R-19 or later versions.

[0269] As an example, the first DCI is a downlink authorization, and the first parameter list is tdra-FieldIndexListDCI-1-3-r18.

[0270] As an example, the first DCI is a downlink authorization, and the second parameter list is tdra-FieldIndexListDCI-1-3-r19.

[0271] As an example, the first DCI is an uplink authorization, and the first parameter list is tdra-FieldIndexListDCI-0-3-r18.

[0272] As an example, the first DCI is an uplink grant, and the second parameter list is tdra-FieldIndexListDCI-0-3-r19.

[0273] As an example, the index configuration in this application includes TDRA-FieldIndexDCI-1-3-r18, and the index indication in this application includes DL-Allocations-1-r18.

[0274] As an example, the index configuration in this application includes TDRA-FieldIndexDCI-1-3-r19, and the index indication in this application includes DL-Allocations-1-r19.

[0275] As an example, the index configuration in this application includes TDRA-FieldIndexDCI-0-3-r18, and the index indication in this application includes UL-Allocations-1-r18.

[0276] As an example, the index configuration in this application includes TDRA-FieldIndexDCI-0-3-r19, and the index indication in this application includes UL-Allocations-1-r19.

[0277] Typically, the first DCI is a downlink grant, the first field included in the first DCI is a rate matching indication, the first field determines the rate matching of at least one downlink BWP in each cell included in the first cell set, and the target parameter list is a list of rate matches.

[0278] As an example, the target parameter list includes rateMatchListDCI-1-3.

[0279] As an example, the name of the target parameter list includes rateMatch.

[0280] As an example, the name of the target parameter list includes List.

[0281] As an example, the first parameter list consists of RRC parameters for releases prior to R-19, and the second parameter list consists of RRC parameters for R-19 or later versions.

[0282] As an example, the first parameter list is rateMatchListDCI-1-3-r18.

[0283] As an example, the second parameter list is rateMatchListDCI-1-3-r19.

[0284] As an example, the index configuration in this application includes RateMatchDCI-1-3-r18; the index indication in this application includes 0, 1 or 2 bits, and depends on higher-level parameters rateMatchPatternGroup1 and rateMatchPatternGroup2.

[0285] As an example, the index configuration in this application includes RateMatchDCI-1-3-r19; the index indication in this application includes 0, 1 or 2 bits, and depends on higher-level parameters rateMatchPatternGroup1 and rateMatchPatternGroup2.

[0286] Typically, the first DCI is a downlink grant, the first domain included in the first DCI is a ZP CSI-RS trigger, the first domain is a ZP CSI-RS resource set in at least one downlink BWP in the cells included in the first cell set, and the target parameter list is a list of ZP CSI-RS.

[0287] As an example, the first domain included in the first DCI is used to trigger the triggering of the ZP CSI-RS resource set in at least one downlink BWP of the cells included in the first cell set.

[0288] As an example, the target parameter list includes zp-CSI-RSListDCI-1-3.

[0289] As an example, the name of the target parameter list includes zp-CSI-RS.

[0290] As an example, the name of the target parameter list includes List.

[0291] As an example, the first parameter list consists of RRC parameters for releases prior to R-19, and the second parameter list consists of RRC parameters for R-19 or later versions.

[0292] As an example, the first parameter list is zp-CSI-RSListDCI-1-3-r18.

[0293] As an example, the second parameter list is zp-CSI-RSListDCI-1-3-r19.

[0294] As an example, the index configuration in this application includes ZP-CSI-DCI-1-3-r18; the index indicator in this application includes 0, 1, or 2 bits and depends on the number of aperiodic ZP-CSI-RS resource sets configured by the higher-level parameter aperiodicZP-CSI-RS-ResourceSetsToAddModList.

[0295] As an example, the index configuration in this application includes ZP-CSI-DCI-1-3-r19; the index indicator in this application includes 0, 1, or 2 bits and depends on the number of aperiodic ZP-CSI-RS resource sets configured by the higher-level parameter aperiodicZP-CSI-RS-ResourceSetsToAddModList.

[0296] Typically, the first DCI is a downlink grant, the first field included in the first DCI is a TCI, the first field determines the TCI index of each cell included in the first cell set, and the target parameter list is a TCI list.

[0297] As an example, the target parameter list includes tci-ListDCI-1-3.

[0298] As an example, the name of the target parameter list includes tci.

[0299] As an example, the name of the target parameter list includes List.

[0300] As an example, the first parameter list consists of RRC parameters for releases prior to R-19, and the second parameter list consists of RRC parameters for R-19 or later versions.

[0301] As an example, the first parameter list is tci-ListDCI-1-3-r18.

[0302] As an example, the second parameter list is tci-ListDCI-1-3-r19.

[0303] As an example, the index configuration in this application includes TCI-DCI-1-3-r18; the index indication in this application includes 3 bits.

[0304] As an example, the index configuration in this application includes TCI-DCI-1-3-r19; the index indication in this application includes 3 bits.

[0305] Typically, the first field included in the first DCI is an SRS request, which determines the SRS request index of each cell included in the first cell set, and the target parameter list is an SRS request list.

[0306] As an example, the first DCI is a downlink authorization, and the target parameter list includes srs-RequestListDCI-1-3.

[0307] As an example, the first DCI is an uplink authorization, and the target parameter list includes srs-RequestListDCI-0-3.

[0308] As an example, the name of the target parameter list includes srs-Request.

[0309] As an example, the name of the target parameter list includes List.

[0310] As an example, the first parameter list consists of RRC parameters for releases prior to R-19, and the second parameter list consists of RRC parameters for R-19 or later versions.

[0311] As an example, the first DCI is a downlink authorization, and the first parameter list is srs-RequestListDCI-1-3-r18.

[0312] As an example, the first DCI is an uplink authorization, and the first parameter list is srs-RequestListDCI-0-3-r18.

[0313] As an example, the first DCI is a downlink authorization, and the second parameter list is srs-RequestListDCI-1-3-r19.

[0314] As an example, the first DCI is an uplink authorization, and the second parameter list is srs-RequestListDCI-0-3-r19.

[0315] As an example, the index configuration in this application includes SRS-RequestCombo-r18; the index indication in this application includes 2 or 3 bits and depends on the configuration of the higher-level parameter supplementaryUplink.

[0316] As an example, the index configuration in this application includes SRS-RequestCombo-r19; the index indication in this application includes 2 or 3 bits and depends on the configuration of the higher-level parameter supplementaryUplink.

[0317] Typically, the first field included in the first DCI is an SRS offset indicator, which determines the SRS offset indicator index of each cell included in the first cell set, and the target parameter list is an SRS offset list.

[0318] As an example, the first DCI is a downlink grant, and the target parameter list includes srs-OffsetListDCI-1-3.

[0319] As an example, the first DCI is an uplink grant, and the target parameter list includes srs-OffsetListDCI-0-3.

[0320] As an example, the name of the target parameter list includes srs-Offset.

[0321] As an example, the name of the target parameter list includes List.

[0322] As an example, the first parameter list consists of RRC parameters for releases prior to R-19, and the second parameter list consists of RRC parameters for R-19 or later versions.

[0323] As an example, the first DCI is a downlink license, and the first parameter list is srs-OffsetListDCI-1-3-r18.

[0324] As an example, the first DCI is an uplink grant, and the first parameter list is srs-OffsetListDCI-0-3-r18.

[0325] As an example, the first DCI is a downlink grant, and the second parameter list is srs-OffsetListDCI-1-3-r19.

[0326] As an example, the first DCI is an uplink grant, and the second parameter list is srs-OffsetListDCI-0-3-r19.

[0327] As an example, the index configuration in this application includes SRS-OffsetCombo-r18; the index indication in this application includes 0, 1, 2 or 3 bits, and depends on the configuration of higher-level parameters AvailableSlotOffset and availableSlotOffsetList.

[0328] As an example, the index configuration in this application includes SRS-OffsetCombo-r19; the index indication in this application includes 0, 1, 2 or 3 bits, and depends on the configuration of higher-level parameters AvailableSlotOffset and availableSlotOffsetList.

[0329] As an example, the subcarrier spacing of a cell in this application refers to the subcarrier spacing used by the active DL BWP in a cell.

[0330] As an example, the subcarrier spacing of a cell in this application refers to the subcarrier spacing used by the active UL BWP in a cell.

[0331] As an example, one cell in this application corresponds to one carrier.

[0332] As an example, one cell in this application corresponds to one serving cell.

[0333] As an example, one cell in this application corresponds to one CC.

[0334] Example 6

[0335] Example 6 illustrates a flowchart of a first node receiving data according to an embodiment of this application, as shown in Figure 6. In Figure 6, the first node U3 and the second node N4 communicate via a wireless link. It should be noted that the order in this embodiment does not limit the signal transmission order or the order of implementation in this application.

[0336] For the first node U3, in step S530, the channel is received in each cell included in the first cell set.

[0337] For the second node N4, in step S540, the channel is transmitted in each cell included in the first cell set.

[0338] As an example, the first DCI schedules each of the channels in each cell included in the first cell set.

[0339] As an example, the first DCI indicates at least one of the time-domain resources, frequency-domain resources, MCS, and HARQ process number occupied by the channel in each cell included in the first cell set.

[0340] As an example, step S530 is located after step S511 in Example 5.

[0341] As an example, step S530 is not earlier than step S511 in Example 5.

[0342] As an example, step S540 is located after step S521 in Example 5.

[0343] As an example, step S540 is not earlier than step S521 in Example 5.

[0344] Example 7

[0345] Example 7 illustrates a flowchart of a first node transmission according to an embodiment of this application, as shown in Figure 7. In Figure 7, the first node U5 and the second node N6 communicate via a wireless link. It should be noted that the order in this embodiment does not limit the signal transmission order or the order of implementation in this application.

[0346] For the first node U5, in step S550, the channel is transmitted in each cell included in the first cell set.

[0347] For the second node N6, in step S560, the channel is received in each cell included in the first cell set.

[0348] As one embodiment, the first node transmits the channel in each cell included in the first cell set.

[0349] As an example, the first DCI schedules each of the channels in each cell included in the first cell set.

[0350] As an example, the first DCI indicates at least one of the time-domain resources, frequency-domain resources, MCS, and HARQ process number occupied by the channel in each cell included in the first cell set.

[0351] As an example, the first DCI indicates the SRI (SRS Resource Set Indicator) used by the channel in each cell included in the first cell set.

[0352] As an example, step S550 is located after step S511 in Example 5.

[0353] As an example, step S550 is not earlier than step S511 in Example 5.

[0354] As an example, step S560 is located after step S521 in Example 5.

[0355] As an example, step S560 is not earlier than step S521 in Example 5.

[0356] Example 8

[0357] Example 8 illustrates a schematic diagram of a target parameter list according to an embodiment of this application, as shown in Figure 8. In Figure 8, the target parameter list includes M1 candidate index configurations, corresponding to candidate index configuration #1 to candidate index configuration #M1 in the figure; any one of the M1 candidate index configurations includes K1 candidate index indicators, corresponding to candidate index indicator #1 to candidate index indicator #K1 in the figure; the K1 candidate index indicators correspond to K1 frequency bands; M1 and K1 are both positive integers greater than 1.

[0358] As an example, the first field indicates a given candidate index configuration from the M1 candidate index configurations, wherein the K1 candidate index indications included in the given candidate index configuration are respectively used to indicate the K1 frequency bands.

[0359] As an example, the target parameter list is the first parameter list, the M1 candidate index configurations are the M1 index configurations included in the first parameter list, and the K1 candidate index indications included in any candidate index configuration are the corresponding K1 index indications.

[0360] As an example, the target parameter list is the second parameter list, the M1 candidate index configurations are the M1 index configurations included in the second parameter list, and the K1 candidate index indications included in any candidate index configuration are the corresponding K1 index indications.

[0361] As an example, the given entry indicated by the first field included in the first DCI is one of the M1 candidate index configurations included in the target parameter list.

[0362] As an example, K1 is equal to the number of cells included in the first cell set, and the K1 frequency bands correspond to the K1 cells included in the first cell set.

[0363] As an example, K1 is equal to the number of DL BWPs included in the cells included in the first cell set, and the K1 frequency bands correspond to the K1 DL BWPs included in the cells included in the first cell set.

[0364] As an example, K1 is equal to the number of UL BWPs included in the cells included in the first cell set, and K1 frequency bands correspond to K1 UL BWPs included in the cells included in the first cell set.

[0365] As an example, K1 is equal to the maximum number of cells that the first cell set can include, and K1 frequency bands correspond to the maximum number of K1 cells that the first cell set can include.

[0366] As an example, K1 is equal to the number of DL BWPs that the cells included in the first cell set can include, and the K1 frequency bands correspond to the K1 DL BWPs that the cells included in the first cell set can include.

[0367] As an example, K1 is equal to the number of UL BWPs that the cells included in the first cell set can include, and the K1 frequency bands correspond to the K1 UL BWPs that the cells included in the first cell set can include.

[0368] Example 9

[0369] Example 9 illustrates a schematic diagram of a first cell set according to an embodiment of this application, as shown in Figure 9. In Figure 9, the first cell set includes K1 cells, and the first cell is one of the K1 cells, where K1 is a positive integer greater than 1.

[0370] As an example, the first cell is any one of the K1 cells.

[0371] As an example, K1 is a positive integer greater than 1.

[0372] As an example, the first DCI is used to indicate the K1 cells.

[0373] As an example, the first DCI is used to indicate the transmission of K1 PDSCHs in K1 cells included in the first cell set, wherein the K1 PDSCHs are transmitted in the K1 cells respectively.

[0374] As a sub-example of this embodiment, the K1 PDSCHs correspond to K1 TBs respectively.

[0375] As a sub-implementation of this embodiment, the K1 PDSCHs correspond to K1 HARQ process numbers respectively.

[0376] As an example, the first DCI is used to indicate the transmission of K1 sub-signals in K1 cells included in the first cell set, wherein the K1 sub-signals are transmitted in the K1 cells respectively.

[0377] As a sub-implementation of this embodiment, the K1 sub-signals correspond to 1 TB (Transport Block).

[0378] As a sub-implementation of this embodiment, the K1 sub-signals correspond to one HARQ process number.

[0379] As a sub-implementation of this embodiment, the K1 sub-signals correspond to 1 PDSCH.

[0380] Example 10

[0381] Example 10 illustrates a structural block diagram of a processing apparatus for a first node according to an embodiment of this application, as shown in Figure 10. In Figure 10, the processing apparatus 1000 in the first node includes a first receiver 1001 and a first transmitter 1002, wherein the first transmitter 1002 is optional.

[0382] In embodiment 10, the first receiver 1001 receives a first parameter list and a second parameter list; and the first receiver 1001 receives a first DCI, the first DCI scheduling a first cell set, the first cell set including multiple cells;

[0383] In embodiment 10, the first field included in the first DCI indicates a given entry from the target parameter list, which is one of the first parameter list or the second parameter list, and the given entry includes the configuration for each cell included in the first cell set; whether the target parameter list is the first parameter list or the second parameter list depends on whether the subcarrier spacing used by the active BWPs corresponding to all cells included in the first cell set is the same.

[0384] As an example, both the first parameter list and the second parameter list include configurations for the first cell set.

[0385] As an example, when the active BWPs corresponding to all cells in the first cell set use the same subcarrier spacing, the target parameter list is the first parameter list; when the active BWPs corresponding to all cells in the first cell set do not use the same subcarrier spacing, the target parameter list is the second parameter list.

[0386] As an example, the first domain included in the first DCI is the TDRA domain, which indicates the location of the time-domain resources occupied by the channel in each cell included in the first cell set, and the target parameter list is an index list for the TDRA domain.

[0387] As an example, the first DCI is a downlink grant, the first field included in the first DCI is a rate matching indication, the first field determines the rate matching of at least one downlink BWP in each cell included in the first cell set, and the target parameter list is a list of rate matches.

[0388] As an example, the first DCI is a downlink grant, the first domain included in the first DCI is a ZP CSI-RS trigger, the first domain is a ZP CSI-RS resource set in at least one downlink BWP of the cells included in the first cell set, and the target parameter list is a list of ZP CSI-RS.

[0389] As an example, the first DCI is a downlink grant, the first field included in the first DCI is a TCI, the first field determines the TCI index of each cell included in the first cell set, and the target parameter list is a TCI list.

[0390] As an example, the first field included in the first DCI is an SRS request, the first field determines the SRS request index of each cell included in the first cell set, and the target parameter list is an SRS request list.

[0391] As an example, the first field included in the first DCI is an SRS offset indicator, the first field determines the SRS offset indicator index of each cell included in the first cell set, and the target parameter list is an SRS offset list.

[0392] As one embodiment, the first receiver 1001 receives a channel in each cell included in the first cell set.

[0393] As one embodiment, the first transmitter 1002 transmits a channel in each cell included in the first cell set.

[0394] As an example, the first parameter list depends on the DCI format used by the first DCI, and the second parameter list depends on the DCI format used by the first DCI.

[0395] As one example, the first node is a user equipment.

[0396] As an example, the first node is a relay node device.

[0397] As an example, the first receiver 1001 includes at least one of the following in embodiment 4: the antenna 452, the receiver 454, the receiver processor 456, the multi-antenna receiver processor 458, the controller / processor 459, the memory 460, and the data source 467.

[0398] As an example, the first transmitter 1002 includes at least one of the following in embodiment 4: the antenna 452, the transmitter 454, the transmission processor 468, the multi-antenna transmission processor 457, the controller / processor 459, the memory 460, and the data source 467.

[0399] Example 11

[0400] Example 11 illustrates a structural block diagram of a processing apparatus for a second node according to an embodiment of this application, as shown in Figure 11. In Figure 11, the processing apparatus 1100 in the second node includes a second transmitter 1101 and a second receiver 1102, wherein the second receiver 1102 is optional.

[0401] In embodiment 11, the second transmitter 1101 sends a first parameter list and a second parameter list; and the second transmitter 1101 sends a first DCI, the first DCI scheduling a first cell set, the first cell set including multiple cells;

[0402] In embodiment 11, the first field included in the first DCI indicates a given entry from the target parameter list, which is one of the first parameter list or the second parameter list, and the given entry includes the configuration for each cell included in the first cell set; whether the target parameter list is the first parameter list or the second parameter list depends on whether the subcarrier spacing used by the active BWPs corresponding to all cells included in the first cell set is the same.

[0403] As an example, both the first parameter list and the second parameter list include configurations for the first cell set.

[0404] As an example, when the active BWPs corresponding to all cells in the first cell set use the same subcarrier spacing, the target parameter list is the first parameter list; when the active BWPs corresponding to all cells in the first cell set do not use the same subcarrier spacing, the target parameter list is the second parameter list.

[0405] As an example, the first domain included in the first DCI is the TDRA domain, which indicates the location of the time-domain resources occupied by the channel in each cell included in the first cell set, and the target parameter list is an index list for the TDRA domain.

[0406] As an example, the first DCI is a downlink grant, the first field included in the first DCI is a rate matching indication, the first field determines the rate matching of at least one downlink BWP in each cell included in the first cell set, and the target parameter list is a list of rate matches.

[0407] As an example, the first DCI is a downlink grant, the first domain included in the first DCI is a ZP CSI-RS trigger, the first domain is a ZP CSI-RS resource set in at least one downlink BWP of the cells included in the first cell set, and the target parameter list is a list of ZP CSI-RS.

[0408] As an example, the first DCI is a downlink grant, the first field included in the first DCI is a TCI, the first field determines the TCI index of each cell included in the first cell set, and the target parameter list is a TCI list.

[0409] As an example, the first field included in the first DCI is an SRS request, the first field determines the SRS request index of each cell included in the first cell set, and the target parameter list is an SRS request list.

[0410] As an example, the first field included in the first DCI is an SRS offset indicator, the first field determines the SRS offset indicator index of each cell included in the first cell set, and the target parameter list is an SRS offset list.

[0411] As one embodiment, the second transmitter 1101 transmits a channel in each cell included in the first cell set.

[0412] As one embodiment, the second receiver 1102 receives a channel in each of the cells included in the first cell set.

[0413] As an example, the first parameter list depends on the DCI format used by the first DCI, and the second parameter list depends on the DCI format used by the first DCI.

[0414] In one embodiment, the second node is a base station device.

[0415] In one embodiment, the second node is a user equipment.

[0416] As an example, the second transmitter 1101 includes at least one of the following in embodiment 4: the antenna 420, the transmitter 418, the transmission processor 416, the multi-antenna transmission processor 471, the controller / processor 475, and the memory 476.

[0417] As one embodiment, the second receiver 1102 includes at least one of the following in embodiment 4: the antenna 420, the receiver 418, the receiver processor 470, the multi-antenna receiver processor 472, the controller / processor 475, and the memory 476.

[0418] Typically, unless otherwise specified, the names of RRC IEs and the names of the fields included in RRC IEs in this application may be appended with suffixes such as -r16, -r17, -r18, -r19, or -r20. Those skilled in the art should understand that the addition of such suffixes will not affect the interpretation of RRC IEs and the interpretation of the fields included in RRC IEs in this application.

[0419] Those skilled in the art will understand that all or part of the steps in the above methods can be implemented by a program instructing related hardware, and the program can be stored in a computer-readable storage medium, such as a read-only memory, hard disk, or optical disk. Optionally, all or part of the steps in the above embodiments can also be implemented using one or more integrated circuits. Correspondingly, each module unit in the above embodiments can be implemented in hardware or in the form of software functional modules. This application is not limited to any specific combination of software and hardware. The user equipment, terminal, and UE in this application include, but are not limited to, drones, communication modules on drones, remote-controlled aircraft, aircraft, small aircraft, mobile phones, tablets, laptops, vehicle-mounted communication equipment, vehicles, RSUs, wireless sensors, internet cards, IoT terminals, RFID (Radio Frequency Identification) terminals, NB-IoT (Narrow Band Internet of Things) terminals, MTC (Machine Type Communication) terminals, eMTC (enhanced MTC) terminals, data cards, internet cards, vehicle-mounted communication equipment, low-cost mobile phones, low-cost tablets, and other wireless communication devices. The base station or system equipment in this application includes, but is not limited to, macrocell base stations, microcell base stations, small cell base stations, home base stations, relay base stations, eNB (evolved Node B), gNB, TRP, GNSS (Global Navigation Satellite System), relay satellites, satellite base stations, airborne base stations, RSUs, unmanned aerial vehicles, and test equipment, such as transceivers or signaling testers that simulate some functions of a base station, and other wireless communication equipment.

[0420] Those skilled in the art will understand that the present invention can be practiced in other specified forms without departing from its core or essential characteristics. Therefore, the embodiments disclosed herein should in any way be considered descriptive rather than restrictive. The scope of the invention is defined by the appended claims rather than the foregoing description, and all modifications within their equivalent meaning and scope are considered to be included therein.

Claims

1. A method of a terminal for multi-cell scheduling for wireless communication, the method comprising: include: Receive the first parameter list and the second parameter list; Receive a first DCI, the first DCI schedules a first set of cells, the first set of cells includes multiple cells; Wherein, the first field included in the first DCI indicates a given entry from the target parameter list, the target parameter list being one of the first parameter list or the second parameter list, the given entry including the configuration for each cell included in the first cell set; whether the target parameter list is the first parameter list or the second parameter list depends on whether the subcarrier spacing used by the active BWPs corresponding to all cells included in the first cell set is the same.

2. The method of claim 1, wherein, Both the first parameter list and the second parameter list include configurations for the first cell set.

3. The method according to claim 1 or 2, characterized in that, When all active BWPs corresponding to all cells in the first cell set use the same subcarrier spacing, the target parameter list is the first parameter list; when the active BWPs corresponding to all cells in the first cell set do not use the same subcarrier spacing, the target parameter list is the second parameter list.

4. The method according to any one of claims 1 to 3, characterized in that, The first domain included in the first DCI is the TDRA domain, which indicates the location of the time-domain resources occupied by the channel in each cell included in the first cell set, and the target parameter list is an index list for the TDRA domain.

5. The method according to any one of claims 1 to 3, characterized in that, The first DCI is a downlink grant, the first field included in the first DCI is a rate matching indication, the first field determines the rate matching of at least one downlink BWP in each cell included in the first cell set, and the target parameter list is a list of rate matches.

6. The method of any one of claims 1 to 3, wherein, The first DCI is a downlink grant, the first domain included in the first DCI is a ZP CSI-RS trigger, the first domain is a ZP CSI-RS resource set in at least one downlink BWP in the cells included in the first cell set, and the target parameter list is a list of ZP CSI-RS.

7. The method of any one of claims 1 to 3, wherein, The first DCI is a downlink grant, the first field included in the first DCI is a TCI, the first field determines the TCI index of each cell included in the first cell set, and the target parameter list is a TCI list.

8. The method of any one of claims 1 to 3, wherein, The first field included in the first DCI is the SRS request, the first field determines the SRS request index of each cell included in the first cell set, and the target parameter list is the SRS request list.

9. The method of any one of claims 1 to 3, wherein, The first field included in the first DCI is the SRS offset indicator, which determines the SRS offset indicator index of each cell included in the first cell set, and the target parameter list is the SRS offset list.

10. The method of any one of claims 1 to 9, wherein include: The channel is received in each cell included in the first set of cells.

11. The method according to any one of claims 1 to 9, characterized in that include: The channel is transmitted in each cell included in the first set of cells.

12. The method of any one of claims 1 to 11, wherein, The first parameter list depends on the DCI format used by the first DCI, and the second parameter list depends on the DCI format used by the first DCI.

13. A terminal, characterized in that, The terminal includes: one or more processors and memory; The memory is coupled to the one or more processors, the memory being used to store computer program code, the computer program code including computer instructions, the one or more processors invoking the computer instructions to cause the terminal to perform the method as described in any one of claims 1-12.

14. A method of multi-cell scheduling for a base station used for wireless communication, the method comprising: include: Send the first parameter list and the second parameter list; Send the first DCI, the first DCI schedules a first set of cells, the first set of cells includes multiple cells; Wherein, the first field included in the first DCI indicates a given entry from the target parameter list, the target parameter list being one of the first parameter list or the second parameter list, the given entry including the configuration for each cell included in the first cell set; whether the target parameter list is the first parameter list or the second parameter list depends on whether the subcarrier spacing used by the active BWPs corresponding to all cells included in the first cell set is the same.

15. The method of claim 14, wherein, Both the first parameter list and the second parameter list include configurations for the first cell set.

16. The method according to claim 14 or 15, characterized in that When all active BWPs corresponding to all cells in the first cell set use the same subcarrier spacing, the target parameter list is the first parameter list; when the active BWPs corresponding to all cells in the first cell set do not use the same subcarrier spacing, the target parameter list is the second parameter list.

17. The method of any one of claims 14-16, wherein, The first domain included in the first DCI is the TDRA domain, which indicates the location of the time-domain resources occupied by the channel in each cell included in the first cell set, and the target parameter list is an index list for the TDRA domain.

18. The method of any one of claims 14-16, wherein, The first DCI is a downlink grant, the first field included in the first DCI is a rate matching indication, the first field determines the rate matching of at least one downlink BWP in each cell included in the first cell set, and the target parameter list is a list of rate matches.

19. The method of any one of claims 14-16, wherein, The first DCI is a downlink grant, the first domain included in the first DCI is a ZP CSI-RS trigger, the first domain is a ZP CSI-RS resource set in at least one downlink BWP in the cells included in the first cell set, and the target parameter list is a list of ZP CSI-RS.

20. The method of any one of claims 14-16, wherein, The first DCI is a downlink grant, the first field included in the first DCI is a TCI, the first field determines the TCI index of each cell included in the first cell set, and the target parameter list is a TCI list.

21. The method of any one of claims 14-16, wherein, The first field included in the first DCI is the SRS request, the first field determines the SRS request index of each cell included in the first cell set, and the target parameter list is the SRS request list.

22. The method of any one of claims 14-16, wherein, The first field included in the first DCI is the SRS offset indicator, which determines the SRS offset indicator index of each cell included in the first cell set, and the target parameter list is the SRS offset list.

23. The method of any one of claims 14-22, wherein include: The channel is transmitted in each cell included in the first set of cells.

24. The method of any one of claims 14-22, wherein include: Access channels are provided in each cell included in the first set of cells.

25. The method of any one of claims 14-24, wherein, The first parameter list depends on the DCI format used by the first DCI, and the second parameter list depends on the DCI format used by the first DCI.

26. A base station, characterized in that, The base station includes: one or more processors and a memory; The memory is coupled to the one or more processors, the memory being used to store computer program code, the computer program code including computer instructions, the one or more processors invoking the computer instructions to cause the Internet of Things device to perform the method as described in any one of claims 14-25.

Images