Disclosure of Invention
The embodiment of the application provides a communication method and a communication device, which are used for reducing the size variety of DCI (downlink control information) for scheduling a physical data channel so as to reduce the number and complexity of blind detection of a terminal.
In order to solve the technical problems, the embodiment of the application provides the following technical scheme:
In a first aspect, 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 for scheduling a physical data channel, and a format of the DCI for scheduling the physical data channel includes multiple DCI formats, where a type of DCI size corresponding to the multiple DCI formats is less than or equal to N, where N is a positive integer less than or equal to 3, and/or when DCI corresponding to the multiple DCI formats is scrambled by using a terminal-specific radio network temporary identifier RNTI, a type of DCI size corresponding to the multiple DCI formats is less than or equal to M, where M is a positive integer less than or equal to 2.
Wherein, the RNTI is the identification of the terminal. The terminal-specific RNTI may be a cell RNTI (cell RNTI, C-RNTI), a configuration scheduling RNTI (configured scheduling RNTI, CS-RNTI), or a modulation and coding policy cell RNTI (modulation and coding scheme C-RNTI, MCS-C-RNTI) of the terminal, or the like.
The physical data channel is used for transmitting uplink data, such as a Physical Uplink SHARED CHANNEL (PUSCH), or downlink data, such as a physical downlink shared channel (physical downlink SHARED CHANNEL, PDSCH), or a physical channel (e.g., PUSCH) for transmitting uplink data and a physical channel (e.g., PDSCH) for transmitting downlink data.
Since the size of the DCI for scheduling the physical data channel is not more than M, where M is a positive integer less than or equal to 3, and/or the size of the DCI scrambled by the terminal-specific radio network temporary identifier RNTI is not more than N, where N is a positive integer less than or equal to 2, compared with the prior art, the number of times of DCI detection of the terminal can be reduced, thereby reducing complexity of the terminal and power consumption of the terminal.
In one possible implementation, the types of DCI sizes corresponding to the multiple DCI formats are less than or equal to N, including when DCI corresponding to the multiple DCI formats is scrambled using a common RNTI or terminal-specific RNTI, the types of DCI sizes corresponding to the multiple DCI formats are less than or equal to N.
The common RNTI may be a system message RNTI (system information RNTI, SI-RNTI), a paging RNTI (PAGING RNTI, P-RNTI), or a random access RNTI (random ACCESS RNTI, RA-RNTI), or the like.
In this implementation manner, by limiting the scrambling manner of the DCI, the type of the size of the DCI may be limited, so that the number of times of DCI detection of the terminal may be reduced, and thus the complexity of the terminal may be reduced, and the power consumption of the terminal may be reduced.
In one possible implementation, the multiple DCI formats include a first format and a second format detected in a terminal-specific search space USS, where DCI corresponding to the first format is used to schedule uplink transmission, and DCI corresponding to the second format is used to schedule downlink transmission, where DCI transmitted in USS is scrambled using the terminal-specific RNTI. In the implementation manner, the types of the DCI sizes of the first format and the second format are limited, so that the detection times of the terminal on the DCI of the first format and the DCI of the second format can be reduced, the complexity of the terminal is further reduced, and the power consumption of the terminal is reduced.
In one possible implementation, the DCI size corresponding to the first format and the DCI size corresponding to the second format are aligned.
In one possible implementation, the DCI size corresponding to the first format is aligned to the DCI size corresponding to the second format. The method can avoid information loss of the DCI in the second format.
Or the DCI size corresponding to the second format is aligned to the DCI size corresponding to the first format. The method can avoid information loss of the DCI of the first format.
Or if the DCI size corresponding to the first format is smaller than the DCI size corresponding to the second format, the DCI size corresponding to the first format is aligned to the DCI size corresponding to the second format, and if the DCI size corresponding to the second format is smaller than the DCI size corresponding to the first format, the DCI size corresponding to the second format is aligned to the DCI size corresponding to the first format. The implementation method does not lose information bits (payload) in DCI corresponding to the first format and the second format, and ensures the accuracy of transmission parameters.
In one possible implementation, the aligning the DCI size corresponding to the second format to the DCI size corresponding to the first format includes puncturing K fields of the DCI corresponding to the second format if the DCI size corresponding to the first format is smaller than the DCI size corresponding to the second format, where K is a positive integer, and filling at least one padding bit in the DCI corresponding to the second format if the DCI size corresponding to the first format is larger than the DCI size corresponding to the second format, and the DCI size corresponding to the second format after being padded is the same as the DCI size corresponding to the first format.
In this implementation manner, the transmission performance and scheduling performance of DCI corresponding to the first format may be guaranteed, and thus the uplink transmission performance of the terminal may be guaranteed.
In one possible implementation, the aligning the DCI size corresponding to the first format to the DCI size corresponding to the second format includes puncturing K fields of the DCI corresponding to the first format if the DCI size corresponding to the second format is smaller than the DCI size corresponding to the first format, where K is a positive integer, and puncturing K fields of the DCI corresponding to the first format and the DCI corresponding to the second format, or filling at least one padding bit in the DCI corresponding to the first format if the DCI size corresponding to the second format is greater than the DCI size corresponding to the first format, and puncturing the DCI corresponding to the first format and the DCI corresponding to the second format.
In this implementation manner, the transmission performance and scheduling performance of the DCI in the second format may be guaranteed, and further, the downlink transmission performance of the terminal device may be guaranteed.
In one possible implementation, the K domains include at least one of a frequency domain resource allocation domain, a time domain resource allocation domain, a physical uplink control channel resource indication domain, a physical downlink shared channel to hybrid automatic repeat request feedback time indication domain, and a demodulation reference signal sequence initialization domain.
In one possible implementation, the multiple DCI formats further include a third format and a fourth format detected in USS, where DCI corresponding to the third format is used to schedule uplink transmission, DCI corresponding to the fourth format 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, where a DCI size corresponding to the third format is aligned to a DCI size corresponding to the first format or to a DCI size corresponding to the second format, and a DCI size corresponding to the fourth format is aligned to a DCI size corresponding to the first format or to a DCI size corresponding to the second format, where a DCI size corresponding to the first format is equal to a DCI size corresponding to the second format. In this implementation manner, by aligning the DCI sizes of the third format and the fourth format to the DCI sizes corresponding to the first format and the second format, the number of DCI sizes that need to be detected by the terminal may be reduced, and the blind detection times of the terminal on the DCI may be reduced, so that implementation complexity, power consumption and cost of the terminal may be reduced.
In one possible implementation, the plurality of DCI formats includes a third format and a fourth format detected in a terminal-specific search space USS, and the third format and the fourth format detected in a common search space CSS, the DCI corresponding to the third format being used for scheduling uplink transmissions and the DCI corresponding to the fourth format being used for scheduling downlink transmissions, wherein the DCI transmitted in USS is scrambled with the terminal-specific RNTI and the DCI transmitted in CSS is scrambled with the terminal-specific RNTI or with a common RNTI, wherein the DCI size corresponding to the third format detected in USS is aligned to the DCI size corresponding to the third format detected in CSS or to the DCI size corresponding to the fourth format detected in CSS, and the DCI size corresponding to the fourth format detected in USS is aligned to the DCI size corresponding to the third format detected in CSS or to the DCI size corresponding to the fourth format detected in CSS. In the implementation manner, by aligning the sizes of DCIs corresponding to the third format and the fourth format in the USS and the CSS, the blind detection times of the DCIs when the time-frequency resources of the USS and the CSS are overlapped by the terminal can be reduced, and the implementation complexity, the power consumption and the cost of the terminal can be reduced.
In one possible implementation, the third format is 0_0 and the fourth format is 1_0.
In one possible implementation, the types of DCI sizes corresponding to multiple DCI formats are smaller than or equal to 2, which is beneficial to reducing the types of sizes of DCIs required to be detected by a terminal to 2, or the types of DCI sizes corresponding to multiple DCI formats are smaller than or equal to 1, which is beneficial to reducing the types of sizes of DCIs required to be detected by a terminal to 1 when the DCIs are scrambled by using a terminal-specific RNTI, or the types of DCI sizes corresponding to multiple DCI formats are smaller than or equal to 2, and the types of DCI sizes corresponding to multiple DCI formats are smaller than or equal to 1, which is beneficial to reducing the types of sizes of DCIs required to be detected by a terminal to 2 when the DCIs required to be scrambled by using a terminal-specific RNTI, and reducing the types of sizes of DCIs required to be used by using a terminal-specific scrambling to 1.
In one possible implementation, the plurality of DCI formats includes a first format, a second format, a third format, and a fourth format detected in a USS, and third and fourth formats detected in a common search space CSS, the DCI corresponding to the first format and the third format being used for scheduling uplink transmissions, the DCI corresponding to the second format being used for scheduling downlink transmissions, the first format being different from the third format, the second format being different from the fourth format, wherein a DCI size detected in a USS is aligned to a DCI size detected in a CSS corresponding to the third format or to a DCI size detected in a CSS corresponding to the fourth format, and the DCI corresponding to the second format detected in a USS is aligned to a size detected in a CSS corresponding to the third format or to a DCI corresponding to the fourth format detected in a CSS corresponding to the size detected in a CSS corresponding to the third format or to the fourth format corresponding to the size detected in a DCS corresponding to the fourth format. In this implementation manner, by aligning the sizes of the first format, the second format, the third format, the fourth format in the USS and the third format and the fourth format in the CSS, the number of times of DCI blind detection when the time-frequency resources of the USS and the CSS overlap can be reduced, so that implementation complexity, power consumption and cost of the terminal can be reduced.
In a second aspect, an embodiment of the present application provides a communication method, including detecting downlink control information DCI from a network device, where the DCI is used for scheduling a physical data channel, and a format of the DCI used for scheduling the physical data channel includes multiple DCI formats, where a DCI size corresponding to a sixth format in the multiple DCI formats is aligned to a DCI size corresponding to a fifth format in the multiple DCI formats, where 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.
In this implementation manner, the DCI size corresponding to the DCI format for scheduling downlink transmission is aligned to the DCI size corresponding to the DCI format for scheduling uplink transmission, so that the information loss of the DCI of the fifth format can be avoided, and the uplink transmission performance of the terminal can be ensured.
In one possible implementation, 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, where K is the same as the DCI size corresponding to the fifth format if the DCI size corresponding to the fifth format is smaller than the DCI size corresponding to the sixth format, or K is a positive integer if the DCI size corresponding to the fifth format is greater than the DCI size corresponding to the sixth format, and at least one padding bit is padded in the DCI corresponding to the sixth format if the DCI size corresponding to the fifth format is smaller than the DCI size corresponding to the sixth format, and the DCI size corresponding to the sixth format after padding is the same as the DCI size corresponding to the fifth format.
In this implementation manner, the transmission performance and scheduling performance of DCI corresponding to the fifth format may be guaranteed, and thus the uplink transmission performance of the terminal may be guaranteed.
In one possible implementation, the K domains include at least one of a frequency domain resource allocation domain, a time domain resource allocation domain, a physical uplink control channel resource indication domain, a physical downlink shared channel to hybrid automatic repeat request feedback time indication domain, and a demodulation reference signal sequence initialization domain.
In one possible implementation, the DCI in the fifth format may be DCI in the first format detected in the terminal-specific search space USS, the DCI in the sixth format may be DCI in the second format detected in the USS, or the DCI in the fifth format may be DCI in the third format detected in the USS, the DCI in the sixth format may be DCI in the fourth format detected in the USS, or the DCI in the fifth format may be DCI in the third format detected in the CSS, and the DCI in the sixth format may be DCI in the fourth format detected in the CSS.
In a third aspect, an embodiment of the present application provides a communication device, where the communication device may be a terminal device, a device in a terminal, or a device that can be used in a matching manner with a terminal. In one design, the apparatus may include modules corresponding to each other for performing the methods/operations/steps/actions described in the first aspect or the second aspect, where the modules may be hardware circuits, software, or a combination of hardware circuits and software.
In one possible design, the communication device may include a detection module, where the detection module is configured to detect downlink control information DCI from a network device, where the DCI is configured to schedule a physical data channel, and a format of the DCI configured to schedule the physical data channel includes multiple DCI formats, where a type of DCI size corresponding to the multiple DCI formats is less than or equal to N, where N is a positive integer less than or equal to 3, and/or where a type of DCI size corresponding to the multiple DCI formats is less than or equal to M, where M is a positive integer less than or equal to 2 when the DCI corresponding to the multiple DCI formats is scrambled by using a terminal-specific radio network temporary identifier RNTI.
In one possible design, the specific format included in the plurality of DCI formats and the pulling manner of the plurality of DCI formats may be referred to a specific description of the DCI formats in the first aspect, which is not repeated herein.
In one possible design, the communication device may include a detection module configured to detect downlink control information DCI from a network device, where the DCI is configured to schedule a physical data channel, and the format of the DCI configured to schedule the physical data channel includes multiple DCI formats, where a DCI size corresponding to a sixth format in the multiple DCI formats is aligned to a DCI size corresponding to a fifth format in the multiple DCI formats, where the DCI corresponding to the fifth format is configured to schedule uplink transmission, and the DCI corresponding to the sixth format is configured to schedule downlink transmission.
In one possible implementation, the DCI in the fifth format may be DCI in the first format detected in the terminal-specific search space USS, the DCI in the sixth format may be DCI in the second format detected in the USS, or the DCI in the fifth format may be DCI in the third format detected in the USS, the DCI in the sixth format may be DCI in the fourth format detected in the USS, or the DCI in the fifth format may be DCI in the third format detected in the CSS, and the DCI in the sixth format may be DCI in the fourth format detected in the CSS.
In one possible design, the fifth format and the sixth format, and other limitations on the manner of pulling the fifth format and the sixth format may be referred to in the second aspect, which is not described herein.
A fourth aspect of the present application provides a communication device, which may be a terminal device, a device in a terminal, or a device that can be used in a matching manner with a terminal. The apparatus comprises a processor for implementing the method described in the first or second aspect above. The apparatus may also include a memory to store instructions and data. The memory is coupled to the processor, and the processor, when executing instructions stored in the memory, may implement the method described in the first aspect or the second aspect. The apparatus may also include a communication interface for the apparatus to communicate with other devices, which may be transceivers, circuits, buses, modules, pins, or other types of communication interfaces, as examples, and other devices may be network devices.
In one possible design, the device comprises a memory for storing program instructions, and a processor for detecting Downlink Control Information (DCI) from a network device by utilizing a communication interface, wherein the DCI is used for scheduling a physical data channel, the format of the DCI for scheduling the physical data channel comprises a plurality of DCI formats, wherein the type of the DCI size corresponding to the plurality of DCI formats is less than or equal to N, N is a positive integer less than or equal to 3, and/or when the DCI corresponding to the plurality of DCI formats is scrambled by using a terminal-specific Radio Network Temporary Identifier (RNTI), the type of the DCI size corresponding to the plurality of DCI formats is less than or equal to M, and M is a positive integer less than or equal to 2.
In one possible design, the specific format included in the plurality of DCI formats and the pulling manner of the plurality of DCI formats may be referred to a specific description of the DCI formats in the first aspect, which is not repeated herein.
In one possible design, the apparatus includes a memory configured to store program instructions, and a processor configured to detect downlink control information, DCI, from a network device using a communication interface, where the DCI is configured to schedule a physical data channel, and a format of the DCI configured to schedule the physical data channel includes a plurality of DCI formats, where a DCI size corresponding to a sixth format of the plurality of DCI formats is aligned to a DCI size corresponding to a fifth format of the plurality of DCI formats, where the DCI corresponding to the fifth format is configured to schedule uplink transmissions, and the DCI corresponding to the sixth format is configured to schedule downlink transmissions.
In one possible design, the fifth format and the sixth format, and other limitations on the manner of pulling the fifth format and the sixth format may be referred to in the second aspect, which is not described herein.
In another possible design, the communication device may be implemented in the form of a chip.
A fifth aspect of the application provides a chip system comprising a processor and possibly a memory for implementing the method described in the first or second aspect. The chip system may be formed of a chip or may include a chip and other discrete devices.
A sixth aspect of the application provides a computer readable storage medium comprising instructions which, when run on a computer, cause the computer to perform the method as in the first aspect or any one of the possible implementations of the first aspect or the method as in the second aspect or any one of the possible implementations of the second aspect of the embodiments of the application.
A seventh aspect of the application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method as in the first aspect or any one of the possible implementations of the first aspect or the method as in the second aspect or any one of the possible implementations of the second aspect of the embodiments of the application.
In an eighth 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 for scheduling a physical data channel, and a format of the DCI for scheduling the physical data channel includes multiple DCI formats, where a type of DCI size corresponding to the multiple DCI formats is less than or equal to N, where N is a positive integer less than or equal to 3, and/or when DCI corresponding to the multiple DCI formats is scrambled by using a terminal-specific radio network temporary identifier RNTI, a type of DCI size corresponding to the multiple DCI formats is less than or equal to M, where M is a positive integer less than or equal to 2.
In one possible design, the specific format included in the plurality of DCI formats and the pulling manner of the plurality of DCI formats may be referred to a specific description of the DCI formats in the first aspect, which is not repeated herein.
In a ninth aspect, an embodiment of the present application provides a communication method, where a network device sends downlink control information DCI to a terminal, where the DCI is used for scheduling a physical data channel, and a format of the DCI used for scheduling the physical data channel includes multiple DCI formats, where a DCI size corresponding to a sixth format in the multiple DCI formats is aligned to a DCI size corresponding to a fifth format in the multiple DCI formats, where 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.
In one possible design, the fifth format and the sixth format, and other limitations on the manner of pulling the fifth format and the sixth format may be referred to in the second aspect, which is not described herein.
In a tenth aspect, an embodiment of the present application provides a communication apparatus, where the communication apparatus may be a network device, an apparatus in a network device, or an apparatus that can be used in a matching manner with a network device. In one design, the apparatus may include modules corresponding to the methods/operations/steps/actions described in the eighth or ninth aspect, where the modules may be hardware circuits, software, or a combination of hardware circuits and software.
In one possible design, the communication device may include a sending module, where the sending module is configured to send downlink control information DCI to a terminal, where the DCI is configured to schedule a physical data channel, and a format of the DCI configured to schedule the physical data channel includes multiple DCI formats, where a type of DCI size corresponding to the multiple DCI formats is less than or equal to N, where N is a positive integer less than or equal to 3, and/or where a type of DCI size corresponding to the multiple DCI formats is less than or equal to M, where M is a positive integer less than or equal to 2 when the DCI corresponding to the multiple DCI formats is scrambled with a terminal-specific radio network temporary identifier RNTI.
In one possible design, the specific format included in the plurality of DCI formats and the manner of pulling the plurality of DCI formats may be referred to in the eighth aspect for a specific description of the DCI formats, which is not repeated herein.
In one possible design, the communication device may include a sending module, where the sending module is configured to send downlink control information DCI to a terminal, where the DCI is configured to schedule a physical data channel, and the format of the DCI configured to schedule the physical data channel includes multiple DCI formats, where a DCI size corresponding to a sixth format in the multiple DCI formats is aligned to a DCI size corresponding to a fifth format in the multiple DCI formats, where the DCI corresponding to the fifth format is configured to schedule uplink transmission, and the DCI corresponding to the sixth format is configured to schedule downlink transmission.
In one possible design, the fifth format and the sixth format, and other limitations on the manner in which the fifth format and the sixth format are aligned may be referred to in the detailed description of the ninth aspect, which is not repeated herein.
An eleventh aspect of the present application provides a communication device comprising a processor for implementing the method described in the eighth or ninth aspect above. The communication device may also include a memory for storing instructions and data. The memory is coupled to the processor, and the processor, when executing instructions stored in the memory, may implement the method described in the eighth or ninth aspect. The communication means may also comprise a communication interface for the apparatus to communicate with other devices, which may be, for example, transceivers, circuits, buses, modules, pins or other types of communication interfaces, and the other devices may be terminal devices.
In one possible design, the communication device comprises a memory for storing program instructions, and a processor for sending Downlink Control Information (DCI) to a terminal device by utilizing a communication interface, wherein the DCI is used for scheduling a physical data channel, the format of the DCI for scheduling the physical data channel comprises a plurality of DCI formats, wherein the type of the DCI size corresponding to the plurality of DCI formats is smaller than or equal to N, N is a positive integer smaller than or equal to 3, and/or when the DCI corresponding to the plurality of DCI formats is scrambled by using a terminal-specific Radio Network Temporary Identifier (RNTI), the type of the DCI size corresponding to the plurality of DCI formats is smaller than or equal to M, and M is a positive integer smaller than or equal to 2.
In one possible design, the specific format included in the plurality of DCI formats and the manner of pulling the plurality of DCI formats may be referred to in the eighth aspect for a specific description of the DCI formats, which is not repeated herein.
In one possible design, the communication device comprises a memory for storing program instructions, and a processor for transmitting Downlink Control Information (DCI) to a terminal device by utilizing a communication interface, wherein the DCI is used for scheduling a physical data channel, the format of the DCI for scheduling the physical data channel comprises a plurality of DCI formats, the DCI size corresponding to a sixth format in the plurality of DCI formats is aligned to the DCI size corresponding to a fifth format in the plurality of DCI formats, 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.
In one possible design, the fifth format and the sixth format, and other limitations on the manner in which the fifth format and the sixth format are aligned may be referred to in the detailed description of the ninth aspect, which is not repeated herein.
In another possible design, the communication device may be implemented in the form of a chip.
A twelfth aspect of the application provides a chip system comprising a processor and possibly a memory for implementing the method described in the eighth or ninth aspect. The chip system may be formed of a chip or may include a chip and other discrete devices.
A thirteenth aspect of the present application provides a computer readable storage medium comprising instructions therein, which when run on a computer, cause the computer to perform the method as in any one of the possible implementations of the eighth or eighth aspect or any one of the possible implementations of the ninth or ninth aspect of the embodiments of the present application.
A fourteenth aspect of the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method as in any one of the possible implementations of the eighth or eighth aspect of the embodiments of the present application or any one of the possible implementations of the ninth or ninth aspect.
In a fifteenth aspect, embodiments of the present application provide a communication system, including the apparatus of the third or fourth aspect, and the apparatus of the tenth or eleventh aspect.
Detailed Description
The embodiment of the application provides a communication method and a communication device. Embodiments of the present application are described below with reference to the accompanying drawings.
The technical scheme of the embodiment of the application can be applied to various wireless communication systems or networks, such as a long term evolution (long term evolution, LTE) system, an LTE frequency division duplex (frequency division duplex, FDD) system, an LTE time division duplex (time division duplex, TDD), a fifth generation (5th generation,5G) system, a future introduced communication system, or fusion of various systems, and the like. Among them, 5G may also be referred to as New Radio (NR).
The network device in embodiments of the present application may be, for example, an access node and/or other network entity, e.g., although not shown, the access network may include a central unit (centralized unit, CU) and Distributed Units (DUs). The access node in the embodiment of the application can be an evolved node B or an evolved node B (evolutional NodeB, eNB or eNodeB) in an LTE system, and can also be a wireless controller in a cloud wireless access network (cloud radio access network, CRAN) scene. Or the access node in the embodiment of the application can 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 evolution PLMN network, and the like. The base stations in the 5G network may be referred to as next generation base stations (gcb), which are not limited in the embodiment of the present application. In the embodiment of the application, the device for realizing the function of the network equipment can be the network equipment, or can be a device which can support the network equipment to realize the function, such as a chip system, and can be installed in the network equipment. In the technical solution provided in the embodiment of the present application, the device for implementing the function of the network device is exemplified by the network device, and the technical solution provided in the embodiment of the present application is described.
The terminal equipment in the embodiment of the application can be called a terminal, can be equipment with a wireless receiving and transmitting function, can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted, can be deployed on water surface (such as a ship and the like), and can be deployed in air (such as an airplane, a balloon, a satellite and the like). The terminal device may be a User Equipment (UE), wherein the UE includes a handheld device, an in-vehicle device, a wearable device, or a computing device with wireless communication capabilities. The UE may be a mobile phone (mobile phone), a tablet computer, or a computer with a wireless transceiver function, for example. The terminal device may also be a Virtual Reality (VR) terminal device, an augmented reality (augmented reality, AR) terminal device, a wireless terminal in industrial control, a wireless terminal in unmanned, a wireless terminal in telemedicine, a wireless terminal in smart grid, a wireless terminal in smart city (SMART CITY), a wireless terminal in smart home (smart home), etc. In the embodiment of the application, the device for realizing the function of the terminal can be the terminal, or can be a device capable of supporting the terminal to realize the function, such as a chip system, and the device can be installed in the terminal. In the embodiment of the application, the chip system can be composed of chips, and can also comprise chips and other discrete devices. In the technical solution provided in the embodiment of the present application, the device for implementing the function of the terminal is the terminal, and the terminal is the UE, which is taken as an example, to describe the technical solution provided in the embodiment of the present application.
The technical scheme provided by the embodiment of the application can be applied to wireless communication among communication equipment. The wireless communication between the communication devices may include wireless communication between the network device and the terminal, wireless communication between the network device and the network device, and wireless communication between the terminal and the terminal. In the embodiments of the present application, the term "wireless communication" may also be simply referred to as "communication", and the term "communication" may also be described as "data transmission", "information transmission" or "transmission". The technical solution may be used for performing wireless communication between a scheduling entity (e.g., a network device) and a subordinate entity (e.g., a UE), and those skilled in the art may use the technical solution provided in the embodiments of the present application to perform wireless communication between other scheduling entities and subordinate entities, e.g., wireless communication between a macro base station and a micro base station, e.g., wireless communication between a first terminal and a second terminal. Wherein the scheduling entity may allocate resources for subordinate entities and/or the scheduling entity may control wireless communication between them.
Information interacted between the UE and the network device is carried over a physical channel. The control information (downlink control information, DCI) sent by the network device to the UE may be carried by a physical downlink control channel (physical downlink control channel, PDCCH), the data sent by the network device to the UE, that is, downlink data, may be carried by a physical downlink shared channel (physical downlink SHARED CHANNEL, PDSCH), and the data sent by the UE to the network device, that is, uplink data, may be carried by a Physical Uplink Shared Channel (PUSCH) SHARED CHANNEL. The physical channel used for carrying DCI may be a channel of another name, for example, an enhanced physical downlink control channel (ENHANCED PHYSICAL downlink control channel, EPDCCH), the channel used for carrying downlink data in the physical layer may be a channel of another name than PDSCH, and the channel used for carrying uplink data in the physical layer may be a channel of another name than PUSCH.
In a wireless communication system, such as an NR communication system, a network device may configure a bandwidth part (BWP) for a UE from a system bandwidth or a carrier bandwidth, and the UE and the network device perform information interaction in the BWP. BWP may be understood as a frequency domain operation interval configured by a network device for a UE, including a frequency domain range, a subcarrier spacing, and the like. One BWP may be used for transmitting only uplink data, which may be referred to as an uplink BWP, or one BWP may be used for transmitting only downlink data, which may be referred to as a downlink BWP, and for a time division duplex system, the uplink BWP and the downlink BWP are often arranged in pairs and their center frequency points are the same. The network device may configure one or more BWP for the UE. The UE may receive one or more of PDCCH, PDSCH, and uplink demodulation reference signals from the network device in downlink BWP. In uplink BWP, the UE may transmit one or more of PUSCH, PUCCH, and downlink demodulation reference signals to the network device.
The network device may perform channel configuration on a channel transmitted in the BWP in configuring the BWP for the UE. Taking the downlink BWP configuration as an example, the network device may perform PDSCH configuration and PDCCH configuration. Wherein configuring the PDCCH includes configuring a search space and a control resource set (control resource set, CORESET) of the PDCCH. Optionally, configuring the PDCCH further includes configuring DCI formats in each search space that the UE needs to detect.
The network device may configure and activate one or more BWP for the UE, and the network device may transmit PDSCH, PUSCH, and/or PDCCH on the activated BWP and the UE, and may not transmit PDSCH, PUSCH, and PDCCH on the non-activated BWP and the UE.
In one possible implementation, some or all of the BWP configuration information may also be preset, i.e. this information is known in advance by the network device and the UE.
DCI in a plurality of different formats may be supported in a communication system. A plurality of indication fields may be included in one DCI, each indication field corresponding to a respective indication function. One or more different indication fields may be included between DCIs corresponding to different DCI formats. From the direction of transmission, the DCI can be classified into DCI for Downlink (DL) transmission and DCI for Uplink (UL) transmission, from whether it is independent of UE-specific higher layer signaling configuration, or from the function of DCI, it can be classified into DCI (fallback DCI) for fallback, non-fallback DCI. Wherein, the retrogressive DCI may also be referred to as retrogressive DCI, and the non-retrogressive DCI may also be referred to as non-retrogressive DCI.
The format of DCI scheduling downlink transmission may be different from the format of DCI scheduling uplink transmission, and the format of the fallback DCI may be different from the format of the non-fallback DCI.
The fallback DCI is hardly dependent on the higher layer signaling configuration of the UE, and the indication fields and the size of each field are only related to the configuration common to the cells, or are predefined, whereas the number of indication fields and the size of these fields included in the non-fallback DCI are typically determined according to the higher layer signaling configuration of the UE. The non-fallback DCI can indicate more functions than the fallback DCI can indicate. Table 1 gives a format classification example of DCI for scheduling PDSCH and PUSCH.
TABLE 1
The DCI sizes corresponding to different DCI formats may be different. The DCI size refers to, in particular, a payload size (payload size) of the DCI, or the number of bits included in the DCI. The network device sends the PDCCH in the time-frequency resource indicated by CORESET and the search space, and correspondingly, the UE performs blind detection on the DCI carried in the PDCCH according to the DCI size corresponding to the DCI format to be detected in the time-frequency resource determined according to CORESET and the search space. The procedure of receiving or detecting DCI may also be regarded as a procedure of receiving or detecting PDCCH.
In general, in one search space, a UE may be configured to detect DCI in 1 or 2 formats. However, since the time-frequency resource locations of different search spaces may overlap, the UE may need to detect DCI of more formats at the same resource location. The more DCI formats, the more kinds of DCI sizes the UE needs to detect, the more times of blind detection on PDCCH, the larger the UE overhead and the higher the power consumption of the UE.
In a communication system, 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) according to the nature of the search space of the PDCCH. Wherein, the DCI transmitted in the CSS may be received by all UEs in the cell, the DCI transmitted in the USS may be received by a specific UE or UE group, or the DCI transmitted in the CSS may be received by the UE group, and the DCI transmitted in the USS may be received by a specific UE. Wherein one UE group includes one or more UEs, and embodiments of the present application are not limited. The CSS can send the back-off DCI, and the USS can send the back-off and non-back-off DCI.
For example, the search space of the PDCCH may be configured (indicated) by the network device for the UE through radio resource control (radio resource control, RRC) signaling. On one BWP of the UE, the network device may configure one or more search spaces for the UE. For a UE, the RRC signaling may be specific to the UE or may be shared (common) with other UEs, and embodiments of the present application are not limited.
For one search space, the network device may configure for the UE whether the type of the search space is a public search space or a UE-specific search space. In addition, the network device may also configure the UE with one or more of the frequency domain resource location, the aggregation level size, the number of PDCCH candidates, the detection period, the time domain resource location, the format of DCI transmitted in the search space. For example, DCI in one common search space may be configured to have formats of 0_0 and 1_0. For another example, the formats of DCI in one UE-specific search space may be configured to be 0_1 and 1_1, or the formats of DCI in one UE-specific search space may be configured to be 0_0 and 1_0. The time domain resource position comprises a first time unit (such as a time slot) offset of the search space in the detection period, a continuous first time unit number occupied by the search space in the detection period, a second time unit (such as a symbol) offset of the search space in each first time unit, and a second time unit number occupied by the search space in each first time unit.
Alternatively, 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 may be configured in such a way that the network device indicates for the UE the set of control resources (control resource set, CORESET) corresponding to the search space, and the parameter of CORESET may be regarded as a parameter of the search space. The network device indicates the frequency domain resource location of CORESET and the second time unit number of CORESET in each first time unit through RRC signaling. Alternatively, one CORESET may correspond to one search space or may correspond to a plurality of different search spaces, which embodiments of the present application are not limited to.
Illustratively, search space a corresponds to CORESET A, which CORESET A occupies 3 symbols in the time domain. The detection period of the search space A is 10 time slots, the offset of the search space A in the detection period is 3 time slots, the continuous time slots occupied by the search space A in the detection period are 2time slots, and the symbol offset of the search space A in each time slot is 3 symbols. The frequency domain resource position of the search space a is CORESET A and the time domain resource position of the search space a is 3 symbols in total from the 3 rd symbol in each of the 4 th and 5 th slots every 10 slots. The time-frequency resources resulting from the frequency domain resource locations and time domain resource locations of search space a may be referred to as the time-frequency resources indicated by search spaces a and CORESET A.
When the network device transmits DCI, such as fallback DCI or non-fallback DCI, to the UE, if used to schedule UE-specific data transmissions (e.g., scheduling PDSCH or PUSCH on which the data is transmitted is UE-specific), the DCI may be scrambled using a UE-specific radio network temporary identity (radio network temporary identity, RNTI). The UE-specific RNTI may be a cell RNTI (cell RNTI, C-RNTI), a configuration scheduling RNTI (configured scheduling RNTI, CS-RNTI), or a modulation and coding policy cell RNTI (modulation and coding scheme C-RNTI, MCS-C-RNTI) of the UE, or the like. The C-RNTI is an important identifier for a network device (e.g., a base station) to identify a UE in an access network layer, and the base station uses the C-RNTI to scramble DCI, which is equivalent to encrypted transmission of DCI between the base station and the UE through the C-RNTI. The detection capability of the DCI scrambled by the C-RNTI reflects the basic capability of the UE for detecting the DCI sent by the base station to a certain extent.
The network device may send a back-off DCI to the UE for scheduling a cell system message, scheduling a group of UEs, or scheduling non-connected UEs, where the DCI may be scrambled using a common RNTI such as a system message RNTI (system information RNTI, SI-RNTI), paging RNTI (PAGING RNTI, P-RNTI), or random access RNTI (random ACCESS RNTI, RA-RNTI). The unconnected state may also be considered an idle (idle) state, or an inactive (inactive) state. The connected state may be considered an active state. From the perspective of whether or not an RRC connection is established between the UE and the network device, the connected state is also referred to as an RRC connected (connected) state, and the unconnected state includes an RRC inactive state and an RRC idle state.
In one possible implementation:
The network device pulls the sizes of DCIs of the two formats, for example, DCIs of formats 0_0 and 1_0, in a zero padding or puncturing manner so that the sizes of DCIs of different DCI formats are the same and the DCI format 0_0 is pulled Ji Da to the DCI format 1_0;
For non-fallback DCIs sent in USS, e.g. in formats between 0_1 and 1_1, the network device does not perform any way of flushing.
Fig. 1 shows an example of the types of DCI sizes showing the above-described regulations, and if the DCI sizes corresponding to the DCI formats in the same dotted line box are different, the DCI sizes are pulled up to the same size. The RNTI in brackets following the DCI format represents the RNTI that may be used to scramble the DCI of the corresponding format.
Further, it may be provided that:
If the types of DCI sizes corresponding to DCI formats required to be detected by the UE exceeds 4 or the types of DCI sizes of DCI scrambled by the C-RNTI exceeds 3, the network device aligns the size of the fallback DCI in USS to the size of the fallback DCI in CSS, referring to the curve with an arrow in fig. 1.
Assuming that the DCI format 0_1 and the DCI format 1_1 in USS are different in size in fig. 1, the types of DCI sizes of the DCI scrambled by the C-RNTI that the UE needs to detect are 4, and these 4 types of DCIs correspond to the DCI formats scrambled by the C-RNTI within the 4 dashed boxes in fig. 1, respectively. Since the types of DCI sizes of the DCI scrambled with the C-RNTI that the UE needs to detect exceeds 3, as shown by the arrow-headed curve in fig. 1, the types of DCI sizes of the DCI that the UE needs to detect of the C-RNTI scrambled DCI in the USS are 3 after the DCI formats 0_0 and 1_0 in the USS are pulled up to the DCI formats 0_0 and 1_0 in the CSS. This pull-up result is one of the most common cases.
In practice, other results are possible, for example, the sizes of DCI format 0_1 and DCI format 1_1 in USS are the same without a pulling operation, or the size of DCI format 0_1 or DCI format 1_1 in USS is the same as the size of DCI format 0_0 or DCI format 1_0 in USS, and at this time, the type of the size of DCI scrambled by the C-RNTI is not more than 3, so that a pulling operation is not required.
In the method, the types of the DCI size can be limited to not more than 4, the types of the DCI size scrambled by the C-RNTI are limited to not more than 3, the types of the DCI size required to be detected by the UE are still more, the number of times of blind detection is still more in the process of blind detection of the PDCCH by the UE at each resource position, and the complexity of the UE is improved because the larger operation amount and memory amount of the UE are occupied in the detection process.
In order to meet the low cost and low complexity terminal requirements in the context of industrial sensor networks, wearable devices, etc., a UE with reduced capability (reduced capability, REDCAP) is to be supported in an NR communication system, and the formal name is a reduced capability NR device (Reduced Capability NR DEVICES), which may also be referred to as NR-REDCAP UE. In the standard discussion, the great names are also light (NR-light) UEs, large-scale machine-type communication (MASSIVE MACHINE TYPE communication, NR mMTC) UEs, and the like. Illustratively, REDCAP UE supports a maximum bandwidth that is smaller than a legacy UE and/or supports a number of antennas that is smaller than a legacy UE. In order to solve the above problems, especially considering that the complexity of REDCAP UE is reduced, the present application provides a communication method and apparatus to reduce the number of PDCCH detections of a UE (especially REDCAP UE), thereby reducing the complexity of the UE. The method may be applied to REDCAP UE, but may also be applied to other types of UEs, for example, UEs supporting enhanced mobile broadband (enhanced Mobile Broadband, eMBB) service or UEs supporting (ultra-mobile low-latency communication, URLLC) service, for reducing power consumption of the UE, which is not limited by embodiments of the present application.
An exemplary system architecture for the application of the present application is first described below.
The embodiment of the application can be applied to an NR communication system and other communication systems as long as a sending entity and a receiving entity of downlink control information exist in the communication system.
Fig. 2 is a schematic diagram of a communication system according to an embodiment of the present application, where, as shown in fig. 2, the communication system includes network devices and UEs 1 to 5. In the communication system, the UE 1-UE 5 can send uplink data to the network equipment, the network equipment can receive the uplink data sent by the UE 1-UE 5, the network equipment can send downlink data to the UE 1-UE 5, and the UE 1-UE 5 can receive the downlink data sent by the network equipment. In addition, UE4 and UE5 may form a sub-communication system, after receiving the downlink information sent by the network device, UE5 may forward the downlink information to UE4, UE4 may send uplink data to UE5, and UE5 may forward the uplink data to the network device.
That is, the downlink data received by the UE in the communication system may be directly sent to the UE by the network device or may be forwarded to the UE by other communication nodes in the communication system, and the uplink data sent by the UE may be directly sent to the network device or may be forwarded to the network device by other communication nodes in the communication system.
The following describes a communication method provided by the embodiment of the present application.
Fig. 3 is a schematic diagram of a communication method provided by an embodiment of the present application, and referring to fig. 3, a possible embodiment of the communication method of the present application may include the following steps:
301. The network equipment sends DCI to the UE;
302. the UE detects DCI from a network device;
in fig. 3, step 301 and step 302 are represented by arrowed line segments between the network device and the UE.
The network device may send DCI to the UE, which the UE may detect. The DCI is used to schedule a physical data channel, and a format of the DCI used to schedule the physical data channel includes a plurality of DCI formats. Wherein the kind of the size of DCI for scheduling the physical data channel does not exceed N, N being a positive integer of 3 or less, and/or the kind of the size of DCI scrambled with the UE-specific radio network temporary identity RNTI does not exceed M, M being a positive integer of 2 or less.
That is, the types of DCI sizes corresponding to the plurality of DCI formats conform to any one of the following three cases:
1) The types of the DCI sizes corresponding to the plurality of DCI formats are smaller than or equal to N, N is a positive integer smaller than or equal to 3, and when the DCI corresponding to the plurality of DCI formats is scrambled by using the UE specific radio network temporary identifier RNTI, the types of the DCI sizes corresponding to the plurality of DCI formats are smaller than or equal to M, and M is a positive integer smaller than or equal to 2.
2) The types of DCI sizes corresponding to the plurality of DCI formats are smaller than or equal to N, and N is a positive integer smaller than or equal to 3.
3) When DCIs corresponding to the plurality of DCI formats are scrambled by using the UE-specific radio network temporary identifier RNTI, the type of the DCI size corresponding to the plurality of DCI formats is less than or equal to M, and M is a positive integer less than or equal to 2.
Since the size of the DCI for scheduling the physical data channel is not more than N, N is a positive integer less than or equal to 3, and/or the size of the DCI scrambled by the UE-specific radio network temporary identifier RNTI is not more than M, M is a positive integer less than or equal to 2, the size of the DCI is reduced, which is advantageous for reducing the PDCCH detection times of the UE and thus reducing the complexity of the UE.
In one possible implementation, regarding "the types of DCI sizes corresponding to the plurality of DCI formats are less than or equal to N, where N is a positive integer less than or equal to 3", it is understood that when DCI corresponding to the plurality of DCI formats is scrambled using a common RNTI or UE-specific RNTI, the types of DCI sizes corresponding to the plurality of DCI formats are less than or equal to N, where N is a positive integer less than or equal to 3. Or it may be further described that a plurality of DCI formats may correspond to a plurality of DCIs, one of which may be scrambled using any one of a common RNTI or a UE-specific RNTI, and different ones of which may be scrambled using the same kind or different kinds of RNTIs, and the kind of DCI size corresponding to the plurality of DCIs is less than or equal to N, which is a positive integer less than or equal to 3.
In one possible implementation, the type of DCI size corresponding to the plurality of DCI formats is less than or equal to N, where N is a positive integer less than or equal to 3, and/or when the DCI corresponding to the plurality of DCI formats is scrambled using the UE-specific radio network temporary identity RNTI, the type of DCI size corresponding to the plurality of DCI formats is less than or equal to N-L, where N is a positive integer less than or equal to 3, where L is a positive integer less than N, e.g., L is 1 or 2.
The physical data channel is used for transmitting uplink data (e.g., the physical data channel is PUSCH), or for transmitting downlink data (e.g., the physical data channel is PUSCH), or includes a physical channel (e.g., PUSCH) for transmitting uplink data and a physical channel (e.g., PDSCH) for transmitting downlink data.
DCI for scheduling PDSCH may indicate one or more of DCI format indication, BWP indication, frequency domain resource allocation, time domain resource allocation, virtual RB (VRB) to Physical RB (PRB) mapping, modulation and coding strategy, new data indication, redundancy version, hybrid automatic repeat request (hybrid automatic repeat request, HARQ) process number, downlink allocation index, PUCCH transmit power control command, PUCCH resource indication, PDSCH to HARQ feedback time indication, antenna port, sounding REFERENCE SIGNAL, SRS request, transmission configuration indication and demodulation reference signal (demodulation REFERENCE SIGNAL, DMRS) sequence initialization. The transmission parameter of the PDSCH may also be referred to as indication information of the PDSCH.
The DCI for scheduling PUSCH may indicate one or more of 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, transmission power command of PUSCH, antenna port, SRS request, channel state information (CHANNEL STATE information, CSI) request, beta coefficient (Beta) offset indication, DMRS sequence initialization, uplink SHARED CHANNEL (UL-SCH) indication, and UL/supplemental uplink (UL, SUL) indication. Wherein, the transmission parameter of the PUSCH may also be referred to as indication information of the PUSCH.
After step 302, the UE may transmit a corresponding physical data channel according to the detected DCI according to the DCI.
For example, assuming that DCI detected by the UE is used to schedule PDSCH, the UE may receive PDSCH transmitted by the network device according to transmission parameters of PDSCH in the DCI. Assuming that DCI detected by the UE is used to schedule PUSCH, the UE may send PUSCH to the network device according to the transmission parameters of PUSCH in the DCI.
For convenience of description, the DCI transmitted by the network device in step 301 and detected by the UE in step 302 is referred to as dci_b, and the DCI format corresponding to dci_b is referred to as format a.
In one possible implementation, the size of dci_b meets the requirement, and no puncturing or zero padding operations need to be performed on dci_b, where dci_b is the same as dci_a. Dci_a is the original DCI obtained according to format a without a pull-up operation.
In a possible implementation, before step 301, the network device obtains dci_a according to the format a, and the network device adjusts the size of dci_a according to the pull rule to obtain dci_b. The loads of DCI_a and DCI_b are different, but the corresponding DCI formats are the same, and are both the format A.
In step 301, the network device transmits dci_b.
Before step 302, the UE may determine the adjusted size of each DCI format according to the pull rule, including determining the DCI size corresponding to format a. Optionally, DCI corresponding to format a may not need to perform a pulling operation to meet the requirement.
In step 302, the UE may detect DCI carried by the PDCCH according to the size adjusted by the determined DCI formats, including detecting dci_b carried by the PDCCH according to the size of DCI corresponding to the adjusted format a.
In one possible implementation, in step 302, the UE may decode dci_b according to the pull-alignment rule. For example, the dci_b is restored to the dci_a, and then the dci_a is decoded to obtain the transmission parameters carried by the dci_b.
The network device performs a pulling-in operation on DCIs corresponding to a part or all of DCI formats for scheduling physical data channels according to a pulling-in rule, limits the type of the size of the DCIs transmitted by the network device for scheduling physical data channels to be less than or equal to N, N being a positive integer less than or equal to 3, and/or limits the type of the size of the DCIs transmitted by the network device for scheduling physical data channels, which are scrambled by the network device using a UE-specific radio network temporary identifier RNTI, to be less than or equal to M, which is a positive integer less than or equal to 2.
The UE determines the size of each DCI format to be adjusted according to the pull rule, so that the UE is favorable to successfully detecting DCI corresponding to the corresponding DCI format carried in the PDCCH, and correctly analyzing information in the DCI according to the pull Ji Guize.
The following describes possible pull-up schemes provided by the present application for different cases of DCI formats included in DCI for scheduling a physical data channel.
1. The DCI for scheduling the physical data channel includes a third format and a fourth format detected in the terminal-specific search space USS and a third format and a fourth format detected in the common search space CSS. Wherein, the DCI corresponding to the third format is used for scheduling uplink transmission (e.g. PUSCH), the DCI corresponding to the fourth format is used for scheduling downlink transmission (e.g. PDSCH), the DCI transmitted in USS is scrambled with a UE-specific RNTI, and the DCI transmitted in CSS is scrambled with a UE-specific RNTI or with a common RNTI.
In one possible implementation, the third format is 0_0 and the fourth format is 1_0.
Illustratively, DCI format 0_0 and DCI format 1_0 include fields and the sizes of the fields are shown in table 2 below:
TABLE 2
The following is a brief description of the fields of DCI format 0_0:
1 bit, is used for distinguishing whether the DCI schedules UL transmission or DL transmission, the field value in 0_0 is 0, it indicates that it schedules a UL transmission;
the frequency domain resource allocation is X bits, which are used for indicating the frequency domain resource allocated in the current scheduling, wherein the specific size of X is related to the bandwidth of UL BWP, in particularIndicating the number of physical resource blocks (physical resource block, PRBs) included in the UL BWP, it can be seen that the larger the UL BWP is, the more possible cases of allocated frequency domain resources, and thus the larger X is. For example, when the UL BWP bandwidth is 96 PRBs, x=13, and the PUSCH scheduled by the DCI including the frequency domain resource allocation domain is transmitted in the UL BWP;
4 bits, which are used for indicating the time domain resources allocated in the current scheduling, wherein states 0-15 represented by the 4 bits indicate one row in a predefined form, and each row represents a certain time domain starting position and length;
A frequency hopping flag, 1 bit, for indicating whether the UL transmission of the UE is frequency hopped;
5 bits, which are used for indicating the modulation mode and the coding rate of the PUSCH scheduled at this time;
the new data indication is 1 bit, which is used for indicating whether the current scheduled data is new data or old data;
the redundancy version is 2 bits and is used for indicating the redundancy version of the data scheduled at this time, and the data can have four redundancy versions of 0,1, 2 and 3 after being coded;
The HARQ process number is 4 bits and is used for indicating which HARQ process data is scheduled at the time;
2 bits, is used for instructing UE to send the adjustment amount of the power of PUSCH;
the UL/SUL indication is 1 bit to indicate whether the current scheduled UL transmission is a transmission on an UL carrier or a Supplementary UL (SUL) carrier, optionally, the domain may exist only when the SUL carrier is configured;
Similarly, the meaning of many fields in DCI format 1_0 is the same as DCI format 0_0, except that UL is changed to DL, which is not described in detail herein, but is described for different fields:
1 bit, is used for distinguishing whether the DCI schedules UL transmission or DL transmission, the value of the domain in 1_0 is 1, which indicates that the DCI schedules a DL transmission;
Y bits, similar to the X bits of the uplink, but the number of PRBs included in the DL BWP is used in calculating YWhen UL BWP and DL BWP are the same size, y=x;
1 bit, indicating whether interleaving mapping is carried out between the VRB and the PRB in the DL transmission or not;
The downlink allocation index is 2 bits, and is used for indicating the accumulated downlink transmission quantity which is scheduled by the network equipment at the present time and corresponds to the feedback of the same time of the hybrid automatic repeat request acknowledgement character (hybrid automatic repeat request acknowledge character, HARQ-ACK);
2 bits, which are used for indicating the adjustment quantity of the power of a physical uplink control channel (physical downlink control channel, PUCCH) transmitted by the UE when the UE carries out HARQ-ACK feedback aiming at the PDSCH scheduled at the time;
3 bits, which are used for indicating PUCCH resources used by the UE for carrying out HARQ-ACK feedback aiming at the PDSCH scheduled at the time;
And the PDSCH to HARQ feedback time indication is 3 bits and is used for indicating the time interval between the PDSCH scheduled at this time and the HARQ feedback of the PDSCH.
In table 2, p is a positive integer.
In one possible implementation, based on the DCI size corresponding to the third format detected in the CSS being the same as the DCI size corresponding to the fourth format or based on the DCI size corresponding to the third format detected in the CSS being pulled to be the same as the DCI size corresponding to the fourth format, the DCI size corresponding to the third format detected in the USS is aligned to the DCI size corresponding to the third format detected in the CSS or to the DCI size corresponding to the fourth format detected in the CSS, and the DCI size corresponding to the fourth format detected in the USS is aligned to the DCI size corresponding to the third format detected in the CSS or to the DCI size corresponding to the fourth format detected in the RNTI to limit the kind of the DCI size for scheduling the physical data channel transmitted by the network device to be less than or equal to N, N being a positive integer of less than or equal to 3, and/or the kind of the DCI size for scheduling the physical data channel scrambled using the UE-specific radio network temporary identity transmitted by the network device is limited to be less than or equal to M being a positive integer of less than or equal to M.
2. The DCI for scheduling the physical data channel includes a first format and a second format detected in a UE-specific search space USS, where the DCI corresponding to the first format is used for scheduling uplink transmission (e.g., PUSCH) and the DCI corresponding to the second format is used for scheduling downlink transmission (e.g., PDSCH), and the DCI transmitted in the USS is scrambled using the UE-specific RNTI.
In one possible implementation, the DCI corresponding to the first format and the DCI corresponding to the second format are both non-fallback DCIs.
For example, the first format may be 0_1 and the second format may be 1_1, but the embodiments of the present application do not limit that the domain and the domain of the first format have the same size as 0_1 and do not limit that the domain and the domain of the second format have the same size as 1_1. Therefore, in the embodiment of the present application, the first format is denoted as 0_3, and the second format is denoted as 1_3. Other identification manners may be provided for the DCI in the first format and the second format in the present application, for example, the first format may be 4_0, the second format may be 4_1, etc., as long as the first format is substantially unchanged, which is not limited by the present application.
Table 3 below gives one possible definition of DCI format 0_3 and DCI format 1_3. The DCI format 0_3 and the DCI format 1_3 include fields and the sizes of the fields are shown in table 3 below:
TABLE 3 Table 3
The following description is given to each field of DCI formats 0_3 and 1_3:
The BWP indication comprises 0-2 bits, wherein the BWP is used for indicating the BWP where the DL (or UL) transmission scheduled at the time is located, and the specific bit number is determined by the DL BWP or UL BWP number configured by the UE;
the antenna port is used for indicating the DMRS port sent by the UE, and the specific bit number is determined by the type and the maximum length of the DMRS configured by the UE;
The SRS request is used for triggering the UE to transmit the aperiodic SRS, and the specific bit number is determined by the SRS configuration of the UE;
the CSI request is used for triggering the UE to carry out aperiodic CSI reporting, and the specific bit number is determined by the CSI reporting configuration of the UE;
The Beta offset indication is used for indicating the UE to report the resource of the CSI information in the PUSCH, and the specific bit number is determined by the indication configuration of the Beta offset;
DMRS sequence initialization, which is to instruct the scrambling code used for initializing the DMRS sequence of the UE, and the specific bit number is determined by the DMRS configuration;
1 bit, is used for indicating whether UE transmits the uplink shared channel (uplink SHARED CHANNEL, UL-SCH) on the PUSCH channel in the UL transmission, wherein the UL-SCH is an uplink shared channel in the logical channel;
The transmission configuration indicates, that is TCI (transmission configuration indication), a downlink reference signal used for indicating that PDSCH or DMRS in the DL transmission is quasi co-located, and the specific number of bits is determined by the configuration of TCI.
The description of other fields in table 3 may refer to the related description of table 2, and will not be repeated here.
It should be noted that, table 3 may be used as a possible method for designing UL non-fallback and DL non-fallback DCI of a UE, that is, a first format DCI and a second format DCI, where the sequence of the included fields may be changed, the number of bits of each field may be different, or some other fields not listed herein may be included, or some fields may not be included.
In one possible implementation, the DCI size corresponding to the first format is aligned to the DCI size corresponding to the second format.
Or in one possible implementation, the DCI size corresponding to the second format is aligned to the DCI size corresponding to the first format.
Or in one possible implementation, if the DCI size corresponding to the first format is smaller than the DCI size corresponding to the second format, the DCI size corresponding to the first format is aligned to the DCI size corresponding to the second format, and if the DCI size corresponding to the second format is smaller than the DCI size corresponding to the first format, the DCI size corresponding to the second format is aligned to the DCI size corresponding to the first format.
3. The DCI for scheduling the physical data channel includes a first format, a second format, a third format and a fourth format detected in the UE-specific search space USS. The DCI corresponding to the first format is used for scheduling uplink transmission (such as PUSCH), the DCI corresponding to the third format is used for scheduling uplink transmission (such as PUSCH), and the first format is different from the third format, the DCI corresponding to the second format is used for scheduling downlink transmission (such as PDSCH), the DCI corresponding to the fourth format is used for scheduling downlink transmission (such as PDSCH), and the DCI corresponding to each format transmitted in USS is different from the fourth format, and is scrambled by using UE specific RNTI.
In one possible implementation, the first format is the DCI format 0_3, the second format is the DCI format 1_3, the third format is 0_0, and the fourth format is 1_0.
In one possible implementation, based on the first format being the same as the DCI size corresponding to the second format, or based on the first format being aligned with the DCI size corresponding to the second format, the DCI size corresponding to the third format transmitted in USS is aligned to the DCI size corresponding to the first format or to the DCI size corresponding to the second format, and the DCI size corresponding to the fourth format is aligned to the DCI size corresponding to the first format or to the DCI size corresponding to the second format.
In any embodiment of the present application, the meaning expressed in the following description manner may be considered as the same, "DCI size corresponding to a certain format (referred to as format a) is aligned to DCI size corresponding to another format (referred to as format B)", "DCI size corresponding to format a is aligned to DCI size corresponding to format B", "DCI size corresponding to format a is pulled up with DCI size corresponding to format B as a standard so that DCI size corresponding to format a is the same as DCI size corresponding to format B", "DCI size corresponding to format a is adjusted, and DCI size corresponding to format a after adjustment is the same as DCI size corresponding to format B", etc.
In any embodiment of the present application, the DCI size corresponding to format a is aligned to the DCI size corresponding to format B, including the following two methods:
In mode 1, if the DCI size corresponding to format a is smaller than the DCI size corresponding to format B, at least one padding bit (e.g., 0 or 1) is padded in the DCI corresponding to format a, and the padded DCI size corresponding to format a is the same as the DCI size corresponding to format B.
In mode 2, if the DCI size corresponding to format a is larger than the DCI size corresponding to format B, K fields of the DCI corresponding to format a are truncated or at least one bit in K fields of 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, wherein K is a positive integer.
In one possible implementation, at least one bit of its high order bits in the truncated domain is truncated, and even all bits in the truncated domain are truncated.
In one possible implementation, the K domains include at least one of the following:
A frequency domain resource allocation domain, a time domain resource allocation domain, a PUCCH resource indication domain, a PDSCH-to-HARQ feedback time indication domain, an SRS request domain, and a DMRS sequence initialization domain. For example, format A is format 1_3, and the K domains include at least one of a frequency domain resource allocation domain, a time domain resource allocation domain, a PUCCH resource indication domain, an SRS request domain, and a PDSCH to HARQ feedback time indication domain. For example, format A is format 0_3, and the K domains include at least one of a frequency domain resource allocation domain, a time domain resource allocation domain, an SRS request domain, and a DMRS sequence initialization domain.
In order to ensure that the DCIs of various formats are accurately notified, the DCIs corresponding to the DCI format with less load can be pulled up to the DCIs corresponding to the DCI format with more load, so that the pulling up is only performed in the mode 1, and the load in the DCIs is not lost.
The above-mentioned pull-up method is specifically described below taking the case that the format a is the second format (e.g., 1_3) and the format B is the first format (e.g., 0_3).
For mode 1, if the DCI size corresponding to DCI format 0_3 is larger than the DCI size corresponding to DCI format 1_3, the network device may fill p padding bits into the DCI corresponding to DCI format 1_3, e.g., may fill p "0" s or "1" s at the end of the payload, so that the DCI sizes corresponding to the two DCI formats are the same, where p is a positive integer.
If the UE detects DCI corresponding to DCI format 1_3 from the network device, the UE may ignore the last p bits of the payload of the DCI or truncate the last p bits of the DCI to obtain DCI corresponding to the unadjusted DCI format 1_3.
For mode 2, if the DCI size corresponding to DCI format 0_3 is smaller than the DCI size corresponding to DCI format 1_3, the network device may truncate at least one bit of at least one domain in the DCI corresponding to DCI format 1_3, for example, truncate one or more upper bits of the frequency domain resource allocation domain in the DCI corresponding to DCI format 1_3, truncate one or more upper bits of the frequency domain resource allocation domain in DCI format 1_3, or truncate all bits of the SRS request domain, so that the DCI sizes corresponding to both DCI formats are the same.
Assume that the upper 3 bits of the frequency resource allocation domain in DCI corresponding to DCI format 1_3 are truncated and the payload in the truncated domain is "11". If the UE detects DCI corresponding to DCI format 1_3 from the network device, the UE may fill the upper 3 bits of the frequency resource allocation domain in the DCI with a predefined value (e.g. "0"), and consider the value indicated by the domain to be "00011".
Alternatively, considering that typical application scenarios of REDCAP UE include industrial sensors and video monitoring, and the like, and REDCAP UE is a sensor terminal or a video terminal, its uplink transmission amount is large, so its transmission service is dominant above. Regardless of the relationship between the DCI size corresponding to DCI format 0_3 and the DCI size corresponding to DCI format 1_3, the DCI size corresponding to DCI format 1_3 is aligned to the DCI size corresponding to DCI format 0_3, that is, the DCI size corresponding to the DCI format of DL scheduling is aligned to the DCI size corresponding to the DCI format of UL scheduling, which is advantageous for protecting the scheduling performance of uplink transmission. Specific:
(1) If the number of bits of DCI format 0_3 is greater than the number of bits of DCI format 1_3, then the accurate indication of the uplink scheduling information may be ensured by zero padding Ji Da for a small period in DCI format 1_3 without having to truncate any field of DCI format 0_3, e.g., if the number of bits of DCI format 0_3 is p more bits than the number of bits of DCI format 1_3 before the padding, then p predefined bits (e.g., "0") may be padded at the end of the valid bits of DCI format 1_3 to align DCI format 1_3 to the size of DCI format 0_3.
(2) If the bit number of DCI format 0_3 is smaller than that of DCI format 1_3, some fields in DCI format 1_3 may be truncated without filling unnecessary bits into DCI format 0_3, so that the load of DCI format 0_3 is reduced as much as possible, and the detection reliability is ensured. For example, if the number of bits of DCI format 0_3 is q bits less than the number of bits of DCI format 1_3 before the pulling, the high q bits of a specific indication field (e.g., a frequency domain resource allocation indication field) of DCI format 1_3 may be truncated, so that DCI format 1_3 is pulled to the size of DCI format 0_3. Wherein q is a positive integer.
In the following, taking the network device in fig. 2 as the gNB and the UE1 as the UE as an example, a possible embodiment of the communication method according to the present application is described based on the method described in fig. 3.
Referring to fig. 4, another possible embodiment of the communication method of the present application includes the following steps 401 to 409.
401. The gNB transmits RRC configuration information to the UE 1.
The RRC configuration information is used to indicate a resource location of the PDCCH configured for the UE1 (including a resource location of the CSS and a resource location of the USS), a DCI format required to be detected by the UE1, and the like.
In a possible implementation manner, the communication method provided by the present application may not perform step 401, and the gnb and the UE1 may determine, according to preset or predefined configuration information, a resource location of the PDCCH allocated to the UE1 and a DCI format required to be detected by the UE 1.
402. The gNB determines the pull Ji Guize corresponding to each DCI format that needs to be detected by UE 1.
After RRC configuration of UE1, the gNB determines each DCI format required to be detected by UE1, and determines a pull Ji Guize corresponding to each DCI format, where the pull rule may be a pull Ji Guize described in the method embodiment related to fig. 3, where the pull rule is used to limit the types of DCI sizes corresponding to each DCI format required to be detected by UE1 to N or less, where N is a positive integer less than or equal to 3, and/or limit the types of DCI sizes corresponding to each DCI format scrambled by using a UE-specific radio network temporary identifier RNTI to be less than or equal to M, where M is a positive integer less than or equal to 2.
403. UE1 determines the pull Ji Guize corresponding to each DCI format to be detected.
After receiving the RRC configuration information from the gNB, the UE1 determines each DCI format to be detected, and determines a pull Ji Guize corresponding to each DCI format, where the pull rule is the same as the pull rule determined by the gNB in step 402.
404. And the UE1 determines the size of the pulled-up DCI corresponding to each DCI format according to the pulling-up rule.
The UE1 determines the size of the DCI corresponding to each DCI format after being pulled up according to the pulling-up rule, where the type of the size of the DCI after being pulled up may be the type of the DCI size corresponding to multiple DCI formats described in the method embodiment related to fig. 3, the type of the size of the DCI after being pulled up does not exceed N, N is a positive integer less than or equal to 3, and/or the type of the DCI size corresponding to each DCI format scrambled by using the UE-specific radio network temporary identifier RNTI is less than or equal to M, where M is a positive integer less than or equal to 2.
405. And the UE1 performs blind detection on the PDCCH according to the RRC configuration information and the size of the DCI which corresponds to each DCI format to be detected and is leveled.
406. And the gNB adjusts the size of the DCI_a according to the pull-up rule to obtain the DCI_b.
When the DCI to be sent to UE1 by the gNB is called dci_a and the format of dci_a is called format a, the gNB adjusts the size of dci_a according to the pull Ji Guize 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 both is format a.
The gNB adjusts the size of DCI_a according to the pull-up rule, and reference may be made to the adjustment procedure described in the method embodiment related to FIG. 3, which is not repeated here.
The order in which the gNB performs steps 402 and 406 and the UE1 performs steps 403 to 405 is not limited.
407. The gNB transmits DCI_b to UE1, and UE1 detects DCI_b.
After the gcb sends the dci_b to the UE1 through the PDCCH, the UE1 may detect, at the configured resource location, the dci_b carried in the PDCCH from the gcb according to the adjusted DCI size (same as the dci_b size) corresponding to the format a.
408. UE1 restores dci_b to dci_a according to pull Ji Guize.
After detecting the dci_b, the UE1 may determine that the format of the dci_b is the format a according to the DCI format indication field, recover the dci_b to the dci_a according to the pull Ji Guize corresponding to the format a, and decode the dci_a to obtain the transmission parameter carried in the dci_a.
409. UE1 transmits the corresponding physical data channel according to dci_a.
Assuming that dci_a detected by UE1 is used to schedule PDSCH, UE may detect PDSCH transmitted by network device according to transmission parameters of PDSCH in dci_a. Assuming that dci_a detected by UE1 is used to schedule PUSCH, the UE may send PUSCH to the network device according to the transmission parameters of PUSCH in dci_a.
Step 402 in the corresponding embodiment of fig. 4 is described below.
In the embodiment of the present application, the type of the size of DCI for scheduling a physical data channel does not exceed N, N is a positive integer less than or equal to 3, and/or the type of the size of DCI scrambled with a UE-specific radio network temporary identity RNTI does not exceed M, M is a positive integer less than or equal to 2. Several possible embodiments of step 402 are described below for several possible combinations of values of M and N.
1. The combination of the values of M and N is that N=3 and M=2.
With this combination of values, the size category of DCI required to be detected by UE1 may be reduced to 3, and/or the size category of DCI scrambled by a specific RNTI of UE1 required to be detected by UE may be reduced to 2.
Each DCI format to be detected by UE1 and 1 includes DCI format 0_0 and DCI format 1_0 transmitted in the CSS, and DCI format 0_0, DCI format 0_3, DCI format 1_0 and DCI format 1_3 transmitted in the USS.
Referring to fig. 5a, step 402 includes refinement steps 4021a to 4026a as follows.
4021A and gNB pull the DCI size corresponding to DCI format 0_0 transmitted in the CSS to the DCI size corresponding to DCI format 1_0.
The DCI format 0_0 sent in the CSS is aligned to the DCI size corresponding to the DCI format 1_0, which considers that important common information or important configuration information is often required to be issued in the CSS, so that the accuracy of the downlink transmission instruction needs to be further ensured.
4022A and gNB concatenate the DCI size corresponding to DCI format 0_0 transmitted in USS to the DCI size corresponding to DCI format 1_0.
The DCI format with a smaller payload is padded by adding padding bits, for example, if the number of payload of 0_0 before padding is smaller than 1_0, 0 is padded in 0_0 until the size of 0_0 is the same as 1_0, whereas if the number of payload of 0_0 before padding is larger than 1_0, 0 is padded in 1_0 until the size of 1_0 is the same as 0_0.
This way no information bits (payload) in any DCI format are lost, ensuring the accuracy of the indication.
In the embodiment of the present application, it may be assumed that the DCI size corresponding to the DCI format 0_0 transmitted in the USS is smaller than the DCI size corresponding to the DCI format 1_0, so that the gNB pulls up the DCI size corresponding to the DCI format 0_0 transmitted in the USS to the DCI size corresponding to the DCI format 1_0.
The embodiment of the present application does not limit the sequence between step 4021a and step 4022 a.
4023A and gNB determine whether the size category of the DCI is less than or equal to 3, and whether the size category of the DCI scrambled by the C-RNTI is less than or equal to 2, if not, step 4024a is executed, and if yes, the process is ended.
After step 4021a and step 4022a, if the size category of DCI required to be detected by UE1 is less than or equal to 3 and the size category of DCI scrambled by the C-RNTI required to be detected by UE1 is less than or equal to 2, then step 402 is considered to be completed, i.e., the flow of step 402 is ended. If the size category of the DCI required to be detected by UE1 is greater than 3, or the size category of the DCI scrambled by the C-RNTI required to be detected by UE1 is greater than or equal to 2, step 4024a is performed.
4024A, gNB aligns DCI format 0_0 and DCI format 1_0 transmitted in USS to DCI format 1_0 transmitted in CSS.
By way of example, step 4024a may specifically include steps 1 through 3 as follows.
1. Optionally, the padding bits in DCI format 0_0 and DCI format 1_0 in the current USS are removed;
2. alternatively, by using in CSSAndInstead of USSAndSo that the number of bits X and Y of the frequency domain resource allocation domain of DCI format 0_0 and DCI format 1_0 in USS is the same as DCI format 0_0 and DCI format 1_0 in CSS;
3. Similar to the pulling method between DCI format 0_0 and DCI format 1_0 in CSS, DCI format 0_0 in USS after step 2 is pulled to DCI format 1_0.
Since the DCI size corresponding to DCI format 0_0 transmitted in the CSS has been pulled up to the DCI size of DCI format 1_0 in step 4021a, step 4024a may also be understood that the gNB pulls up DCI format 0_0 and DCI format 1_0 transmitted in the USS to DCI format 0_0 transmitted in the CSS.
4025A and gNB determine whether the size category of the DCI is less than or equal to 3, and whether the size category of the DCI scrambled by the C-RNTI is less than or equal to 2, if not, step 4026a is executed, and if yes, the process is ended.
After step 4024a, if the size category of the DCI required to be detected by UE1 is less than or equal to 3 and the size category of the DCI scrambled by the C-RNTI required to be detected by UE1 is less than or equal to 2, then step 402 is considered to be completed, i.e., the flow of step 402 is ended. If the size category of the DCI required to be detected by UE1 is greater than 3, or the size category of the DCI scrambled by the C-RNTI required to be detected by UE1 is greater than or equal to 2, step 4026a is performed.
4026A and gNB concatenate the DCI size corresponding to DCI format 0_3 transmitted in USS with the DCI size corresponding to DCI format 1_3;
The DCI format with the smaller payload is pulled up to the DCI format with the larger payload by supplementing the padding bits, or the DCI size corresponding to DCI format 1_3 is aligned to the DCI size corresponding to DCI format 0_3, regardless of the relation between the DCI size corresponding to DCI format 0_3 and the DCI size corresponding to DCI format 1_3.
In the embodiment of the present application, it is assumed that the gNB pulls up the DCI size corresponding to the DCI format 0_3 transmitted in the USS to the DCI size corresponding to the DCI format 1_3.
Through steps 4021a to 4026a, the gnb may determine a pulling rule corresponding to each DCI format to be detected by the UE1, that is, pulling 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, pulling 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, pulling the DCI format 0_0 and the DCI format 1_0 sent in the USS to the DCI format 1_0 sent in the CSS, and pulling 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.
After the gNB determines the pulling rule corresponding to each DCI format that needs to be detected by the UE1, the pulling rule of the dci_a may be determined according to the search space of the dci_a and the format a thereof, and if the search space is USS and the format a is DCI format 0_0, the gNB may pull the dci_a to the DCI size corresponding to the DCI format 1_0 sent in the CSS. Assuming that in step 406, the gNB fills the end of the payload of dci_a with p "0 s", dci_a filled with p "0 s" is referred to as dci_b, where p is a positive integer.
The implementation of step 403 may refer to the corresponding embodiment of fig. 5a, and will not be described here again. Therefore, the UE1 can determine a pulling rule corresponding to each DCI format required to be detected by the UE1, namely, pulling the DCI size corresponding to the DCI format 0_0 transmitted in the CSS to the DCI size corresponding to the DCI format 1_0, pulling the DCI size corresponding to the DCI format 0_0 transmitted in the USS to the DCI size corresponding to the DCI format 1_0, pulling the DCI format 0_0 and the DCI format 1_0 transmitted in the USS to the DCI format 1_0 transmitted in the CSS, and pulling the DCI size corresponding to the DCI format 0_3 transmitted in the USS to the DCI size corresponding to the DCI format 1_3.
Then, in step 404, the UE1 may determine the size of the DCI format 0_0, DCI format 0_3, DCI format 1_0, and DCI format 1_3 transmitted in the USS by determining the size of the DCI format 0_0 and DCI format 1_0 transmitted in the CSS by pulling Ji Guize.
In step 408, UE1 may restore dci_b to dci_a according to the pull rule, for example, truncate the last p-bit zero padding bits of the payload of dci_b, to obtain truncated DCI, i.e., dci_a.
Assuming that a certain period of time has elapsed, the format and scrambling method corresponding to the DCI transmitted by the gNB to the UE1 are as shown in fig. 5b, and the DCI sizes corresponding to the DCI formats in the same dashed box are the same. As can be seen, the corresponding communication method of fig. 5a is advantageous to limit the size variety of DCI sent by the gNB (detected by UE 1) scrambled by the characteristic RNTI of the UE to no more than 2. Wherein, the DCI in the non-connected state indicates DCI transmitted by the gNB to the UE when the RRC state of the UE is in the non-connected state. The DCI in the connected state indicates DCI transmitted by the gNB to the UE when the RRC state of the UE is in the connected state.
Referring to fig. 6a, step 402 includes refinement steps 4021b through 4026b as follows.
4021B and gNB pull the DCI size corresponding to DCI format 0_0 transmitted in the CSS to the DCI size corresponding to DCI format 1_0.
4022B and gNB concatenate the DCI size corresponding to DCI format 0_0 transmitted in USS to the DCI size corresponding to DCI format 1_0.
4023B and gNB determine whether the size category of the DCI is less than or equal to 3, and whether the size category of the DCI scrambled by the C-RNTI is less than or equal to 2, if not, step 4024b is executed, and if yes, the process is ended.
Steps 4021b to 4023b may be understood by referring to the descriptions related to steps 4021a to 4023a in the corresponding embodiment of fig. 5a, and are not described herein.
4024B and gNB concatenate the DCI size corresponding to DCI format 0_3 transmitted in USS to the DCI size corresponding to DCI format 1_3.
Step 4024b may be understood by reference to the relevant description of step 4026a, which is not repeated here.
4025B and gNB determine whether the size category of the DCI is less than or equal to 3, and whether the size category of the DCI scrambled by the C-RNTI is less than or equal to 2, if not, step 4026b is executed, and if yes, the process is ended.
After step 4024b, if the size category of the DCI required to be detected by UE1 is less than or equal to 3 and the size category of the DCI scrambled by the C-RNTI required to be detected by UE1 is less than or equal to 2, then step 402 is considered to be completed, i.e., the flow of step 402 is ended. If the size category of the DCI required to be detected by UE1 is greater than 3, or the size category of the DCI scrambled by the C-RNTI required to be detected by UE1 is greater than or equal to 2, step 4026b is performed.
4026B, gNB concatenates DCI format 0_0 and DCI format 1_0 transmitted in USS to DCI format 1_3 transmitted in USS.
Since the DCI size corresponding to DCI format 0_3 transmitted in USS has been pulled up to the DCI size of DCI format 1_3 in step 4024b, step 4026b may also be understood that the gNB pulls up DCI format 0_0 and DCI format 1_0 transmitted in USS to DCI format 0_3 transmitted in CSS.
Through steps 4021b to 4026b, the gnb may determine a pulling rule corresponding to each DCI format to be detected by the UE1, that is, pulling 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, pulling 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, and pulling the DCI formats 0_0 and 1_0 sent in the USS to the DCI format 1_3 sent in the USS.
It is assumed that, in a certain period of time, the format and scrambling method corresponding to the DCI transmitted by the gNB to the UE1 are as shown in fig. 6b, and the DCI sizes corresponding to the DCI formats in the same dashed box are the same. As can be seen, the corresponding communication method of fig. 6a is advantageous to limit the size variety of DCI sent by the gNB (detected by UE 1) scrambled by the characteristic RNTI of the terminal to no more than 2.
1.2, Each DCI format required to be detected by UE1 includes DCI format 0_0 and DCI format 1_0 transmitted in the CSS, DCI format 0_3 and DCI format 1_3 transmitted in the USS.
Referring to fig. 7a, step 402 includes refinement steps 4021c to 4025c as follows.
4021C and gNB pull the DCI size corresponding to DCI format 0_0 transmitted in the CSS to the DCI size corresponding to DCI format 1_0.
4022C and gNB concatenate the DCI size corresponding to DCI format 0_0 transmitted in USS to the DCI size corresponding to DCI format 1_0.
4023C, the gNB determines whether the size category of the DCI required to be detected by the UE1 is less than or equal to 3, and whether the size category of the DCI scrambled by the C-RNTI required to be detected by the UE1 is less than or equal to 2, if not, step 4024C is executed, if yes, then the processing is ended.
Steps 4021c to 4023c may be understood by referring to the descriptions related to steps 4021a to 4023a in the corresponding embodiment of fig. 5a, and are not described herein.
4024C and gNB concatenate the DCI size corresponding to DCI format 0_3 transmitted in USS to the DCI size corresponding to DCI format 1_3.
Step 4024c may be understood with reference to the description of step 4026a, which is not described herein.
Assuming that a certain period of time has elapsed, the format and scrambling method corresponding to the DCI transmitted by the gNB to the UE1 are as shown in fig. 7b, and the DCI sizes corresponding to the DCI formats in the same dashed box are the same. As can be seen, the corresponding communication method of fig. 7a is advantageous to limit the size variety of DCI sent by the gNB (detected by UE 1) scrambled by the characteristic RNTI of the terminal to no more than 2.
2. The combination of the values of M and N is that M=2 and N=1.
With this combination of values, the size category of DCI required to be detected by UE1 may be reduced to 2, and/or the size category of DCI scrambled by a specific RNTI of UE1 required to be detected by UE may be reduced to 1.
Each DCI format to be detected by UE1 and 2.1 includes DCI format 0_0 and DCI format 1_0 transmitted in the CSS, and DCI format 0_0, DCI format 0_3, DCI format 1_0 and DCI format 1_3 transmitted in the USS.
Referring to fig. 8a, step 402 includes refinement steps 4021d to 4028d as follows.
4021D and gNB pull the DCI size corresponding to DCI format 0_0 transmitted in the CSS to the DCI size corresponding to DCI format 1_0.
4022D and gNB concatenate the DCI size corresponding to DCI format 0_0 transmitted in USS to the DCI size corresponding to DCI format 1_0.
4023D and gNB determine whether the size category of the DCI is less than or equal to 2, and whether the size category 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 process is ended.
4024D, gNB aligns DCI format 0_0 and DCI format 1_0 transmitted in the USS to DCI format 1_0 transmitted in the CSS.
4025D and gNB determine whether the size category of the DCI is less than or equal to 2, and whether the size category 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 process is ended.
Steps 4021d to 4025d may be understood by referring to the descriptions related to steps 4021a to 4025a in the corresponding embodiment of fig. 5a, and are not described herein.
4026D and gNB concatenate the DCI size corresponding to DCI format 0_3 transmitted in USS to the DCI size corresponding to DCI format 1_3.
4027D and gNB determine whether the size category of the DCI is less than or equal to 2, and whether the size category 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 process is ended.
After step 4026d, step 4027d is performed.
4028D, gNB concatenates DCI sizes corresponding to DCI format 0_3 and DCI format 1_3 transmitted in USS to DCI format 0_0 transmitted in USS.
Since the DCI size corresponding to DCI format 0_0 transmitted in the CSS has been pulled up to the DCI size of DCI format 1_0 in step 4021d, and DCI format 0_0 and DCI format 1_0 transmitted in the USS have been pulled up to DCI format 1_0 transmitted in the CSS in step 4024d, step 4028d may also be understood as that the gNB pulls up the DCI size corresponding to DCI format 0_3 and DCI format 1_3 transmitted in the USS to DCI format 1_0 transmitted in the USS, or to DCI format 0_0 transmitted in the CSS, or to DCI format 1_0 transmitted in the CSS.
Assuming that a certain period of time has elapsed, the format and scrambling method corresponding to the DCI transmitted by the gNB to the UE1 are as shown in fig. 8b, and the DCI sizes corresponding to the DCI formats in the same dashed box are the same. As can be seen, the corresponding communication method of fig. 8a is advantageous to limit the size variety of DCI sent by the gNB (detected by UE 1) scrambled by the characteristic RNTI of the UE to no more than 1.
2.2, Each DCI format required to be detected by UE1 includes DCI format 0_0 and DCI format 1_0 transmitted in the CSS, DCI format 0_3 and DCI format 1_3 transmitted in the USS.
Referring to fig. 9a, step 402 includes refinement steps 4021e to 4026e as follows.
4021E and gNB pull the DCI size corresponding to DCI format 0_0 transmitted in the CSS to the DCI size corresponding to DCI format 1_0.
4022E and gNB concatenate the DCI size corresponding to DCI format 0_0 transmitted in USS to the DCI size corresponding to DCI format 1_0.
4023E and gNB determine whether the size category of the DCI is less than or equal to 2, and whether the size category 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 process is ended.
Steps 4021e to 4023e may be understood by referring to the descriptions related to steps 4021a to 4023a in the corresponding embodiment of fig. 5a, and are not described herein.
4024E and gNB concatenate the DCI size corresponding to DCI format 0_3 transmitted in USS to the DCI size corresponding to DCI format 1_3.
Step 4024e may be understood with reference to the description of step 4026a, which is not described herein.
4025E and gNB determine whether the size category of the DCI is less than or equal to 2, and whether the size category 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 process is ended.
Step 4025e is performed after step 4024 e.
4026E and gNB concatenate DCI sizes corresponding to DCI format 0_3 and DCI format 1_3 transmitted in USS to DCI format 0_0 transmitted in CSS.
Since the DCI size corresponding to DCI format 0_0 transmitted in the CSS has been pulled up to the DCI size of DCI format 1_0 in step 4021e, step 4026e may also be understood that the gNB pulls up the DCI sizes corresponding to DCI format 0_3 and DCI format 1_3 transmitted in the USS to DCI format 1_0 transmitted in the CSS.
Assuming that a certain period of time has elapsed, the format and scrambling method corresponding to the DCI transmitted by the gNB to the UE1 are as shown in fig. 9b, and the DCI sizes corresponding to the DCI formats in the same dashed box are the same. As can be seen, the corresponding communication method of fig. 9a is advantageous to limit the size variety of DCI sent by the gNB (detected by UE 1) scrambled by the characteristic RNTI of the UE to no more than 1.
It should be understood that the specific examples of the embodiments of the present application are intended to facilitate a better understanding of the embodiments of the present application by those skilled in the art, and are not intended to limit the scope of the embodiments of the present application.
It should be understood that, in various embodiments of the present application, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic thereof, and should not constitute any limitation on the implementation process of the embodiments of the present application.
In the embodiments of the present application, the method provided in the embodiments of the present application is described in terms of the network device, the terminal, and the interaction between the network device and the terminal, respectively. In order to implement the functions in the method provided by the embodiment of the present application, the network device and the terminal may include hardware structures and/or software modules, and implement the functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Some of the functions described above are performed in a hardware configuration, a software module, or a combination of hardware and software modules, depending on the specific application of the solution and design constraints.
Fig. 10 shows a schematic structural diagram of a communication device. The communication device is used for realizing the functions of the UE described in the embodiment of the application. As shown in fig. 10, the communication device 10 may include a detection module 1001. The detection module 1001 is configured to perform step 302 in fig. 3, step 405 in fig. 4, step 407 performed by UE1, and so on. The detection module may also be referred to as a receiving module.
In one possible implementation, referring to the modules represented by the dashed boxes in fig. 10, the communication apparatus 10 may further include a processing module 1002, where the processing module 1002 is coupled to the detection module 1001 for performing steps 403, 404, and 408 in fig. 4. Reference is made to the detailed description of the corresponding steps in the above method embodiments for specific execution, 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, which may be in electrical, mechanical, or other forms for information interaction between the devices, units, or modules.
In a possible implementation, the communication apparatus 10 may further comprise a transmitting module (not shown in fig. 10), for example for transmitting PUSCH to a network device. The detection module and the transmission module of the communication device 10 may be integrated as a transceiver module or a communication module.
Fig. 11 is a schematic structural diagram of a communication device according to an embodiment of the present application. The communication device is used for realizing the functions of the network equipment described in the embodiment of the application. Referring to fig. 11, the communication device 11 includes a transmitting module 1101. The sending module 1101 is configured to perform step 301 in fig. 3, step 401 in fig. 4, and step 407. Optionally, referring to the module corresponding to the dashed box in fig. 11, the communication device 11 further includes a processing module 1102. The processing module 1102 is configured to perform step 402, step 406, etc. in fig. 4. Reference is made to the detailed description of the corresponding steps in the above method embodiments for specific execution, and details are not repeated here.
In a possible implementation, the communication device 11 may further include a receiving module (not shown in fig. 11), for example, for receiving a PUSCH transmitted by the terminal. The receiving module and the transmitting module of the communication device 11 may be integrated as a transceiver module or a communication module.
The division of the modules in the embodiments of the present application is schematically only one logic function division, and there may be another division manner in actual implementation, and in addition, each functional module in each embodiment of the present application may be integrated in one processor, or may exist separately and physically, or two or more modules may be integrated in one module. The integrated modules may be implemented in hardware or in software functional modules.
Fig. 12 shows an apparatus 1200 according to an embodiment of the present application, which is configured to implement the functions of the terminal in the above method. The device can be a terminal or a device which can be matched with the terminal for use. The apparatus may be installed in a terminal. The device may be a chip system, for example. In the embodiment of the application, the chip system can be formed by a chip, and can also comprise the chip and other discrete devices. The apparatus 1200 includes at least one processor 1220 configured to implement the functions of a terminal in the method provided by the embodiment of the present application.
The apparatus 1200 may also include at least one memory 1230 for storing program instructions and/or data. Memory 1230 is coupled to processor 1220. Processor 1220 may operate in conjunction with memory 1230. Processor 1220 may execute program instructions stored in memory 1230. One or more of the at least one memory may be included in the processor.
The apparatus 1200 may also include a communication interface 1210 for communicating with other devices over a transmission medium, such that an apparatus for use in the apparatus 1200 may communicate with other devices. Illustratively, the communication interface 1210 may be a transceiver, circuit, bus, module, pin, or other type of communication interface, which may be a network device. The processor 1220 utilizes a communication interface to send and receive data, for example, utilizes the communication interface to detect DCI from a network device, so as to implement the functions of the terminal in the method provided in the embodiment of the present application, specifically referring to the detailed description in the method example, which is not repeated herein.
The specific connection medium between the transceiver 1210, the processor 1220 and the memory 1230 is not limited in the embodiment of the present application. The embodiment of the present application is shown in fig. 12 as a memory 1230, a processor 1220, and a transceiver 1210 connected by a bus 1240, which is shown in fig. 12 as a bold line, and the connection between other components is merely illustrative and not limited thereto. The buses may be classified as address buses, data buses, control buses, etc. For ease of illustration, only one thick line is shown in fig. 12, but not only one bus or one type of bus.
Fig. 13 shows an apparatus 1300 according to an embodiment of the present application, which is configured to implement the functions of the network device in the above method. The device may be a network device or a device that can be used in cooperation with a network device. The apparatus may be installed in a network device. The device may be a chip system, for example. The apparatus 1300 includes at least one processor 1320 for implementing the functions of the network device in the method provided by the embodiment of the present application.
The apparatus 1300 may also include at least one memory 1330 for storing program instructions and/or data. A memory 1330 is coupled to processor 1320. Processor 1320 may operate in conjunction with memory 1330. Processor 1320 may execute program instructions stored in memory 1330. One or more of the at least one memory may be included in the processor.
The apparatus 1300 may also include a communication interface 1310 for communicating with other devices over a transmission medium, such that an apparatus for use in the apparatus 1300 may communicate with other devices. By way of example, 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. Processor 1320 utilizes a communication interface to send and receive data, for example, utilizes the communication interface to send DCI to a terminal, so as to implement the functions of the network device in the method provided in the embodiment of the present application, specifically referring to the detailed description in the method example, which is not described herein.
The specific connection medium between the transceiver 1310, the processor 1320, and the memory 1330 is not limited in this embodiment of the present application. The embodiment of the present application is shown in fig. 13 with the memory 1330, the processor 1320, and the transceiver 1310 connected by a bus 1340, which is shown in bold lines in fig. 13, and the connection between other components is merely illustrative, and not limiting. The buses may be classified as address buses, data buses, control buses, etc. For ease of illustration, only one thick line is shown in fig. 13, but not only one bus or one type of bus.
In the embodiment of the present application, the processor may be a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the methods, steps and logic blocks disclosed in the embodiments of the present application. The general purpose processor may be a microprocessor or any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in a hardware processor for execution, or in a combination of hardware and software modules in the processor for execution.
In the embodiment of the present application, the memory may be a nonvolatile memory, such as a hard disk (HARD DISK DRIVE, HDD) or a solid-state disk (SSD), or may be a volatile memory (RAM). The memory is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to such. The memory in embodiments of the present application may also be circuitry or any other device capable of performing memory functions for storing program instructions and/or data.
The technical scheme provided by the embodiment of the application can be realized completely or partially by software, hardware, firmware or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present application, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, a network device, a terminal device, or other programmable apparatus. 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, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., 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, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., digital video disc (digital video disc, DVD)), or a semiconductor medium, etc.
In the embodiments of the present application, where there is no logical conflict, embodiments may be referred to each other, for example, methods and/or terms between method embodiments may be referred to each other, for example, functions and/or terms between apparatus embodiments and method embodiments may be referred to each other.
In the embodiment of the present application, at least one may also be described as one or more, and a plurality may be two, three, four or more, and the present application is not limited thereto.
In the embodiment of the application, "/" can indicate that the related objects are in an OR relationship, for example, A/B can indicate A or B, and/or can be used for describing that the related objects have three relationships, for example, A and/or B, and can indicate that A exists alone, A exists together with B, and B exists alone, wherein A and B can be singular or plural. In order to facilitate description of the technical solution of the embodiments of the present application, in the embodiments of the present application, the words "first", "second", etc. may be used to distinguish between technical features that are the same or similar in function. The terms "first," "second," and the like do not necessarily denote any order of quantity or order of execution, nor do the terms "first," "second," and the like. In embodiments of the application, the words "exemplary" or "such as" are used to mean examples, illustrations, or descriptions, and any embodiment or design described as "exemplary" or "such as" should not be construed as preferred or advantageous over other embodiments or designs. The use of the word "exemplary" or "such as" is intended to present the relevant concepts in a concrete fashion to facilitate understanding.
It will be apparent to those skilled in the art that various modifications and variations can be made to the present application without departing from the scope of the application. Thus, it is intended that the present application also include such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.