WO2021204107A1 - Procédé et appareil de communication - Google Patents

Procédé et appareil de communication Download PDF

Info

Publication number
WO2021204107A1
WO2021204107A1 PCT/CN2021/085608 CN2021085608W WO2021204107A1 WO 2021204107 A1 WO2021204107 A1 WO 2021204107A1 CN 2021085608 W CN2021085608 W CN 2021085608W WO 2021204107 A1 WO2021204107 A1 WO 2021204107A1
Authority
WO
WIPO (PCT)
Prior art keywords
dci
format
size corresponding
formats
equal
Prior art date
Application number
PCT/CN2021/085608
Other languages
English (en)
Chinese (zh)
Inventor
费永强
郑娟
侯海龙
李超君
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2021204107A1 publication Critical patent/WO2021204107A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0023—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the signalling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0036—Systems modifying transmission characteristics according to link quality, e.g. power backoff arrangements specific to the receiver
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0036—Systems modifying transmission characteristics according to link quality, e.g. power backoff arrangements specific to the receiver
    • H04L1/0038—Blind format detection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • This application relates to the field of communication technology, and in particular to a communication method and device.
  • network equipment can Terminal equipment, such as user equipment (UE), sends downlink control information (DCI) for scheduling data transmission between the network equipment and the terminal equipment.
  • DCI downlink control information
  • the embodiments of the present application provide a communication method and device, which are used to reduce the size and type of DCI used for scheduling physical data channels, so as to reduce the number and complexity of blind detection of the terminal.
  • an embodiment of the present application provides a communication method, including: detecting downlink control information DCI from a network device, where the DCI is used to schedule a physical data channel, and the DCI is used to schedule a physical data channel
  • the format includes multiple DCI formats; wherein the types of DCI sizes corresponding to the multiple DCI formats are less than or equal to N, and N is a positive integer less than or equal to 3; and/or, the DCI corresponding to the multiple DCI formats is When the terminal-specific wireless network temporary identification RNTI is used for scrambling, the types of DCI sizes corresponding to the multiple DCI formats are less than or equal to M, and M is a positive integer less than or equal to 2.
  • RNTI is the identification of the terminal.
  • the terminal-specific RNTI can be the terminal's cell RNTI (cell RNTI, C-RNTI), configured scheduling RNTI (configured scheduling RNTI, CS-RNTI), or modulation and coding strategy cell RNTI (modulation and coding scheme C-RNTI, MCS-C) -RNTI) and so on.
  • the physical data channel is used to transmit uplink data.
  • the physical data channel is a physical uplink shared channel (PUSCH), or it is used to transmit downlink data.
  • the physical data channel is a physical downlink shared channel (PDSCH). ), or, includes a physical channel (such as PUSCH) used to transmit uplink data and a physical channel (such as PDSCH) used to transmit downlink data.
  • PUSCH physical uplink shared channel
  • PDSCH physical downlink shared channel
  • M is a positive integer less than or equal to 3
  • N are positive integers less than or equal to 2.
  • the types of DCI sizes corresponding to the multiple DCI formats are less than or equal to N, including: when the DCI corresponding to the multiple DCI formats is scrambled 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.
  • the public RNTI may be system information RNTI (system information RNTI, SI-RNTI), paging RNTI (paging RNTI, P-RNTI), or random access RNTI (random access RNTI, RA-RNTI), etc.
  • system information RNTI system information RNTI
  • SI-RNTI system information RNTI
  • paging RNTI paging RNTI
  • P-RNTI paging RNTI
  • random access RNTI random access RNTI
  • RA-RNTI random access RNTI
  • the size and type of this type of DCI can be limited, and the number of DCI detections of the terminal can be reduced, thereby reducing the complexity of the terminal and reducing the power consumption of the terminal.
  • 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 is used for scheduling uplink transmission, and The DCI corresponding to the second format is used for scheduling downlink transmission, where the DCI transmitted in the USS is scrambled using the terminal-specific RNTI.
  • limiting the types of DCI sizes in the first format and the second format can reduce the number of times the terminal detects the DCI in the first format and the second format, thereby reducing the complexity of the terminal and reducing the power consumption of the terminal. .
  • the DCI size corresponding to the first format and the DCI size corresponding to the second format are aligned.
  • the DCI size corresponding to the first format is aligned to the DCI size corresponding to the second format. This method can avoid the information loss of the DCI in the second format.
  • the DCI size corresponding to the second format is aligned to the DCI size corresponding to the first format. This method can avoid the information loss of the DCI in the first format.
  • 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
  • the DCI size corresponding to the second format is smaller than the first format
  • the DCI size corresponding to the second format is aligned to the DCI size corresponding to the first format.
  • 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 that corresponding to the second format The DCI size of the DCI corresponding to the second format is truncated, and the DCI size corresponding to the second format after the truncation 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 greater 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 first filled bit The DCI size corresponding to the second format is the same as the DCI size corresponding to the first format.
  • the transmission performance and scheduling performance of the DCI corresponding to the first format can be guaranteed, and thus the uplink transmission performance of the terminal can be guaranteed.
  • 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 that corresponding to the first format The DCI size of the DCI corresponding to the first format is truncated, and the DCI size corresponding to the first format after the truncation is the same as the DCI size corresponding to the second format, where K is A positive integer; or, if the DCI size corresponding to the second format is greater than the DCI size corresponding to the first format, then the DCI corresponding to the first format is filled with at least one padding bit, and the first filled bit The DCI size corresponding to one format is the same as the DCI size corresponding to the second format.
  • the transmission performance and scheduling performance of the DCI in the second format can be guaranteed, and thus the downlink transmission performance of the terminal device can be guaranteed.
  • the K domains include at least one of the following domains: frequency domain resource allocation domain; time domain resource allocation domain; physical uplink control channel resource indication domain; physical downlink shared channel to hybrid automatic reset Transmission request feedback time indication field; and demodulation reference signal sequence initialization field.
  • the multiple DCI formats further include a third format and a fourth format detected in the USS, the DCI corresponding to the third format is used for scheduling uplink transmission, and the fourth format corresponds to DCI is used to schedule 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 The DCI size corresponding to the first format is 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 first format.
  • 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.
  • the number of DCI sizes that the terminal needs to detect can be reduced, and the terminal's blindness to DCI can be reduced.
  • the number of detections can reduce the complexity, power consumption and cost of the terminal.
  • the multiple DCI formats include the third format and the fourth format detected in the terminal-specific search space USS, and the third format and the fourth format detected in the common search space CSS.
  • 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 DCI transmitted in the USS is scrambled using the terminal-specific RNTI
  • the DCI transmitted in the CSS is scrambled using the terminal-specific RNTI or is scrambled using a common RNTI; wherein the DCI size corresponding to the third format detected in the USS is aligned to the size of the DCI detected in the CSS
  • the DCI size corresponding to the third format is aligned to the DCI size corresponding to the fourth format detected in the CSS
  • the DCI size corresponding to the fourth format detected in the USS is aligned to the DCI size detected in the CSS
  • the DCI size corresponding to the third format may be aligned to the DCI
  • the number of blind DCI detections of the terminal when the time-frequency resources of the USS and CSS overlap can reduce the terminal's Implementation complexity, power consumption and cost.
  • the third format is 0_0
  • the fourth format is 1_0.
  • the types of DCI sizes corresponding to multiple DCI formats are less than or equal to 2, which is beneficial to reduce the types of DCI sizes that the terminal needs to detect to two; or, the multiple DCI formats correspond to
  • the types of DCI sizes corresponding to the multiple DCI formats are less than or equal to 1, which is conducive to reducing the size and type of the DCI scrambled by the terminal’s specific RNTI that the terminal needs to detect to 1; or, when the type of DCI size corresponding to multiple DCI formats is less than or equal to 2, and the DCI corresponding to the multiple DCI formats is scrambled using a terminal-specific RNTI, the DCI size corresponding to the multiple DCI formats
  • the type of is less than or equal to 1, which is beneficial to reduce the type of DCI that the terminal needs to detect to two, and reduce the type of DCI scrambled by the terminal-specific RNTI to one.
  • the multiple DCI formats include the first format, the second format, the third format, and the fourth format detected in the USS, and the third format and the fourth format detected in the common search space CSS.
  • the fourth format, 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 the same as
  • the third format is different
  • the second format is different from the fourth format;
  • the DCI size corresponding to the first format detected in USS is aligned to the corresponding third format detected in CSS Or is aligned to the DCI size corresponding to the fourth format detected in the CSS
  • the DCI size corresponding to the second format detected in the USS is aligned to the third format detected in the CSS
  • the DCI size corresponding to the format is aligned 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 third format detected
  • the DCI size corresponding to the format is aligned to the DCI size corresponding to the fourth format detected in the CSS
  • the DCI size corresponding to the fourth format detected in the USS is aligned to the DCI size detected in the CSS
  • the DCI size corresponding to the third format may be aligned to the DCI size corresponding to the fourth format detected in the CSS.
  • 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 to schedule a physical data channel, and the DCI is used to schedule a physical data channel
  • the format includes multiple DCI formats; wherein the DCI size corresponding to the sixth format in the multiple DCI formats is aligned to the DCI size corresponding to the fifth format in the multiple DCI formats, and the DCI corresponding to the fifth format Used for scheduling uplink transmission, and the DCI corresponding to the sixth format is used for scheduling downlink transmission.
  • the DCI size corresponding to the DCI format used for scheduling downlink transmission is aligned with the DCI size corresponding to the DCI format used for scheduling uplink transmission, which can avoid the information loss of the DCI format of the fifth format and ensure the uplink of the terminal. Transmission performance.
  • the DCI size corresponding to the sixth format in the multiple DCI formats is aligned to the DCI size corresponding to the fifth format in the multiple DCI formats, including: if the fifth format corresponds to The DCI size corresponding to the sixth format is smaller than the DCI size corresponding to the sixth format, the K fields of the DCI corresponding to the sixth format are truncated, and the truncated DCI size corresponding to the sixth format is the same as the fifth
  • the DCI sizes corresponding to the formats are the same, where K is a positive integer; or, if the DCI size corresponding to the fifth format is greater than the DCI size corresponding to the sixth format, at least one of the DCI sizes corresponding to the sixth format is filled Filling bits, the size of the DCI corresponding to the sixth format after being filled is the same as the size of the DCI corresponding to the fifth format.
  • the transmission performance and scheduling performance of the DCI corresponding to the fifth format can be guaranteed, and thus the uplink transmission performance of the terminal can be guaranteed.
  • the K domains include at least one of the following domains: frequency domain resource allocation domain; time domain resource allocation domain; physical uplink control channel resource indication domain; physical downlink shared channel to hybrid automatic reset Transmission request feedback time indication field; and demodulation reference signal sequence initialization field.
  • the DCI of the fifth format may be the DCI of the first format detected in the terminal-specific search space USS
  • the DCI of the sixth format may be the DCI of the second format detected in the USS.
  • DCI; or, the DCI of the fifth format may be the DCI of the third format detected in the USS, and the DCI of the sixth format may be the DCI of the fourth format detected in the USS; or, the DCI of the fifth format
  • the DCI may be the DCI of the third format detected in the CSS, and the DCI of the sixth format may be the DCI of the fourth format detected in the CSS.
  • an embodiment of the present application provides a communication device.
  • the communication device may be a terminal device, a device in a terminal, or a device that can be matched and used with the terminal.
  • the device may include modules that perform one-to-one correspondence of the methods/operations/steps/actions described in the first aspect or the second aspect.
  • the modules may be hardware circuits, software, or hardware. Circuit combined with software implementation.
  • the communication device may include a detection module configured to detect downlink control information DCI from a network device, where the DCI is used to schedule a physical data channel, and the DCI is used to schedule a physical data channel.
  • the DCI format for scheduling the physical data channel includes multiple types of DCI formats; wherein the types of DCI sizes corresponding to the multiple types of DCI formats are less than or equal to N, and N is a positive integer less than or equal to 3; and/or, the multiple types
  • the DCI corresponding to the DCI format is scrambled using the terminal-specific wireless network temporary identification RNTI
  • the type of the DCI size corresponding to the multiple DCI formats is less than or equal to M, and M is a positive integer less than or equal to 2.
  • the specific formats included in the multiple DCI formats and the alignment manner of the multiple DCI formats can be referred to the specific description of the DCI format in the first aspect, which will not be repeated here.
  • the communication device may include a detection module configured to detect downlink control information DCI from a network device, where the DCI is used to schedule a physical data channel, and the DCI is used to schedule a physical data channel.
  • the DCI format for scheduling the physical data channel includes multiple DCI formats; wherein the DCI size corresponding to the sixth format in the multiple DCI formats is aligned to the DCI size corresponding to the fifth format in the multiple DCI formats, and The DCI corresponding to the fifth format is used for scheduling uplink transmission, and the DCI corresponding to the sixth format is used for scheduling downlink transmission.
  • the DCI of the fifth format may be the DCI of the first format detected in the terminal-specific search space USS
  • the DCI of the sixth format may be the DCI of the second format detected in the USS.
  • DCI; or, the DCI of the fifth format may be the DCI of the third format detected in the USS, and the DCI of the sixth format may be the DCI of the fourth format detected in the USS; or, the DCI of the fifth format
  • the DCI may be the DCI of the third format detected in the CSS, and the DCI of the sixth format may be the DCI of the fourth format detected in the CSS.
  • the fourth aspect of the present application provides a communication device.
  • the communication device may be a terminal device, a device in a terminal, or a device that can be matched and used with the terminal.
  • the device includes a processor, configured to implement the method described in the first aspect or the second aspect.
  • the device may also include a memory for storing instructions and data.
  • the memory is coupled with the processor, and when the processor executes the instructions stored in the memory, the method described in the first aspect or the second aspect can be implemented.
  • the device may also include a communication interface, which is used for the device to communicate with other devices.
  • the communication interface may be a transceiver, circuit, bus, module, pin, or other type of communication interface.
  • the device can be a network device.
  • the device includes: a memory for storing program instructions; a processor for detecting downlink control information DCI from a network device using a communication interface, where the DCI is used for scheduling physical data Channel, the format of the DCI used to schedule the physical data channel includes multiple DCI formats; wherein the types of DCI sizes corresponding to the multiple DCI formats are 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 using a terminal-specific wireless network temporary identification RNTI, the type of the DCI size corresponding to the multiple DCI formats is less than or equal to M, and M is a positive integer less than or equal to 2 .
  • the specific formats included in the multiple DCI formats and the alignment manner of the multiple DCI formats can be referred to the specific description of the DCI format in the first aspect, which will not be repeated here.
  • the device includes: a memory for storing program instructions; a processor for detecting downlink control information DCI from a network device using a communication interface, where the DCI is used for scheduling physical data Channel, the format of the DCI used to schedule the physical data channel includes multiple DCI formats; wherein the DCI size corresponding to the sixth format among the multiple DCI formats is aligned to the fifth format corresponding to the multiple DCI formats The DCI size corresponding to the fifth format is used for scheduling uplink transmission, and the DCI corresponding to the sixth format is used for scheduling downlink transmission.
  • the communication device can be implemented in the form of a chip.
  • a fifth aspect of the present application provides a chip system.
  • the chip system includes a processor and may also include a memory for implementing the method described in the first aspect or the second aspect.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • a sixth aspect of the present application provides a computer-readable storage medium.
  • the computer-readable storage medium includes instructions. When the instructions run on a computer, the computer executes any one of the first aspect or the first aspect of the embodiments of the present application.
  • the method in two possible implementation manners or the second aspect or the method in any one of the possible implementation manners of the second aspect.
  • the seventh aspect of the present application provides a computer program product.
  • the computer program product includes instructions. When the instructions run on a computer, the computer executes the first aspect or any possible implementation manner of the first aspect of the embodiments of the present application. Or the second aspect or any one of the possible implementations of the second aspect.
  • an embodiment of the present application provides a communication method, including: sending downlink control information DCI to a terminal, where the DCI is used to schedule a physical data channel, and the format of the DCI used to schedule the physical data channel Including multiple DCI formats; wherein, the types of DCI sizes corresponding to the multiple DCI formats are less than or equal to N, and N is a positive integer less than or equal to 3; and/or, the DCI corresponding to the multiple DCI formats is used by the terminal When a specific wireless network temporary identification RNTI is scrambled, the types of DCI sizes corresponding to the multiple DCI formats are less than or equal to M, and M is a positive integer less than or equal to 2.
  • the specific formats included in the multiple DCI formats and the alignment manner of the multiple DCI formats can be referred to the specific description of the DCI format in the first aspect, which will not be repeated here.
  • an embodiment of the present application provides a communication method, including: a network device sends downlink control information DCI to a terminal, where the DCI is used to schedule a physical data channel, and the DCI is used to schedule a physical data channel
  • the format includes multiple DCI formats; wherein the DCI size corresponding to the sixth format in the multiple DCI formats is aligned to the DCI size corresponding to the fifth format in the multiple DCI formats, and the DCI corresponding to the fifth format Used for scheduling uplink transmission, and the DCI corresponding to the sixth format is used for scheduling downlink transmission.
  • an embodiment of the present application provides a communication device.
  • the communication device may be a network device, a device in a network device, or a device that can be matched and used with the network device.
  • the device may include a module that performs one-to-one correspondence of the method/operation/step/action described in the eighth aspect or the ninth aspect.
  • the module may be a hardware circuit, software, or hardware Circuit combined with software implementation.
  • the communication device may include a sending module configured to send downlink control information DCI to the terminal, where the DCI is used to schedule physical data channels, and the DCI is used to schedule physical data channels.
  • the DCI format of the data channel includes multiple DCI formats; wherein the types of DCI sizes corresponding to the multiple DCI formats are less than or equal to N, and N is a positive integer less than or equal to 3; and/or, the multiple DCI formats When the corresponding DCI is scrambled using the terminal-specific wireless network temporary identification RNTI, the type of the DCI size corresponding to the multiple DCI formats is less than or equal to M, and M is a positive integer less than or equal to 2.
  • the specific formats included in the multiple DCI formats and the alignment manner of the multiple DCI formats can be referred to the specific description of the DCI format in the eighth aspect, which will not be repeated here.
  • the communication device may include a sending module configured to send downlink control information DCI to the terminal, where the DCI is used to schedule physical data channels, and the DCI is used to schedule physical data channels.
  • the DCI format of the data channel includes multiple DCI formats; wherein the DCI size corresponding to the sixth format in the multiple DCI formats is aligned to the DCI size corresponding to the fifth format in the multiple DCI formats, and the fifth The DCI corresponding to the format is used for scheduling uplink transmission, and the DCI corresponding to the sixth format is used for scheduling downlink transmission.
  • An eleventh aspect of the present application provides a communication device, which includes a processor, configured to implement the method described in the eighth or ninth aspect.
  • the communication device may also include a memory for storing instructions and data.
  • the memory is coupled with the processor, and when the processor executes the instructions stored in the memory, the method described in the eighth aspect or the ninth aspect can be implemented.
  • the communication device may also include a communication interface for the device to communicate with other devices.
  • the communication interface may be a transceiver, circuit, bus, module, pin or other type of communication interface, Other devices can be terminal devices.
  • the communication device includes: a memory for storing program instructions; a processor for sending downlink control information DCI to a terminal device using a communication interface, where the DCI is used for scheduling physical data Channel, the format of the DCI used to schedule the physical data channel includes multiple DCI formats; wherein the types of DCI sizes corresponding to the multiple DCI formats are 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 using a terminal-specific wireless network temporary identification RNTI, the type of the DCI size corresponding to the multiple DCI formats is less than or equal to M, and M is a positive integer less than or equal to 2 .
  • the specific formats included in the multiple DCI formats and the alignment manner of the multiple DCI formats can be referred to the specific description of the DCI format in the eighth aspect, which will not be repeated here.
  • the communication device includes: a memory for storing program instructions; a processor for sending downlink control information DCI to a terminal device using a communication interface, where the DCI is used for scheduling physical data Channel, the format of the DCI used to schedule the physical data channel includes multiple DCI formats; wherein the DCI size corresponding to the sixth format among the multiple DCI formats is aligned to the fifth format corresponding to the multiple DCI formats The DCI size corresponding to the fifth format is used for scheduling uplink transmission, and the DCI corresponding to the sixth format is used for scheduling downlink transmission.
  • the communication device can be implemented in the form of a chip.
  • a twelfth aspect of the present application provides a chip system.
  • the chip system includes a processor and a memory for implementing the method described in the eighth aspect or the ninth aspect.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • a thirteenth aspect of the present application provides a computer-readable storage medium.
  • the computer-readable storage medium includes instructions.
  • the computer executes any of the eighth aspect or the eighth aspect of the embodiments of the present application.
  • the fourteenth aspect of the present application provides a computer program product.
  • the computer program product includes instructions.
  • the instructions run on a computer, the computer executes any possible implementation such as the eighth aspect or the eighth aspect of the embodiments of the present application. Or the ninth aspect or any one of the possible implementation manners of the ninth aspect.
  • an embodiment of the present application provides a communication system, including the device described in the third aspect or the fourth aspect, and the device described in the tenth aspect or the eleventh aspect.
  • Figure 1 shows the DCI size types obtained by a Lacy method
  • FIG. 2 is a possible schematic diagram of a communication system provided by an embodiment of this application.
  • FIG. 3 is a schematic diagram of an embodiment of the communication method of this application.
  • FIG. 4 is a schematic diagram of another embodiment of the communication method of this application.
  • FIG. 5a is a possible detailed flowchart of step 402 in FIG. 4;
  • Fig. 5b shows the format and scrambling mode corresponding to the DCI sent to UE1 after the gNB executes the scheme of Fig. 5a;
  • FIG. 6a is another possible detailed flowchart of step 402 in FIG. 4;
  • Fig. 6b shows the format and scrambling mode corresponding to the DCI sent to UE1 after the gNB executes the scheme of Fig. 6a;
  • FIG. 7a is another possible detailed flowchart of step 402 in FIG. 4;
  • Fig. 7b shows the format and scrambling mode corresponding to the DCI sent to UE1 after the gNB executes the scheme of Fig. 7a;
  • FIG. 8a is another possible detailed flowchart of step 402 in FIG. 4;
  • Fig. 8b shows the format and scrambling mode corresponding to the DCI sent to UE1 after the gNB executes the scheme of Fig. 8a;
  • FIG. 9a is another possible detailed flowchart of step 402 in FIG. 4;
  • Fig. 9b shows the format and scrambling mode corresponding to the DCI sent to UE1 after the gNB executes the scheme of Fig. 9a;
  • FIG. 10 is a schematic diagram of a possible structure of the UE of this application.
  • FIG. 11 is a schematic diagram of a possible structure of the communication device of this application.
  • FIG. 12 is a schematic diagram of a possible structure of the network device of this application.
  • FIG. 13 is a schematic diagram of another possible structure of the communication device of this application.
  • LTE long term evolution
  • FDD frequency division duplex
  • TDD time division duplex
  • 5G fifth generation
  • 5G can also be called new radio (NR).
  • the network device in the embodiment of the present application may be, for example, an access node and/or other network entity.
  • the access network may include a central unit (CU) and a distributed unit (DU). ).
  • the access node in the embodiment of this application can be an evolved base station or an evolved NodeB (evolutional NodeB, eNB or eNodeB) in the LTE system, or it can be a cloud radio access network (CRAN) scenario Wireless controller.
  • 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 future evolved PLMN network, etc.
  • the base station in the 5G network may be referred to as a next generation NodeB (gNB), which is not limited in the embodiment of the present application.
  • the device used to implement the function of the network device may be a network device; it may also be a device capable of supporting the network device to implement the function, such as a chip system, and the device may be installed in the network device.
  • the device used to implement the functions of the network equipment is a network device as an example to describe the technical solutions provided in the embodiments of the present application.
  • the terminal device in the embodiments of this application can be called a terminal, which can be a device with wireless transceiver function, and it can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; it can also be deployed on the water (such as a ship Etc.); it can also be deployed in the air (for example, on airplanes, balloons, and satellites).
  • the terminal device may be a user equipment (UE), where the UE includes a handheld device with a wireless communication function, a vehicle-mounted device, a wearable device, or a computing device.
  • the UE may be a mobile phone, a tablet computer, or a computer with a wireless transceiver function.
  • Terminal equipment can also be virtual reality (VR) terminal equipment, augmented reality (AR) terminal equipment, wireless terminals in industrial control, wireless terminals in unmanned driving, wireless terminals in telemedicine, and smart Wireless terminals in power grids, wireless terminals in smart cities, wireless terminals in smart homes, and so on.
  • the device used to implement the function of the terminal may be a terminal; it may also be a device capable of supporting the terminal to implement the function, such as a chip system, and the device may be installed in the terminal.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the device used to implement the functions of the terminal is a terminal, and the terminal is a UE as an example to describe the technical solutions provided in the embodiments of the present application.
  • the technical solutions provided by the embodiments of the present application can be applied to wireless communication between communication devices.
  • the wireless communication between 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.
  • wireless communication may also be simply referred to as "communication”
  • communication may also be described as "data transmission”, "information transmission” or “transmission”.
  • This technical solution can be used for wireless communication between a scheduling entity (such as a network device) and a subordinate entity (such as a UE).
  • a person skilled in the art can use the technical solution provided in the embodiments of this application to perform communication between other scheduling entities and subordinate entities.
  • Wireless communication such as wireless communication between a macro base station and a micro base station, such as wireless communication between a first terminal and a second terminal.
  • the scheduling entity can allocate resources for the subordinate entities, and/or the scheduling entity can control the wireless communication between them.
  • the information exchanged between the UE and the network equipment is carried through the physical channel.
  • the control information sent by the network device to the UE such as downlink control information (DCI) can be carried by the physical downlink control channel (PDCCH);
  • the data sent by the network device to the UE is also the downlink Data can be carried by a physical downlink shared channel (PDSCH);
  • PDSCH physical downlink shared channel
  • PUSCH physical uplink shared channel
  • the physical channel used to carry DCI can also be a channel with other names, such as enhanced physical downlink control channel (EPDCCH);
  • EPCCH enhanced physical downlink control channel
  • the channel used to carry downlink data at the physical layer can be other than PDSCH Channels with other names;
  • the channels used to carry uplink data at the physical layer may be channels with other names except PUSCH, which is not limited in the embodiments of the present application.
  • a network device can configure a bandwidth part (BWP) for the UE from the system bandwidth or carrier bandwidth, and the UE and the network device exchange information in the BWP.
  • BWP can be understood as a frequency domain working interval configured by the network device for the UE, including frequency domain range and subcarrier spacing.
  • a BWP can only be used to transmit uplink data, and the BWP can be called an uplink BWP; or a BWP can be used only to transmit downlink data, and the BWP can be called a downlink BWP; for a time division duplex system, the uplink BWP and the downlink BWP are often They are configured in pairs, and their center frequencies 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 equipment: PDCCH, PDSCH, and uplink demodulation reference signal.
  • the UE may send one or more of the following channels to the network device: PUSCH, PUCCH, and downlink demodulation reference signals.
  • the network device may perform channel configuration on the channel transmitted in the BWP. Taking the configuration of the downlink BWP as an example, the network device can perform PDSCH configuration and PDCCH configuration.
  • configuring the PDCCH includes configuring the search space and control resource set (CORESET) of the PDCCH.
  • configuring the PDCCH also includes configuring the DCI format that the UE needs to detect in each search space.
  • the network device can configure multiple BWPs for the UE and activate one or more BWPs from them.
  • the network device can transmit PDSCH, PUSCH, and/or PDCCH to the UE on the activated BWP, and cannot transmit PDSCH to the UE on the BWP that is not activated. , PUSCH, and PDCCH.
  • part or all of the configuration information in the BWP configuration information may also be preset, that is, the information is known in advance by the network device and the UE.
  • the communication system can support a variety of DCI in different formats.
  • a DCI can include multiple indicator fields, and each indicator field corresponds to its own indicator function.
  • DCI corresponding to different DCI formats may include one or more different indication fields.
  • DCI can be divided into: DCI for scheduling downlink (DL) transmission and DCI for scheduling uplink (uplink, UL) transmission; from the perspective of whether it is independent of UE-specific high-level signaling configuration, or from
  • DCI can be divided into: fallback DCI (fallback DCI) and non-fallback DCI (non-fallback DCI).
  • the backed-out DCI may also be called back-off DCI
  • the non-back-off DCI may also be called non-back-off DCI.
  • the format of the DCI for scheduling downlink transmission and the format of the DCI for scheduling uplink transmission may be different, and the format of the back-off DCI and the format of the non-back-off DCI may be different.
  • the DCI of the fallback hardly depends on the high-level signaling configuration of the UE.
  • the indication field and the size of each field are only related to the common configuration of the cell or are predefined; the DCI that is not the fallback includes many
  • the indication fields and the sizes of these fields are usually determined according to the high-level signaling configuration of the UE.
  • the non-fallback DCI can indicate more functions than the fallback DCI can indicate.
  • Table 1 shows an example of DCI format classification for scheduling PDSCH and PUSCH.
  • the DCI size corresponding to different DCI formats may be different.
  • the DCI size specifically refers to the payload size of the DCI, or the number of bits included in the DCI.
  • the network device sends the PDCCH in the time-frequency resources indicated by the CORESET and the search space. Accordingly, the UE in the time-frequency resources determined according to the CORESET and the search space, compares the DCI carried in the PDCCH according to the DCI size corresponding to the DCI format to be detected Perform blind detection.
  • the process of receiving or detecting DCI can also be considered as the process of receiving or detecting PDCCH.
  • the UE can be configured to detect DCI of one or two formats. However, since the location of time-frequency resources in different search spaces may overlap, the UE may need to detect more DCI formats at the same resource location. The more DCI formats, the more types of DCI sizes that the UE needs to detect, and the more times the PDCCH is blindly detected, the UE has too much overhead and the UE's power consumption is higher.
  • the search space of the PDCCH can be divided into a common search space (CSS) and a UE-specific search space (UE-specific search space, USS).
  • the DCI sent in the CSS can be received by all UEs in the cell, and the DCI sent in the USS can be received by a specific UE or UE group; or the DCI sent in the CSS can be received by the UE group and sent in the USS
  • the DCI can be received by a specific UE.
  • one UE group includes one or more UEs, which is not limited in the embodiment of the present application.
  • the DCI with fallback can be sent; in the USS, the DCI with fallback and non-fallback can be sent.
  • the search space of the PDCCH may be configured (indicated) by the network equipment for the UE through radio resource control (radio resource control, RRC) signaling.
  • RRC radio resource control
  • the network device can configure one or more search spaces for the UE.
  • the RRC signaling may be specific to the UE, or it may be shared with other UEs (common), which is not limited in the embodiment of the present application.
  • the network device can configure for the UE whether the type of the search space is a public search space or a UE-specific search space.
  • the network device can also configure one or more of the following parameters of the search space for the UE: frequency domain resource location, aggregation level size, number of candidate PDCCHs, detection period, time domain resource location, and data transmitted in the search space.
  • the format of DCI For example, the format of DCI in a common search space can be configured as 0_0 and 1_0.
  • the format of the DCI in a UE-specific search space may be configured as 0_1 and 1_1, or the format of the DCI in a UE-specific search space may be configured as 0_0 and 1_0.
  • the time domain resource location includes: the first time unit (such as a time slot) offset of the search space in the detection period, the number of consecutive first time units occupied by the search space in the detection period, and each first time unit The offset of the second time unit (such as the symbol) of the search space in the time unit, and the number of second time units occupied by the search space in each first time unit.
  • the first time unit such as a time slot
  • the second time unit such as the symbol
  • the frequency domain resource location of the search space and the number of second time units of the search space in each first time unit can be configured in the following manner: the network device indicates to the UE the control resource set corresponding to the search space ( control resource set, CORESET), the parameters of the CORESET can be regarded as the parameters of the search space.
  • the network device indicates the CORESET through RRC signaling: the frequency domain resource location, and the number of second time units of the CORESET in each first time unit.
  • one CORESET may correspond to one search space, or may correspond to multiple different search spaces, which is not limited in the embodiment of the present application.
  • the search space A corresponds to CORESET A, which occupies 3 symbols in the time domain.
  • the detection cycle of search space A is 10 time slots
  • the offset of search space A in the detection cycle is 3 time slots
  • the continuous time slots occupied by search space A in the detection cycle are 2 time slots, each time slot
  • the symbol offset of the search space A in the slot is 3 symbols.
  • the frequency domain resource position of search space A is CORESET A's frequency domain resource position
  • the time domain resource position of search space A is: in every 10 timeslots, in the fourth and fifth timeslots In each slot, starting from the third symbol, a total of 3 symbols are occupied.
  • the time-frequency resource obtained from the position of the frequency domain resource and the position of the time domain resource in the search space A may be referred to as the time-frequency resource indicated by the search space A and CORESET A.
  • the UE-specific radio network temporary identity can be used to scramble the DCI.
  • the UE-specific RNTI can be the UE’s cell RNTI (cell RNTI, C-RNTI), configured scheduling RNTI (configured scheduling RNTI, CS-RNTI), or modulation and coding strategy cell RNTI (modulation and coding scheme C-RNTI, MCS). -C-RNTI) and so on.
  • C-RNTI is an important identifier for network equipment (such as base station) to identify the UE at the access network level, and the base station uses C-RNTI to scramble DCI, which is equivalent to performing DCI between the base station and the UE through C-RNTI Encrypted transmission.
  • the ability to detect the DCI scrambled by the C-RNTI reflects the basic ability of the UE to detect the DCI sent by the base station to a certain extent.
  • the network equipment can send back DCI to the UE for scheduling cell system messages, scheduling a group of UEs, or scheduling non-connected UEs.
  • system messages RNTI system information RNTI, SI-RNTI
  • Public RNTIs such as RNTI (paging RNTI, P-RNTI) or random access RNTI (random access RNTI, RA-RNTI) scramble the DCI.
  • the non-connected state can also be considered as an idle state or an inactive state.
  • the connected state can be considered an active state. From the perspective of whether an RRC connection is established between the UE and the network equipment, the connected state is also called the RRC connected (connected) state, and the non-connected state includes the RRC inactive state and the RRC idle state.
  • the network device aligns the sizes of the DCIs of these two formats by zero-padding or puncturing, so that the DCI sizes of different DCI formats are the same, and The DCI format 0_0 is aligned with the DCI format 1_0; the network device will adjust the size between the fallback DCIs sent in the USS. Specifically, the smaller of the DCI format 0_0 and the DCI format 1_0 is filled with zeros to the larger of the DCI format 0_0. Way to align
  • the network device does not perform alignment in any way.
  • Fig. 1 shows an example of the above-mentioned prescribed DCI size types. If the DCI sizes corresponding to the DCI formats in the same dashed frame are different, they will be aligned to the same size.
  • the RNTI in parentheses after the DCI format represents the RNTI that may be used to scramble the DCI of the corresponding format.
  • the network device transfers the fallback DCI size in the USS to the CSS
  • the back-off DCI size is aligned, refer to the curve with arrows in Figure 1.
  • the types of DCI sizes of the DCI scrambled by the C-RNTI that the UE needs to detect are four, and the four types of DCI correspond to the figure.
  • the sizes of DCI format 0_1 and DCI format 1_1 in USS are the same without aligning; or, the size of DCI format 0_1 or DCI format 1_1 in USS is the same as that in USS.
  • the DCI format 0_0 or the DCI format 1_0 have the same size. At this time, since the size of the DCI scrambled by the C-RNTI does not exceed three types, the alignment operation is not required.
  • the types of DCI sizes can be limited to no more than 4, and the types of DCI scrambled using C-RNTI are limited to no more than 3.
  • the types of DCI sizes that the UE needs to detect There are still many. In the process of blind detection of the PDCCH by the UE at each resource location, the number of blind detections is still large, and the detection process occupies a large amount of calculation and storage of the UE, which increases the complexity of the UE.
  • a reduced-capability (REDCAP) UE will be supported in the NR communication system, officially named NR with reduced capability.
  • Equipment Reduced Capability NR Devices
  • NR-REDCAP UE the names used were NR-light UE and massive machine type communication (NR mMTC) UE.
  • the maximum bandwidth supported by the REDCAP UE is smaller than that of the traditional UE, and/or the number of antennas supported is smaller than that of the traditional UE.
  • the present application provides a communication method and device to reduce the number of PDCCH detections of the UE (especially the REDCAP UE), thereby reducing the complexity of the UE.
  • this method can also be applied to other types of UEs, such as UEs that support enhanced Mobile Broadband (eMBB) services or UEs that support (ultra-reliable low-latency communication, URLLC) services. It is used to reduce the power consumption of the UE, which is not limited in the embodiment of the present application.
  • eMBB enhanced Mobile Broadband
  • URLLC ultra-reliable low-latency communication
  • the embodiments of the present application can be applied to an NR communication system, and can also be applied to other communication systems, as long as there is a sending entity and a receiving entity of downlink control information in the communication system.
  • FIG. 2 is a possible schematic diagram of a communication system provided by an embodiment of the application.
  • the communication system includes network equipment and UE1 to UE5.
  • UE1 ⁇ UE5 can send uplink data to network equipment, and network equipment can receive uplink data sent by UE1 ⁇ UE5; network equipment can send downlink data to UE1 ⁇ UE5, and UE1 ⁇ UE5 can receive downlink data sent by network equipment. data.
  • UE4 and UE5 can form a sub-communication system.
  • UE5 After receiving the downlink information sent by the network device, UE5 can forward the downlink information to UE4, UE4 can send uplink data to UE5, and UE5 forwards the uplink data to the network device. .
  • the downlink data received by the UE in the communication system can be directly sent by the network device to the UE, or it can be forwarded to the UE by other communication nodes in the communication system; the uplink data sent by the UE can be sent directly. To the network device, it can also be forwarded to the network device by other communication nodes in the communication system.
  • FIG. 3 is a schematic diagram of a communication method provided by an embodiment of this application.
  • a possible embodiment of the communication method of this application may include the following steps:
  • a network device sends DCI to a UE
  • the UE detects DCI from a network device.
  • the arrowed line between the network device and the UE represents step 301 and step 302 at the same time.
  • the network device can send DCI to the UE, and the UE can detect the DCI.
  • the DCI is used to schedule the physical data channel, and the format of the DCI used to schedule the physical data channel includes multiple DCI formats.
  • the type of the size of the DCI used to schedule the physical data channel does not exceed N, and N is a positive integer less than or equal to 3, and/or the type of the size of the DCI scrambled by the UE-specific wireless network temporary identifier RNTI does not Over M, M is a positive integer less than or equal to 2.
  • the types of DCI sizes corresponding to multiple DCI formats are less than or equal to N, and N is a positive integer less than or equal to 3, and when the DCI corresponding to multiple DCI formats is scrambled using the UE-specific wireless network temporary identifier RNTI, it is often
  • the type of DCI size corresponding to each DCI format is less than or equal to M, and M is a positive integer less than or equal to 2.
  • N is a positive integer less than or equal to 3.
  • the type of the DCI size corresponding to the multiple DCI formats is less than or equal to M, and M is a positive integer less than or equal to 2.
  • N is a positive integer less than or equal to 3
  • M are positive integers less than or equal to 2
  • the types of DCI sizes corresponding to multiple DCI formats are less than or equal to N, and N is a positive integer less than or equal to 3
  • the DCI corresponding to multiple DCI formats is used in common
  • the types of DCI sizes corresponding to multiple DCI formats are less than or equal to N, and N is a positive integer less than or equal to 3.
  • multiple DCI formats can correspond to multiple DCIs, one DCI of the multiple DCIs can be scrambled using either a common RNTI or a UE-specific RNTI, and different DCIs in the multiple DCIs It can be scrambled by using the same type or different types of RNTI, and the types of DCI sizes corresponding to the multiple DCIs are less than or equal to N, and N is a positive integer less than or equal to 3.
  • the types of DCI sizes corresponding to multiple DCI formats are less than or equal to N, and N is a positive integer less than or equal to 3; and/or, the DCI corresponding to multiple DCI formats is used in UE-specific radio
  • the types of DCI sizes corresponding to multiple DCI formats are less than or equal to NL
  • N is a positive integer less than or equal to 3
  • L is a positive integer less than N, for example, L is 1 or 2.
  • the physical data channel is used to transmit uplink data (such as the physical data channel is PUSCH), or is used to transmit downlink data (such as the physical data channel is PUSCH), or includes the physical channel used to transmit uplink data (such as PUSCH) and The physical channel used to transmit downlink data (such as 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 (virtual RB, VRB) to physical RB ( physical RB, PRB) mapping, modulation and coding strategy, new data indication, redundancy version, hybrid automatic repeat request (HARQ) process number, downlink allocation index, PUCCH transmission power control command, PUCCH resource indication , PDSCH to HARQ feedback time indication, antenna port, sounding reference signal (sounding reference signal, SRS) request, transmission configuration indication, and demodulation reference signal (demodulation reference signal, DMRS) sequence initialization.
  • the transmission parameters of the PDSCH may also be referred to as PDSCH indication information.
  • the DCI used to schedule PUSCH may indicate one or more of the following transmission parameters of 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 offset indication, DMRS sequence initialization, Uplink shared channel (UL-SCH) indication and UL/supplementary UL (SUL) indication.
  • the transmission parameters of the PUSCH may also be referred to as the indication information of the PUSCH.
  • the UE can transmit the corresponding physical data channel according to the detected DCI according to the DCI.
  • the UE may receive the PDSCH sent by the network device according to the transmission parameters of the PDSCH in the DCI. Assuming that the DCI detected by the UE is used to schedule the PUSCH, the UE can send the PUSCH to the network device according to the transmission parameters of the PUSCH in the DCI.
  • DCI_b the DCI sent by the network device in step 301 and detected by the UE in step 302
  • DCI_b the DCI format corresponding to DCI_b
  • format A the DCI format corresponding to DCI_b
  • DCI_b meets the requirement, and there is no need to perform puncturing or zero padding operations on DCI_b, and DCI_b and DCI_a are the same.
  • DCI_a is the original DCI obtained according to format A without razor operation.
  • the network device obtains DCI_a according to format A, and the network device adjusts the size of DCI_a according to the Lacy rule to obtain DCI_b.
  • the loads of DCI_a and DCI_b are different, but the corresponding DCI formats of the two are the same, and both are format A.
  • step 301 the network device sends DCI_b.
  • the UE may determine the adjusted size of each DCI format according to the Lacy rule, including determining the DCI size corresponding to format A.
  • the DCI corresponding to format A may not need to perform a align operation to meet the demand.
  • the UE may detect the DCI carried in the PDCCH according to the determined adjusted size of each DCI format, including detecting the DCI_b carried in the PDCCH according to the DCI size corresponding to the adjusted format A.
  • the UE may decode DCI_b according to the Lacy rule. For example, restore DCI_b to DCI_a, and then decode DCI_a to obtain the transmission parameters carried by it.
  • the network device aligns the DCI corresponding to some or all of the DCI format used to schedule the physical data channel according to the align rule, and restricts the type of the size of the DCI used to schedule the physical data channel sent by the network device to be less than or equal to N, N is a positive integer less than or equal to 3; and/or, the type of DCI used to schedule physical data channels that is scrambled by the network device using the UE-specific wireless network temporary identification RNTI, which is sent by the network device, is used to schedule the physical data channel When it is less than or equal to M, M is a positive integer less than or equal to 2.
  • the UE determines the size of each DCI format that needs to be adjusted according to the Lacy rule, which helps to successfully detect the DCI corresponding to the corresponding DCI format carried in the PDCCH, and correctly parse the information in the DCI according to the Lacy rule.
  • the DCI used to schedule the physical data channel includes the third format and the fourth format detected in the terminal-specific search space USS, and the third format and the fourth format detected in the common search space CSS.
  • the DCI corresponding to the third format is used to schedule uplink transmissions (such as PUSCH)
  • the DCI corresponding to the fourth format is used to schedule downlink transmissions (such as PDSCH).
  • the DCI transmitted in the USS is scrambled using a UE-specific RNTI.
  • the DCI transmitted in the CSS is scrambled using a UE-specific RNTI or is scrambled using a common RNTI.
  • the third format is 0_0
  • the fourth format is 1_0.
  • DCI format indication 1 bit, used to distinguish whether the DCI schedules UL transmission or DL transmission.
  • the value of this field in 0_0 is 0, which means that it schedules a UL transmission;
  • Frequency domain resource allocation X bits are used to indicate the frequency domain resources allocated in this scheduling.
  • PRB physical resource blocks
  • Time domain resource allocation 4 bits, used to indicate the time domain resources allocated in this scheduling.
  • the state 0-15 indicated by the 4 bits indicates a row in a predefined table, and each row indicates a certain time domain start Position and length;
  • Frequency hopping flag 1 bit, used to indicate whether the UE's UL transmission is frequency hopping;
  • Modulation and coding strategy 5 bits, used to indicate the modulation mode and coding rate of the PUSCH scheduled this time;
  • New data indication 1 bit, used to indicate whether the data scheduled this time is new data or old data
  • Redundancy version 2 bits, used to indicate the redundancy version of the data scheduled this time; data can have four redundancy versions: 0, 1, 2, and 3 after being encoded;
  • HARQ process number 4 bits, used to indicate the data of which HARQ process is scheduled this time;
  • PUSCH transmit power control command 2 bits, used to indicate the amount of power adjustment for the UE to transmit PUSCH;
  • UL/SUL indication 1 bit, used to indicate whether the UL transmission scheduled this time is transmitted on a UL carrier or a supplementary UL (SUL) carrier; optionally, this is only possible when the SUL carrier is configured Domain exists
  • DCI format 1_0 has the same meaning as DCI format 0_0, except that UL becomes DL, which will not be repeated here, but different fields will be introduced:
  • DCI format indication field 1 bit, used to distinguish whether the DCI schedules UL transmission or DL transmission.
  • the value of this field in 1_0 is 1, indicating that it schedules a DL transmission;
  • VRB to PRB mapping 1 bit, indicating whether interleaving mapping is performed between VRB and PRB in this DL transmission;
  • Downlink allocation index 2 bits, used to indicate the cumulative number of downlink transmissions that are scheduled by the network device up to the current time and correspond to the same hybrid automatic repeat request acknowledgement character (HARQ-ACK) feedback;
  • HARQ-ACK hybrid automatic repeat request acknowledgement character
  • PUCCH transmit power control command 2 bits, used to instruct the UE to send the physical uplink control channel (physical downlink control channel, PUCCH) power adjustment amount when it performs HARQ-ACK feedback for this scheduled PDSCH;
  • PUCCH resource indicator 3 bits, used to indicate the PUCCH resource used when the UE performs HARQ-ACK feedback for the PDSCH scheduled this time;
  • PDSCH to HARQ feedback time indicator 3 bits, used to indicate the time interval between the PDSCH scheduled this time and the HARQ feedback of the PDSCH.
  • p is a positive integer.
  • 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 the DCI size corresponding to the third format detected in the CSS is the same as the fourth format
  • the corresponding DCI sizes are aligned to the same, and 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 fourth format detected in the CSS
  • 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
  • the type of DCI used to schedule the physical data channel sent by the network device is restricted to be less than or equal to N, where N is a positive integer less than or equal to 3; and/or the UE-specific wireless network that is sent by the network device is used
  • the DCI used to schedule the physical data channel includes the first format and the second format detected in the UE-specific search space USS, where the DCI corresponding to the first format is used to schedule uplink transmission (such as PUSCH), and the second format The corresponding DCI is used to schedule downlink transmissions (such as PDSCH), and the DCI transmitted in the USS is scrambled using a UE-specific RNTI.
  • the DCI corresponding to the first format and the DCI corresponding to the second format are both non-fallback DCI.
  • the first format may be 0_1, and the second format may be 1_1.
  • the embodiment of the present application does not limit the domain and the size of the first format to be the same as 0_1, and does not limit the domain and the size of the second format. 1_1 is the same. Therefore, in the embodiment of the present application, the first format is recorded as 0_3, and the second format is recorded as 1_3.
  • the DCI in the first format and the second format in the present invention can also have other identification methods.
  • the first format can be 4_0
  • the second format can be 4_1, etc., as long as the essence remains unchanged, the present invention does this. No restrictions.
  • Table 3 below provides a possible definition of DCI format 0_3 and DCI format 1_3.
  • the domains included in DCI format 0_3 and DCI format 1_3 and the size of each domain are shown in Table 3 below:
  • BWP indication 0 to 2 bits, used to indicate the BWP where the scheduled DL (or UL) transmission is located, the specific number of bits is determined by the number of DL BWP or UL BWP configured by the UE;
  • Antenna port used to indicate the DMRS port sent by the UE.
  • the specific number of bits is determined by the DMRS type and maximum length configured by the UE;
  • SRS request used to trigger the UE to transmit aperiodic SRS, the specific number of bits is determined by the UE's SRS configuration;
  • CSI request used to trigger the UE to perform aperiodic CSI reporting, the specific number of bits is determined by the UE's CSI reporting configuration;
  • Beta offset indication it is used to indicate the resource for the UE to report CSI information in the PUSCH. The specific number of bits is determined by the configuration of the Beta offset indication;
  • DMRS sequence initialization used to indicate the scrambling code used for the initialization of the DMRS sequence of the UE, the specific number of bits is determined by the DMRS configuration;
  • UL-SCH indication 1 bit, used to indicate whether the UE transmits an uplink shared channel (UL-SCH) on the PUSCH channel in this UL transmission, where UL-SCH is the uplink shared channel in the logical channel;
  • Transmission configuration indication used to indicate the downlink reference signal permitted to be co-located in the PDSCH or DMRS in this DL transmission, and the specific number of bits is determined by the configuration of the TCI.
  • Table 3 can be used as a possible design method of the UL non-fallback and DL non-fallback DCI of the UE, that is, the design method of the DCI in the first format and the DCI in the second format, including the fields
  • the order of the can be changed, the number of bits in each field can be different, or it may include some other fields not listed here, or it may not include some fields.
  • the DCI size corresponding to the first format is aligned to the DCI size corresponding to the second format.
  • the DCI size corresponding to the second format is aligned to the DCI size corresponding to the first format.
  • the DCI size corresponding to the first format is smaller than the DCI size corresponding to the second format, then the DCI size corresponding to the first format is aligned to the DCI size corresponding to the second format;
  • the DCI size corresponding to the format is smaller than the DCI size corresponding to the first format, and the DCI size corresponding to the second format is aligned to the DCI size corresponding to the first format.
  • the DCI used to schedule the physical data channel includes the first format, the second format, the third format, and the fourth format detected in the UE-specific search space USS.
  • the DCI corresponding to the first format is used to schedule uplink transmission (such as PUSCH)
  • the DCI corresponding to the third format is used to schedule uplink transmission (such as PUSCH)
  • the first format is different from the third format
  • the DCI corresponding to the fourth format is used for scheduling downlink transmission (such as PDSCH)
  • the second format is different from the fourth format
  • the DCI corresponding to the above formats transmitted in the USS is used UE-specific RNTI scrambling.
  • the first format is the aforementioned DCI format 0_3
  • the second format is the aforementioned DCI format 1_3
  • the third format is 0_0
  • the fourth format is 1_0.
  • the third format transmitted in the USS corresponds to The DCI size is aligned to the DCI size corresponding to the first format or 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 second format The corresponding DCI size.
  • the DCI size corresponding to format A is aligned to the DCI size corresponding to format B, including the following two ways:
  • Method 1 If the DCI size corresponding to format A is smaller than the DCI size corresponding to format B, then the DCI corresponding to format A is filled with at least one padding bit (for example, 0 or 1), and the DCI size corresponding to format A after padding is the same as The DCI corresponding to format B has the same size.
  • the DCI size corresponding to format A is greater than the DCI size corresponding to format B, then the K fields of DCI corresponding to format A are truncated, or at least one bit of the K fields in the DCI corresponding to format A is Truncated.
  • the size of the DCI corresponding to the truncated format B is the same as the size of the DCI corresponding to the format A, where K is a positive integer.
  • the truncated field in the truncated field, at least one high-order bit of the truncated field is truncated, and even all bits in the truncated field are truncated.
  • the K domains include at least one of the following domains:
  • format A is format 1_3
  • the K domains include at least one of the following domains: frequency domain resource allocation domain, time domain resource allocation domain, PUCCH resource indication domain, SRS request domain, and PDSCH to HARQ feedback time indication domain.
  • format A is format 0_3
  • the K domains include at least one of the following domains: frequency domain resource allocation domain, time domain resource allocation domain, SRS request domain, and DMRS sequence initialization domain.
  • the DCI corresponding to the DCI format with a smaller load can be aligned with the DCI corresponding to the DCI format with a larger load. In this way, only method 1 is required for alignment. The load in the DCI will be lost.
  • the following takes the format A as the second format (such as 1_3 above) and the format B as the first format (such as 0_3 above) as an example to specifically introduce the above-mentioned Lacy mode.
  • the network device can fill p padding bits in the DCI corresponding to DCI format 1_3, for example, p “0”s can be filled at the end of the payload. "Or "1", so that the DCI sizes corresponding to the two DCI formats are the same, where p is a positive integer.
  • the UE can ignore the last p bits of the DCI payload, or truncate the last p bits of the DCI to obtain the DCI corresponding to the unadjusted DCI format 1_3 .
  • the network device can truncate at least one bit of at least one field in the DCI corresponding to DCI format 1_3, for example, truncate the DCI corresponding to DCI format 1_3
  • the higher one or more bits of the resource allocation field in the intermediate frequency domain, or the higher one or more bits of the time domain resource allocation field in DCI format 1_3 are truncated, or all the bits of the SRS request field are truncated, so that two types of DCI
  • the DCI corresponding to the format has the same size.
  • the UE can fill the high 3 bits of the frequency domain resource allocation field in the DCI with a predefined value (for example, "0"), and consider the value indicated by the field " 00011".
  • REDCAP UE as a sensor terminal or video terminal, has a large uplink transmission volume, so its transmission service is the dominant player.
  • DCI size corresponding to DCI format 0_3 is aligned to the DCI size corresponding to DCI format 0_3, which means that the DCI format of DL scheduling corresponds to
  • the DCI size is aligned with the DCI size corresponding to the UL scheduled DCI format, which is beneficial to protect the scheduling performance of uplink transmission.
  • DCI format 0_3 If the number of bits in DCI format 0_3 is less than the number of bits in DCI format 1_3, some fields in DCI format 1_3 can be truncated, instead of filling useless bits in DCI format 0_3, so as to reduce the load of DCI format 0_3 as much as possible. Ensure the reliability of its detection. For example, if the number of bits in DCI format 0_3 is q bits less than the number of bits in DCI format 1_3 before aligning, the high q bits of the specific indicator field (such as the frequency domain resource allocation indicator field) of DCI format 1_3 can be truncated , So as to align the DCI format 1_3 to the size of the DCI format 0_3. Among them, q is a positive integer.
  • another possible embodiment of the communication method of the present application includes the following steps 401 to 409.
  • the gNB sends RRC configuration information to UE1.
  • the RRC configuration information is used to indicate the resource location of the PDCCH configured for the UE1 (including the resource location of the CSS and the resource location of the USS) and the DCI format that the UE1 needs to detect.
  • the communication method provided in this application may not perform step 401, and the gNB and UE1 may determine the PDCCH resource location allocated to UE1 and what UE1 needs to detect according to preset or predefined configuration information. DCI format.
  • the gNB determines the Latch rule corresponding to each DCI format that UE1 needs to detect.
  • the aligning rule may be the aligning rule described in the method embodiment involved in FIG. 3.
  • the Lacy rule is used to limit the types of DCI sizes corresponding to each DCI format that UE1 needs to detect to no more than N, where N is a positive integer less than or equal to 3, and/or the UE-specific wireless network temporary identification will be used
  • the type of DCI size corresponding to each DCI format scrambled by RNTI is limited to less than or equal to M, and M is a positive integer less than or equal to 2.
  • the UE1 determines the Latch rule corresponding to each DCI format that needs to be detected.
  • the UE1 After receiving the RRC configuration information from the gNB, the UE1 determines each DCI format to be detected, and determines the alignment rule corresponding to each DCI format, and the alignment rule is the same as the alignment rule determined by the gNB in step 402.
  • the UE1 determines the size of the DCI corresponding to each DCI format after being aligned according to the alignment rule.
  • the UE1 determines the size of the DCI corresponding to each DCI format after being aligned according to the aligning rule, and the type of the aligning size of the DCI may be the type of the DCI size corresponding to the multiple DCI formats described in the method embodiment involved in FIG. 3 ,
  • the size of the DCI after being aligned does not exceed N, and N is a positive integer less than or equal to 3, and/or the size of the DCI that is scrambled using the UE-specific wireless network temporary identifier RNTI and the DCI size corresponding to each DCI format
  • the kind is less than or equal to M, and M is a positive integer less than or equal to 2.
  • the UE1 performs blind detection on the PDCCH according to the RRC configuration information and the size of the DCI corresponding to each DCI format to be detected after being aligned.
  • the gNB adjusts the size of DCI_a according to the Lacy rule to obtain DCI_b.
  • the DCI to be sent by the gNB to the UE1 is called DCI_a, and the format of the DCI_a is called format A. Then, the gNB adjusts the size of DCI_a according to the Latch 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 format of the two is format A.
  • the gNB adjusts the size of DCI_a according to the Lacy rule, and reference may be made to the adjustment process described in the method embodiment involved in FIG. 3, which will not be repeated here.
  • step 402 and step 406 by the gNB The sequence between the execution of step 402 and step 406 by the gNB and the execution of step 403 to step 405 by the UE1 is not limited.
  • the gNB sends DCI_b to UE1, and UE1 detects DCI_b.
  • the UE1 can detect the DCI_b carried in the PDCCH from the gNB according to the adjusted DCI size corresponding to format A (the same size as the DCI_b) at the configured resource location.
  • the UE1 restores DCI_b to DCI_a according to the Lacy rule.
  • the UE1 After the UE1 detects DCI_b, it can determine the format of DCI_b as format A according to the DCI format indication field, restore DCI_b to DCI_a according to the Latch rule corresponding to format A, and decode DCI_a to obtain the transmission parameters carried in DCI_a.
  • UE1 transmits the corresponding physical data channel according to DCI_a.
  • the UE can detect the PDSCH sent by the network device according to the transmission parameters of the PDSCH in the DCI_a. Assuming that the DCI_a detected by the UE1 is used to schedule the PUSCH, the UE can send the PUSCH to the network device according to the transmission parameters of the PUSCH in the DCI_a.
  • the step 402 in the embodiment corresponding to FIG. 4 will be introduced below.
  • the type of the size of the DCI used to schedule the physical data channel does not exceed N, where N is a positive integer less than or equal to 3, and/or the DCI scrambled by the UE-specific wireless network temporary identification RNTI
  • the size of the type does not exceed M, and M is a positive integer less than or equal to 2.
  • the size and type of DCI that the UE1 needs to detect can be reduced to three, and/or the size and type of DCI scrambled by a specific RNTI of the UE1 that the UE needs to be detected can be reduced to two.
  • Each DCI format that UE1 needs to detect includes DCI format 0_0 and DCI format 1_0 sent in CSS, and DCI format 0_0, DCI format 0_3, DCI format 1_0 and DCI format 1_3 sent in USS.
  • step 402 includes the following refinement steps 4021a to 4026a.
  • the gNB aligns the DCI size corresponding to the DCI format 0_0 sent in the CSS to the DCI size corresponding to the DCI format 1_0.
  • the DCI format 0_0 sent in the CSS is aligned with the DCI size corresponding to the DCI format 1_0, considering that important public information or important configuration information is often required to be delivered in the CSS, so it is more necessary to ensure the accuracy of the downlink transmission instructions.
  • the gNB aligns the DCI size corresponding to the DCI format 0_0 sent in the USS to the DCI size corresponding to the DCI format 1_0.
  • the DCI format with a smaller load is supplemented with padding bits to the DCI format with a larger load. For example, if the number of loads of 0_0 is less than 1_0 before the alignment, then 0_0 is filled with 0 until the size of 0_0 is equal to 1_0 is the same; on the contrary, if the load number of 0_0 is more than 1_0 before the alignment, 0 is filled in 1_0 until the size of 1_0 is the same as 0_0.
  • This method does not lose any information bits (payload) in the DCI format, and ensures the accuracy of the indication.
  • the DCI size corresponding to the DCI format 0_0 sent in the USS is smaller than the DCI size corresponding to the DCI format 1_0, so the gNB corresponds the DCI size corresponding to the DCI format 0_0 sent in the USS to the DCI format 1_0
  • the size of the DCI is Latched.
  • the embodiment of the present application does not limit the sequence between step 4021a and step 4022a.
  • the gNB judges whether the DCI size type 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, execute step 4024a, and if yes, end.
  • step 4021a and step 4022a if the size category of the DCI that UE1 needs to detect is less than or equal to 3, and the size category of the DCI scrambled by the C-RNTI that UE1 needs to detect is less than or equal to 2, the step is considered complete 402, that is, the process of step 402 ends. If the size category of the DCI that UE1 needs to detect is greater than 3, or the size category of the DCI scrambled by the C-RNTI that UE1 needs to detect is greater than or equal to 2, step 4024a is executed.
  • the gNB aligns the DCI format 0_0 and DCI format 1_0 sent in the USS to the DCI format 1_0 sent in the CSS.
  • step 4024a may specifically include the following steps 1 to 3.
  • the DCI format 0_0 in the USS after the above step 2 is aligned to the DCI format 1_0.
  • step 4024a can also be understood as the DCI format 0_0 and DCI sent by the gNB in the USS The format 1_0 is aligned with the DCI format 0_0 sent in the CSS.
  • the gNB determines whether the DCI size type 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 4026a is executed, and if so, the end is ended.
  • step 4024a if the size type of the DCI that UE1 needs to detect is less than or equal to 3, and the size type of the DCI scrambled by the C-RNTI that UE1 needs to detect is less than or equal to 2, it is considered that step 402 is completed, that is End the flow of step 402. If the size category of the DCI that UE1 needs to detect is greater than 3, or the size category of the DCI scrambled by the C-RNTI that UE1 needs to detect is greater than or equal to 2, step 4026a is executed.
  • the gNB aligns the DCI size corresponding to the DCI format 0_3 sent in the USS with the DCI size corresponding to the DCI format 1_3;
  • the DCI format with a smaller load is supplemented with padding bits to align the DCI format with a larger load, or regardless of the relationship between the DCI size corresponding to DCI format 0_3 and the DCI size corresponding to DCI format 1_3, it will The DCI size corresponding to the DCI format 1_3 is aligned to the DCI size corresponding to the DCI format 0_3.
  • the gNB aligns the DCI size corresponding to the DCI format 0_3 sent in the USS to the DCI size corresponding to the DCI format 1_3.
  • the gNB can determine the alignment rule corresponding to each DCI format that UE1 needs to detect, that is, the DCI size corresponding to DCI format 0_0 sent in the CSS is aligned to the DCI size corresponding to DCI format 1_0;
  • the DCI size corresponding to the DCI format 0_0 sent in the USS is aligned with the DCI size corresponding to the DCI format 1_0;
  • the DCI format 0_0 and DCI format 1_0 sent in the USS are aligned with the DCI format 1_0 sent in the CSS; in the USS
  • the DCI size corresponding to the DCI format 0_3 sent in the DCI format is aligned with the DCI size corresponding to the DCI format 1_3.
  • the align rule of DCI_a can be determined according to the search space of DCI_a and its format A. Assuming that the search space is USS and format A is DCI format 0_0, then gNB The DCI_a may be aligned with the DCI size corresponding to the DCI format 1_0 sent in the CSS. Assuming that in step 406, the gNB fills p "0"s at the end of the payload of DCI_a, and DCI_a filled with p "0"s is called DCI_b, where p is a positive integer.
  • UE1 can determine the alignment rule corresponding to each DCI format that UE1 needs to detect, that is: the DCI size corresponding to DCI format 0_0 sent in the CSS is aligned to the DCI size corresponding to DCI format 1_0; the one sent in USS The DCI size corresponding to DCI format 0_0 is aligned with the DCI size corresponding to DCI format 1_0; the DCI format 0_0 and DCI format 1_0 sent in the USS are aligned to the DCI format 1_0 sent in the CSS; the DCI format sent in the USS The DCI size corresponding to 0_3 is aligned with the DCI size corresponding to DCI format 1_3.
  • UE1 can determine the size of the DCI format 0_0 and DCI format 1_0 sent in the CSS after being aligned according to the Latch rule, and determine the DCI format 0_0, DCI format 0_3, and DCI format sent in the USS. The size of the DCI corresponding to 1_0 and DCI format 1_3 after being aligned.
  • the UE1 may restore DCI_b to DCI_a according to the Lacy rule, for example, truncating the p-bit zero padding bits at the end of the payload of DCI_b to obtain the truncated DCI, namely DCI_a.
  • the format and scrambling method corresponding to the DCI sent by the gNB to the UE1 are as shown in FIG. It can be seen that the communication method corresponding to Fig. 5a is beneficial to limit the size and type of DCI sent by the gNB (detected by the UE1) and scrambled by the characteristic RNTI of the UE to no more than two.
  • the DCI in the unconnected state represents the DCI sent by the gNB to the UE when the RRC state of the UE is in the unconnected state.
  • the DCI in the connected state indicates the DCI sent by the gNB to the UE when the RRC state of the UE is in the connected state.
  • step 402 includes the following refinement steps 4021b to 4026b.
  • the gNB aligns the DCI size corresponding to the DCI format 0_0 sent in the CSS to the DCI size corresponding to the DCI format 1_0.
  • the gNB aligns the DCI size corresponding to the DCI format 0_0 sent in the USS to the DCI size corresponding to the DCI format 1_0.
  • the gNB determines whether the DCI size type 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 4024b is executed, and if so, the end is ended.
  • Steps 4021b to 4023b can be understood with reference to the related descriptions of steps 4021a to 4023a in the embodiment corresponding to FIG. 5a, and details are not described herein again.
  • the gNB aligns the DCI size corresponding to the DCI format 0_3 sent in the USS to the DCI size corresponding to the DCI format 1_3.
  • Step 4024b can be understood with reference to the related description of step 4026a, which will not be repeated here.
  • the gNB determines whether the DCI size type 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, and if so, the end is ended.
  • step 4024b if the size and type of DCI that UE1 needs to detect is less than or equal to 3, and the size and type of DCI scrambled by C-RNTI that UE1 needs to detect is less than or equal to 2, it is considered that step 402 is completed, that is End the flow of step 402. If the size category of the DCI that UE1 needs to detect is greater than 3, or the size category of the DCI scrambled by the C-RNTI that UE1 needs to detect is greater than or equal to 2, step 4026b is executed.
  • the gNB aligns the DCI format 0_0 and DCI format 1_0 sent in the USS to the DCI format 1_3 sent in the USS.
  • step 4026b can also be understood as the DCI format 0_0 and DCI sent by the gNB in the USS The format 1_0 is aligned with the DCI format 0_3 sent in the CSS.
  • the gNB can determine the alignment rule corresponding to each DCI format that UE1 needs to detect, that is, the DCI size corresponding to DCI format 0_0 sent in the CSS is aligned to the DCI size corresponding to DCI format 1_0;
  • the DCI size corresponding to the DCI format 0_3 sent in the USS is aligned with the DCI size corresponding to the DCI format 1_3;
  • the DCI format 0_0 and the DCI format 1_0 sent in the USS are aligned with the DCI format 1_3 sent in the USS.
  • the format and scrambling method corresponding to the DCI sent by the gNB to the UE1 are shown in FIG. It can be seen that the communication method corresponding to FIG. 6a is beneficial to limit the size and type of DCI sent by the gNB (detected by the UE1) and scrambled by the characteristic RNTI of the terminal to no more than two.
  • Each DCI format that UE1 needs to detect includes DCI format 0_0 and DCI format 1_0 sent in CSS, and DCI format 0_3 and DCI format 1_3 sent in USS.
  • step 402 includes the following refinement steps 4021c to 4025c.
  • the gNB aligns the DCI size corresponding to the DCI format 0_0 sent in the CSS to the DCI size corresponding to the DCI format 1_0.
  • the gNB aligns the DCI size corresponding to the DCI format 0_0 sent in the USS to the DCI size corresponding to the DCI format 1_0.
  • gNB judges whether the size and type of DCI that UE1 needs to detect is less than or equal to 3, and whether the size and type of DCI scrambled by C-RNTI that UE1 needs to detect is less than or equal to 2, if not, step 4024c is performed , If yes, end.
  • Steps 4021c to 4023c can be understood with reference to the related descriptions of steps 4021a to 4023a in the embodiment corresponding to FIG. 5a, and details are not described herein again.
  • the gNB aligns the DCI size corresponding to DCI format 0_3 sent in the USS to the DCI size corresponding to DCI format 1_3.
  • Step 4024c can be understood with reference to the related description of step 4026a, which will not be repeated here.
  • the format and scrambling method corresponding to the DCI sent by the gNB to the UE1 are as shown in FIG. It can be seen that the communication method corresponding to FIG. 7a is beneficial to limit the size and type of DCI sent by the gNB (detected by the UE1) and scrambled by the characteristic RNTI of the terminal to no more than two.
  • the size and type of DCI that the UE1 needs to detect can be reduced to two, and/or the size and type of the DCI scrambled by a specific RNTI of the UE1 that the UE needs to be detected can be reduced to one.
  • Each DCI format that UE1 needs to detect includes DCI format 0_0 and DCI format 1_0 sent in CSS, and DCI format 0_0, DCI format 0_3, DCI format 1_0 and DCI format 1_3 sent in USS.
  • step 402 includes the following refinement steps 4021d to 4028d.
  • the gNB aligns the DCI size corresponding to the DCI format 0_0 sent in the CSS to the DCI size corresponding to the DCI format 1_0.
  • the gNB aligns the DCI size corresponding to the DCI format 0_0 sent in the USS to the DCI size corresponding to the DCI format 1_0.
  • the gNB judges whether the DCI size type is less than or equal to 2, and the size type of the DCI scrambled by the C-RNTI is less than or equal to 1, if not, step 4024b is executed, and if yes, the end is ended.
  • the gNB aligns the DCI format 0_0 and DCI format 1_0 sent in the USS to the DCI format 1_0 sent in the CSS.
  • the gNB judges whether the DCI size type is less than or equal to 2, and the size type of the DCI scrambled by the C-RNTI is less than or equal to 1, if not, step 4026d is executed, and if yes, the end is ended.
  • Steps 4021d to 4025d can be understood with reference to related descriptions of steps 4021a to 4025a in the embodiment corresponding to FIG. 5a, and details are not described herein again.
  • the gNB aligns the DCI size corresponding to DCI format 0_3 sent in the USS to the DCI size corresponding to DCI format 1_3.
  • the gNB judges whether the DCI size type is less than or equal to 2, and whether the size type of the DCI scrambled by the C-RNTI is less than or equal to 1, if not, step 4028d is executed, and if yes, the end is ended.
  • step 4027d is executed.
  • the gNB aligns the DCI size corresponding to the DCI format 0_3 and DCI format 1_3 sent in the USS to the DCI format 0_0 sent in the USS.
  • step 4028d can also be understood as that the gNB will align the DCI format 0_3 and DCI format 1_3 sent in the USS to the DCI format 1_0 sent in the USS, or to the DCI format 1_0 sent in the USS.
  • the DCI format 0_0 sent in the CSS is aligned, or the DCI format 1_0 sent in the CSS is aligned.
  • the format and scrambling method corresponding to the DCI sent by the gNB to the UE1 are as shown in FIG. It can be seen that the communication method corresponding to FIG. 8a is beneficial to limit the size and type of DCI sent by the gNB (detected by the UE1) and scrambled by the characteristic RNTI of the UE to no more than one.
  • Each DCI format that UE1 needs to detect includes DCI format 0_0 and DCI format 1_0 sent in CSS, and DCI format 0_3 and DCI format 1_3 sent in USS.
  • step 402 includes the following refinement steps 4021e to 4026e.
  • the gNB aligns the DCI size corresponding to the DCI format 0_0 sent in the CSS to the DCI size corresponding to the DCI format 1_0.
  • the gNB aligns the DCI size corresponding to the DCI format 0_0 sent in the USS to the DCI size corresponding to the DCI format 1_0.
  • the gNB judges whether the DCI size type is less than or equal to 2, and the size type of the DCI scrambled by the C-RNTI is less than or equal to 1, if not, step 4024b is executed, and if so, the end is ended.
  • Steps 4021e to 4023e can be understood with reference to the related descriptions of steps 4021a to 4023a in the embodiment corresponding to FIG. 5a, and will not be repeated here.
  • the gNB aligns the DCI size corresponding to the DCI format 0_3 sent in the USS to the DCI size corresponding to the DCI format 1_3.
  • Step 4024e can be understood with reference to the related description of step 4026a, which will not be repeated here.
  • the gNB determines whether the DCI size type is less than or equal to 2, and the size type of the DCI scrambled by the C-RNTI is less than or equal to 1, if not, step 4026d is executed, and if yes, the end is ended.
  • Step 4025e is performed after step 4024e.
  • the gNB aligns the DCI size corresponding to the DCI format 0_3 and DCI format 1_3 sent in the USS to the DCI format 0_0 sent in the CSS.
  • step 4026e can also be understood as the DCI format 0_3 and DCI sent in USS by gNB The DCI size corresponding to the format 1_3 is aligned with the DCI format 1_0 sent in the CSS.
  • the format and scrambling method corresponding to the DCI sent by the gNB to the UE1 are as shown in FIG. It can be seen that the communication method corresponding to FIG. 9a is beneficial to limit the size and type of DCI sent by the gNB (detected by the UE1) and scrambled by the characteristic RNTI of the UE to no more than one.
  • the size of the sequence number of the above-mentioned processes does not mean the order of execution.
  • the execution order of each process should be determined by its function and internal logic, and should not correspond to the embodiments of the present application.
  • the implementation process constitutes any limitation.
  • the methods provided in the embodiments of the present application are introduced from the perspective of network equipment, terminal, and interaction between the network equipment and the terminal.
  • the network device and the terminal may include a hardware structure and/or software module, and the above functions are implemented in the form of a hardware structure, a software module, or a hardware structure plus a software module. Whether a certain function among the above-mentioned functions is executed by a hardware structure, a software module, or a hardware structure plus a software module depends on the specific application and design constraint conditions of the technical solution.
  • Fig. 10 shows a schematic structural diagram of a communication device.
  • the communication device is used to implement the functions of the UE described in the embodiments of the present application.
  • the communication device 10 may include: a detection module 1001.
  • the detection module 1001 is used to perform step 302 in FIG. 3, step 405 in FIG. 4, steps performed by UE1 in step 407, and so on.
  • the detection module may also be referred to as a receiving module.
  • the communication device 10 may further include a processing module 1002, which is coupled with the detection module 1001 and configured to perform step 403 and step in FIG. 4 404 and step 408.
  • a processing module 1002 which is coupled with the detection module 1001 and configured to perform step 403 and step in FIG. 4 404 and step 408.
  • the specific execution process please refer to the detailed description of the corresponding steps in the foregoing method embodiments, and details are not repeated here.
  • the coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units or modules, and may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules.
  • the communication device 10 may further include a sending module (not shown in FIG. 10), for example, for sending a PUSCH to a network device.
  • the detection module and the sending module of the communication device 10 may be integrated into a transceiver module or a communication module.
  • FIG. 11 is a schematic structural diagram of a communication device according to an embodiment of the application.
  • the communication device is used to implement the functions of the network equipment described in the embodiments of the present application.
  • the communication device 11 includes a sending module 1101.
  • the sending module 1101 is used to execute step 301 in FIG. 3, step 401 and step 407 in FIG.
  • the communication device 11 further includes a processing module 1102.
  • the processing module 1102 is used to execute steps 402 and 406 in FIG. 4 and so on.
  • the specific execution process please refer to the detailed description of the corresponding steps in the foregoing method embodiments, and details are not repeated here.
  • the communication device 11 may further include a receiving module (not shown in FIG. 11), for example, for receiving the PUSCH sent by the terminal.
  • the receiving module and the sending module of the communication device 11 may be integrated into a transceiver module or a communication module.
  • the division of modules in the embodiments of this application is illustrative, and it is only a logical function division. In actual implementation, there may be other division methods.
  • the functional modules in the various embodiments of this application can be integrated into one process. In the device, it can also exist alone physically, or two or more modules can be integrated into one module.
  • the above-mentioned integrated modules can be implemented in the form of hardware or software functional modules.
  • an apparatus 1200 provided in an embodiment of this application is used to implement the function of the terminal in the foregoing method.
  • the device can be a terminal or a device that can be used in conjunction with the terminal.
  • the device can be installed in the terminal.
  • the device may be a chip system.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the apparatus 1200 includes at least one processor 1220, which is configured to implement the function of the terminal in the method provided in the embodiment of the present application.
  • the apparatus 1200 may further include at least one memory 1230 for storing program instructions and/or data.
  • the memory 1230 and the processor 1220 are coupled.
  • the processor 1220 may cooperate with the memory 1230 to operate.
  • the processor 1220 may execute program instructions stored in the memory 1230.
  • One or more of the at least one memory may be included in the processor.
  • the apparatus 1200 may further include a communication interface 1210 for communicating with other devices through a transmission medium, so that the apparatus used in the apparatus 1200 can communicate with other devices.
  • the communication interface 1210 may be a transceiver, circuit, bus, module, pin, or other type of communication interface, and the other device may be a network device.
  • the processor 1220 uses a communication interface to send and receive data, for example, to use the communication interface to detect DCI from a network device to implement the function of the terminal in the method provided in the embodiment of the present application. For details, please refer to the detailed description in the method example, which will not be repeated here.
  • the specific connection medium between the aforementioned communication interface 1210, the processor 1220, and the memory 1230 is not limited in the embodiment of the present application.
  • the memory 1230, the processor 1220, and the communication interface 1210 are connected by a bus 1240.
  • the bus is represented by a thick line in FIG. , Is not limited.
  • the bus can be divided into an address bus, a data bus, a control bus, and so on. For ease of presentation, only one thick line is used in FIG. 12 to represent it, but it does not mean that there is only one bus or one type of bus.
  • an apparatus 1300 provided in an embodiment of this application is used to implement the function of the network device in the foregoing method.
  • the device can be a network device, or a device that can be matched and used with a network device.
  • the device can be installed in network equipment.
  • the device may be a chip system.
  • the apparatus 1300 includes at least one processor 1320, which is configured to implement the function of the network device in the method provided in the embodiment of the present application.
  • the device 1300 may further include at least one memory 1330 for storing program instructions and/or data.
  • the memory 1330 and the processor 1320 are coupled.
  • the processor 1320 may operate in cooperation with the memory 1330.
  • the processor 1320 may execute program instructions stored in the memory 1330.
  • One or more of the at least one memory may be included in the processor.
  • the apparatus 1300 may further include a communication interface 1310 for communicating with other devices through a transmission medium, so that the apparatus used in the apparatus 1300 can communicate with other devices.
  • 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 uses the communication interface to send and receive data, for example, uses the communication interface to send DCI to the terminal to realize the function of the network device in the method provided in the embodiment of the present application. For details, please refer to the detailed description in the method example, which will not be repeated here.
  • the embodiment of the present application does not limit the specific connection medium between the communication interface 1310, the processor 1320, and the memory 1330.
  • the memory 1330, the processor 1320, and the communication interface 1310 are connected by a bus 1340.
  • the bus is represented by a thick line in FIG. , Is not limited.
  • the bus can be divided into an address bus, a data bus, a control bus, and so on. For ease of presentation, only one thick line is used in FIG. 13, but it does not mean that there is only one bus or one type of bus.
  • 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, which may implement or Perform the methods, steps, and logic block diagrams disclosed in the embodiments of the present application.
  • the general-purpose processor may be a microprocessor or any conventional processor or the like.
  • the steps of the method disclosed in combination with the embodiments of the present application may be directly embodied as being executed and completed by a hardware processor, or executed and completed by a combination of hardware and software modules in the processor.
  • the memory may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), etc., or a volatile memory (volatile memory), for example Random-access memory (random-access memory, RAM).
  • the memory is any other medium that can be used to carry or store desired program codes in the form of instructions or data structures and that can be accessed by a computer, but is not limited to this.
  • the memory in the embodiments of the present application may also be a circuit or any other device capable of realizing a storage function for storing program instructions and/or data.
  • the technical solutions provided in the embodiments of the present application may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it can be implemented in the form of a computer program product in whole or in part.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a terminal device, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer instructions may be transmitted from a website, computer, server, or data center. Transmission to another website, computer, server, or data center via wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or a data center integrated with one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a digital video disc (DVD)), or a semiconductor medium.
  • the embodiments can be mutually cited.
  • the methods and/or terms between the method embodiments can be mutually cited, such as the functions and/or functions between the device embodiments.
  • Or terms may refer to each other, for example, functions and/or terms between the device embodiment and the method embodiment may refer to each other.
  • At least one can also be described as one or more, and the multiple can be two, three, four or more, which is not limited in the present application.
  • “/" can indicate that the associated objects are in an "or” relationship.
  • A/B can indicate A or B; and "and/or” can be used to describe that there are three types of associated objects.
  • the relationship, for example, A and/or B can mean that: A alone exists, A and B exist at the same time, and B exists alone, where A and B can be singular or plural.
  • words such as “first” and “second” may be used to distinguish technical features with the same or similar functions. The words “first” and “second” do not limit the quantity and order of execution, and the words “first” and “second” do not limit the difference.
  • words such as “exemplary” or “for example” are used to indicate examples, illustrations or illustrations, and any embodiment or design solution described as “exemplary” or “for example” shall not be interpreted It is more preferable or more advantageous than other embodiments or design solutions.
  • the use of words such as “exemplary” or “for example” is intended to present related concepts in a specific manner to facilitate understanding.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne un procédé et un appareil de communication, qui sont utilisés pour réduire le nombre d'instances de détection de DCI par un terminal et réduire ainsi la complexité du terminal. Le procédé comprend les étapes suivantes : un terminal détecte des informations de commande de liaison descendante (DCI) à partir d'un dispositif réseau, les DCI étant utilisées pour planifier un canal de données physique, et les formats des DCI pour planifier le canal de données physique comprenant une pluralité de formats de DCI ; et le nombre de types de tailles de DCI correspondant à la pluralité de formats de DCI est inférieur ou égal à N, N étant un nombre entier positif inférieur ou égal à 3, et/ou lorsque les DCI correspondant à la pluralité de formats DCI sont brouillées en utilisant un identifiant temporaire de réseau radio (RNTI) spécifique à un terminal, le nombre de types des tailles de DCI correspondant à la pluralité de formats de DCI est inférieur ou égal à M, M étant un nombre entier positif inférieur ou égal à 2.
PCT/CN2021/085608 2020-04-10 2021-04-06 Procédé et appareil de communication WO2021204107A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010278718.2A CN113517946A (zh) 2020-04-10 2020-04-10 一种通信方法及装置
CN202010278718.2 2020-04-10

Publications (1)

Publication Number Publication Date
WO2021204107A1 true WO2021204107A1 (fr) 2021-10-14

Family

ID=78023719

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/085608 WO2021204107A1 (fr) 2020-04-10 2021-04-06 Procédé et appareil de communication

Country Status (2)

Country Link
CN (1) CN113517946A (fr)
WO (1) WO2021204107A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024159549A1 (fr) * 2023-02-03 2024-08-08 北京小米移动软件有限公司 Procédé et appareil d'alignement et de détermination de taille d'informations de commande de liaison descendante

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114285521B (zh) * 2021-12-22 2024-05-28 中国信息通信研究院 一种信息格式类型确定方法和设备
WO2023123315A1 (fr) * 2021-12-31 2023-07-06 Oppo广东移动通信有限公司 Procédé de communication sans fil, équipement terminal et dispositif de réseau
CN115136522B (zh) * 2022-05-25 2024-01-02 北京小米移动软件有限公司 下行控制信息尺寸对齐方法和装置、通信装置及存储介质
CN117997468A (zh) * 2022-11-04 2024-05-07 华为技术有限公司 一种下行控制信息的传输方法及通信装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140307696A1 (en) * 2011-11-11 2014-10-16 Lg Electronics Inc. Method and device for obtaining and receiving control information in wireless communication system
CN104349473A (zh) * 2013-08-09 2015-02-11 电信科学技术研究院 一种时分双工上下行配置信息传输方法及装置
CN110536448A (zh) * 2019-08-15 2019-12-03 中兴通讯股份有限公司 一种信息确定方法、装置和存储介质
CN110972319A (zh) * 2018-09-30 2020-04-07 北京三星通信技术研究有限公司 物理下行控制信道的检测方法、发送方法及相应设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140307696A1 (en) * 2011-11-11 2014-10-16 Lg Electronics Inc. Method and device for obtaining and receiving control information in wireless communication system
CN104349473A (zh) * 2013-08-09 2015-02-11 电信科学技术研究院 一种时分双工上下行配置信息传输方法及装置
CN110972319A (zh) * 2018-09-30 2020-04-07 北京三星通信技术研究有限公司 物理下行控制信道的检测方法、发送方法及相应设备
CN110536448A (zh) * 2019-08-15 2019-12-03 中兴通讯股份有限公司 一种信息确定方法、装置和存储介质

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024159549A1 (fr) * 2023-02-03 2024-08-08 北京小米移动软件有限公司 Procédé et appareil d'alignement et de détermination de taille d'informations de commande de liaison descendante

Also Published As

Publication number Publication date
CN113517946A (zh) 2021-10-19

Similar Documents

Publication Publication Date Title
JP7449974B2 (ja) ダウンリンク制御情報伝送方法
WO2021204107A1 (fr) Procédé et appareil de communication
US20180199334A1 (en) Signaling, procedures, user equipment and base stations for uplink ultra reliable low latency communications
US11444737B2 (en) Communication method and device
WO2017045496A1 (fr) Procédé et appareil de commande de liaison descendante
WO2019029727A1 (fr) Procédé, appareil terminal et appareil de réseau permettant de déterminer des informations de rétroaction
US11778619B2 (en) Communication method and apparatus, and computer storage medium
US20230038936A1 (en) Control information transmission method
EP3897005A1 (fr) Procédé et appareil de communication
WO2018171474A1 (fr) Procédé, dispositif, et système de transmission de données
WO2020143802A1 (fr) Procédé et appareil de communication
WO2011157188A1 (fr) Procédé et dispositif de transmission de liaison montante fondée sur la contention
WO2020143558A1 (fr) Procédé et dispositif de mesure de canal
WO2020221174A1 (fr) Procédé et appareil de communication
WO2020169063A1 (fr) Procédé de transmission de données, et appareil de communication
WO2020088423A1 (fr) Procédé et appareil de communication
WO2019029463A1 (fr) Procédé et dispositif de réception d'informations de commande et d'envoi d'informations de commande
WO2021062687A1 (fr) Procédé et dispositif de communication
TWI759507B (zh) 回饋應答訊息的傳輸方法、裝置及系統
WO2020228542A1 (fr) Procédé et appareil d'émission et de réception de message d'accusé de réception de demande de répétition automatique hybride (harq-ack)
WO2021031948A1 (fr) Procédé de traitement de données et appareil de communication
WO2022199607A1 (fr) Procédé et appareil de transmission de données
WO2021072610A1 (fr) Procédé et appareil pour activer et libérer une transmission de planification non dynamique
WO2023207919A1 (fr) Procédé de planification de ressource et appareil de communication
WO2023185433A1 (fr) Procédé de communication et appareil de communication

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21785067

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21785067

Country of ref document: EP

Kind code of ref document: A1