CN113517946A

CN113517946A - A communication method and device

Info

Publication number: CN113517946A
Application number: CN202010278718.2A
Authority: CN
Inventors: 费永强; 郑娟; 侯海龙; 李超君
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2020-04-10
Filing date: 2020-04-10
Publication date: 2021-10-19
Also published as: WO2021204107A1

Abstract

The embodiments of the present application disclose a communication method and device, which are used to reduce the number of times of DCI detection by a terminal, thereby reducing the complexity of the terminal. The method includes: a terminal detects downlink control information DCI from a network device, wherein the DCI is used to schedule a physical data channel, and the format of the DCI used to schedule the physical data channel includes multiple DCI formats; wherein the multiple DCI formats correspond to The type of DCI size is less than or equal to N, and N is a positive integer less than or equal to 3; and/or, when the DCI corresponding to the multiple DCI formats is scrambled by the terminal-specific wireless network temporary identifier RNTI, the corresponding DCI formats The type of DCI size is less than or equal to M, where M is a positive integer less than or equal to 2.

Description

Communication method and device

Technical Field

The present application relates to the field of communications technologies, and in particular, to a communication method and apparatus.

Background

In a wireless communication system, for example, in a Long Term Evolution (LTE) system and a fifth generation (5G) communication system (or New Radio (NR)) system, a network device may send Downlink Control Information (DCI) to a terminal device, for example, a User Equipment (UE), for scheduling data transmission between the network device and the terminal device.

Disclosure of Invention

The embodiment of the application provides a communication method and a communication device, which are used for reducing the size and the type of DCI (downlink control information) used for scheduling a physical data channel so as to reduce the times and the complexity of blind detection of a terminal.

In order to solve the above technical problem, an embodiment of the present application provides the following technical solutions:

in a first aspect, an embodiment of the present application provides a communication method, including: detecting Downlink Control Information (DCI) from a network device, wherein the DCI is used for scheduling a physical data channel, and the format of the DCI used for scheduling the physical data channel comprises a plurality of DCI formats; the types of the DCI sizes corresponding to the plurality of DCI formats are less than or equal to N, wherein N is a positive integer less than or equal to 3; and/or when the DCI corresponding to the plurality of DCI formats is scrambled by using a terminal-specific Radio Network Temporary Identifier (RNTI), the kinds of DCI sizes corresponding to the plurality of DCI formats are less than or equal to M, and M is a positive integer less than or equal to 2.

Wherein, the RNTI is the identifier of the terminal. The terminal-specific RNTI may be a cell RNTI (C-RNTI), a configured scheduling RNTI (CS-RNTI), or a modulation and coding scheme cell RNTI (MCS-C-RNTI) of the terminal.

The physical data channel is used for transmitting uplink data, such as a Physical Uplink Shared Channel (PUSCH) for the physical data channel, or for transmitting downlink data, such as a Physical Downlink Shared Channel (PDSCH) for the physical data channel, or includes a physical channel (e.g., PUSCH) for transmitting uplink data and a physical channel (e.g., PDSCH) for transmitting downlink data.

Because the size of the DCI used for scheduling the physical data channel does not exceed M, wherein M is a positive integer less than or equal to 3, and/or the size of the DCI scrambled by the radio network temporary identifier RNTI specific to the terminal does not exceed N, wherein N is a positive integer less than or equal to 2, compared with the prior art, the DCI detection times of the terminal can be reduced, the complexity of the terminal is further reduced, and the power consumption of the terminal is reduced.

In one possible implementation manner, the number of DCI sizes corresponding to the multiple DCI formats is less than or equal to N, and the method includes: when DCI corresponding to the plurality of DCI formats is scrambled by using a common RNTI or a terminal-specific RNTI, the variety of DCI sizes corresponding to the plurality of DCI formats is less than or equal to N.

The common RNTI may be a system information RNTI (SI-RNTI), a paging RNTI (P-RNTI), or a random access RNTI (RA-RNTI), etc.

In the implementation manner, by limiting the scrambling mode of the DCI, the type of the size of the DCI of the type can be limited, and the DCI detection times of the terminal can be reduced, so that the complexity of the terminal is reduced, and the power consumption of the terminal is reduced.

In a possible implementation manner, the multiple DCI formats include a first format and a second format detected in a terminal-specific search space USS, where the DCI corresponding to the first format is used to schedule uplink transmission and the DCI corresponding to the second format is used to schedule downlink transmission, and the DCI transmitted in the USS is scrambled using the terminal-specific RNTI. In this implementation manner, by limiting the types of the DCI sizes of the first format and the second format, the number of times of detecting the DCI of the first format and the second format by the terminal can be reduced, thereby reducing the complexity of the terminal and reducing the power consumption of the terminal.

In one possible implementation, the DCI size corresponding to the first format and the DCI size corresponding to the second format are aligned.

In one possible implementation, the DCI size corresponding to the first format is aligned to the DCI size corresponding to the second format. The method can avoid information loss of the DCI of the second format.

Or, the DCI size corresponding to the second format is aligned to the DCI size corresponding to the first format. The method can avoid information loss of the DCI of the first format.

Or, if the DCI size corresponding to the first format is smaller than the DCI size corresponding to the second format, aligning the DCI size corresponding to the first format to the DCI size corresponding to the second format; if the DCI size corresponding to the second format is smaller than the DCI size corresponding to the first format, the DCI size corresponding to the second format is aligned to the DCI size corresponding to the first format. The implementation method does not lose information bits (payload) in the DCI corresponding to the first format and the second format, and ensures the accuracy of transmission parameters.

In one possible implementation, aligning the DCI size corresponding to the second format to the DCI size corresponding to the first format includes: if the DCI size corresponding to the first format is smaller than the DCI size corresponding to the second format, truncating K fields of the DCI corresponding to the second format, wherein the truncated DCI size corresponding to the second format is the same as the DCI size corresponding to the first format, and K is a positive integer; or, if the DCI size corresponding to the first format is larger than the DCI size corresponding to the second format, at least one padding bit is padded in the DCI corresponding to the second format, and the padded DCI size corresponding to the second format is the same as the DCI size corresponding to the first format.

In this implementation manner, the transmission performance and the scheduling performance of the DCI corresponding to the first format may be ensured, and thus the uplink transmission performance of the terminal may be ensured.

In one possible implementation, aligning the DCI size corresponding to the first format to the DCI size corresponding to the second format includes: if the DCI size corresponding to the second format is smaller than the DCI size corresponding to the first format, truncating K fields of the DCI corresponding to the first format, wherein the truncated DCI size corresponding to the first format is the same as the DCI size corresponding to the second format, and K is a positive integer; or, if the DCI size corresponding to the second format is larger than the DCI size corresponding to the first format, at least one padding bit is padded in the DCI corresponding to the first format, and the padded DCI size corresponding to the first format is the same as the DCI size corresponding to the second format.

In this implementation manner, the transmission performance and the scheduling performance of the DCI of the second format may be ensured, and thus the downlink transmission performance of the terminal device may be ensured.

In one possible implementation, the K domains include at least one of: a frequency domain resource allocation domain; a time domain resource allocation domain; a physical uplink control channel resource indication domain; a physical downlink shared channel to a hybrid automatic repeat request feedback time indication domain; and demodulating a reference signal sequence initialization field.

In a possible implementation manner, the multiple DCI formats further include a third format and a fourth format detected in the USS, where the DCI corresponding to the third format is used to schedule uplink transmission, and the DCI corresponding to the fourth format is used to schedule downlink transmission, where the first format is different from the third format, and the second format is different from the fourth format; the DCI size corresponding to the third format is aligned to the DCI size corresponding to the first format or aligned to the DCI size corresponding to the second format, and the DCI size corresponding to the fourth format is aligned to the DCI size corresponding to the first format or aligned to the DCI size corresponding to the second format, where the DCI size corresponding to the first format is equal to the DCI size corresponding to the second format. In this implementation manner, by aligning the DCI sizes of the third format and the fourth format to the DCI sizes corresponding to the first format and the second format, the number of DCI sizes that the terminal needs to detect can be reduced, and the number of blind detection times of the terminal on the DCI can be reduced, so that the implementation complexity, power consumption, and cost of the terminal can be reduced.

In one possible implementation manner, the multiple DCI formats include a third format and a fourth format detected in a terminal-specific search space USS, and the third format and the fourth format detected in a common search space CSS, where DCI corresponding to the third format is used for scheduling uplink transmission and DCI corresponding to the fourth format is used for scheduling downlink transmission, where DCI transmitted in the USS is scrambled using the terminal-specific RNTI, and DCI transmitted in the CSS is scrambled using the terminal-specific RNTI or is scrambled using the common RNTI; wherein the DCI size corresponding to the third format detected in the USS is aligned to the DCI size corresponding to the third format detected in the CSS or aligned to the DCI size corresponding to the fourth format detected in the CSS, and the DCI size corresponding to the fourth format detected in the USS is aligned to the DCI size corresponding to the third format detected in the CSS or aligned to the DCI size corresponding to the fourth format detected in the CSS. In the implementation manner, by aligning the sizes of the DCI corresponding to the third format and the fourth format in the USS and the CSS, the blind DCI detection times of the terminal when the time-frequency resources of the USS and the CSS are overlapped can be reduced, and the implementation complexity, power consumption and cost of the terminal can be reduced.

In one possible implementation manner, the third format is 0_0, and the fourth format is 1_ 0.

In a possible implementation manner, the types of DCI sizes corresponding to multiple DCI formats are less than or equal to 2, which is beneficial to reducing the size types of DCI required to be detected by a terminal to 2; or when the DCI corresponding to the multiple DCI formats is scrambled by using the terminal-specific RNTI, the size of the DCI corresponding to the multiple DCI formats is less than or equal to 1, which is beneficial to reducing the size of the DCI scrambled by the terminal-specific RNTI required to be detected by the terminal to 1; or, when the DCI sizes corresponding to the multiple DCI formats are less than or equal to 2 and the DCI corresponding to the multiple DCI formats are scrambled using the terminal-specific RNTI, the DCI sizes corresponding to the multiple DCI formats are less than or equal to 1, which is beneficial to reducing the size types of the DCI required to be detected by the terminal to 2, and reducing the size types of the DCI scrambled using the terminal-specific RNTI to 1.

In one possible implementation manner, the multiple DCI formats include a first format, a second format, a third format, and a fourth format detected in the USS, and a third format and a fourth format detected in a common search space CSS, where the DCI corresponding to the first format and the third format is used for scheduling uplink transmission, the DCI corresponding to the second format and the fourth format is used for scheduling downlink transmission, the first format is different from the third format, and the second format is different from the fourth format; wherein the DCI size corresponding to the first format detected in the USS is aligned to the DCI size corresponding to the third format detected in the CSS or to the DCI size corresponding to the fourth format detected in the CSS, and, the DCI size corresponding to the second format detected in the USS is aligned to the DCI size corresponding to the third format detected in the CSS or to the DCI size corresponding to the fourth format detected in the CSS, the DCI size corresponding to the third format detected in the USS is aligned to the DCI size corresponding to the third format detected in the CSS or to the DCI size corresponding to the fourth format detected in the CSS, and, the DCI size corresponding to the fourth format detected in the USS is aligned to the DCI size corresponding to the third format detected in the CSS or to the DCI size corresponding to the fourth format detected in the CSS. In the implementation manner, by aligning the first format, the second format, the third format and the fourth format in the USS with the third format and the fourth format in the CSS, the DCI blind detection times when the time-frequency resources of the USS and the CSS overlap can be reduced, so that the implementation complexity, power consumption and cost of the terminal can be reduced.

In a second aspect, an embodiment of the present application provides a communication method, including: detecting Downlink Control Information (DCI) from a network device, wherein the DCI is used for scheduling a physical data channel, and the format of the DCI used for scheduling the physical data channel comprises a plurality of DCI formats; the DCI size corresponding to a sixth format of the multiple DCI formats is aligned to the DCI size corresponding to a fifth format of the multiple DCI formats, where the DCI corresponding to the fifth format is used to schedule uplink transmission and the DCI corresponding to the sixth format is used to schedule downlink transmission.

In this implementation manner, the DCI size corresponding to the DCI format for scheduling downlink transmission is aligned with the DCI size corresponding to the DCI format for scheduling uplink transmission, so that information loss of the DCI of the fifth format can be avoided, and uplink transmission performance of the terminal can be ensured.

In one possible implementation, aligning the DCI size corresponding to the sixth format of the multiple DCI formats to the DCI size corresponding to the fifth format of the multiple DCI formats includes: if the DCI size corresponding to the fifth format is smaller than the DCI size corresponding to the sixth format, truncating K fields of the DCI corresponding to the sixth format, where the truncated DCI size corresponding to the sixth format is the same as the DCI size corresponding to the fifth format, and K is a positive integer; or, if the DCI size corresponding to the fifth format is larger than the DCI size corresponding to the sixth format, at least one padding bit is padded in the DCI corresponding to the sixth format, and the padded DCI size corresponding to the sixth format is the same as the DCI size corresponding to the fifth format.

In this implementation manner, the transmission performance and the scheduling performance of the DCI corresponding to the fifth format may be ensured, and thus the uplink transmission performance of the terminal may be ensured.

In one possible implementation, the DCI of the fifth format may be a DCI of a first format detected in a terminal-specific search space USS, and the DCI of the sixth format may be a DCI of a second format detected in a USS; alternatively, the DCI of the fifth format may be a DCI of a third format detected in the USS, and the DCI of the sixth format may be a DCI of a fourth format detected in the USS; alternatively, the DCI of the fifth format may be a DCI of a third format detected in the CSS, and the DCI of the sixth format may be a DCI of a fourth format detected in the CSS.

In a third aspect, an embodiment of the present application provides a communication apparatus, where the communication apparatus may be a terminal device, may also be an apparatus in a terminal, or may be an apparatus capable of being used in cooperation with a terminal. In one design, the apparatus may include a module corresponding to one or more of the methods/operations/steps/actions described in the first aspect or the second aspect, where the module may be a hardware circuit, a software circuit, or a combination of a hardware circuit and a software circuit.

In one possible design, the communications apparatus may include a detection module to detect downlink control information, DCI, from a network device, where the DCI is to schedule a physical data channel, a format of the DCI to schedule the physical data channel including a plurality of DCI formats; the types of the DCI sizes corresponding to the plurality of DCI formats are less than or equal to N, wherein N is a positive integer less than or equal to 3; and/or when the DCI corresponding to the plurality of DCI formats is scrambled by using a terminal-specific Radio Network Temporary Identifier (RNTI), the kinds of DCI sizes corresponding to the plurality of DCI formats are less than or equal to M, and M is a positive integer less than or equal to 2.

In a possible design, the specific format included in the multiple DCI formats and the alignment manner of the multiple DCI formats may refer to the specific description of the DCI format in the first aspect, which is not described herein again.

In one possible design, the communications apparatus may include a detection module to detect downlink control information, DCI, from a network device, where the DCI is to schedule a physical data channel, a format of the DCI to schedule the physical data channel including a plurality of DCI formats; the DCI size corresponding to a sixth format of the multiple DCI formats is aligned to the DCI size corresponding to a fifth format of the multiple DCI formats, where the DCI corresponding to the fifth format is used to schedule uplink transmission and the DCI corresponding to the sixth format is used to schedule downlink transmission.

In a possible design, the fifth format and the sixth format and other definitions of the alignment manner between the fifth format and the sixth format may be referred to in the detailed description of the second aspect, and are not described herein again.

A fourth aspect of the present application provides a communication apparatus, which may be a terminal device, an apparatus in a terminal, or an apparatus capable of being used with a terminal. The apparatus comprises a processor for implementing the method described in the first or second aspect above. The apparatus may also include a memory to store instructions and data. The memory is coupled to the processor, and the processor, when executing the instructions stored in the memory, may implement the method described in the first aspect or the second aspect. The apparatus may also include a communication interface for the apparatus to communicate with other devices, such as a transceiver, circuit, bus, module, pin, or other type of communication interface, which may be network devices.

In one possible design, the apparatus includes: a memory for storing program instructions; a processor configured to detect downlink control information, DCI, from a network device using a communication interface, wherein the DCI is used to schedule a physical data channel, and a format of the DCI used to schedule the physical data channel includes a plurality of DCI formats; the types of the DCI sizes corresponding to the plurality of DCI formats are less than or equal to N, wherein N is a positive integer less than or equal to 3; and/or when the DCI corresponding to the plurality of DCI formats is scrambled by using a terminal-specific Radio Network Temporary Identifier (RNTI), the kinds of DCI sizes corresponding to the plurality of DCI formats are less than or equal to M, and M is a positive integer less than or equal to 2.

In one possible design, the apparatus includes: a memory for storing program instructions; a processor configured to detect downlink control information, DCI, from a network device using a communication interface, wherein the DCI is used to schedule a physical data channel, and a format of the DCI used to schedule the physical data channel includes a plurality of DCI formats; the DCI size corresponding to a sixth format of the multiple DCI formats is aligned to the DCI size corresponding to a fifth format of the multiple DCI formats, where the DCI corresponding to the fifth format is used to schedule uplink transmission and the DCI corresponding to the sixth format is used to schedule downlink transmission.

In another possible design, the communication device may be implemented in the form of a chip.

A fifth aspect of the present application provides a chip system, which includes a processor and may further include a memory, and is configured to implement the method described in the first aspect or the second aspect. The chip system may be formed by a chip, and may also include a chip and other discrete devices.

A sixth aspect of the present application provides a computer-readable storage medium, which includes instructions that, when executed on a computer, cause the computer to perform a method as in the first aspect or any one of the possible implementations of the first aspect or the second aspect, or any one of the possible implementations of the second aspect.

A seventh aspect of the present application provides a computer program product, which includes instructions that, when executed on a computer, cause the computer to perform the method according to the first aspect or any one of the possible implementations of the first aspect or the second aspect, or any one of the possible implementations of the second aspect.

In an eighth aspect, an embodiment of the present application provides a communication method, including: sending Downlink Control Information (DCI) to a terminal, wherein the DCI is used for scheduling a physical data channel, and the format of the DCI used for scheduling the physical data channel comprises a plurality of DCI formats; the types of the DCI sizes corresponding to the plurality of DCI formats are less than or equal to N, wherein N is a positive integer less than or equal to 3; and/or when the DCI corresponding to the plurality of DCI formats is scrambled by using a terminal-specific Radio Network Temporary Identifier (RNTI), the kinds of DCI sizes corresponding to the plurality of DCI formats are less than or equal to M, and M is a positive integer less than or equal to 2.

In a ninth aspect, an embodiment of the present application provides a communication method, including: the network equipment sends Downlink Control Information (DCI) to a terminal, wherein the DCI is used for scheduling a physical data channel, and the format of the DCI used for scheduling the physical data channel comprises a plurality of DCI formats; the DCI size corresponding to a sixth format of the multiple DCI formats is aligned to the DCI size corresponding to a fifth format of the multiple DCI formats, where the DCI corresponding to the fifth format is used to schedule uplink transmission and the DCI corresponding to the sixth format is used to schedule downlink transmission.

In a tenth aspect, an embodiment of the present application provides a communication apparatus, where the communication apparatus may be a network device, may also be an apparatus in a network device, or may be an apparatus capable of being used in cooperation with a network device. In one design, the apparatus may include a module corresponding to one or more of the methods/operations/steps/actions described in the eighth aspect or the ninth aspect, where the module may be a hardware circuit, a software circuit, or a combination of a hardware circuit and a software circuit.

In one possible design, the communications apparatus may include a transmitting module configured to transmit downlink control information, DCI, to a terminal, wherein the DCI is used to schedule a physical data channel, and a format of the DCI used to schedule the physical data channel includes a plurality of DCI formats; the types of the DCI sizes corresponding to the plurality of DCI formats are less than or equal to N, wherein N is a positive integer less than or equal to 3; and/or when the DCI corresponding to the plurality of DCI formats is scrambled by using a terminal-specific Radio Network Temporary Identifier (RNTI), the kinds of DCI sizes corresponding to the plurality of DCI formats are less than or equal to M, and M is a positive integer less than or equal to 2.

In a possible design, the specific format included in the multiple DCI formats and the alignment manner of the multiple DCI formats may refer to the specific description of the DCI format in the eighth aspect, which is not described herein again.

In one possible design, the communications apparatus may include a transmitting module configured to transmit downlink control information, DCI, to a terminal, wherein the DCI is used to schedule a physical data channel, and a format of the DCI used to schedule the physical data channel includes a plurality of DCI formats; the DCI size corresponding to a sixth format of the multiple DCI formats is aligned to the DCI size corresponding to a fifth format of the multiple DCI formats, where the DCI corresponding to the fifth format is used to schedule uplink transmission and the DCI corresponding to the sixth format is used to schedule downlink transmission.

In a possible design, the fifth format and the sixth format and other definitions of the alignment manner between the fifth format and the sixth format may be referred to in the detailed description of the ninth aspect, and are not described herein again.

An eleventh aspect of the present application provides a communication device comprising a processor for implementing the method described in the above eighth or ninth aspect. The communication device may also include a memory for storing instructions and data. The memory is coupled to the processor, and the processor can implement the method described in the above eighth aspect or ninth aspect when executing the instructions stored in the memory. The communication apparatus may further include a communication interface for the apparatus to communicate with other devices, such as a transceiver, circuit, bus, module, pin, or other type of communication interface, which may be terminal devices.

In one possible design, the communication device includes: a memory for storing program instructions; a processor, configured to transmit downlink control information DCI to a terminal device using a communication interface, where the DCI is used for scheduling a physical data channel, and a format of the DCI used for scheduling the physical data channel includes multiple DCI formats; the types of the DCI sizes corresponding to the plurality of DCI formats are less than or equal to N, wherein N is a positive integer less than or equal to 3; and/or when the DCI corresponding to the plurality of DCI formats is scrambled by using a terminal-specific Radio Network Temporary Identifier (RNTI), the kinds of DCI sizes corresponding to the plurality of DCI formats are less than or equal to M, and M is a positive integer less than or equal to 2.

In one possible design, the communication device includes: a memory for storing program instructions; a processor, configured to transmit downlink control information DCI to a terminal device using a communication interface, where the DCI is used for scheduling a physical data channel, and a format of the DCI used for scheduling the physical data channel includes multiple DCI formats; the DCI size corresponding to a sixth format of the multiple DCI formats is aligned to the DCI size corresponding to a fifth format of the multiple DCI formats, where the DCI corresponding to the fifth format is used to schedule uplink transmission and the DCI corresponding to the sixth format is used to schedule downlink transmission.

A twelfth aspect of the present application provides a chip system, including: the processor may further comprise a memory for implementing the method described in the eighth aspect or the ninth aspect. The chip system may be formed by a chip, and may also include a chip and other discrete devices.

A thirteenth aspect of the present application provides a computer-readable storage medium including instructions that, when executed on a computer, cause the computer to perform a method as in any one of the possible implementations of the eighth aspect or any one of the possible implementations of the ninth aspect or the ninth aspect of the embodiments of the present application.

A fourteenth aspect of the present application provides a computer program product comprising instructions that, when executed on a computer, cause the computer to perform the method according to any one of the possible implementations of the eighth aspect or any one of the possible implementations of the ninth aspect or the ninth aspect of the embodiments of the present application.

In a fifteenth aspect, an embodiment of the present application provides a communication system, including the apparatus of the third aspect or the fourth aspect, and the apparatus of the tenth aspect or the eleventh aspect.

Drawings

Fig. 1 shows DCI size categories obtained by a alignment method;

fig. 2 is a schematic diagram of a communication system according to an embodiment of the present disclosure;

FIG. 3 is a schematic diagram of an embodiment of the communication method of the present application;

FIG. 4 is a schematic diagram of another embodiment of the communication method of the present application;

FIG. 5a is a flow chart of a possible refinement of step 402 in FIG. 4;

fig. 5b shows the format and scrambling pattern corresponding to the DCI sent to the UE1 after the gNB executes the scheme of fig. 5 a;

FIG. 6a is a flow chart of another possible refinement of step 402 in FIG. 4;

fig. 6b shows the format and scrambling pattern corresponding to the DCI sent to the UE1 after the gNB executes the scheme of fig. 6 a;

FIG. 7a is a flow chart of another possible refinement of step 402 in FIG. 4;

fig. 7b shows the format and scrambling pattern corresponding to the DCI sent to the UE1 after the gNB executes the scheme of fig. 7 a;

FIG. 8a is a flow chart of another possible refinement of step 402 in FIG. 4;

fig. 8b shows the format and scrambling pattern corresponding to the DCI sent to the UE1 after the gNB executes the scheme of fig. 8 a;

FIG. 9a is a flow chart of another possible refinement of step 402 in FIG. 4;

fig. 9b shows the format and scrambling pattern corresponding to the DCI sent to the UE1 after the gNB executes the scheme of fig. 9 a;

FIG. 10 is a schematic diagram of a possible structure of a UE of the present application;

FIG. 11 is a schematic diagram of a possible structure of the communication device of the present application;

FIG. 12 is a schematic diagram of a possible structure of a network device according to the present application;

fig. 13 is a schematic diagram of another possible structure of the communication device of the present application.

Detailed Description

The embodiment of the application provides a communication method and device. Embodiments of the present application are described below with reference to the accompanying drawings.

The technical solution of the embodiments of the present application may be applied to various wireless communication systems or networks, for example: a Long Term Evolution (LTE) system, an LTE Frequency Division Duplex (FDD) system, an LTE Time Division Duplex (TDD), a fifth generation (5th generation, 5G) system, a future introduced communication system, or a combination of multiple systems. Among them, 5G may also be referred to as New Radio (NR).

The network device in the embodiments of the present application may be, for example, an access node and/or other network entities, for example, although not shown, an access network may include a Central Unit (CU) and a Distributed Unit (DU). The access node in this embodiment may be an evolved node B (evolved NodeB, eNB, or eNodeB) in an LTE system, or may also be a wireless controller in a Cloud Radio Access Network (CRAN) scenario. Alternatively, the access node in the embodiment of the present application may be a relay station, an access point, a vehicle-mounted device, a wearable device, a base station in a 5G network, or a base station in a PLMN network that is evolved in the future, and the like. The base station in the 5G network may be referred to as a next generation base station (gNB), and the embodiment of the present invention is not limited thereto. In the embodiment of the present application, the apparatus for implementing the function of the network device may be a network device; or may be a device, such as a system-on-chip, capable of supporting the network device to implement the function, and the device may be installed in the network device. In the technical solution provided in the embodiment of the present application, a device for implementing a function of a network device is taken as an example of a network device, and the technical solution provided in the embodiment of the present application is described.

The terminal device in the embodiment of the present application may be referred to as a terminal, and may be a device with a wireless transceiving function, which may be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; can also be deployed on the water surface (such as a ship and the like); and may also be deployed in the air (e.g., airplanes, balloons, satellites, etc.). The terminal device may be a User Equipment (UE), wherein the UE includes a handheld device, a vehicle-mounted device, a wearable device, or a computing device having wireless communication functionality. Illustratively, the UE may be a mobile phone (mobile phone), a tablet computer, or a computer with wireless transceiving function. The terminal device may also be a Virtual Reality (VR) terminal device, an Augmented Reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in unmanned driving, a wireless terminal in telemedicine, a wireless terminal in smart grid, a wireless terminal in smart city (smart city), a wireless terminal in smart home (smart home), and so on. In the embodiment of the present application, the apparatus for implementing the function of the terminal may be a terminal; it may also be a device, such as a system-on-chip, capable of supporting the terminal to implement the function, which may be installed in the terminal. 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. In the technical solution provided in the embodiment of the present application, a device for implementing a function of a terminal is a terminal, and the terminal is a UE as an example, the technical solution provided in the embodiment of the present application is described.

The technical scheme provided by the embodiment of the application can be applied to wireless communication among communication devices. The wireless communication between the communication devices may include: wireless communication between a network device and a terminal, wireless communication between a network device and a network device, and wireless communication between a terminal and a terminal. In the embodiments of the present application, the term "wireless communication" may also be simply referred to as "communication", and the term "communication" may also be described as "data transmission", "information transmission", or "transmission". The technical solution can be used for performing wireless communication between a scheduling entity (e.g., a network device) and a subordinate entity (e.g., a UE), and those skilled in the art can use the technical solution provided in the embodiments of the present application for performing wireless communication between other scheduling entities and subordinate entities, for example, wireless communication between a macro base station and a micro base station, for example, wireless communication between a first terminal and a second terminal. Wherein the scheduling entity may allocate resources for subordinate entities and/or the scheduling entity may control wireless communication therebetween.

The information exchanged between the UE and the network device is carried over a physical channel. Control information, such as Downlink Control Information (DCI), sent by the network device to the UE may be carried by a Physical Downlink Control Channel (PDCCH); data sent by the network device to the UE, that is, downlink data, may be carried by a Physical Downlink Shared Channel (PDSCH); data, that is, uplink data, sent by the UE to the network device may be carried through a Physical Uplink Shared Channel (PUSCH). The physical channel for carrying the DCI may also be a channel with another name, for example, an Enhanced Physical Downlink Control Channel (EPDCCH); the channel for carrying downlink data at the physical layer may be a channel of other name than the PDSCH; the channel for carrying the uplink data in the physical layer may be a channel with other names except for the PUSCH, and the embodiment of the present application is not limited.

In a wireless communication system, such as an NR communication system, a network device may configure a bandwidth part (BWP) for a UE from a system bandwidth or a carrier bandwidth, and the UE and the network device perform information interaction in the BWP. BWP may be understood as a frequency domain operation interval configured by the network device for the UE, including frequency domain range and subcarrier spacing. One BWP may be used only for transmitting upstream data, which may be referred to as an upstream BWP; or one BWP may be used only for transmitting downstream data, which may be referred to as a downstream BWP; for a time division duplex system, the upstream BWP and the downstream BWP are often configured in pairs, and their center frequency points are the same. The network device may configure one or more BWPs for the UE. The UE may receive one or more of the following channels from the network device in downlink BWP: PDCCH, PDSCH, and uplink demodulation reference signal. In uplink BWP, the UE may send one or more of the following channels to the network device: PUSCH, PUCCH, and downlink demodulation reference signals.

In configuring BWP for a UE, a network device may perform channel configuration on a channel transmitted in the BWP. Taking configuring downlink BWP as an example, the network device may perform PDSCH configuration and PDCCH configuration. Wherein configuring the PDCCH includes configuring a search space and a control resource set (CORESET) of the PDCCH. Optionally, configuring the PDCCH further includes configuring a DCI format that the UE needs to detect in each search space.

The network device may configure multiple BWPs for the UE and activate one or more BWPs therefrom, and the network device may transmit PDSCH, PUSCH, and/or PDCCH with the UE on the activated BWPs and may not transmit PDSCH, PUSCH, and PDCCH with the UE on the inactive BWPs.

In a possible implementation, some or all of the BWP configuration information may also be preset, i.e. the information is known to the network device and the UE in advance.

DCI in a plurality of different formats may be supported in a communication system. A plurality of indication fields may be included in one DCI, each indication field corresponding to a respective indication function. One or more different indication fields may be included between corresponding DCIs of different DCI formats. From the direction of transmission, DCI can be divided into: DCI for scheduling Downlink (DL) transmission and DCI for scheduling Uplink (UL) transmission; from the viewpoint of whether it is independent of UE-specific higher layer signaling configuration, or from the viewpoint of DCI functionality, DCI can be classified into: fallback DCI, non-fallback DCI. Wherein, the fallback DCI may also be referred to as fallback DCI, and the non-fallback DCI may also be referred to as non-fallback DCI.

The format of the DCI scheduling downlink transmission may be different from the format of the DCI scheduling uplink transmission, and the format of the fallback DCI may be different from the format of the non-fallback DCI.

The fallback DCI is hardly dependent on the higher layer signaling configuration of the UE, and it includes an indication field and the size of each field is only related to the configuration common to the cells, or is predefined; and the number of indication fields included in the non-fallback DCI and the size of the fields are usually determined according to the higher layer signaling configuration of the UE. Non-fallback DCI can indicate more functions than fallback DCI can indicate. Table 1 gives an example of a format classification of DCI for scheduling PDSCH and PUSCH.

TABLE 1

The DCI sizes may be different for different DCI formats. The DCI size specifically refers to a payload size (payload size) of the DCI, or a number of bits included in the DCI. And the network equipment sends the PDCCH in the time-frequency resource indicated by the CORESET and the search space, and correspondingly, the UE carries out blind detection on the DCI carried in the PDCCH according to the DCI size corresponding to the DCI format to be detected in the time-frequency resource determined according to the CORESET and the search space. The procedure of receiving or detecting DCI may also be referred to as a procedure of receiving or detecting PDCCH.

Generally, in one search space, the UE may be configured to detect 1 or 2 formats of DCI. However, since time-frequency resource locations of different search spaces may overlap together, the UE may need to detect DCI of more various formats in the same resource location. The more DCI formats are, the more types of DCI sizes that the UE needs to detect are, the more times the PDCCH is blindly detected is, the larger the UE overhead is, and the higher the power consumption of the UE is.

In a communication system, a search space of a PDCCH may be divided into a Common Search Space (CSS) and a UE-specific search space (USS) according to the property of the search space of the PDCCH. The DCI transmitted in the CSS may be received by all UEs in the cell, and the DCI transmitted in the USS may be received by a specific UE or UE group; alternatively, the DCI transmitted in the CSS may be received by a group of UEs, and the DCI transmitted in the USS may be received by one specific UE. One UE group includes one or more UEs, which is not limited in the embodiments of the present application. The fallback DCI may be transmitted in the CSS; in the USS, fallback and non-fallback DCI may be sent.

Illustratively, the search space of the PDCCH may be configured (indicated) by the network device for the UE through Radio Resource Control (RRC) signaling. On one BWP for the UE, the network device may configure one or more search spaces for the UE. For a UE, the RRC signaling may be specific to the UE, or may be shared (common) with other UEs, and the embodiments of the present application are not limited thereto.

For one search space, the network device may configure the UE whether the type of search space is a common search space or a UE-specific search space. Furthermore, the network device may also configure one or more of the following parameters of the search space for the UE: frequency domain resource position, aggregation level size, number of candidate PDCCHs, detection period, time domain resource position, and format of DCI transmitted in the search space. For example, formats of DCI in one common search space may be configured to be 0_0 and 1_ 0. For another example, the formats of DCI in one UE-specific search space may be configured to be 0_1 and 1_1, or the formats of DCI in one UE-specific search space may be configured to be 0_0 and 1_ 0. Wherein, the time domain resource location includes: the search space is offset by a first time unit (e.g., slot) in the detection period, the number of consecutive first time units occupied by the search space in the detection period, the offset of a second time unit (e.g., symbol) of the search space in each first time unit, and the number of second time units occupied by the search space in each first time unit.

Optionally, the frequency domain resource location of the search space and the number of the second time units of the search space in each first time unit may be configured as follows: the network device indicates, for the UE, a control resource set (CORESET) corresponding to the search space, and a parameter of the CORESET may be regarded as a parameter of the search space. The network device indicates, through RRC signaling, that of the CORESET: frequency domain resource location, and the number of second time units of the CORESET in each first time unit. Optionally, one CORESET may correspond to one search space, or may correspond to a plurality of different search spaces, which is not limited in the embodiment of the present application.

Illustratively, the search space a corresponds to CORESET a, which occupies 3 symbols in the time domain. The detection period of the search space a is 10 slots, the offset of the search space a in the detection period is 3 slots, the consecutive slots occupied by the search space a in the detection period are 2 slots, and the symbol offset of the search space a in each slot is 3 symbols. Then the frequency domain resource location of the search space a is the frequency domain resource location of CORESET a, and the time domain resource location of the search space a is: in each of 10 slots, 3 symbols are occupied in total starting from the 3 rd symbol in each of the 4 th and 5th slots. The time-frequency resources resulting from the frequency-domain resource locations and time-domain resource locations of search space a may be referred to as the time-frequency resources indicated by search space a and CORESET a.

When the network device sends DCI to the UE, such as fallback DCI or non-fallback DCI, if the DCI is used to schedule UE-specific data transmission (e.g., schedule PDSCH or PUSCH on which data transmitted is specific to the UE), the DCI may be scrambled using a Radio Network Temporary Identity (RNTI). The UE-specific RNTI may be a cell RNTI (C-RNTI), a configured scheduling RNTI (CS-RNTI), or a modulation and coding scheme cell RNTI (MCS-C-RNTI) of the UE. The C-RNTI is an important identification for a network device (such as a base station) to identify the UE in an access network layer, and the base station scrambles DCI by using the C-RNTI, which is equivalent to encrypted transmission of the DCI between the base station and the UE through the C-RNTI. The detection capability of the DCI scrambled by the C-RNTI embodies the basic capability of the UE for detecting the DCI transmitted by the base station to a certain extent.

The network device may send the returned DCI to the UE for scheduling a cell system message, scheduling a group of UEs, or scheduling a non-connected UE, and at this time, the DCI may be scrambled using a common RNTI such as a system information RNTI (SI-RNTI), a paging RNTI (P-RNTI), or a random access RNTI (RA-RNTI). The unconnected state may also be considered to be an idle (idle) state or an inactive (inactive) state. The connected state may be considered an activated (active) state. From the perspective of whether an RRC connection is established between the UE and the network device, the connected state is also referred to as an RRC connected (connected) state, and the unconnected state includes an RRC inactive state and an RRC idle state.

In one possible implementation:

in the fallback DCI sent in the CSS, for example, the DCI with formats 0_0 and 1_0, the network device aligns sizes of the DCI with the two formats in a zero padding or puncturing manner, so that DCI sizes with different DCI formats are the same, and DCI format 0_0 aligns the sizes to DCI format 1_ 0; network equipment aligns sizes of backspacing DCIs sent in the USS, specifically, the smaller one of DCI format 0_0 and DCI format 1_0 is aligned to the larger one in a zero padding mode;

for non-fallback DCI sent in USS, e.g. formats between 0_1 and 1_1, the network device does not do any way of aligning.

Fig. 1 shows an example of the DCI size types defined above, and if the DCI sizes corresponding to the DCI formats in the same dashed line frame are different, the DCI sizes are aligned to be the same. The RNTI in the parentheses after the DCI format represents the RNTI that may be used to scramble the DCI of the corresponding format.

Further, it may be provided that:

if the DCI size category corresponding to the DCI format that the UE needs to detect exceeds 4, or the DCI size category scrambled by the C-RNTI exceeds 3, the network device aligns the fallback DCI size in the USS to the fallback DCI size in the CSS, referring to the curve with an arrow in fig. 1.

In fig. 1, it is assumed that DCI format 0_1 and DCI format 1_1 in the USS are different in size, and the DCI size of the DCI scrambled by the C-RNTI that the UE needs to detect is 4, where the 4 types of DCI correspond to the DCI formats scrambled by the C-RNTI in the 4 dashed boxes in fig. 1. Since the types of DCI sizes of the DCI scrambled by the C-RNTI that the UE needs to detect exceed 3, as shown by the curve with an arrow in fig. 1, DCI format 0_0 and DCI format 1_0 in the USS are aligned with DCI format 0_0 and DCI format 1_0 in the CSS, and after the alignment, the types of DCI sizes of the DCI scrambled by the C-RNTI that the UE needs to detect are 3. This alignment result is one of the most common.

There may actually be other results, for example, the sizes of DCI format 0_1 and DCI format 1_1 in USS are the same without a pulling operation; alternatively, the size of DCI format 0_1 or DCI format 1_1 in the USS is the same as the size of DCI format 0_0 or DCI format 1_0 in the USS, and in this case, the number of types of DCI sizes scrambled by C-RNTI does not exceed 3, so the alignment operation is not required.

In the method, only the size types of the DCI can be limited to be not more than 4, and the size types of the DCI scrambled by using the C-RNTI are limited to be not more than 3, so that the UE still has more size types of the DCI to be detected, the UE still has more blind detection times in the process of carrying out blind detection on the PDCCH at each resource position, the UE occupies larger calculation amount and storage amount in the detection process, and the complexity of the UE is improved.

In order to meet the requirements of low-cost and low-complexity terminals in the scenarios of industrial sensor networks, wearable Devices, etc., a Reduced Capability (redcapability) UE, formally called Reduced Capability NR Devices (NR-redcapability) UE, is to be supported in an NR communication system. In the standard discussion process, there are light (NR-light) UEs, large machine type communication (NR mtc) UEs, and so on. Illustratively, the maximum bandwidth supported by the REDCAP UE is smaller than that of the legacy UE, and/or the number of antennas supported is smaller than that of the legacy UE. In order to solve the above problem, especially considering reducing complexity of the redtap UE, the present application provides a communication method and apparatus to reduce PDCCH detection times of the UE (especially the redtap UE), thereby reducing complexity of the UE. The method may be applied to REDCAP UE, and may also be applied to other types of UEs, such as UE supporting enhanced Mobile Broadband (eMBB) service or UE supporting (URLLC) service, for reducing power consumption of the UE, which is not limited in the embodiment of the present application.

An exemplary system architecture for application of the present application is first described below.

The embodiments of the present application may be applied to an NR communication system, and may also be applied to other communication systems as long as a transmitting entity and a receiving entity of downlink control information exist in the communication system.

Fig. 2 is a schematic diagram of a communication system provided in an embodiment of the present application, where as shown in fig. 2, the communication system includes a network device and UEs 1 to 5. In the communication system, the UEs 1 to 5 may send uplink data to the network device, and the network device may receive the uplink data sent by the UEs 1 to 5; the network device may send downlink data to the UEs 1 to 5, and the UEs 1 to 5 may receive the downlink data sent by the network device. In addition, the UE4 and the UE5 may form a sub-communication system, the UE5 may forward downlink information to the UE4 after receiving the downlink information sent by the network device, the UE4 may send uplink data to the UE5, and the UE5 forwards the uplink data to the network device.

That is to say, the downlink data received by the UE in the communication system may be directly sent to the UE by the network device, or may be forwarded to the UE by other communication nodes in the communication system; the uplink data sent by the UE may be directly sent to the network device, or may be forwarded to the network device by other communication nodes in the communication system.

The following describes a communication method provided in an embodiment of the present application.

Fig. 3 is a schematic diagram of a communication method provided in an embodiment of the present application, and referring to fig. 3, a possible embodiment of the communication method of the present application may include the following steps:

301. the network equipment sends DCI to the UE;

302. the UE detects DCI from the network equipment;

in fig. 3, steps 301 and 302 are represented simultaneously by the line segment with an arrow between the network device and the UE.

The network device may send DCI to the UE, which the UE may detect. The DCI is used to schedule a physical data channel, and the format of the DCI used to schedule the physical data channel includes a plurality of DCI formats. Wherein, the size of DCI used for scheduling physical data channel is not more than N, N is a positive integer less than or equal to 3, and/or the size of DCI scrambled by using UE-specific Radio Network Temporary Identifier (RNTI) is not more than M, M is a positive integer less than or equal to 2.

That is, the types of DCI sizes corresponding to the multiple DCI formats may be in any one of the following three cases:

1) the types of DCI sizes corresponding to the plurality of DCI formats are less than or equal to N, wherein N is a positive integer less than or equal to 3, and when the DCIs corresponding to the plurality of DCI formats are scrambled by using the UE-specific Radio Network Temporary Identifier (RNTI), the types of DCI sizes corresponding to the plurality of DCI formats are less than or equal to M, and M is a positive integer less than or equal to 2.

2) The types of the DCI sizes corresponding to the plurality of DCI formats are less than or equal to N, wherein N is a positive integer less than or equal to 3.

3) When DCIs corresponding to the plurality of DCI formats are scrambled by using a UE-specific Radio Network Temporary Identifier (RNTI), the types of DCI sizes corresponding to the plurality of DCI formats are less than or equal to M, and M is a positive integer less than or equal to 2.

Because the size of the DCI used for scheduling the physical data channel does not exceed N, wherein N is a positive integer less than or equal to 3, and/or the size of the DCI scrambled by the radio network temporary identifier RNTI specific to the UE does not exceed M, and M is a positive integer less than or equal to 2, the size of the DCI is reduced, the PDCCH detection times of the UE are favorably reduced, and the complexity of the UE is further reduced.

In one possible implementation manner, regarding that "the number of DCI sizes corresponding to multiple DCI formats is less than or equal to N, where N is a positive integer less than or equal to 3", it can be understood that, when the DCIs corresponding to multiple DCI formats are scrambled using the common RNTI or the UE-specific RNTI, the number of DCI sizes corresponding to multiple DCI formats is less than or equal to N, where N is a positive integer less than or equal to 3. Alternatively, it can also be described as: the plurality of DCI formats may correspond to a plurality of DCIs, one of the plurality of DCIs may be scrambled using any one of a common RNTI or a UE-specific RNTI, different DCIs of the plurality of DCIs may be scrambled using the same kind or different kinds of RNTIs, a kind of DCI size corresponding to the plurality of DCIs less than or equal to N, N being a positive integer less than or equal to 3.

In one possible implementation manner, the type of the DCI size corresponding to the multiple DCI formats is less than or equal to N, where N is a positive integer less than or equal to 3; and/or when the DCIs corresponding to the multiple DCI formats are scrambled by using the UE-specific Radio Network Temporary Identifier (RNTI), the types of the DCI sizes corresponding to the multiple DCI formats are less than or equal to N-L, N is a positive integer less than or equal to 3, L is a positive integer less than N, and L is 1 or 2, for example.

The physical data channel is used for transmitting uplink data (e.g., the physical data channel is a PUSCH), or is used for transmitting downlink data (e.g., the physical data channel is a PUSCH), or includes a physical channel for transmitting uplink data (e.g., a PUSCH) and a physical channel for transmitting downlink data (e.g., a PDSCH).

The DCI used to schedule the PDSCH may indicate one or more of the following transmission parameters of the PDSCH: DCI format indication, BWP indication, frequency domain resource allocation, time domain resource allocation, Virtual RB (VRB) to Physical RB (PRB) mapping, modulation and coding strategy, new data indication, redundancy version, hybrid automatic repeat request (HARQ) process number, downlink allocation index, PUCCH transmit power control command, PUCCH resource indication, PDSCH to HARQ feedback time indication, antenna port, Sounding Reference Signal (SRS) request, transmission configuration indication, and demodulation reference signal (DMRS) sequence initialization. The transmission parameter of the PDSCH may also be referred to as PDSCH indication information.

The DCI used to schedule the PUSCH may indicate one or more of the following transmission parameters of the PUSCH: DCI format indication, BWP indication, frequency domain resource allocation, time domain resource allocation, frequency hopping flag, modulation and coding strategy, new data indication, redundancy version, HARQ process number, downlink allocation index, PUSCH transmit power command, antenna port, SRS request, Channel State Information (CSI) request, Beta coefficient (Beta) offset indication, DMRS sequence initialization, uplink shared channel (UL-SCH) indication, and UL/Supplemental Uplink (SUL) indication. The transmission parameter of the PUSCH may also be referred to as indication information of the PUSCH.

After step 302, the UE may transmit a corresponding physical data channel according to the detected DCI.

For example, assuming that DCI detected by the UE is used for scheduling the PDSCH, the UE may receive the PDSCH transmitted by the network device according to the transmission parameters of the PDSCH in the DCI. Assuming that DCI detected by the UE is used for scheduling PUSCH, the UE may transmit PUSCH to the network device according to the transmission parameters of PUSCH in the DCI.

For convenience of description, the DCI detected by the UE in step 302 and transmitted by the network device in step 301 is referred to as DCI _ b, and a DCI format corresponding to DCI _ b is referred to as format a.

In one possible implementation, the size of the DCI _ b meets the requirement, and the DCI _ b and the DCI _ a are the same without performing alignment operations such as puncturing or zero padding on the DCI _ b. DCI _ a is the original DCI without the alignment operation according to format a.

In a possible implementation manner, before step 301, the network device obtains DCI _ a according to format a, and the network device adjusts the size of DCI _ a according to a alignment rule to obtain DCI _ b. The DCI _ a and the DCI _ b have different loads, but the DCI formats corresponding to the DCI _ a and the DCI _ b are the same, and are both format a.

In step 301, the network device transmits DCI _ b.

Before step 302, the UE may determine the adjusted size of each DCI format according to the alignment rule, including determining the DCI size corresponding to format a. Optionally, DCI corresponding to format a may satisfy the requirement without performing a leveling operation.

In step 302, the UE may detect DCI carried by the PDCCH according to the adjusted size of each determined DCI format, including detecting DCI _ b carried by the PDCCH according to the DCI size corresponding to the adjusted format a.

In one possible implementation manner, in step 302, the UE may decode DCI _ b according to the alignment rule. For example, the DCI _ b is restored to the DCI _ a, and then the DCI _ a is decoded to obtain the transmission parameters carried by the DCI _ b.

The network equipment limits the size of DCI (Downlink control information) used for scheduling the physical data channel, which is sent by the network equipment, to be less than or equal to N, wherein N is a positive integer less than or equal to 3, by performing a pull-up operation on DCI corresponding to part or all of DCI formats used for scheduling the physical data channel according to a pull-up rule; and/or limiting the kind of the size of DCI which is transmitted by the network equipment, scrambled by the network equipment by using the UE-specific Radio Network Temporary Identity (RNTI) and used for scheduling the physical data channel to be less than or equal to M, wherein M is a positive integer less than or equal to 2.

The UE determines the size of each DCI format to be adjusted according to the alignment rule, so that the DCI corresponding to the corresponding DCI format carried in the PDCCH can be successfully detected, and the information in the DCI can be correctly analyzed according to the alignment rule.

The following describes possible alignment schemes provided in the present application for different cases of DCI formats included in DCI for scheduling physical data channels.

First, DCI for scheduling physical data channels includes a third format and a fourth format detected in a terminal-specific search space USS, and the third format and the fourth format detected in a common search space CSS. The DCI corresponding to the third format is used for scheduling uplink transmission (e.g. PUSCH), the DCI corresponding to the fourth format is used for scheduling downlink transmission (e.g. PDSCH), the DCI transmitted in the USS is scrambled using the UE-specific RNTI, and the DCI transmitted in the CSS is scrambled using the UE-specific RNTI or is scrambled using the common RNTI.

In one possible implementation, the third format is 0_0 and the fourth format is 1_ 0.

Illustratively, DCI format 0_0 and DCI format 1_0 include fields and the sizes of the fields are shown in table 2 below:

TABLE 2

The fields of DCI format 0_0 are briefly described as follows:

the DCI format indicates: 1 bit for distinguishing whether the DCI is scheduled for UL transmission or DL transmission, where the field value in 0_0 is 0, indicating that the DCI is scheduled for an UL transmission;

and (3) frequency domain resource allocation: x bits for indicating the frequency domain resources allocated in the scheduling, wherein the specific size of X is related to the bandwidth of UL BWP, specifically

Indicating the number of Physical Resource Blocks (PRBs) included in UL BWP; it can be seen that the larger the UL BWP, the more likely the frequency domain resources are allocated and hence the larger X. For example, when the UL BWP bandwidth is 96 PRBs, X ═ 13, the PUSCH scheduled by the DCI including the frequency domain resource allocation field is transmitted in the UL BWP;

time domain resource allocation: 4 bits for indicating the time domain resources allocated in the scheduling, wherein the state 0-15 represented by the 4 bits indicates a row in a predefined table, and each row represents a certain time domain starting position and length;

frequency hopping flag: 1 bit for indicating whether the UL transmission of the UE is frequency hopped;

modulation and coding strategy: 5 bits for indicating the modulation mode and the coding rate of the PUSCH scheduled this time;

new data indication: 1 bit for indicating whether the data scheduled this time is new data or old data;

redundancy version: 2 bits for indicating the redundancy version of the data scheduled this time; the data can have four redundancy versions of 0, 1, 2 and 3 after being coded;

HARQ process number: 4 bits, which are used to indicate which HARQ process data is scheduled this time;

transmission power control command for PUSCH: 2 bits for indicating an adjustment amount of power for transmitting the PUSCH by the UE;

UL/SUL indicates: 1 bit, which is used to indicate whether the UL transmission of this scheduling is performed on an UL carrier or a Supplemental Uplink (SUL) carrier; alternatively, the domain may exist only when the SUL carrier is configured;

similarly, many fields in DCI format 1_0 have the same meaning as DCI format 0_0, only the UL is changed to DL, which is not described herein, but different fields are introduced:

DCI format indication field: 1 bit for distinguishing whether the DCI is scheduled for UL transmission or DL transmission, where the field value in 1_0 is 1, indicating that the DCI is scheduled for a DL transmission;

and (3) frequency domain resource allocation: y bits, like X bits of the uplink, but for calculating Y, the number of PRBs included in the DL BWP is used

When the UL BWP and DL BWP are the same in size, Y is X;

VRB to PRB mapping: 1 bit, indicating whether interleaving mapping is performed between the VRB and the PRB in the DL transmission;

downlink allocation index: 2 bits, configured to indicate an accumulated downlink transmission number corresponding to a same HARQ-ACK (hybrid automatic repeat request acknowledgement character) feedback scheduled by the network device at the current time;

transmission power control command of PUCCH: 2 bits, configured to indicate an adjustment amount of power of a physical downlink control channel (PUCCH) to be transmitted when the UE performs HARQ-ACK feedback for the currently scheduled PDSCH;

and PUCCH resource indication: 3 bits, which are used for indicating PUCCH resources used by the UE for HARQ-ACK feedback of the PDSCH scheduled this time;

PDSCH-to-HARQ feedback time indication: and 3 bits, which are used to indicate the time interval between the PDSCH scheduled this time and the HARQ feedback of the PDSCH.

In Table 2, p is a positive integer.

In one possible implementation, based on that the DCI size corresponding to the third format detected in the CSS is the same as the DCI size corresponding to the fourth format, or based on that the DCI size corresponding to the third format detected in the CSS is pulled to be the same as the DCI size corresponding to the fourth format, the DCI size corresponding to the third format detected in the USS is aligned to the DCI size corresponding to the third format detected in the CSS or aligned to the DCI size corresponding to the fourth format detected in the CSS, and the DCI size corresponding to the fourth format detected in the USS is aligned to the DCI size corresponding to the third format detected in the CSS or aligned to the DCI size corresponding to the fourth format detected in the CSS, so as to limit the kind of the DCI size for scheduling the physical data channel sent by the network device to be N, where N is a positive integer less than or equal to 3; and/or limiting the kind of the size of DCI which is transmitted by the network equipment and scrambled by the UE-specific Radio Network Temporary Identity (RNTI) and is used for scheduling the physical data channel to be less than or equal to M, wherein M is a positive integer less than or equal to 2.

And secondly, the DCI used for scheduling the physical data channel comprises a first format and a second format detected in the UE-specific search space USS, wherein the DCI corresponding to the first format is used for scheduling uplink transmission (such as PUSCH), the DCI corresponding to the second format is used for scheduling downlink transmission (such as PDSCH), and the DCI transmitted in the USS is scrambled by using the UE-specific RNTI.

In a possible implementation manner, both the DCI corresponding to the first format and the DCI corresponding to the second format are non-fallback DCIs.

For example, the first format may be 0_1, and the second format may be 1_1, but in the embodiments of the present application, the field of the first format is not limited to be the same as 0_1, and the field of the second format is not limited to be the same as 1_ 1. Therefore, in the embodiment of the present application, the first format is denoted as 0_3, and the second format is denoted as 1_ 3. The DCI of the first format and the second format in the present invention may have other identification manners, for example, the first format may be 4_0, the second format may be 4_1, and the like, as long as the first format and the second format are not substantially changed, which is not limited in the present invention.

Table 3 below gives one possible way of defining DCI format 0_3 and DCI format 1_ 3. The fields included in DCI format 0_3 and DCI format 1_3 and the sizes of the fields are as shown in table 3 below:

TABLE 3

The fields of DCI formats 0_3 and 1_3 are described below as follows:

BWP indicates: 0-2 bits for indicating the BWP where the DL (or UL) transmission of the current scheduling is located, where the specific bit number is determined by the DL BWP or UL BWP number configured by the UE;

antenna port: the specific bit number is determined by the DMRS type and the maximum length configured by the UE;

and (3) SRS request: the method is used for triggering the UE to transmit the aperiodic SRS, and the specific bit number is determined by the SRS configuration of the UE;

and CSI request: the method comprises the steps of triggering the UE to carry out aperiodic CSI reporting, wherein the specific bit number is determined by CSI reporting configuration of the UE;

beta offset indicates: the resource is used for indicating the UE to report the CSI information in the PUSCH, and the specific bit number is determined by the indication configuration of Beta offset;

and (3) DMRS sequence initialization: a scrambling code used for indicating initialization of a DMRS sequence of the UE, wherein the specific bit number is determined by the DMRS configuration;

UL-SCH indicates: 1 bit, which is used to indicate whether the UE transmits an uplink shared channel (UL-SCH) on a PUSCH channel in the UL transmission, where the UL-SCH is an uplink shared channel in a logical channel;

transmission configuration indication: that is, a TCI (transmission configuration indication) for indicating the downlink reference signal quasi co-located with the PDSCH or DMRS in the DL transmission, and the specific bit number is determined by the configuration of the TCI.

For the description of other fields in table 3, reference may be made to the above description related to table 2, which is not described herein again.

It should be noted that table 3 may be used as a possible design method of the UL non-fallback and DL non-fallback DCI of the UE, that is, the order of the fields included in the DCI of the first format and the DCI of the second format may be changed, the bit number of each field may be different, or some other fields not listed herein may be included, or some fields may not be included.

In one possible implementation, the DCI size corresponding to the first format is aligned to the DCI size corresponding to the second format.

Alternatively, in a possible implementation, the DCI size corresponding to the second format is aligned to the DCI size corresponding to the first format.

Or, in a possible implementation manner, if the DCI size corresponding to the first format is smaller than the DCI size corresponding to the second format, the DCI size corresponding to the first format is aligned to the DCI size corresponding to the second format; if the DCI size corresponding to the second format is smaller than the DCI size corresponding to the first format, the DCI size corresponding to the second format is aligned to the DCI size corresponding to the first format.

And thirdly, the DCI for scheduling the physical data channel includes a first format, a second format, a third format and a fourth format detected in the UE-specific search space USS. The DCI corresponding to the first format is used for scheduling uplink transmission (such as PUSCH), the DCI corresponding to the third format is used for scheduling uplink transmission (such as PUSCH), and the first format is different from the third format; the DCI corresponding to the second format is used for scheduling downlink transmission (e.g., PDSCH), the DCI corresponding to the fourth format is used for scheduling downlink transmission (e.g., PDSCH), and the second format is different from the fourth format, and the DCI corresponding to each of the formats transmitted in the USS is scrambled using the UE-specific RNTI.

In a possible implementation manner, the first format is the DCI format 0_3, the second format is the DCI format 1_3, the third format is 0_0, and the fourth format is 1_ 0.

In a possible implementation manner, based on that the DCI sizes corresponding to the first format and the second format are the same, or based on that the DCI sizes corresponding to the first format and the second format are aligned, the DCI size corresponding to the third format transmitted in the USS is aligned to the DCI size corresponding to the first format or aligned to the DCI size corresponding to the second format, and the DCI size corresponding to the fourth format is aligned to the DCI size corresponding to the first format or aligned to the DCI size corresponding to the second format.

In any of the examples herein, the following descriptions may be considered to be synonymous with: "the DCI size corresponding to a certain format (referred to as format a) is aligned to the DCI size corresponding to another format (referred to as format B)", "the DCI size corresponding to format a is aligned to the DCI size corresponding to format B", "the DCI size corresponding to format a is aligned using the DCI size corresponding to format B as a standard so that the DCI size corresponding to format a is the same as the DCI size corresponding to format B", "the DCI size corresponding to format a is adjusted, and the adjusted DCI size corresponding to format a is the same as the DCI size corresponding to format B", and the like.

In any embodiment of the present application, aligning the DCI size corresponding to format a to the DCI size corresponding to format B includes the following two ways:

in the method 1, if the DCI size corresponding to the format a is smaller than the DCI size corresponding to the format B, at least one padding bit (e.g., 0 or 1) is padded in the DCI corresponding to the format a, and the padded DCI size corresponding to the format a is the same as the DCI size corresponding to the format B.

Mode 2, if the DCI size corresponding to format a is larger than the DCI size corresponding to format B, K fields of the DCI corresponding to format a are truncated, or at least one bit in the K fields of the DCI corresponding to format a is truncated. The DCI size corresponding to truncated format B is the same as the DCI size corresponding to format a, where K is a positive integer.

In one possible implementation, at least one bit of the upper bits of the truncated field is truncated, and even all bits of the truncated field are truncated.

In one possible implementation, the K fields include at least one of:

the system comprises a frequency domain resource allocation domain, a time domain resource allocation domain, a PUCCH resource indication domain, a PDSCH-HARQ feedback time indication domain, an SRS request domain and a DMRS sequence initialization domain. For example, format a is format 1_3, then the K fields include at least one of: the system comprises a frequency domain resource allocation domain, a time domain resource allocation domain, a PUCCH resource indication domain, an SRS request domain and a PDSCH-to-HARQ feedback time indication domain. For example, format a is format 0_3, then the K fields include at least one of: the system comprises a frequency domain resource allocation domain, a time domain resource allocation domain, an SRS request domain and a DMRS sequence initialization domain.

In order to ensure that the DCI of various formats is accurately notified, the DCI corresponding to the DCI format with a smaller load may be aligned to the DCI corresponding to the DCI format with a larger load, so that the alignment is performed only by adopting the method 1, and the load in the DCI is not lost.

The above-mentioned leveling method will be specifically described below by taking the format a as the second format (e.g. 1_3) and the format B as the first format (e.g. 0_ 3).

With respect to the mode 1: if the DCI size corresponding to DCI format 0_3 is greater than the DCI size corresponding to DCI format 1_3, the network device may fill p padding bits in the DCI corresponding to DCI format 1_3, for example, p "0" or "1" may be filled at the end of the payload, so that the DCI sizes corresponding to the two DCI formats are the same, where p is a positive integer.

If the UE detects DCI corresponding to DCI format 1_3 from the network device, the UE may ignore the last p bits of the DCI load, or truncate the last p bits of the DCI, to obtain DCI corresponding to the unadjusted DCI format 1_ 3.

With respect to the mode 2: if the DCI size corresponding to DCI format 0_3 is smaller than the DCI size corresponding to DCI format 1_3, the network device may truncate at least one bit of at least one field in the DCI corresponding to DCI format 1_3, for example, truncate one or more higher bits of a frequency domain resource allocation field in the DCI corresponding to DCI format 1_3, truncate one or more higher bits of a time domain resource allocation field in DCI format 1_3, truncate all bits of an SRS request field, and the like, so that the DCI sizes corresponding to the two DCI formats are the same.

Assuming that the upper 3 bits of the frequency domain resource allocation field in the DCI corresponding to DCI format 1_3 are truncated, the truncated payload in the field is "11". If the UE detects DCI corresponding to DCI format 1_3 from the network device, the UE may fill a predefined value (e.g., "0") into the upper 3 bits of the frequency domain resource allocation field in the DCI, and consider the value indicated by the field to be "00011".

Alternatively, considering that typical application scenarios of the redtap UE include industrial sensors, video monitoring and the like, the redtap UE is a sensor terminal or a video terminal, and the uplink transmission amount thereof is large, so that the transmission service thereof is dominant. No matter how the relation between the DCI size corresponding to DCI format 0_3 and the DCI size corresponding to DCI format 1_3 is, the DCI size corresponding to DCI format 1_3 is aligned to the DCI size corresponding to DCI format 0_3, that is, the DCI size corresponding to the DCI format scheduled by DL is aligned to the DCI size corresponding to the DCI format scheduled by UL, which is beneficial to protecting the scheduling performance of uplink transmission. Specifically, the method comprises the following steps:

(1) if the bit number of the DCI format 0_3 is greater than that of the DCI format 1_3, the zero padding alignment size in the DCI format 1_3 is not required to truncate any domain of the DCI format 0_3, thereby ensuring accurate indication of the scheduling information of uplink transmission; for example, if the number of bits of DCI format 0_3 is p more than the number of bits of DCI format 1_3 before alignment, p predefined bits (e.g., "0") may be padded at the end of the valid bits of DCI format 1_3 to align DCI format 1_3 to the size of DCI format 0_ 3.

(2) If the number of bits of the DCI format 0_3 is less than that of the DCI format 1_3, some fields in the DCI format 1_3 may be truncated without filling useless bits into the DCI format 0_3, so that the load of the DCI format 0_3 is reduced as much as possible, and the detection reliability is ensured. For example, if the number of bits of DCI format 0_3 is smaller than the number of bits of DCI format 1_3 by q bits before alignment, the high q bits of the specific indication field (e.g., frequency domain resource allocation indication field) of DCI format 1_3 may be truncated to align DCI format 1_3 to the size of DCI format 0_ 3. Wherein q is a positive integer.

In the following, taking the network device in fig. 2 as the gNB and the UE1 as the UE as an example, a possible embodiment of the communication method of the present application is described based on the method described in fig. 3.

Referring to fig. 4, another possible embodiment of the communication method of the present application includes the following steps 401 to 409.

401. The gNB sends RRC configuration information to the UE 1.

The RRC configuration information is used to indicate resource locations of PDCCHs configured for the UE1 (including resource locations of CSSs and USSs), DCI formats required to be detected by the UE1, and the like.

In a possible implementation manner, the communication method provided by the present application may not perform step 401, and the gNB and the UE1 may determine, according to preset or predefined configuration information, a resource location of a PDCCH allocated for the UE1 and a DCI format that the UE1 needs to detect.

402. The gNB determines the alignment rule corresponding to each DCI format that the UE1 needs to detect.

After RRC configuration is performed on UE1 by the gNB, each DCI format that needs to be detected by UE1 is determined, and a padding rule corresponding to each DCI format is determined, where the padding rule may be the padding rule described in the method embodiment related to fig. 3, and the padding rule is used to limit the number of DCI sizes corresponding to each DCI format that needs to be detected by UE1 to be no more than N, where N is a positive integer less than or equal to 3, and/or limit the number of DCI sizes corresponding to each DCI format that are scrambled by using a UE-specific radio network temporary identifier RNTI to be less than or equal to M, where M is a positive integer less than or equal to 2.

403. The UE1 determines the alignment rule corresponding to each DCI format to be detected.

After receiving the RRC configuration information from the gNB, the UE1 determines each DCI format to be detected, and determines a leveling rule corresponding to each DCI format, where the leveling rule is the same as the leveling rule determined by the gNB in step 402.

404. The UE1 determines the size of the aligned DCI corresponding to each DCI format according to the alignment rule.

The UE1 determines, according to the alignment rule, the aligned DCI sizes corresponding to the DCI formats, where the types of the aligned DCI sizes may be the types of DCI sizes corresponding to the multiple DCI formats described in the method embodiment related to fig. 3, where the types of the aligned DCI sizes are not more than N, where N is a positive integer less than or equal to 3, and/or the types of DCI sizes corresponding to the DCI formats scrambled by using the UE-specific radio network temporary identifier RNTI are less than or equal to M, where M is a positive integer less than or equal to 2.

405. The UE1 performs blind detection on the PDCCH according to the RRC configuration information and the size of the aligned DCI corresponding to each DCI format to be detected.

406. And the gNB adjusts the size of the DCI _ a according to the alignment rule to obtain the DCI _ b.

The DCI to be sent by the gNB to the UE1 is referred to as DCI _ a, and the format of the DCI _ a is referred to as format a, so that the gNB adjusts the size of the DCI _ a according to the alignment rule corresponding to format a. In the embodiment of the present application, the adjusted DCI _ a is referred to as DCI _ b. The DCI format indication fields of DCI _ a and DCI _ b both indicate that the formats of both are format a.

The gNB adjusts the size of the DCI _ a according to the alignment rule, which may refer to the adjustment process described in the method embodiment related to fig. 3, and is not described herein again.

The sequence between the execution of steps 402 and 406 by the gNB and the execution of steps 403 to 405 by the UE1 is not limited.

407. The gNB sends DCI _ b to UE1, and UE1 detects DCI _ b.

After the gNB sends DCI _ b to the UE1 through the PDCCH, the UE1 may detect DCI _ b carried in the PDCCH from the gNB according to the adjusted DCI size (the same as the DCI _ b) corresponding to format a at the configured resource location.

408. The UE1 restores DCI _ b to DCI _ a according to the alignment rule.

After detecting the DCI _ b, the UE1 may determine that the format of the DCI _ b is format a according to the DCI format indication field, restore the DCI _ b to the DCI _ a according to the alignment rule corresponding to the format a, and decode the DCI _ a to obtain the transmission parameter carried in the DCI _ a.

409. The UE1 transmits the corresponding physical data channel according to the DCI _ a.

Assuming that DCI _ a detected by UE1 is used to schedule PDSCH, the UE may detect PDSCH transmitted by the network device according to the transmission parameters of PDSCH in DCI _ a. Assuming that DCI _ a detected by UE1 is used to schedule PUSCH, the UE may transmit PUSCH to the network device according to the transmission parameters of PUSCH in DCI _ a.

Step 402 in the corresponding embodiment of fig. 4 is described below.

In the embodiment of the present application, the kind of the size of the DCI for scheduling the physical data channel does not exceed N, where N is a positive integer less than or equal to 3, and/or the kind of the size of the DCI scrambled by the UE-specific radio network temporary identity RNTI does not exceed M, where M is a positive integer less than or equal to 2. Several possible embodiments of step 402 are described below with respect to several possible combinations of values of M and N.

1. The value combination of M and N is as follows: n is 3 and M is 2.

Under the value combination, the size category of DCI required to be detected by the UE1 can be reduced to 3, and/or the size category of DCI scrambled by the specific RNTI of the UE1 required to be detected by the UE can be reduced to 2.

1.1, the DCI formats required to be detected by the UE1 include DCI format 0_0 and DCI format 1_0 transmitted in the CSS, and DCI format 0_0, DCI format 0_3, DCI format 1_0 and DCI format 1_3 transmitted in the USS.

Referring to fig. 5a, step 402 includes the following refinement steps 4021a to 4026 a.

4021a and gNB align the DCI size corresponding to DCI format 0_0 transmitted in CSS with the DCI size corresponding to DCI format 1_ 0.

The reason why the DCI format 0_0 transmitted in the CSS is aligned to the DCI size corresponding to the DCI format 1_0 is to consider that important common information or important configuration information often needs to be issued in the CSS, and therefore accuracy of downlink transmission indication needs to be ensured.

4022a and gNB align the DCI size corresponding to DCI format 0_0 transmitted in the USS with the DCI size corresponding to DCI format 1_ 0.

Aligning the DCI format with a large load by supplementing padding bits from the DCI format with a small load, for example, if the load of 0_0 is less than 1_0 before alignment, 0 is padded in 0_0 until the size of 0_0 is the same as 1_ 0; on the other hand, if the load of 0_0 is larger than 1_0 before alignment, 1_0 is filled with 0 until 1_0 is the same as 0_ 0.

This way, information bits (payload) in any DCI format are not lost, and the accuracy of indication is guaranteed.

In this embodiment, it may be assumed that the DCI size corresponding to DCI format 0_0 transmitted in the USS is smaller than the DCI size corresponding to DCI format 1_0, and therefore, the gNB aligns the DCI size corresponding to DCI format 0_0 transmitted in the USS with the DCI size corresponding to DCI format 1_ 0.

The sequence between step 4021a and step 4022a is not limited in the embodiments of the present application.

4023a, gNB determines whether the size type of DCI is less than or equal to 3, and whether the size type of DCI scrambled by C-RNTI is less than or equal to 2, if not, step 4024a is executed, if yes, the process is ended.

After the step 4021a and the step 4022a, if the size category of DCI required to be detected by the UE1 is less than or equal to 3 and the size category of DCI scrambled by the C-RNTI required to be detected by the UE1 is less than or equal to 2, the step 402 is considered to be completed, i.e., the procedure of the step 402 is ended. If the size category of DCI required to be detected by the UE1 is greater than 3, or the size category of DCI scrambled by the C-RNTI required to be detected by the UE1 is greater than or equal to 2, then step 4024a is performed.

4024a and gNB align DCI format 0_0 and DCI format 1_0 transmitted in USS with DCI format 1_0 transmitted in CSS.

Illustratively, step 4024a may specifically include the following steps 1 to 3.

1. Optionally, padding bits in DCI format 0_0 and DCI format 1_0 in the current USS are removed;

2. optionally by using in CSS

And

substitution in USS

And

so that the bit numbers X and Y of the frequency domain resource allocation domains of DCI format 0_0 and DCI format 1_0 in the USS are the same as DCI format 0_0 and DCI format 1_0 in the CSS;

3. similar to the alignment method between DCI format 0_0 and DCI format 1_0 in CSS, DCI format 0_0 in the USS after step 2 is aligned to DCI format 1_ 0.

Since the DCI size corresponding to DCI format 0_0 transmitted in CSS has been pulled to the DCI size of DCI format 1_0 in step 4021a, step 4024a may also understand that gNB pulls DCI format 0_0 and DCI format 1_0 transmitted in USS to DCI format 0_0 transmitted in CSS.

4025a, gNB determines whether the size type of DCI is less than or equal to 3 and whether the size type of DCI scrambled by C-RNTI is less than or equal to 2, if not, step 4026a is executed, if yes, the process is ended.

After step 4024a, if the DCI size category required to be detected by UE1 is less than or equal to 3 and the DCI size category required to be detected by UE1 scrambled by C-RNTI is less than or equal to 2, step 402 is deemed to be completed, i.e., the process of step 402 is terminated. If the size category of DCI required to be detected by the UE1 is greater than 3, or the size category of DCI scrambled by the C-RNTI required to be detected by the UE1 is greater than or equal to 2, then step 4026a is performed.

4026a and gNB align the DCI size corresponding to DCI format 0_3 transmitted in the USS with the DCI size corresponding to DCI format 1_ 3;

and aligning the DCI format with the larger load by the DCI format with the smaller load in a mode of supplementing padding bits, or aligning the DCI size corresponding to the DCI format 1_3 to the DCI size corresponding to the DCI format 0_3 no matter how the relation between the DCI size corresponding to the DCI format 0_3 and the DCI size corresponding to the DCI format 1_ 3.

In the embodiment of the present application, it is assumed that the gNB aligns the DCI size corresponding to the DCI format 0_3 transmitted in the USS with the DCI size corresponding to the DCI format 1_ 3.

After steps 4021a to 4026a, the gNB may determine the alignment rule corresponding to each DCI format that the UE1 needs to detect, that is: aligning the DCI size corresponding to the DCI format 0_0 transmitted in the CSS to the DCI size corresponding to the DCI format 1_ 0; the DCI size corresponding to the DCI format 0_0 transmitted in the USS is aligned to the DCI size corresponding to the DCI format 1_ 0; DCI format 0_0 and DCI format 1_0 transmitted in the USS are aligned to DCI format 1_0 transmitted in the CSS; the DCI size corresponding to DCI format 0_3 transmitted in the USS is aligned with the DCI size corresponding to DCI format 1_ 3.

After the gNB determines the alignment rule corresponding to each DCI format that the UE1 needs to detect, the gNB may determine the alignment rule of DCI _ a according to the search space of DCI _ a and its format a, and assuming that the search space is USS and format a is DCI format 0_0, the gNB may align DCI _ a to the DCI size corresponding to DCI format 1_0 sent in the CSS. Assuming that in step 406, the gNB pads p "0" s to the end of the payload of DCI _ a, and DCI _ a that is padded with p "0" s is referred to as DCI _ b, where p is a positive integer.

The implementation manner of step 403 may refer to the embodiment corresponding to fig. 5a, and is not described herein again. Therefore, the UE1 may determine the alignment rule corresponding to each DCI format that the UE1 needs to detect, that is: aligning the DCI size corresponding to the DCI format 0_0 transmitted in the CSS to the DCI size corresponding to the DCI format 1_ 0; the DCI size corresponding to the DCI format 0_0 transmitted in the USS is aligned to the DCI size corresponding to the DCI format 1_ 0; DCI format 0_0 and DCI format 1_0 transmitted in the USS are aligned to DCI format 1_0 transmitted in the CSS; the DCI size corresponding to DCI format 0_3 transmitted in the USS is aligned with the DCI size corresponding to DCI format 1_ 3.

Then, in step 404, the UE1 may determine the size of the aligned DCI format 0_0 and DCI format 1_0 transmitted in the CSS according to the alignment rule, and determine the size of the aligned DCI corresponding to the DCI format 0_0, DCI format 0_3, DCI format 1_0, and DCI format 1_3 transmitted in the USS.

In step 408, the UE1 may restore DCI _ b to DCI _ a according to the alignment rule, for example, truncate the last p-bit zero padding bits of the payload of DCI _ b, to obtain a truncated DCI, i.e., DCI _ a.

Assuming that after a certain time duration, the format and scrambling mode corresponding to the DCI sent by the gNB to the UE1 are as shown in fig. 5b, and the DCI sizes corresponding to the DCI formats in the same dashed-line box are the same. It can be seen that the communication method corresponding to fig. 5a is advantageous to limit the size category of DCI scrambled by the UE's feature RNTI, which is transmitted by the gNB (detected by the UE 1), to no more than 2. The DCI in the non-connected state indicates DCI transmitted by the gNB to the UE when the RRC state of the UE is in the non-connected state. The DCI in the connected state indicates DCI transmitted by the gNB to the UE when the RRC state of the UE is the connected state.

Referring to fig. 6a, step 402 includes the following refinement steps 4021b to 4026 b.

4021b and gNB align the DCI size corresponding to DCI format 0_0 transmitted in CSS with the DCI size corresponding to DCI format 1_ 0.

4022b and gNB align the DCI size corresponding to DCI format 0_0 transmitted in the USS with the DCI size corresponding to DCI format 1_ 0.

4023b, gNB determines whether the size type of DCI is less than or equal to 3, and whether the size type of DCI scrambled by C-RNTI is less than or equal to 2, if not, step 4024b is executed, if yes, the process is ended.

Steps 4021b to 4023b can be understood by referring to the description related to steps 4021a to 4023a in the embodiment corresponding to fig. 5a, and are not described herein again.

4024b and gNB align the DCI size corresponding to DCI format 0_3 transmitted in the USS with the DCI size corresponding to DCI format 1_ 3.

Step 4024b can be understood by referring to the description related to step 4026a, and will not be described herein.

4025b, the gNB determines whether the size type of the DCI is less than or equal to 3, and whether the size type of the DCI scrambled by the C-RNTI is less than or equal to 2, if not, step 4026b is executed, if yes, the process is ended.

After step 4024b, if the DCI size category required to be detected by the UE1 is less than or equal to 3 and the DCI size category required to be detected by the UE1 scrambled by the C-RNTI is less than or equal to 2, the procedure of step 402 is deemed to be complete, i.e., the procedure of step 402 is ended. If the size category of DCI required to be detected by the UE1 is greater than 3, or the size category of DCI scrambled by the C-RNTI required to be detected by the UE1 is greater than or equal to 2, then step 4026b is performed.

4026b, gNB aligns DCI format 0_0 and DCI format 1_0 transmitted in USS with DCI format 1_3 transmitted in USS.

Since the DCI size corresponding to DCI format 0_3 transmitted in USS has been pulled to the DCI size of DCI format 1_3 in step 4024b, step 4026b may also understand that gNB pulls DCI format 0_0 and DCI format 1_0 transmitted in USS to DCI format 0_3 transmitted in CSS.

After steps 4021b to 4026b, the gNB may determine the alignment rule corresponding to each DCI format that the UE1 needs to detect, that is: aligning the DCI size corresponding to the DCI format 0_0 transmitted in the CSS to the DCI size corresponding to the DCI format 1_ 0; aligning the DCI size corresponding to the DCI format 0_3 transmitted in the USS to the DCI size corresponding to the DCI format 1_ 3; DCI format 0_0 and DCI format 1_0 transmitted in the USS are aligned to DCI format 1_3 transmitted in the USS.

It is assumed that, within a certain time duration, the format and scrambling mode corresponding to the DCI sent by the gNB to the UE1 are as shown in fig. 6b, and the DCI formats within the same dashed-line box correspond to the same DCI size. It can be seen that the communication method corresponding to fig. 6a is advantageous to limit the size category of DCI scrambled by the terminal's feature RNTI, which is transmitted by the gNB (detected by the UE 1), to no more than 2.

1.2, each DCI format that the UE1 needs to detect includes DCI format 0_0 and DCI format 1_0 transmitted in the CSS, and DCI format 0_3 and DCI format 1_3 transmitted in the USS.

Referring to fig. 7a, step 402 includes the following refinement steps 4021c to 4025 c.

4021c and gNB align the DCI size corresponding to DCI format 0_0 transmitted in CSS with the DCI size corresponding to DCI format 1_ 0.

4022c and gNB align the DCI size corresponding to DCI format 0_0 transmitted in the USS with the DCI size corresponding to DCI format 1_ 0.

4023C, the gNB determines whether the size type of the DCI required to be detected by the UE1 is less than or equal to 3, and whether the size type of the DCI required to be detected by the UE1 and scrambled by the C-RNTI is less than or equal to 2, if not, step 4024C is executed, and if yes, the process is ended.

Steps 4021c to 4023c can be understood by referring to the description related to steps 4021a to 4023a in the embodiment corresponding to fig. 5a, and are not described herein again.

4024c and gNB align the DCI size corresponding to DCI format 0_3 transmitted in the USS with the DCI size corresponding to DCI format 1_ 3.

Step 4024c can be understood by referring to the description related to step 4026a, and will not be described herein.

Assuming that after a certain time duration, the format and scrambling mode corresponding to the DCI sent by the gNB to the UE1 are as shown in fig. 7b, and the DCI sizes corresponding to the DCI formats in the same dashed-line box are the same. It can be seen that the communication method corresponding to fig. 7a is advantageous to limit the size category of DCI scrambled by the terminal's feature RNTI, which is transmitted by the gNB (detected by the UE 1), to no more than 2.

2. The value combination of M and N is as follows: m is 2 and N is 1.

Under the value combination, the size category of DCI required to be detected by the UE1 can be reduced to 2, and/or the size category of DCI scrambled by the specific RNTI of the UE1 required to be detected by the UE can be reduced to 1.

2.1, each DCI format that the UE1 needs to detect includes DCI format 0_0 and DCI format 1_0 transmitted in the CSS, and DCI format 0_0, DCI format 0_3, DCI format 1_0 and DCI format 1_3 transmitted in the USS.

Referring to fig. 8a, step 402 includes the following refinement steps 4021d to 4028 d.

4021d and gNB align the DCI size corresponding to DCI format 0_0 transmitted in CSS with the DCI size corresponding to DCI format 1_ 0.

4022d and gNB align the DCI size corresponding to DCI format 0_0 transmitted in the USS with the DCI size corresponding to DCI format 1_ 0.

4023d, gNB determines whether the size type of DCI is less than or equal to 2, and whether the size type of DCI scrambled by C-RNTI is less than or equal to 1, if not, step 4024b is executed, if yes, the process is ended.

4024d, gNB aligns DCI format 0_0 and DCI format 1_0 transmitted in USS with DCI format 1_0 transmitted in CSS.

4025d, gNB determines whether the size type of DCI is less than or equal to 2, and whether the size type of DCI scrambled by C-RNTI is less than or equal to 1, if not, step 4026d is executed, if yes, the process is ended.

Steps 4021d to 4025d can be understood by referring to the description related to steps 4021a to 4025a in the embodiment corresponding to fig. 5a, and are not described herein again.

4026d and gNB align the DCI size corresponding to DCI format 0_3 transmitted in the USS with the DCI size corresponding to DCI format 1_ 3.

4027d, gNB determines whether the size type of DCI is less than or equal to 2, and whether the size type of DCI scrambled by C-RNTI is less than or equal to 1, if not, step 4028d is executed, if yes, the process is ended.

After step 4026d, step 4027d is performed.

4028d and gNB align DCI sizes corresponding to DCI format 0_3 and DCI format 1_3 transmitted in USS with DCI format 0_0 transmitted in USS.

Since the DCI size corresponding to DCI format 0_0 transmitted in CSS has already been aligned to the DCI size of DCI format 1_0 in step 4021d, and DCI format 0_0 and DCI format 1_0 transmitted in USS have already been aligned to DCI format 1_0 transmitted in CSS in step 4024d, step 4028d may also be understood as the gNB aligning the DCI sizes corresponding to DCI format 0_3 and DCI format 1_3 transmitted in USS to DCI format 1_0 transmitted in USS, or aligning to DCI format 0_0 transmitted in CSS, or aligning to DCI format 1_0 transmitted in CSS.

Assuming that after a certain time duration, the format and scrambling mode corresponding to the DCI sent by the gNB to the UE1 are as shown in fig. 8b, and the DCI sizes corresponding to the DCI formats in the same dashed-line box are the same. It can be seen that the communication method corresponding to fig. 8a is advantageous to limit the size category of DCI scrambled by the UE's feature RNTI, which is transmitted by the gNB (detected by the UE 1), to not more than 1.

2.2, each DCI format that the UE1 needs to detect includes DCI format 0_0 and DCI format 1_0 transmitted in the CSS, and DCI format 0_3 and DCI format 1_3 transmitted in the USS.

Referring to fig. 9a, step 402 includes the following refinement steps 4021e to 4026 e.

4021e and gNB align the DCI size corresponding to DCI format 0_0 transmitted in CSS with the DCI size corresponding to DCI format 1_ 0.

4022e and gNB align the DCI size corresponding to DCI format 0_0 transmitted in the USS with the DCI size corresponding to DCI format 1_ 0.

4023e, gNB determines whether the size type of DCI is less than or equal to 2, and whether the size type of DCI scrambled by C-RNTI is less than or equal to 1, if not, step 4024b is executed, if yes, the process is ended.

Steps 4021e to 4023e can be understood by referring to the description related to steps 4021a to 4023a in the embodiment corresponding to fig. 5a, and are not described herein again.

4024e and gNB align the DCI size corresponding to DCI format 0_3 transmitted in the USS with the DCI size corresponding to DCI format 1_ 3.

Step 4024e can be understood by referring to the description related to step 4026a, and will not be described herein.

4025e, gNB determines whether the size type of DCI is less than or equal to 2, and whether the size type of DCI scrambled by C-RNTI is less than or equal to 1, if not, step 4026d is executed, if yes, the process is ended.

Step 4025e is performed after step 4024 e.

4026e and gNB align DCI sizes corresponding to DCI format 0_3 and DCI format 1_3 transmitted in USS with DCI format 0_0 transmitted in CSS.

Since the DCI size corresponding to DCI format 0_0 transmitted in CSS has already been aligned to the DCI size of DCI format 1_0 in step 4021e, step 4026e may also understand that gNB aligns the DCI sizes corresponding to DCI format 0_3 and DCI format 1_3 transmitted in USS to DCI format 1_0 transmitted in CSS.

Assuming that after a certain time duration, the format and scrambling mode corresponding to the DCI sent by the gNB to the UE1 are as shown in fig. 9b, and the DCI sizes corresponding to the DCI formats in the same dashed-line box are the same. It can be seen that the communication method corresponding to fig. 9a is advantageous to limit the size category of DCI scrambled by the UE's feature RNTI, which is transmitted by the gNB (detected by the UE 1), to not more than 1.

It should be understood that the specific examples in the embodiments of the present application are for the purpose of promoting a better understanding of the embodiments of the present application and are not intended to limit the scope of the embodiments of the present application.

It should be understood that, in the various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

In the embodiments provided in the present application, the method provided in the embodiments of the present application is introduced from the perspective of a network device, a terminal, and interaction between the network device and the terminal. In order to implement the functions in the method provided by the embodiments of the present application, the network device and the terminal may include a hardware structure and/or a software module, and the functions are implemented in the form of a hardware structure, a software module, or a hardware structure and a software module. Whether any of the above-described functions is implemented as a hardware structure, a software module, or a hardware structure plus a software module depends upon the particular application and design constraints imposed on the technical solution.

Fig. 10 shows a schematic configuration of a communication apparatus. The communication apparatus is configured to implement the functions of the UE described in the embodiments of the present application. As shown in fig. 10, the communication device 10 may include: a detection module 1001. The detecting module 1001 is configured to perform step 302 in fig. 3, step 405 in fig. 4, step 1 in step 407, and the like. The detection module may also be referred to as a receiving module.

In one possible implementation, referring to the modules represented by the dashed boxes in fig. 10, the communication device 10 may further include a processing module 1002, and the processing module 1002 is coupled with the detecting module 1001 for executing the steps 403, 404 and 408 in fig. 4. For the specific implementation process, reference is made to the detailed description of the corresponding steps in the above method embodiments, which is not repeated herein.

The coupling in the embodiments of the present application is an indirect coupling or a communication connection between devices, units or modules, and may be an electrical, mechanical or other form for information interaction between the devices, units or modules.

In one possible implementation, the communication apparatus 10 may further include a transmitting module (not shown in fig. 10), for example, configured to transmit the PUSCH to the network device. The detection module and the transmission module of the communication device 10 may be integrated as a transceiving module or a communication module.

Fig. 11 is a schematic structural diagram of a communication device according to an embodiment of the present application. The communication device is used for realizing the functions of the network equipment described in the embodiments of the present application. Referring to fig. 11, the communication device 11 includes a sending module 1101. The sending module 1101 is configured to execute step 301 in fig. 3, step 401 in fig. 4, and step 407. Optionally, referring to the modules corresponding to the dashed line boxes in fig. 11, the communication device 11 further includes a processing module 1102. The processing module 1102 is used for executing the steps 402 and 406 and the like in fig. 4. For the specific implementation process, reference is made to the detailed description of the corresponding steps in the above method embodiments, which is not repeated herein.

In a possible implementation, the communication apparatus 11 may further include a receiving module (not shown in fig. 11), for example, configured to receive a PUSCH transmitted by the terminal. The receiving module and the transmitting module of the communication device 11 may be integrated as a transceiving module or a communication module.

The division of the modules in the embodiments of the present application is schematic, and only one logical function division is provided, and in actual implementation, there may be another division manner, and in addition, each functional module in each embodiment of the present application may be integrated in one processor, may also exist alone physically, or may also be integrated in one module by two or more modules. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode.

Fig. 12 shows an apparatus 1200 provided in this embodiment of the present application, for implementing the functions of the terminal in the foregoing method. The device may be a terminal or a device that can be used in cooperation with a terminal. The apparatus may be installed in a terminal. Illustratively, the apparatus may be a system-on-a-chip. 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. The apparatus 1200 includes at least one processor 1220 for implementing the functions of the terminal in the methods provided by the embodiments of the present application.

The apparatus 1200 may also include at least one memory 1230 for storing program instructions and/or data. Memory 1230 is coupled to processor 1220. The processor 1220 may cooperate with the memory 1230. Processor 1220 may execute program instructions stored in memory 1230. One or more of the at least one memory may be included in the processor.

The apparatus 1200 may also include a communication interface 1210 for communicating with other devices over a transmission medium such that the apparatus used in the apparatus 1200 may communicate with other devices. Illustratively, the communication interface 1210 may be a transceiver, circuit, bus, module, pin, or other type of communication interface, which may be a network device. The processor 1220 is configured to receive and transmit data through the communication interface, for example, detect DCI from a network device through the communication interface, to implement the function of the terminal in the method provided in the embodiment of the present application, which is specifically referred to the detailed description in the method example, and is not described herein again.

The specific connection medium among the transceiver 1210, the processor 1220 and the memory 1230 is not limited in the embodiments of the present application. In fig. 12, the memory 1230, the processor 1220 and the transceiver 1210 are connected by a bus 1240, the bus is represented by a thick line in fig. 12, and the connection manner among other components is only schematically illustrated and not limited. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 12, but this is not intended to represent only one bus or type of bus.

Fig. 13 shows an apparatus 1300 provided in this embodiment of the present application, configured to implement the functions of the network device in the foregoing method. The device may be a network device, or may be a device that can be used in cooperation with a network device. The apparatus may be installed in a network device. Illustratively, the apparatus may be a system-on-a-chip. The apparatus 1300 includes at least one processor 1320 configured to implement the functions of the network device in the methods provided in the embodiments of the present application.

The apparatus 1300 may also include at least one memory 1330 for storing program instructions and/or data. A memory 1330 is coupled to the processor 1320. The processor 1320 may operate in conjunction with the memory 1330. Processor 1320 may execute program instructions stored in memory 1330. One or more of the at least one memory may be included in the processor.

Apparatus 1300 may also include a communication interface 1310 for communicating with other devices over a transmission medium, such that the apparatus used in apparatus 1300 may communicate with other devices. Illustratively, the communication interface 1310 may be a transceiver, circuit, bus, module, pin, or other type of communication interface, and the other device may be a terminal. The processor 1320 may receive and transmit data through the communication interface, for example, send DCI to the terminal through the communication interface, to implement the function of the network device in the method provided in the embodiment of the present application, which is specifically described in detail in the method example, and is not described herein again.

The embodiment of the present application does not limit the specific connection medium among the transceiver 1310, the processor 1320, and the memory 1330. In fig. 13, the memory 1330, the processor 1320, and the transceiver 1310 are connected by a bus 1340, which is indicated by a thick line in fig. 13, and the connection manner among other components is only for illustrative purposes and is not limited thereto. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 13, but this is not intended to represent only one bus or type of bus.

In the embodiments of the present application, the processor may be a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the methods, steps, and logic blocks disclosed in the embodiments of the present application. A general purpose processor may be a microprocessor or any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in a processor.

In the embodiment of the present application, the memory may be a nonvolatile memory, such as a Hard Disk Drive (HDD) or a solid-state drive (SSD), and may also be a volatile memory, for example, a random-access memory (RAM). The memory is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to such. The memory in the embodiments of the present application may also be circuitry or any other device capable of performing a storage function for storing program instructions and/or data.

The technical solutions provided in the embodiments of the present application may be wholly or partially implemented 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 instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the invention to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, a network appliance, a terminal device or other programmable apparatus. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). 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, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., Digital Video Disk (DVD)), or a semiconductor medium, among others.

In the embodiments of the present application, the embodiments may refer to each other, for example, methods and/or terms between the embodiments of the method may refer to each other, for example, functions and/or terms between the embodiments of the apparatus and the embodiments of the method may refer to each other, without logical contradiction.

In the embodiments of the present application, at least one may also be described as one or more, and a plurality may be two, three, four or more, which is not limited in the present application.

In the embodiments of the present application, "/" may indicate a relationship in which the objects associated before and after are "or", for example, a/B may indicate a or B; "and/or" may be used to describe that there are three relationships for the associated object, 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. For convenience in describing the technical solutions of the embodiments of the present application, in the embodiments of the present application, terms such as "first" and "second" may be used to distinguish technical features having the same or similar functions. The terms "first", "second", and the like do not necessarily limit the number and execution order, and the terms "first", "second", and the like do not necessarily differ. In the embodiments of the present application, the words "exemplary" or "such as" are used to indicate examples, illustrations or illustrations, and any embodiment or design described as "exemplary" or "e.g.," should not be construed as preferred or advantageous over other embodiments or designs. The use of the terms "exemplary" or "such as" are intended to present relevant concepts in a concrete fashion for ease of understanding.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1. a communication method, is characterized in that, comprises:

Detect downlink control information DCI from the network device, where the DCI is used for scheduling physical data channels, and the format of the DCI used for scheduling physical data channels includes multiple DCI formats; wherein,

The types of DCI sizes corresponding to the multiple DCI formats are less than or equal to N, where N is a positive integer less than or equal to 3; and/or,

When the DCI corresponding to the multiple DCI formats is scrambled by using the terminal-specific wireless network temporary identifier RNTI, the types of DCI sizes corresponding to the multiple DCI formats are less than or equal to M, where M is a positive integer less than or equal to 2.

2. The method according to claim 1, wherein the types of DCI sizes corresponding to the multiple DCI formats are less than or equal to N, comprising:

When the DCI corresponding to the multiple DCI formats is scrambled by using a common RNTI or a terminal-specific RNTI, the types of DCI sizes corresponding to the multiple DCI formats are less than or equal to N.

3. The method according to claim 1 or 2, wherein the multiple DCI formats include a first format and a second format detected in a terminal-specific search space USS, and the DCI corresponding to the first format It is used for scheduling uplink transmission, and the DCI corresponding to the second format is used for scheduling downlink transmission, wherein the DCI transmitted in the USS is scrambled by using the terminal-specific RNTI.

4. The method according to claim 3, wherein the DCI size corresponding to the first format is aligned to the DCI size corresponding to the second format, or the DCI size corresponding to the second format is aligned to the DCI size corresponding to the first format.

5. The method according to claim 4, wherein the DCI size corresponding to the second format is aligned to the DCI size corresponding to the first format, comprising:

If the size of the DCI corresponding to the first format is smaller than the size of the DCI corresponding to the second format, the K fields of the DCI corresponding to the second format are truncated, and the truncated DCI corresponding to the second format The DCI size is the same as the DCI size corresponding to the first format, where K is a positive integer;

Or, if the DCI size corresponding to the first format is larger than the DCI size corresponding to the second format, the DCI corresponding to the second format is filled with at least one padding bit, and the filled second format corresponds to The size of the DCI is the same as the size of the DCI corresponding to the first format.

6. The method according to claim 5, wherein the K domains comprise at least one of the following domains:

frequency domain resource allocation domain;

Time domain resource allocation domain;

Physical uplink control channel resource indication field;

Physical Downlink Shared Channel to Hybrid Automatic Repeat Request Feedback Time Indication Field; and

The demodulation reference signal sequence initialization field.

7. The method according to any one of claims 3 to 6, wherein the multiple DCI formats further include a third format and a fourth format detected in the USS, and the DCI corresponding to the third format is used for scheduling uplink transmission, the DCI corresponding to the fourth format is used for scheduling downlink transmission, the first format is different from the third format, and the second format is different from the fourth format; wherein,

The DCI size corresponding to the third format is aligned to the DCI size corresponding to the first format or to the DCI size corresponding to the second format, and the DCI size corresponding to the fourth format is aligned to the DCI size corresponding to the fourth format. The DCI size corresponding to the first format or is aligned to the DCI size corresponding to the second format, wherein the DCI size corresponding to the first format is equal to the DCI size corresponding to the second format.

8. The method according to any one of claims 1 to 6, wherein the multiple DCI formats include a third format and a fourth format detected in a terminal-specific search space USS, and a common search The third format and the fourth format detected in the spatial CSS, the DCI corresponding to the third format is used for scheduling uplink transmission, and the DCI corresponding to the fourth format is used for scheduling downlink transmission, wherein the transmission in USS The DCI of the terminal is scrambled using the terminal-specific RNTI, and the DCI transmitted in the CSS is scrambled using the terminal-specific RNTI or scrambled using the common RNTI; wherein,

The DCI size corresponding to the third format detected in the USS is aligned to the DCI size corresponding to the third format detected in the CSS or to the DCI size corresponding to the fourth format detected in the CSS, And, the DCI size corresponding to the fourth format detected in the USS is aligned to the DCI size corresponding to the third format detected in the CSS or to the DCI corresponding to the fourth format detected in the CSS size.

9. The method according to claim 7 or 8, wherein the third format is 0_0, and the fourth format is 1_0.

10. A communication method, comprising:

The DCI size corresponding to the sixth format among the multiple DCI formats is aligned to the DCI size corresponding to the fifth format among the multiple DCI formats, and the DCI corresponding to the fifth format is used for scheduling uplink transmission, and the sixth format is used for scheduling uplink transmission. The DCI corresponding to the format is used for scheduling downlink transmission.

11. A communication method, comprising:

Send downlink control information DCI to the terminal, where the DCI is used for scheduling physical data channels, and the format of the DCI used for scheduling physical data channels includes multiple DCI formats; wherein,

12. The method according to claim 11, wherein the types of DCI sizes corresponding to the multiple DCI formats are less than or equal to N, comprising:

13. The method according to claim 11 or 12, wherein the multiple DCI formats include a first format and a second format sent in a terminal-specific search space USS, and the DCI corresponding to the first format For scheduling uplink transmission, the DCI corresponding to the second format is used for scheduling downlink transmission, wherein the DCI transmitted in the USS is scrambled by using the terminal-specific RNTI.

The method according to claim 13, wherein the DCI size corresponding to the first format is aligned to the DCI size corresponding to the second format, or the DCI size corresponding to the second format is aligned to the DCI size corresponding to the first format.

15. The method according to claim 14, wherein the DCI size corresponding to the second format is aligned to the DCI size corresponding to the first format, comprising:

16. The method of claim 15, wherein the K domains comprise at least one of the following domains:

frequency domain resource allocation domain;

Time domain resource allocation domain;

Physical uplink control channel resource indication field;

The demodulation reference signal sequence initialization field.

17. The method according to any one of claims 13 to 16, wherein the multiple DCI formats further include a third format and a fourth format sent in the USS, and the DCI corresponding to the third format used for scheduling uplink transmission, the DCI corresponding to the fourth format is used for scheduling downlink transmission, the first format is different from the third format, and the second format is different from the fourth format; wherein,

18. The method according to any one of claims 11 to 16, wherein the multiple DCI formats include a third format and a fourth format sent in a terminal-specific search space USS, and a The third format and the fourth format sent in the spatial CSS, the DCI corresponding to the third format is used for scheduling uplink transmission, and the DCI corresponding to the fourth format is used for scheduling downlink transmission, wherein the transmission in the USS The DCI of the terminal is scrambled using the terminal-specific RNTI, and the DCI transmitted in the CSS is scrambled using the terminal-specific RNTI or scrambled using the common RNTI; wherein,

The DCI size corresponding to the third format sent in the USS is aligned to the DCI size corresponding to the third format sent in the CSS or to the DCI size corresponding to the fourth format sent in the CSS, In addition, the size of the DCI corresponding to the fourth format sent in the USS is aligned to the size of the DCI corresponding to the third format sent in the CSS or to the DCI corresponding to the fourth format sent in the CSS size.

19. The method according to claim 17 or 18, wherein the third format is 0_0, and the fourth format is 1_0.

20. A communication method, comprising:

The DCI size corresponding to the sixth format among the multiple DCI formats is aligned to the DCI size corresponding to the fifth format among the multiple DCI formats, and the DCI corresponding to the fifth format is used for scheduling uplink transmission, and the sixth format is used for scheduling uplink transmission. The DCI corresponding to the format is used to schedule downlink transmission.

21. A communication device, characterized by being used for implementing the method according to any one of claims 1 to 10.

22. A communications apparatus comprising a processor and a memory coupled to the processor, the processor for performing the method of any one of claims 1 to 10.

23. A communication device comprising a processor and a communication interface,

The processor uses the communication interface to detect downlink control information DCI from a network device, wherein the DCI is used for scheduling physical data channels, and the format of the DCI used for scheduling physical data channels includes multiple DCIs format; where,

When the DCI corresponding to the multiple DCI formats is scrambled using the terminal-specific wireless network temporary identifier RNTI, the types of DCI sizes corresponding to the multiple DCI formats are less than or equal to M, where M is a positive integer less than or equal to 2.

24. A communication device, comprising a detection module;

The detection module is configured to detect downlink control information DCI from a network device, wherein the DCI is used to schedule a physical data channel, and the format of the DCI used to schedule the physical data channel includes multiple DCI formats; wherein,

25. A communication device, characterized by being used for implementing the method according to any one of claims 11 to 20.

26. A communications apparatus comprising a processor and a memory coupled to the processor, the processor for performing the method of any of claims 11 to 20.

27. A communication device comprising a processor and a communication interface,

The processor uses the communication interface to send downlink control information DCI to the terminal, wherein the DCI is used for scheduling a physical data channel, and the format of the DCI used for scheduling the physical data channel includes multiple DCI formats; in,

28. A communication device, comprising a sending module;

The sending module is configured to send downlink control information DCI to the terminal, wherein the DCI is used to schedule a physical data channel, and the format of the DCI used to schedule the physical data channel includes multiple DCI formats; wherein,

29. A communication system comprising the communication device of any one of claims 21 to 24, and the communication device of any one of claims 25 to 28.

30. A computer readable storage medium comprising instructions which, when executed on a computer, cause the computer to perform the method of any one of claims 1 to 20.

31. A computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of any one of claims 1 to 20.