Communication method and communication device
By introducing multiple subfields in DCI, allowing one DCI to schedule multiple cells and multiple physical shared channels at the same time, the problem of low DCI scheduling efficiency in carrier aggregation scenarios is solved, and efficient physical shared channel scheduling is achieved.
Patent Information
- Application Number
- CN202311438718.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-10-31
- Publication Date
- 2025-05-02
AI Technical Summary
In the carrier aggregation scenario, it is difficult for the downlink control information DCI to efficiently schedule multiple physical shared channels, resulting in low scheduling efficiency.
By introducing multiple subfields in the DCI, one DCI allows a DCI to schedule the physical shared channels of multiple cells at the same time, and multiple physical shared channels share the same scheduling information on the same cell, thereby improving scheduling efficiency.
It realizes efficient scheduling of multiple cells and multiple physical shared channels, reduces the load size and transmission complexity of DCI, and improves the overall performance of the system.
Smart Images

Figure CN119921918A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of communication technology, and in particular to a communication method and a communication device. Background Art
[0002] Carrier aggregation (CA) is a technology that aggregates multiple carrier components (CCs) to support a larger transmission bandwidth. CA supports aggregation between CCs with the same or different sub-carrier spacing (SCS), for example, CC 1 with an SCS of 15kHz, CC 2 with an SCS of 15kHz, and CC 3 with an SCS of 60kHz.
[0003] When multiple CCs in a CA scenario are scheduled through downlink control information (DCI), the DCI can only schedule one physical downlink share channel (PDSCH) or one physical uplink share channel (PUSCH) on each CC.
[0004] That is to say, when multiple PDSCH / PUSCH need to be scheduled on certain CCs in the CA scenario, they need to be scheduled through multiple DCIs, and the scheduling efficiency is low. Summary of the invention
[0005] The embodiments of the present application provide a communication method and a communication device, which are beneficial to improving the efficiency of DCI scheduling PDSCH / PUSCH.
[0006] In a first aspect, the present application provides a communication method. Taking a terminal executing the method as an example, the method includes: the terminal receives downlink control information DCI from a network device, and the DCI is used to schedule M physical shared channels on multiple cells. The first cell is one of the multiple cells, and the first cell includes N physical shared channels scheduled by DCI, where N is an integer greater than 1, and M is an integer greater than N; further, the terminal transmits the M physical shared channels based on the DCI.
[0007] In the method described in the first aspect, one DCI can jointly schedule the physical shared channels of multiple cells, and multiple physical shared channels on the same cell can be jointly scheduled by the DCI. Compared with the method in which only one physical shared channel on the same cell can be scheduled by DCI, it is beneficial to improve the scheduling efficiency of the physical shared channels on the DCI-scheduled cell.
[0008] In a possible implementation, the DCI includes a first field, the first field includes a first subfield and a second subfield, the first subfield is applied to N physical shared channels on a first cell, and the second subfield is applied to a physical shared channel on a second cell, and the second cell is one of the multiple cells different from the first cell. By implementing this possible implementation, the same information can be indicated for all physical shared channels on the same cell through the same subfield, which is conducive to saving the payload size of the DCI.
[0009] In a possible implementation manner, the DCI includes a second field, and the value of the second field of the M physical shared channels is the same.
[0010] In a possible implementation, the second field is a time domain resource allocation TDRA field, the TDRA field is used to indicate a first index value, the first index value is used to indicate a second index value group, the second index value in the second index value group corresponds one-to-one to a cell in a plurality of cells, the second index value is used to indicate a time domain resource set, the time domain resource set includes time domain resources of different physical shared channels on the cell corresponding to the second index value. By implementing this possible implementation, the time domain resources of each physical shared channel can be determined respectively through a piece of information indicated by the TDRA field, which is conducive to saving the payload size of the DCI.
[0011] In a possible implementation manner, the DCI includes a third field, the third field includes M subfields, and the M subfields are respectively applied to M physical shared channels.
[0012] In a possible implementation, the physical shared channel is a physical downlink shared channel, and the terminal sends HARQ feedback information to the network device. The number of bits of the HARQ feedback information is the number of transport blocks carried in the maximum number of physical downlink shared channels that can be scheduled in the multiple cells.
[0013] In a possible implementation, the HARQ feedback information includes multiple groups of bit groups, the bit groups in the multiple groups of bit groups correspond one-to-one to cells in multiple cells, the bits in the bit groups correspond one-to-one to the transmission blocks of the physical downlink shared channel on the cells corresponding to the bit groups, and the bits in the bit groups are used to indicate whether the transmission block corresponding to the bits is successfully received.
[0014] In a possible implementation, the terminal sends first capability information and second capability information to the network device, where the first capability information is used to indicate that the terminal supports multi-cell scheduling, and the second capability information is used to indicate that the terminal supports multiple physical shared channel scheduling on the same cell.
[0015] In a possible implementation manner, a terminal receives first configuration information from a network device, where the first configuration information is used to configure a maximum number of physical shared channels that can be scheduled in each of a plurality of cells.
[0016] In the second aspect, the present application provides a communication method. Taking a network device executing the method as an example, the method includes: the network device sends downlink control information DCI to a terminal, and the DCI is used to schedule M physical shared channels on multiple cells. The first cell is one of the multiple cells, and the first cell includes N physical shared channels scheduled by DCI, N is an integer greater than 1, and M is an integer greater than N; further, the network device transmits the M physical shared channels based on DCI.
[0017] For the beneficial effects obtained by the method described in the second aspect, reference may be made to the description of the beneficial effects obtained by the method described in the first aspect.
[0018] In one possible implementation, the DCI includes a first field, the first field includes a first subfield and a second subfield, the first subfield is applied to N physical shared channels on a first cell, and the second subfield is applied to a physical shared channel on a second cell, where the second cell is one of multiple cells different from the first cell.
[0019] In a possible implementation manner, the DCI includes a second field, and the value of the second field of the M physical shared channels is the same.
[0020] In one possible implementation, the second field is a time domain resource allocation TDRA field, which is used to indicate a first index value, and the first index value is used to indicate a second index value group. The second index value in the second index value group corresponds one-to-one to a cell in a plurality of cells, and the second index value is used to indicate a time domain resource set, which includes time domain resources of different physical shared channels on the cell corresponding to the second index value.
[0021] In a possible implementation manner, the DCI includes a third field, the third field includes M subfields, and the M subfields are respectively applied to M physical shared channels.
[0022] In a possible implementation, the physical shared channel is a physical downlink shared channel, and the network device receives HARQ feedback information from the terminal, the number of bits of the HARQ feedback information being the number of transport blocks carried in the maximum number of physical downlink shared channels that can be scheduled in the multiple cells.
[0023] In a possible implementation, the HARQ feedback information includes multiple groups of bit groups, the bit groups in the multiple groups of bit groups correspond one-to-one to cells in multiple cells, the bits in the bit groups correspond one-to-one to the transmission blocks of the physical downlink shared channel on the cells corresponding to the bit groups, and the bits in the bit groups are used to indicate whether the transmission block corresponding to the bits is successfully received.
[0024] In a possible implementation, the network device receives first capability information and second capability information from the terminal, the first capability information is used to indicate that the terminal supports multi-cell scheduling, and the second capability information is used to indicate that the terminal supports multiple physical shared channel scheduling on the same cell.
[0025] In a possible implementation manner, the network device sends first configuration information to the terminal, where the first configuration information is used to configure a maximum number of physical shared channels that can be scheduled in each of a plurality of cells.
[0026] In a third aspect, the present application provides a communication device, which may be a terminal, a device in a terminal, or a device that can be used in combination with a terminal. The communication device may also be a chip system. The communication device may execute the method described in the first aspect. The functions of the communication device may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions. The unit or module may be software and / or hardware. The operations and beneficial effects performed by the communication device may refer to the method and beneficial effects described in the first aspect above.
[0027] In a fourth aspect, the present application provides a communication device, which may be a network device, or a device in a network device, or a device that can be used in combination with a network device. The communication device may also be a chip system. The communication device may execute the method described in the second aspect. The functions of the communication device may be implemented by hardware, or by hardware executing corresponding software implementations. The hardware or software includes one or more units or modules corresponding to the above functions. The unit or module may be software and / or hardware. The operations and beneficial effects performed by the communication device may refer to the method and beneficial effects described in the second aspect above.
[0028] In a fifth aspect, the present application provides a communication device, comprising a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor or send signals from the processor to other communication devices outside the communication device, and the processor is used to implement the method described in the first aspect through a logic circuit or by executing code instructions, or the processor is used to implement the method described in the second aspect through a logic circuit or by executing code instructions.
[0029] In a sixth aspect, the present application provides a computer-readable storage medium, in which a computer program or instruction is stored. When the computer program or instruction is executed by a communication device, the method described in the first aspect is implemented, or the method described in the second aspect is implemented.
[0030] In a seventh aspect, the present application provides a computer program product comprising instructions, which, when a communication device reads and executes the instructions, causes the communication device to execute the method as described in the first aspect, or causes the communication device to execute the method as described in the second aspect.
[0031] In an eighth aspect, the present application provides a communication system, comprising a communication device for executing the method described in the first aspect above, and a communication device for executing the method described in the second aspect above. BRIEF DESCRIPTION OF THE DRAWINGS
[0032] Figure 1 is a schematic diagram of a communication system provided in an embodiment of the present application;
[0033] Figure 2 is a schematic diagram of carrier aggregation provided in an embodiment of the present application;
[0034] Figure 3 It is a schematic diagram of several DCI-scheduled physical shared channels provided in an embodiment of the present application;
[0035] Figure 4 This is a schematic diagram of a DCI scheduling PDSCH provided in an embodiment of the present application;
[0036] Figure 5 It is a flow chart of a communication method provided in an embodiment of the present application;
[0037] Figure 6 It is a schematic diagram of determining the time domain resources of each physical shared channel based on the TDRA field provided by an embodiment of the present application;
[0038] Figure 7 This is a schematic diagram of a maximum number of PDSCHs that can be scheduled by a DCI provided in an embodiment of the present application;
[0039] Figure 8 It is a schematic diagram of a PDSCH actually scheduled by DCI provided in an embodiment of the present application;
[0040] Fig. 9 is a structural diagram of a communication device provided in an embodiment of the present application;
[0041] Fig.10 It is a structural diagram of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0042] In order to facilitate a specific understanding of the embodiments of the present application, the system architecture involved in the embodiments of the present application is first introduced below.
[0043] Figure 1 FIG. 1 is a schematic diagram of the architecture of a communication system 1000 used in an embodiment of the present application. Figure 1 As shown, the communication system includes a radio access network (RAN) 100 and a core network 200. Optionally, the communication system 1000 may also include the Internet 300. The RAN 100 includes at least one RAN node (such as Figure 1 110a and 110b in the figure, collectively referred to as 110), and may also include at least one terminal (such as Figure 1 120a-120j in the figure are collectively referred to as 120). RAN 100 may also include other RAN nodes, such as wireless relay equipment and / or wireless backhaul equipment ( Figure 1 (not shown in the figure). The terminal 120 is connected to the RAN node 110 by wireless means, and the RAN node 110 is connected to the core network 200 by wireless or wired means. The core network device in the core network 200 and the RAN node 110 in the RAN 100 can be independent and different physical devices, or the same physical device that integrates the logical functions of the core network device and the logical functions of the RAN node. Terminals and terminals and RAN nodes and RAN nodes can be connected to each other by wire or wireless means. It should be noted that the RAN node 110 may also be referred to as the network device 110 in the following text.
[0044] RAN100 may be an evolved universal terrestrial radio access (E-UTRA) system, a new radio (NR) system, and a future radio access system defined in the 3rd generation partnership project (3GPP). RAN100 may also include two or more of the above-mentioned different radio access systems. RAN100 may also be an open RAN (O-RAN).
[0045] RAN nodes, also known as radio access network equipment, RAN entities or access nodes, are used to help terminals access the communication system wirelessly. In one application scenario, a RAN node can be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next generation NodeB (gNB) in a fifth generation (5G) mobile communication system, a next generation NodeB in a sixth generation (6G) mobile communication system, or a base station in a future mobile communication system. A RAN node can be a macro base station (such as a Figure 1 110a), or a micro base station or an indoor station (such as Figure 1 110b) in the figure, it can also be a relay node or a donor node.
[0046] In another application scenario, the cooperation of multiple RAN nodes can be used to help the terminal achieve wireless access, and different RAN nodes respectively implement part of the functions of the base station. For example, the RAN node can be a centralized unit (CU), a distributed unit (DU) or a radio unit (RU). The CU here completes the functions of the radio resource control protocol and the packet data convergence protocol (PDCP) of the base station, and can also complete the function of the service data adaptation protocol (SDAP); the DU completes the functions of the radio link control layer and the medium access control (MAC) layer of the base station, and can also complete the functions of part of the physical layer or all of the physical layer. For the specific description of the above-mentioned various protocol layers, please refer to the relevant technical specifications of 3GPP. RU can be used to implement the transceiver function of radio frequency signals. CU and DU can be two independent RAN nodes, or they can be integrated in the same RAN node, such as integrated in a baseband unit (BBU). RU can be included in a radio frequency device, such as a remote radio unit (RRU) or an active antenna unit (AAU). The CU can be further divided into two types of RAN nodes: CU-control plane and CU-user plane.
[0047] In different systems, RAN nodes may have different names. For example, in an O-RAN system, CU may be called an open CU (open CU, O-CU), DU may be called an open DU (open DU, O-DU), and RU may be called an open RU (open RU, O-RU). The RAN node in the embodiment of the present application may be implemented by a software module, a hardware module, or a combination of a software module and a hardware module. For example, the RAN node may be a server loaded with a corresponding software module. The embodiments of the present application do not limit the specific technology and specific device form adopted by the RAN node. For the convenience of description, the following description takes a base station as an example of a RAN node.
[0048] A terminal is a device with wireless transceiver function, which can send signals to a base station or receive signals from a base station. A terminal can also be called a terminal device, user equipment (UE), a mobile station, a mobile terminal, etc. The terminal can be widely used in various scenarios, for example, device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IOT), virtual reality, augmented reality, industrial control, automatic driving, telemedicine, smart grid, smart furniture, smart office, smart wear, smart transportation, smart city, etc. The terminal can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a wearable device, a vehicle, an airplane, a ship, a robot, a mechanical arm, a smart home device, etc. The embodiments of the present application do not limit the specific technology and specific device form adopted by the terminal.
[0049] Base stations and terminals can be fixed or movable. Base stations and terminals can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on the water surface; they can also be deployed on airplanes, balloons, and artificial satellites. The embodiments of this application do not limit the application scenarios of base stations and terminals.
[0050] The roles of the base station and the terminal can be relative, for example, Figure 1The helicopter or drone 120i in the figure can be configured as a mobile base station. For the terminal 120j that accesses the wireless access network 100 through 120i, the terminal 120i is a base station; but for the base station 110a, 120i is a terminal, that is, 110a and 120i communicate through the wireless air interface protocol. Of course, 110a and 120i can also communicate through the interface protocol between base stations. In this case, relative to 110a, 120i is also a base station. Therefore, base stations and terminals can be collectively referred to as communication devices. Figure 1 110a and 110b in the figure may be referred to as communication devices having base station functions. Figure 1 120a-120j in the figure can be called communication devices with terminal functions.
[0051] Base stations and terminals, base stations and base stations, and terminals and terminals can communicate through authorized spectrum, unauthorized spectrum, or both; they can communicate through spectrum below 6 gigahertz (GHz), spectrum above 6 GHz, or spectrum below 6 GHz and spectrum above 6 GHz. The embodiments of the present application do not limit the spectrum resources used for wireless communication.
[0052] In the embodiments of the present application, the functions of the base station may also be performed by a module (such as a chip) in the base station, or by a control subsystem including the base station function. The control subsystem including the base station function here may be a control center in the above-mentioned application scenarios such as smart grid, industrial control, smart transportation, and smart city. The functions of the terminal may also be performed by a module (such as a chip or a modem) in the terminal, or by a device including the terminal function.
[0053] In this application, the base station sends a downlink signal or downlink information to the terminal, and the downlink information is carried on the downlink channel; the terminal sends an uplink signal or uplink information to the base station, and the uplink information is carried on the uplink channel. In order to communicate with the base station, the terminal needs to establish a wireless connection with the cell controlled by the base station. The cell with which the terminal has established a wireless connection is called the service cell of the terminal. When the terminal communicates with the service cell, it will also be interfered by signals from neighboring cells.
[0054] It can be understood that in the embodiments of the present application, PDSCH, PDCCH and PUSCH are merely examples of downlink data channels, downlink control channels and uplink data channels, respectively. In different systems and different scenarios, data channels and control channels may have different names, and the embodiments of the present application do not limit this.
[0055] In order to facilitate understanding of the relevant contents of the embodiments of the present application, some of the terms involved in the embodiments of the present application are explained below. This part is only for ease of understanding and cannot be regarded as a disclosure or specific limitation of the technical solution of the present application.
[0056] 1. Cell
[0057] A cell is a set of resources managed by a base station, including frequency domain resources and spatial domain resources. The frequency domain resources of a cell include uplink frequency domain resources and / or downlink frequency domain resources; the spatial domain resources of a cell can be the spatial domain resources corresponding to a beam or a group of beams, which can also be understood as a cell corresponding to a specific physical coverage area. In an embodiment of the present application, different cells can be managed by different base stations. For example, cell #1 and cell #2 can be managed by different base stations. In this case, it can be said that cell #1 and cell #2 do not share the same station. Cell #1 and cell #2 can also be managed by the same base station and have the same baseband processing unit and / or radio frequency processing unit. This application does not specifically limit this.
[0058] Depending on the frequency band range in which the cell is located (or understood to correspond to), the cell in the range of 450MHz-6000MHz can be called a cell in the frequency range (FR) 1 or a low-frequency cell, and the cell in the range of 24250MHz-52600MHz can be called a cell in FR2 or a high-frequency cell. It should be noted that there is a one-to-one correspondence between the cell and the carrier. In the absence of logical conflicts, the cell and the carrier can be used interchangeably. In other words, the frequency band range in which the cell is located can be understood as the frequency band range in which the frequency of the cell's corresponding carrier is located, and can also be called the working frequency band of the cell or the frequency band in which the cell is located.
[0059] 2. CA
[0060] See also Figure 2 As shown in the figure, CA technology is a technology that aggregates two or more CCs to support a larger transmission bandwidth. In other words, CA technology can realize frequency resource integration, aggregate spectrum resources of the same frequency band or different frequency bands for terminals to use, thereby improving the utilization rate of the entire network resources.
[0061] When CA is configured for a terminal, the terminal may have multiple service cells, including a primary cell (PCell) and at least one SCell. PCell is the cell where the terminal and the network device establish an initial connection (connection establishment), or the cell where the terminal reestablishes the radio resource control (RRC) connection. PCell is responsible for the radio resource control RRC communication with the terminal, and the CC corresponding to PCell is called the primary component carrier (PCC). SCell is added / modified / released through the RRC connection reconfiguration message after the initial security activation procedure; SCell is used to provide additional radio resources, and there is no RRC communication between SCell and the terminal.
[0062] It should be noted that in the CA scenario, it can support aggregation of cells of the same SCS, and it can also support aggregation of cells of different SCSs.
[0063] 3. DCI
[0064] The network device sends DCI to the terminal through the physical downlink control channel (PDCCH), and the DCI includes scheduling information of the physical shared channel. In a possible implementation, the DCI includes: control information related to data transmission, such as resource allocation information for data transmission, format information of uplink / downlink resources in a time slot, and power control information of physical shared channels and signals, etc.; information of dynamic time slot configuration; resource preemption information, etc. Further, after the terminal detects the DCI, it transmits the physical shared channel according to the DCI. It should be noted that the physical shared channels mentioned in this application include PDSCH and PUSCH. If there is no special explanation in the following text, the physical shared channel can be PDSCH or PUSCH. It should be noted that in this application, "transmission" includes "sending" and "receiving". If the execution subject of "transmission" is the sending end, then "transmission" is equivalent to "sending"; if the execution subject of "transmission" is the receiving end, then "transmission" is equivalent to "receiving". For example, "terminal transmits PDSCH" is equivalent to "terminal receives PDSCH", and "terminal transmits PUSCH" is equivalent to "terminal sends PUSCH".
[0065] According to the relationship between the carrier sending DCI and the scheduled physical shared channel, DCI can be divided into the following three types:
[0066] ①, DCI scheduled by the carrier; for example, Figure 3 As shown in 3a, the DCI for scheduling the physical shared channel on CC 1 is sent on CC 1, and the DCI for scheduling the physical shared channel on CC 2 is also sent on CC 2; wherein, the DCI format of the DCI can be DCI format 0_0, DCI format 1_0, DCI format 0_1, DCI format 1_1, DCI format 0_2 or DCI format 1_2.
[0067] ②, DCI scheduled across carriers; for example, Figure 3 As shown in 3b, the DCI for scheduling the physical shared channel on CC 2 is sent on CC 1; wherein the DCI format of the DCI may be DCI format 0_1, DCI format 1_1, DCI format 0_2 or DCI format 1_2.
[0068] ③. Multi-carrier scheduled DCI, also called multi-cell scheduled DCI or single DCI; Figure 3 As shown in 3c, the DCI for scheduling the physical shared channel on CC 1 and the DCI for scheduling the physical shared channel on CC 2 are the same DCI (ie Figure 3 The single DCI in the multi-carrier scheduled DCI is sent on CC 1. The DCI format of the single DCI may be DCI format 0_3 or DCI format 1_3. It should be noted that the multiple CCs scheduled by the multi-carrier scheduled DCI usually correspond to the same SCS; and for a CC scheduled by the multi-carrier scheduled DCI, the number of physical shared channels that can be scheduled by the DCI on the CC is usually 1.
[0069] 4. Hybrid automatic repeat request (HARQ) feedback information
[0070] In wireless communication systems, HARQ technology is usually used between the sender and the receiver to improve the reliability of data transmission. The sender sends a transport block (TB) to the receiver. If the receiver successfully receives the TB, the receiver feeds back an acknowledgement (ACK) to the sender; if the receiver does not successfully receive the TB, the receiver feeds back a negative acknowledgement (NACK) message to the sender, and the sender retransmits the TB after receiving the NACK. HARQ feedback information is used to feedback PDSCH reception, semi-persistent scheduling (SPS) PDSCH reception, and SPS PDSCH release reception. HARQ feedback information can be carried on the physical downlink control channel (PUCCH) or on the PUSCH.
[0071] For example, Figure 4 As shown, the network device sends a DCI for scheduling PDSCH in time slot (slot) n, and the DCI indicates that the terminal is in slot n+K 0 Receive PDSCH on and in slot n+K 0 +K 1 The HARQ feedback information corresponding to the PDSCH is fed back on the PUCCH of the DCI. 0 The value of K 1 The value of and the indication information used to indicate the PUCCH resource information. 0 It can be understood as the offset between the time slot where the DCI is located and the time slot where the PDSCH is located; K 1 It can be understood as the offset between the time slot where the PDSCH is located and the time slot where the HARQ feedback information is located.
[0072] In a possible implementation, the terminal can feedback multiple HARQ feedback information through the HARQ codebook in an uplink time slot, and one bit in the HARQ codebook can be used to indicate the HARQ feedback information of a TB or the HARQ feedback information of a HARQ process. Usually, the HARQ codebook includes a semi-static codebook (also referred to as a type 1 HARQ-ACK codebook or a type 1 semi-static codebook) and a dynamic codebook (also referred to as a type 2 HARQ-ACK codebook or a type 2 dynamic codebook). The network device can instruct the terminal to generate the type of HARQ-ACK codebook through an RRC parameter (e.g., a pdsch-HARQ-ACK-Codebook parameter).
[0073] Among them, the type 2 dynamic codebook is a codebook generation mode that changes dynamically according to the actual data scheduling situation. The dynamic codebook is generated based on the cumulative count and total count of the {serving cell, PDCCH monitoring occasion}-pair. Among them, the cumulative count is indicated by the counter downlink assignment index (C-DAI), and the total count is indicated by the total downlink assignment index (T-DAI). The C-DAI is included in the DCI, indicating the {serving cell, PDCCH monitoring occasion}-pair with the smallest corresponding cell index value in the PDSCH jointly scheduled by the DCI, until the cumulative number of the current serving cell and the current PDCCH monitoring occasion. The order of accumulation is first according to the serving cell index and then according to the PDCCH monitoring occasion index. T-DAI is included in the DCI and indicates the {Serving Cell, PDCCH monitoring opportunity}-pair of the PDSCH with the smallest cell index in the PDSCH scheduled by the DCI, up to the total number of the current PDCCH monitoring opportunities, which can be updated at each PDCCH monitoring opportunity. In this application, the downlink allocation index has the same meaning as the downlink allocation indication.
[0074] In summary, when multiple physical shared channels need to be scheduled in certain cells in a CA scenario, they need to be scheduled through multiple DCIs, and the scheduling efficiency is low. In order to improve the efficiency of DCI scheduling of physical shared channels, the present application provides a communication method and a communication device. The communication method and the communication device provided in the embodiments of the present application are described in detail below in conjunction with the accompanying drawings.
[0075] See also Figure 5 , Figure 5 is a flow chart of a communication method provided in an embodiment of the present application. Figure 5 As shown, the communication method includes the following steps S501 to S502: Figure 5 The method execution subject shown is described by taking a terminal and a network device as an example. It can be understood that Figure 5 The execution subject of the method shown may also be a module in a terminal (for example, a chip) and a module in a network device (for example, a chip, or a CU, or a DU).
[0076] S501. A network device sends a DCI to a terminal, where the DCI is used to schedule M physical shared channels on multiple cells. The multiple cells scheduled by the DCI include a first cell, where N physical shared channels are scheduled by the DCI, where N is an integer greater than 1, and M is an integer greater than N. Accordingly, the terminal receives the DCI from the network device.
[0077] When there are M physical shared channels that need to be scheduled on multiple cells, the network device sends a DCI to the terminal. The DCI is a single DCI, which indicates the time domain resource allocation information and frequency domain resource allocation information of the scheduled M physical shared channels. At least one cell (for example, the first cell) among the multiple cells has multiple physical shared channels jointly scheduled by the DCI. Among them, the multiple cells can correspond to one SCS, that is, the SCS of the multiple cells is the same; or, the multiple cells can also correspond to at least two SCSs.
[0078] Before the network device sends the DCI to the terminal, the terminal may send first capability information and second capability information to the network device, where the first capability information is used to indicate that the terminal supports multi-cell scheduling, and the second capability information is used to indicate that the terminal supports scheduling of multiple physical shared channels on the same cell. That is, when the terminal supports multi-cell scheduling and supports scheduling of multiple physical shared channels on the same cell, the network device sends the DCI in S501 to the terminal.
[0079] In a possible implementation, in order to avoid resource conflicts, the following information may be constrained in the communication protocol: the terminal does not expect the same cell to be configured to support multi-cell joint scheduling and repetition transmission of the physical shared channel of the cell.
[0080] The DCI mentioned in S501 is described in detail below. For the convenience of description, the number of cells scheduled by the DCI is denoted as P in the following text, where P is an integer greater than 1.
[0081] The DCI includes one or more of the following three fields: a first field, a second field, and a third field. The following describes the three fields:
[0082] 1. The first field includes a first subfield and a second subfield, the first subfield is applied to N physical shared channels on a first cell, and the second subfield is applied to one physical shared channel on a second cell, and the second cell is one of the multiple cells scheduled by the DCI that is different from the first cell. The first cell is any cell among the P cells that has multiple physical shared channels scheduled by the DCI, and the second cell is any cell among the P cells that has only one physical shared channel scheduled by the DCI.
[0083] It can be understood that the number of subfields in the first field is P, and the subfields in the first field correspond one-to-one to the cells in the P cells, that is, P pieces of information can be configured for the P cells through the P subfields in the first field. The subfields in the first field are applied to all physical shared channels scheduled by the DCI on the cell corresponding to the subfield, that is, the subfields in the first field are used to configure information for the physical shared channels on the cell corresponding to the subfield. In other words, when there are multiple physical shared channels scheduled by the DCI on a cell among the P cells (such as the first cell mentioned in the present application), the subfield corresponding to the cell is used to configure the same information for all physical shared channels scheduled by the DCI on the cell.
[0084] Among them, the first field can be a frequency domain resource allocation (FDRA) field or a modulation and coding scheme (MCS) field. It should be noted that the first field mentioned in the present application can be understood as any one of a certain type of field (for the sake of distinction, it can be called the first type of field), and the DCI can include multiple fields of the first type of field. For example, when the DCI includes an FDRA field and an MCS field, the FDRA field can be called the first field mentioned in the present application, and the MCS field can also be called the first field mentioned in the present application. Similarly, the second field mentioned in the present application can be understood as any one of the second type of fields; the third field mentioned in the present application can be understood as any one of the third type of fields. It should also be noted that in the present application, a field of the first type of field can indicate different information for physical shared channels on different cells, and indicate the same information for different physical shared channels on the same cell. A field of the second type of field can indicate the same information for different physical shared channels. A field of the third type of field can indicate different information for different physical shared channels.
[0085] Exemplarily, DCI 1 is used to schedule cell 1 and cell 2, wherein PDSCH 1 and PDSCH 2 on cell 1 are scheduled by the DCI 1, and PDSCH 3 on cell 2 is scheduled by the DCI 1. The DCI 1 includes an MCS field, and the MCS field includes subfield #1 and subfield #2, subfield #1 is used to indicate the MCS corresponding to cell 1 (i.e., PDSCH 1 and PDSCH 2 on cell 1 correspond to the same MCS), and subfield #2 is used to indicate the MCS corresponding to cell 2 (i.e., the MCS corresponding to PDSCH 3 on cell 2).
[0086] Before the network device sends the DCI to the terminal, the network device may also send second configuration information to the terminal, and the second configuration information is used to configure whether the subfield in the first field is configured with the same information for all physical shared channels scheduled by DCI on the cell corresponding to the subfield. Or it can be understood that the network device can indicate through the second configuration information whether a piece of information configured by the subfield in the first field is applied to all physical shared channels scheduled by DCI on the cell corresponding to the subfield. The second configuration information can be carried in RRC signaling.
[0087] Exemplarily, the cells that need to be jointly scheduled include cell 1 and cell 2. Cell 1 is an FR1 cell, the time slot interval corresponding to cell 1 is usually longer, the channel quality conditions on adjacent time slots may change, and the corresponding MCS requirements may be different; cell 2 is an FR2 cell, the time slot interval corresponding to cell 2 is usually shorter, the channel quality conditions on adjacent time slots are closer, and the corresponding MCS requirements may be the same. In this case, before sending DCI 1 to schedule cell 1 and cell 2, the network device sends second configuration information to the terminal, and the second configuration information indicates subfield #1 in the MCS field corresponding to cell 1, which is used to indicate different MCSs for different physical shared channels on cell 1, that is, subfield #1 of the MCS field in the subsequent DCI 1 carries multiple copies of information indicating MCS, and the multiple copies of information indicating MCS correspond one-to-one to the physical shared channels on cell 1; the second configuration information indicates subfield #2 in the MCS field corresponding to cell 2, which is used to indicate the same MCS for different physical shared channels on cell 2, that is, subfield #2 of the MCS field in the subsequent DCI 1 carries only one copy of information indicating MCS, and this copy of information indicating MCS is applied to all physical shared channels scheduled by DCI 1 on cell 1.
[0088] 2. The second field is applied to the M physical shared channels on the P cells, and the values of the second fields of the M physical shared channels are the same.
[0089] It can be understood that the same information is configured for the M physical shared channels through the second field, that is, the information configured in the second field is applied to the M physical shared channels. It can also be understood that the value of the second field corresponding to the M physical shared channels is the same.
[0090] When the physical shared channel is a PDSCH, the second field may be any one of the following: an identifier for DCI formants field, a bandwidth part (BWP) indication field, a time domain resource assignment (TDRA) field, a virtual physical resource block to physical resource block mapping (VRB-to-PRB mapping) field, a physical resource block (PRB) bundling size indication field, a rate matching indication field, a zero power channel state information reference signal trigger field, a downlink assignment index field, a transmission power control command for scheduled PUCCH (TPC command for scheduled PUCCH) field, a PUCCH resource indication field, a PDSCH-to-HARQ feedback timing indicator field, and a one-shot HARQ feedback information request (One-shot HARQ-ACK) field. request) field, enhanced Type-3 codebook indication field, HARQ-ACK retransmission indication field, transmission configuration indication field, sounding reference signal (SRS) request field, SRS offset indication field, demodulation reference signal sequence initialization indication field or priority indication field.
[0091] When the physical shared channel is PUSCH, the second field can be any one of the following: identifier for DCI formants field, BWP indication field, TDRA field, frequency hopping flag field, downlink assignment index field, SRS request field, SRS offset indication field, channel state information request (CSI) request field, demodulation reference signal sequence initialization indication field or priority index field.
[0092] It should be noted that different physical shared channels in the same cell have different time domain resources. The following is an exemplary description using the second field being the TDRA field as an example.
[0093] In a possible implementation, the TDRA field indicates a first index value (or the value of the TDRA field is the first index value), the first index value indicates a second index value group, the second index value in the second index value group corresponds one-to-one to a cell in a plurality of cells, and the second index value is used to indicate a time domain resource set, the time domain resource set including time domain resources of different physical shared channels on the cell corresponding to the second index value. The time domain resources include one or more of the following information: K 0 The value of the physical shared channel, the starting symbol of the physical shared channel, the number of time domain symbols of the physical shared channel, and the mapping type information. Among them, the starting symbol of the physical shared channel and the number of time domain symbols of the physical shared channel can be indicated by a start and length indicator value (SLIV).
[0094] Exemplarily, the multiple cells scheduled by the DCI include cells 1 to 4, and four physical shared channels may be scheduled by the DCI in each cell. The corresponding relationship between the first index value and the second index value group may be as follows: Figure 6 As shown in Table 1, each first index value corresponds to a second index value group (i.e. Figure 6 1), each second index value group includes 4 second index values (#0, #1, #2 and #3), and the 4 second index values in each second index value group correspond to cells 1 to 4 respectively. The correspondence between the second index value and the time domain resource set can be as follows Figure 6 As shown in Table 2, each second index value indicates a time domain resource set (i.e. Figure 6 The time domain resource set of each row includes the time domain resources of the physical shared channels scheduled on the cell, and the number of columns of the physical shared channels in Table 2 is the number of physical shared channels that can be scheduled on a cell. In this case, if the TDRA field in the DCI indicates that the first index value is 1, the multiple second index values included in the second index value group #1 are determined according to the first index value: the second index value of cell 1 is 2, the second index value of cell 2 is 2, the second index value of cell 3 is 3, and the second index value of cell 4 is 3. The following is an example of determining the time domain resources of cell 1 according to the second index value of cell 1. This method can be used to determine the time domain resources of the corresponding cells according to the second index values of other cells. The second index value corresponding to cell 1 is 2, which indicates that the time domain resource set #2 corresponding to cell 1 includes: the time domain resources corresponding to the physical shared channel 1 on cell 1 are [K0 21, SLIV 21 、mappingType 21 ], the time domain resource corresponding to the physical shared channel 2 on cell 1 is [K0 22 , SLIV 22 、mappingType 22 ], the time domain resource corresponding to the physical shared channel 3 on cell 1 is [K0 23 , SLIV 23 、mappingType 23 ], the time domain resource corresponding to the physical shared channel 4 on cell 1 is [K0 24 , SLIV 24 、mappingType 24 ].
[0095] It should be noted that the number of time domain resources included in the time domain resource set corresponding to the second index value is one or more. For example, when the DCI schedules multiple physical shared channels in the aforementioned first cell and one physical shared channel on the second cell, and the second index value #1 corresponding to the first cell and the second index value #2 corresponding to the second cell are determined according to the TDRA field in the DCI, the second index value #1 indicates a time domain resource set, and the time domain resource set includes the time domain resources of multiple physical shared channels scheduled by the DCI in the first cell, and the second index value #2 indicates a time domain resource set, and the time domain resource is the time domain resource of the physical shared channel scheduled by the DCI on the second cell.
[0096] Before the network device sends the DCI to the terminal, the network device may also send third configuration information to the terminal, where the third configuration information is used to configure the correspondence between the first index value and the second index value group, and the correspondence between the second index value and the time domain resource set. The third configuration information may be carried in the RRC signaling.
[0097] It is understandable that the third configuration information may also implicitly indicate the maximum number of physical shared channels that can be jointly scheduled on the cell. When the actual scheduling is performed through DCI later, the actual number of physical shared channels scheduled by the DCI may be less than or equal to the maximum number. Figure 6 The correspondence between the second index value and the time domain resource set shown in Table 2, in Table 2, the time domain resource corresponding to the physical shared channel 3 in the time domain resource set #1 is empty. In this case, the third configuration information implicitly indicates that the maximum number of physical shared channels that can be scheduled on the cell is 4. In the subsequent actual scheduling, if the TDRA field indicates that the time domain resource set of the cell is the time domain resource set #1, the actual number of physical shared channels scheduled by the DCI on the cell is 3, that is, the physical shared channel 3 on the cell is not scheduled.
[0098] It should be noted that the joint scheduling of multiple physical shared channels transmitted in consecutive time slots is supported on the same cell, and / or the joint scheduling of multiple physical shared channels transmitted in non-continuous time slots is supported on the same cell. When the third configuration information indicates that a physical shared channel on the cell is not actually scheduled, in the DCI group bit, the position of the TDRA field is before the position of the FDRA field.
[0099] Before the network device sends DCI to the terminal, the network device may also send first configuration information to the terminal, where the first configuration information is used to indicate the maximum number of physical shared channels that can be jointly scheduled by DCI on each cell. When the actual scheduling is subsequently performed through DCI, the actual number of physical shared channels scheduled by the DCI may be less than or equal to the maximum number. Optionally, the maximum number of PDSCHs that can be jointly scheduled by DCI on each cell and the maximum number of PUSCHs that can be jointly scheduled by DCI on each cell may be indicated by the same first configuration information or by different first configuration information. It should be noted that the first to third configuration information mentioned in the present application may be carried in the same RRC message or in different RRC messages.
[0100] Among them, the maximum number of physical shared channels that can be jointly scheduled by DCI on each cell can be a predefined value, and the predefined value can be adjusted according to the specific application scenario, and the specific value is not limited in this application. For example, the predefined maximum number of physical shared channels that can be jointly scheduled by DCI on each cell is 8. Alternatively, the maximum number can also be determined according to the SCS of each cell; in one possible implementation, the larger the SCS of the cell, the larger the maximum number of physical shared channels that can be jointly scheduled on the cell; for example, the maximum number of physical shared channels that can be jointly scheduled by DCI on a cell with an SCS of 30kHz is 2, the maximum number of physical shared channels that can be jointly scheduled by DCI on a cell with an SCS of 60kHz is 4, and the maximum number of physical shared channels that can be jointly scheduled by DCI on a cell with an SCS of 120kHz is 8. Alternatively, the maximum number can also be determined based on the third capability information of the terminal, where the third capability information indicates that the terminal supports the maximum number of physical shared channels that can be jointly scheduled by DCI on the same cell; that is, before the network device sends DCI to the terminal, the terminal sends the third capability information to the network device, and the third capability information can be carried in the same message as the aforementioned first capability information and second capability information, or can be carried in different messages.
[0101] 3. The third field includes M subfields, and the M subfields are respectively applied to M physical shared channels.
[0102] It can be understood that the subfields in the third field correspond to the M physical shared channels one by one, that is, M pieces of information can be configured for the M physical shared channels through the M subfields in the third field.
[0103] The third field may be a redundancy version (RV) indication field, a new data indication (NDI) field or a HARQ process number (HARQ process number) field.
[0104] For example, the third field is a HARQ process number field, and the HARQ process number of a physical shared channel is indicated by 4 bits, so the third field needs 4M bits to indicate the HARQ process numbers of the M physical shared channels.
[0105] S502: The terminal and the network device transmit the M physical shared channels.
[0106] When the physical shared channel is PUSCH, the terminal sends M PUSCHs scheduled by the DCI to the network device; accordingly, the network device receives the M PUSCHs scheduled by the DCI from the terminal. When the physical shared channel is PDSCH, the network device sends M PDSCHs scheduled by the DCI to the terminal; accordingly, the terminal receives the M PDSCHs scheduled by the DCI from the network device.
[0107] In the case where the physical shared channel is PDSCH, after the terminal receives M PDSCHs from the network device, the terminal sends HARQ feedback information to the network device. The number of bits of the HARQ feedback information is the number of TBs carried in the maximum number of PDSCHs that can be scheduled on the P cells. Or it can be understood that the sum of the number of TBs carried in the maximum number of PDSCHs that can be jointly scheduled on each of the P cells is the number of bits of the HARQ feedback information.
[0108] It should be noted that the number of TBs carried by the PDSCH in this application is one or more; and the number of TBs carried by each PDSCH in this application may be different or the same. In the following text, only for the convenience of description, each PDSCH carrying 1 TB is used as an example for schematic illustration, which should not be regarded as a specific limitation of this application.
[0109] Example 1: The network device sends an RRC message to the terminal, such as Figure 7As shown, the RRC message configures the cell set scheduled by DCI 1 to include cell 0 to cell 2, and the cell set scheduled by DCI 2 to include cell 3 to cell 5; wherein, the maximum number of PDSCHs that can be jointly scheduled on CC0 and CC 3 is 1, and the maximum number of PDSCHs that can be jointly scheduled on CC 1, CC 2, CC 4 and CC 5 is 4, and each PDSCH is configured with only 1 TB. The number of bits of the HARQ feedback information corresponding to DCI 1 is the number of TBs of the maximum number of PDSCHs that can be scheduled on cell 0 to cell 2 (i.e., 9 TBs), i.e., 9 bits; the number of bits of the HARQ feedback information corresponding to DCI 2 is the number of TBs of the maximum number of PDSCHs that can be scheduled on cell 3 to cell 5 (i.e., 9 TBs), i.e., 9 bits.
[0110] In the actual scheduling process, the actual number of PDSCHs actually scheduled on the cell is less than or equal to the maximum number of PDSCHs that can be scheduled and configured on the cell. Based on this, the HARQ feedback information can be designed to include multiple groups of bit groups, the bit groups correspond one-to-one to the cells in the multiple cells, the bits in the bit groups correspond one-to-one to the TBs of the physical downlink shared channels on the cells corresponding to the bit groups, and the bits in the bit groups are used to indicate whether the TB corresponding to the bit is successfully received. When a bit indicates that the TB corresponding to the bit is not successfully received, the PDSCH carrying the TB may be a transmission failure or may not be scheduled.
[0111] Following the above example 1, the monitoring timing configuration of cell 0 is the same as the monitoring timing configuration of cell 3. The terminal receives DCI 1 at the monitoring timing of cell 0, and receives DCI 2 at the monitoring timing of cell 3; and Figure 8 In the actual scheduling process shown in Figure 8a, DCI 1 actually schedules 7 PDSCHs in cells 0 to 2, and DCI 2 actually schedules 6 PDSCHs in cells 3 to 5. The C-DAI in DCI 1 is 1 and the T-DAI is 2; the C-DAI in DCI 2 is 2 and the T-DAI is 2. Based on DCI 1 and DCI 2, the terminal receives the 13 PDSCHs and generates the following information for the received PDSCHs: Figure 8 8b shows the HAQR feedback information. The information bits corresponding to each cell in the HARQ bit information (ie the bit group mentioned in the present application) are used to indicate whether the TB carried on the PDSCH in each cell is successfully received.
[0112] It should be noted that when the HARQ codebook includes both the HARQ feedback information corresponding to the DCI for scheduling a single cell and the HARQ feedback information corresponding to the DCI for scheduling multiple cells, the HARQ codebook includes a first-level sub-codebook and a second-level sub-codebook, the first-level sub-codebook is the HARQ feedback information corresponding to the DCI for scheduling a single cell, and the second-level sub-codebook is the HARQ feedback information corresponding to the DCI for scheduling multiple cells. The two sub-codebooks are cascaded, and the second-level sub-codebook is located behind the first-level sub-codebook. The HARQ feedback information corresponding to the DCI in this application is located in the second-level sub-codebook. In the second-level sub-codebook, the order of the HARQ feedback information corresponding to multiple DCIs is determined according to the C-DAI indication carried in each DCI; for example, Figure 8 In the HARQ feedback information, the C-DAI of DCI 1 is smaller than the C-DAI of DCI 2. The PDSCH scheduled by DCI 1 is fed back first, and the PDSCH scheduled by DCI 2 is fed back first. In the second-level sub-codebook, the feedback order of multiple PDSCHs scheduled by the same DCI is determined according to the order of the time units used by the network device to send the PDSCH; for example, Figure 8 The PDSCH sent in the time slot earlier (ie, located closer to the left) is fed back first, and the PDSCH sent in the time slot later (ie, located closer to the right) is fed back later.
[0113] In a possible implementation, in order to avoid PDSCH processing process crossover and reduce the complexity of decoding PDSCH, the communication protocol can also perform scheduling constraints, constraining the earliest time unit (e.g., time slot) for sending PDSCH scheduled by the first DCI to be no earlier than the latest time unit for sending PDSCH scheduled by the second DCI, wherein the time unit for sending the first DCI is later than the time unit for sending the second DCI. This implementation is conducive to avoiding out-of-order scheduling of PDSCH.
[0114] In summary, in the scenario where physical shared channels on multiple cells are scheduled by one DCI, one or more physical shared channels can be scheduled by the DCI on each cell, which is conducive to improving the scheduling efficiency of physical shared channels scheduled by DCI, compared with the method where only one physical shared channel can be scheduled by DCI on the same cell. For example, in the scenario where cell 1 and cell 2 can be jointly scheduled by DCI, physical shared channels 1 and 2 on cell 1 need to be scheduled, and physical shared channels 3 and 4 on cell 2 need to be scheduled, if only one physical shared channel can be scheduled by DCI on the same cell, at least 2 DCIs are required; while through Figure 5 The provided communication method can schedule physical shared channels 1 to 4 through one DCI, thereby improving the scheduling efficiency of DCI scheduling physical shared channels.
[0115] It is understandable that in order to implement the functions in the above embodiments, the terminal includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the units and method steps of each example described in the embodiments disclosed in this application, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or a computer software transceiver unit driving the hardware depends on the specific application scenario and design constraints of the technical solution.
[0116] Fig. 9 and Fig.10 The following is a schematic diagram of the structure of possible communication devices provided in the embodiments of the present application. These communication devices can be used to implement the functions of the terminal in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments. In the embodiments of the present application, the communication device can be as follows: Figure 1 The terminal 120 shown may also be a module (such as a chip) applied to the terminal, or the communication device may be Figure 1 The network device 110 shown may also be a module (such as a chip) applied to a network device.
[0117] like Fig. 9 As shown, the communication device 900 includes a processing unit 910 and a transceiver unit 920. The communication device 900 is used to implement the above Figure 5 The functions of the terminal in the method embodiment shown in FIG.
[0118] When the communication device 900 is used to implement Figure 5 The functions of the terminal in the method embodiment shown are: a transceiver unit 920, used to receive downlink control information DCI from a network device, where the DCI is used to schedule M physical shared channels on multiple cells, where the first cell is one of the multiple cells, and the first cell includes N physical shared channels scheduled by DCI, where N is an integer greater than 1, and M is an integer greater than N; the transceiver unit 920 is also used to transmit M physical shared channels based on DCI.
[0119] In one possible implementation, the DCI includes a first field, which includes a first subfield and a second subfield, the first subfield is applied to N physical shared channels on a first cell, and the second subfield is applied to a physical shared channel on a second cell, which is one of multiple cells different from the first cell.
[0120] In a possible implementation, the DCI includes a second field, and the value of the second field of the M physical shared channels is the same.
[0121] In one possible implementation, the second field is a time domain resource allocation TDRA field, which is used to indicate a first index value, and the first index value is used to indicate a second index value group. The second index value in the second index value group corresponds one-to-one to a cell in a plurality of cells, and the second index value is used to indicate a time domain resource set, which includes time domain resources of different physical shared channels on the cell corresponding to the second index value.
[0122] In a possible implementation, the DCI includes a third field, where the third field includes M subfields, and the M subfields are respectively applied to M physical shared channels.
[0123] In a possible implementation, the physical shared channel is a physical downlink shared channel, and the transceiver unit 920 is also used to send HARQ feedback information to the network device, and the number of bits of the HARQ feedback information is the number of transport blocks carried in the maximum number of physical downlink shared channels that can be scheduled in the multiple cells.
[0124] In a possible implementation, the HARQ feedback information includes multiple groups of bit groups, the bit groups in the multiple groups of bit groups correspond one-to-one to cells in multiple cells, the bits in the bit groups correspond one-to-one to the transmission blocks of the physical downlink shared channel on the cells corresponding to the bit groups, and the bits in the bit groups are used to indicate whether the transmission block corresponding to the bits is successfully received.
[0125] In a possible implementation, the transceiver unit 920 is further used to send first capability information and second capability information to the network device, where the first capability information is used to indicate that the terminal supports multi-cell scheduling, and the second capability information is used to indicate that the terminal supports multiple physical shared channel scheduling on the same cell.
[0126] In a possible implementation, the transceiver unit 920 is further configured to receive first configuration information from a network device, where the first configuration information is used to configure a maximum number of physical shared channels that can be scheduled on each of the multiple cells.
[0127] For more detailed description of the transceiver unit 920 and the processing unit 910, please refer to Figure 5 The relevant description of the terminal in the method embodiment is shown.
[0128] like Fig. 9 As shown, the communication device 900 includes a processing unit 910 and a transceiver unit 920. The communication device 900 is used to implement the above Figure 5 The functions of the network device in the method embodiment shown in FIG.
[0129] When the communication device 900 is used to implement Figure 5The functions of the network device in the method embodiment shown are: a transceiver unit 920, used to send downlink control information DCI to the terminal, where the DCI is used to schedule M physical shared channels on multiple cells, where the first cell is one of the multiple cells, and the first cell includes N physical shared channels scheduled by DCI, where N is an integer greater than 1, and M is an integer greater than N; the transceiver unit 920 is also used to transmit M physical shared channels based on DCI.
[0130] In one possible implementation, the DCI includes a first field, which includes a first subfield and a second subfield, the first subfield is applied to N physical shared channels on a first cell, and the second subfield is applied to a physical shared channel on a second cell, which is one of multiple cells different from the first cell.
[0131] In a possible implementation, the DCI includes a second field, and the value of the second field of the M physical shared channels is the same.
[0132] In one possible implementation, the second field is a time domain resource allocation TDRA field, which is used to indicate a first index value, and the first index value is used to indicate a second index value group. The second index value in the second index value group corresponds one-to-one to a cell in a plurality of cells, and the second index value is used to indicate a time domain resource set, which includes time domain resources of different physical shared channels on the cell corresponding to the second index value.
[0133] In a possible implementation, the DCI includes a third field, where the third field includes M subfields, and the M subfields are respectively applied to M physical shared channels.
[0134] In a possible implementation, the physical shared channel is a physical downlink shared channel, and the transceiver unit 920 is also used to receive HARQ feedback information from the terminal, and the number of bits of the HARQ feedback information is the number of transport blocks carried in the maximum number of physical downlink shared channels that can be scheduled in the multiple cells.
[0135] In a possible implementation, the HARQ feedback information includes multiple groups of bit groups, the bit groups in the multiple groups of bit groups correspond one-to-one to cells in multiple cells, the bits in the bit groups correspond one-to-one to the transmission blocks of the physical downlink shared channel on the cells corresponding to the bit groups, and the bits in the bit groups are used to indicate whether the transmission block corresponding to the bits is successfully received.
[0136] In a possible implementation, the transceiver unit 920 is further used to receive first capability information and second capability information from the terminal, the first capability information is used to indicate that the terminal supports multi-cell scheduling, and the second capability information is used to indicate that the terminal supports multiple physical shared channel scheduling on the same cell.
[0137] In a possible implementation, the transceiver unit 920 is further configured to send first configuration information to the terminal, where the first configuration information is used to configure a maximum number of physical shared channels that can be scheduled in each of the multiple cells.
[0138] For more detailed description of the transceiver unit 920 and the processing unit 910, please refer to Figure 5 The relevant description of the network device in the method embodiment is shown.
[0139] like Fig.10 As shown, the communication device 1000 includes a processor 1010 and an interface circuit 1020. The processor 1010 and the interface circuit 1020 are coupled to each other. It is understood that the interface circuit 1020 can be a transceiver or an input-output interface. Optionally, the communication device 1000 may also include a memory 1030 for storing instructions executed by the processor 1010 or storing input data required by the processor 1010 to execute instructions or storing data generated after the processor 1010 executes instructions.
[0140] When the communication device 1000 is used to implement Figure 5 When the method is shown, the processor 1010 is used to implement the functions of the processing unit 910, and the interface circuit 1020 is used to implement the functions of the transceiver unit 920.
[0141] When the above-mentioned communication device is a chip applied to a terminal, the terminal chip implements the functions of the terminal in the above-mentioned method embodiment. The terminal chip receives information from the base station, which can be understood as the information is first received by other modules in the terminal (such as a radio frequency module or an antenna), and then sent to the terminal chip by these modules. The terminal chip sends information to the base station, which can be understood as the information is first sent to other modules in the terminal (such as a radio frequency module or an antenna), and then sent to the base station by these modules.
[0142] When the above-mentioned communication device is a chip applied to a network device, the network device chip implements the function of the network device in the above-mentioned method embodiment. The network device chip receives information from the terminal, which can be understood as the information is first received by other modules in the network device (such as a radio frequency module or an antenna), and then sent to the network device chip by these modules. The network device chip sends information to the terminal, which can be understood as the information is sent to other modules in the network device (such as a radio frequency module or an antenna), and then sent to the terminal by these modules.
[0143] In the present application, when entity A sends information to entity B, it can be that A sends it directly to B, or that A sends it to B indirectly through other entities. Similarly, when entity B receives information from entity A, it can be that entity B directly receives the information sent by entity A, or that entity B indirectly receives the information sent by entity A through other entities. Entities A and B here can be RAN nodes or terminals, or modules inside the RAN nodes or terminals. The sending and receiving of information can be information interaction between a RAN node and a terminal, for example, information interaction between a base station and a terminal; the sending and receiving of information can also be information interaction between two RAN nodes, for example, information interaction between a CU and a DU; the sending and receiving of information can also be information interaction between different modules inside a device, for example, information interaction between a terminal chip and other modules of the terminal, or information interaction between a base station chip and other modules in the base station.
[0144] It is understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.
[0145] The method steps in the embodiments of the present application can be implemented in hardware or in software instructions that can be executed by a processor. The software instructions can be composed of corresponding software modules, and the software modules can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, register, hard disk, mobile hard disk, CD-ROM or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. The storage medium can also be a component of the processor. The processor and the storage medium can be located in an ASIC. In addition, the ASIC can be located in a base station or a terminal. The processor and the storage medium can also be present in a base station or a terminal as discrete components.
[0146] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When a computer program or instruction is loaded and executed on a computer, the process or function of the embodiment of the present application is executed in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device or other programmable device. The computer program or instruction can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer program or instruction can be transmitted from one website site, computer, server or data center to another website site, computer, server or data center by wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server, data center, etc. that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, a hard disk, or a tape; it can also be an optical medium, such as a digital video disc; it can also be a semiconductor medium, such as a solid-state hard disk. The computer-readable storage medium may be a volatile or nonvolatile storage medium, or may include both volatile and nonvolatile types of storage media.
[0147] In the various embodiments of the present application, unless otherwise specified or provided for in any logical conflict, the terms and / or descriptions between the different embodiments are consistent and may be referenced to each other, and the technical features in the different embodiments may be combined to form new embodiments according to their inherent logical relationships.
[0148] In the present application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. In the text description of the present application, the character " / " generally indicates that the previous and next associated objects are in an "or" relationship; in the formula of the present application, the character " / " indicates that the previous and next associated objects are in a "division" relationship. "Including at least one of A, B and C" can mean: including A; including B; including C; including A and B; including A and C; including B and C; including A, B and C.
[0149] It is understood that the various numbers involved in the embodiments of the present application are only for the convenience of description and are not used to limit the scope of the embodiments of the present application. The size of the sequence number of the above-mentioned processes does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic.
Claims
1. A communication method, characterized in that: The method comprises: receiving downlink control information DCI from a network device, where the DCI is used to schedule M physical shared channels on multiple cells, where a first cell is one of the multiple cells, where N physical shared channels on the first cell are scheduled by the DCI, where N is an integer greater than 1, and M is an integer greater than N; The M physical shared channels are transmitted based on the DCI.
2. The method according to claim 1, characterized in that: The DCI includes a first field, the first field includes a first subfield and a second subfield, the first subfield is applied to N physical shared channels on the first cell, the second subfield is applied to a physical shared channel on a second cell, and the second cell is one of the multiple cells different from the first cell.
3. The method according to claim 1 or 2, characterized in that: The DCI includes a second field, and the second field of the M physical shared channels has the same value.
4. The method according to claim 3, characterized in that: The second field is a time domain resource allocation TDRA field, the TDRA field is used to indicate a first index value, the first index value is used to indicate a second index value group, the second index values in the second index value group correspond one-to-one to a cell in the multiple cells, the second index value is used to indicate a time domain resource set, and the time domain resource set includes time domain resources of different physical shared channels on the cell corresponding to the second index value.
5. The method according to any one of claims 1 to 4, characterized in that: The DCI includes a third field, the third field includes M subfields, and the M subfields are respectively applied to the M physical shared channels.
6. The method according to any one of claims 1 to 5, characterized in that: The physical shared channel is a physical downlink shared channel, and the method further includes: HARQ feedback information is sent to the network device, where the number of bits of the HARQ feedback information is the number of transport blocks carried in the maximum number of physical downlink shared channels that can be scheduled in the multiple cells.
7. The method according to claim 6, characterized in that: The HARQ feedback information includes multiple groups of bit groups, the bit groups in the multiple groups of bit groups correspond one-to-one to the cells in the multiple cells, the bits in the bit groups correspond one-to-one to the transmission blocks of the physical downlink shared channel in the cells corresponding to the bit groups, and the bits in the bit groups are used to indicate whether the transmission blocks corresponding to the bits are successfully received.
8. The method according to any one of claims 1 to 7, characterized in that: The method further comprises: First capability information and second capability information are sent to the network device, where the first capability information is used to indicate that the terminal supports multi-cell scheduling, and the second capability information is used to indicate that the terminal supports multiple physical shared channel scheduling on the same cell.
9. The method according to any one of claims 1 to 8, characterized in that: The method further comprises: First configuration information is received from the network device, where the first configuration information is used to configure a maximum number of physical shared channels that can be scheduled on each of the multiple cells.
10. A communication method, characterized in that: The method comprises: Sending downlink control information DCI to a terminal, where the DCI is used to schedule M physical shared channels on multiple cells, where a first cell is one of the multiple cells, and where N physical shared channels on the first cell are scheduled by the DCI, where N is an integer greater than 1, and M is an integer greater than N; The M physical shared channels are transmitted based on the DCI.
11. The method according to claim 10, characterized in that: The DCI includes a first field, the first field includes a first subfield and a second subfield, the first subfield is applied to N physical shared channels on the first cell, the second subfield is applied to a physical shared channel on a second cell, and the second cell is one of the multiple cells different from the first cell.
12. The method according to claim 10 or 11, characterized in that: The DCI includes a second field, and the second field of the M physical shared channels has the same value.
13. The method according to claim 12, characterized in that: The second field is a time domain resource allocation TDRA field, the TDRA field is used to indicate a first index value, the first index value is used to indicate a second index value group, the second index values in the second index value group correspond one-to-one to a cell in the multiple cells, the second index value is used to indicate a time domain resource set, and the time domain resource set includes time domain resources of different physical shared channels on the cell corresponding to the second index value.
14. The method according to any one of claims 10 to 13, characterized in that: The DCI includes a third field, the third field includes M subfields, and the M subfields are respectively applied to the M physical shared channels.
15. The method according to any one of claims 10 to 14, characterized in that: The physical shared channel is a physical downlink shared channel, and the method further includes: HARQ feedback information is received from the terminal, where the number of bits of the HARQ feedback information is the number of transport blocks carried in the maximum number of physical downlink shared channels that can be scheduled in the multiple cells.
16. The method according to claim 15, characterized in that: The HARQ feedback information includes multiple groups of bit groups, the bit groups in the multiple groups of bit groups correspond one-to-one to the cells in the multiple cells, the bits in the bit groups correspond one-to-one to the transmission blocks of the physical downlink shared channel in the cells corresponding to the bit groups, and the bits in the bit groups are used to indicate whether the transmission blocks corresponding to the bits are successfully received.
17. The method according to any one of claims 10 to 16, characterized in that: The method further comprises: First capability information and second capability information are received from the terminal, wherein the first capability information is used to indicate that the terminal supports multi-cell scheduling, and the second capability information is used to indicate that the terminal supports multiple physical shared channel scheduling on the same cell.
18. The method according to any one of claims 10 to 17, characterized in that: The method further comprises: First configuration information is sent to the terminal, where the first configuration information is used to configure a maximum number of physical shared channels that can be scheduled on each of the multiple cells.
19. A communication device, characterized in that: The method comprises a module for executing the method according to any one of claims 1 to 9, or comprises a module for executing the method according to any one of claims 10 to 18.
20. A communication device, characterized in that: It includes a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor or send signals from the processor to other communication devices outside the communication device, and the processor is used to implement the method as described in any one of claims 1 to 9 through a logic circuit or by executing code instructions, or the processor is used to implement the method as described in any one of claims 10 to 18 through a logic circuit or by executing code instructions.
21. A computer-readable storage medium, characterized in that: The storage medium stores a computer program or instruction. When the computer program or instruction is executed by the communication device, the communication device implements the method as described in any one of claims 1 to 9, or implements the method as described in any one of claims 10 to 18.
22. A computer program product, characterized in that The computer program product includes a computer program or instructions. When the computer program or instructions are executed by a communication device, the communication device implements the method according to any one of claims 1 to 9, or implements the method according to any one of claims 10 to 18.
Citation Information
Cited By
Communication method and communication apparatus
EP4790936A1
Communication method and communication apparatus
WO2025092837A1