Method and apparatus in node used for multi-cell scheduling of wireless communication

Abstract

The invention discloses a method and an apparatus in a node used for multi-cell scheduling of wireless communication. A node firstly receives a first information block and a second information block; then receiving a first DCI (Downlink Control Information), the first DCI scheduling a first cell set, the first cell set comprising a plurality of cells; the first DCI comprises a first domain, interpretation of the first domain included in the first DCI depends on a target information block, and the target information block is one of the first information block or the second information block; whether the target information block is the first information block or the second information block depends on whether subcarrier intervals adopted by active BWPs corresponding to all cells included in the first cell set are the same or not. According to the invention, uplink and downlink transmission configuration under multi-cell scheduling is enhanced, and the performance is improved.

Description

Technical Field

[0001] This application relates to a signal transmission method and apparatus in a wireless communication system, and particularly to a method and apparatus for multi-cell scheduling. Background Art

[0002] The application scenarios of future wireless communication systems are becoming more and more diversified, and different application scenarios put forward different performance requirements for the system. In order to meet the different performance requirements of various application scenarios, at the 105th plenary session of 3GPP (3rd Generation Partner Project), RAN (Radio Access Network), it was decided to enhance multi-carrier in the second phase of the new air interface technology (NR, New Radio) (or 5G). An important enhancement direction is that multiple cells scheduled simultaneously support different SCS (Subcarrier Spacing) / carrier types.

[0003] In the existing NR system, Release 18 already supports multiple different carriers being scheduled by the same DCI (Downlink Control Information) to improve the transmission bandwidth and transmission efficiency. However, in the Release 18 version, multiple co-scheduled cells need to ensure the same SCS. And the new WID (Work Item Description) "Multi-carrier Enhancement for NR Phase 2" for Release 19 agreed upon based on the RAN#105 plenary session is to achieve more flexible single DCI multi-cell scheduling on the basis of Release 18. Summary of the Invention

[0004] In the process of multi-carrier communication, such as in Carrier Aggregation (CA), the system supports cross-carrier scheduling. In networks supported by existing standards, such as 5G NR in Rel-18 and earlier versions, for multiple scheduled cells, it is necessary to ensure that the subcarrier spacings of multiple cells are the same. In the relevant discussions of Rel-19, the limitation that the above-mentioned multiple cells need the same subcarrier spacing will not exist, thereby improving the flexibility of the system.

[0005] In view of the problem that in the multi-cell scheduling scenario of NR, the same PDCCH schedules multiple cells with different subcarrier spacings simultaneously, this application discloses a solution. It should be noted that although the original intention of this application is for the multi-cell scheduling scenario, this application can also be applied to other non-multi-cell scheduling scenarios; further, adopting a unified design solution 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, vehicle-to-everything networks, etc.) helps to reduce hardware complexity and cost. Without conflict, the embodiments and features in any node of this application can be applied to any other node. Without conflict, the embodiments and features in the embodiments of this application can be combined with each other arbitrarily.

[0006] In particular, the explanations of the terms, nouns, functions, and variables in this application (if not otherwise specified) can refer to the definitions in TS38 series and TS37 series of the technical standards (Technical Specification, TS) of 3GPP (the 3rd Generation Partnership Project). If necessary, TS38.211, TS38.212, TS38.213, TS38.214, TS38.215, TS38.300, TS38.304, TS38.305, TS38.321, TS38.331, TS37.355, TS38.423 in the 3GPP technical standards can be referred to for assisting in the understanding of this application.

[0007] As an example, the explanations of the terms in this application refer to the definitions in the TS38 series of the 3GPP specification protocol.

[0008] As an example, the explanations of the terms in this application refer to the definitions in the TS37 series of the 3GPP specification protocol.

[0009] As an example, the explanations of the terms in this application refer to the definitions in the TS40 series of the 3GPP specification protocol.

[0010] As an example, the explanations of the terms in this application refer to the definitions in the TS39 series of the 3GPP specification protocol.

[0011] As an example, the interpretation of the terms in this application refers to the definitions in the 3GPP specification protocol Rel-17 version.

[0012] As an example, the interpretation of the terms in this application refers to the definitions in the 3GPP specification protocol Rel-18 version.

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

[0014] Receiving a first information block and a second information block;

[0015] The first receiver receives a first DCI (Downlink Control Information), and the first DCI schedules a first cell set, where the first cell set includes multiple cells;

[0016] Wherein, the first DCI includes a first field, and the interpretation of the first field included in the first DCI depends on a target information block, and the target information block is one of the first information block and the second information block; whether the target information block is the first information block or the second information block depends on whether the subcarrier intervals adopted by the active BWPs (BandWidth Parts) corresponding to all the cells included in the first cell set are the same.

[0017] As an example, the problems to be solved by this application include: when there is a scenario where the cells in the scheduled multiple cells, that is, the cells in the first cell set, adopt different subcarrier intervals, the problem of the interpretation of the fields in the corresponding DCI.

[0018] As an example, the features of this application include: when multiple scheduled cells share the first field in a DCI, the interpretation of the first field depends on whether the cells in the first cell set adopt the same subcarrier interval; furthermore, for the two scenarios of adopting the same subcarrier interval and adopting different subcarrier intervals, the corresponding interpretations of the first field are different.

[0019] As an example, the features of this application include: for the scenario where the cells in the first cell set adopt different subcarrier intervals, a new high-layer parameter, that is, the second information block, is added to adapt to the scheduling requirements corresponding to different subcarrier intervals, and further flexibility is increased to improve the overall performance of the system.

[0020] According to one aspect of the present application, the above method is characterized in that when the subcarrier spacings adopted by the active BWPs respectively corresponding to all the cells included in the first cell set are the same, the target information block is the first information block; when the subcarrier spacings adopted by the active BWPs respectively corresponding to all the cells included in the first cell set are not all the same, the target information block is the second information block.

[0021] As an embodiment, the features of the present application include: for the first cell set to be scheduled, different parameter sets, namely the first information block and the second information block, are designed respectively for two scenarios of the same subcarrier spacing and different subcarrier spacings, so as to adapt to the scheduling requirements corresponding to different subcarrier spacings, and further increase flexibility to improve the overall system performance.

[0022] According to one aspect of the present application, the above method is characterized in that the first DCI is a downlink grant, the first domain included in the first DCI indicates the time domain position of the HARQ-ACK (Hybrid Automatic Repeat request Acknowledgement) of the channel in at least one cell included in the first cell set, and the target information block includes a timing list of the PDSCH (Physical Downlink Shared CHannel) configured by RRC (Radio Resource Control) signaling to the downlink ACK (Acknowledgement).

[0023] As an embodiment, the features of the present application include: when the first domain indicates the HARQ-ACK feedback time, since the subcarrier spacings corresponding to the cells in the first cell set to be scheduled are different, the corresponding processing delays will also be different; while in the single DCI scheduling multi-cell scenario in the traditional Release-17, the subcarrier spacings of multiple cells are the same and the above problems will not occur; therefore, a new timing list needs to be designed to meet the requirements of different delays brought by different subcarrier spacings of different cells.

[0024] According to one aspect of the present application, the above method is characterized in that the first DCI is a downlink grant, the first domain included in the first DCI indicates the PRB bundling size of the channel in at least one cell included in the first cell set, and the target information block includes the PRB (Physical Resource Block) bundling type configured by RRC signaling.

[0025] As an example, the features of the present application include: when the first field indicates the PRB bundling size, since the subcarrier intervals corresponding to the cells in the first cell set to be scheduled are different, the corresponding PRB bundling size and the channel decoding method 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 problems will not occur; therefore, a new timing list needs to be designed to meet the different delay requirements brought by different subcarrier intervals for different cells.

[0026] According to one aspect of the present application, the above method is characterized in that the first DCI is an uplink grant, the first field included in the first DCI indicates the beta_offset of the codebook of HARQ-ACK for the channels in at least one cell included in the first cell set, and the target information block includes the BetaOffsets configured by RRC signaling.

[0027] As an example, the features of the present application include: when the first field indicates the beta_offset adopted by the codebook of HARQ-ACK, since the subcarrier intervals corresponding to the cells in the first cell set to be scheduled are different, the corresponding appropriate beta_offset values 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 problems will not occur; therefore, a new timing list needs to be designed to meet the different delay requirements brought by different subcarrier intervals for different cells.

[0028] According to one aspect of the present application, the above method is characterized in that the first field included in the first DCI indicates the frequency hopping of the channels in at least one cell included in the first cell set, and the target information block includes the frequency hopping parameters configured by RRC signaling.

[0029] As an example, the features of the present application include: when the first field indicates the frequency hopping parameters, since the subcarrier intervals corresponding to the cells in the first cell set to be scheduled are different, the corresponding appropriate frequency hopping parameters 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 problems will not occur; therefore, a new timing list needs to be designed to meet the requirements of different frequency hopping parameters for different cells.

[0030] According to one aspect of the present application, the above method is characterized by including:

[0031] Receiving the channel in at least one cell included in the first cell set.

[0032] According to one aspect of the present application, the above method is characterized in that it includes:

[0033] Transmit the channel in at least one cell included in the first cell set.

[0034] According to one aspect of the present application, the above method is characterized in that the value indicated by the first field included in the first DCI is common to each cell in the first cell set.

[0035] As an embodiment, the features of the present application include: the value indicated by the first field included in the first DCI is common to each cell in the first cell set. In the scenario where the first information block and the second information block are introduced, the way of interpreting the first field can be increased, so as to adapt to the scenario where different subcarrier intervals are adopted by the first cell set for scheduling, improve the adaptability of the system to different scenarios, and improve the overall performance.

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

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

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

[0039] The present application discloses a method in a second node for multi-cell scheduling used for wireless communication, which includes:

[0040] Transmit a first information block and a second information block;

[0041] Transmit a first DCI, where the first DCI schedules a first cell set, and the first cell set includes multiple cells;

[0042] Wherein, the first DCI includes a first field, and the interpretation of the first field included in the first DCI depends on a target information block, and the target information block is one of the first information block and the second information block; whether the target information block is the first information block or the second information block depends on whether the subcarrier intervals adopted by the active BWPs respectively corresponding to all cells included in the first cell set are the same.

[0043] According to one aspect of the present application, the above method is characterized in that when the subcarrier spacings adopted by the active BWPs respectively corresponding to all the cells included in the first cell set are the same, the target information block is the first information block; when the subcarrier spacings adopted by the active BWPs respectively corresponding to all the cells included in the first cell set are not all the same, the target information block is the second information block.

[0044] According to one aspect of the present application, the above method is characterized in that the first DCI is a downlink grant, the first field included in the first DCI indicates the time domain position of the HARQ-ACK for the channel in at least one cell included in the first cell set, and the target information block includes a list of timings of PDSCH to downlink ACK configured by RRC signaling.

[0045] According to one aspect of the present application, the above method is characterized in that the first DCI is a downlink grant, the first field included in the first DCI indicates the PRB bundling size of the channel in at least one cell included in the first cell set, and the target information block includes a PRB bundling type configured by RRC signaling.

[0046] According to one aspect of the present application, the above method is characterized in that the first DCI is an uplink grant, the first field included in the first DCI indicates the beta_offset of the codebook of the HARQ-ACK for the channel in at least one cell included in the first cell set, and the target information block includes BetaOffsets configured by RRC signaling.

[0047] According to one aspect of the present application, the above method is characterized in that the first DCI is an uplink grant, the first field included in the first DCI indicates the frequency hopping of the channel in at least one cell included in the first cell set, and the target information block includes frequency hopping parameters configured by RRC signaling.

[0048] According to one aspect of the present application, the above method is characterized by including:

[0049] Transmitting the channel in at least one cell included in the first cell set.

[0050] According to one aspect of the present application, the above method is characterized by including:

[0051] Receiving the channel in at least one cell included in the first cell set.

[0052] According to one aspect of the present application, the value indicated by the first field included in the first DCI is common to each cell in the first cell set.

[0053] According to one aspect of the present application, the method is characterized in that the second node is a base station.

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

[0055] The present application discloses a device for a first node used in wireless communication, including:

[0056] A first receiver, receiving a first information block and a second information block;

[0057] The first receiver receives a first DCI, and the first DCI schedules a first cell set, where the first cell set includes a plurality of cells;

[0058] Wherein, the first DCI includes a first field, and the interpretation of the first field included in the first DCI depends on a target information block, and the target information block is one of the first information block and the second information block; whether the target information block is the first information block or the second information block depends on whether the subcarrier intervals adopted by the active BWPs corresponding to all the cells included in the first cell set are the same.

[0059] The present application discloses a device for a second node used in wireless communication, including:

[0060] A second transmitter, transmitting a first information block and a second information block;

[0061] The second transmitter transmits a first DCI, and the first DCI schedules a first cell set, where the first cell set includes a plurality of cells;

[0062] Wherein, the first DCI includes a first field, and the interpretation of the first field included in the first DCI depends on a target information block, and the target information block is one of the first information block and the second information block; whether the target information block is the first information block or the second information block depends on whether the subcarrier intervals adopted by the active BWPs corresponding to all the cells included in the first cell set are the same.

[0063] As an embodiment, compared with the traditional solution, the present application has the following advantageous but not limited advantages:

[0064] For the scenario where different sub - carrier intervals are adopted for the cells in the first cell set, a new high - layer parameter, i.e., the second information block, is added to adapt to the scheduling requirements corresponding to different sub - carrier intervals, thereby further increasing flexibility to improve the overall system performance;

[0065] Ensure signaling compatibility, without adding new bits in the current DCI format, reduce signaling overhead, and improve spectrum efficiency. Brief Description of the Drawings

[0066] By reading the following detailed description of non - restrictive embodiments with reference to the accompanying drawings, other features, objects, and advantages of the present application will become more apparent:

[0067] Figure 1 Shows a flowchart of transmission by a first node according to an embodiment of the present application;

[0068] Figure 2 Shows a schematic diagram of a network architecture according to an embodiment of the present application;

[0069] Figure 3 Shows a schematic diagram of an embodiment of a radio protocol architecture of a user plane and a control plane according to an embodiment of the present application;

[0070] Figure 4 Shows a schematic diagram of a first communication device and a second communication device according to an embodiment of the present application;

[0071] Figure 5 Shows a flowchart of transmission between a first node and a second node according to an embodiment of the present application;

[0072] Figure 6 Shows a flowchart of reception by a first node according to an embodiment of the present application;

[0073] Figure 7 Shows a flowchart of transmission by a first node according to an embodiment of the present application;

[0074] Figure 8 Shows a schematic diagram of a first information block and a second information block according to an embodiment of the present application;

[0075] Figure 9 Shows a schematic diagram of a first cell set according to an embodiment of the present application;

[0076] Figure 10 Shows a block diagram of a processing device in a first node according to an embodiment of the present application;

[0077] Figure 11Shows a structural block diagram of a processing device in a second node according to an embodiment of the present application. Detailed implementation

[0078] The technical solutions of the present application will be further described in detail below in conjunction with the accompanying drawings. It should be noted that, without conflict, the embodiments and features in the embodiments of the present application can be combined with each other arbitrarily. Considering aspects such as performance, flexibility, complexity, overhead, and compatibility, those skilled in the art have the motivation to flexibly combine the embodiments in different drawings without conflict, including but not limited to the embodiments in the attached Figure 1 drawings and the embodiments in the attached Figure 5 -attached Figure 9 drawings, the embodiments in the attached Figure 5 drawings and the embodiments in the attached Figure 6 -attached Figure 9 drawings, etc.

[0079] Example 1

[0080] Embodiment 1 exemplifies a flowchart of the transmission of a first node according to an embodiment of the present application, as shown in the attached Figure 1 drawings. In the attached Figure 1 drawings, each box represents a step. In particular, the order of the steps in the box does not represent a specific chronological relationship between the steps.

[0081] The first node receives a first information block and a second information block in step 101; receives a first DCI in step 102, and the first DCI schedules a first cell set, and the first cell set includes multiple cells;

[0082] In Embodiment 1, the first DCI includes a first field, and the interpretation of the first field included in the first DCI depends on a target information block, and the target information block is one of the first information block or the second information block; whether the target information block is the first information block or the second information block depends on whether the subcarrier intervals adopted by the active BWPs corresponding to all the cells included in the first cell set are the same.

[0083] As an embodiment, the first information block includes higher layer signaling.

[0084] As an embodiment, the first information block includes higher layer parameters.

[0085] As an embodiment, the first information block includes one or more RRC IEs (Information Elements).

[0086] As an example, the first information block includes one or more fields in an RRC IE.

[0087] As an example, the first information block is transmitted via a ServingCellConfig IE.

[0088] As an example, the first information block is transmitted via an mc-DCI-SetOfCellsToAddModList.

[0089] As an example, the first information block is transmitted via an mc-DCI-SetOfCellsToAddModList-r18.

[0090] As an example, the first information block is transmitted via an mc-DCI-SetOfCellsToAddModList-r19.

[0091] As an example, the first information block is transmitted via an MC-DCI-SetOfCells.

[0092] As an example, the first information block is transmitted via an MC-DCI-SetOfCells-r18.

[0093] As an example, the first information block is transmitted via an MC-DCI-SetOfCells-r19.

[0094] As an example, the second information block includes higher layer signaling.

[0095] As an example, the second information block includes higher layer parameters.

[0096] As an example, the second information block includes one or more RRC IEs.

[0097] As an example, the second information block includes one or more fields in an RRC IE.

[0098] As an example, the second information block is transmitted via a ServingCellConfig IE.

[0099] As an example, the second information block is transmitted via an mc-DCI-SetOfCellsToAddModList.

[0100] As an example, the second information block is transmitted via an mc-DCI-SetOfCellsToAddModList-r18.

[0101] As an example, the second information block is transmitted via mc-DCI-SetOfCellsToAddModList-r19.

[0102] As an example, the second information block is transmitted via MC-DCI-SetOfCells.

[0103] As an example, the second information block is transmitted via MC-DCI-SetOfCells-r18.

[0104] As an example, the second information block is transmitted via MC-DCI-SetOfCells-r19.

[0105] As an example, the first information block and the second information block are transmitted via an RRC IE.

[0106] As an example, the first information block and the second information block are transmitted via a field in an RRC IE.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0126] As an example, the interpretation of the first field included in the first DCI depending on the target information block means that the parameter corresponding to the value indicated by the first field included in the first DCI depends on the target information block.

[0127] As an embodiment, the interpretation of the first domain included in the first DCI depending on the target information block means that the configuration corresponding to the value indicated by the first domain included in the first DCI depends on the target information block.

[0128] As an embodiment, the first DCI schedules the multiple cells included in the first cell set.

[0129] As a sub - embodiment of this embodiment, the first DCI schedules a target radio signal, and the target radio signal includes multiple sub - signals, and the multiple sub - signals are respectively sent by the first node in the multiple cells.

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

[0131] As a sub - embodiment of this embodiment, the first DCI schedules a target radio signal, and the transport channel occupied by the target radio signal includes a UL - SCH (UpLink - Shared CHannel).

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

[0133] As a sub - embodiment of this embodiment, the multiple sub - signals respectively correspond to multiple transport blocks.

[0134] As a sub - embodiment of this embodiment, the multiple sub - signals respectively correspond to multiple bit blocks.

[0135] As an embodiment, the first DCI schedules multiple channels, and the multiple channels are respectively transmitted in the multiple cells.

[0136] As an embodiment, the first DCI schedules multiple channels, and the multiple channels are respectively transmitted in multiple active BWPs in the multiple cells.

[0137] As an embodiment, the multiple cells are respectively multiple serving cells.

[0138] As an embodiment, the multiple cells respectively correspond to multiple ServCellIndex.

[0139] As an embodiment, the multiple cells respectively correspond to multiple servCellId.

[0140] As an embodiment, the multiple cells respectively correspond to multiple scheduledCellIds.

[0141] As an embodiment, the multiple cells respectively correspond to multiple CIFs (Carrier Indicator Fields).

[0142] As an embodiment, the multiple cells respectively correspond to multiple PhysCellIds.

[0143] As an embodiment, the multiple cells are respectively multiple CCs (Component Carriers).

[0144] As an embodiment, the multiple cells are respectively multiple carriers.

[0145] Example 2

[0146] Embodiment 2 exemplifies a schematic diagram of a network architecture according to an embodiment of the present application, as shown in the appendix Figure 2 as follows.

[0147] The appendix Figure 2 illustrates the network architecture 200. The network architecture 200 is a network architecture of LTE (Long-Term Evolution), LTE-A (Long-Term Evolution Advanced), 5G system, 5G-Advanced and future 6G systems. The network architectures of LTE, LTE-A, 5G system, 5G-Advanced and future 6G systems are referred to as EPS (Evolved Packet System). The 5GNR or LTE network architecture may be referred to as 5GS (5G System) / EPS or some other suitable term; the 6G network architecture may be referred to as 6GS (6G System) / EPS or some other suitable term. The 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 service 230.. The network architecture 200 may be interconnected with other access networks, but these entities / interfaces are not shown for simplicity. As shown in the appendix Figure 2As shown, the network architecture 200 provides packet switching services. However, those skilled in the art will readily understand that the various concepts presented throughout this application can be extended to networks that provide circuit switching services. The RAN 202 includes Node B 203 and other nodes 204. Node 203 provides user and control plane protocol termination towards the UE 201. Node 203 can be connected to other nodes 204 via the Xn interface (e.g., backhaul). Node 203 can also be referred to as a base station, base transceiver station, radio base station, radio transceiver, transceiver function, Basic Service Set (BSS), Extended Service Set (ESS), Transmitter Receiver Point (TRP), or some other suitable term. Node 203 provides an access point to the core network 210 for the UE 201; the core network 210 is a 5GC (5G Core Network) / EPC (Evolved Packet Core), or alternatively, the core network 210 is a 6GC. Examples of the UE 201 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptop computers, Personal Digital Assistants (PDAs), satellite radios, Global Positioning Systems, 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 the UE 201 as a mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable term. Node 203 is connected to the core network 210 via the S1 / NG interface.The core network 210 includes an MME (Mobility Management Entity) / AMF (Authentication Management Field) / SMF (Session Management Function) 211, other MME / AMF / SMFs 214, an S-GW (Service Gateway) / UPF (User Plane Function) 212, and a P-GW (Packet Data Network Gateway) / UPF 213. The MME / AMF / SMF 211 is a control node that processes 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, and the S-GW / UPF 212 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 is connected to the Internet service 230. The Internet service 230 includes operator-corresponding Internet protocol services, specifically including the Internet, intranet, IMS (IP Multimedia Subsystem), and packet switching services.

[0148] As an embodiment, the first node described in this application includes the UE 201.

[0149] As an embodiment, the second node described in this application includes the node 203.

[0150] As an embodiment, the node 203 is a macro cell base station.

[0151] As an embodiment, the node 203 is a micro cell base station.

[0152] As an embodiment, the node 203 is a pico cell base station.

[0153] As an embodiment, the node 203 is a femtocell.

[0154] As an embodiment, the node 203 is a base station device that supports large delay differences.

[0155] As an embodiment, the node 203 is an aerial platform device.

[0156] As an embodiment, the node 203 is a satellite device.

[0157] As an embodiment, the node 203 is a test device (e.g., a transceiver that emulates some functions of a base station, a signaling tester).

[0158] As an embodiment, the UE 201 includes a mobile phone.

[0159] As an embodiment, the UE 201 includes a terminal.

[0160] As an embodiment, the UE 201 is a means of transportation including an automobile.

[0161] As an embodiment, the radio link from the UE 201 to the node 203 is an uplink, and the uplink is used to perform uplink transmission.

[0162] As an embodiment, the radio link from the node 203 to the UE 201 is a downlink, and the downlink is used to perform downlink transmission.

[0163] As an embodiment, the radio link between the node 203 and the UE 201 includes a cellular network link.

[0164] As an embodiment, the node 203 and the UE 201 are connected through the Uu air interface.

[0165] As an embodiment, the sender of the first DCI includes the gNB 203.

[0166] As an embodiment, the receiver of the first DCI includes the UE 201.

[0167] As an embodiment, the sender of the channel in the at least one cell includes the gNB 203.

[0168] As an embodiment, the receiver of the channel in the at least one cell includes the UE 201.

[0169] As an embodiment, the receiver of the channel in the at least one cell includes the gNB 203.

[0170] As an embodiment, the sender of the channel in the at least one cell includes the UE 201.

[0171] As an embodiment, the UE 201 supports the 5G system.

[0172] As an example, the node 203 supports the 5G system.

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

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

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

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

[0177] As an example, the UE 201 supports at least single DCI multi-cell scheduling, and the subcarrier spacings adopted by the multiple carriers are different.

[0178] As an example, the node 203 supports at least single DCI multi-cell scheduling, and the subcarrier spacings adopted by the multiple carriers are different.

[0179] Example 3

[0180] Embodiment 3 exemplifies a schematic diagram of an embodiment of the radio protocol architecture of the user plane and the control plane according to an embodiment of the present application, as shown in the appendix Figure 3 as shown.

[0181] Figure 3 is a schematic diagram illustrating an embodiment of the radio protocol architecture for the user plane 350 and the control plane 300 Figure 3Show the radio protocol architecture of the control plane 300 for the first communication node device (UE or RSU (Road Side Unit) in V2X (Vehicle to Everything), in-vehicle device or in-vehicle communication module) and the second node device (gNB, UE or RSU in V2X, in-vehicle device or in-vehicle 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 as PHY 301 in this article. 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, and these sublayers terminate at the second node device. The PDCP sublayer 304 provides multiplexing between different radio bearers and logical channels. The PDCP sublayer 304 also provides security by encrypting data packets, and provides handover support for the first communication node device between the second communication node devices. The RLC sublayer 303 provides segmentation and reassembly of upper layer data packets, retransmission of lost data packets, and reordering of data packets to compensate for disordered reception due to HARQ (Hybrid Automatic Repeat Request). The MAC sublayer 302 provides multiplexing between logical and transport channels. The MAC sublayer 302 is also responsible for allocating various radio resources (e.g., resource blocks) in 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 in the control plane 300 is responsible for obtaining radio resources (i.e., radio bearers) and configuring the lower layers using RRC signaling between the second communication node device and the first communication node device.The radio protocol architecture of the user plane 350 includes Layer 1 (L1) and Layer 2 (L2). The radio protocol architecture for the first communication node device and the second communication node device in the user plane 350 is generally the same as the corresponding layers and sub-layers in the control plane 300 for the physical layer 351, the PDCP sub-layer 354 in L2 355, the RLC sub-layer 353 in L2 355, and the MAC sub-layer 352 in L2 355. However, the PDCP sub-layer 354 also provides header compression for upper layer data packets to reduce radio transmission overhead. The L2 355 in the user plane 350 also includes an SDAP (Service Data Adaptation Protocol) sub-layer 356. The SDAP sub-layer 356 is responsible for the mapping between QoS (Quality of Service) flows and data radio bearers (DRBs) to support service diversity. Although not shown, the first communication node device may have several upper layers above L2 355, including a network layer (e.g., an IP (Internet Protocol) layer) that terminates at the P-GW on the network side and an application layer that terminates at the other end of the connection (e.g., a remote UE, a server, etc.).

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

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

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

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

[0186] As an example, the channel in at least one cell in this application is generated at the RRC 306.

[0187] As an example, the channel in at least one cell in this application is generated at the MAC 302 or the MAC 352.

[0188] As an example, the upper layer in this application refers to the layer above the physical layer.

[0189] As an example, the upper layer in this application includes the MAC layer.

[0190] As an example, in the present application, the higher layer includes the RRC layer.

[0191] Example 4

[0192] Example 4 illustrates a schematic diagram of a first communication device and a second communication device according to an embodiment of the present application, as shown in the accompanying Figure 4 drawing. The accompanying Figure 4 drawing is a block diagram of a first communication device 410 and a second communication device 450 that communicate with each other in an access network.

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

[0194] 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.

[0195] 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 the functionality of L2. 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 for the second communication device 450 based on various priority metrics. The controller / processor 475 is also responsible for HARQ operations, 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). The transmit processor 416 implements encoding and interleaving to facilitate forward error correction (FEC) at the second communication device 450, and mapping of signal constellations based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-ary phase shift keying (M-PSK), M-ary quadrature amplitude modulation (M-QAM)). The multi-antenna transmit processor 471 performs digital spatial precoding on the encoded and modulated symbols, including codebook-based precoding, non-codebook-based precoding, and beamforming processing, to generate one or more parallel streams. The transmit processor 416 then maps each parallel stream to subcarriers, multiplexes the modulated symbols with reference signals (e.g., pilots) in the time domain and / or frequency domain, and then uses the inverse fast Fourier transform (IFFT) to generate a physical channel carrying time-domain multi-carrier symbol streams. Subsequently, the multi-antenna transmit processor 471 performs transmit analog precoding / beamforming operations on the time-domain multi-carrier symbol streams. Each transmitter 418 converts the baseband multi-carrier symbol streams provided by the multi-antenna transmit processor 471 into radio frequency streams and then provides them to different antennas 420.

[0196] 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 signals via its respective antenna 452. Each receiver 454 recovers the information modulated onto the radio frequency carrier, and converts the radio frequency stream into a baseband multi-carrier symbol stream and provides it to the receive processor 456. The receive processor 456 and the multi-antenna receive processor 458 perform various signal processing functions of L1. The multi-antenna receive processor 458 performs receive analog precoding / beamforming operations on the baseband multi-carrier symbol stream from the receivers 454. The receive processor 456 uses the Fast Fourier Transform (FFT) to convert the baseband multi-carrier 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 receive processor 456, where the reference signal will be used for channel estimation, and the data signal recovers any parallel streams destined for the second communication device 450 after multi-antenna detection in the multi-antenna receive processor 458. The symbols on each parallel stream are demodulated and recovered in the receive processor 456, and soft decisions are generated. Subsequently, the receive processor 456 decodes and de-interleaves the soft decisions to recover the upper layer data and control signals transmitted by the first communication device 410 on the physical channel. Subsequently, the upper layer data and control signals are provided to the controller / processor 459. The controller / processor 459 performs the functions of L2. The controller / processor 459 may be associated with a memory 460 that stores program code and data. The memory 460 may be referred to as a computer-readable medium. In the DL, the controller / processor 459 provides demultiplexing between the transmission and the logical channels, packet reassembly, decryption, header decompression, control signal processing to recover the upper layer data packets from the core network. Subsequently, the upper layer data packets are 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 the Acknowledgement (ACK) and / or Negative Acknowledgement (NACK) protocols to support HARQ operations.

[0197] 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 an upper layer data packet to a controller / processor 459. The data source 467 represents all protocol layers above L2. Similar to the transmission function at the first communication device 410 described in DL, the controller / processor 459 performs 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, and implements L2 functions for the user plane and the control plane. The controller / processor 459 is also responsible for HARQ operations, retransmission of lost packets, and signaling to the first communication device 410. A transmit processor 468 performs modulation mapping and channel coding processing. A multi-antenna transmit processor 457 performs digital multi-antenna spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing. Subsequently, the transmit processor 468 modulates the generated parallel streams into a multi-carrier / single-carrier symbol stream, and after passing through an analog precoding / beamforming operation in the multi-antenna transmit processor 457, provides it to different antennas 452 via a transmitter 454. Each transmitter 454 first converts the baseband symbol stream provided by the multi-antenna transmit processor 457 into a radio frequency symbol stream and then provides it to the antenna 452.

[0198] In the transmission from the second communication device 450 to the first communication device 410, the functions at the first communication device 410 are similar to the receiving functions 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 a radio frequency signal through its corresponding antenna 420, converts the received radio frequency signal into a baseband signal, and provides the baseband signal to a multi-antenna receive processor 472 and a receive processor 470. The receive processor 470 and the multi-antenna receive processor 472 jointly implement L1 functions. A controller / processor 475 implements L2 functions. The controller / processor 475 may be associated with a memory 476 that stores program code and data. The memory 476 may be referred to as a computer-readable medium. The controller / processor 475 provides demultiplexing between the transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover the upper layer data packet from the second communication device 450. The upper layer data packet from the controller / processor 475 may be provided to the core network. The controller / processor 475 is also responsible for error detection using the ACK and / or NACK protocols to support HARQ operations.

[0199] As an example, 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 is configured to at least receive a first information block and a second information block; and receive a first DCI, the first DCI scheduling a first cell set, the first cell set including a plurality of cells; the first DCI includes a first field, the interpretation of the first field included in the first DCI depends on a target information block, the target information block being one of the first information block and the second information block; whether the target information block is the first information block or the second information block depends on whether the subcarrier spacings adopted by the active BWPs respectively corresponding to all the cells included in the first cell set are the same.

[0200] As an example, the second communication device 450 includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generating actions when executed by at least one processor, the actions including: receiving a first information block and a second information block; and receiving a first DCI.

[0201] As an example, 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 is configured to at least transmit a first information block and a second information block; and transmit a first DCI, the first DCI scheduling a first cell set, the first cell set including a plurality of cells; the first DCI includes a first field, the interpretation of the first field included in the first DCI depends on a target information block, the target information block being one of the first information block and the second information block; whether the target information block is the first information block or the second information block depends on whether the subcarrier spacings adopted by the active BWPs respectively corresponding to all the cells included in the first cell set are the same.

[0202] As an example, the first communication device 410 includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generating actions when executed by at least one processor, the actions including: transmitting a first information block and a second information block; and transmitting a first DCI.

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

[0204] As an example, the second node described in the present application includes the first communication device 410.

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

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

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

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

[0209] Example 5

[0210] Embodiment 5 exemplifies a flowchart of transmission between a first node and a second node according to an embodiment of the present application, as shown in the appendix Figure 5 shown. In the appendix Figure 5 , communication is performed between the first node U1 and the second node N2 via a wireless link. It should be specifically noted that the order in this embodiment does not limit the signal transmission order and the implementation order in the present application.

[0211] For the first node U1, in step S510, a first information block and a second information block are received; in step S511, a first DCI is received.

[0212] For the second node N2, in step S520, a first information block and a second information block are sent; in step S521, a first DCI is sent.

[0213] In Embodiment 5, the first DCI schedules a first cell set, and the first cell set includes multiple cells; the first DCI includes a first field, and the interpretation of the first field included in the first DCI depends on a target information block, and the target information block is one of the first information block and the second information block; whether the target information block is the first information block or the second information block depends on whether the subcarrier intervals adopted by the active BWPs respectively corresponding to all the cells included in the first cell set are the same.

[0214] As an embodiment, the first node U1 is the first node described in the present application.

[0215] As an embodiment, the second node N2 is the second node described in the present application.

[0216] As an embodiment, the first node U1 is a terminal in the present application.

[0217] As an embodiment, the second node N2 is a base station in the present application.

[0218] Typically, when the subcarrier intervals adopted by the active BWPs respectively corresponding to all the cells included in the first cell set are the same, the target information block is the first information block; when the subcarrier intervals adopted by the active BWPs respectively corresponding to all the cells included in the first cell set are not all the same, the target information block is the second information block.

[0219] As an embodiment, the subcarrier intervals adopted by the active BWPs respectively corresponding to all the cells included in the first cell set are the same, and the target information block is the first information block.

[0220] As an example, the subcarrier spacings adopted by the active BWPs respectively corresponding to all the cells included in the first cell set are not all the same, and the target information block is the second information block.

[0221] As an example, the meaning that the subcarrier spacings adopted by the active BWPs respectively corresponding to all the cells included in the first cell set are not all the same includes that there are at least two cells among all the cells included in the first cell set, and the subcarrier spacings adopted by the two active BWPs corresponding to them are different.

[0222] As an example, the meaning that the subcarrier spacings adopted by the active BWPs respectively corresponding to all the cells included in the first cell set are not all the same includes that for any two cells among all the cells included in the first cell set, the subcarrier spacings adopted by the two active BWPs corresponding to them are different.

[0223] Typically, the first DCI is a downlink grant, the first field included in the first DCI indicates the time domain position of the HARQ-ACK for the channel in at least one cell included in the first cell set, and the target information block includes a list of timings from the PDSCH configured by RRC signaling to the downlink ACK.

[0224] As an example, the first DCI is a downlink grant, and the DCI format of the first DCI is format 1_3.

[0225] As an example, the first field included in the first DCI is the PDSCH-to-HARQ_feedback timing indicator.

[0226] As an example, the first field included in the first DCI indicates the time domain position of the HARQ-ACK for the channel in each cell included in the first cell set.

[0227] As an example, the channel in the at least one cell includes the PDSCH.

[0228] As an example, the channel in the at least one cell includes the DL-SCH.

[0229] As an example, the target information block includes dl-DataToUL-ACK.

[0230] As an example, the name of the parameter carrying the target information block includes dl-DataToUL-ACK.

[0231] As an example, the name of the parameter carrying the target information block includes dl.

[0232] As an example, the name of the parameter carrying the target information block includes DataToUL.

[0233] As an example, the name of the parameter carrying the target information block includes ACK.

[0234] As an example, the target information block includes a list of timings of PDSCH to downlink ACK configured by RRC signaling, and the target information block is one of the first information block or the second information block.

[0235] As a sub - example of this example, the first information block is an RRC parameter of a Release before version R - 19, and the second information block is an RRC parameter of version R - 19 or after version R - 19.

[0236] As a sub - example of this example, the first information block is dl - DataToUL - ACK - r16.

[0237] As a sub - example of this example, the first information block is dl - DataToUL - ACK - r17.

[0238] As a sub - example of this example, the first information block is dl - DataToUL - ACK - r18.

[0239] As a sub - example of this example, the second information block is dl - DataToUL - ACK - r19.

[0240] As a sub - example of this example, the second information block is dl - DataToUL - ACK - DCI - 1 - 3.

[0241] As a sub - example of this example, the second information block is dl - DataToUL - ACK - SCS - DCI - 1 - 3.

[0242] As a sub - example of this example, the second information block is dl - DataToUL - ACK - DCI - 1 - 3 - r19.

[0243] Typically, the first DCI is a downlink grant, the first domain included in the first DCI indicates the PRB bundling size of the channel in at least one cell included in the first cell set, and the target information block includes an RRC - signaled PRB bundling type.

[0244] As an example, the first DCI is a downlink grant, and the DCI format of the first DCI is format 1_3.

[0245] As an example, the first field included in the first DCI is the PRB bundling size indicator.

[0246] As an example, the first field included in the first DCI indicates the PRB bundling size for the channel in each cell included in the first cell set.

[0247] As an example, the channel in the at least one cell includes the PDSCH.

[0248] As an example, the channel in the at least one cell includes the DL-SCH.

[0249] As an example, the target information block includes the prb-BundlingType.

[0250] As an example, the name of the parameter carrying the target information block includes the prb-BundlingType.

[0251] As an example, the name of the parameter carrying the target information block includes the prb.

[0252] As an example, the name of the parameter carrying the target information block includes the BundlingType.

[0253] As an example, the target information block includes the PRB bundling type configured by RRC signaling, and the target information block is one of the first information block or the second information block.

[0254] As a sub-example of this example, the first information block is an RRC parameter of a Release before version R-19, and the second information block is an RRC parameter of version R-19 or later than version R-19.

[0255] As a sub-example of this example, the first information block is the prb-BundlingType.

[0256] As a sub-example of this example, the second information block is the prb-BundlingType-r19.

[0257] As a sub-example of this example, the second information block is the prb-BundlingType-DCI-1-3.

[0258] As a sub - embodiment of this embodiment, the second information block is prb - BundlingType - SCS - DCI - 1 - 3.

[0259] As a sub - embodiment of this embodiment, the second information block is prb - BundlingType - DCI - 1 - 3 - r19.

[0260] Typically, the first DCI is an uplink grant, and the first field included in the first DCI indicates the beta_offset of the codebook for HARQ - ACK of the channel in at least one cell included in the first cell set. The target information block includes BetaOffsets configured by RRC signaling.

[0261] As an embodiment, the first DCI is an uplink grant, and the DCI format of the first DCI is format 0_3.

[0262] As an embodiment, the first field included in the first DCI is a beta_offset indicator.

[0263] As an embodiment, the first field included in the first DCI indicates the beta_offset of the codebook for HARQ - ACK of the channel in each cell included in the first cell set.

[0264] As an embodiment, the channel in the at least one cell includes PUSCH.

[0265] As an embodiment, the channel in the at least one cell includes UL - SCH.

[0266] As an embodiment, the target information block includes betaOffsets.

[0267] As an embodiment, the name of the parameter carrying the target information block includes betaOffsets.

[0268] As an embodiment, the name of the parameter carrying the target information block includes beta.

[0269] As an embodiment, the name of the parameter carrying the target information block includes Offsets.

[0270] As an embodiment, the target information block includes BetaOffsets configured by RRC signaling, and the target information block is one of the first information block or the second information block.

[0271] As a sub - embodiment of this embodiment, the first information block is an RRC parameter of a Release before Release 19, and the second information block is an RRC parameter of Release 19 or after Release 19.

[0272] As a sub - embodiment of this embodiment, the first information block is betaOffsets.

[0273] As a sub - embodiment of this embodiment, the second information block is betaOffsets - r19.

[0274] As a sub - embodiment of this embodiment, the second information block is betaOffsets - DCI - 0 - 3.

[0275] As a sub - embodiment of this embodiment, the second information block is betaOffsets - SCS - DCI - 0 - 3.

[0276] As a sub - embodiment of this embodiment, the second information block is betaOffsets - DCI - 0 - 3 - r19.

[0277] Typically, the first DCI is an uplink grant. The first field included in the first DCI indicates frequency hopping of a channel in at least one cell included in the first cell set, and the target information block includes frequency hopping parameters configured by RRC signaling.

[0278] As an embodiment, the first DCI is an uplink grant, and the DCI format of the first DCI is format 0_3.

[0279] As an embodiment, the first field included in the first DCI is Frequency hopping flag.

[0280] As an embodiment, the first field included in the first DCI indicates frequency hopping of the channel in each cell included in the first cell set.

[0281] As an embodiment, the channel in the at least one cell includes PUSCH.

[0282] As an embodiment, the channel in the at least one cell includes UL - SCH.

[0283] As an embodiment, the target information block includes frequencyHopping.

[0284] As an embodiment, the name of the parameter carrying the target information block includes frequency.

[0285] As an example, the name of the parameter carrying the target information block includes Hopping.

[0286] As an example, the target information block includes the hopping parameters configured by RRC signaling, and the target information block is one of the first information block or the second information block.

[0287] As a sub - example of this example, the first information block is the RRC parameter of a Release before Release 19, and the second information block is the RRC parameter of Release 19 or after Release 19.

[0288] As a sub - example of this example, the first information block is frequencyHopping.

[0289] As a sub - example of this example, the second information block is frequencyHopping - r19.

[0290] As a sub - example of this example, the second information block is frequencyHopping - DCI - 0 - 3.

[0291] As a sub - example of this example, the second information block is frequencyHopping - SCS - DCI - 0 - 3.

[0292] As a sub - example of this example, the second information block is frequencyHopping - DCI - 0 - 3 - r19.

[0293] As an example, the sub - carrier spacing of a cell in this application refers to the sub - carrier spacing adopted by the active DL BWP in a cell.

[0294] As an example, the sub - carrier spacing of a cell in this application refers to the sub - carrier spacing adopted by the active UL BWP in a cell.

[0295] As an example, a cell in this application corresponds to a carrier.

[0296] As an example, a cell in this application corresponds to a serving cell.

[0297] As an example, a cell in this application corresponds to a CC.

[0298] Example 6

[0299] Example 6 exemplifies the flowchart of the reception by the first node according to an embodiment of this application, as shown in the appendix Figure 6as shown. In the appendix Figure 6 In it, communication is carried out between the first node U3 and the second node N4 through a wireless link. It should be specifically noted that the order in this embodiment does not limit the signal transmission order and the implementation order in this application.

[0300] For the first node U3, in step S530, the channel is received in at least one cell included in the first cell set.

[0301] For the second node N4, in step S540, the channel is sent in at least one cell included in the first cell set.

[0302] As an embodiment, the first node receives the channel in each cell included in the first cell set.

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

[0304] As an embodiment, the first DCI schedules the channel in at least one cell included in the first cell set.

[0305] As an embodiment, the first DCI indicates at least one of the time domain resource, frequency domain resource, MCS (Modulation and Coding Scheme), and HARQ process number occupied by the channel in at least one cell included in the first cell set.

[0306] As an embodiment, the first DCI indicates the TCI (Transmission Configuration Indication) adopted by the channel in at least one cell included in the first cell set.

[0307] As an embodiment, step S530 is located after step S511 in Embodiment 5.

[0308] As an embodiment, step S530 is not earlier than step S511 in Embodiment 5.

[0309] As an embodiment, step S540 is located after step S521 in Embodiment 5.

[0310] As an embodiment, step S540 is not earlier than step S521 in Embodiment 5.

[0311] Example 7

[0312] Example 7 exemplifies a flowchart of transmissions by a first node according to an embodiment of the present application, as shown in the appended Figure 7 figure. In the appended Figure 7 figure, communication is carried out between a first node U5 and a second node N6 via a wireless link. It should be specifically noted that the order in this embodiment does not limit the signal transmission order and implementation order in the present application.

[0313] For the first node U5, in step S550, the channel is transmitted in at least one cell included in the first cell set.

[0314] For the second node N6, in step S560, the channel is received in at least one cell included in the first cell set.

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

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

[0317] As an embodiment, the first DCI schedules the channel in at least one cell included in the first cell set.

[0318] As an embodiment, 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 at least one cell included in the first cell set.

[0319] As an embodiment, the first DCI indicates the SRI (SRS Resource Set Indicator) adopted by the channel in at least one cell included in the first cell set.

[0320] As an embodiment, step S550 is located after step S511 in Example 5.

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

[0322] As an embodiment, step S560 is located after step S521 in Example 5.

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

[0324] Example 8

[0325] Example 8 illustrates a schematic diagram of a first information block and a second information block according to an embodiment of the present application, as shown in the appendix Figure 8 as shown

[0326] As an embodiment, both the first information block and the second information block are directed to one cell in the first cell set

[0327] As an embodiment, the first information block and the second information block are directed to all cells in the first cell set

[0328] As an embodiment, any cell in the first cell set is configured with the corresponding first information block and second information block

[0329] Example 9

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

[0331] As an embodiment, the first cell is any one of the K1 cells

[0332] As an embodiment, K1 is a positive integer greater than 1

[0333] As an embodiment, the first DCI is used to indicate the K1 cells

[0334] As an embodiment, the first DCI is used to indicate that K1 PDSCHs are transmitted in the K1 cells included in the first cell set, and the K1 PDSCHs are respectively transmitted in the K1 cells

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

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

[0337] As an embodiment, the first DCI is used to indicate that K1 sub - signals are transmitted in the K1 cells included in the first cell set, and the K1 sub - signals are respectively transmitted in the K1 cells

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

[0339] As a sub - embodiment of this embodiment, the K1 sub - signals correspond to 1 HARQ process number.

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

[0341] Example 10

[0342] Embodiment 10 illustrates a structural block diagram of a processing device in a first node according to an embodiment of the present application, as shown in the appendix Figure 10 shown. In the appendix Figure 10 a processing device 1000 in a first node includes a first receiver 1001 and a first transmitter 1002, where the first transmitter 1002 is optional.

[0343] In Embodiment 10, the first receiver 1001 receives a first information block and a second information block; and the first receiver 1001 receives a first DCI, and the first DCI schedules a first cell set, and the first cell set includes a plurality of cells;

[0344] In Embodiment 10, the first DCI includes a first field, and the interpretation of the first field included in the first DCI depends on a target information block, and the target information block is one of the first information block and the second information block; whether the target information block is the first information block or the second information block depends on whether the sub - carrier intervals adopted by the active BWPs respectively corresponding to all cells included in the first cell set are the same.

[0345] As an embodiment, when the sub - carrier intervals adopted by the active BWPs respectively corresponding to all cells included in the first cell set are the same, the target information block is the first information block; when the sub - carrier intervals adopted by the active BWPs respectively corresponding to all cells included in the first cell set are not all the same, the target information block is the second information block.

[0346] As an embodiment, the first DCI is a downlink grant, and the first field included in the first DCI indicates the time - domain position of HARQ - ACK for a channel in at least one cell included in the first cell set, and the target information block includes a timing list of PDSCH to downlink ACK configured by RRC signaling.

[0347] As an embodiment, the first DCI is a downlink grant, and the first field included in the first DCI indicates the PRB bundling size of a channel in at least one cell included in the first cell set, and the target information block includes a PRB bundling type configured by RRC signaling.

[0348] As an example, the first DCI is an uplink grant, and the first field included in the first DCI indicates the beta_offset of the codebook for HARQ-ACK of a channel in at least one cell included in the first cell set, and the target information block includes BetaOffsets configured by RRC signaling.

[0349] As an example, the first DCI is an uplink grant, and the first field included in the first DCI indicates the frequency hopping of a channel in at least one cell included in the first cell set, and the target information block includes frequency hopping parameters configured by RRC signaling.

[0350] As an example, the first receiver 1001 receives the channel in at least one cell included in the first cell set.

[0351] As an example, the first transmitter 1002 transmits the channel in at least one cell included in the first cell set.

[0352] As an example, the value indicated by the first field included in the first DCI is common to each cell in the first cell set.

[0353] As an example, the first node is a user equipment.

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

[0355] As an example, the first receiver 1001 includes 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, the data source 467} in Embodiment 4.

[0356] As an example, the first transmitter 1002 includes at least one of {the antenna 452, the transmitter 454, the transmitting processor 468, the multi-antenna transmitting processor 457, the controller / processor 459, the memory 460, the data source 467} in Embodiment 4.

[0357] Example 11

[0358] Embodiment 11 exemplifies a structural block diagram of a processing device in a second node according to an embodiment of the present application, as shown in the appendix Figure 11 shown. In the appendix Figure 11Among them, the processing device 1100 in the second node includes a second transmitter 1101 and a second receiver 1102.

[0359] In Embodiment 11, the second transmitter 1101 transmits a first information block and a second information block; and the second transmitter 1101 transmits a first DCI, and the first DCI schedules a first cell set, and the first cell set includes a plurality of cells;

[0360] In Embodiment 11, the first DCI includes a first field, and the interpretation of the first field included in the first DCI depends on a target information block, and the target information block is one of the first information block and the second information block; whether the target information block is the first information block or the second information block depends on whether the subcarrier intervals adopted by the active BWPs respectively corresponding to all the cells included in the first cell set are the same.

[0361] As an embodiment, when the subcarrier intervals adopted by the active BWPs respectively corresponding to all the cells included in the first cell set are the same, the target information block is the first information block; when the subcarrier intervals adopted by the active BWPs respectively corresponding to all the cells included in the first cell set are not all the same, the target information block is the second information block.

[0362] As an embodiment, the first DCI is a downlink grant, and the first field included in the first DCI indicates the time domain position of HARQ-ACK for the channel in at least one cell included in the first cell set, and the target information block includes a timing list of PDSCH to downlink ACK configured by RRC signaling.

[0363] As an embodiment, the first DCI is a downlink grant, and the first field included in the first DCI indicates the PRB bundling size of the channel in at least one cell included in the first cell set, and the target information block includes a PRB bundling type configured by RRC signaling.

[0364] As an embodiment, the first DCI is an uplink grant, and the first field included in the first DCI indicates the beta_offset of the codebook of HARQ-ACK for the channel in at least one cell included in the first cell set, and the target information block includes BetaOffsets configured by RRC signaling.

[0365] As an embodiment, the first DCI is an uplink grant, and the first field included in the first DCI indicates the frequency hopping of the channel in at least one cell included in the first cell set, and the target information block includes frequency hopping parameters configured by RRC signaling.

[0366] As an example, the second transmitter 1101 transmits the channel in at least one cell included in the first cell set.

[0367] As an example, the second receiver 1102 receives the channel in at least one cell included in the first cell set.

[0368] As an example, the value indicated by the first field included in the first DCI is common to each cell in the first cell set.

[0369] As an example, the second node is a base station device.

[0370] As an example, the second node is a user equipment.

[0371] As an example, the second transmitter 1101 includes at least one of {the antenna 420, the transmitter 418, the transmit processor 416, the multi-antenna transmit processor 471, the controller / processor 475, the memory 476} in Embodiment 4.

[0372] As an example, the second receiver 1102 includes at least one of {the antenna 420, the receiver 418, the receive processor 470, the multi-antenna receive processor 472, the controller / processor 475, the memory 476} in Embodiment 4.

[0373] Typically, unless otherwise indicated, the names of RRC IEs and the names of the fields included in the RRC IEs in this application can be suffixed with -r16, -r17, -r18, -r19, or -r20. Those skilled in the art should understand that adding the above suffixes will not affect the interpretation of the RRC IEs and the fields included in the RRC IEs in this application.

[0374] Those of ordinary skill in the art can understand that all or part of the steps in the above method can be completed by instructing relevant hardware through a program, and the program can be stored in a computer-readable storage medium, such as a read-only memory, a hard disk, or an optical disc, etc. 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 a hardware form or in the form of a software function module. This application is not limited to any specific form of the 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 control aircraft, aircraft, small aircraft, mobile phones, tablet computers, laptops, vehicle-mounted communication devices, transportation means, vehicles, RSU, wireless sensors, network cards, Internet of Things 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, network cards, vehicle-mounted communication devices, low-cost mobile phones, low-cost tablet computers, and other wireless communication devices. The base station or system device 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, aerial base stations, RSU, drones, test equipment, such as transceiver devices or signaling testers that simulate some functions of base stations, and other wireless communication devices.

[0375] Those skilled in the art should understand that the present invention can be implemented in other specified forms without departing from its core or basic characteristics. Therefore, the currently disclosed embodiments should be regarded as descriptive rather than restrictive in any case. The scope of the invention is determined by the appended claims rather than the previous description, and all modifications within the equivalent meaning and scope thereof are considered to be included therein.

Claims

1. A method for a terminal used for multi-cell scheduling of wireless communications, characterized in that: include: receiving a first information block and a second information block; receiving a first DCI, where the first DCI schedules a first cell set, where the first cell set includes multiple cells; Among them, the first DCI includes a first domain, and the interpretation of the first domain included in the first DCI depends on the target information block, and the target information block is one of the first information block or the second information block; whether the target information block is the first information block or the second information block depends on whether the subcarrier spacing adopted by the active BWP corresponding to all cells included in the first cell set is the same.

2. The method according to claim 1, characterized in that When the subcarrier spacing used by the active BWPs respectively corresponding to all cells included in the first cell set is the same, the target information block is the first information block; when the subcarrier spacing used by the active BWPs respectively corresponding to all cells included in the first cell set is not the same, the target information block is the second information block.

3. The method according to claim 1 or 2, characterized in that: The first DCI is a downlink authorization, the first field included in the first DCI indicates the time domain position of the HARQ-ACK for a channel in at least one cell included in the first cell set, and the target information block includes a timing list of PDSCH to downlink ACK configured by RRC signaling.

4. The method according to claim 1 or 2, characterized in that: The first DCI is a downlink grant, the first field included in the first DCI indicates a PRB bundling size of a channel in at least one cell included in the first cell set, and the target information block includes a PRB bundling type configured by RRC signaling.

5. The method according to claim 1 or 2, characterized in that: The first DCI is an uplink grant, the first field included in the first DCI indicates a beta_offset of a HARQ-ACK codebook for a channel in at least one cell included in the first cell set, and the target information block includes BetaOffsets configured by RRC signaling.

6. The method according to claim 1 or 2, characterized in that: The first DCI is an uplink grant, the first field included in the first DCI indicates frequency hopping of a channel in at least one cell included in the first cell set, and the target information block includes frequency hopping parameters configured by RRC signaling.

7. The method according to any one of claims 1 to 6, characterized in that include: The channel is received in at least one cell included in the first cell set.

8. The method according to any one of claims 1 to 6, characterized in that include: The channel is transmitted in at least one cell included in the first cell set.

9. The method according to any one of claims 1 to 8, characterized in that: The value indicated by the first field included in the first DCI is common to each cell in the first cell set.

10. A terminal, characterized in that: The terminal includes: one or more processors and a memory; The memory is coupled to the one or more processors, and the memory is used to store computer program codes, where the computer program codes include computer instructions. The one or more processors call the computer instructions to enable the terminal to execute the method according to any one of claims 1 to 9.

11. A method for a base station used for multi-cell scheduling of wireless communications, characterized in that: include: Sending a first information block and a second information block; Sending a first DCI, where the first DCI schedules a first cell set, where the first cell set includes multiple cells; Among them, the first DCI includes a first domain, and the interpretation of the first domain included in the first DCI depends on the target information block, and the target information block is one of the first information block or the second information block; whether the target information block is the first information block or the second information block depends on whether the subcarrier spacing adopted by the active BWP corresponding to all cells included in the first cell set is the same.

12. The method according to claim 11, characterized in that When the subcarrier spacing used by the active BWPs respectively corresponding to all cells included in the first cell set is the same, the target information block is the first information block; when the subcarrier spacing used by the active BWPs respectively corresponding to all cells included in the first cell set is not the same, the target information block is the second information block.

13. The method according to claim 11 or 12, characterized in that: The first DCI is a downlink authorization, the first field included in the first DCI indicates the time domain position of the HARQ-ACK for a channel in at least one cell included in the first cell set, and the target information block includes a timing list of PDSCH to downlink ACK configured by RRC signaling.

14. The method according to claim 11 or 12, characterized in that: The first DCI is a downlink grant, the first field included in the first DCI indicates a PRB bundling size of a channel in at least one cell included in the first cell set, and the target information block includes a PRB bundling type configured by RRC signaling.

15. The method according to claim 11 or 12, characterized in that: The first DCI is an uplink grant, the first field included in the first DCI indicates a beta_offset of a HARQ-ACK codebook for a channel in at least one cell included in the first cell set, and the target information block includes BetaOffsets configured by RRC signaling.

16. The method according to claim 11 or 12, characterized in that: The first DCI is an uplink grant, the first field included in the first DCI indicates frequency hopping of a channel in at least one cell included in the first cell set, and the target information block includes frequency hopping parameters configured by RRC signaling.

17. The method according to any one of claims 11 to 16, characterized in that include: The channel is transmitted in at least one cell included in the first cell set.

18. The method according to any one of claims 11 to 16, characterized in that include: The channel is received in at least one cell included in the first cell set.

19. The method according to any one of claims 11 to 18, characterized in that The value indicated by the first field included in the first DCI is common to each cell in the first cell set.

20. 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, and the memory is used to store computer program codes, wherein the computer program codes include computer instructions, and the one or more processors call the computer instructions to enable the Internet of Things device to execute the method according to any one of claims 11-19.

Images