CN114826537A

CN114826537A - Communication method and device

Info

Publication number: CN114826537A
Application number: CN202210455026.XA
Authority: CN
Inventors: 黄秀璇; 李新县; 丁梦颖; 彭金磷
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2022-04-27
Filing date: 2022-04-27
Publication date: 2022-07-29
Also published as: CN117040707A

Abstract

A communication method and device, the method includes: a terminal receives first control information from network equipment, wherein the first control information simultaneously supports single carrier scheduling and multi-carrier scheduling, the first control information comprises a first field, and the first field indicates single carrier scheduling or multi-carrier scheduling; when the first field indicates single carrier scheduling, the terminal communicates with the network equipment on one scheduled carrier; or, when the first field indicates multi-carrier scheduling, the terminal communicates with the network device on the scheduled multiple carriers. By adopting the method and the device, the single carrier scheduling or the multi-carrier scheduling can be displayed or indicated in a hidden mode by utilizing the first field in the first control information, the network equipment does not need to additionally send the notification message, and the air interface overhead is saved.

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 determine the current scheduling single carrier or joint multi-carrier scheduling of the control information is a problem worthy of research.

Disclosure of Invention

The embodiment of the application provides a communication method and a communication device, which are used for determining single carrier scheduling or joint multi-carrier scheduling of first control information scheduling.

In a first aspect, a communication method is provided, where an execution subject of the method is a terminal or a component (a processor, a chip, or other device) configured in the terminal, and where the execution subject is the terminal, the method includes: a terminal receives first control information from network equipment, wherein the first control information simultaneously supports single carrier scheduling and multi-carrier scheduling, the first control information comprises a first field, and the first field indicates single carrier scheduling or multi-carrier scheduling; when the first field indicates single carrier scheduling, the terminal communicates with the network equipment on one scheduled carrier; or, when the first field indicates multi-carrier scheduling, the terminal communicates with the network device on the scheduled multiple carriers.

By the method, the single carrier scheduling or the multi-carrier scheduling of the first control information can be displayed or indicated in a hidden mode by utilizing the first field in the first control information, and the network equipment does not need to additionally send the notification message, so that the air interface overhead is saved.

In one design, the first field is a field configured independently for each carrier, the first field indicating the single carrier scheduling when the first field contains one scheduling information; or, when the first field contains multiple pieces of scheduling information and the multiple pieces of scheduling information are the same, the first field indicates the single carrier scheduling; or, when the first field contains multiple pieces of scheduling information and the multiple pieces of scheduling information are different, the first field indicates the multi-carrier scheduling.

In the current design, when the first field is a field configured for each carrier independently, the first field includes information corresponding to each carrier when the first control information schedules multiple carriers. For example, for the MCS field in the first control information, if the MCS field is a field configured independently for each carrier, the first control information schedules N carriers, and the MCS includes N pieces of information, which correspond one-to-one to the N carriers. Therefore, for a field configured independently for each carrier, when the field includes scheduling information of a single carrier, determining single carrier scheduling; when the scheduling information of the multiple carriers is included in the field, the multi-carrier scheduling is determined. It should be noted that, in some cases, although the first field includes a plurality of pieces of scheduling information, the plurality of pieces of scheduling information are the same, and this case is also referred to as single carrier scheduling. For example, the first field is an MCS field, and the MCS field includes information a corresponding to carrier 1, the a information is copied into multiple copies and carried in the MCS field, that is, the MCS field includes multiple information a, and at this time, even if the MCS field carries multiple pieces of scheduling information, the MCS field is considered to indicate single carrier scheduling. In the design, the current design is adopted to determine single carrier scheduling or multi-carrier scheduling, additional information is not required to be added, and the expense of first control information is saved.

In one design, the first field is a carrier indication field, and the single carrier scheduling or the multi-carrier scheduling is determined according to a size of the carrier indication field.

In one design, the first field may contain a bitmap that indicates the multi-carrier scheduling or single-carrier scheduling.

In one design, the first field is a partial bandwidth, BWP, indication field that indicates a first BWP; and determining that the scheduling mode corresponding to the first BWP is the single-carrier scheduling or the multi-carrier scheduling. For example, the terminal may determine, according to the correspondence between the BWP and the scheduling manner, that the scheduling manner corresponding to the first BWP is single carrier scheduling or multi-carrier scheduling.

By the method, the corresponding relation between the BWP and the scheduling mode is bound in advance, the network equipment can indicate different scheduling modes in a hidden way by indicating different BWPs, the network equipment does not need to additionally indicate the scheduling modes, and the air interface overhead is saved.

In one design, the receiving the first control information from the network device further comprises: and receiving a radio resource control message from the network equipment, wherein the radio resource control message comprises a search space configured for a terminal, the search space comprises first control information and second control information, and the second control information is control information supporting single carrier scheduling.

In the above design, the first control information may be single DCI, and the second DCI may be current legacy DCI. When the single DCI and the legacy DCI are configured in the same search space, the terminal can preferentially receive the single DCI and ensure the reception of the single DCI.

In one design, prior to receiving the first control information from the network device, further comprising: receiving configuration information from a network device, the configuration information being used for configuring a parameter n _MI The parameter n _MI A specific search space may be configured for multi-carrier joint scheduling, and the configuration information may be RRC signaling. The method further comprises the following steps: UE according to parameter n _MI Determining an initial Control Channel Element (CCE) location; determining a PDCCH candidate set according to the initial CCE position; and determining a search space specific to the multi-carrier joint scheduling according to the PDCCH candidate set.

Optionally, the UE may be configured to select the parameter n according to _MI Determining an initial CCE location satisfying the following:

where L denotes a PDCCH aggregation level, and for a common search space, L ═ {4, 8, 16}, and for a UE-specific search space, {1, 2, 4, 8, 16 };

representing a frequency domain starting position of the PDCCH candidate set; n is a radical of hydrogen _CCE，p Representing the number of CCEs in the p-th CORESET;

denotes n corresponding to the aggregation level L _CI And the number of candidate sets of PDCCH in the search space;

representing the maximum candidate set number on the aggregation level L of the p-th CORESET and the s-th search space; n is _CI The cross-carrier indication is represented, frequency domain conflict is avoided when PDCCH candidate sets on carriers with different subcarrier intervals are scheduled, CIF indication in cross-carrier scheduling configuration (Cross Carrier scheduling Confi) configuration of high-level signaling is used, and if the CIF indication is not configured, the CIF indication is 0; i denotes a CCE index (index) within an aggregation level L, where i ═ 0, 1.

In the design, the complexity of terminal blind detection can be reduced by defining a specific search space for the jointly scheduled multiple carriers.

In one design, prior to receiving the first control information from the network device, further comprising: according to the parameter n _CI Determining an initial CCE position; determining a PDCCH candidate set according to the initial CCE position; and determining a search space specific to the multi-carrier joint scheduling according to the PDCCH candidate set. By way of example, the parameter n may be _CI The expansion is from 3 bits to 8 bits. When the parameter n _CI When the indicated value is 8-255, the specific search space of the multi-carrier joint scheduling can be determined according to the values between 8-255.

Optionally, according to the parameter n _CI Determining an initial CCE location satisfying the following:

for the description of the parameters in the above formula, refer to the above description, and are not repeated. Through the design, a special search space can be defined for the multi-carrier of the joint scheduling, and the blind detection complexity of the terminal is reduced.

In a second aspect, a communication method is provided, where an execution subject of the method is a network device or a component (processor, chip, or other device) configured in the network device, and taking the network device as an example, the method includes: the method comprises the steps that network equipment sends first control information to a terminal, wherein the first control information simultaneously supports single carrier scheduling and multi-carrier scheduling, the first control information comprises a first field, and the first field indicates single carrier scheduling or multi-carrier scheduling; when the first field indicates single carrier scheduling, the network equipment communicates with the terminal on one scheduled carrier; alternatively, when the first field indicates multi-carrier scheduling, the network device communicates with the terminal on the scheduled multiple carriers.

Through the design, the network equipment can display or hide indication single carrier scheduling or multi-carrier scheduling by utilizing the first field in the first control information, and the network equipment does not need to additionally send a notification message, so that the air interface overhead is saved.

In one design, the first field is a carrier indication field, and the single carrier scheduling or the multi-carrier scheduling is indicated according to a size of the carrier indication field.

In one design, the first field contains a bitmap that indicates the single carrier scheduling or the multi-carrier scheduling.

In one design, the first field is a partial bandwidth BWP indication field, the BWP indication field indicating a first BWP, the first BWP indicating the single-carrier scheduling or the multi-carrier scheduling.

In one design, before sending the first control information to the terminal, the method further includes: sending a radio resource control message to the terminal, wherein the radio resource control message comprises a search space configured for the terminal; the search space comprises the first control information or second control information, the second control information is control information supporting single carrier scheduling, and the first control information and the second control information are scrambled by using a cell-radio network temporary identifier (C-RNTI); or the search space comprises the first control information and the second control information, the first control information is scrambled by adopting other modes except C-RNTI, and the second control information is scrambled by adopting C-RNTI; or, when the plurality of carriers scheduled by the first control information include a main carrier and an auxiliary carrier, the search space includes a search space of the main carrier and a search space of the auxiliary carrier, the search space of the main carrier includes the second control information, the search space of the auxiliary carrier includes the first control information and third control information, and the first control information, the second control information, and the third control information are scrambled by using a C-RNTI.

In one design, before the network device sends the first control information to the terminal, the method further includes: sending configuration information to the terminal, wherein the configuration information is used for configuring the parameter n _MI The parameter n _MI And a special search space can be configured for multi-carrier joint scheduling, and the blind detection complexity of the terminal is reduced. Optionally, the configuration information may be RRC signaling.

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 communication system provided in an embodiment of the present application;

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

fig. 3 is a schematic diagram of cross-carrier scheduling provided in an embodiment of the present application;

fig. 4 is a schematic diagram of single DCI provided in an embodiment of the present application;

fig. 5 is a flowchart of a communication method provided in an embodiment of the present application;

fig. 6 is a flowchart of downlink scheduling provided in the embodiment of the present application;

fig. 7 is a flowchart of uplink scheduling provided in the embodiment of the present application;

fig. 8 and 9 are schematic diagrams of SSs corresponding to Pcell and Scell provided in the embodiment of the present application;

fig. 10 and 11 are schematic diagrams of apparatuses provided in embodiments of 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-to-event (V2X), machine-type communication (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.

Currently, the UE performs uplink transmission and downlink transmission according to scheduling of a base station. For example, the base station may send a PDCCH including (DCI) to the UE, where the DCI may schedule uplink transmission or downlink transmission of the UE, the uplink data included in the PUSCH and the downlink data included in the PDSCH. According to different scheduling modes, the method is divided into self-carrier scheduling and cross-carrier scheduling. Optionally, in the description of the embodiment of the present application, the CC and the carrier are not distinguished, and may be replaced with each other. In the self-carrier scheduling, DCI and a PDSCH or PUSCH scheduled by the DCI are transmitted in the same Carrier Component (CC). For example, as shown in fig. 2, taking DCI scheduling PDSCH as an example, the base station transmits DCI on CC1, which schedules PDSCH1 in CC 1; the base station transmits DCI on CC2 that schedules PDSCH2 in CC 2. In cross-carrier scheduling, DCI and the DCI scheduled PDSCH are transmitted in different carriers. For example, as shown in fig. 3, taking DCI scheduling PDSCH as an example, the base station transmits DCI in CC1, and the DCI schedules PDSCH2 and the like in CC 2. Regardless of self-carrier scheduling or cross-carrier scheduling, the DCI supports single carrier scheduling, that is, the DCI schedules data transmission in one carrier. If data transmission in a plurality of carriers is scheduled, a plurality of DCIs need to be sent for scheduling respectively, and the overhead of a control channel is increased. In order to reduce the overhead of the control channel, a single (single) DCI scheme is proposed, and the single DCI supports both single-carrier scheduling and multi-carrier scheduling. Taking multicarrier scheduling as an example, as shown in fig. 4, single DCI is transmitted in CC1, and the single DCI schedules PDSCH1 in CC1 and PDSCH2 in CC 2. In order for the UE to know whether the current single DCI schedules a single carrier or schedules multiple carriers. In one scheme, the base station may send an RRC message to the UE indicating whether the subsequent single DCI is single carrier scheduled or multi-carrier scheduled. In this scheme, the base station needs to additionally send an RRC message to the UE, which increases air interface overhead.

In the method, a field in the first control information is used to display or indicate that the first control information is single carrier scheduling or multi-carrier scheduling, and an RRC message does not need to be sent additionally, thereby reducing air interface overhead. Optionally, the first control information may support single carrier scheduling and multi-carrier scheduling simultaneously, and the first control information may be single DCI. As shown in fig. 5, a flow chart is provided, which at least comprises:

step 501: the UE receives first control information from a base station, wherein the first control information comprises a first field, and the first field indicates single carrier scheduling or multi-carrier scheduling.

For example, the first control information may support both single carrier scheduling and multi-carrier scheduling, and the first control information may be referred to as a first DCI or a single DCI, and the first control information is described as a single DCI as an example. The first field may indicate or imply single carrier scheduling or multi-carrier scheduling, as described in detail below.

Step 502: when the first field indicates single carrier scheduling, the UE communicates with the base station on one scheduled carrier; alternatively, when the first field indicates multi-carrier scheduling, the UE communicates with the base station on the scheduled multiple carriers.

In one design, single DCI may support both single-carrier scheduling and multi-carrier joint scheduling. Assignments for certain fields in the single DCI may be shared among multiple carriers, e.g., DCI format indication (identifier for DCI formats) fields and CRC fields, etc. Assignment of certain fields in the single DCI requires independent configuration for each carrier, for example, Modulation and Coding Scheme (MCS), Redundancy Version (RV), and new data indicator (new data indicator). For a field configured independently for each carrier in the single DCI, it can be used to indicate whether the single DCI is currently single carrier scheduling or multi-carrier scheduling. That is, when the first field is a field configured independently for each carrier, the first field included in the single DCI may indicate single carrier scheduling or multi-carrier scheduling. For example, when the first field contains only one scheduling information, a single carrier scheduling may be indicated, e.g., an MCS field, an RV field, or a new data indication field, etc. For a field configured independently for each carrier, when a single DCI schedules multiple carriers, the independently configured field contains information corresponding to each carrier. For example, for an independently configured MCS field, when single DCI schedules carrier 1, carrier 2, and carrier 3, the MCS field contains information a, information B, and information C, where information a corresponds to the modulation coding scheme of carrier 1, information B corresponds to the modulation coding scheme of carrier 2, and information C corresponds to the modulation coding scheme of carrier 3. When the independently configured field in the single DCI only contains one piece of scheduling information, the single carrier scheduling of the current single DCI can be determined. Corresponding information is not assigned to other carriers or the state is set to a reserved state (reserved). For example, for an independently configured MSC field, when the MCS field contains information a, the UE may determine that the current single DCI is single carrier scheduling. Specifically, which carrier is scheduled for data transmission may be indicated by a Carrier Indicator Field (CIF) field in the single DCI. Alternatively, the first and second electrodes may be,

for the independently configured first field, although the plurality of scheduling information are included, the plurality of scheduling information are the same, and the first field may be determined to indicate single carrier scheduling. For example, single DCI schedules carrier 1, carrier 2, and carrier 3 without being scheduled. The MCS, new data indicator, RV, or the like independently configured in the single DCI may be referred to as a first field, and the first field includes scheduling information of carrier 1, but includes the scheduling information of carrier 1 copied 2 times. For example, if the scheduling information of carrier 1 is information a, the first field includes information a, and information a. In this design, although a plurality of pieces of scheduling information are included for the above independently configured fields, the plurality of pieces of scheduling information are the same. For example, if single DCI is used to schedule carrier 1, and the scheduling information corresponding to carrier 1 is a, the first field configured independently may include 3 scheduling information, but the 3 scheduling information are all a, that is, the information corresponding to carrier 1 is used for both the information corresponding to carrier 2 and carrier 3. The first field indicates multi-carrier scheduling only if the plurality of scheduling information is included in the independently configured first field and the plurality of scheduling information is different. For example, if the first field includes 3 pieces of scheduling information, which are scheduling information a corresponding to carrier 1, scheduling information B corresponding to carrier 2, and scheduling information C corresponding to carrier 3, it is determined that the single DCI schedules carrier 1, carrier 2, and carrier 3 at the same time.

In one design, the CIF field may take the value of 0 bits, or 3 bits. When the CIF field is configured with 0 bit, single DCI is represented by self-carrier scheduling. When the CIF field is configured to be 3 bits, the single DCI is cross-carrier scheduling and supports a cross-carrier scheduling situation of 8 carriers at most. In the embodiment of the present application, a configuration may be added to the CIF field, and the configuration may be referred to as a target configuration. When the bits occupied by the CIF field are the number of bits in the target configuration, it can be considered that the current single DCI schedules multiple carriers. In one design, the CIF field may be configured to 8 bits when the single DCI supports multi-carrier scheduling, and the 8 bits may represent scheduling of 256 carrier combinations at most. In the embodiment of the present application, when the first field is a CIF field, single carrier scheduling or multi-carrier scheduling may be determined according to the size of the CIF field. Optionally, the size of the CIF field may also be referred to as the size of the CIF field, or the number of bits occupied by the CIF field. For example, when the size of the CIF field is a first value, a single carrier schedule may be determined. The first value may be the aforementioned 0 bit or 3 bits. Specifically, when the CIF field is 0 bit, it may indicate that the single DCI is currently self-carrier scheduling. When the CIF field is 3 bits, it may indicate that the single DCI is currently cross-carrier scheduling, and the 3 bits support a case of indicating 8 carriers of cross-carrier scheduling at most. Alternatively, when the size of the CIF field is a second value, the multicarrier scheduling may be determined. The second value includes, but is not limited to, 8 bits. For example, taking the CIF field as 8 bits as an example, the corresponding relationship between the value of the CIF field and the multi-carrier scheduling combination can be seen in table 1 below.

TABLE 1 CIF value and multicarrier scheduling combination correspondence

CIF	Scheduling combinations	CIF	Scheduling combinations
				00000000	CC1+CC2	00000111	CC1+CC2
00000001	CC1+CC3	00001000	CC1+CC3
				00000010	CC1+CC4	00001001	CC1+CC4
00000011	CC1+CC5	00001010	CC1+CC5
				00000100	CC1+CC6	00001011	CC1+CC6
00000101	CC1+CC7	00001100	CC1+CC7
				00000110	CC1+CC8	00001101	CC1+CC8
……	……	……	……

Alternatively, the first field contains a bitmap (bitmap), which may indicate single carrier scheduling or multi-carrier scheduling. For example, a field, such as a multi-carrier indicator field (MIF) field, may be newly added in the single DCI, and may specifically indicate which fields are jointly scheduled in a bitmap manner. If an 8-bit byte is defined and respectively corresponds to 8 carriers, the value of each bit of the 8-bit byte can be 0 or 1, and when the value is 0, the corresponding carrier is not jointly scheduled by single DCI; and when the value is 1, the corresponding carrier is jointly scheduled by single DCI. It can be understood that when there are 10 and 7 1 values in the 8-bit byte, it indicates that the current single DCI schedules a single carrier. The specific scheduled single carrier is a carrier corresponding to a byte with a value of 1.

Or, the scheduling mode is bound with a bandwidth part (BWP), the BWP supporting single carrier scheduling and the BWP supporting multi-carrier scheduling are preconfigured, and the dynamic switching of the single carrier and multi-carrier scheduling functions is realized through BWP switching. For example, the first field is a BWP indication field. Upon receiving the single DCI, the UE determines a first BWP included in a BWP indicator (bandwidth part indicator) field included in the single DCI. And determining the scheduling mode corresponding to the first BWP as single-carrier scheduling or multi-carrier scheduling and the like according to the corresponding relation between the BWP and the scheduling mode. The correspondence of the BWP and the scheduling is pre-configured. For example, the base station configures a correspondence between the BWP and the scheduling scheme in advance for the UE through signaling such as RRC or MAC control signaling (CE). Alternatively, the correspondence between BWP and scheduling is preset, or the protocol is specified, and is not limited. For example, the correspondence between BWP0 and the single carrier scheduling scheme and the correspondence between BWP1 and the multi-carrier scheduling scheme are established in advance. When the value of the BWP indication field in the single DCI is set to 0, the UE may be instructed to switch to BWP0 for data transmission. Since BWP0 has correspondence with single carrier scheduling, it can implicitly indicate single DCI scheduling single carrier. Alternatively, when the value of the BWP indication field in the single DCI is 1, the UE may be instructed to switch to BWP1 for data transmission. Since BWP1 has a corresponding relationship with multi-carrier scheduling, it can implicitly indicate single DCI to schedule multi-carriers. BWP refers to a set of contiguous Resource Block (RB) resources on a carrier. Wherein a plurality of BWPs can be configured on each CC for one UE, and at each time there is at least one active BWP in one CC, and the active BWP is used for actually transmitting or receiving data. When single DCI indicates a single carrier scheduling scheme, which single carrier is specifically scheduled may be indicated by a CIF field, similar to the foregoing. When the single DCI indicates the multi-carrier scheduling mode, it may need the assistance of other information to determine which carriers are specifically scheduled. For example, the base station may transmit a piece of control information, which may be MAC CE, DCI, etc., and which may indicate which carriers are specifically scheduled by single DCI. Alternatively, the CIF field may be extended, and the CIF field indicates a specifically scheduled carrier, etc., without limitation. It should be noted that the above description is given by taking the first field as BWP, and is not limited. For example, the assignment of other fields may be established in correspondence with the scheduling. By indicating the assignment in this field, dynamic switching of the indicated scheduling mode can be implicit.

Taking the above flow in fig. 5 as an example, applying to downlink scheduling, as shown in fig. 6, a flow chart is provided, which at least includes:

step 601: and the base station allocates downlink time-frequency resources for the UE according to the channel state reported by the UE and by combining the information such as the UE capability and the like, and indicates scheduling information to the UE through the PDCCH.

The PDCCH indicates scheduling information, and the scheduling information comprises single DCI. Or, it is described that the single DCI is transmitted in the PDCCH, which is a control channel for transmitting the single DCI, etc. single DCI may schedule one carrier or may jointly schedule multiple carriers. In downlink scheduling, the assignment of a DCI format indication (identifier for DCI formats) field in single DCI is 1, and the field is used for indicating uplink scheduling transmission or downlink scheduling transmission. The DCI format indication field is assigned a value of 1 when indicating a downlink scheduled transmission. When uplink scheduling transmission is indicated, the assignment of the DCI format indication field is 0. Regarding single DCI currently specifically being single carrier scheduling or multi-carrier scheduling, there are several implementation manners:

when single is indicated to be scheduled by single carrier: the carrier specific field not scheduled is not assigned. As mentioned above, some fields in the single DCI may be shared by multiple carriers, and some fields need to be configured independently for each carrier. The special field may refer to a field configured separately for each carrier, such as a MCS, a new data indication, or an RV. For a field configured separately for each carrier in the single DCI, when scheduling multiple carriers, scheduling information corresponding to each carrier in the multiple carriers needs to be included in the field. In this example, when single carrier scheduling is indicated, scheduling information of a single carrier is contained in a field configured independently for each carrier. Or, the special domain of the carrier which is not scheduled adopts the value of the corresponding domain of the scheduled carrier. For example, if the single DCI schedules only carrier 1, the fields of carrier 2 and carrier 3 that need to be indicated separately all adopt the value corresponding to carrier 1. At this time, it may indicate that carrier 2 and carrier 3 are not scheduled, and only carrier 1 is scheduled at this time. Or, the scheduling mode is bound with the BWP, and the dynamic switching of the single carrier and the multi-carrier is realized through the BWP switching. For example, for the BWP indication field, when the value of the BWP indication field is 0, single DCI scheduling single carrier may be indicated.

When single DCI is indicated to be currently scheduled by multiple carriers: the scheduling function is bound with BWP, and dynamic switching of single carrier and multi-carrier is realized through BWP switching. For example, for the BWP indication field, when the value of the field is 1, single DCI joint scheduling multi-carrier may be indicated; or, in multi-carrier scheduling, the combination situation of the jointly scheduled carriers, such as CIF field, can be indicated by a special field in the single DCI. For example, 8 bits are allocated in the CIF field, and the 8 bits may indicate a combination of 256 jointly scheduled carriers, as shown in table 1 above. Or, in the multi-carrier scheduling, a new field, such as an MIF field, may be added to the single DCI, and the MIF field may indicate the jointly scheduled carrier in a bitmap manner. Or, similar to the CIF field, the corresponding relationship between bits and carrier combinations may be pre-established, and the MIF field may indicate different carrier combinations by carrying different bit information, and the like, without limitation. Alternatively, in multi-carrier scheduling, the base station may send a control message indicating which carriers are jointly scheduled.

Step 602: the base station transmits downlink data on the PDSCH resources allocated to the UE, and the UE demodulates the downlink data according to the received indication information, which may refer to information carried in the single DCI, such as MCS.

Taking the above flow in fig. 5 as an example, applying to uplink scheduling, as shown in fig. 7, a flow chart is provided, which at least includes:

step 701: when the UE has uplink data to send, the UE may send a Scheduling Request (SR) to the base station on a PUCCH or PUSCH channel, and request an uplink grant to the base station.

Step 702: when receiving the SR, the base station responds to the SR and sends scheduling information to the UE through the PDCCH.

Step 703: when receiving the scheduling information, the UE transmits a MAC Protocol Data Unit (PDU) on a resource allocated by the base station, where the MAC PDU includes information such as a Buffer Status Report (BSR).

Step 704: and if the BSR received by the base station is more than 0, continuing to schedule the UE and sending scheduling information to the UE through the PDCCH.

Step 705: and the UE transmits data on the PUSCH resource indicated by the base station.

In the above steps 702 and 704, the base station transmits scheduling information to the UE through the PDCCH, where the scheduling information may be included in a single DCI, and the single DCI may support both single carrier scheduling and joint multi-carrier scheduling functions, that is, the single DCI may schedule the PUSCH on one carrier only or may jointly schedule the PUSCH on multiple carriers. In uplink scheduling, a DCI format field in single DCI is configured to be 0, which is used to indicate that uplink scheduling transmission is currently performed. In this embodiment of the present application, for implementation of single DCI specifically indicating single carrier scheduling or joint multi-carrier scheduling at different times, reference may be made to the implementation manner of the downlink scheduling process, which is not described again.

In the method, the single DCI supports both single carrier scheduling and joint multi-carrier scheduling, how the single DCI indicates the single carrier scheduling or multi-carrier scheduling function at different moments is designed, and in the design, the base station does not need to send an RRC to indicate the single carrier scheduling or multi-carrier scheduling, the single carrier scheduling or multi-carrier scheduling of the single DCI is indicated in a display or hidden mode with smaller control information overhead, and the downlink capacity is improved.

After the initial access of the UE is completed, the base station may configure a control resource set (core set) and a Search Space (SS) for the UE through the RRC, and the UE continuously monitors a location corresponding to the SS. In one design, the number of different DCI payload sizes that a UE listens to in each slot may not exceed 4, and the number of DCI payload sizes that a CRC is scrambled by a cell radio network temporary identifier (C-RNTI) may not exceed 3. The DCI payload size may also be referred to as a DCI size (size). The conventional (legacy) DCI currently comprises DCI x _0, DCI x _1 and DCI x _2, the three DCIs are scrambled by adopting C-RNTI, and the sizes of the three DCIs are respectively as follows: dimension a, dimension B, and dimension C. In the present embodiment, four different DCI sizes (sizes) will occur due to the introduction of single DCI. Contrary to the above design, in order to solve the above problems, the present application provides the following solutions:

the first scheme is as follows: the UE is designed not to listen to DCI x _1 and single DCI at the same time. Since single DCI can implement the function of DCI x _1, when single DCI is introduced, the DCI monitored by the UE in the SS may be designed as: DCI x _0, DCIx _2 and single DCI, the single DCI is scrambled by C-RNTI. For example, the base station may send, to the UE, an RRC message, where the RRC message is used to configure an SS for the terminal, where the SS includes first control information or second control information, the first control information is DCI supporting simultaneous single carrier and multi-carrier joint scheduling, and the second control information is DCI supporting single carrier scheduling. For example, the first control information may be single DCI, the second control information may be DCI x _0, and the first control information and the second control information are scrambled with C-RNTI at the same time.

Taking the initial access process of the UE as an example, the process of the UE monitoring the DCI includes:

step 1: the UE scans and obtains a CORESET0 indicated by a Master Information Block (MIB) through a synchronization signal and a PBCH block (SSB), and obtains scheduling information of a corresponding system information block 1(system information block1, SIB1) through blind detection, thereby completing initial access.

Step 2: after the initial access is completed, the base station configures the CORESET and the SSs through RRC, and the UE continuously monitors the positions corresponding to the SSs. Since in one design, one UE supports listening for a maximum of 3C-RNTI scrambled DCI sizes. When introducing single DCI, four different DCI size sizes will occur. In this scheme, in order to satisfy the number limitation on the size of the blind DCI in the above design, because the single DCI includes the function of the legacy DCI x _1, the legacy DCI x _1 is replaced by the single DCI, that is, the UE is not required to monitor the DCI x _1 and the single DCI at the same time, where the DCI monitored by the UE includes: DCI x _0, DCI x _2, and single DCI.

And step 3: and the UE performs CRC blind test attempt in the PDDCH candidate set by monitoring the DCI, finds the DCI belonging to the UE and completes the blind test.

The second scheme is as follows: in order to maintain the current design, a scheme of scrambling the single DCI by using a non-C-RNTI is designed, and at the moment, the UE monitors the single DCI and the legacy DCI simultaneously, namely the UE monitors the single DCI, the DCI x _0, the DCI x _1 and the DCI x _2 simultaneously. For example, the base station may send an RRC message to the UE, where the RRC message includes first control information and second control information, the first control information may be scrambled using other methods than C-RNTI, and the second control information may be scrambled using C-RNTI. The first control information may be single DCI, and the second control information may be legacy DCI.

Regarding the second scheme, the following explanation is provided by taking the following scheduling as an example: for the flow of downlink scheduling, the description in fig. 6 can be referred to. In the second scheme, in step 601, the base station transmits a PDCCH indicating scheduling information included in single DCI. The single DCI is sent to the UE through the PDCCH through the processes of CRC scrambling, polar (polar) coding, speed matching, scrambling, Quadrature Phase Shift Keying (QPSK) modulation, pre-framing, power control, resource mapping, precoding, beamforming, time domain processing, medium radio frequency processing and the like. In the CRC scrambling process, a 16-bit CRC is scrambled according to a Radio Network Temporary Identity (RNTI). In this second scheme, in order to satisfy the above design, the single DCI is scrambled by using a non-C-RNTI scrambling method. The non-C-RNTI may be denoted as an X-RNTI. The X-RNTI is mainly used for dynamically scheduling multiple carrier transmissions in a joint manner, the corresponding transmission channel is a downlink-shared channel (DL-SCH) or an uplink-shared channel (UL-SCH), and the corresponding logical channel is a Dedicated Control Channel (DCCH), in the foregoing step 601, since the single-RNTI is mainly used for supporting joint scheduling of multiple carriers without using C-RNTI scrambling, the single-DCI does not occupy the constraint of "DCI size not exceeding 3C-scrambles" for UE blind detection, the single-carrier RNTI scheduling and the multi-carrier scheduling may be respectively associated with different DCI formats, and the base station may transmit different formats to implement a scheduling manner of whether different time slots are a selective DCI scheduling manner or a multi-carrier joint scheduling manner, specifically, the base station may transmit measurement information fed back by the UE, to determine whether to adopt a single carrier scheduling mode or a multi-carrier scheduling mode. And if the single carrier scheduling mode is determined, the UE sends legacy in the next time slot. And if the multi-carrier scheduling mode is determined to be adopted, transmitting single DCI in the next time slot. For example, the UE in the current time slot sends single DCI to jointly schedule multiple carriers, and if the measurement information fed back by the terminal is smaller than a certain threshold, it indicates that the coverage performance of the current UE is poor. In the next time slot, the base station may send single carrier scheduling of legacy DCI to improve coverage performance. Since the load size of single DCI is larger than that of legacy DCI, the larger the load size of DCI, the worse the coverage performance. Therefore, when the coverage performance of the location where the UE is located is poor, legacy DCI may be transmitted to improve the coverage performance.

The second scheme is described by taking UE initial access as an example.

Step 1: the UE can obtain CORESET0 indicated by the MIB through SSB scanning, and obtain corresponding SIB scheduling information through blind detection to complete initial access.

Step 2: after the initial access is completed, the base station may configure the CORESET and the SSs through RRC messages, and the UE continuously monitors the locations of the SSs. In one design, one UE supports listening for a maximum of 3C-RNTI scrambled DCI sizes and 1 other RNTI scrambled DCI sizes. In this design, since the single DCI does not employ C-RNTI scrambling, the terminal may listen to both legacy DCI and single DCI.

And step 3: and the UE performs CRC blind detection attempt in the PDCCH candidate set by monitoring to find the DCI belonging to the UE and complete the blind detection.

In the design, the multi-carrier joint scheduling is realized through the single DCI, the scrambling mode of the C-RNTI adopted by the single DCI is restricted, and the UE can monitor the legacy DCI and the single DCI at the same time.

In the third scheme: a DCI size (size) budget (budget) is defined on each carrier. When single DCI employs multi-carrier scheduling, it is considered that DCI x _0 is not monitored on the secondary carrier. In the design of the present application, DCI x _1, DCI x _2, and single DCI may be monitored on the secondary carrier. And monitoring DCI x _0, DCI x _1 and DCI x _2 on the main carrier. For example, the base station sends an RRC message to the UE, which contains the SSs scheduled for the UE. When the multiple carriers scheduled by the single DCI include a primary carrier and a secondary carrier, the SS includes an SS of the primary carrier and an SS of the secondary carrier, and the SS of the primary carrier includes second control information, where the second control information may include DCI x _0, DCI x _1, DCI x _2, and the like. The SS of the secondary carrier includes first control information and third control information, where the first control information may include single DCI, and the third control information includes DCI x _1 and DCI x _ 2. The first control information, the second control information and the third control information are scrambled by using C-RNTI.

For example, as shown in fig. 8, single DCI is transmitted on carrier 1, and the single DCI jointly schedules carrier 1 and carrier 2. In a Carrier Aggregation (CA) or non-CA scenario, carrier 1 corresponds to a primary cell (Pcell), and may be referred to as a primary carrier, and carrier 2 corresponds to a secondary carrier (Scell), and may be referred to as a secondary carrier. Considering that DCI x _0 is not monitored on Scell, the blind detection budget for single DCI can be calculated on carrier 2. At this time, the UE monitors DCI x _0, DCI x _1, and DCI x _2 on the SS corresponding to carrier 1 (corresponding to Pcell), and monitors DCI x _1, DCI x _2, and single DCI on carrier 2 (corresponding to Scell).

Alternatively, as shown in fig. 9, single DCI is transmitted on carrier 1, and carrier 1 and carrier 2 are jointly scheduled. In a CA or non-CA scenario, if carrier 1 corresponds to Scell, carrier 2 corresponds to Pcell. Considering that Scell does not listen to DCI x _0, the blind detection budget of single DCI is calculated on scheduled carrier 1. And the UE monitors DCI x _1, DCI x _2 and single DCI on the SS corresponding to the carrier 1, and monitors DCI x _0, DCI x _1 and DCI x _2 on the SS corresponding to the carrier 2.

A fourth scheme: jointly defining the budget of the multi-carrier scheduling, and adding 1 to the total budget quantity of the plurality of carriers which are jointly scheduled. If the single DCI jointly schedules the two carriers, the DCI formats scrambled by the C-RNTI which can be detected in a blind mode on the two carriers do not exceed 7, namely the maximum value of the DCI formats scrambled by the C-RNTI which can be detected in a blind mode on the two carriers is 7. Optionally, there are several following implementation modes:

it is configured that single DCI is transmitted on carrier 1, and single DCI schedules two carriers, and two carriers of joint scheduling only increase 1 DCI size budget, which may be calculated on carrier 1 or carrier 2. If the increased 1 DCI size budget is placed on the carrier 1, the single DCI budget is calculated in the blind detection budget of the carrier 1, and the UE monitors the DCI sizes scrambled by 4C-RNTIs at most on the SS corresponding to the carrier 2. Similarly, if 1 increased DCI size budget is placed on carrier 2, the single DCI budget is within the blind detection budget of carrier 2, and the UE monitors DCI sizes scrambled by 4C-RNTI at most on the SS corresponding to carrier 2. At this time, the single DCI can adopt a C-RNTI scrambling mode.

The fifth scheme is as follows: the DCI size budget is separately defined on each carrier, a new DCI size budget is added on each carrier, and the original '3 + 1' is changed into '4 + 1', namely the UE can monitor 4 kinds of C-RNTI scrambled DCI sizes and 1 kind of non-C-RNTI scrambled DCI sizes on each carrier. At this time, the single DCI can adopt a C-RNTI scrambling mode.

Through the design, the DCI size budget rule under the multi-carrier joint scheduling is redefined, so that the blind decoding budget of the PDCCH is not exceeded after single DCI is introduced.

The sixth scheme is as follows: in this scheme, following the current design, the number of different DCI payload sizes that the UE listens to in each slot does not exceed 4, and the number of DCI payload sizes for CRC scrambling by C-RNTI does not exceed the provision of 3. In this scheme, the UE may be configured to simultaneously listen to single DCI and legacy DCI. When the UE monitors both simultaneously, exceeding the provisions in the current design, the UE may choose to monitor single DCI instead of legacy DCI. For example, the base station sends an RRC message to the UE, where the RRC message includes an SS configured for the UE, the SS includes first control information and second control information, the first control information supports both single carrier scheduling and multi-carrier joint scheduling, and the first control information may be single DCI. The second control information supports single carrier scheduling, and the second control information may be legacy DCI.

Optionally, before step 501 in fig. 5, the method may further include: and the base station defines a new search space for the multi-carrier of the single DCI joint scheduling to reduce the complexity of the UE blind detection.

Currently, before the UE performs blind detection, the UE can obtain information such as time-frequency resource information of the PDCCH, a scheduling period, aggregation levels that the PDCCH may send, and the number of times of blind detection required for each aggregation level according to a search space and a CORESET associated with the search space. Therefore, the UE may determine each PDCCH candidate set according to the above information in combination with the blind detection formula, decode each candidate set, and stop the blind detection procedure once the decoding is successful.

Wherein, determining the position of each PDCCH candidate set requires knowing the position information of the initial Control Channel Element (CCE), i.e. the CCE _start To determine the initial CCE location, see the following blind test formula 1:

representing the maximum candidate set number on the aggregation level L of the p-th CORESET and the s-th search space; n is _CI Is a cross-carrier fingerIt is shown that when scheduling PDCCH candidate sets on carriers of different subcarrier intervals, frequency domain collision is avoided, indicated by CIF in cross carrier scheduling configuration (cross carrier scheduling config) of high layer signaling, if not configured, 0; i denotes a CCE index (index) within an aggregation level L, where i ═ 0, 1.

Through the above formula, the initial position of the CCE can be calculated, and the position of the PDCCH can be further determined, at which time the UE performs decoding. It can be seen that, when the search space corresponding to the cross-carrier scheduling is determined, n is mainly passed _CI To identify. To avoid the conflict of CCE positions in multi-carrier joint scheduling, one scheme is to define a specific search space for multi-carrier joint scheduling and introduce a new identifier, i.e. n _MI The carrier combination number of the joint scheduling is indicated. This value is 1 when co-scheduling CC1 and CC2, and 2 when co-scheduling CC1 and CC3, as in single DCI. n is _MI The specific value of (2) is configured by the higher layer RRC signaling, and specifically, see the following blind test formula 2:

by introducing n _MI And a special search space can be defined for multi-carrier joint scheduling, and resource configuration conflict on a frequency domain is effectively avoided. In this design, the base station may configure n to the UE via RRC signaling _MI . UE according to n _MI Determining the initial CCE position by combining the blind test formula 2; and further determining a PDCCH candidate set according to the initial CCE position, wherein the PDCCH candidate set comprises all PDCCH resources which can possibly send single DCI, and the set of the PDCCH candidate set is called a search space. In the design, the UE can perform blind detection in the search space by using the CRC corresponding to the single DCI, thereby reducing the complexity of the blind detection of the UE.

In another scheme, n of current cross-carrier scheduling is multiplexed _CI Identity, but need to be n _CI New meanings are added. At present, n _CI At most 3 bits are configured, i.e. a maximum of 7 is taken. In order to additionally indicate the search space of the multi-carrier joint scheduling, it is necessary to increase the number of bits for it,an optional configuration value is 8 bits, that is, the corresponding CCE starting positions in the multi-carrier joint scheduling may be distinguished by using a value between 8 and 255. For example, when n _CI When the numerical value between 8 and 255 is indicated, the numerical value between 8 and 255 can be substituted into the blind test formula 1 to determine the CCE initial position; determining a PDCCH candidate set according to the CCE starting position; and determining a search space according to the PDCCH candidate set. And the UE performs blind detection in the search space by using the CRC corresponding to the single DCI, so that the blind detection complexity of the UE is reduced.

In the scheme, the complexity of blind detection can be reduced, and the conflict on CCE resource allocation is prevented when the PDCCH frequency domain position is determined. It should be noted that the above scheme for reducing the UE blind detection complexity may be used in combination with the aforementioned schemes in fig. 5 to 9, or may be used alone, without limitation.

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 various illustrative elements and method steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. 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. 10 and fig. 11 are schematic structural diagrams of a possible communication device 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. 10, the communication device 1000 includes a processing unit 1010 and a transceiver unit 1020. The communication device 1000 is used to implement the functions of the terminal or the base station in the above method embodiments.

When the communication device 1000 is used to implement the functions of the terminal in the above method embodiments: the transceiving unit 1020 is configured to receive first control information from a network device, where the first control information simultaneously supports single carrier scheduling and multi-carrier scheduling, and the first control information includes a first field, where the first field indicates single carrier scheduling or multi-carrier scheduling; the processing unit 1010 is configured to communicate with the network device on the scheduled one carrier when the first field indicates single carrier scheduling; alternatively, when the first field indicates multi-carrier scheduling, communicating with the network device on the scheduled multiple carriers.

When the communication apparatus 1000 is used to implement the functions of the base station in the above-described method embodiments: the transceiving unit 1020 is configured to send first control information to a terminal, where the first control information simultaneously supports single carrier scheduling and multi-carrier scheduling, and the first control information includes a first field, where the first field indicates single carrier scheduling or multi-carrier scheduling; a processing unit 1010 configured to communicate with the terminal on one scheduled carrier when the first field indicates single carrier scheduling; alternatively, when the first field indicates multi-carrier scheduling, communicating with the terminal on the scheduled multiple carriers.

The more detailed description of the processing unit 1010 and the transceiver unit 1020 can be obtained by directly referring to the related description in the above method embodiment, which is not repeated herein.

As shown in fig. 11, the communication device 1100 includes a processor 1110 and an interface circuit 1120. The processor 1110 and the interface circuit 1120 are coupled to each other. It is understood that the interface circuit 1120 may be a transceiver or an input-output interface. Optionally, the communication device 1100 may further include a memory 1130 for storing instructions to be executed by the processor 1110 or for storing input data required by the processor 1110 to execute the instructions or for storing data generated by the processor 1110 after executing the instructions.

When the communication device 1100 is configured to implement the method, the processor 1110 is configured to implement the functions of the processing unit 1010, and the interface circuit 1120 is configured to implement the functions of the transceiver 1020.

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.

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; alternatively, the base station module sends information to other modules in the base station (such as a radio frequency module or an antenna), and the information is sent by the base station to the terminal. The base station module may be a baseband chip of a base station, and may also be a DU or other modules, where the DU may be a DU under an open radio access network (O-RAN) architecture.

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 this 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 text description of the present application, the character "/" generally indicates that the preceding and following 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:

receiving first control information from network equipment, wherein the first control information simultaneously supports single carrier scheduling and multi-carrier scheduling, and comprises a first field which indicates single carrier scheduling or multi-carrier scheduling;

communicate with the network device on the scheduled one carrier when the first field indicates single carrier scheduling; alternatively, the first and second electrodes may be,

communicate with the network device on the scheduled plurality of carriers when the first field indicates multi-carrier scheduling.

2. The method of claim 1, wherein the first field is a field configured independently for each carrier, the first field indicating the single carrier scheduling when the first field contains one scheduling information; alternatively, the first and second electrodes may be,

when the first field contains a plurality of scheduling information and the plurality of scheduling information are the same, the first field indicates the single carrier scheduling; alternatively, the first and second electrodes may be,

the first field indicates the multi-carrier scheduling when the first field includes a plurality of scheduling information and the plurality of scheduling information are different.

3. The method of claim 1 or 2, wherein the first field is a carrier indication field, and the single carrier scheduling or multi-carrier scheduling is determined according to a size of the carrier indication field.

4. The method of claim 1 or 2, wherein the first field contains a bitmap, the bitmap indicating the multi-carrier scheduling or single-carrier scheduling.

5. The method of claim 1 or 2, wherein the first field is a partial bandwidth, BWP, indication field, the BWP indication field indicating a first BWP; and determining that the scheduling mode corresponding to the first BWP is the single-carrier scheduling or the multi-carrier scheduling.

6. The method of any of claims 1 to 5, wherein prior to receiving the first control information from the network device, further comprising:

and receiving a radio resource control message from the network equipment, wherein the radio resource control message comprises a search space configured for the terminal, the search space comprises first control information and second control information, and the second control information supports single carrier scheduling.

7. A method of communication, comprising:

sending first control information to a terminal, wherein the first control information simultaneously supports single carrier scheduling and multi-carrier scheduling, the first control information comprises a first field, and the first field indicates single carrier scheduling or multi-carrier scheduling;

communicate with the terminal on the scheduled one carrier when the first field indicates single carrier scheduling; alternatively, the first and second electrodes may be,

communicate with the terminal on the scheduled multiple carriers when the first field indicates multi-carrier scheduling.

8. The method of claim 7, wherein the first field is a field configured independently for each carrier, the first field indicating the single carrier scheduling when the first field contains one scheduling information; alternatively, the first and second electrodes may be,

9. The method according to claim 7 or 8, wherein the first field is a carrier indication field, and the single carrier scheduling or the multi-carrier scheduling is indicated according to a size of the carrier indication field.

10. The method of claim 7 or 8, wherein the first field contains a bitmap, the bitmap indicating the single carrier schedule or the multi-carrier schedule.

11. The method of claim 7 or 8, wherein the first field is a partial bandwidth BWP indication field, the BWP indication field indicating a first BWP, and the corresponding scheduling manner of the first BWP is the single-carrier scheduling or the multi-carrier scheduling.

12. The method according to any of claims 7 to 11, wherein before sending the first control information to the terminal, further comprising:

sending a radio resource control message to the terminal, wherein the radio resource control message comprises a search space configured for the terminal;

the search space comprises the first control information or second control information, the second control information is control information supporting single carrier scheduling, and the first control information and the second control information are scrambled by using a cell-radio network temporary identifier (C-RNTI); alternatively, the first and second electrodes may be,

the search space comprises the first control information and the second control information, the first control information is scrambled by adopting other modes except C-RNTI, and the second control information is scrambled by adopting C-RNTI; alternatively, the first and second electrodes may be,

the multiple carriers scheduled by the first control information comprise a main carrier and an auxiliary carrier, the search space comprises a search space of the main carrier and a search space of the auxiliary carrier, the search space of the main carrier comprises the second control information, the search space of the auxiliary carrier comprises the first control information and third control information, and the first control information, the second control information and the third control information are scrambled by adopting C-RNTI.

13. A communication apparatus comprising means for implementing the method of any of claims 1 to 6.

14. 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 6.

15. A communication apparatus, characterized in that it comprises means for implementing the method of any of claims 7 to 12.

16. 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 7 to 12.

17. A communication system comprising the apparatus of claim 13 or 14 and the apparatus of claim 15 or 16.

18. 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 6, or the method of any of claims 7 to 12.

19. 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 6, or the method of any one of claims 7 to 12, when the computer program or instructions are run on a computer.