CN114885431A

CN114885431A - Communication method and device

Info

Publication number: CN114885431A
Application number: CN202210342432.5A
Authority: CN
Inventors: 黄秀璇; 李新县; 丁梦颖; 彭金磷
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2022-03-31
Filing date: 2022-03-31
Publication date: 2022-08-09
Also published as: CN116939850A

Abstract

A communication method and device, the method includes: the base station sends a first DCI for scheduling a plurality of CCs to the terminal, wherein the first DCI at least comprises a first field shared by the plurality of CCs. By adopting the method and the device, information does not need to be configured independently for each CC in the first field of the first DCI, so that the load overhead of the first DCI is reduced.

Description

Communication method and device

Technical Field

The embodiment of the application relates to the technical field of communication, in particular to a communication method and device.

Background

Carrier Aggregation (CA) is a technology that aggregates 2 or more carrier elements (CCs) together to support a larger transmission bandwidth. Each CC corresponds to an independent cell, and 1 CC may be generally identical to one cell. To efficiently utilize the scattered spectrum, CA supports aggregation between different CCs. For example, aggregation between CCs within the same or different bandwidths; aggregation between adjacent or non-adjacent CCs within the same frequency band; aggregation among CCs within different frequency bands, etc. How to design Downlink Control Information (DCI) so that the DCI schedules data transmission in multiple CCs to implement carrier aggregation between different CCs is a problem worthy of study.

Disclosure of Invention

The application provides a communication method and device, which can realize that data transmission in a plurality of CCs is scheduled by using first DCI, and carrier aggregation of the plurality of CCs is realized.

In a first aspect, a communication method is provided, where the method is executed as a network device, or configured as a component (processor, chip or other) in the network device, and the method includes: sending first downlink control information DCI to a terminal; the first DCI is used for scheduling transmission of multiple carrier elements (CCs), and the first DCI includes a first field, where information carried in the first field is shared by the multiple CCs; when the information k0 carried in the first field is configured to be shared by the plurality of CCs, the k0 is used to indicate an offset value of a first reference position and a time unit corresponding to a Physical Downlink Shared Channel (PDSCH), and the first reference position is determined according to the time unit corresponding to the first DCI.

By the method, when the first DCI schedules the plurality of CCs, the first DCI at least comprises the first field which is shared by the plurality of CCs, and independent information does not need to be configured for each CC in the first field, so that the load overhead of the first DCI is reduced. In the above design, a time domain resource allocation field may be included in the first field, and when the information k0 carried in the time domain resource allocation field is configured to be shared by multiple CCs, the design of k0 is taken as a detailed description, so that a time unit corresponding to a PDSCH in multiple CCs may be indicated by using one value of k0, and the load overhead of the first DCI is saved.

In one design, the first DCI further includes a second field, and information carried in the second field is configured independently for each of the plurality of CCs.

In one design, further comprising: determining information carried by a corresponding field in the first DCI according to the configuration state of the field in the first DCI; wherein the configuration state of the fields in the first DCI includes sharing, flexibility and independence, and for one field of the first DCI: when the configuration state of the field is shared, the information carried in the field is shared by the plurality of CCs scheduled by the first DCI; or, when the configuration state of the field is flexible, the information carried in the field is shared by the multiple CCs scheduled by the first DCI, or the information carried in the field includes information configured independently for each CC; or, when the configuration state of the field is independent, the information carried in the field includes information configured independently for each CC.

With the above design, the field configuration state for each field in the first DCI may be protocol-specified or preset. When the configuration state of a field is shared, the information carried by the field may be shared by multiple CCs. Or, when the configuration state of a field is independent, the information carried in the field is configured independently for each CC. Alternatively, when the configuration state of a field is flexible, the information carried in the field may be shared by multiple CCs or configured independently for each CC. By adopting the method, the base station can determine each field in the first DCI to be shared or independent according to the field configuration state specified by the protocol, and the implementation of the base station is easy.

In one design, the configuration state is a shared field that includes at least one of: DCI format indication, carrier indication, downlink allocation indication, Transmission Power Control (TPC) command scheduled by a Physical Uplink Control Channel (PUCCH), PUCCH resource indication, transmission configuration indication, or Cyclic Redundancy Check (CRC).

In one design, when the first field carries information k ₁ Configured to be shared by the plurality of CCs, the k ₁ An offset value indicating a second reference position and a time unit corresponding to HARQ, wherein the second reference position is determined according to the time unit corresponding to the PDSCH in at least one CC of the plurality of CCs.

Through the method, the first field comprises the PDSCH-to-HARQ feedback time indication field, when the information k1 carried in the PDSCH-to-HARQ feedback time indication field can be shared by a plurality of CCs, the time unit for transmitting HARQ on the plurality of CCs can be indicated by carrying one k1 value, and the load overhead of the first DCI is saved.

In one design, the plurality of CCs scheduled by the first DCI include at least a first CC and a second CC, and the first DCI is sent to the terminal on the first CC, further comprising: transmitting a second DCI to the terminal on the first CC; the first DCI is a DCI supporting multi-carrier joint scheduling, and the second DCI is a DCI supporting single-carrier scheduling.

With the above method, in addition to the first DCI, the second DCI may be transmitted on the first CC. The first DCI may be a DCI supporting multi-carrier scheduling, and the second DCI may be a single DCI, for example. The second DCI may be a DCI supporting single carrier scheduling, for example, the first DCI is a single DCI, or a legacy DCI.

In one design, the first DCI and the second DCI are transmitted in a same time unit when a subcarrier spacing, SCS, of the first CC is smaller than a SCS, of the second CC.

In one design, when the SCS of the first CC is greater than the SCS of the second CC, the first DCI is sent in N time units as a cycle, and the second DCI is sent in time units during different cycles of the first DCI, where a value of N is determined according to the SCS of the first CC and the SCS of the second CC.

In one design, when the first DCI schedules multiple data transmissions on one CC, information carried in any one of the following fields included in the first DCI is shared for the multiple data transmissions of the one CC: frequency domain resource allocation, modulation coding scheme MCS of the transport block TB, new data indication of the TB, or redundancy version RV of the TB.

By the above method, the first DCI may schedule multiple data transmissions on the same CC, where the data transmission may be a PDSCH or a PUSCH, and is not limited. In the scheme, through further design, multiple data transmissions of the same CC can further share fields in the DCI, and the load overhead of the first DCI is reduced.

In one design, when the k0 is a set of k0, the set of k0 includes a plurality of k0 therein, the set of k0 is shared by the plurality of CCs scheduled by the first DCI, and the plurality of k0 included in the set of k0 is independently configured for the plurality of data transmissions scheduled by the first DCI in one CC.

In a second aspect, a communication method is provided, where an execution subject of the method is a terminal or a component (processor, chip, or other device) configured in the terminal, and the method includes: receiving first Downlink Control Information (DCI) from network equipment; the first DCI is used for scheduling transmission of multiple carrier elements (CCs), and the first DCI includes a first field, where information carried in the first field is shared by the multiple CCs; when the information k0 carried in the first field is configured to be shared by the plurality of CCs, the k0 is used to indicate an offset value of a first reference position and a time unit corresponding to a Physical Downlink Shared Channel (PDSCH), and the first reference position is determined according to the time unit corresponding to the first DCI.

By the method, the first DCI can schedule data transmission in the multiple CCs, and the first field in the DCI can be designed to be shared by the multiple CCs without independently configuring corresponding information for each CC, so that the load overhead of the first DCI is reduced.

In one design, the configuration state of the fields in the first DCI includes shared, flexible, and independent, and at least one of the first field and the second field is determined according to the configuration state of the fields in the first DCI specified by the protocol.

In one design, the plurality of CCs scheduled by the first DCI include a first CC and a second CC, a subcarrier spacing SCS of the first CC is smaller than a SCS of the second CC, the first reference location is a time unit corresponding to the first DCI in the second CC, and the k0 is used to indicate an offset value of the time unit corresponding to the first DCI and a time unit corresponding to the PDSCH in the second CC, and the method further includes: and determining an offset value of a time unit corresponding to the first DCI and a time unit corresponding to the PDSCH in the first CC according to the SCS of the first CC, the SCS of the second CC and the k 0.

In one design, the determining, according to the SCS of the first CC, the SCS of the second CC, and the k0, an offset value of a time unit corresponding to the first DCI and a time unit corresponding to the PDSCH in the first CC may satisfy the following condition:

wherein, floor represents a rounding-down operation, k0 represents an offset value between a time unit corresponding to the first DCI and a time unit corresponding to the PDSCH in the second CC, u1 represents an index of an SCS corresponding to the second CC, and u2 represents an index of an SCS corresponding to the first CC.

In one design, the plurality of CCs scheduled by the first DCI include a first CC and a second CC, the SCS of the first CC is smaller than the SCS of the second CC, the first reference location is an offset value of a time unit corresponding to the first DCI and a time unit corresponding to a PDSCH in the first CC, the k0 is used to indicate an offset value of a time unit corresponding to the first DCI and a time unit corresponding to a PDSCH in the first CC, the method further includes:

determining a time unit corresponding to the PDSCH in the second CC according to the time unit corresponding to the PDSCH in the first CC; or receiving indication information from the network device, where the indication information is used to indicate an offset value of a time unit corresponding to the first DCI and a time unit corresponding to the PDSCH in the second CC; or determining a time unit corresponding to the PDSCH in the second CC according to a third field in the first DCI, where the third field is used to indicate an offset value between the time unit corresponding to the PDSCH in the first CC and the time unit corresponding to the PDSCH in the second CC.

In one design, when the place isInformation k carried in the first field ₁ Configured to be shared by the plurality of CCs, the k ₁ An offset value indicating a second reference position and a transmission HARQ time unit, the second reference position being determined according to a time unit corresponding to a PDSCH in one of the plurality of CCs, the method further comprising: according to the second reference position and the k ₁ And determining a time unit corresponding to HARQ in the plurality of CCs of the first DCI.

In one design, the plurality of CCs scheduled by the first DCI include at least a first CC on which the first DCI is received from the network device and a second CC, further comprising: receiving, on the first CC, second DCI from the network device; the first DCI is a DCI supporting multi-carrier joint scheduling, and the second DCI is a DCI supporting single-carrier scheduling.

In one design, the first DCI and the second DCI are received in a same time unit when a subcarrier spacing, SCS, of the first CC is smaller than a SCS, of the second CC.

In one design, when the SCS of the first CC is greater than the SCS of the second CC, the first DCI is received in cycles of N time units, and the second DCI is received in time units during different cycles of the first DCI, where a value of N is determined according to the SCS of the first CC and the SCS of the second CC.

In one design, when the first DCI schedules multiple data transmissions on one CC, information carried in any one of the following fields included in the first DCI is shared by the multiple data transmissions of the one CC: frequency domain resource allocation, modulation coding scheme MCS of the transport block TB, new data indication of the TB, or redundancy version RV of the TB.

In a third aspect, a communication device is provided, which is configured to implement the method of the first aspect, and includes corresponding functional modules or units, respectively, configured to implement the steps in the method of the first aspect. The functions can be realized by hardware, and corresponding software can be executed by hardware, and the hardware or the software comprises one or more modules or units corresponding to the functions.

In a fourth aspect, a communications apparatus is provided that includes a processor and a memory. Wherein the memory is used for storing computer programs or instructions, and the processor is coupled with the memory; the computer program or instructions, when executed by a processor, cause the apparatus to perform the method of the first aspect described above.

In a fifth aspect, a communication device is provided, which is adapted to implement the method of the second aspect, and includes corresponding functional modules or units, respectively, adapted to implement the steps in the method of the second aspect. The functions can be realized by hardware, and corresponding software can be executed by hardware, and the hardware or the software comprises one or more modules or units corresponding to the functions.

In a sixth aspect, a communications apparatus is provided that includes a processor and a memory. Wherein the memory is used for storing computer programs or instructions, and the processor is coupled with the memory; the computer program or instructions, when executed by a processor, cause the apparatus to perform the method of the second aspect described above.

In a seventh aspect, a computer-readable storage medium is provided, in which a computer program or instructions are stored, which, when run on a computer, cause the computer to perform the method of the first aspect described above.

In an eighth aspect, a computer-readable storage medium is provided, in which a computer program or instructions are stored, which, when run on a computer, cause the computer to perform the method of the second aspect described above.

In a ninth aspect, there is provided a computer program product comprising a computer program or instructions for causing a computer to perform the method of the first aspect when the computer program or instructions are run on the computer.

In a tenth aspect, there is provided a computer program product comprising a computer program or instructions for causing a computer to perform the method of the second aspect described above when the computer program or instructions are run on the computer.

In an eleventh aspect, there is provided a system comprising the apparatus of the third or fourth aspect, and the apparatus of the fifth or sixth aspect.

Drawings

FIG. 1 is a schematic diagram of a network architecture provided herein;

fig. 2 is a schematic diagram of self-carrier scheduling provided in the present application;

FIG. 3 is a schematic diagram of cross-carrier scheduling provided herein;

FIG. 4 is a schematic diagram of single DCI scheduling provided herein;

FIG. 5 is a flow chart of a communication method provided herein;

FIG. 6 is a schematic diagram of k0 provided herein;

FIGS. 7-9 are schematic diagrams of K0 calculation for different SCS of CC;

FIG. 10 is a schematic representation of k1 provided herein;

fig. 11 to 14 are diagrams illustrating the capability of a terminal to process DCI on a scheduling carrier;

fig. 15 and 16 are schematic diagrams of single DCI scheduling multiple PDSCH/PUSCH on the same carrier;

fig. 17 and 18 are schematic views of the apparatus provided in the present application.

Detailed Description

Fig. 1 is a schematic block diagram of a communication system 1000 to which the present application can be applied. As shown in fig. 1, the communication system includes a radio access network 100 and a core network 200, and optionally, the communication system 1000 may further include an internet 300. The radio access network 100 may include at least one access network device (e.g., 110a and 110b in fig. 1) and may further include at least one terminal (e.g., 120a-120j in fig. 1). The terminal is connected with the access network equipment in a wireless mode, and the access network equipment is connected with the core network in a wireless or wired mode. The core network device and the access network device may be separate physical devices, or the functions of the core network device and the logical functions of the access network device may be integrated on the same physical device, or a physical device may be a physical device in which the functions of a part of the core network device and a part of the access network device are integrated. The terminal and the access network equipment can be connected with each other in a wired or wireless mode. Fig. 1 is a schematic diagram, and the communication system may further include other network devices, such as a wireless relay device and a wireless backhaul device, which are not shown in fig. 1.

The access network device may be a base station (base station), an evolved NodeB (eNodeB), a Transmission Reception Point (TRP), a next generation base station (next generation NodeB, gNB) in a fifth generation (5th generation, 5G) mobile communication system, an access network device in an open radio access network (O-RAN), a next generation base station in a sixth generation (6th generation, 6G) mobile communication system, a base station in a future mobile communication system, or an access node in a wireless fidelity (WiFi) system, etc.; or may be a module or unit that performs a part of the functions of the base station, for example, a Central Unit (CU), a Distributed Unit (DU), a centralized unit control plane (CU-CP) module, or a centralized unit user plane (CU-UP) module. The access network device may be a macro base station (e.g., 110a in fig. 1), a micro base station or an indoor station (e.g., 110b in fig. 1), a relay node or a donor node, and the like. The specific technology and the specific device form adopted by the access network device are not limited in the application.

In this embodiment of the present application, the apparatus for implementing the function of the access network device may be an access network device; or may be a device capable of supporting the access network equipment to implement the function, such as a chip system, a hardware circuit, a software module, or a hardware circuit plus a software module, which may be installed in the access network equipment or may be used in cooperation with the access network equipment. In the embodiment of the present application, the chip system may be composed of a chip, and may also include a chip and other discrete devices. For convenience of description, the following describes the technical solution provided by the present application by taking an example in which a device for implementing a function of an access network device is an access network device and the access network device is a base station.

(1) A protocol layer structure.

The communication between the access network equipment and the terminal follows a certain protocol layer structure. The protocol layer structures may include a control plane protocol layer structure and a user plane protocol layer structure. For example, the control plane protocol layer structure may include functions of protocol layers such as a Radio Resource Control (RRC) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, a Medium Access Control (MAC) layer, and a physical layer. For example, the user plane protocol layer structure may include functions of protocol layers such as a PDCP layer, an RLC layer, a MAC layer, and a physical layer, and in a possible implementation, a Service Data Adaptation Protocol (SDAP) layer may be further included above the PDCP layer.

(2) A Central Unit (CU) and a Distributed Unit (DU).

The access devices may include CUs and DUs. Multiple DUs can be centrally controlled by one CU. As an example, the interface between a CU and a DU may be referred to as the F1 interface. Wherein, the Control Plane (CP) interface may be F1-C, and the User Plane (UP) interface may be F1-U. The application does not limit the specific names of the interfaces. CUs and DUs can be divided according to the protocol layers of the wireless network: for example, the functions of the PDCP layer and the above protocol layers are set in the CU, and the functions of the lower protocol layers (e.g., the RLC layer and the MAC layer, etc.) of the PDCP layer are set in the DU; for another example, the functions of the protocol layers above the PDCP layer are provided in the CU, and the functions of the PDCP layer and the protocol layers below are provided in the DU, which is not limited.

The above-described division of the processing functions of the CUs and the DUs into protocol layers is an example, and may be performed in other manners. For example, a CU or DU may be partitioned into functions with more protocol layers, and for example, a CU or DU may also be partitioned into partial processing functions with protocol layers. In one design, some of the functions of the RLC layer and the functions of protocol layers above the RLC layer are provided in the CUs, and the remaining functions of the RLC layer and the functions of protocol layers below the RLC layer are provided in the DUs. In another design, the functions of the CU or the DU may also be divided according to the service type or other system requirements, for example, divided by time delay, and the function that processing time needs to meet the delay requirement is set in the DU, and the function that does not need to meet the delay requirement is set in the CU. In another design, a CU may also have one or more functions of the core network. Illustratively, the CUs may be located on the network side to facilitate centralized management. In another design, a Radio Unit (RU) of the DU is set to zoom out. Optionally, the RU may have radio frequency functionality.

Alternatively, the DU and RU may be divided at a physical layer (PHY). For example, a DU may implement higher layer functions in the PHY layer, and an RU may implement lower layer functions in the PHY layer. Wherein, when used for transmission, the function of the PHY layer may include at least one of: adding Cyclic Redundancy Check (CRC) codes, channel coding, rate matching, scrambling, modulation, layer mapping, precoding, resource mapping, physical antenna mapping, or radio frequency transmission functions. For reception, the PHY layer functions may include at least one of: CRC checking, channel decoding, de-rate matching, descrambling, demodulation, de-layer mapping, channel detection, resource de-mapping, physical antenna de-mapping, or radio frequency reception functions. The higher layer function in the PHY layer may include a part of the function of the PHY layer, for example, the part of the function is closer to the MAC layer, and the lower layer function in the PHY layer may include another part of the function of the PHY layer, for example, the part of the function is closer to the rf function. For example, higher layer functions in the PHY layer may include adding CRC codes, channel coding, rate matching, scrambling, modulation, and layer mapping, and lower layer functions in the PHY layer may include precoding, resource mapping, physical antenna mapping, and radio frequency transmission functions; alternatively, higher layer functions in the PHY layer may include adding CRC codes, channel coding, rate matching, scrambling, modulation, layer mapping, and precoding, and lower layer functions in the PHY layer may include resource mapping, physical antenna mapping, and radio frequency transmission functions. For example, higher layer functions in the PHY layer may include CRC checking, channel decoding, de-rate matching, decoding, demodulation, and de-layer mapping, and lower layer functions in the PHY layer may include channel detection, resource de-mapping, physical antenna de-mapping, and radio frequency reception functions; alternatively, higher layer functions in the PHY layer may include CRC checking, channel decoding, de-rate matching, decoding, demodulation, de-layer mapping, and channel detection, and lower layer functions in the PHY layer may include resource de-mapping, physical antenna de-mapping, and radio frequency reception functions.

Illustratively, the functionality of a CU may be implemented by one entity, or by different entities. For example, the functionality of a CU may be further divided, i.e. the control plane and the user plane are separated and implemented by different entities, respectively a control plane CU entity (i.e. CU-CP entity) and a user plane CU entity (i.e. CU-UP entity). The CU-CP entity and CU-UP entity may be coupled to the DU to collectively perform the functions of the access network device.

Optionally, any one of the DU, CU-CP, CU-UP, and RU may be a software module, a hardware structure, or a software module + hardware structure, without limitation. The existence form of different entities can be different, and is not limited. For example, DU, CU-CP, CU-UP are software modules, and RU is a hardware structure. These modules and the methods performed thereby are also within the scope of the present application.

In one possible implementation, the access network equipment includes CU-CP, CU-UP, DU, and RU. For example, the execution body of the present application includes, without limitation, a DU, or a DU and an RU, or a CU-CP, a DU, and an RU, or a CU-UP, a DU, and an RU. The method executed by each module is also within the protection scope of the application.

A terminal may also be referred to as a terminal equipment, a User Equipment (UE), a mobile station, a mobile terminal, etc. The terminal may be widely applied to communication in various scenarios, including, for example, but not limited to, at least one of the following scenarios: device-to-device (D2D), vehicle (V2X), machine-to-equipment (MTC), internet of things (IOT), virtual reality, augmented reality, industrial control, autopilot, telemedicine, smart grid, smart furniture, smart office, smart wear, smart transportation, or smart city, etc. The terminal can be a mobile phone, a tablet personal computer, a computer with a wireless transceiving function, a wearable device, a vehicle, an unmanned aerial vehicle, a helicopter, an airplane, a steamship, a robot, a mechanical arm, an intelligent household device or the like. The specific technology and the specific equipment form adopted by the terminal are not limited in the application.

In the embodiment of the present application, the apparatus for implementing the function of the terminal may be a terminal; or may be a device capable of supporting the terminal to implement the function, such as a chip system, a hardware circuit, a software module, or a hardware circuit plus a software module, which may be installed in the terminal or may be used in cooperation with the terminal. For convenience of description, the following describes technical solutions provided by the present application by taking an apparatus for implementing a function of a terminal as an example.

The base stations and terminals may be fixed or mobile. Base stations and/or terminals may be deployed on land, including indoors or outdoors, hand-held, or vehicle-mounted; can also be deployed on the water surface; it may also be deployed on airborne airplanes, balloons and satellite vehicles. The application scenarios of the base station and the terminal are not limited. The base station and the terminal may be deployed in the same scenario or different scenarios, for example, the base station and the terminal are deployed on the land at the same time; or, the base station is deployed on land, the terminal is deployed on the water surface, and the like, for example, no longer.

The roles of base station and terminal may be relative, e.g., helicopter or drone 120i in fig. 1 may be configured to move the base station, for those terminals 120j that access radio access network 100 through 120i, terminal 120i is the base station; however, for the base station 110a, 120i is a terminal, i.e. the base station 110a and 120i communicate with each other via a wireless air interface protocol. The 110a and 120i may communicate with each other via an interface protocol between the base station and the base station, and in this case, 120i is also the base station as compared to 110 a. Therefore, the base station and the terminal may be collectively referred to as a communication apparatus, 110a and 110b in fig. 1 may be referred to as a communication apparatus having a base station function, and 120a to 120j in fig. 1 may be referred to as a communication apparatus having a terminal function.

The base station and the terminal, the base station and the base station, and the terminal can communicate through the authorized spectrum, the unlicensed spectrum, or both the authorized spectrum and the unlicensed spectrum; communication may be performed in a frequency spectrum of 6 gigahertz (GHz) or less, in a frequency spectrum of 6GHz or more, or in a frequency spectrum of 6GHz or less and in a frequency spectrum of 6GHz or more. The spectrum resources used for wireless communication are not limited in this application.

In the embodiment of the application, a base station sends a downlink signal or downlink information to a terminal, and the downlink information is carried on a downlink channel; the terminal sends uplink signals or uplink information to the base station, and the uplink information is carried on an uplink channel. A terminal may establish a radio connection with a cell controlled by a base station in order to communicate with the base station. The cell in which a radio connection is established with a terminal is called a serving cell of the terminal. When the terminal communicates with the serving cell, it may be interfered by signals from neighboring cells.

It is to be understood that, in the embodiments of the present application, a Physical Downlink Shared Channel (PDSCH), a Physical Downlink Control Channel (PDCCH), a Physical Uplink Shared Channel (PUSCH), and a Physical Uplink Control Channel (PUCCH) are merely examples of a downlink data channel, a downlink control channel, an uplink data channel, and an uplink control channel, and in different systems and different scenarios, the data channel and the control channel may have different names, which is not limited in the embodiments of the present application.

In one design, if a base station wants to schedule a UE on multiple carriers to simultaneously perform PDSCH or PUSCH transmission, it needs to send multiple Downlink Control Information (DCI) for scheduling, and each carrier needs one DCI for scheduling. According to the carrier wave for sending DCI, the method is divided into two modes of self-carrier wave scheduling and cross-carrier wave scheduling. When self-carrier scheduling is used, DCI scheduling a PDSCH or PUSCH on the carrier is also transmitted on the carrier, or it is described that in self-carrier scheduling, DCI and the PDSCH or PUSCH scheduled by the DCI are transmitted in the same Carrier Component (CC). For example, as shown in fig. 2, in CC1, DCI and a PDSCH or PUSCH scheduled on CC1 by the DCI are transmitted. In CC2, DCI and the PDSCH or PUSCH scheduled by the DCI are transmitted. In cross-carrier scheduling, the DCI transmitted on the PDSCH or PUSCH on the carrier is scheduled to be transmitted on another carrier, thereby achieving the effect that the DCI is transmitted on only one carrier. Alternatively described, in cross-carrier scheduling, DCI and a PDSCH or PUSCH scheduled by the DCI may be transmitted in different CCs. For example, as shown in fig. 3, DCI is transmitted in the CC1, which schedules PDSCH or PUSCH in the CC 2.

In the above design, each DCI is typically used to schedule one PDSCH or PUSCH, whether self-carrier scheduling or cross-carrier scheduling. In order to reduce the overhead of DCI, a single DCI scheme is proposed, and multiple PDSCHs or PUSCHs may be scheduled simultaneously using single DCI. The multiple PDSCH or PUSCH may be on the same CC or different CCs. For example, multiple PDSCHs in the same CC may be scheduled using single DCI, or multiple PDSCHs in different CCs may be scheduled. Alternatively, multiple PUSCHs in the same CC may be scheduled using single DCI, or multiple PUSCHs in different CCs may be scheduled. Or, the single DCI may be used to schedule the PDSCH and PUSCH in the same CC, or schedule the PDSCH and PUSCH in different CCs, etc. It should be noted that for single DCI scheduled PDSCH or PUSCH, etc., as an example, not as a limitation of the present application. For example, in other application scenarios, the single DCI may also schedule other resources, such as sidelink resources. As shown in fig. 4, single DCI is transmitted at CC1, which may simultaneously schedule PDSCH1 in CC1 and PDSCH2 in CC 2. The basic principle of the single DCI technology is to schedule PDSCH or PUSCH of multiple carriers or CCs by using a single DCI, and compared with the above self-carrier scheduling or cross-carrier scheduling, each DCI schedules PDSCH or PUSCH of one carrier or CC, the number of DCIs can be reduced, and overhead of a control channel is reduced. In this embodiment of the present application, the Single DCI includes a plurality of fields, and for any field, if corresponding information is configured for the PDSCH or the PUSCH on each CC scheduled by the Single DCI, the load overhead of the Single DCI is relatively large. How to reduce the load overhead of single DCI is a technical problem to be solved by the application. It should be noted that in the description of the embodiments of the present application, the PDSCH or PUSCH may be described as: PDSCH/PUSCH, "/" indicates the relationship of "or".

The application provides a communication method, in which a plurality of PDSCHs or PUSCHs scheduled by single DCI can share field information, thereby reducing the load overhead of the single DCI. As shown in fig. 5, a flow of a communication method is provided, which at least includes:

step 501: the base station sends a first DCI to the UE, the first DCI supporting joint multi-carrier scheduling, the first DCI scheduling transmission of the plurality of CCs. Alternatively, the first DCI may be referred to as a single DCI.

Optionally, step 502: and the UE receives the PDSCH or transmits the PUSCH on the plurality of CCs according to the scheduling of the first DCI.

The first DCI includes a first field, and information carried in the first field is shared by the multiple CCs. The first field is a general term for a field shared by multiple CCs, and may be specifically one or more fields. For example, the subsequent time domain resource indication field, and a PDSCH-to-hybrid automatic repeat request (HARQ) feedback time indication field, etc., may be referred to as a first field. Or may be described as including a plurality of fields in the first field, each of the plurality of fields being shared by the plurality of CCs. The information carried by the first field may be information carried by any one of fields shared by a plurality of CCs. For example, the information k0 carried in the first field may refer to the information k0 carried in the time domain resource indication field, the information k1 carried in the first field may refer to the information k1 carried in the PDSCH-to-HARQ feedback time indication field, and the like. Optionally, the first DCI further includes a second field, where information carried in the second field is configured independently for each CC in the multiple CCs. Optionally, a field in the DCI may also be referred to as a DCI field, and information carried in the DCI field may be referred to as a field value.

In one design, the configuration state of the fields in the first DCI may include shared, flexible, independent, and the like. The configuration state of each field may be specified by a protocol, predefined, or the like, without limitation. For example, the base station may determine, according to the configuration state of each field in the first DCI, information carried by a corresponding field in the first DCI. For a specific field in the first DCI, the field may be referred to as a target field, and information carried in the target field may be referred to as target information:

when the configuration status of the target field is shared (common), the information carried in the target field is shared by the plurality of CCs scheduled by the first DCI. For example, the first DCI schedules PDSCH or PUSCH on the first CC and the second CC, the first DCI may determine the target information according to the PDSCH or PUSCH on the first CC, or determine the target information according to the PDSCH or PUSCH on the second CC, or jointly determine the target information according to the PDSCH or PUSCH on the first CC and the PDSCH or PUSCH on the second CC. And carrying target information in a target field in the first DCI, wherein the target information is shared by the first CC and the second CC. Or, when the configuration state of the target field is flexible (flexible), the information carried in the target field is shared by the multiple CCs scheduled by the first DCI, or the information carried in the target field includes information configured independently for each CC; or, when the configuration state of the target field is independent (independent), the information carried in the target field includes information configured independently for each CC. For example, the first DCI schedules PDSCH1 of the first CC and PDSCH2 of the second CC, and the target field in the first DCI carries: object information 1 and object information 2. The UE may receive PDSCH1 according to target information 1, PDSCH2 according to target information 2, and so on.

Illustratively, the configuration state is a shared field including at least one of: DCI format indication, carrier indication, downlink allocation indication, Transmission Power Control (TPC) command for PUCCH scheduling, PUCCH resource indication, transmission configuration indication, second TPC command for PUCCH scheduling, single HARQ-ACK request, HARQ-ACK retransmission indication, priority indication, channel access indication, PUCCH cell indication, CRC, or the like. The configuration status is a flexible field comprising at least one of: bandwidth part (BWP) indication, frequency domain resource allocation, time domain resource allocation, Virtual Resource Block (VRB) to Physical Resource Block (PRB) mapping, PRB interleave granularity indication, speed matching indication, Zero Power (ZP) channel state information reference signal (CSI-RS) trigger, HARQ process number, PDSCH to HARQ feedback time indication, antenna port and layer number, Sounding Reference Signal (SRS) request, Code Block Group (CBG) transmission information, CBG refresh information, demodulation reference signal (DMRS) sequence initialization, PDCCH enhanced codebook indication, PDSCH group, new feedback indication, required group number, minimum scheduling available value, secondary cell indication, or listening adaptation. The configuration state is an independent field, including at least one of: a Modulation and Coding Scheme (MCS) of Transport Block (TB) 1, a new data indication of TB1, a Redundancy Version (RV) of TB1, an MCS of TB2, a new data indication of TB2, or an RV of TB 2. As shown in table 1, functions of the fields, the number of bits occupied by each field, and the arrangement state in the first DCI are exemplified.

Table 1, field value configuration in the first DCI;

in the embodiment of the application, compared with multiple DCI schedules under the existing CA mechanism, the design of scheduling multiple CCs by using the first DCI can significantly reduce the overhead of a control channel, release more downlink resources for PDSCH transmission, improve downlink capacity, and simultaneously save the overhead of DCI size for the shared design of specific fields in the first DCI, thereby ensuring the system coverage performance.

As can be seen from the foregoing description, the time domain resource allocation and the field configuration state of the PDSCH-to-HARQ feedback time indication in the first DCI are flexible. When the time domain resource allocation field is configured to be shared by multiple CCs, the information k0 carried by the time domain resource allocation field may be shared by multiple CCs. When the PDSCH-to-HARQ feedback time indication field is configured to be shared by multiple CCs, the information k1 carried by the PDSCH-to-HARQ feedback time indication field may be shared by multiple CCs. It is described in detail below how multiple CCs share k0 and k 1.

K0 denotes a time interval for receiving PDCCH and transmitting PDSCH, and the unit of the time interval is a time unit used for transmission or scheduling information, such as symbol, slot, frame or subframe, and the description of the time unit can be specifically referred to below, and K0 is described in the unit of slot. As shown in fig. 6, a PDCCH is received in slot 0, and the PDCCH carries DCI. If the value of k0 carried in the DCI is 4, the UE may receive the DCI scheduled PDSCH in time slot 4. As mentioned above, the configuration status of the time domain resource allocation field of the first DCI is flexible, and the time domain resource allocation field of the first DCI may be set to be shared or independent. When the time domain resource allocation field of the first DCI is set to be independent and the time domain resource allocation field includes a plurality of k0, each k0 value corresponds to one PDSCH scheduled by the DCI, that is, a separate k0 value is configured for each PDSCH scheduled by the DCI to determine the receiving position of the PDSCH, and no additional constraint rule is required, but a certain number of bits is increased. The k0 design when the time domain resource allocation field is set to shared is described below.

In this embodiment of the application, when the information k0 carried in the time domain resource allocation field of the first DCI is configured to be shared by multiple CCs, the k0 is used to indicate an offset value of a first reference position and a time unit corresponding to the PDSCH, and the first reference position is determined according to the time unit corresponding to the first DCI. For example, the unit of the time unit may be a unit of a radio frame (radio frame), a subframe (subframe), a slot (slot), a mini-slot (mini-slot), and a symbol (symbol). For example, in one particular implementation, a time unit may include 2 slots, etc. One radio frame may include one or more subframes, and one subframe may include one or more slots. There may be different slot lengths for different subcarrier spacings. For example, a time slot may be 1 millisecond (ms) when the subcarrier spacing is 15 kHz; one slot may be 0.5ms when the subcarrier spacing is 30 kHz. One slot may include one or more symbols. For example, the next slot of a normal Cyclic Prefix (CP) may include 14 time domain symbols, and the next slot of an extended CP may include 12 time domain symbols. The time domain symbols may be referred to simply as symbols. The time domain symbol may be an Orthogonal Frequency Division Multiplexing (OFDM) symbol, or may be a discrete fourier transform spread orthogonal frequency division multiplexing (DFT-s-OFDM) symbol. A minislot, also called a mini-slot, may be a unit smaller than a slot, and one minislot may include one or more symbols. For example, a micro-slot may include 2 symbols, 4 symbols, or 7 symbols, etc. One slot may include one or more minislots. In the following description, the unit of time unit is mainly taken as an example of a time slot.

For example, when the plurality of CCs scheduled by the first DCI include a first CC and a second CC. When parameter sets (numerology) of the first CC and the second CC are the same, subcarrier spacing (SCS) corresponding to the first CC and the second CC are the same, slot lengths corresponding to the first CC and the second CC are the same, and slot positions corresponding to DCI transmission in the first CC and the second CC are also the same. The first reference position may refer to a slot position where DCI is transmitted in the first CC or in the second CC. That is, the k0 may refer to a time interval between a time slot position for transmitting the PDCCH and a time slot position for transmitting the PDSCH, where the PDCCH carries the first DCI. The parameter set numerology is explained as follows:

the parameter set includes SCS, symbol length, slot length, and Cyclic Prefix (CP) length. A new feature in New Radio (NR) systems is multiple parameter sets, which can be mixed for simultaneous use. As shown in table 2, the following parameter sets can currently be supported in NR:

table 2 frame structure configuration in NR

As shown in table 2, the index of the parameter set numerology is denoted by u, which takes values from 0 to 4. For example, when u is 0, its corresponding SCS is 15kHz, the slot length is 1ms, each subframe includes 1 slot, and each frame includes 10 slots, etc. When u is 1, its corresponding SCS is 1/2 ═ 0.5ms, each subframe includes 2 slots, and each frame includes 20 slots. It can be seen that under different parameter set numerology, corresponding to different SCS, the corresponding slot length in each SCS is not the same.

For example, the plurality of CCs scheduled by the first DCI include a first CC and a second CC, the parameter set of the first CC is different from that of the second CC, and then the SCS of the first CC is different from that of the second CC, and the slot length in the first CC is different from that in the second CC. If the SCS of the first CC is smaller than the SCS of the second CC, the first reference location may refer to the time unit corresponding to the first DCI in the second CC, and the k0 is used to indicate the offset value (or referred to as the slot interval between the time unit corresponding to the first DCI and the time unit corresponding to the PDSCH in the second CC), the method further includes: and the UE determines the offset value of the time unit corresponding to the first DCI and the time unit corresponding to the PDSCH in the first CC according to the SCS of the first CC, the SCS of the second CC and the k 0. For example, the UE determines, according to the SCS of the first CC, the SCS of the second CC, and the k0, an offset value of a time unit corresponding to the first DCI and a time unit corresponding to the PDSCH in the first CC, and the following condition is satisfied:

wherein, floor represents a rounding-down operation, k0 represents an offset value between a time cell corresponding to the first DCI and a time cell corresponding to the PDSCH in the second CC, u1 represents an index of an SCS corresponding to the second CC, and u2 represents an index of an SCS corresponding to the first CC.

For example, as shown in fig. 7, the first DCI is single DCI, the SCS of the first CC is 15kHz, and the SCS of the second CC is 30 kHz. The base station transmits single DCI on the first CC, which schedules PDSCH transmission of the first CC and PDSCH transmission of the second CC. K0 carried in the first DCI may indicate a time interval between a slot corresponding to the single DCI in the second CC and a slot corresponding to the PDSCH in the second CC. Setting the value of k0 to be equal to 4, the UE shifts the position of 4 slots in the direction of increasing the slot number in the slot corresponding to the single DCI in the second CC, and receives the PDSCH.

When the SCS of the first CC is equal to 15kHz and the SCS of the second CC is equal to 30kHz, the slot length in the first CC is equal to two slot lengths in the second CC. In this embodiment of the present application, a slot position for receiving the PDSCH in the first CC may also be calculated according to the above formula 1. The specific calculation process is as follows:

for example, as shown in table 3 below, when the value of SCS is 30kHz, the value of u is 1, and when the value of SCS is 15kHz, the value of u is 0. In the scenario shown in fig. 7, u1 has a value equal to 1, u2 has a value of 0, and k0 has a value equal to 4. When the values of u1, u1, and k0 are respectively substituted into the above formula 1, the calculation result 2 can be obtained. The UE receives a single DCI slot position and a PDSCH slot position in the first CC, with a slot interval of 2.

TABLE 3 different subcarrier spacing configurations in NR

It should be noted that in table 3, the CP may be referred to as a CP length, or a CP type, abbreviated CP. The CP type may be Extended CP (ECP) or normal (normal) CP (NCP). The extended CP next slot may include 12 time domain symbols and the normal CP next slot may include 14 time domain symbols.

For example, as shown in fig. 8, the first DCI is single DCI, the SCS of the first CC is 15kHz, and the SCS of the second CC is 30 kHz. The base station transmits single DCI on the second CC, which schedules PDSCH of the first CC and PDSCH transmission of the second CC. K0 carried in the first DCI may indicate a time interval between a time slot corresponding to the single DCI in the second CC and a time slot corresponding to the PDSCH in the second CC. Setting the value of k0 equal to 2, the UE shifts the position of 2 slots in the direction of increasing the slot number in the slot position corresponding to the single DCI in the second CC, and receives the PDSCH.

In this embodiment of the present application, a slot position for receiving the PDSCH in the first CC may also be calculated according to the above formula 1. As can be inquired from table 3, when the first CC is 30kHz, the value of u1 is 1; when the first CC is 15kHz, the value of u2 is 0; meanwhile, the value of k0 is equal to 2, the values of u1, u2 and k0 are replaced in the formula 1, and the calculation result is equal to 1. The UE has an offset value equal to 1 between slots corresponding to the single DCI in the first CC and the PDSCH. The subsequent UE receives the PDSCH at a position shifted by 1 slot with respect to the single DCI in the first CC.

Or, in another design, k0 carried in the time domain resource allocation field of the first DCI is used to indicate an offset between a time unit corresponding to the first DCI in the first CC and a time unit corresponding to the PDSCH, that is, the first reference location is the time unit corresponding to the first DCI in the first CC. The method further comprises the following steps: and the UE determines a time unit corresponding to the PDSCH in the second CC according to the time unit corresponding to the PDSCH in the first CC. Or, the UE receives indication information from the base station, where the indication information is used to indicate an offset value of a time unit corresponding to the first DCI and a time unit corresponding to the PDSCH in the second CC; or, the UE determines a time unit corresponding to the PDSCH in the second CC according to a third field in the first DCI, where the third field is used to indicate an offset value between the time unit corresponding to the PDSCH in the first CC and the time unit corresponding to the PDSCH in the second CC.

For example, as shown in fig. 9, the first DCI is single DCI, the SCS of the first CC is 15kHz, and the SCS of the second CC is 30 kHz. The base station transmits single DCI on the first CC, the single DCI scheduling a PDSCH of the first CC and a PDSCH of the second CC. K0 carried in the first DCI may indicate a time interval between a time slot corresponding to the single DCI in the first CC and a time slot corresponding to the PDSCH in the second CC. Setting the value of k0 equal to 2, the UE receives the PDSCH by shifting the position of 2 slots in the first slot corresponding to the single DCI in the first CC in the direction of increasing the slot number.

And the UE determines a time slot corresponding to the PDSCH in the second CC according to the time slot corresponding to the PDSCH in the first CC. Since the SCS of the first CC is different from the SCS of the second CC, one slot length in the first CC is equal to two slot lengths in the second CC. The PDSCH may be received in the first of two slots, corresponding to two slots in the second CC, at the slot position of the PDSCH in the first CC. Of course, the PDSCH may be received in the second of the two slots, but is not limited thereto. Alternatively, the base station may further transmit an indication information to the UE, the indication information may be used to indicate another k0, and the k0 is used to indicate an offset between a slot corresponding to the single DCI and a PDSCH transmission slot in the second CC. Wherein, the indication information may be RRC signaling, and the RRC signaling is used for semi-statically configuring another k 0. Or the indication information may be DCI, which dynamically configures another k0, etc.; or, a field, which may be referred to as a third field, may be added to the single DCI to indicate a slot corresponding to the PDSCH in the second CC and an offset relative to a slot corresponding to the PDSCH in the first CC.

In the embodiment of the present application, the time domain resource indication field may also carry k2 in addition to the k0, where k2 is a time interval between the PDCCH and the PUSCH. When the process of multiple CCs sharing k2 is similar to the process of multiple CCs sharing k0, see each other.

Through the design, a plurality of CCs scheduled by the first DCI can share the time domain resource indication field, so that the bit overhead of the first DCI is reduced, and the coverage performance is improved.

k1 refers to the time slot interval between downlink received PDSCH data and feedback HARQ, and the unit may be time units such as time slots. Taking the time slot as an example, as shown in fig. 10, a PDCCH carrying DCI is received in time slot 0, and when k0 carried in the time domain resource indication field in the DCI is equal to 4, the PDSCH is received in time slot 4. When information k1 carried in the PDSCH-to-HARQ feedback time indication field in the DCI is equal to 3, HARQ feedback may be sent in slot 7, where the HARQ feedback may be carried in the PUCCH, and the HARQ feedback may specifically be positive Acknowledgement (ACK) or Negative Acknowledgement (NACK), or the like.

In this embodiment, when k1 carried in the PDSCH-to-HARQ feedback time indication field in the first DCI is configured to be shared by multiple CCs, then k1 may indicate an offset value of a second reference position and a time unit corresponding to HARQ, where the second reference position is determined according to the time unit corresponding to at least one CC in the multiple CCs scheduled by the first DCI. The method further comprises the following steps: and the UE determines time units corresponding to HARQ in the plurality of CCs scheduled by the first DCI according to the second reference position and the k 1. For example, the second reference position may be a time unit corresponding to a first PDSCH as the second reference position, or a time unit corresponding to a last PDSCH as the second reference position, in the PDSCHs of the plurality of CCs scheduled by the first DCI; on any one of the plurality of CCs, the UE transmits HARQ at the same position in the plurality of CCs with an offset of k1 time cells from the second reference position.

In this embodiment of the present application, if the plurality of CCs scheduled by the first DCI include a first CC and a second CC, the base station may send the first DCI on any one of the two CCs. For example, if the base station is configured to transmit the first DCI in the first CC, the base station may also transmit the second DCI on the first CC. The first DCI is a DCI supporting multi-carrier joint scheduling, for example, the first DCI is a single DCI. The second DCI is a DCI supporting single carrier scheduling, for example, the second DCI is a single DCI or a regular legacy DCI, and the legacy DCI may be DCI 1_1, DCI 0_1, DCI 1_0, or DCI 0_ 0.

And when the SCS of the first CC is smaller than that of the second CC, the first DCI and the second DCI are sent in the same time unit. Or, when the SCS of the first CC is greater than the SCS of the second CC, the first DCI is sent in a period of time unit N, and the second DCI is sent in time units at different periodic intervals, where the value of N is determined according to the SCS of the first CC and the SCS of the second CC.

Taking the first DCI as a single DCI as an example, when it is set that at most one PDSCH/PUSCH on each carrier can be jointly scheduled by the single DCI, the UE needs to define the DCI processing capability, for example:

when two single DCI are used for scheduling, 1 single DCI schedules a single carrier, and the other single DC jointly schedules two carriers. The DCI for jointly scheduling the two carriers is the first DCI, and the DCI for scheduling the single carrier is the second DCI. For example, as shown in fig. 11, CC1 is referred to as a scheduled carrier, SCS of CC1 is 15kHz, CC2 is referred to as a scheduled carrier, and SCS of CC2 is 30 kHz. The base station transmits single DCI1 and single DCI2 in CC1, single DCI1 jointly schedules PDSCH1 in two CCs, and single DCI2 schedules PDSCH2 in CC 2. At this time, the UE supports processing single DCI on the scheduling carrier. Optionally, the capability of the UE to process the total number N of DCIs on the scheduled carrier (i.e., CC1) is related to the SCS. For example, if { scheduling carrier, scheduled carrier } corresponds to {15kHz,30kHz } or a combination of {30kHz,60kHz }, the value of N is 2; if { scheduled carrier, scheduled carrier } corresponds to a combination of {15kHz,60kHz }, then the value of N is 4. Optionally, one of the single DCI on the scheduling carrier may schedule one PDSCH, that is, the single DCI2 schedules one PDSCH in a single carrier. Or,

when 1 single DCI and 1 legacy DCI are used for scheduling, the single DCI jointly schedules 2 carriers, and the legacy DCI schedules one carrier. The single DCI is the first DCI, and the legacy DCI is the second DCI. As shown in fig. 12, CC1 is referred to as a scheduled carrier and CC2 is referred to as a scheduled carrier. Single DCI1 transmitted in CC1 schedules PDSCH1 in CC1 and CC2, and legacy DCI transmitted in CC1 schedules PDSCH2 in CC 2. At this time, the UE supports processing two types of DCI on the scheduling carrier, namely single DCI and legacy DCI. Optionally, the capability of the UE to process the total number N of DCIs on the scheduling carrier (i.e., CC1) is related to SCS. For example, if { scheduling carrier, scheduled carrier } corresponds to {15kHz,30kHz } or a combination of {30kHz,60kHz }, the value of N is 2; if { scheduling carrier, scheduled carrier } corresponds to a combination of {15kHz,60kHz }, then the value of N is 4. Or,

when 1 single DCI and 1 legacy DCI are used for scheduling, the single DCI jointly schedules 2 carriers, and the legacy DCI schedules one carrier. The single DCI is the first DCI, and the legacy DCI is the second DCI. As shown in fig. 13, CC1 is referred to as scheduled carrier, SCS corresponding to CC1 is 30kHz, CC2 is referred to as scheduled carrier, and SCS corresponding to CC2 is 15 kHz. The base station transmits single DCI on CC1 that schedules PDSCH1 in CC1 and CC2, and legacy DCI on CC1 that schedules PDSCH2 in CC 1. Optionally, the UE processes 1 single DCI in every N time slots on the scheduling carrier, and the remaining time slots only support legacy DCI processing. The period, which may be referred to as single DCI, is N slots, and the slots during different periods of the single DCI support the processing of legacy DCI. Optionally, the value of N may be related to SCS configuration. For example, if { scheduling carrier, scheduled carrier } corresponds to {30kHz,15kHz } or a combination of {60kHz,30kHz }, the value of N is 2; if { scheduling carrier, scheduled carrier } corresponds to a combination of {60kHz,15kHz }, then the value of N is 4. Or,

single DCI may all be used for scheduling, but at this time, single DCI of other slots schedules only one PDSCH. As shown in fig. 14, CC1 is called scheduled carrier, SCS corresponding to CC1 is 30kHz, CC2 is called scheduled carrier, and SCS corresponding to CC2 is 15 kHz. The base station transmits single DCI1 on CC1, which single DCI1 schedules PDSCH1 in CC1 and CC2, respectively. Single DCI2 is transmitted on CC1, which single DCI2 schedules PDSCH2 in CC 1. In this case, single DCI1 is the first DCI, and single DCI2 is the second DCI. Optionally, the UE supports processing N single DCI per N slots on the scheduling carrier. The value of N is mainly related to SCS configuration. For example, if { scheduling carrier, scheduled carrier } corresponds to {30kHz,15kHz } or a combination of {60kHz,30kHz }, the value of N is 2; if { scheduling carrier, scheduled carrier } corresponds to a combination of {60kHz,15kHz }, then the value of N is 4. Optionally, among the N single DCI, there are N-1 single DCI that only supports the single carrier scheduling function.

In the embodiment of the present application, the capability of the UE to process DCI on a scheduling carrier or a scheduled carrier in different parameter set numerology configuration scenarios is mainly defined above.

The following focuses on the issue of how fields of single DCI are designed to further reduce DCI loading when multiple PDSCH/PUSCH on each carrier or CC can be jointly scheduled by single DCI.

For example, when the first DCI schedules multiple data transmissions on one CC, e.g., when multiple PDSCHs or multiple PUSCHs are scheduled on one CC, then certain field information may be shared among the scheduled multiple PDSCHs or PUSCHs, further reducing the payload size of the first DCI. For example, information carried by any one of the following fields included in the first DCI may be shared by multiple data transmissions of the CC: frequency domain resource allocation, MCS of TB, new data indication of TB, or RV of TB. Optionally, the TB may include TB1 and/or TB2, etc. Optionally, when the first DCI schedules multiple data transmissions on one CC, the information k0 carried in the time domain resource allocation field may be a group k0, and the group k0 includes multiple k 0. The group k0 is shared by multiple CCs, and k0 included in the group k0 are independently configured for multiple data transmissions scheduled by single DCI in one CC. The following description will take the first DCI as a single DCI as an example.

When the multi-carrier scheduling is realized by using the single DCI to schedule a plurality of PDSCH/PUSCHs, the number of PDSCH/PUSCHs which can be simultaneously scheduled by the single DCI on 1 carrier is not restricted any more, and the PDSCH/PUSCHs on all carriers are indicated by the single DCI scheduling. This design may result in a multiple increase in the size of single DCI, affecting transmission coverage. In the embodiment of the application, a plurality of PDSCH/PUSCHs of the same CC scheduled by single DCI can further share some fields, so that the overhead of the DCI size is further reduced. For example, single DCI schedules CC1 and CC 2. Some fields in the single DCI may be shared by the CC1 and CCC2, or corresponding information may be configured for both CCs independently. Taking the MCS field in the single DCI as an example, if two CCs share the MCS field, the information a carried in the MCS field may be shared by CC1 and CC 2. If the information carried in the MCS field is configured separately for two CCs, the information B1 and B2 may be carried in the MCS, respectively, B1 corresponds to the MCS configuration in CC1, and B2 corresponds to the MCS configuration in CC 2. Further, if the base station schedules multiple PDSCH/PUSCH in the CC1, theoretically each PDSCH/PUSCH corresponds to one MCS configuration. In the present application, some fields of the single DCI are designed to be shared by multiple CCs, so as to reduce the size overhead of the single DCI, through the following analysis and design, the specific analysis is as follows:

for example, as shown in fig. 15, single DCI jointly schedules CC1 and CC2, with the parameter set for CC1 being the same as the parameter set for CC2, both with SCS at 15 kHz. Then, under the same parameter set configuration, the time slots on each carrier are the same in size, the PDSCH on different carriers is scheduled in the same Transmission Time Interval (TTI), the time domain resource allocation fields in the DCI may be shared, and one TTI may be considered as one time slot. Meanwhile, the two carriers can jointly feed back the HARQ information, and DCI fields related to the PUCCH, such as PUCCH resource indication, HARQ time indication, TPC command, and other fields, can also be shared. For example, the value k1 refers to a time interval between the PDSCH and the PUCCH, and may be used as a reference point for a joint scheduling cell or a time unit corresponding to a first PDSCH in the scheduling CC, or may be used as a reference point for a joint scheduling cell or a time unit corresponding to a last PDSCH in the scheduling CC. Taking the time unit as the time slot example, the time slot for transmitting HARQ may be determined by offsetting k1 time slots in the direction of increasing the slot number according to the reference point. Furthermore, adjacent slots are typically correlated for multiple PDSCH transmissions on the same carrier or CC, and thus fields such as frequency domain resource allocation, MCS, new data indication and RV may be shared. Or,

the manner in which multiple PDSCH/PUSCH are scheduled on multiple carriers or CCs under different parameter set scenarios may be seen in fig. 16. Because the time lengths on different carriers are different, the number of PDSCHs jointly scheduled by single DCI in the same TTI is more, and the size of the corresponding DCI is multiplied, which affects the coverage capability. Therefore, a limitation must be imposed on a joint scheduling mode for scheduling multiple PDSCHs for multiple TTIs in different parameter set scenarios, which is specifically designed as follows: if the number of the PDSCH/PUSCHs to be transmitted is larger than the number of the carriers or CCs, the time-frequency domain allocation situation of the number of the PDSCH/PUSCHs to be transmitted by the base station on the carrier of the single DCI joint scheduling has the following realization modes:

predefining the number of PDSCH/PUSCH scheduled by single DCI at most; or, predefining the capability of maximally supporting the number of the scheduling CCs on the frequency domain of the single DCI, and limiting the number of the CCs which can be scheduled simultaneously on the frequency domain; or, the capability of predefining the maximum number of supported scheduling time slots in the time domain of the single DCI is performed, and the number of time slots simultaneously scheduled on one CC in the time domain is limited.

For PDSCH/PUSCH transmission on different carriers or CCs, the time domain resource allocation field in the DCI domain may be shared, and the specific method of shared joint indication includes:

the value of k0 is defined by CC of large subcarrier spacing, and the value of k0 of small subcarrier spacing can be obtained according to the subcarrier spacing multiple relation, which can be seen in the above formula 1. Or, the value of the convention k0 is based on the CC of the small subcarrier spacing, a new third field is designed in the DCI to indicate the offset of the position of the small subcarrier spacing k0, and a new field of each PDSCH transmission is independently indicated.

For PDSCH/PUSCH transmission at different slot positions on the same carrier or CC, adjacent slots are usually correlated, so fields such as frequency domain resource allocation, MCS, new data allocation and RV in single DCI can be shared. Specifically, the configuration status of each field in the single DCI can be as shown in table 4:

table 4, field value configuration of single DCI;

it should be noted that for table 4, "on different CCs" means that for a field in a single, it is shared, flexible, or independent on different CCs. The "on the same CC" refers to a field in the single DCI, and multiple PDSCH/PUSCH scheduled by the single DCI on the same CC are shared, flexible, or independent. For example, for the MCS field of TB1, this field is configured independently on different CCs but shared on the same CC. For example, single DCI schedules PDSCH transmissions in CC1 and CC 2. For the MCS field of TB1, the MSC field includes a and B information, the a information corresponding to CC1 and the B information for CC 2. Further, if the single DCI schedules multiple PDSCHs in CC2, the multiple PDSCHs in this CC2 share B information.

In the design, the scheduling of multiple PDSCH/PUSCHs on multiple carriers or CCs is realized by using single DCI, and the load overhead of the single DCI is reduced by aiming at the sharing design of the DCI fields when the multiple PDSCH/PUSCHs are transmitted on the same carrier or CC and on different carriers or CCs.

It is understood that, in order to implement the functions in the above-described method, the base station and the terminal include corresponding hardware structures and/or software modules for performing the respective functions. Those of skill in the art will readily appreciate that the present application is capable of being implemented as hardware or a combination of hardware and computer software in connection with the exemplary elements and method steps described herein. Whether a function is performed as hardware or computer software driven hardware depends on the particular application scenario and design constraints imposed on the solution.

Fig. 17 and 18 are schematic structural diagrams of possible communication devices provided in the present application. These communication devices can be used to implement the functions of the base station or the terminal in the above method, and therefore, the beneficial effects of the above method can also be achieved. In the embodiment of the present application, the communication device may be one of the terminals 120a to 120j shown in fig. 1, may also be the

base station

110a or 110b shown in fig. 1, and may also be a module (e.g., a chip) applied to the terminal or the base station.

As shown in fig. 17, the communication apparatus 1700 includes a processing unit 1710 and a transceiving unit 1720. The communication apparatus 1700 is used to implement the functions of the base station in the above method embodiments.

When the communication apparatus 1700 is used to implement the functions of the base station in the above method embodiments: the transceiving unit 1720 is configured to send first downlink control information DCI to the terminal; the first DCI is used for scheduling transmission of multiple carrier elements (CCs), and the first DCI includes a first field, where information carried in the first field is shared by the multiple CCs; when the information k0 carried in the first field is configured to be shared by the plurality of CCs, the k0 is used to indicate an offset value of a first reference position and a time unit corresponding to a Physical Downlink Shared Channel (PDSCH), and the first reference position is determined according to the time unit corresponding to the first DCI. Optionally, the processing unit 1710 is configured to determine the first DCI.

When the communication apparatus 1700 is used to implement the functions of the terminal in the above-described method embodiments: the transceiving unit 1720 is configured to receive first downlink control information DCI from a network device; the first DCI is used for scheduling transmission of multiple carrier elements (CCs), and the first DCI includes a first field, where information carried in the first field is shared by the multiple CCs; when the information k0 carried in the first field is configured to be shared by the plurality of CCs, the k0 is used to indicate an offset value of a first reference position and a time unit corresponding to a Physical Downlink Shared Channel (PDSCH), and the first reference position is determined according to the time unit corresponding to the first DCI. Optionally, the processing unit 1710 is configured to process the first DCI.

More detailed descriptions of the processing unit 1710 and the transceiving unit 1720 may be directly obtained by referring to the related descriptions in the above method embodiments, and are not repeated herein.

As shown in fig. 18, the communications device 1800 includes a processor 1810 and interface circuits 1820. The processor 1810 and the interface circuit 1820 are coupled to one another. It is understood that the interface circuit 1820 may be a transceiver or an input-output interface. Optionally, the communications apparatus 1800 may also include a memory 1830 for storing instructions to be executed by the processor 1810 or for storing input data required by the processor 1810 to execute the instructions or for storing data generated by the processor 1810 after executing the instructions.

When the communication device 1800 is used for implementing the above methods, the processor 1810 is used for implementing the functions of the processing unit 1710, and the interface circuit 1820 is used for implementing the functions of the transceiving unit 1720.

When the communication device is a module applied to a base station, the base station module realizes the functions of the base station in the method. The base station module receives information from other modules (such as a radio frequency module or an antenna) in the base station, and the information is sent to the base station by the terminal equipment; alternatively, the base station module sends information to other modules (such as a radio frequency module or an antenna) in the base station, and the information is sent by the base station to the terminal device. The base station module may be a baseband chip of a base station, or may be a DU or other modules, where the DU may be a DU under an open radio access network (O-RAN) architecture.

When the communication device is a chip applied to a terminal, the terminal chip realizes the functions of the terminal in the method embodiment. The terminal chip receives information from other modules (such as a radio frequency module or an antenna) in the terminal, and the information is sent to the terminal by the base station; alternatively, the terminal chip sends information to other modules in the terminal (such as a radio frequency module or an antenna), and the information is sent by the terminal to the base station.

It is understood that the processor in this application may be a Central Processing Unit (CPU), other general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. The general purpose processor may be a microprocessor, but may be any conventional processor.

The memory in this application may be random access memory, flash memory, read only memory, programmable read only memory, erasable programmable read only memory, electrically erasable programmable read only memory, registers, hard disk, removable hard disk, CD-ROM, or any other form of storage medium known in the art.

An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. The storage medium may also be integral to the processor. The processor and the storage medium may reside in an ASIC. In addition, the ASIC may reside in a base station or a terminal device. Of course, the processor and the storage medium may reside as discrete components in a base station or terminal device.

The methods in the present application may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may 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 the computer program or instructions are loaded and executed on a computer, the processes or functions described herein are performed in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, a network appliance, a user equipment, a core network appliance, an OAM, or other programmable device. The computer program or instructions may 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 instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire or wirelessly. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that integrates one or more available media. The usable medium may be a magnetic medium, such as a floppy disk, a hard disk, a magnetic tape; optical media such as digital video disks; but also semiconductor media such as solid state disks. The computer readable storage medium may be volatile or nonvolatile storage medium, or may include both volatile and nonvolatile types of storage media.

In this application, unless otherwise specified or conflicting with respect to logic, the terminology and/or description between different embodiments is consistent and may be mutually referenced, and the technical features of different embodiments may be combined to form new embodiments according to their inherent logical relationships.

In the present application, "at least one" means one or more, "a plurality" means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone, wherein A and B can be singular or plural. In the description of the text of the present application, the character "/" generally indicates that the former and latter associated objects are in an "or" relationship; in the formula of the present application, the character "/" indicates that the preceding and following related objects are in a relationship of "division". "including at least one of a, B or C" may mean: comprises A; comprises B; comprises C; comprises A and B; comprises A and C; comprises B and C; including A, B and C.

It is to be understood that the various numerical designations referred to in this application are for convenience of description and are not intended to limit the scope of this application. The sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of the processes should be determined by their functions and inherent logic.

Claims

1. A method of communication, comprising:

sending first downlink control information DCI to a terminal;

the first DCI is used for scheduling transmission of multiple carrier elements (CCs), and the first DCI includes a first field, where information carried in the first field is shared by the multiple CCs; when the information k0 carried in the first field is configured to be shared by the plurality of CCs, the k0 is used to indicate an offset value of a first reference position and a time unit corresponding to a Physical Downlink Shared Channel (PDSCH), and the first reference position is determined according to the time unit corresponding to the first DCI.

2. The method of claim 1, further comprising a second field in the first DCI, the information carried in the second field being independently configured for each of the plurality of CCs.

3. The method of claim 1 or 2, further comprising:

determining information carried by a corresponding field in the first DCI according to the configuration state of the field in the first DCI;

wherein the configuration state of the fields in the first DCI includes sharing, flexibility and independence, and for one field of the first DCI:

when the configuration state of the field is shared, the information carried in the field is shared by the plurality of CCs scheduled by the first DCI; or,

when the configuration state of the field is flexible, the information carried in the field is shared by the plurality of CCs scheduled by the first DCI, or the information carried in the field includes information configured independently for each CC; or,

and when the configuration state of the field is independent, the information carried in the field comprises the information independently configured for each CC.

4. The method of claim 3, wherein the configuration state is a shared field comprising at least one of:

DCI format indication, carrier indication, downlink allocation indication, Transmission Power Control (TPC) command scheduled by a Physical Uplink Control Channel (PUCCH), PUCCH resource indication, transmission configuration indication, or Cyclic Redundancy Check (CRC).

5. Method according to any of claims 1 to 4, characterized in that when the information k carried in the first field is ₁ Configured to be shared by the plurality of CCs, the k ₁ An offset value indicating a second reference position and a time unit corresponding to a hybrid automatic repeat request, HARQ, wherein the second reference position is determined according to the time unit corresponding to the PDSCH in at least one CC of the plurality of CCs.

6. The method of any of claims 1 to 5, wherein the plurality of CCs scheduled for the first DCI includes at least a first CC and a second CC, the first DCI being sent to the terminal on the first CC, further comprising: transmitting a second DCI to the terminal on the first CC;

the first DCI is a DCI supporting multi-carrier joint scheduling, and the second DCI is a DCI supporting single-carrier scheduling.

7. The method of claim 6, wherein the first DCI and the second DCI are sent in a same time unit when a subcarrier spacing (SCS) of the first CC is smaller than a SCS of the second CC.

8. The method of claim 6, wherein the first DCI is sent in N time units for a cycle when the SCS of the first CC is larger than the SCS of the second CC, and wherein the second DCI is sent in time units during a different cycle of the first DCI, and wherein a value of N is determined according to the SCS of the first CC and the SCS of the second CC.

9. The method of any of claims 1 to 8, wherein when the first DCI schedules multiple data transmissions on one CC, information carried by any of the following fields included in the first DCI is shared for the multiple data transmissions of the one CC:

frequency domain resource allocation, modulation coding scheme MCS of the transport block TB, new data indication of the TB, or redundancy version RV of the TB.

10. The method of any one of claims 1 to 9, wherein when the k0 is a set of k0, a plurality of k0 are included in the set of k0, the set of k0 is shared by a plurality of CCs scheduled by the first DCI, and a plurality of k0 included in the set of k0 are independently configured for a plurality of data transmissions scheduled by the first DCI in one CC.

11. A method of communication, comprising:

receiving first Downlink Control Information (DCI) from network equipment;

12. The method of claim 11, further comprising a second field in the first DCI, the information carried in the second field being independently configured for each of the plurality of CCs.

13. The method of claim 11 or 12, wherein the configuration state of the fields in the first DCI comprises shared, flexible, and independent, and wherein at least one of the first field and the second field is determined according to the configuration state of the fields in the first DCI.

14. The method of claim 13, wherein the configuration state is a shared field comprising at least one of:

15. The method of any of claims 11 to 14, wherein the plurality of CCs scheduled by the first DCI include a first CC and a second CC, a subcarrier spacing, SCS, of the first CC is smaller than a SCS of the second CC, the first reference location is a time unit corresponding to the first DCI in the second CC, the k0 is used to indicate an offset value of the time unit corresponding to the first DCI and a time unit corresponding to the PDSCH in the second CC, the method further comprising:

and determining an offset value of a time unit corresponding to the first DCI and a time unit corresponding to the PDSCH in the first CC according to the SCS of the first CC, the SCS of the second CC and the k 0.

16. The method of claim 15, wherein the determining the offset value of the time unit corresponding to the first DCI and the time unit corresponding to the PDSCH in the first CC according to the SCS of the first CC, the SCS of the second CC, and the k0 satisfies the following condition:

17. The method of any of claims 11 to 14, wherein the plurality of CCs scheduled by the first DCI include a first CC and a second CC, the SCS of the first CC is smaller than the SCS of the second CC, the first reference location is an offset value of a time unit corresponding to the first DCI and a time unit corresponding to the PDSCH in the first CC, the k0 is used to indicate an offset value of a time unit corresponding to the first DCI and a time unit corresponding to the PDSCH in the first CC, the method further comprising:

determining a time unit corresponding to the PDSCH in the second CC according to the time unit corresponding to the PDSCH in the first CC; or,

receiving indication information from the network device, where the indication information is used to indicate an offset value of a time unit corresponding to the first DCI and a time unit corresponding to the PDSCH in the second CC; or,

determining a time unit corresponding to the PDSCH in the second CC according to a third field in the first DCI, wherein the third field is used for indicating the time unit corresponding to the PDSCH in the first CC and an offset value of the time unit corresponding to the PDSCH in the second CC.

18. The method according to any of claims 11 to 17, wherein when information k carried in the first field is present ₁ Configured to be shared by the plurality of CCs, the k ₁ An offset value for indicating a second reference position and transmitting a hybrid automatic repeat request, HARQ, time unit, the second reference position being determined according to a time unit corresponding to a PDSCH in one of the plurality of CCs, the method further comprising:

according to the second reference position and the k ₁ And determining a time unit corresponding to HARQ in the plurality of CCs of the first DCI.

19. The method of any of claims 11 to 18, wherein the plurality of CCs of the first DCI schedule include at least a first CC on which the first DCI is received from the network device and a second CC, further comprising: receiving, on the first CC, second DCI from the network device;

20. The method of claim 19, wherein the first DCI and the second DCI are received in a same time unit when a subcarrier spacing, SCS, of the first CC is smaller than a SCS, of the second CC.

21. The method of claim 19, wherein the first DCI is received at N time units when the SCS of the first CC is greater than the SCS of the second CC, the second DCI being received at time units during different cycles of the first DCI, the value of N being determined according to the SCS of the first CC and the SCS of the second CC.

22. The method of any of claims 11 to 21, wherein when the first DCI schedules multiple data transmissions on one CC, information carried in any one of the following fields included in the first DCI is shared for the multiple data transmissions of the one CC:

23. The method of any of claims 11 to 22, wherein when the k0 is a set of k0, a plurality of k0 are included in the set of k0, the set of k0 is shared by a plurality of CCs scheduled by the first DCI, and a plurality of k0 included in the set of k0 are independently configured for a plurality of data transmissions scheduled by the first DCI in one CC.

24. A communication apparatus, characterized in that it comprises means for implementing the method of any of claims 1 to 10.

25. A communications device comprising a processor and a memory, the processor and the memory coupled, the processor configured to implement the method of any of claims 1 to 10.

26. A communications device comprising means for implementing the method of any one of claims 11 to 23.

27. A communications device comprising a processor and a memory, the processor and the memory coupled, the processor configured to implement the method of any of claims 11 to 23.

28. A communication system comprising the apparatus of claim 24 or 25 and the apparatus of claim 26 or 27.

29. A computer-readable storage medium having stored thereon a computer program or instructions which, when run on a computer, cause the computer to perform the method of any of claims 1 to 10, or the method of any of claims 11 to 23.

30. A computer program product comprising a computer program or instructions for causing a computer to perform the method of any one of claims 1 to 10, or the method of any one of claims 11 to 23, when the computer program or instructions is run on a computer.