WO2022089335A1 - 通信方法、装置及系统 - Google Patents

通信方法、装置及系统 Download PDF

Info

Publication number
WO2022089335A1
WO2022089335A1 PCT/CN2021/125901 CN2021125901W WO2022089335A1 WO 2022089335 A1 WO2022089335 A1 WO 2022089335A1 CN 2021125901 W CN2021125901 W CN 2021125901W WO 2022089335 A1 WO2022089335 A1 WO 2022089335A1
Authority
WO
WIPO (PCT)
Prior art keywords
parameter
candidate set
value
dci
terminal type
Prior art date
Application number
PCT/CN2021/125901
Other languages
English (en)
French (fr)
Inventor
吕永霞
王婷
王君
马江镭
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2022089335A1 publication Critical patent/WO2022089335A1/zh
Priority to US18/309,104 priority Critical patent/US20230319860A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/51—Allocation or scheduling criteria for wireless resources based on terminal or device properties
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0023—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the signalling
    • H04L1/0026—Transmission of channel quality indication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H04W72/232—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the physical layer, e.g. DCI signalling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
    • H04W72/542—Allocation or scheduling criteria for wireless resources based on quality criteria using measured or perceived quality
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/51—Allocation or scheduling criteria for wireless resources based on terminal or device properties
    • H04W72/512—Allocation or scheduling criteria for wireless resources based on terminal or device properties for low-latency requirements, e.g. URLLC
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/535—Allocation or scheduling criteria for wireless resources based on resource usage policies
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present invention relates to the field of communication technologies, and in particular, to a communication method, device and system.
  • the network device can configure multiple RRC parameters for the terminal device through radio resource control (radio resource control, RRC) signaling, so that the terminal device can communicate according to the multiple RRC parameters.
  • RRC radio resource control
  • the network device can schedule RRC signaling to send multiple RRC parameters to the terminal device through scheduling at the physical layer, for example, by controlling the sending and receiving of downlink control information (DCI) and the sending and receiving of data channels.
  • DCI downlink control information
  • the network device needs to The complete set of values of each RRC parameter is sent to the terminal device, resulting in a large RRC signaling overhead, a large storage overhead of the terminal device, and a large power consumption of the terminal device.
  • the network equipment schedules RRC signaling or data signals by sending DCI to the terminal equipment
  • the format of the DCI is a fixed format pre-specified by the communication protocol
  • the signaling overhead of the DCI is relatively large, resulting in low spectral efficiency of the communication system.
  • the power consumption of the terminal equipment is large.
  • the purpose of this application is to provide a communication method, device and system, which can improve the need for network equipment to send the complete set of values of each RRC parameter to the terminal equipment when configuring multiple RRC parameters for the terminal equipment, resulting in
  • the RRC signaling overhead is relatively large, the storage overhead of the terminal device is relatively large, and the power consumption of the terminal device is also relatively large.
  • an embodiment of the present application provides a communication method, the method includes: a terminal device determines a first value candidate set; the first value candidate set corresponds to a terminal type of the terminal device; the first value candidate set includes A candidate set of values of radio resource control RRC parameters corresponding to the terminal type; the terminal device receives the first value from the network device; wherein, the first value includes a group of RRC parameter values in the first candidate set of values; the terminal device Communicate according to the first value.
  • the network device can determine the first value for the terminal device from the first value candidate set, thereby preventing the network device from using each RRC parameter
  • the complete set of values is sent to the terminal equipment, which reduces the RRC signaling overhead, reduces the storage overhead of the terminal equipment, and reduces the power consumption of the terminal equipment.
  • the types of RRC parameters corresponding to the terminal type include one or more of the following: configuration parameters for data transmission, configuration parameters for channel state information CSI measurement feedback, configuration parameters for initial access, mobile configuration parameters for power control, configuration parameters for power control, and configuration parameters for beam management.
  • the RRC parameter value candidate set is used to indicate the configuration mode of the RRC parameter; wherein, the configuration mode includes a configuration parameter field, and the configuration parameter field includes configuration parameters of the configuration mode; or, the configuration mode includes configuration parameters.
  • the terminal device receives the first value candidate set from the network device.
  • the method before the terminal device receives the first value candidate set from the network device, the method further includes:
  • the terminal device sends the first request information to the network device, wherein the first request information is used to request a value candidate set of the RRC parameter corresponding to the terminal type.
  • the terminal device sends the first feature information to the network device, wherein the first feature information is used to indicate the terminal type.
  • the network device may determine the first value candidate set corresponding to the terminal type of the terminal device according to the first request information or the first feature information sent by the terminal device, and send the first value candidate set For the terminal device, a feasible solution is provided for the terminal device to determine the first value candidate set.
  • the types of RRC parameters corresponding to the eMBB include data transmission configuration parameters, channel state information CSI measurement feedback configuration parameters, initial access configuration parameters, mobile characteristic configuration parameters, power control configuration parameters and beam management configuration parameters; and/or; when the terminal type is an ultra-reliable low-latency communication device URLLC, the type of RRC parameters corresponding to the URLLC includes data transmission configuration parameters, channel Configuration parameters of status information CSI measurement feedback and configuration parameters of beam management; and/or; when the terminal type is IoT device IoT, the types of RRC parameters corresponding to IoT include configuration parameters for data transmission, configuration parameters for initial access, Mobility configuration parameters; and/or; when the terminal type is customer premise equipment CPE, the types of RRC parameters corresponding to the CPE include configuration parameters for data transmission and configuration parameters for channel state information CSI measurement feedback.
  • the terminal type is an enhanced mobile broadband device eMBB
  • the types of RRC parameters corresponding to the eMBB include data transmission configuration parameters, channel state information CSI measurement feedback configuration parameters, initial access configuration parameters, mobile
  • the type of RRC parameters corresponding to the terminal type can be determined according to the terminal type, so as to realize customization of the RRC parameters of the terminal type, and reduce signaling overhead while meeting the communication requirements of the terminal device.
  • the candidate set of subcarrier spacing configuration parameters in the configuration parameters of data transmission are 15kHz, 30kHz, 120kHz, and 240kHz;
  • the configuration parameters for CSI measurement feedback The candidate sets for the value of the CSI reporting time domain configuration parameter are periodic reporting, aperiodic reporting, and semi-persistent reporting;
  • the candidate sets for the value of the beam failure recovery timing parameter in the configuration parameters of beam management are 10ms, 20ms, 40ms, 60ms, 80ms, 100ms, 150ms, 200ms; and/or;
  • the candidate set of subcarrier spacing configuration parameters in the configuration parameters of data transmission is 30kHz, 60kHz, 120kHz;
  • the candidate set of the value of the CSI reporting time domain configuration parameter in the configuration parameters of the CSI measurement feedback is aperiodic reporting;
  • the candidate set of RRC parameter values corresponding to the terminal type can be determined according to the terminal type, so as to realize the customization of the candidate value set of RRC parameters of the terminal type, so as to meet the communication requirements of the terminal equipment and reduce signaling overhead.
  • the terminal type is determined according to one or more of the following factors: service type, mobility, transmission delay requirement, channel environment, reliability requirement, coverage requirement, and communication scenario.
  • the network device and/or the terminal device may determine the terminal type based on the above factors, so as to determine the RRC parameters for the terminal type that meet the communication requirements, thereby reducing signaling overhead.
  • an embodiment of the present application provides a terminal device, where the terminal device can implement the functions performed by the terminal device in the first aspect or a possible design of the first aspect, and the functions can be implemented by executing corresponding software through hardware.
  • the hardware or software includes one or more modules corresponding to the above functions. For example, processing modules and transceiver modules.
  • a processing module configured to determine a first value candidate set; the first value candidate set corresponds to the terminal type of the terminal device; the first value candidate set includes a value candidate set of radio resource control RRC parameters corresponding to the terminal type; sending and receiving The module is configured to receive the first value from the network device; wherein the first value includes a set of RRC parameter values in the first value candidate set; the processing module is configured to communicate according to the first value.
  • the types of RRC parameters corresponding to the terminal type include one or more of the following: configuration parameters for data transmission, configuration parameters for channel state information CSI measurement feedback, configuration parameters for initial access, mobile configuration parameters for power control, configuration parameters for power control, and configuration parameters for beam management.
  • the RRC parameter value candidate set is used to indicate the configuration mode of the RRC parameter; wherein, the configuration mode includes a configuration parameter field, and the configuration parameter field includes configuration parameters of the configuration mode; or, the configuration mode includes configuration parameters.
  • the transceiver module is further configured to receive the first value candidate set from the network device.
  • the transceiver module before receiving the first value candidate set from the network device, is also used to send first request information to the network device; wherein the first request information is used to request the RRC parameter corresponding to the terminal type. Value candidate set.
  • the transceiver module is further configured to send the first characteristic information to the network device, wherein the first characteristic information is used to indicate the terminal type.
  • the types of RRC parameters corresponding to the eMBB include data transmission configuration parameters, channel state information CSI measurement feedback configuration parameters, initial access configuration parameters, mobile characteristic configuration parameters, power control configuration parameters and beam management configuration parameters; and/or; when the terminal type is an ultra-reliable low-latency communication device URLLC, the type of RRC parameters corresponding to the URLLC includes data transmission configuration parameters, channel Configuration parameters of status information CSI measurement feedback and configuration parameters of beam management; and/or; when the terminal type is IoT device IoT, the types of RRC parameters corresponding to IoT include configuration parameters for data transmission, configuration parameters for initial access, Mobility configuration parameters; and/or; when the terminal type is customer premise equipment CPE, the types of RRC parameters corresponding to the CPE include configuration parameters for data transmission and configuration parameters for channel state information CSI measurement feedback.
  • the terminal type is an enhanced mobile broadband device eMBB
  • the types of RRC parameters corresponding to the eMBB include data transmission configuration parameters, channel state information CSI measurement feedback configuration parameters, initial access configuration parameters, mobile
  • the candidate set of subcarrier spacing configuration parameters in the configuration parameters of data transmission are 15kHz, 30kHz, 120kHz, and 240kHz;
  • the configuration parameters for CSI measurement feedback The candidate sets for the value of the CSI reporting time domain configuration parameter are periodic reporting, aperiodic reporting, and semi-persistent reporting;
  • the candidate sets for the value of the beam failure recovery timing parameter in the configuration parameters of beam management are 10ms, 20ms, 40ms, 60ms, 80ms, 100ms, 150ms, 200ms; and/or;
  • the candidate set of subcarrier spacing configuration parameters in the configuration parameters of data transmission is 30kHz, 60kHz, 120kHz;
  • the candidate set of the value of the CSI reporting time domain configuration parameter in the configuration parameters of the CSI measurement feedback is aperiodic reporting;
  • the terminal type is determined according to one or more of the following factors: service type, mobility, transmission delay requirement, channel environment, reliability requirement, coverage requirement, and communication scenario.
  • an embodiment of the present application provides a terminal device, where the terminal device may be a terminal device or a chip or a system-on-chip in the terminal device.
  • the terminal device can implement the functions performed by the terminal device in the above aspects or possible designs, and the functions can be implemented by hardware.
  • the terminal device may include: a transceiver and a processor. The transceiver and the processor may be used to support the terminal device to implement the functions involved in the first aspect or any possible design of the first aspect.
  • the processor is used to determine the first value candidate set; the first value candidate set corresponds to the terminal type of the terminal device; the first value candidate set includes the value candidate set of the radio resource control RRC parameter corresponding to the terminal type;
  • the processor is configured to receive the first value from the network device; wherein the first value includes a set of RRC parameter values in the first value candidate set; the processor is configured to communicate according to the first value.
  • the terminal device may further include a memory, which is used for storing necessary computer-executed instructions and data of the terminal device. When the terminal device is running, the transceiver and the processor execute the computer-executed instructions stored in the memory, so that the terminal device executes the communication method described in the first aspect or any possible design of the first aspect .
  • an embodiment of the present application provides a communication method, the method comprising: a network device determining a first value; the network device sending the first value to a terminal device; wherein the first value includes a first value candidate A set of RRC parameter values in the set; the first value candidate set corresponds to the terminal type of the terminal device; the first value candidate set includes a value candidate set of RRC parameters corresponding to the terminal type.
  • the network device can determine the first value for the terminal device from the first value candidate set, thereby preventing the network device from using each RRC parameter
  • the complete set of values is sent to the terminal equipment, which reduces the RRC signaling overhead, reduces the storage overhead of the terminal equipment, and reduces the power consumption of the terminal equipment.
  • the types of RRC parameters corresponding to the terminal type include one or more of the following: configuration parameters for data transmission, configuration parameters for channel state information CSI measurement feedback, configuration parameters for initial access, mobile configuration parameters for power control, configuration parameters for power control, and configuration parameters for beam management.
  • the RRC parameter value candidate set is used to indicate the configuration mode of the RRC parameter; wherein, the configuration mode includes a configuration parameter field, and the configuration parameter field includes configuration parameters of the configuration mode; or, the configuration mode includes configuration parameters.
  • the network device sends the first value candidate set to the terminal device.
  • the method before the network device sends the first value candidate set to the terminal device, the method further includes:
  • the network device receives the first request information from the terminal device; wherein, the first request information is used to request the value candidate set of the RRC parameter corresponding to the terminal type.
  • the network device receives the first feature information from the terminal device; wherein the first feature information is used to indicate the terminal type.
  • the network device may determine the first value candidate set corresponding to the terminal type of the terminal device according to the first request information or the first feature information sent by the terminal device, and send the first value candidate set For the terminal device, a feasible solution is provided for the terminal device to determine the first value candidate set.
  • the types of RRC parameters corresponding to the eMBB include data transmission configuration parameters, channel state information CSI measurement feedback configuration parameters, initial access configuration parameters, mobile characteristic configuration parameters, power control configuration parameters and beam management configuration parameters; and/or; when the terminal type is an ultra-reliable low-latency communication device URLLC, the type of RRC parameters corresponding to the URLLC includes data transmission configuration parameters, channel Configuration parameters of status information CSI measurement feedback and configuration parameters of beam management; and/or; when the terminal type is IoT device IoT, the types of RRC parameters corresponding to IoT include configuration parameters for data transmission, configuration parameters for initial access, Mobility configuration parameters; and/or; when the terminal type is customer premise equipment CPE, the types of RRC parameters corresponding to the CPE include configuration parameters for data transmission and configuration parameters for channel state information CSI measurement feedback.
  • the terminal type is an enhanced mobile broadband device eMBB
  • the types of RRC parameters corresponding to the eMBB include data transmission configuration parameters, channel state information CSI measurement feedback configuration parameters, initial access configuration parameters, mobile
  • the type of RRC parameters corresponding to the terminal type can be determined according to the terminal type, so as to realize customization of the RRC parameters of the terminal type, and reduce signaling overhead while meeting the communication requirements of the terminal device.
  • the candidate set of subcarrier spacing configuration parameters in the configuration parameters of data transmission are 15kHz, 30kHz, 120kHz, and 240kHz;
  • the configuration parameters for CSI measurement feedback The candidate sets for the value of the CSI reporting time domain configuration parameter are periodic reporting, aperiodic reporting, and semi-persistent reporting;
  • the candidate sets for the value of the beam failure recovery timing parameter in the configuration parameters of beam management are 10ms, 20ms, 40ms, 60ms, 80ms, 100ms, 150ms, 200ms; and/or;
  • the candidate set of subcarrier spacing configuration parameters in the configuration parameters of data transmission is 30kHz, 60kHz, 120kHz;
  • the candidate set of the value of the CSI reporting time domain configuration parameter in the configuration parameters of the CSI measurement feedback is aperiodic reporting;
  • the candidate set of RRC parameter values corresponding to the terminal type can be determined according to the terminal type, so as to realize the customization of the candidate value set of RRC parameters of the terminal type, so as to meet the communication requirements of the terminal equipment and reduce signaling overhead.
  • the terminal type is determined according to one or more of the following factors: service type, mobility, transmission delay requirement, channel environment, reliability requirement, coverage requirement, and communication scenario.
  • the network device and/or the terminal device may determine the terminal type based on the above factors, so as to determine the RRC parameters for the terminal type that meet the communication requirements, thereby reducing signaling overhead.
  • an embodiment of the present application provides a network device, where the network device can implement the functions performed by the network device in the fourth aspect or a possible design of the fourth aspect, and the functions can be implemented by executing corresponding software through hardware.
  • the hardware or software includes one or more modules corresponding to the above functions. For example, a processing module and a transceiver module, the processing module is used to determine the first value; the transceiver module is used to send the first value to the terminal device; wherein the first value includes a group of RRCs in the first value candidate set parameter value; the first value candidate set corresponds to the terminal type of the terminal device; the first value candidate set includes the value candidate set of the radio resource control RRC parameter corresponding to the terminal type.
  • the types of RRC parameters corresponding to the terminal type include one or more of the following: configuration parameters for data transmission, configuration parameters for channel state information CSI measurement feedback, configuration parameters for initial access, mobile configuration parameters for power control, configuration parameters for power control, and configuration parameters for beam management.
  • the RRC parameter value candidate set is used to indicate the configuration mode of the RRC parameter; wherein, the configuration mode includes a configuration parameter field, and the configuration parameter field includes configuration parameters of the configuration mode; or, the configuration mode includes configuration parameters.
  • the transceiver module is further configured to send the first value candidate set to the terminal device.
  • the transceiver module before sending the first value candidate set to the terminal device, is also used to receive first request information from the terminal device; wherein, the first request information is used to request the RRC parameter corresponding to the terminal type. Value candidate set.
  • the transceiver module is further configured to receive first feature information from the terminal device, wherein the first feature information is used to indicate the terminal type.
  • the types of RRC parameters corresponding to the eMBB include data transmission configuration parameters, channel state information CSI measurement feedback configuration parameters, initial access configuration parameters, mobile characteristic configuration parameters, power control configuration parameters and beam management configuration parameters; and/or; when the terminal type is an ultra-reliable low-latency communication device URLLC, the type of RRC parameters corresponding to the URLLC includes data transmission configuration parameters, channel Configuration parameters of status information CSI measurement feedback and configuration parameters of beam management; and/or; when the terminal type is IoT device IoT, the types of RRC parameters corresponding to IoT include configuration parameters for data transmission, configuration parameters for initial access, Mobility configuration parameters; and/or; when the terminal type is customer premise equipment CPE, the types of RRC parameters corresponding to the CPE include configuration parameters for data transmission and configuration parameters for channel state information CSI measurement feedback.
  • the terminal type is an enhanced mobile broadband device eMBB
  • the types of RRC parameters corresponding to the eMBB include data transmission configuration parameters, channel state information CSI measurement feedback configuration parameters, initial access configuration parameters, mobile
  • the candidate set of subcarrier spacing configuration parameters in the configuration parameters of data transmission are 15kHz, 30kHz, 120kHz, and 240kHz;
  • the configuration parameters for CSI measurement feedback The candidate sets for the value of the CSI reporting time domain configuration parameter are periodic reporting, aperiodic reporting, and semi-persistent reporting;
  • the candidate sets for the value of the beam failure recovery timing parameter in the configuration parameters of beam management are 10ms, 20ms, 40ms, 60ms, 80ms, 100ms, 150ms, 200ms; and/or;
  • the candidate set of subcarrier spacing configuration parameters in the configuration parameters of data transmission is 30kHz, 60kHz, 120kHz;
  • the candidate set of the value of the CSI reporting time domain configuration parameter in the configuration parameters of the CSI measurement feedback is aperiodic reporting;
  • the terminal type is determined according to one or more of the following factors: service type, mobility, transmission delay requirement, channel environment, reliability requirement, coverage requirement, and communication scenario.
  • an embodiment of the present application provides a network device, where the network device may be a network device or a chip or a system-on-a-chip in the network device.
  • the network device can implement the functions performed by the network device in the above aspects or possible designs, and the functions can be implemented by hardware.
  • the network device may include: a transceiver and a processor. The transceiver and the processor may be used to support the network device to implement the functions involved in the fourth aspect or any possible design of the fourth aspect.
  • the processor is used to determine the first value; the transceiver is used to send the first value to the terminal device; wherein the first value includes a set of RRC parameter values in the first value candidate set; the first value candidate set Corresponding to the terminal type of the terminal device; the first value candidate set includes the value candidate set of the radio resource control RRC parameter corresponding to the terminal type.
  • the network device may further include a memory for storing necessary computer-executed instructions and data of the network device. When the network device is running, the transceiver and the processor execute the computer-executable instructions stored in the memory, so that the network device executes the communication method described in the fourth aspect or any possible design of the fourth aspect .
  • an embodiment of the present application provides a communication method, the method includes: a terminal device receives first downlink control information DCI from a network device; the first DCI includes values of multiple DCI parameters; the first DCI includes The DCI parameter corresponding to the terminal type of the terminal device; the candidate set of DCI parameter values corresponds to the terminal type; the candidate set includes at least one value of the DCI parameter corresponding to the terminal type; the terminal device communicates according to the first DCI.
  • the seventh aspect by determining the DCI corresponding to the terminal device for the terminal device in a customized manner according to the terminal type, the signaling overhead of the DCI can be reduced, the spectral efficiency of the communication system can be improved, and the power consumption of the terminal device can be reduced at the same time.
  • the terminal device receiving the first DCI from the network device includes: the terminal device determines the first DCI format; wherein the first DCI format corresponds to the terminal type; and the terminal device receives the data from the network according to the first DCI format. The first DCI of the device.
  • the terminal device can receive DCI from the network device according to the DCI format corresponding to the terminal device, thereby improving communication reliability.
  • the terminal device determines the candidate set of DCI parameter values according to the correspondence between the DCI format and the candidate set of DCI parameter values, and the first DCI format.
  • the terminal device can parse the first DCI sent by the network device according to the correspondence between the DCI format and the candidate set of DCI parameter values.
  • the method before the terminal device receives the first DCI from the network device, the method further includes: the terminal device receives indication information from the network device; wherein the indication information is used to indicate the DCI parameter corresponding to the terminal type and the value of the DCI parameter. A candidate set of values.
  • the terminal device can determine the DCI parameter corresponding to the terminal type and a candidate set of DCI parameter values according to the indication information sent by the network device, and then parse the received first DCI.
  • the method before the terminal device receives the indication information from the network device, the method further includes: the terminal device sends second request information to the network device; wherein the second request information is used to request DCI parameters and DCI parameters corresponding to the terminal type. A candidate set of parameter values.
  • the terminal device sends second feature information to the network device; wherein the second feature information is used to indicate the terminal type.
  • the terminal device can send the second request information or the second feature information to the network device, so that the network device can determine the terminal type of the terminal device for the terminal device according to the second request information or the second feature information Corresponding DCI parameters and candidate sets of DCI parameter values.
  • the DCI parameters corresponding to eMBB include time domain resource allocation, frequency domain resource allocation, bandwidth part BWP indication, modulation and coding mode MCS, new data indication, redundancy redundant version, HARQ process number, HARQ timing, transmission power control TPC command, antenna port, precoding and number of layers, sounding reference signal SRS request, channel state information CSI request; and/or;
  • the terminal type is When the ultra-reliable and low-latency communication device URLLC is used, the DCI parameters corresponding to URLLC include time domain resource indication, frequency domain resource indication, modulation and coding mode MCS, new data indication, hybrid automatic repeat request HARQ process number, transmission power control command, Sounding reference signal SRS request, channel state information CSI request; and/or;
  • the DCI parameters corresponding to IoT include frequency domain resource indication, modulation and coding mode MCS, hybrid automatic repeat request HARQ process and/or;
  • DCI parameters corresponding to the terminal type can be determined according to the terminal type, so as to realize the DCI customization of the terminal type, and reduce signaling overhead while meeting the communication requirements of the terminal device.
  • the terminal type is enhanced mobile broadband equipment eMBB
  • the number of bits corresponding to the candidate set of the value of the MCS parameter is 5; the number of bits corresponding to the candidate set of the value of the HARQ process number parameter is 4;
  • the terminal type is an ultra-reliable low-latency communication device URLLC
  • the number of bits corresponding to the candidate set of the value of the MCS parameter is 2 or 3
  • the number of bits corresponding to the candidate set of the value of the HARQ process number parameter is 1
  • the number of bits corresponding to the candidate set of the value of the sounding reference signal SRS request parameter is 1
  • the number of bits corresponding to the candidate set of the value of the channel state information CSI request parameter is 1
  • the terminal type is the Internet of Things
  • the device is IoT
  • the number of bits corresponding to the candidate set of the value of the MCS parameter is 2 or 3
  • the number of bits corresponding to the candidate set of the value of the HARQ process ID parameter is 1 or 2
  • a candidate set of DCI parameter values corresponding to the terminal type can be determined according to the terminal type, so as to realize the customization of the candidate set of DCI parameter values of the terminal type, so as to meet the communication requirements of the terminal equipment and reduce the Signaling overhead.
  • the DCI format corresponding to the eMBB is format 1, wherein the DCI parameters corresponding to format 1 and the candidate sets of the values of the DCI parameters are as follows: Modulation and coding mode MCS The number of bits corresponding to the candidate set of the value of the parameter is 5; the number of bits corresponding to the candidate set of the value of the HARQ process ID parameter of the hybrid automatic repeat request is 4; and/or; when the terminal type is ultra-reliable and low-latency communication
  • the DCI format corresponding to URLLC is format 2, wherein the DCI parameter corresponding to format 2 and the candidate set of DCI parameter values are as follows: 3; the number of bits corresponding to the candidate set of the value of the HARQ process number parameter of the hybrid automatic repeat request is 1; the number of bits corresponding to the candidate set of the value of the sounding reference signal SRS request parameter is 1, and the The number of bits corresponding to the candidate set of values is 1
  • the DCI format corresponding to the terminal type can be determined according to the terminal type, so as to realize the customization of the DCI format of the terminal type, so that the terminal device can receive DCI according to the DCI format corresponding to the terminal device. Reduce signaling overhead.
  • the terminal type is determined according to one or more of the following factors: service type, mobility, transmission delay requirement, channel environment, reliability requirement, coverage requirement, and communication scenario.
  • the network device and/or the terminal device may determine the terminal type based on the above factors, so as to determine the DCI that meets the communication requirement for the terminal type, thereby reducing signaling overhead.
  • an embodiment of the present application provides a terminal device, where the terminal device can implement the functions performed by the terminal device in the seventh aspect or possible designs of the seventh aspect, and the functions can be implemented by executing corresponding software through hardware.
  • the hardware or software includes one or more modules corresponding to the above functions. For example, transceiver modules and processing modules.
  • the transceiver module is used to receive the first downlink control information DCI from the network device; the first DCI includes the values of multiple DCI parameters; the DCI parameters included in the first DCI correspond to the terminal type of the terminal device; the values of the DCI parameters
  • the candidate set corresponds to the terminal type; the candidate set includes at least one value of the DCI parameter corresponding to the terminal type; the processing module is configured to communicate according to the first DCI.
  • the processing module is further configured to determine the first DCI format; wherein the first DCI format corresponds to the terminal type; the transceiver module is further configured to receive the first DCI from the network device according to the first DCI format .
  • the processing module is further configured to determine the candidate set of the value of the DCI parameter according to the corresponding relationship between the DCI format and the candidate set of the value of the DCI parameter, and the first DCI format.
  • the transceiver module is also used for the terminal device to receive indication information from the network device; wherein the indication information is used to indicate the DCI parameter corresponding to the terminal type and a candidate set of DCI parameter values.
  • the transceiver module before the transceiver module receives the indication information from the network device, it is also used by the terminal device to send second request information to the network device; wherein the second request information is used to request DCI parameters and DCI parameters corresponding to the terminal type.
  • the candidate set of values before the transceiver module receives the indication information from the network device, it is also used by the terminal device to send second request information to the network device; wherein the second request information is used to request DCI parameters and DCI parameters corresponding to the terminal type.
  • the transceiver module is further configured to send second feature information to the network device, wherein the second feature information is used to indicate the terminal type.
  • the DCI parameters corresponding to eMBB include time domain resource allocation, frequency domain resource allocation, bandwidth part BWP indication, modulation and coding mode MCS, new data indication, redundancy redundant version, HARQ process number, HARQ timing, transmission power control TPC command, antenna port, precoding and number of layers, sounding reference signal SRS request, channel state information CSI request; and/or;
  • the terminal type is When the ultra-reliable and low-latency communication device URLLC is used, the DCI parameters corresponding to URLLC include time domain resource indication, frequency domain resource indication, modulation and coding mode MCS, new data indication, hybrid automatic repeat request HARQ process number, transmission power control command, Sounding reference signal SRS request, channel state information CSI request; and/or;
  • the DCI parameters corresponding to IoT include frequency domain resource indication, modulation and coding mode MCS, hybrid automatic repeat request HARQ process and/or;
  • the terminal type is enhanced mobile broadband equipment eMBB
  • the number of bits corresponding to the candidate set of the value of the MCS parameter is 5; the number of bits corresponding to the candidate set of the value of the HARQ process number parameter is 4;
  • the terminal type is an ultra-reliable low-latency communication device URLLC
  • the number of bits corresponding to the candidate set of the value of the MCS parameter is 2 or 3
  • the number of bits corresponding to the candidate set of the value of the HARQ process number parameter is 1
  • the number of bits corresponding to the candidate set of the value of the sounding reference signal SRS request parameter is 1
  • the number of bits corresponding to the candidate set of the value of the channel state information CSI request parameter is 1
  • the terminal type is the Internet of Things
  • the device is IoT
  • the number of bits corresponding to the candidate set of the value of the MCS parameter is 2 or 3
  • the number of bits corresponding to the candidate set of the value of the HARQ process ID parameter is 1 or 2
  • the DCI format corresponding to the eMBB is format 1, wherein the DCI parameters corresponding to format 1 and the candidate sets of the values of the DCI parameters are as follows: Modulation and coding mode MCS The number of bits corresponding to the candidate set of the value of the parameter is 5; the number of bits corresponding to the candidate set of the value of the HARQ process ID parameter of the hybrid automatic repeat request is 4; and/or; when the terminal type is ultra-reliable and low-latency communication
  • the DCI format corresponding to URLLC is format 2, wherein the DCI parameter corresponding to format 2 and the candidate set of DCI parameter values are as follows: 3; the number of bits corresponding to the candidate set of the value of the HARQ process number parameter of the hybrid automatic repeat request is 1; the number of bits corresponding to the candidate set of the value of the sounding reference signal SRS request parameter is 1, and the The number of bits corresponding to the candidate set of values is 1
  • the terminal type is determined according to one or more of the following factors: service type, mobility, transmission delay requirement, channel environment, reliability requirement, coverage requirement, and communication scenario.
  • an embodiment of the present application provides a terminal device, where the terminal device may be a terminal device or a chip or a system-on-a-chip in the terminal device.
  • the terminal device can implement the functions performed by the terminal device in the above aspects or possible designs, and the functions can be implemented by hardware.
  • the terminal device may include: a transceiver and a processor. The transceiver and the processor may be used to support the terminal device to implement the functions involved in the seventh aspect or any possible design of the seventh aspect.
  • the transceiver is used to receive the first downlink control information DCI from the network device; the first DCI includes the values of multiple DCI parameters; the DCI parameters included in the first DCI correspond to the terminal type of the terminal device; the values of the DCI parameters
  • the candidate set corresponds to the terminal type; the candidate set includes at least one value of the DCI parameter corresponding to the terminal type; the processor is configured to communicate according to the first DCI.
  • the terminal device may further include a memory, which is used for storing necessary computer-executed instructions and data of the terminal device. When the terminal device is running, the transceiver and the processor execute the computer-executable instructions stored in the memory, so that the terminal device executes the communication method described in the seventh aspect or any possible design of the seventh aspect .
  • an embodiment of the present application provides a communication method, the method includes: a network device determines a first DCI; the first DCI includes values of multiple DCI parameters; the DCI parameters included in the first DCI are related to the terminal of the terminal device The type corresponds; the candidate set of DCI parameter values corresponds to the terminal type; the candidate set includes at least one value of the DCI parameter corresponding to the terminal type; the network device sends the first DCI to the terminal device.
  • the signaling overhead of the DCI can be reduced, the spectral efficiency of the communication system can be improved, and the power consumption of the terminal device can be reduced.
  • sending the first DCI from the network device to the terminal device includes: the network device sends the first DCI format to the terminal device; so that the terminal device receives the first DCI from the network device according to the first DCI format; wherein , the first DCI format corresponds to the terminal type.
  • the terminal device can receive DCI from the network device according to the DCI format corresponding to the terminal device, thereby improving communication reliability.
  • the method before the network device sends the first DCI to the terminal device, the method further includes: the network device sends indication information to the terminal device; wherein the indication information is used to indicate the DCI parameter corresponding to the terminal type and the value of the DCI parameter. candidate set.
  • the terminal device can determine the DCI parameter corresponding to the terminal type and a candidate set of DCI parameter values according to the indication information sent by the network device, and then parse the received first DCI.
  • the method before the network device sends the indication information to the terminal device, the method further includes: the network device receives second request information from the terminal device; wherein the second request information is used to request DCI parameters and DCI parameters corresponding to the terminal type. A candidate set of parameter values.
  • the network device receives second feature information from the terminal device; wherein the second feature information is used to indicate the terminal type.
  • the terminal device can send the second request information or the second feature information to the network device, so that the network device can determine the terminal type of the terminal device for the terminal device according to the second request information or the second feature information Corresponding DCI parameters and candidate sets of DCI parameter values.
  • the DCI parameters corresponding to eMBB include time domain resource allocation, frequency domain resource allocation, bandwidth part BWP indication, modulation and coding mode MCS, new data indication, redundancy redundant version, HARQ process number, HARQ timing, transmission power control TPC command, antenna port, precoding and number of layers, sounding reference signal SRS request, channel state information CSI request; and/or;
  • the terminal type is When the ultra-reliable and low-latency communication device URLLC is used, the DCI parameters corresponding to URLLC include time domain resource indication, frequency domain resource indication, modulation and coding mode MCS, new data indication, hybrid automatic repeat request HARQ process number, transmission power control command, Sounding reference signal SRS request, channel state information CSI request; and/or;
  • the DCI parameters corresponding to IoT include frequency domain resource indication, modulation and coding mode MCS, hybrid automatic repeat request HARQ process and/or;
  • DCI parameters corresponding to the terminal type can be determined according to the terminal type, so as to realize the DCI customization of the terminal type, and reduce signaling overhead while meeting the communication requirements of the terminal device.
  • the terminal type is enhanced mobile broadband equipment eMBB
  • the number of bits corresponding to the candidate set of the value of the MCS parameter is 5; the number of bits corresponding to the candidate set of the value of the HARQ process number parameter is 4;
  • the terminal type is an ultra-reliable low-latency communication device URLLC
  • the number of bits corresponding to the candidate set of the value of the MCS parameter is 2 or 3
  • the number of bits corresponding to the candidate set of the value of the HARQ process number parameter is 1
  • the number of bits corresponding to the candidate set of the value of the sounding reference signal SRS request parameter is 1
  • the number of bits corresponding to the candidate set of the value of the channel state information CSI request parameter is 1
  • the terminal type is the Internet of Things
  • the device is IoT
  • the number of bits corresponding to the candidate set of the value of the MCS parameter is 2 or 3
  • the number of bits corresponding to the candidate set of the value of the HARQ process ID parameter is 1 or 2
  • a candidate set of DCI parameter values corresponding to the terminal type can be determined according to the terminal type, so as to realize the customization of the candidate set of DCI parameter values of the terminal type, so as to meet the communication requirements of the terminal equipment and reduce the Signaling overhead.
  • the DCI format corresponding to the eMBB is format 1, wherein the DCI parameters corresponding to format 1 and the candidate sets of the values of the DCI parameters are as follows: Modulation and coding mode MCS The number of bits corresponding to the candidate set of the value of the parameter is 5; the number of bits corresponding to the candidate set of the value of the HARQ process ID parameter of the hybrid automatic repeat request is 4; and/or; when the terminal type is ultra-reliable and low-latency communication
  • the DCI format corresponding to URLLC is format 2, wherein the DCI parameter corresponding to format 2 and the candidate set of DCI parameter values are as follows: 3; the number of bits corresponding to the candidate set of the value of the HARQ process number parameter of the hybrid automatic repeat request is 1; the number of bits corresponding to the candidate set of the value of the sounding reference signal SRS request parameter is 1, and the The number of bits corresponding to the candidate set of values is 1
  • the DCI format corresponding to the terminal type can be determined according to the terminal type, so as to realize the customization of the DCI format of the terminal type, so that the terminal device can receive DCI according to the DCI format corresponding to the terminal device. Reduce signaling overhead.
  • the terminal type is determined according to one or more of the following factors: service type, mobility, transmission delay requirement, channel environment, reliability requirement, coverage requirement, and communication scenario.
  • the network device and/or the terminal device may determine the terminal type based on the above factors, so as to determine the DCI that meets the communication requirement for the terminal type, thereby reducing signaling overhead.
  • an embodiment of the present application provides a network device.
  • the network device can implement the functions performed by the network device in the tenth aspect or a possible design of the tenth aspect, and the functions can be implemented by executing corresponding software through hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • a processing module and a transceiver module the processing module is used to determine the first DCI; the first DCI includes the values of multiple DCI parameters; the DCI parameters included in the first DCI correspond to the terminal types of the terminal equipment; the values of the DCI parameters
  • the candidate set corresponds to the terminal type; the candidate set includes at least one value of the DCI parameter corresponding to the terminal type; the transceiver module is configured to send the first DCI to the terminal device.
  • the transceiver module is also used for the network device to send the first DCI format to the terminal device; so that the terminal device receives the first DCI from the network device according to the first DCI format; wherein the first DCI format is the same as the first DCI format. corresponding to the terminal type.
  • the transceiver module before sending the first DCI to the terminal device, is also used to send indication information to the terminal device; wherein, the indication information is used to indicate the DCI parameter corresponding to the terminal type and the candidate set of the value of the DCI parameter. .
  • the transceiver module before sending the indication information to the terminal device, is also used to receive second request information from the terminal device; wherein, the second request information is used to request the DCI parameter corresponding to the terminal type and the acquisition of the DCI parameter.
  • a candidate set of values before sending the indication information to the terminal device, the transceiver module is also used to receive second request information from the terminal device; wherein, the second request information is used to request the DCI parameter corresponding to the terminal type and the acquisition of the DCI parameter.
  • the transceiver module is further configured to receive second feature information from the terminal device, wherein the second feature information is used to indicate the terminal type.
  • the DCI parameters corresponding to eMBB include time domain resource allocation, frequency domain resource allocation, bandwidth part BWP indication, modulation and coding mode MCS, new data indication, redundancy redundant version, HARQ process number, HARQ timing, transmission power control TPC command, antenna port, precoding and number of layers, sounding reference signal SRS request, channel state information CSI request; and/or;
  • the terminal type is When the ultra-reliable and low-latency communication device URLLC is used, the DCI parameters corresponding to URLLC include time domain resource indication, frequency domain resource indication, modulation and coding mode MCS, new data indication, hybrid automatic repeat request HARQ process number, transmission power control command, Sounding reference signal SRS request, channel state information CSI request; and/or;
  • the DCI parameters corresponding to IoT include frequency domain resource indication, modulation and coding mode MCS, hybrid automatic repeat request HARQ process and/or;
  • the terminal type is enhanced mobile broadband equipment eMBB
  • the number of bits corresponding to the candidate set of the value of the MCS parameter is 5; the number of bits corresponding to the candidate set of the value of the HARQ process number parameter is 4;
  • the terminal type is an ultra-reliable low-latency communication device URLLC
  • the number of bits corresponding to the candidate set of the value of the MCS parameter is 2 or 3
  • the number of bits corresponding to the candidate set of the value of the HARQ process number parameter is 1
  • the number of bits corresponding to the candidate set of the value of the sounding reference signal SRS request parameter is 1
  • the number of bits corresponding to the candidate set of the value of the channel state information CSI request parameter is 1
  • the terminal type is the Internet of Things
  • the device is IoT
  • the number of bits corresponding to the candidate set of the value of the MCS parameter is 2 or 3
  • the number of bits corresponding to the candidate set of the value of the HARQ process ID parameter is 1 or 2
  • the DCI format corresponding to the eMBB is format 1, wherein the DCI parameters corresponding to format 1 and the candidate sets of the values of the DCI parameters are as follows: Modulation and coding mode MCS The number of bits corresponding to the candidate set of the value of the parameter is 5; the number of bits corresponding to the candidate set of the value of the HARQ process ID parameter of the hybrid automatic repeat request is 4; and/or; when the terminal type is ultra-reliable and low-latency communication
  • the DCI format corresponding to URLLC is format 2, wherein the DCI parameter corresponding to format 2 and the candidate set of DCI parameter values are as follows: 3; the number of bits corresponding to the candidate set of the value of the HARQ process number parameter of the hybrid automatic repeat request is 1; the number of bits corresponding to the candidate set of the value of the sounding reference signal SRS request parameter is 1, and the The number of bits corresponding to the candidate set of values is 1
  • the terminal type is determined according to one or more of the following factors: service type, mobility, transmission delay requirement, channel environment, reliability requirement, coverage requirement, and communication scenario.
  • an embodiment of the present application provides a network device, where the network device may be a network device or a chip or a system-on-a-chip in the network device.
  • the network device can implement the functions performed by the network device in the above aspects or possible designs, and the functions can be implemented by hardware.
  • the network device may include: a transceiver and a processor. The transceiver and the processor may be used to support the network device to implement the functions involved in the tenth aspect or any possible design of the tenth aspect.
  • the processor is used to determine the first DCI; the first DCI includes the values of multiple DCI parameters; the DCI parameters included in the first DCI correspond to the terminal type of the terminal device; the candidate set of DCI parameter values corresponds to the terminal type; The candidate set includes at least one value of the DCI parameter corresponding to the terminal type; the transceiver is configured to send the first DCI to the terminal device.
  • the network device may further include a memory for storing necessary computer-executed instructions and data of the network device. When the network device is running, the transceiver and the processor execute the computer-executable instructions stored in the memory, so that the network device executes the communication method described in the tenth aspect or any possible design of the tenth aspect. .
  • the network device in the eleventh aspect and the twelfth aspect reference may be made to the behavior function of the network device in the communication method provided by the tenth aspect or any possible design of the tenth aspect.
  • a thirteenth aspect provides a communication device comprising one or more processors and one or more memories; the one or more memories are coupled to the one or more processors, and the one or more memories are used for Stores computer program code or computer instructions; when executed by one or more processors, the computer instructions cause the communication apparatus to perform the communication method as described in the first aspect or any possible design of the first aspect, or to perform the fourth aspect Or the communication method described in any possible design of the fourth aspect, or the communication method described in the seventh aspect or any possible design of the seventh aspect, or the tenth aspect or any of the tenth aspect. A possible design of the described communication method.
  • a fourteenth aspect provides a computer-readable storage medium, the computer-readable storage medium stores computer instructions or programs, and when the computer instructions or programs run on a computer, causes the computer to perform the first aspect or the first aspect
  • a fifteenth aspect provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the communication method as described in the first aspect or any possible design of the first aspect, or perform as The communication method described in the fourth aspect or any possible design of the fourth aspect, or the communication method described in the seventh aspect or any possible design of the seventh aspect, or the tenth aspect or the tenth aspect.
  • the communication method of any possible design of the aspect is not limited to be performed by the communication method described in the first aspect or any possible design of the first aspect, or perform as The communication method described in the fourth aspect or any possible design of the fourth aspect, or the communication method described in the seventh aspect or any possible design of the seventh aspect, or the tenth aspect or the tenth aspect.
  • a sixteenth aspect provides a communication device, the communication device includes a processor and a communication interface; the processor is used to read instructions, and when the communication device is a chip, it can execute any one of the first aspect or the first aspect
  • the communication method described in the possible design, or the communication method described in the fourth aspect or any possible design of the fourth aspect, or the communication method described in the seventh aspect or any possible design of the seventh aspect The communication method, or executing the communication method according to the tenth aspect or any possible design of the tenth aspect, when the communication device is a terminal device, it can execute the first aspect or any possible design of the first aspect.
  • the communication method described above or execute the communication method described in the seventh aspect or any possible design of the seventh aspect; when the communication device is a network device, it can execute the fourth aspect or any possible design of the fourth aspect. Design the communication method, or implement the communication method according to the tenth aspect or any possible design of the tenth aspect.
  • the technical effect brought by any one of the design methods in the thirteenth aspect to the sixteenth aspect can refer to the technical effect brought by any possible design of the above-mentioned first aspect, or refer to the above-mentioned fourth aspect.
  • a seventeenth aspect provides a communication system, the communication system comprising the terminal device according to any one of the second aspect to the third aspect and the network device according to any one of the fifth aspect to the sixth aspect, Or include the terminal device according to any one of the eighth aspect to the ninth aspect and the network device according to any one of the eleventh aspect to the twelfth aspect.
  • FIG. 1a is a schematic diagram of the composition of a communication system provided by an embodiment of the application.
  • FIG. 1b is a schematic diagram of a protocol stack of a terminal device and a network device provided by an embodiment of the application;
  • FIG. 1c is a schematic diagram of the composition of a communication system provided by an embodiment of the present application.
  • FIG. 2 is a schematic diagram of the composition of a communication device according to an embodiment of the present application.
  • 3a is a flowchart of a communication method provided by an embodiment of the present application.
  • 3b is a flowchart of a communication method provided by an embodiment of the present application.
  • 3c is a flowchart of a communication method provided by an embodiment of the present application.
  • FIG. 4 is a schematic diagram of a terminal type provided by an embodiment of the present application.
  • FIG. 5a is a flowchart of a communication method provided by an embodiment of the present application.
  • 5b is a flowchart of a communication method provided by an embodiment of the present application.
  • FIG. 5c is a flowchart of a communication method provided by an embodiment of the present application.
  • FIG. 6 is a schematic diagram of a DCI parameter provided by an embodiment of the present application.
  • FIG. 7 is a schematic diagram of a symbol provided in an embodiment of the present application.
  • FIG. 8 is a schematic diagram of the composition of a terminal device according to an embodiment of the present application.
  • FIG. 9 is a schematic diagram of the composition of a network device according to an embodiment of the present application.
  • the network device can configure multiple RRC parameters for the terminal device through radio resource control (radio resource control, RRC) signaling, so that the terminal device can communicate according to the multiple RRC parameters.
  • RRC radio resource control
  • the values of multiple RRC parameters carried in the RRC signaling are predetermined by the communication protocol, there are many RRC parameters, and there are also many values of the same RRC parameter.
  • each RRC parameter needs to indicate a value from the complete set of RRC parameter values and send it to the terminal device, resulting in high RRC signaling overhead, high storage overhead of the terminal device, and high power consumption of the terminal device.
  • the network device when the network device sends RRC parameters to the terminal device, it can schedule the RRC signaling to the terminal device through scheduling of the physical layer, for example, by controlling the sending and receiving of downlink control information (DCI) and the sending and receiving of data channels RRC parameters.
  • DCI downlink control information
  • the network device schedules RRC signaling by sending DCI to the terminal device since the format of the DCI is a fixed format pre-specified by the communication protocol, the signaling overhead of the DCI is relatively large, resulting in low spectral efficiency of the communication system and the terminal device. Power consumption is large.
  • an embodiment of the present application provides a communication method, the method includes: the terminal device determines a first value candidate set; the first value candidate set communicates with the terminal The terminal type of the device corresponds to; the first value candidate set includes a value candidate set of RRC parameters corresponding to the terminal type; the terminal device receives the first value from the network device; the first value includes a value in the first value candidate set.
  • the network device can determine the first value for the terminal device from the first value candidate set.
  • the RRC parameter indicates the first value from the complete set of values of the RRC parameter and sends it to the terminal device, thereby reducing the RRC signaling overhead, the storage overhead of the terminal device, and the power consumption of the terminal device.
  • an embodiment of the present application provides a communication method, the method includes: the terminal device receives a first DCI from a network device; the first DCI includes the values of multiple DCI parameters; the first DCI The DCI parameter included in the DCI corresponds to the terminal type of the terminal device; the candidate set of DCI parameter values corresponds to the terminal type; the candidate set includes at least one value of the DCI parameter corresponding to the terminal type; the terminal device communicates according to the first DCI.
  • the signaling overhead of the DCI can be reduced, the spectrum efficiency of the communication system can be improved, and the power consumption of the terminal device can be reduced at the same time.
  • the communication methods provided in the embodiments of the present application may be used in any communication system, and the communication system may be a third generation partnership project (3GPP) communication system, for example, a long term evolution (long term evolution, LTE) system , and can be fifth generation (5G) mobile communication systems, new radio (NR) systems, NR V2X systems, and can also be applied to LTE and 5G hybrid networking systems, or device-to-device ( device-to-device, D2D) communication system, machine to machine (M2M) communication system, Internet of Things (Internet of Things, IoT), frequency division duplex (frequency division duplex, FDD) system, time division duplex (time division duplex, TDD) systems, satellite communication systems, and other next-generation communication systems may also be non-3GPP communication systems without limitation.
  • 3GPP third generation partnership project
  • LTE long term evolution
  • NR new radio
  • NR V2X NR V2X
  • device-to-device device-to-device, D2D) communication system
  • the communication methods provided by the embodiments of the present application can be applied to various communication scenarios, for example, can be applied to one or more of the following communication scenarios: enhanced mobile broadband (enhanced mobile broadband, eMBB), ultra-reliable and low-latency communication (ultra-reliable and low-latency communication) reliable low latency communication (URLLC), machine type communication (MTC), internet of things (IoT), narrow band internet of things (NB-IoT), customer premises equipment (customer) premise equipment (CPE), augmented reality (AR), virtual reality (VR), massive machine type communications (mMTC), device to device (D2D), vehicle Networking (vehicle to everything, V2X), vehicle to vehicle (vehicle to vehicle, V2V), etc.
  • enhanced mobile broadband enhanced mobile broadband
  • eMBB enhanced mobile broadband
  • ultra-reliable and low-latency communication ultra-reliable and low-latency communication
  • reliable low latency communication URLLC
  • MTC machine type communication
  • IoT internet of things
  • IoT internet of thing, IoT
  • IoT may include one or more of NB-IoT, MTC, mMTC, etc., which is not limited.
  • the embodiments of the present application are applicable to both homogeneous network and heterogeneous network scenarios, and also have no restrictions on transmission points, which may be multi-point coordinated transmission between macro base stations and macro base stations, micro base stations and micro base stations, and macro base stations and micro base stations. , applicable to frequency division multiplexing system, time division multiplexing system, duplex system, access backhaul system, relay system, etc.
  • the embodiments of the present application are applicable to low-frequency scenarios (sub 6G), and are also applicable to high-frequency scenarios (above 6G), terahertz, optical communication, and the like.
  • eMBB may refer to a large-flow mobile broadband service such as three-dimensional (three-dimensional, 3D)/ultra-high-definition video.
  • eMBB can further improve performance such as network speed and user experience based on mobile broadband services. For example, when users watch 4K high-definition video, the peak network speed can reach 10Gbps.
  • URLLC can refer to services with high reliability, low latency, and extremely high availability. Specifically, URLLC can include the following communication scenarios and applications: industrial application and control, traffic safety and control, remote manufacturing, remote training, remote surgery, unmanned driving, industrial automation, security industry, etc.
  • MTC which can refer to low-cost, coverage-enhanced services, can also be referred to as M2M.
  • mMTC refers to large-scale IoT business.
  • NB-IoT can be a service with wide coverage, multiple connections, low speed, low cost, low power consumption, and excellent architecture.
  • NB-IoT can include smart water meters, smart parking, smart pet tracking, smart bicycles, smart smoke detectors, smart toilets, smart vending machines, and so on.
  • CPE can refer to a mobile signal access device that receives mobile signals and forwards them with wireless fidelity (WiFi) signals, or can refer to devices that convert high-speed 4G or 5G signals into WiFi signals, which can support more Internet access at the same time number of mobile terminals.
  • WiFi wireless fidelity
  • CPE can be widely used in wireless network access in rural areas, towns, hospitals, units, factories, communities, etc., which can save the cost of laying wired networks.
  • V2X can enable communication between vehicles, vehicles and network devices, and network devices and network devices, so as to obtain a series of traffic information such as real-time road conditions, road information, pedestrian information, etc., and provide in-vehicle entertainment information to improve driving safety. Reduce congestion and improve traffic efficiency.
  • FIG. 1a is a schematic diagram of a communication system provided by an embodiment of the present application. As shown in FIG. 1a, the communication system may include a terminal device and a network device.
  • the terminal equipment in FIG. 1a may be located within the cell coverage of the network equipment.
  • the terminal equipment can communicate with the network equipment through the uplink (uplink, UL) or the downlink (downlink, DL).
  • the terminal equipment can use the uplink physical layer shared channel (physical sidelink share). channel, PUSCH) to send data to the network device;
  • the network device can send the PDCCH carrying DCI to the terminal device, or it can send data to the terminal through the physical downlink share channel (PDSCH) .
  • PDSCH physical downlink share channel
  • the uplink physical layer shared channel may also be referred to as a physical uplink shared channel for short.
  • the downlink physical layer shared channel may also be simply referred to as the physical downlink shared channel.
  • the terminal device may include a physical layer (PHY), a medium access control (MAC), and a radio link control (RLC) layer.
  • PHY physical layer
  • MAC medium access control
  • RLC radio link control
  • PDCP Packet Data Convergence Protocol
  • SDAP Service Data Adaptation Protocol
  • RRC Radio Resource Control
  • Terminal equipment can include user plane protocol (user plane) and control plane protocol (control plane),
  • the terminal device in FIG. 1a may be referred to as a terminal (terminal) or user equipment (UE), or a mobile station (mobile station, MS) or a mobile terminal (mobile terminal, MT), etc.
  • a device that provides voice and/or data connectivity may be a mobile phone, an unmanned aerial vehicle, a tablet computer, or a computer with a wireless transceiver function, or a handheld device with a wireless connection function, a vehicle-mounted device, and the like.
  • the terminal device can also be a handheld computer, mobile internet device (MID), wearable device, eMBB terminal, URLLC terminal, MTC terminal, NB-IoT terminal, CPE terminal, VR terminal, AR terminal, V2X terminal, industrial Wireless terminals in control, wireless terminals in unmanned driving, wireless terminals in telemedicine, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, smart homes home) wireless terminals, sensors, cellular phones, cordless phones, session initiation protocol (SIP, session initiation protocol) phones, wireless local loop (WLL, wireless local loop) stations, personal digital assistants (PDA, personal digital assistant) , computing equipment or other processing equipment connected to a wireless modem, on-board terminals, vehicles with vehicle-to-vehicle (V2V) capabilities, and unmanned aerial vehicle (UAV)-to-UAV communication capabilities
  • wearable devices can also be called wearable smart devices, which is a general term for the intelligent design of daily wear and the development of wearable devices using wearable technology, such as glasses, gloves, watches, clothing and shoes.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories.
  • Wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-scale, complete or partial functions without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, which needs to cooperate with other devices such as smart phones. Use, such as all kinds of smart bracelets, smart jewelry, etc. for physical sign monitoring.
  • the terminal device may also be a terminal device in an Internet of Things (IoT, internet of things) system.
  • IoT Internet of Things
  • IoT is an important part of the development of information technology in the future. Its main technical feature is to connect items to the network through communication technology, so as to realize the intelligent network of human-machine interconnection and interconnection of things.
  • IoT technology can achieve massive connections, deep coverage, and terminal power saving through, for example, narrowband (NB, narrow band) technology.
  • NB narrowband
  • terminal equipment can also include sensors such as smart printers, train detectors, and gas stations.
  • the main functions include collecting data, receiving control information and downlink data from network equipment, and sending electromagnetic waves to transmit uplink data to network equipment.
  • the network device in FIG. 1a can be any device with wireless transceiver function, and can be used for air interface related functions, such as wireless link maintenance function, wireless resource management function, and partial mobility management function.
  • the wireless link maintenance function is used to maintain the wireless link with the terminal equipment, and is also responsible for the protocol conversion between wireless link data and Internet protocol (IP) data;
  • the wireless resource management function may include wireless link
  • Some mobility management functions may include configuring terminal equipment for measurement, evaluating the wireless link quality of terminal equipment, and deciding on handover of terminal equipment between cells.
  • a schematic diagram of a protocol stack between a terminal device and a network device may be shown in Figure 1b, and the protocol stack of the network device may include a PHY layer, a MAC layer, an RLC layer, a PDCP layer, an SDAP layer, and an RRC layer.
  • the protocol stack of the network device also includes a user plane protocol and a control plane protocol, and each layer of the terminal device and the network device can be connected to each other for information transmission.
  • the network device may be a device supporting wired access or a device supporting wireless access.
  • the network device may be an access network (access network, AN)/radio access network (radio access network, RAN) device, which is composed of multiple AN/RAN nodes.
  • AN/RAN nodes can be: access point (AP), base station (nodeB, NB), enhanced base station (enhance nodeB, eNB), next-generation base station (NR nodeB, gNB), transmission reception point (transmission reception point) point, TRP), transmission point (TP), or some other access node, etc.
  • RAN nodes may be: evolved Node B (gNB), transmission reception point (TRP), evolved Node B (evolved Node B, eNB), radio network controller (radio network controller) , RNC), home base station (for example, home evolved NodeB, or home Node B, HNB), wireless fidelity (wireless fidelity, Wifi) access point (access point, AP), wireless relay node, wireless backhaul node, Transmission point (TP) or transmission and reception point (TRP), etc.
  • 5G such as ngNB in NR system, or transmission point (TRP or TP), base station in 5G system
  • a network node that constitutes a gNB or a transmission point, such as a baseband unit (BBU), or a distributed unit (DU), D2D, V2X, machine to A device that assumes the function of a base station in machine-to-machine (M2M) communication, or
  • the gNB may include a centralized unit (CU) and DU, and the gNB may also include an active antenna unit (AAU).
  • the CU can implement part of the functions of the gNB, and the DU can implement part of the functions of the gNB.
  • the CU is responsible for processing non-real-time protocols and services, implementing radio resource control (RRC), and packet data convergence protocol (packet data convergence protocol, PDCP) layer.
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • the DU is responsible for processing physical layer protocols and real-time services, and implementing the functions of the radio link control (RLC) layer, medium access control (MAC) layer, and physical (PHY) layer.
  • RLC radio link control
  • MAC medium access control
  • PHY physical
  • the higher-layer signaling such as the RRC layer signaling
  • the network device may be a device including one or more of a CU node, a DU node, and an AAU node.
  • the CU can be divided into network devices in an access network (radio access network, RAN), and the CU can also be divided into network devices in a core network (core network, CN), which is not limited in this application.
  • the network equipment can provide services for the cell, and the terminal equipment communicates with the cell through the transmission resources (for example, frequency domain resources, or spectrum resources) allocated by the network equipment, and the cell can belong to a macro base station (for example, a macro eNB or a macro gNB, etc. ), it can also belong to the base station corresponding to the small cell, where the small cell can include: urban cell (metro cell), micro cell (micro cell), pico cell (pico cell), femto cell (femto cell) etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.
  • a macro base station for example, a macro eNB or a macro gNB, etc.
  • the measurement unit in the time domain of communication may be referred to as a time unit or a time scheduling unit.
  • the time scheduling unit or time unit may be a radio frame, a subframe, a time slot (slot), a mini-slot (mini-slot) or a sub-slot, and the like.
  • the time scheduling unit or time unit may also be one or more symbols, etc., wherein a symbol is a basic unit in the time domain.
  • the measurement unit in the frequency domain of communication may be referred to as a frequency domain resource unit or a frequency domain scheduling unit.
  • the frequency domain resource unit may be a basic resource element (resource element, RE), a resource block (resource block), a resource block group (resource block group), and the like.
  • one resource block may include one or more resource units.
  • a resource block group may include one or more resource blocks.
  • a frequency domain resource unit used for data transmission may include several basic resource units, one RE may correspond to one subcarrier, and there are X1 basic resource units in a physical resource block (physical resource block, PRB), where X1 is Integer greater than or equal to 1.
  • X1 is 12.
  • the terminal device and the network device in the embodiments of the present application may be one or more chips, or may be a system on chip (system on chip, SOC), or the like.
  • Figure 1a is only an exemplary drawing, which includes an unlimited number of devices.
  • the names of each device and each link in Figure 1a are not limited.
  • each device and each link can also be named with other names.
  • Device (user equipment, Uu) interface for communication, UL can also be named as Uu link, etc., without limitation.
  • the communication system may further include a core network and an external network.
  • the mobile network can be divided into three parts, namely a base station subsystem, a network subsystem, and a system support part.
  • the network equipment may be located in the base station subsystem
  • the core network may be located in the network subsystem.
  • the core network can be used to transmit call requests or data requests from the air interface to different external networks.
  • the core network can be used as an interface provided by the bearer network to the external network, and can provide functions such as user connection, user management, and bearer connection.
  • the establishment of the user connection may include functions such as mobility management (mobility management, MM), calling management (calling management, CM), switching/routing, and recording notification.
  • User management may include user description, quality of service (QoS), user communication recording (accounting), virtual home environment (VHE) (for example, providing virtual home environment through dialogue with intelligent network platform) , security (for example, the authentication center provides corresponding security measures, including security management of mobile services and security processing of external network access) and other functions.
  • Bearer connections (access to) include to external public switched telephone networks (PSTN), external circuit data networks and packet data networks, the Internet and intranets, and mobile own short messages Service (short message service, SMS) server and other functions.
  • PSTN public switched telephone networks
  • SMS short message service
  • the basic services provided by the core network may include mobile office, e-commerce, communications, entertainment services, travel and location-based services, telemetry-simple messaging services (monitoring and control), and the like.
  • the external network may be an operator network that provides data transmission services to users, such as an operator network that may provide users with IP multimedia services (IP multi-media service, IMS).
  • An application server may be deployed in the DN, and the application server may provide data transmission services to users.
  • the operator may include a public land mobile network (PLMN), and a PLMN is a government or a government-approved operator, a network established and operated to provide land mobile communication services for the public, for example, a mobile Operators, Unicom operators or telecom operators, etc.
  • PLMN public land mobile network
  • a PLMN is a government or a government-approved operator, a network established and operated to provide land mobile communication services for the public, for example, a mobile Operators, Unicom operators or telecom operators, etc.
  • each terminal device and network device may adopt the composition structure shown in FIG. 2 , or include the components shown in FIG. 2 .
  • FIG. 2 is a schematic diagram of the composition of a communication apparatus 200 provided by an embodiment of the present application.
  • the communication apparatus 200 may be a terminal device or a chip or a system-on-chip in the terminal device; it may also be a network device or a chip or a system-on-chip in the network device.
  • the communication device 200 includes a processor 201 , a transceiver 202 and a communication line 203 .
  • the communication apparatus 200 may further include a memory 204 .
  • the processor 201 , the memory 204 and the transceiver 202 may be connected through a communication line 203 .
  • the processor 201 is a central processing unit (CPU), a general-purpose processor network processor (NP), a digital signal processing (DSP), a microprocessor, a microcontroller, Programmable logic device (PLD) or any combination thereof.
  • the processor 201 may also be other apparatuses having processing functions, such as circuits, devices or software modules, which are not limited.
  • Transceiver 202 for communicating with other devices or other communication networks.
  • the other communication network may be Ethernet, radio access network (RAN), wireless local area networks (WLAN) and the like.
  • Transceiver 202 may be a module, circuit, transceiver, or any device capable of enabling communication.
  • the communication line 203 is used to transmit information between components included in the communication device 200 .
  • Memory 204 for storing instructions.
  • the instructions may be computer programs.
  • the memory 204 may be a read-only memory (ROM) or other types of static storage devices that can store static information and/or instructions, or a random access memory (RAM) or a random access memory (RAM).
  • ROM read-only memory
  • RAM random access memory
  • RAM random access memory
  • RAM random access memory
  • RAM random access memory
  • EEPROM electrically erasable programmable read-only memory
  • CD- ROM compact disc read-only memory
  • optical disc storage including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.
  • the memory 204 may exist independently of the processor 201 , or may be integrated with the processor 201 .
  • the memory 204 may be used to store instructions or program code or some data or the like.
  • the memory 204 may be located in the communication device 200, or may be located outside the communication device 200, which is not limited.
  • the processor 201 is configured to execute the instructions stored in the memory 204 to implement the communication methods provided by the following embodiments of the present application.
  • the processor 201 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 2 .
  • the communication apparatus 200 includes a plurality of processors, for example, in addition to the processor 201 in FIG. 2 , a processor 207 may also be included.
  • the communication apparatus 200 further includes an output device 205 and an input device 206 .
  • the input device 206 is a device such as a keyboard, a mouse, a microphone or a joystick
  • the output device 205 is a device such as a display screen, a speaker, and the like.
  • the communication apparatus 200 may be a desktop computer, a portable computer, a network server, a mobile phone, a tablet computer, a wireless terminal, an embedded device, a chip system or a device with a similar structure in FIG. 2 .
  • the composition shown in FIG. 2 does not constitute a limitation on the communication device.
  • the communication device may include more or less components than those shown in the figure, or combine some components , or a different component arrangement.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • actions, terms, etc. involved in the various embodiments of the present application can be referred to each other, and are not limited.
  • the names of the messages or the names of parameters in the messages exchanged between the devices are just an example, and other names may also be used in the specific implementation, which is not limited.
  • the communication methods shown in the embodiments of the present application may be applied to communication between a first communication apparatus and a second communication apparatus, where the first communication apparatus may be a terminal device or a network device.
  • the second communication apparatus may be a terminal device or a network device.
  • the following embodiments are described by taking the first communication device as a terminal device and the second communication device as a network device as an example.
  • the communication methods shown in the embodiments of the present application can be applied to the communication between a terminal device and a network device, can also be applied to the communication between a terminal device and a terminal device, and can also be applied to a network device and a network device. communication between.
  • the communication between the network device and the network device may be multi-point coordinated transmission between the macro base station and the macro base station, the micro base station and the micro base station, and the macro base station and the micro base station.
  • the following describes the communication method provided by the embodiment of the present application by taking the communication method shown in the embodiment of the present application applied to the communication between the terminal device and the network device as an example, in conjunction with the communication system shown in FIG. 1a, wherein the terminal device may be Any terminal device in the communication system; the network device can be any network device in the communication system.
  • the terminal equipment and network equipment described in the following embodiments may have the components shown in FIG. 2 .
  • FIG. 3a is a flowchart of a communication method provided by an embodiment of the present application. As shown in FIG. 3a, the method may include:
  • Step 301 The terminal device determines a first value candidate set.
  • the first value candidate set may correspond to the terminal type of the terminal device; the first value candidate set may include a value candidate set of RRC parameters corresponding to the terminal type.
  • the types of RRC parameters may be one or more of the following: configuration parameters for data transmission, configuration parameters for channel state information (channel state information, CSI) measurement feedback, configuration parameters for initial access, and mobility parameters.
  • the RRC parameters include one or more of the following: subcarrier spacing (subcarrier spacing, SCS) configuration parameters, CSI reporting frequency domain configuration parameters, CSI reporting time domain configuration parameters, channel quality information (channel quality information, CQI) ) table, beam failure recovery timing, configuration grant configuration parameters, subband size indication, bandwidth part (BWP) configuration parameters, code block group (CBG) configuration parameters, maximum number of beam failure instances (beam -failure-instance-maxcount) configuration parameters, CSI measurement configuration parameters, physical uplink control channel (physical uplink control channel, PUCCH) format configuration parameters, RRC parameters in protocol 38.331, other RRC parameters, etc. Specifically, this application does not limit this.
  • the configuration grant configuration parameters may include one or more of the following: frequency hopping indication (frequency hopping), modulation and coding scheme (modulation and coding scheme, MCS) table, resource allocation (resource allocation), number of repetitions, Repeat K times of redundancy version, period, configuration permission configuration parameters in protocol 38.331, other configuration permission configuration parameters, etc. Specifically, this application does not limit this.
  • the candidate set of values for each RRC parameter is a subset of the full set of values for the RRC parameter.
  • SCS includes 15kHz, 30kHz, 60kHz, 120kHz and 240kHz, other subcarrier spacing, etc.
  • the value of the SCS configuration parameter may include at least one candidate set, and each candidate set may include one or more of 15 kHz, 30 kHz, 60 kHz, 120 kHz and 240 kHz, and other subcarrier spacing values.
  • the CSI reporting frequency domain method may be wideband reporting (wideband), subband reporting (subband), subband reporting indication (csi-reporting band), other CSI reporting frequency domain methods, etc. .
  • the CSI reporting frequency domain configuration parameters may include at least one candidate set, and each candidate set may include one or more of full-band reporting, sub-band reporting, sub-band reporting indication, and other CSI reporting frequency domain configuration parameters, etc. kind.
  • the CQI table may include table1, table2, table3, other CQI tables, and so on. Specifically, this application does not limit this.
  • the CQI table may include at least one candidate set, and each candidate set may include one or more of table1, table2, table3, other CQI tables, and the like.
  • table1 is a CQI table of 64QAM normal bit rate
  • table2 is a CQI table of 256QAM
  • table3 is a CQI table of 64QAM low bit rate, etc.
  • this application does not limit this. It should be noted that, for the specific description of table1, table2, and table3, reference may be made to the relevant description of the CQI table in the existing communication protocol, which will not be repeated.
  • the subband size may include value1, value2, other subband sizes, and so on.
  • the subband size indication may include at least one candidate set, and each candidate set may include one or more of value1, value2, other subband sizes, and the like.
  • the timer values may include 10ms, 20ms, 40ms, 60ms, 80ms, 100ms, 150ms, 200ms, and other timer values.
  • the beam failure recovery timing may include at least one candidate set, and each candidate set may include one or more of 10ms, 20ms, 40ms, 60ms, 80ms, 100ms, 150ms, 200ms, other timer values, etc. .
  • the frequency domain hopping indication may include intraslot hopping and interslot hopping.
  • this application does not limit this.
  • the frequency-domain frequency hopping indication may include at least one candidate set, and each candidate set may include one or more of intra-slot frequency hopping and inter-slot frequency hopping.
  • the MCS table may be 256QAM, normal bit rate 64QAM and low bit rate 64QAM, other MCS tables, and so on. Specifically, this application does not limit this.
  • the MCS table may include at least one candidate set, and each candidate set may include one or more of 256QAM, normal code rate 64QAM, low code rate 64QAM, other MCS tables, and the like.
  • resource allocation can include type 0, type 1 and dynamic switching, other resource allocation methods, and so on.
  • the resource allocation may include at least one candidate set, and each candidate set may include one or more of type 0, type 1 and dynamic switching, other resource allocation methods, and the like.
  • the number of repetitions may include 1 repetition, 2 repetitions, 4 repetitions, 8 repetitions, other repetitions, and the like. Specifically, this application does not limit this.
  • the number of repetitions may include at least one candidate set, and each candidate set may include one or more of repetitions 1, 2, 4, and 8.
  • the redundant version repeated K times may be 0, 2, 3, 1, or, 0, 3, 0, 3, or, 0, 0, 0, 0, other redundant versions, and so on. Specifically, this application does not limit this.
  • the redundant version repeated K times may include at least one candidate set, and each candidate set may include 0, 2, 3, 1, or 0, 3, 0, 3, or 0, 0, 0, one or more of 0.
  • the period can include multiple values.
  • a period may include at least one candidate set, and each candidate set may include one or more period values.
  • the value candidate set of the RRC parameter is used to indicate the configuration mode of the RRC parameter.
  • the configuration mode includes a configuration parameter field, and the configuration parameter field includes configuration parameters of the configuration mode; or, the configuration mode includes configuration parameters.
  • the candidate set of the configuration permission configuration parameter value can be used to indicate the configuration mode of the configuration permission configuration parameter
  • the configuration mode can include the configuration parameter field
  • the configuration parameter field can include the frequency domain hopping One or more of frequency indication, MCS table, resource allocation, number of repetitions, redundancy version repeated K times, and period.
  • the configuration parameter field may include frequency-domain hopping configuration parameters indicated by the frequency.
  • the candidate set of SCS configuration parameter values may be used to indicate the configuration mode of the SCS configuration parameter, and the configuration mode may include configuration parameters, for example, the configuration mode may include 15 kHz, 30 kHz, 60 kHz, One or more of 120kHz and 240kHz.
  • the terminal type corresponding to the terminal device is determined according to one or more of the following factors: service type, mobility, transmission delay requirement, channel environment, reliability requirement , Coverage requirements, and communication scenarios.
  • the service type may be determined according to the size of the service data, for example, the service type may include large-packet data, medium-packet data, small-packet data, and the like.
  • Mobility may include movement and fixation; wherein, movement may also include irregular movement, movement along a fixed route, ultra-short-distance movement, and the like.
  • Transmission delay requirements may include high transmission delay, low transmission delay, and normal transmission delay.
  • the channel environment may include a changeable channel environment, a stable channel environment, a relatively stable channel environment, and the like. Reliability requirements can include high reliability, low reliability, average reliability, and the like. Coverage requirements may include wide coverage, strong coverage, weak coverage, general coverage, and deep coverage.
  • the communication scenarios may include the communication scenarios included in the foregoing description of the communication system, or the communication scenarios may also include uplink communication, downlink communication, uplink and downlink communication, sidelink communication, backhaul communication, access communication, relay communication, Satellite communication, terahertz communication, optical communication, green communication, etc. are not limited.
  • the eMBB devices are mainly used to transmit large-packet data, and can also be used to transmit small-packet data.
  • the requirements for transmission delay and reliability are general, both uplink and downlink communication are available, and the channel environment is relatively complex and changeable. It can communicate indoors or outdoors.
  • the eMBB device can be a mobile phone.
  • URLLC devices are mainly used to transmit small-packet data, and can also transmit medium-packet data. Generally, they are in a non-mobile state, or they can move along a fixed route.
  • NB-IoT devices are mainly used to transmit small data. They are generally in a non-mobile state and their locations are known. They have moderate requirements for transmission delay and reliability, more uplink communications, and relatively stable channel environments.
  • NB-IoT devices can be Smart water meters, sensors.
  • CPE equipment is mainly used to transmit large packet data. It is generally in a non-mobile state, or can move in ultra-short distances. It has moderate requirements for transmission delay and reliability, both uplink and downlink communication, and the channel environment is relatively stable.
  • CPE equipment It can be terminal equipment, AR, VR, etc. in the smart home.
  • the terminal type corresponding to the terminal device can be determined as eMBB device, URLLC device, NB-IoT device or CPE device.
  • eMBB devices can also be described as eMBB
  • URLLC devices can also be described as URLLC
  • NB-IoT devices can also be described as NB-IoT
  • CPE devices can also be described as CPE
  • V2X devices can also be described as V2X. be restricted.
  • the first value candidate set corresponding to the terminal type is determined according to the terminal type.
  • the first value candidate set may include a value candidate set of the RRC parameter corresponding to the terminal type.
  • different terminal types correspond to different first value candidate sets.
  • the RRC parameter value candidate set is used to indicate the configuration mode of the RRC parameter; the configuration mode includes a configuration parameter field, and the configuration parameter field includes configuration parameters of the configuration mode; or, the configuration mode includes a configuration parameter.
  • the terminal type has a corresponding relationship with the RRC parameter value candidate set, and may also include one or more of the following: the terminal type has a corresponding relationship with the RRC parameter type, and the terminal type has a corresponding relationship with the configuration mode corresponding to the RRC parameter. , the terminal type has a corresponding relationship with the configuration parameter field of the configuration mode corresponding to the RRC parameter, and the terminal type has a corresponding relationship with the configuration parameter of the RRC parameter.
  • the following embodiment is a communication method, in which the RRC parameters can be customized according to the terminal type, so as to realize the function matching with the terminal, optimally meet the requirements of various devices, reduce the signaling overhead, and reduce the delay under parameter switching. Reduce communication complexity and chip cost.
  • the embodiments of the present application may be used as independent embodiments, and may also be combined with other embodiments of the present invention, which are not specifically limited in the present application.
  • the terminal type has a corresponding relationship with the type of the RRC parameter.
  • the following embodiment is a method for designing an RRC parameter type.
  • the RRC parameter type can be customized according to the terminal type, so as to realize the matching of the function type and the terminal, optimally meet the requirements of various devices, reduce signaling overhead, and reduce parameter switching.
  • the delay can reduce the communication complexity and reduce the chip cost.
  • the embodiments of the present application may be used as independent embodiments, and may also be combined with other embodiments of the present invention, which are not specifically limited in the present application.
  • the communication requirements corresponding to the terminal types may be different. Therefore, the terminal equipment does not need to support at least one of the above RRC parameter types. Therefore, the RRC parameter type suitable for the terminal equipment to communicate can be determined according to the terminal type. , so as to meet the different communication requirements of terminal equipment of different terminal types, and at the same time reduce the signaling overhead.
  • the terminal device and/or the network device may determine a candidate set of types of RRC parameters according to the terminal type.
  • the terminal type has a corresponding relationship with the candidate set of RRC parameter types, where the corresponding relationship may be predefined by the protocol, or may be notified by the network device to the terminal device through high-level signaling or physical layer signaling.
  • the application is not limited.
  • the terminal device when the terminal device is always in a stationary state, the terminal device may not need to support beam management, and the network device may not need to configure configuration parameters of beam management for the terminal device.
  • the terminal device When the terminal device always performs small packet transmission or short-range transmission, the terminal device may not need to support power control, and the network device may not need to configure the configuration parameters of power control for the terminal device.
  • the types of RRC parameters corresponding to eMBB may include configuration parameters for data transmission, configuration parameters for CSI measurement feedback, configuration parameters for initial access, configuration parameters for mobility, and configuration for power control. parameters and configuration parameters for beam management.
  • configuration parameters for data transmission may include SCS configuration parameters; configuration parameters for CSI measurement feedback may include beam failure recovery timing; configuration parameters for beam management may include CSI reporting time domain configuration parameters.
  • the type of RRC parameters corresponding to URLLC may include configuration parameters for data transmission, configuration parameters for channel state information CSI measurement feedback, and configuration parameters for beam management.
  • URLLC mainly transmits small-packet services
  • power control can be omitted, which reduces the complexity.
  • URLLC is mainly a stationary scenario or a mobile scenario with a fixed path, and the channel state is relatively stable. Therefore, CSI measurement feedback is not required, and low-rate transmission is used to reduce power consumption and improve communication efficiency.
  • beam management can be performed to achieve beam alignment, position prediction, and data transmission in advance, which can reduce delay, meet the needs of accurate operation and delay of services, and improve communication efficiency.
  • configuration parameters for data transmission may include SCS configuration parameters, etc.
  • configuration parameters for CSI measurement feedback may include CSI reporting time domain configuration parameters, etc.
  • beam management configuration parameters may include CSI reporting time domain configuration parameters, etc.
  • the types of RRC parameters corresponding to NB-IoT include data transmission configuration parameters, initial access configuration parameters, and mobility configuration parameters.
  • the application scenario of NB-Iot can be a high-speed mobile scenario, mobility management can be performed, power control can be omitted, and complexity is reduced.
  • the configuration parameters of data transmission may include SCS configuration parameters and the like.
  • the type of RRC parameters corresponding to the CPE may include configuration parameters for data transmission and configuration parameters for channel state information CSI measurement feedback.
  • the configuration parameters for data transmission may include SCS configuration parameters; the configuration parameters for CSI measurement feedback may include CSI reporting time domain configuration parameters.
  • the value candidate set of each RRC parameter corresponding to the terminal type can be further determined for the terminal type according to the communication requirements of the terminal type, and the first value candidate set corresponding to the terminal type is the value candidate of each RRC parameter corresponding to the terminal type. collection of sets.
  • the candidate set of SCS configuration parameter values corresponding to the terminal type can be determined according to the terminal type.
  • the terminal device and/or the network device may determine a candidate set of SCS configuration parameter values according to the terminal type.
  • the embodiments of the present application may be used as independent embodiments, or may be combined with other embodiments in the present application, which are not specifically limited in the present application.
  • the terminal type has a corresponding relationship with the candidate set of SCS configuration parameter values.
  • the corresponding relationship may be predefined by the protocol, or may be notified to the terminal device by the network device through high-level signaling or physical layer signaling. Specifically, This application does not limit this.
  • terminal type A may correspond to candidate set A of SCS configuration parameter values
  • terminal type B may correspond to candidate set B, . . . of SCS configuration parameter values
  • terminal type X may correspond to candidate set X of SCS configuration parameter values.
  • the candidate set of SCS configuration parameter values may include 15kHz, 30kHz, 120kHz, and 240kHz.
  • eMBB is mainly for medium and large packet service transmission, and does not need to meet the requirements of low-latency reliability, data transmission can be performed with relatively small subcarrier intervals such as 15kHz and 30kHz for the FR1 frequency band to improve communication efficiency.
  • the candidate set of SCS configuration parameter values may include 30 kHz, 60 kHz, 120 kHz or 240 kHz.
  • URLLC is mainly for small packet service transmission and needs to meet the requirements of low latency reliability
  • it can use relatively large sub-carrier spacing for data transmission in the FR1 frequency band, such as 30kHz, 60kHz, etc.
  • For the FR2 frequency band use Data transmission with a relatively large sub-carrier interval such as 120 kHz can meet the requirements of low latency, and repeated transmission within a certain time unit.
  • the candidate set of SCS configuration parameter values may include 15 kHz and 120 kHz.
  • a relatively small sub-carrier spacing such as 15 kHz can be used for the FR1 frequency band, and a relatively small sub-carrier spacing such as 120 kHz can be used for the FR2 frequency band.
  • the subcarrier interval is used for data transmission to improve communication efficiency.
  • the first candidate set of SCS configuration parameter values may include 15 kHz and 120 kHz
  • the second candidate set of SCS configuration parameter values may include 30 kHz and 240 kHz.
  • a relatively small sub-carrier spacing such as 15 kHz can be used for the FR1 frequency band, and a relatively small sub-carrier spacing such as 120 kHz can be used for the FR2 frequency band.
  • the carrier interval is used for data transmission to improve communication efficiency; when it is necessary to meet the requirements of low-latency reliability, a relatively small sub-carrier interval such as 30 kHz can be used for the FR1 frequency band, and a relatively large sub-carrier interval such as 240 kHz can be used for the FR2 frequency band. transmission to meet the delay requirements and improve communication efficiency.
  • frequency bands of different frequency points may correspond to different sets of SCS configuration parameter values.
  • the full set of SCS configuration parameter values can include 15kHz, 30kHz, 60kHz, etc.; for frequency range 2 (frequency range 2, FR2), the full set of SCS configuration parameter values can be Including 60kHz, 120kHz, 240kHz, etc.; wherein, FR1 can be a frequency band below 6G; FR2 can be a frequency band above 6G.
  • the terminal device and/or the network device may determine a candidate set of SCS configuration parameter values according to the terminal type and frequency band.
  • the embodiments of the present application may be used as independent embodiments, or may be combined with other embodiments in the present application, which are not specifically limited in the present application.
  • the terminal type and frequency band have a corresponding relationship with the candidate set of SCS configuration parameter values.
  • the corresponding relationship may be predefined by the protocol, or may be notified to the terminal device by the network device through high-level signaling or physical layer signaling. Yes, this application does not limit it.
  • terminal type A can correspond to candidate set A1 of SCS configuration parameter values for FR1, and can correspond to candidate set A2 of SCS configuration parameter values for FR2;
  • terminal type B can correspond to candidate set B1 of SCS configuration parameter values for FR1,
  • the terminal type X can correspond to the candidate set X1 of the SCS configuration parameter value for FR1 and the candidate set X2 of the SCS configuration parameter value for FR2.
  • the candidate set of SCS configuration parameter values may include 15kHz and 30kHz; for FR2, the candidate set of SCS configuration parameter values may include 120kHz and 240kHz.
  • the specific analysis description can be as above, which is not repeated here.
  • the candidate set of SCS configuration parameter values may include 30 kHz and 60 kHz; for FR2, the candidate set of SCS configuration parameter values may include 120 kHz.
  • the specific analysis description can be as above, which is not repeated here.
  • the candidate set of SCS configuration parameter values may include 15 kHz; for FR2, the candidate set of SCS configuration parameter values may include 120 kHz.
  • the specific analysis description can be as above, which is not repeated here.
  • the candidate set of SCS configuration parameter values may include 15 kHz; for FR2, the candidate set of SCS configuration parameter values may include 120 kHz.
  • the specific analysis description can be as above, which is not repeated here.
  • designing the candidate set of SCS configuration parameter values according to the terminal type and frequency band can further reduce signaling overhead compared to designing the candidate set of SCS configuration parameter values only according to the terminal type.
  • the corresponding terminal type can be determined according to the terminal type.
  • the candidate set of CSI reporting frequency domain configuration parameter values can be determined according to the terminal type.
  • the terminal device and/or the network device may determine a candidate set of CSI reporting frequency domain configuration parameter values according to the terminal type.
  • the embodiments of the present application may be used as independent embodiments, or may be combined with other embodiments in the present application, which are not specifically limited in the present application.
  • the terminal type has a corresponding relationship with the candidate set of CSI reporting frequency domain configuration parameter values. Specifically, this application does not limit this.
  • terminal type A can correspond to the candidate set AC of the CSI reporting frequency domain configuration parameter value
  • terminal type B can correspond to the candidate set BC of the CSI reporting frequency domain configuration parameter value
  • terminal type X can correspond to the CSI reporting frequency domain configuration parameter The candidate set XC of parameter values.
  • the candidate set of CSI reporting frequency domain configuration parameter values may include full-band reporting, sub-band reporting, and sub-band reporting indication.
  • the CSI reporting frequency domain configuration parameters that can be used for CSI measurement feedback can include full-band reporting, sub-band reporting, and sub-band reporting indication to meet the needs of various scenarios and indicate on-demand. Reduce power consumption and improve communication efficiency.
  • the candidate set of the value of the CSI reporting frequency domain configuration parameter may include full-band reporting or sub-band reporting.
  • the CSI reporting frequency domain configuration parameters that can be used for CSI measurement feedback can be full-band reporting or sub-band reporting, reducing power consumption. Improve communication efficiency.
  • the candidate set of CSI reporting frequency domain configuration parameter values may include full-band reporting and sub-band reporting.
  • the CSI reporting frequency domain configuration parameters that can be used for CSI measurement feedback can be full-band reporting.
  • the CSI reporting frequency domain configuration parameter for CSI measurement feedback can be subband reporting, which can meet the needs of various scenarios, provide on-demand instructions, reduce power consumption, and improve communication efficiency.
  • the candidate set of CSI reporting frequency domain configuration parameter values may include full-band reporting.
  • the CSI reporting frequency domain configuration parameters used for CSI measurement feedback can be full-band reporting, which reduces complexity, reduces power consumption, and improves communication efficiency.
  • the candidate set of CQI table values corresponding to the terminal type can be determined according to the terminal type.
  • the terminal type A can correspond to the candidate set AQ of the CQI table value
  • the terminal type B can correspond to the candidate set BQ of the CQI table value
  • ... the terminal type X can correspond to the candidate set XQ of the CQI table value.
  • the candidate set of CQI table values may include table1, table2, and table3.
  • the candidate set of eMBB CQI table values can be designed to include table1, table2, table3, which can meet the requirements of different scenarios. demand to improve communication efficiency.
  • the candidate set of CQI table values may include table3.
  • the candidate set of CQI table values of URLLC can be designed to include table3, that is, the CQI table of 64QAM low bit rate, which can meet the requirements of low-latency reliability. High reliability requirements to improve communication efficiency.
  • the candidate set of CQI table values may include table1.
  • the candidate set of CQI table values of URLLC can be designed to include table1, that is, the CQI table of 64QAM normal code rate , which can meet the communication needs and improve the communication efficiency.
  • the candidate set of CQI table values may include table2 and table3.
  • the candidate set of CQI table values can be designed to include table2, that is, the CQI table of 256QAM, so as to realize fast large-packet transmission.
  • the candidate set of CQI table values can be designed to include table3, that is, the CQI table of 64QAM low bit rate, to meet reliability requirements and improve communication efficiency.
  • the corresponding terminal type can be determined according to the terminal type.
  • the candidate set of beam failure recovery timing values can be determined according to the terminal type.
  • the terminal device and/or the network device may determine a candidate set of beam failure recovery timing values according to the terminal type.
  • the embodiments of the present application may be used as independent embodiments, or may be combined with other embodiments in the present application, which are not specifically limited in the present application.
  • the terminal type has a corresponding relationship with the candidate set of beam failure recovery timing values.
  • the corresponding relationship may be predefined by the protocol, or may be notified to the terminal device by the network device through high-level signaling or physical layer signaling. , which is not limited in this application.
  • terminal type A may correspond to a candidate set AT of beam failure recovery timing values
  • terminal type B may correspond to a candidate set BT of beam failure recovery timing values
  • terminal type X may correspond to a candidate set of beam failure recovery timing values XT.
  • the candidate set of beam failure recovery timing values may include 10ms, 20ms, 40ms, 60ms, 80ms, 100ms, 150ms, and 200ms.
  • the candidate set of beam failure recovery timing values can include 10ms, 20ms, 40ms, 60ms, 80ms, 100ms, 150ms, 200ms and other values to meet the needs of various scenarios, as needed indication, reduce power consumption and improve communication efficiency.
  • the candidate set of beam failure recovery timing values may include 10ms, 20ms, and 40ms.
  • the candidate set of beam failure recovery timing values that can be used can include 10ms, 20ms, 40ms, fast Realize beam recovery, reduce delay, and improve communication efficiency.
  • the candidate set of beam failure recovery timing values may include 80ms, 100ms, 150ms, and 200ms.
  • the candidate set of beam failure recovery timing values that can be used can include 80ms, 100ms, 150ms, 200ms, and beam failure The value of the recovery timing is larger, and it can be indicated on demand, which can reduce power consumption and improve communication efficiency.
  • the candidate set of beam failure recovery timing values may include 20ms, 60ms, and 80ms.
  • the candidate set of beam failure recovery timing values can include 20ms, 60ms, 80ms, reducing complexity, reducing delay, and improving communication efficiency.
  • the terminal type can be determined according to the terminal type.
  • the terminal device and/or the network device may determine a candidate set of CSI reporting time domain configuration parameter values according to the terminal type.
  • the embodiments of the present application may be used as independent embodiments, or may be combined with other embodiments in the present application, which are not specifically limited in the present application.
  • the terminal type has a corresponding relationship with the candidate set of CSI reporting time domain configuration parameter values, where the corresponding relationship may be predefined by the protocol, or may be notified to the terminal device by the network device through high-level signaling or physical layer signaling. Specifically, this application does not limit this.
  • terminal type A may correspond to the candidate set AS of the value of the CSI reporting time domain configuration parameter
  • terminal type B may correspond to the candidate set BS of the value of the CSI reporting time domain configuration parameter
  • terminal type X may correspond to the CSI reporting time domain configuration The candidate set XS of parameter values.
  • the candidate set for the value of the CSI reporting time domain configuration parameter may include periodic reporting, aperiodic reporting, and semi-persistent reporting.
  • the candidate set of CSI reporting time domain configuration parameters that can be used can include periodic reporting, aperiodic reporting, and semi-persistent reporting, to meet the needs of various scenarios, and indicate on demand. Reduce power consumption and improve communication efficiency.
  • the candidate set of the value of the CSI reporting time domain configuration parameter may include aperiodic reporting.
  • the CSI reporting time domain configuration parameter of the CSI measurement feedback can be aperiodic reporting. , on-demand instructions, reduce power consumption, reduce delay, and improve communication efficiency.
  • the candidate set of CSI reporting time domain configuration parameter values may include periodic reporting.
  • the CSI reporting time domain configuration parameter of the CSI measurement feedback adopted can be reported periodically, which reduces complexity, reduces power consumption, and improves communication efficiency.
  • the set of candidate value sets for each RRC parameter corresponding to the terminal type may be determined as the first candidate value set corresponding to the terminal type.
  • the terminal device may determine the first value candidate set corresponding to the terminal type of the terminal device according to at least one of the following manners 1 to 4.
  • Manner 1 The first value candidate set is predetermined by the communication protocol.
  • a training model such as machine learning and neural network may be used to determine the RRC parameter corresponding to the terminal type and the candidate set of values of each RRC parameter corresponding to the terminal type for the terminal type.
  • the RRC parameter values corresponding to the terminal type and the RRC parameter value candidate sets corresponding to the terminal type may be determined according to the RRC parameter values configured for each terminal device by the network device within a period of time according to the communication requirements of each terminal device.
  • the RRC parameter corresponding to the terminal type and the candidate set of value of each RRC parameter corresponding to the terminal type may also be determined according to the communication experience.
  • the communication quality of the terminal device under different RRC parameter combinations and/or different candidate sets of RRC parameter values can be determined through training models such as machine learning or neural network, and the RRC parameters corresponding to the terminal type and the terminal type can be determined according to the communication quality.
  • the corresponding candidate set of values for each RRC parameter can be determined through training models such as machine learning or neural network, and the RRC parameters corresponding to the terminal type and the terminal type can be determined according to the communication quality.
  • the corresponding candidate set of values for each RRC parameter can be determined through training models such as machine learning or neural network.
  • the terminal type A including terminal equipment 1, terminal equipment 2 and terminal equipment 3 it can be determined according to the RRC parameter values configured by the network equipment for terminal equipment 1, terminal equipment 2 and terminal equipment 3 within a period of time.
  • RRC parameters corresponding to the terminal type A, and a candidate set of values for each RRC parameter corresponding to the terminal type are included in the terminal type A.
  • the first value candidate set corresponding to each terminal type can be written into the communication protocol, so that the network device and the terminal device can determine the first value candidate set corresponding to the terminal type of the terminal device according to the communication protocol, so as to avoid the network device to The terminal device sends the first value candidate set, which saves signaling overhead, reduces communication delay, and reduces terminal power consumption.
  • Manner 2 The network device sends the first value candidate set to the terminal device.
  • the network device may determine the first value candidate set corresponding to the terminal device according to the terminal type of the terminal device during the random access process or when the terminal device initially accesses the network, and deliver the first value candidate set to the terminal device.
  • the network device may send the first value candidate set through high-layer signaling or physical layer signaling, and the terminal device determines the first value candidate set according to an instruction of the network device.
  • the network device can configure the first value candidate set, realize the configuration flexibility of the first value candidate set, better adapt to different scenarios, meet the needs of different scenarios, reduce the cost of value indication, and improve communication efficiency.
  • Manner 3 The terminal device sends the first request information to the network device, and the network device sends the first value candidate set to the terminal device according to the first request information.
  • the first request information is used to request a candidate set of values of RRC parameters corresponding to the terminal type of the terminal device.
  • the first request information includes an RRC parameter value candidate set corresponding to the terminal type determined by the terminal device.
  • the terminal device may determine a candidate set of RRC parameter values suitable for communication by itself according to its own communication requirements, and send the candidate set of RRC parameter values to the network device.
  • the network device After the network device receives the RRC parameter value candidate set sent by the terminal device, it determines whether the terminal device can use the RRC parameter value candidate set, and if so, the RRC parameter value candidate set is used as the first value candidate set.
  • the value candidate set is sent to the terminal device. If not, the network device may determine the first value candidate set corresponding to the terminal device according to the terminal type of the terminal device, and send the first value candidate set to the terminal device.
  • the terminal device can send the proposed first value candidate set to the network device, so as to realize the configuration flexibility of the first value candidate set, better meet the communication requirements of the terminal device, and better adapt to different scenarios. Meet the needs of different scenarios, reduce the overhead of value indication, and improve communication efficiency.
  • Manner 4 The terminal device sends the first feature information to the network device, and the network device sends the first value candidate set to the terminal device according to the first feature information.
  • the first feature information may be used to indicate the terminal type of the terminal device.
  • the first feature information may be the terminal type of the terminal device, or a communication requirement used to indicate the terminal type of the terminal device, and the communication requirement may be service type, mobility, transmission delay requirement, channel environment, reliability One or more of sexual requirements, coverage requirements, and communication scenarios.
  • the network device may determine the terminal type of the terminal device according to the first feature information sent by the terminal device, determine the first value candidate set corresponding to the terminal type, and send the first value candidate set to the terminal device.
  • the terminal device can send the first feature information to the network device, and determine the first value candidate set based on the first feature information, so as to realize the configuration flexibility of the first value candidate set, and better meet the communication requirements of the terminal device. , better adapt to different scenarios, meet the needs of different scenarios, reduce the overhead of value indication, and improve communication efficiency.
  • Step 302 The network device sends the first value to the terminal device.
  • the terminal device receives the first value.
  • the first value includes a set of RRC parameter values in the first value candidate set.
  • the network device may not send the first value to the terminal device. At this time, the terminal device and the network device may determine that the value of the RRC parameter is the first value.
  • the network device may not send the first value to the terminal device.
  • the terminal device and the network device may determine that the value of the RRC parameter is a default value.
  • the default value includes the value of the RRC parameter corresponding to the terminal type in the first value candidate set. That is, when the network device does not indicate the value of the RRC parameter to the terminal device, the value of the RRC parameter is the default value, or, when the terminal device does not receive the value of the RRC parameter indicated by the network device, the value of the RRC parameter is the default value. value.
  • the default value of the RRC parameter value may be predefined by the protocol, or may be notified by the network device to the terminal device through higher layer signaling or physical layer signaling.
  • the RRC parameter when the RRC parameter takes the default value, the signaling overhead can be reduced and the communication performance can be improved.
  • the network device may determine the first value from the first value candidate set according to the first value candidate set corresponding to the terminal device, and send the first value to the terminal device.
  • the first value candidate set corresponding to terminal device A includes SCS configuration parameters and CSI reporting frequency domain configuration parameters
  • the candidate set of SCS configuration parameter values includes 15 kHz, 30 kHz, 120 kHz, 240 kHz, and CSI reporting frequency domain.
  • the candidate set of configuration parameter values includes full-band reporting, sub-band reporting, and sub-band reporting indication.
  • the network device can determine the first value for terminal device A according to the communication requirements of the terminal device.
  • the first value includes SCS.
  • the configuration parameter, the CSI reporting frequency domain configuration parameter, and the SCS configuration parameter value is 15kHz
  • the CSI reporting frequency domain configuration parameter value is full-band reporting.
  • Step 303 The terminal device communicates according to the first value.
  • the network device can determine the first value for the terminal device from the first value candidate set, thereby reducing the RRC signaling overhead , reduce the storage overhead of the terminal device, and at the same time reduce the power consumption of the terminal device.
  • the communication method provided by the embodiment of the present application may be described from the perspective of the first communication device.
  • FIG. 3b is a flowchart of a communication method provided by an embodiment of the application. As shown in FIG. 3b, the method may include:
  • Step 301a The first communication apparatus determines a candidate set of values for RRC parameters corresponding to the terminal type of the first communication apparatus.
  • this step can be omitted.
  • Step 302a the first communication device sends the first request information and/or the first feature information.
  • this step can be omitted.
  • Step 303a The first communication device determines a first value candidate set.
  • Step 304a the first communication device receives the first value.
  • Step 305a the first communication device performs communication according to the first value.
  • the communication method provided by this embodiment of the present application may be described from the perspective of the second communication device.
  • FIG. 3c is a flowchart of a communication method provided by an embodiment of the present application. As shown in FIG. 3c, the method may include:
  • Step 301b the second communication device receives the first request information and/or the first feature information.
  • this step can be omitted.
  • Step 302b the second communication apparatus determines the first value candidate set.
  • Step 303b the second communication apparatus sends the first value candidate set.
  • Step 304b the second communication device sends the first value.
  • the embodiment of the present application also provides a communication method for improving the network When sending DCI to terminal equipment to schedule RRC signaling and/or data signals, since the format of DCI is a fixed format pre-defined by the communication protocol, the signaling overhead of DCI is relatively large, resulting in low spectral efficiency of the communication system and power consumption of terminal equipment. major technical issues.
  • FIG. 5a is a flowchart of a communication method provided by an embodiment of the present application.
  • the embodiment of the present application may be used as an independent embodiment, and may also be combined with other embodiments of the present application. Specifically, the present application does not do this. limited. As shown in Figure 5a, the method may include:
  • Step 501 The network device sends the first DCI to the terminal device.
  • the terminal device receives the first DCI.
  • the first DCI may include values of multiple DCI parameters; the DCI parameters included in the first DCI correspond to the terminal type of the terminal device; the candidate set of DCI parameter values corresponds to the terminal type; the candidate set includes the corresponding terminal type At least one value of the DCI parameter.
  • the DCI parameters may include one or more of the following: DCI format indication (uplink and downlink indication), carrier indicator field (carrier indicator), bandwidth part indicator (bandwidth part indicator), frequency domain Resource allocation, time domain resource allocation, frequency domain frequency hopping indication, virtual resource block to physical resource block mapping (virtual resource block to physical resource block mapping, VRB-to-PRB mapping), physical resource block bundling size indication (PRB bundling) size indicator), MCS, new data indicator (new data indicator), redundancy version (redundancy version), hybrid automatic repeat request process number (hybrid automatic repeat request process number, HARQ process number), HARQ timing, scheduling physical uplink sharing Channel transmission power control command (transmit power control command for scheduled physical uplink shared channel, TPC command for scheduled PUSCH), uplink or supplementary uplink indicator (uplink/supplementary uplink indicator, UL/SUL indicator), precoding and layer number (precoding) information and number of layers), antenna ports (antenna ports), sounding reference signal resource indicator (uplink and downlink indication), carrier indicator field
  • the DCI parameter corresponding to the terminal type may be determined according to the terminal type.
  • the terminal device and/or the network device may determine the DCI parameter according to the terminal type.
  • the embodiments of the present application may be used as independent embodiments, or may be combined with other embodiments in the present application, which are not specifically limited in the present application.
  • the terminal type has a corresponding relationship with the DCI parameter, wherein the corresponding relationship may be predefined by the protocol, or may be notified by the network device to the terminal device through high-level signaling or physical layer signaling. Specifically, this application does not do this. limited.
  • the communication requirements corresponding to the terminal types may be different, so that the terminal equipment may not need to support one or more of the above DCI parameters. Therefore, the DCI parameters suitable for the terminal equipment to communicate can be determined according to the terminal type. , so as to meet the different communication requirements of terminal equipment of different terminal types, and at the same time reduce the DCI signaling overhead.
  • terminal types correspond to different DCI parameter sets
  • the DCI parameter sets may include one or more of the above DCI parameters.
  • terminal type A may correspond to DCI parameter set AD
  • terminal type B may correspond to DCI parameter set BD
  • terminal type X may correspond to DCI parameter set XD.
  • the DCI parameters corresponding to eMBB may include time domain resource allocation, frequency domain resource allocation, BWP indication, MCS, new data indication, redundancy version, number of HARQ processes, HARQ timing, and TPC commands. , antenna port, precoding and number of layers, SRS request, CSI request.
  • the DCI parameters corresponding to eMBB may also include DCI format indication (uplink and downlink indication), carrier indication field, BWP indication, frequency domain resource allocation, time domain resource allocation, frequency domain frequency hopping indication, VRB-to-PRB mapping , PRB bundle size indication, MCS, new data indication, redundancy version, HARQ process number, HARQ timing, TPC command, uplink or supplementary uplink indication, precoding information and layer number, antenna port.
  • DCI format indication uplink and downlink indication
  • BWP indication carrier indication field
  • BWP indication frequency domain resource allocation
  • time domain resource allocation time domain resource allocation
  • frequency domain frequency hopping indication VRB-to-PRB mapping
  • PRB bundle size indication MCS
  • new data indication redundancy version
  • HARQ process number HARQ timing
  • TPC command uplink or supplementary uplink indication
  • precoding information and layer number antenna port.
  • the DCI parameters corresponding to URLLC may include time domain resource indication, frequency domain resource indication, MCS, new data indication, HARQ process number, TPC command, SRS request, and CSI request.
  • URLLC is mainly a small packet service transmission.
  • URLLC is mainly a static scene or a fixed path mobile scene, and the channel state is relatively stable, so frequency-domain frequency hopping and VRB-to-PRB interleaving mapping may not be performed, that is, DCI parameters may not include frequency-domain frequency hopping indication, VRB- to-PRB mapping to reduce signaling overhead.
  • URLLC can generally use low-rate transmission. Therefore, only a single antenna port can be used for rank 1 transmission, which reduces power consumption, reduces signaling overhead, and improves communication efficiency.
  • the DCI parameters may not include precoding information, the number of layers, and the antenna ports, thereby reducing signaling overhead.
  • beam management can be performed to achieve beam alignment, position prediction, and data transmission in advance. Therefore, DCI parameters can include SRS requests and CSI requests. It can reduce the delay, meet the needs of precise operation and delay of the business, and improve the communication efficiency.
  • the DCI parameters corresponding to the URLLC may also include frequency domain resource allocation, MCS, new data indication, and redundancy version.
  • the channel state is relatively stable, so the DCI parameter may not include the SRS request and the CSI request.
  • the complexity and signaling overhead can be reduced, communication requirements can be met, and communication efficiency can be improved.
  • the DCI parameters corresponding to NB-IoT may include frequency domain resource indication, MCS, and HARQ process number.
  • the application scenario of NB-Iot can be small packet data transmission and static scenario
  • the SRS request, CSI request, frequency domain frequency hopping indication, VRB-to-PRB mapping, and precoding information may not be included in the DCI. and layers, antenna ports, using low-speed transmission, reducing signaling overhead, reducing power consumption, and improving communication efficiency.
  • the DCI parameters corresponding to NB-IoT may also include MCS, new data indication, and redundancy version.
  • the number of HARQ processes can be designed to be 1, so the HARQ process number can be excluded from the DCI, which reduces signaling overhead, reduces power consumption, and improves communication efficiency.
  • the DCI parameters corresponding to the CPE may include time domain resource allocation, frequency domain resource allocation, BWP indication, MCS, new data indication, redundancy version, HARQ process number, HARQ timing, and TPC commands. , antenna port, precoding and number of layers, SRS request, CSI request.
  • CPE mainly transmits large-package services.
  • CPE is mainly a static scene, and the channel state is relatively stable, so frequency-domain frequency hopping and VRB-to-PRB interleaving mapping may not be performed, that is, DCI parameters may not include frequency-domain frequency hopping indication and VRB-to-PRB mapping. Signaling overhead.
  • the DCI parameters corresponding to the CPE may also include frequency domain resource allocation, time domain resource allocation, frequency domain frequency hopping indication, VRB-to-PRB mapping, PRB bundle size indication, MCS, new data indication, redundancy version, Precoding and number of layers, antenna ports.
  • the channel state is relatively stable, so the DCI parameter may not include the SRS request and the CSI request.
  • the complexity and signaling overhead can be reduced, communication requirements can be met, and communication efficiency can be improved.
  • the DCI parameters included in the DCI can be customized, and the DCI parameters included in the DCI can be customized according to the terminal type or terminal device, so as to match the parameter requirements with the communication requirements of the terminal type, and optimally meet the communication requirements of various devices. , reduce signaling overhead, reduce storage overhead, and improve spectral efficiency.
  • the DCI parameter set corresponding to the uplink communication may be determined for the terminal type according to the uplink communication requirement of the terminal type, and/or the DCI parameter set corresponding to the downlink communication may be determined for the terminal type according to the downlink communication requirement of the terminal type.
  • the terminal device and/or the network device may determine the DCI parameter according to the terminal type and the communication link.
  • the embodiments of the present application may be used as independent embodiments, or may be combined with other embodiments in the present application, which are not specifically limited in the present application.
  • the communication link in this embodiment of the present application may include one or more of the following: an uplink communication link, a downlink communication link, a duplex communication link, a backhaul communication link, a side link, an access link, a middle Continue the communication link, etc.
  • the descriptions in the embodiments of the present application are exemplified in the upper row and the lower row.
  • the communication link DCI may refer to a DCI used to schedule data transmission of the communication link.
  • it may include one or more of the following: uplink DCI, downlink DCI, duplex DCI, backhaul DCI, sidelink DCI, access link DCI, relay DCI, and the like.
  • the terminal type, the communication link and the DCI parameters have a corresponding relationship, wherein the corresponding relationship can be predefined by the protocol, or the network device can notify the terminal device through high-level signaling or physical layer signaling.
  • this application This is not limited.
  • terminal type A may correspond to the uplink DCI parameter set AD1, corresponding to the downlink DCI parameter set AD2; terminal type B may correspond to the uplink DCI parameter set BD1, corresponding to the downlink DCI parameter set BD2; ...; terminal type X may correspond to the uplink DCI parameter set XD1 , corresponding to the downlink DCI parameter set XD2.
  • the uplink DCI parameters corresponding to eMBB may include DCI format indication (uplink and downlink indication), carrier indication field, BWP indication, frequency domain resource allocation, time domain resource allocation, and frequency domain frequency hopping indication. , VRB-to-PRB mapping, PRB bundle size indication, MCS, new data indication, redundancy version, HARQ process number, HARQ timing, TPC command, uplink or supplementary uplink indication, precoding and layer number, antenna port.
  • DCI format indication uplink and downlink indication
  • BWP indication carrier indication field
  • BWP indication frequency domain resource allocation
  • time domain resource allocation time domain resource allocation
  • frequency domain frequency hopping indication frequency domain frequency hopping indication.
  • VRB-to-PRB mapping PRB bundle size indication
  • MCS new data indication
  • redundancy version redundancy version
  • HARQ process number HARQ timing
  • TPC command uplink or supplementary uplink indication
  • precoding and layer number antenna port.
  • the downlink DCI parameters corresponding to eMBB may include DCI format indication (uplink and downlink indication), carrier indication field, BWP indication, frequency domain resource allocation, time domain resource allocation, frequency domain frequency hopping indication, VRB-to-PRB mapping , PRB bundle size indication, MCS, new data indication, redundancy version, HARQ process number, HARQ timing, TPC command, uplink or supplementary uplink indication, precoding and layer number, antenna port, SRS request, CSI request, CBG transmission information .
  • DCI format indication uplink and downlink indication
  • BWP indication carrier indication field
  • BWP indication frequency domain resource allocation
  • time domain resource allocation time domain resource allocation
  • frequency domain frequency hopping indication VRB-to-PRB mapping
  • PRB bundle size indication MCS
  • new data indication redundancy version
  • HARQ process number HARQ timing
  • TPC command uplink or supplementary uplink indication
  • precoding and layer number antenna port
  • SRS request CSI request
  • CBG transmission information eMBB
  • the uplink DCI parameters corresponding to the URLLC may include frequency domain resource allocation, MCS, new data indication, and redundancy version.
  • the downlink DCI parameters corresponding to the URLLC may include frequency domain resource allocation, MCS, new data indication, redundancy version, and CSI request.
  • the uplink DCI parameters corresponding to IoT may include MCS, new data indication, and redundancy version.
  • the downlink DCI parameters corresponding to NB-IoT may include MCS, new data indication, redundancy version, and CSI request.
  • the uplink DCI parameters corresponding to the CPE may include frequency domain resource allocation, time domain resource allocation, frequency domain frequency hopping indication, VRB-to-PRB mapping, PRB bundle size indication, MCS, new Data indication, redundancy version, precoding and number of layers, antenna ports.
  • the downlink DCI parameters corresponding to the CPE may include frequency domain resource allocation, time domain resource allocation, frequency domain frequency hopping indication, VRB-to-PRB mapping, PRB bundle size indication, MCS, new data indication, redundancy version, Precoding and number of layers, antenna ports, SRS request, CSI request.
  • the above embodiment it is possible to design the customization of DCI parameters included in the DCI of different communication links, customize the DCI parameters included in the DCI according to the terminal type or the requirements of different communication links of the terminal equipment, and realize the parameter requirements and terminal types.
  • the communication link requirements are matched to optimally meet the communication link requirements of various devices, reduce signaling overhead, reduce storage overhead, and improve spectral efficiency.
  • a candidate set of values of DCI parameters corresponding to the terminal type may be further determined for the terminal type according to the communication requirements of the terminal type.
  • the terminal device and/or the network device may determine a candidate set of DCI parameter values according to the terminal type.
  • the embodiments of the present application may be used as independent embodiments, or may be combined with other embodiments in the present application, which are not specifically limited in the present application.
  • the terminal type has a corresponding relationship with the candidate set of DCI parameter values, wherein the corresponding relationship may be predefined by the protocol, or may be notified by the network device to the terminal device through high-level signaling or physical layer signaling.
  • determining the candidate set for the value of each DCI parameter corresponding to the terminal type for the terminal type according to the communication requirement of the terminal type includes: determining the number of bits corresponding to the candidate set for the value of the DCI parameter corresponding to the terminal type according to the terminal type; The terminal type determines at least one value in a candidate set of DCI parameter values corresponding to the terminal type.
  • the number of bits corresponding to the candidate set of TPC command values corresponding to the terminal type and the candidate set of TPC command values corresponding to the terminal type can be determined according to the terminal type.
  • the terminal device and/or the network device may determine, according to the terminal type, the number of bits corresponding to the candidate set of TPC command values and the candidate set of TPC command values corresponding to the terminal type.
  • the embodiments of the present application may be used as independent embodiments, or may be combined with other embodiments in the present application, which are not specifically limited in the present application.
  • the number of bits corresponding to the terminal type and the candidate set of DCI parameter values, and the candidate set of the value of the TPC command corresponding to the terminal type have a corresponding relationship, wherein the corresponding relationship may be predefined by the protocol, or may be the network
  • the device informs the terminal device through high-layer signaling or physical-layer signaling, which is not specifically limited in this application.
  • the number of bits corresponding to the candidate set of the value of the TPC command corresponding to the terminal type A is AT1
  • the candidate set of the value of the corresponding TPC command is the candidate set T1
  • the candidate set of the value of the TPC command corresponding to the terminal type B The corresponding number of bits is AT2
  • the candidate set for the value of the corresponding TPC command is the candidate set T2
  • the number of bits corresponding to the candidate set for the value of the TPC command corresponding to the terminal type X is ATX
  • the corresponding candidate set for the value of the TPC command is ATX.
  • the candidate set of values is the candidate set TX.
  • the number of bits corresponding to the candidate set of values of the TPC command may be at least 1 bit.
  • the candidate set of the value of the TPC command may include the value of 1 and the value of 2; when the number of bits corresponding to the candidate set of the value of the TPC command is In the case of 2 bits, the candidate set of values of the TPC command may include value 1, value 2, value 3, and value 4.
  • the number of bits corresponding to the candidate set of values of the TPC command corresponding to the eMBB may be determined according to the communication requirement of the eMBB.
  • the number of bits corresponding to the candidate set of TPC command values corresponding to eMBB may be 2 bits, and the candidate set of TPC command values may include value 1, value 2, value 3, and value 4.
  • the TPC command is 00
  • the value of the TPC command can be instructed to take the value 1
  • the TPC command is 01
  • the value of the TPC command can be instructed to take the value 2
  • the TPC command is 10
  • the value of the TPC command can be instructed
  • the value is 3
  • the value in the candidate set of the value of the TPC command corresponding to the eMBB may be determined according to the communication requirement of the eMBB.
  • the value 1 can be -1dB
  • the value 2 can be 0dB
  • the value 3 can be 1dB
  • a value of 4 can be 3dB.
  • the value 1 may be -4dB
  • the value 2 may be -1dB
  • the value 3 It can be 1dB
  • the value of 4 can be 4dB.
  • the number of bits corresponding to the candidate set of values of the TPC command corresponding to the URLLC may be determined according to the communication requirement of the URLLC.
  • the number of bits corresponding to the candidate set of the value of the TPC command corresponding to the URLLC may be 1 bit, and the candidate set of the value of the TPC command may include the value 1 and the value 2.
  • the TPC command is 0, the value of the TPC command can be instructed to take the value of 1; when the TPC command is 1, the value of the TPC command can be instructed to take the value of 2.
  • the value in the candidate set of the value of the TPC command corresponding to the URLLC can be determined according to the communication requirement of the URLLC.
  • the value 1 may be -1dB, and the value 2 may be 0dB.
  • the value of 1 may be -1dB, and the value of 2 may be 1dB.
  • the number of bits corresponding to the candidate set of values of the TPC command corresponding to NB-IoT may be determined according to the communication requirement of NB-IoT.
  • the number of bits corresponding to the candidate set of the value of the TPC command corresponding to NB-IoT may be 1 bit, and the candidate set of the value of the TPC command may include the value of 1 and the value of 2.
  • the TPC command is 0, the value of the TPC command can be instructed to take the value of 1; when the TPC command is 1, the value of the TPC command can be instructed to take the value of 2.
  • the value in the candidate set of the value of the TPC command corresponding to the NB-IoT can be determined according to the communication requirement of the NB-IoT.
  • the value 1 may be 0dB, and the value 2 may be 1dB.
  • the value of 1 may be 1dB, and the value of 2 may be 4dB.
  • the number of bits corresponding to the candidate set of values of the TPC command corresponding to the CPE may be determined according to the communication requirement of the CPE.
  • the number of bits corresponding to the candidate set of the value of the TPC command corresponding to the CPE may be 1 bit, and the candidate set of the value of the TPC command may include the value 1 and the value 2.
  • the TPC command is 0, the value of the TPC command can be instructed to take the value of 1; when the TPC command is 1, the value of the TPC command can be instructed to take the value of 2.
  • the value in the candidate set of the value of the TPC command corresponding to the CPE may be determined according to the communication requirement of the CPE.
  • the value 1 may be -1dB, and the value 2 may be 0dB.
  • the value of 1 may be -1dB, and the value of 2 may be 1dB.
  • the number of bits corresponding to the candidate set of MCS values corresponding to the terminal type and the candidate set of MCS values corresponding to the terminal type may be determined according to the terminal type.
  • the number of bits corresponding to the candidate set of MCS values corresponding to terminal type A is AM1
  • the corresponding candidate set of MCS values is candidate set M1
  • the bits corresponding to the candidate set of MCS values corresponding to terminal type B The number is AM2
  • the candidate set of the corresponding MCS value is the candidate set M2; ...
  • the number of bits corresponding to the candidate set of the MCS value corresponding to the terminal type X is AMX
  • the corresponding candidate set of the MCS value is the candidate set Set MX.
  • the number of bits corresponding to the candidate set of MCS values may be at least 1 bit.
  • the candidate set of the value of MCS may include the value of 1 and the value of 2;
  • the candidate set of the value of MCS may include the value of 1, the value of 2, the value of 3 and the value of 4;
  • the candidate set of the value of MCS It can include value 1, value 2, value 3, value 4, value 5, value 6, value 7, value 8.
  • the number of bits corresponding to the candidate set of MCS values corresponding to the eMBB may be determined according to the communication requirement of the eMBB.
  • the number of bits corresponding to the candidate set of MCS values corresponding to eMBB may be 5 bits, and the candidate set of MCS values may include values of 0, 1, . . . , and 31.
  • MCS 00000
  • the value of MCS can be instructed to be 0
  • MCS 00001
  • the value of MCS can be instructed to be 1
  • ... when MCS is 11111, the value of MCS can be instructed to be 1 value 31.
  • the value in the candidate set of the value of the MCS corresponding to the eMBB may be determined according to the communication requirement of the eMBB.
  • the candidate set of MCS values may be one or more of the following Tables 1 to 3.
  • the candidate set of MCS values may include one or more rows in the following Tables 1 to 3.
  • the number of bits corresponding to the candidate set of MCS values corresponding to the URLLC may be determined according to the communication requirement of the URLLC.
  • the number of bits corresponding to the candidate set of MCS values corresponding to URLLC may be 3 bits, and the candidate sets of MCS values may include values 0, 1, . . . , and 7.
  • MCS 000, it can be indicated that the value of MCS is 0; when MCS is 001, it can be indicated that the value of MCS is 1; ...; when MCS is 111, it can be indicated that the value of MCS is 0 value 7.
  • the value in the candidate set of the value of the MCS corresponding to the URLLC may be determined according to the communication requirement of the URLLC.
  • the candidate set of MCS values may be the following Table 4.
  • the number of bits corresponding to the candidate set of MCS values corresponding to NB-IoT may be determined according to the communication requirement of NB-IoT.
  • the number of bits corresponding to the candidate set of MCS values corresponding to NB-IoT may be 2 bits, and the candidate sets of MCS values may include values 0, 1, 2, and 3.
  • MCS When MCS is 00, it can be indicated that the value of MCS is 0; when MCS is 01, it can be indicated that the value of MCS is 1; when MCS is 10, it can be indicated that the value of MCS is 2 ; When MCS is 11, the value of MCS can be instructed to be 3.
  • the value in the candidate set of the value of the MCS corresponding to the NB-IoT can be determined according to the communication requirement of the NB-IoT.
  • the candidate set of MCS values may be the following Table 5.
  • the number of bits corresponding to the candidate set of the MCS value is 2 bits or 3 bits, it can correspond to a specific MCS value, which is suitable for artificial intelligence training (artificial intelligence training, AI training), factory scenarios, etc. Scenarios where the channel and interference are relatively stable.
  • the network device sends the uplink specific MCS value to the terminal device, and the terminal device sends the downlink specific MCS value to the network device; or the network device sends the uplink specific MCS value to the terminal device.
  • the value of the specific MCS of the downlink and the value of the specific MCS of the downlink are the values of the specific MCS of the downlink.
  • the network device and/or the terminal device may adopt the following methods In one or more of the manners 1 to 4, a DCI parameter corresponding to the terminal type and a candidate set of DCI parameter values are determined.
  • Manner 1 The DCI parameter corresponding to the terminal type and the candidate set of the value of the DCI parameter are predetermined by the communication protocol.
  • a training model such as machine learning and neural network can be used to determine the RRC parameter corresponding to the terminal type, and each DCI parameter corresponding to the terminal type and a candidate set of DCI parameter values for the terminal type.
  • the DCI parameter corresponding to the terminal type and the candidate for the value of each DCI parameter corresponding to the terminal type may be determined according to the value of the DCI parameter configured for each terminal device by the network device within a period of time according to the communication requirements of each terminal device. set.
  • DCI parameters corresponding to the terminal type and a candidate set of values of each DCI parameter corresponding to the terminal type may also be determined according to communication experience.
  • the communication quality of the terminal device under different combinations of DCI parameters and/or different candidate sets of DCI parameter values can be determined through a training model such as machine learning or neural network, and the DCI parameters corresponding to the terminal type are determined according to the communication quality, and the terminal A candidate set of values for each DCI parameter corresponding to the type.
  • the terminal type A including terminal equipment 1, terminal equipment 2 and terminal equipment 3 it can be determined according to the DCI parameter values configured by the network equipment for terminal equipment 1, terminal equipment 2 and terminal equipment 3 within a period of time.
  • the DCI parameter corresponding to each terminal type and the candidate set of DCI parameter values can be written into the communication protocol, so that the network device and the terminal device can determine the DCI parameter and the DCI parameter corresponding to the terminal type of the terminal device according to the communication protocol.
  • the candidate set of values prevents the network device from sending the DCI parameter corresponding to the terminal type and the candidate set of DCI parameter values to the terminal device, saving signaling overhead, reducing communication delay, and reducing terminal power consumption.
  • Mode 2 The network device sends indication information to the terminal device.
  • the indication information may be used to indicate a DCI parameter corresponding to the terminal type and a candidate set of values of the DCI parameter.
  • the network device may determine the DCI parameter corresponding to the terminal type and a candidate set of DCI parameter values according to the terminal type of the terminal device during the random access process or when the terminal device initially accesses the network, and assign the terminal type corresponding to the DCI parameter.
  • the DCI parameter and the candidate set of DCI parameter values are delivered to the terminal device.
  • the network device may send the DCI parameter and the candidate set of DCI parameter values through high-layer signaling or physical layer signaling, and the terminal device determines the candidate set of DCI parameters and DCI parameter values according to the instruction of the network device.
  • the network device can configure the DCI parameter and the candidate set of DCI parameter values, realize the configuration flexibility of the DCI parameter and the candidate set of the DCI parameter value, better adapt to different scenarios, and meet the needs of different scenarios , reducing the overhead of value indication and improving communication efficiency.
  • the network device may determine the DCI parameter corresponding to the terminal type and the candidate set of DCI parameter values by using the method shown in the first manner, which will not be repeated.
  • the network device may determine the value of the TPC command corresponding to the terminal type according to the terminal type of the terminal device during the random access process or when the terminal device initially accesses the network.
  • the number of bits corresponding to the candidate set and the value of the TPC command in the candidate set are sent to the terminal device.
  • the network device may determine a candidate set of values of the MSC corresponding to the terminal type according to the terminal type of the terminal device during the random access process or when the terminal device initially accesses the network.
  • the corresponding number of bits and the value of the MSC in the candidate set are sent to the terminal equipment.
  • Manner 3 The terminal device sends second request information to the network device, and the network device sends the terminal device according to the second request information, a DCI parameter corresponding to the terminal type and a candidate set of DCI parameter values.
  • the second request information is used to request a DCI parameter corresponding to a terminal type of the terminal device and a candidate set of values of the DCI parameter.
  • the second request information includes a DCI parameter corresponding to the terminal type determined by the terminal device and a candidate set of values of the DCI parameter.
  • the terminal device may determine a DCI parameter and a candidate set of DCI parameter values suitable for its own communication according to its own communication requirements, and send the DCI parameter and the candidate set of DCI parameter values to the network device.
  • the network device receives the DCI parameter and the candidate set of DCI parameter values sent by the terminal device, it determines whether the terminal device can use the DCI parameter and the candidate set of DCI parameter values, and if so, determines whether the DCI parameter and the DCI parameter value candidate set can be used by the terminal device.
  • the candidate set of DCI parameter values is sent to the terminal device as a candidate set of DCI parameters corresponding to the terminal type and DCI parameter values. If not, the network device can determine the DCI corresponding to the terminal type according to the terminal type of the terminal device. parameters and candidate sets of DCI parameter values, and send the DCI parameters and the candidate set of DCI parameter values to the terminal device.
  • both the network device and the terminal device may use the method described in the above-mentioned way 1 to determine the DCI parameter corresponding to the terminal type and the candidate set of DCI parameter values, which will not be repeated.
  • the terminal device may send the number of bits corresponding to the candidate set of the value of the TPC command determined by the terminal device and the value of the TPC command in the candidate set to the network device.
  • the number of bits corresponding to the candidate set of the value of the TPC command sent by the device and the value of the TPC command in the candidate set and determine whether the terminal device can use the number of bits corresponding to the candidate set of the value of the TPC command and the value of the TPC command in the candidate set.
  • the network device can determine the number of bits corresponding to the candidate set of the value of the TPC command corresponding to the terminal type and the TPC command in the candidate set according to the terminal type of the terminal device.
  • value of the TPC command, and the number of bits corresponding to the candidate set of the value of the TPC command and the value of the TPC command in the candidate set are sent to the terminal device.
  • the terminal device may send the number of bits corresponding to the candidate set of the MCS value determined by the terminal device and the value of the MCS in the candidate set to the network device.
  • the number of bits corresponding to the candidate set of the MCS value and the value of the MCS in the candidate set to determine whether the terminal device can use the number of bits corresponding to the candidate set of the MCS value and the value of the MCS in the candidate set, if possible.
  • the number of bits corresponding to the candidate set of the value of the MCS and the value of the MCS in the candidate set are sent to the terminal equipment as the number of bits corresponding to the candidate set of the value of the MCS corresponding to the terminal type and the value of the MCS in the candidate set , if not, the network device can determine the number of bits corresponding to the candidate set of the value of the MCS corresponding to the terminal type and the value of the MCS in the candidate set according to the terminal type of the terminal device, and the candidate set of the value
  • the terminal device can send the proposed DCI parameter and the candidate set of DCI parameter values to the network device, so as to realize the configuration flexibility of the DCI parameter and the candidate set of DCI parameter values, and better meet the communication requirements of the terminal device. It can better adapt to different scenarios, meet the needs of different scenarios, reduce the overhead of value indication, and improve communication efficiency.
  • the terminal device sends second feature information to the network device, and the network device sends to the terminal device a DCI parameter corresponding to the terminal type and a candidate set of DCI parameter values according to the second feature information.
  • the second feature information may be used to indicate the terminal type of the terminal device.
  • the second feature information may be the terminal type of the terminal device, or a communication requirement used to indicate the terminal type of the terminal device, and the communication requirement may be service type, mobility, transmission delay requirement, channel environment, reliability One or more of sexual requirements, coverage requirements, and communication scenarios.
  • the network device may determine the terminal type of the terminal device according to the second feature information sent by the terminal device, and determine the DCI parameter corresponding to the terminal type and a candidate set of DCI parameter values, and determine the DCI parameter and the DCI parameter value.
  • a candidate set of values is sent to the end device.
  • the terminal device may send second characteristic information to the network device, and the network device determines the terminal type of the terminal device according to the second characteristic information, and determines the TPC command corresponding to the terminal type.
  • the number of bits corresponding to the candidate set of values and the value of the TPC command in the candidate set are sent to the terminal device.
  • the terminal device may send second characteristic information to the network device, and the network device determines the terminal type of the terminal device according to the second characteristic information, and determines the value of the MCS corresponding to the terminal type.
  • the number of bits corresponding to the candidate set and the value of the MCS in the candidate set, and the number of bits corresponding to the candidate set of the MCS value and the value of the MCS in the candidate set are sent to the terminal device.
  • the candidate set of DCI parameters and the values of the DCI parameters can be determined by the second characteristic information, and the configuration of the candidate sets of the values of the DCI parameters and the DCI parameters can be realized. Flexibility, better meet the communication needs of terminal equipment, better adapt to different scenarios, meet the needs of different scenarios, reduce the overhead of value indication, and improve communication efficiency.
  • a candidate set of DCI parameter values corresponding to the terminal type may be determined for the terminal type, and corresponding to the terminal type.
  • the candidate set of values of the DCI parameters determines the first DCI corresponding to the terminal type.
  • the first DCI may include the MCS parameter and the HARQ process number, wherein the number of bits corresponding to the candidate set of the value of the MCS parameter is 5; the candidate set of the value of the HARQ process number corresponds to The number of bits is 4.
  • the first DCI may include an MCS parameter, a HARQ process number, an SRS request, and a CSI request, wherein the number of bits corresponding to the candidate set of values of the MCS parameter is 2 or 3; the HARQ process The number of bits corresponding to the candidate set of the value of the number is 1; the number of bits corresponding to the candidate set of the value of the SRS request is 1; the number of bits corresponding to the candidate set of the value of the CSI request is 1.
  • the candidate set for the value of the MCS parameter can include 4 or 8 values, that is, the corresponding number of bits is 2 or 3. Compared with The number of bits is 5, which can reduce signaling overhead.
  • URLLC can generally use low-rate transmission. Therefore, only a single antenna port can be used for rank 1 transmission, which reduces power consumption, reduces signaling overhead, and improves communication efficiency. That is, the DCI parameters may not include precoding information, the number of layers, and the antenna ports, thereby reducing signaling overhead.
  • DCI parameters can include SRS requests and CSI requests.
  • the measurement situation is relatively simple, and a 1-bit SRS request and a 1-bit CSI request can be configured. Compared with the configuration of more SRS or CSI in eMBB, signaling overhead can be reduced and communication efficiency can be improved.
  • the data packets of URLLC are mainly small packets, so fewer HARQ processes can be used, and when the HARQ process number indication is performed, signaling overhead can be reduced and communication efficiency can be improved.
  • the first DCI may include the MCS parameter and the HARQ process number, wherein the number of bits corresponding to the candidate set of the value of the MCS parameter is 2 or 3; the value of the HARQ process number parameter is 2 or 3. The number of bits corresponding to the candidate set is 1 or 2.
  • the candidate set for the value of the MCS parameter can include 4 or 8 values, that is, the corresponding number of bits is 2 or 3, compared to Since the number of bits is 5, signaling overhead can be reduced.
  • the data packets of URLLC are mainly small packets, so fewer HARQ processes can be used, and when the HARQ process number indication is performed, signaling overhead can be reduced and communication efficiency can be improved.
  • the first DCI may include the MCS parameter and the HARQ process number, wherein the number of bits corresponding to the candidate set of the value of the MCS parameter is 2, 3, 4 or 5; the HARQ process number parameter The number of bits corresponding to the candidate set of values is 4.
  • the candidate set of the value of the MCS parameter can include 4 or 8 values, that is, the corresponding number of bits is 2 or 3. Compared with the number of bits, it can be 5. Reduce signaling overhead.
  • the number of values in the value candidate set of the MCS parameter can be flexibly configured, which is suitable for different communication scenarios, and reduces signaling overhead while meeting different communication requirements.
  • the data packets of the CPE are mainly large packets, so more HARQ processes can be used to improve communication efficiency.
  • the candidate set of DCI parameters and the values of DCI parameters can be determined according to the terminal type, so as to realize the configuration flexibility of the candidate sets of DCI parameters and the values of DCI parameters, so as to better meet the communication requirements of terminal equipment, and better It can adapt to different scenarios, meet the needs of different scenarios, reduce the overhead of value indication, and improve communication efficiency.
  • Step 502 the terminal device communicates according to the first DCI.
  • the terminal device may determine the value of each DCI parameter in the first DCI according to the candidate set of DCI parameter values corresponding to the terminal type of the terminal device and the first DCI, and determine the value of each DCI parameter in the first DCI according to the value of each DCI parameter in the first DCI. value for communication.
  • the network device may not send the first value to the terminal device.
  • a DCI parameter the terminal device and the network device may determine that the value of the first DCI parameter is the first value.
  • the network device may not notify the terminal device. Send the first value.
  • the terminal device and the network device may determine that the value of the first DCI parameter is a default value.
  • the default value includes the value of the first DCI parameter corresponding to the terminal type in the value candidate set of the first DCI parameter. That is, when the network device does not indicate the value of the first DCI parameter to the terminal device, the value of the first DCI parameter is the default value, or, when the terminal device does not receive the value of the first DCI parameter indicated by the network device , the value of the first DCI parameter is the default value.
  • the default value of the first DCI parameter may be predefined by the protocol, or may be notified by the network device to the terminal device through high layer signaling or physical layer signaling.
  • the network device by determining the DCI parameters included in the DCI corresponding to the terminal type and the candidate set of DCI parameter values according to the terminal type, the network device can be made to determine the DCI parameters for the terminal device from the candidate set of DCI parameter values. , reduce signaling overhead, reduce storage overhead of terminal equipment, meet the communication requirements of different terminal types, and reduce power consumption of terminal equipment.
  • the first DCI may be on the same symbol as the data channel, that is, single-symbol transmission.
  • the embodiments of the present application may be used as independent embodiments, or may be combined with other embodiments in the present application, which are not specifically limited in the present application.
  • the DMRS of the control channel and the DMRS of the data channel may be shared.
  • the frequency domain position of the control channel has a corresponding relationship with the frequency domain position of the data channel.
  • the relationship between the frequency domain position of the data channel and the frequency domain position of the control channel can be predefined, so as to reduce the indication overhead of the frequency domain position of the data channel and improve communication efficiency.
  • the frequency domain position of the data channel can be determined by indicating the offset of the frequency domain position of the data channel and the frequency domain position of the control channel, thereby reducing the indication overhead of the frequency domain position of the data channel and improving communication efficiency.
  • the pilot overhead can be reduced. For example, if configuration 1 is adopted, the pilot overhead can be increased by 50%, and if configuration 2 is adopted, the pilot overhead can be increased by 33%. overhead.
  • the frequency domain position of the DCI may be determined by means of frequency domain position indication or fixed position, such as frequency domain interleaving/non-interleaving. And without the need for time domain location indication, the scheduling and transmission of small data can be quickly realized, saving communication delay.
  • the communication method provided by the embodiment of the present application may be described from the perspective of the first communication device.
  • FIG. 5b is a flowchart of a communication method provided by an embodiment of the present application. As shown in FIG. 5b, the method may include:
  • Step 501a the first communication apparatus determines a DCI parameter corresponding to the terminal type of the first communication apparatus and a candidate set of values of the DCI parameter.
  • the DCI parameters corresponding to the terminal type of the first communication apparatus determined by the first communication apparatus and the candidate set of DCI parameter values reference may be made to the DCI parameters corresponding to the terminal type of the terminal equipment determined by the terminal equipment in step 501 above. And the specific description of the candidate set for the value of the DCI parameter will not be repeated.
  • this step can be omitted.
  • Step 502a the first communication device sends the second request information and/or the second feature information.
  • this step can be omitted.
  • Step 503a The first communication apparatus receives the DCI parameter corresponding to the terminal type and a candidate set of values of the DCI parameter.
  • the candidate set of the DCI parameters corresponding to the terminal type and the values of the DCI parameters received by the first communication device reference may be made to the candidate set for the terminal equipment to receive the DCI parameters corresponding to the terminal type and the values of the DCI parameters in step 501 above. The relevant description of the set will not be repeated.
  • Step 504a the first communication device receives the first DCI.
  • Step 505a the first communication device communicates according to the first DCI.
  • the communication method provided by this embodiment of the present application may be described from the perspective of the second communication device.
  • FIG. 5c is a flowchart of a communication method provided by an embodiment of the present application. As shown in FIG. 5c, the method may include:
  • Step 501b the second communication apparatus receives the second request information and/or the second feature information.
  • this step can be omitted.
  • Step 502b the second communication apparatus determines a DCI parameter corresponding to the terminal type and a candidate set of values of the DCI parameter.
  • the candidate set of the DCI parameter corresponding to the terminal type and the value of the DCI parameter determined by the second communication device reference may be made to the candidate set of the DCI parameter corresponding to the terminal type and the value of the DCI parameter determined by the network device in step 501 above. The specific description of the set will not be repeated.
  • Step 503b The second communication apparatus sends the DCI parameter corresponding to the terminal type and a candidate set of values of the DCI parameter.
  • Step 504b the second communication device sends the first DCI.
  • the embodiment of the present application may also determine the DCI format corresponding to the terminal type based on the DCI parameter corresponding to the terminal type and the candidate set of DCI parameter values.
  • the embodiments of the present application may be used as independent embodiments, and may also be combined with other embodiments in the present application, which are not specifically limited in the present application.
  • the DCI format F1 corresponding to terminal type 1 can be determined according to the DCI parameters corresponding to terminal type 1 and the candidate set of DCI parameter values; for terminal type 2, the DCI parameter corresponding to terminal type 2 can be determined according to And the candidate set of the value of the DCI parameter, determine the DCI format F2 corresponding to the terminal type 1; ...; for the terminal type X, according to the candidate set of the DCI parameter corresponding to the terminal type 1 and the value of the DCI parameter, determine the terminal type 1.
  • the corresponding DCI format FX can be determined according to the DCI parameters corresponding to terminal type 1 and the candidate set of DCI parameter values
  • the corresponding uplink DCI format and downlink DCI format may be determined for the terminal type.
  • the uplink DCI format UF1 corresponding to terminal type 1 can be determined according to the DCI parameters corresponding to terminal type 1 during uplink communication and the candidate set of DCI parameter values, and the DCI format UF1 corresponding to terminal type 1 during downlink communication can be determined.
  • the candidate set of parameters and DCI parameter values determine the uplink DCI format DF1 corresponding to terminal type 1; for terminal type 2, determine Uplink DCI format UF2 corresponding to terminal type 1, according to the corresponding DCI parameters and the candidate set of DCI parameter values during downlink communication of terminal type 2, determine the uplink DCI format DF2 corresponding to terminal type 2; ...; for terminal type X, you can Determine the uplink DCI format UF1 corresponding to the terminal type X according to the corresponding DCI parameters and the candidate set of the values of the DCI parameters during the uplink communication of the terminal type X.
  • the candidate set determines the uplink DCI format DFX corresponding to the terminal type X.
  • terminal type 1, terminal type 2, ..., terminal type X may be at least one of the above terminal types, such as eMBB, URLLC, IoT, CPE, V2X, AR/VR, etc.
  • a DCI format may also be determined based on a terminal type, and a DCI parameter corresponding to the DCI and a candidate set of DCI parameter values may be determined based on the DCI format.
  • the embodiments of the present application may be used as independent embodiments, or may be combined with other embodiments in the present application, which are not specifically limited in the present application.
  • the terminal type and/or the network device may determine the DCI format according to the terminal type, and determine the DCI parameter corresponding to the DCI and a candidate set of DCI parameter values according to the DCI format.
  • the terminal type has a corresponding relationship with the DCI format.
  • the corresponding relationship may be predefined by the protocol, or may be notified by the network device to the terminal device through high-level signaling or physical layer signaling, which is not specifically limited in this application.
  • the DCI format has a corresponding relationship with the DCI parameter and the candidate set of values of the DCI parameter.
  • the corresponding relationship may be predefined by the protocol, or may be notified by the network device to the terminal device through high-level signaling or physical layer signaling, which is not specifically limited in this application.
  • the DCI format F1 corresponding to terminal type 1 can be determined according to terminal type 1, the DCI parameters corresponding to DCI and the candidate set of DCI parameter values determined according to the DCI format F1;
  • the terminal type 2 determines the DCI format F2 corresponding to the terminal type 1, and determines the DCI parameter corresponding to the DCI and the candidate set of DCI parameter values according to the DCI format F2; ...;
  • the corresponding terminal type X can be determined according to the terminal type X.
  • the DCI format FX is determined according to the DCI format FX to determine the DCI parameter corresponding to the DCI and the candidate set of the value of the DCI parameter.
  • the corresponding uplink DCI format and downlink DCI format may be determined for the terminal type.
  • a DCI format may also be determined based on a terminal type and a communication link, and a DCI parameter corresponding to the DCI and a candidate set of DCI parameter values may be determined based on the DCI format.
  • the embodiments of the present application may be used as independent embodiments, or may be combined with other embodiments in the present application, which are not specifically limited in the present application.
  • the terminal type and/or the network device may determine the DCI format according to the terminal type and the communication link, and determine the DCI parameter corresponding to the DCI and a candidate set of DCI parameter values according to the DCI format.
  • the terminal type and communication link have a corresponding relationship with the DCI format.
  • the corresponding relationship may be predefined by the protocol, or may be notified by the network device to the terminal device through high-level signaling or physical layer signaling, which is not specifically limited in this application.
  • the DCI format has a corresponding relationship with the DCI parameter and the candidate set of values of the DCI parameter.
  • the corresponding relationship may be predefined by the protocol, or may be notified by the network device to the terminal device through high-level signaling or physical layer signaling, which is not specifically limited in this application.
  • the uplink DCI format UF1 corresponding to terminal type 1 can be determined according to terminal type 1
  • the DCI parameters corresponding to DCI during uplink communication and the candidate set of DCI parameter values during uplink communication can be determined according to the uplink DCI format UF1, and according to the terminal type 1.
  • the upstream DCI format UF2 is determined according to the upstream DCI format UF2, and the DCI parameters corresponding to the DCI and the candidate set of the values of the DCI parameters in the upstream communication are determined according to the upstream DCI format UF2, and the downstream DCI format DF2 corresponding to the terminal type 2 is determined according to the terminal type 2.
  • the uplink DCI format UF1 corresponding to terminal type X can be determined according to terminal type X, and uplink communication can be determined according to uplink DCI format UF1
  • the downlink DCI format DFX corresponding to the terminal type X according to the terminal type X
  • terminal type 1, terminal type 2, ..., terminal type X may be at least one of the above terminal types, such as eMBB, URLLC, IoT, CPE, V2X, AR/VR, etc.
  • the DCI format corresponding to eMBB may be format one, wherein the DCI parameter corresponding to format one and the candidate set of DCI parameter values are as follows: bits corresponding to the candidate set of values of the MCS parameter The number of bits is 5; the number of bits corresponding to the candidate set of the value of the HARQ process ID parameter is 4.
  • the DCI format corresponding to URLLC may be format 2, wherein the DCI parameter corresponding to format 2 and the candidate set of the value of the DCI parameter are as follows: bits corresponding to the candidate set of the value of the MCS parameter The number of bits is 2 or 3; the number of bits corresponding to the candidate set of the value of the HARQ process number parameter is 1; the number of bits corresponding to the candidate set of the value of the SRS request parameter is 1, and the number of bits corresponding to the candidate set of the value of the CSI request parameter The number of bits is 1.
  • the DCI format corresponding to IoT may be format 3, wherein the DCI parameters corresponding to format 3 and the candidate set of DCI parameter values are as follows: bits corresponding to the candidate set of MCS parameter values. The number of bits is 2 or 3; the number of bits corresponding to the candidate set of the value of the HARQ process ID parameter is 1 or 2.
  • the DCI format corresponding to IoT may be format 4, wherein the DCI parameters corresponding to format 4 and the candidate set of DCI parameter values are as follows: bits corresponding to the candidate set of values of the MCS parameter The number is 2, 3, 4 or 5; the number of bits corresponding to the candidate set of the value of the HARQ process ID parameter is 4.
  • the network device may send the DCI format corresponding to the terminal type of the terminal device to the terminal device, so that the terminal device receives the DCI sent by the network device according to the DCI format corresponding to the terminal type of the terminal device.
  • the terminal device can also determine the candidate set of the value of the DCI parameter in the DCI format sent by the network device according to the corresponding relationship between the DCI format and the candidate set of the value of the DCI parameter, and the DCI format sent by the network device, and then The DCI is parsed according to the candidate set of values of the DCI parameter and the DCI sent by the network device.
  • the network device may send the first DCI format to the terminal device, so that the terminal device receives the first DCI format sent by the network device according to the first DCI format.
  • DCI and determine the candidate set of the value of the DCI parameter in the first DCI according to the corresponding relationship between the DCI format and the candidate set of the value of the DCI parameter, and the first DCI format, and according to the value of the DCI parameter in the first DCI
  • the candidate set of the value of the DCI parameter is determined.
  • the candidate set and the first DCI determine the value of each DCI parameter in the first DCI, and communicate based on the value of each DCI parameter in the first DCI.
  • the network device determines the DCI format corresponding to the terminal type according to the terminal type, which facilitates the terminal device to receive DCI according to the DCI format sent by the network device, improves the success rate of the terminal device receiving DCI, and facilitates the terminal device to receive DCI according to the DCI format.
  • the corresponding relationship between the candidate sets of DCI parameter values, and the received DCI is analyzed to meet the communication requirements of different terminal types, reduce signaling overhead, and improve communication quality.
  • each device includes corresponding hardware structures and/or software modules for performing each function.
  • the present application can be implemented in hardware or in the form of a combination of hardware and computer software, in conjunction with the algorithm steps of the examples described in the embodiments disclosed herein. Whether a function is performed by hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.
  • each device may be divided into functional modules according to the foregoing method examples.
  • each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module.
  • the above-mentioned integrated modules can be implemented in the form of hardware, and can also be implemented in the form of software function modules. It should be noted that, the division of modules in the embodiments of the present application is schematic, and is only a logical function division, and there may be other division manners in actual implementation.
  • FIG. 8 shows a terminal device
  • the terminal device 80 may include a processing module 801 and a transceiver module 802 .
  • the terminal device 80 may be a terminal device, or may be a chip applied in the terminal device or other combined devices, components and the like having the functions of the above-mentioned terminal device.
  • the processing module 801 may be a processor (or a processing circuit), such as a baseband processor, which may include one or more CPUs
  • the transceiver module 802 may be a transceiver. It can include antennas and radio frequency circuits, etc.
  • the processing module 801 may be a processor (or a processing circuit), such as a baseband processor, and the transceiver module 802 may be a radio frequency unit.
  • the processing module 801 may be a processor (or a processing circuit) of the chip system, and may include one or more central processing units, and the transceiver module 802 may be the input and output of a chip (eg, a baseband chip). interface.
  • processing module 801 in this embodiment of the present application may be implemented by a processor or a processor-related circuit component (or referred to as a processing circuit), and the transceiver module 802 may be implemented by a transceiver or a transceiver-related circuit component.
  • processing module 801 can be used to perform all operations performed by the terminal device in the embodiments shown in FIGS. 3a-7 except for the transceiving operations, and/or other processes used to support the techniques described herein
  • Transceiver module 802 may be used to perform all of the transceive operations performed by the terminal device in the embodiments shown in Figures 3a-7, and/or to support other processes of the techniques described herein.
  • the processing module 801 is configured to determine a first value candidate set; the first value candidate set corresponds to the terminal type of the terminal device; the first value candidate set includes the value candidates of the radio resource control RRC parameter corresponding to the terminal type
  • the transceiver module 802 is used for receiving the first value from the network device; wherein, the first value includes a set of RRC parameter values in the first value candidate set; the processing module 801 is used for receiving the first value according to the first value to communicate.
  • the types of RRC parameters corresponding to the terminal type include one or more of the following: configuration parameters for data transmission, configuration parameters for channel state information CSI measurement feedback, configuration parameters for initial access, mobile configuration parameters for power control, configuration parameters for power control, and configuration parameters for beam management.
  • the RRC parameter value candidate set is used to indicate the configuration mode of the RRC parameter; wherein, the configuration mode includes a configuration parameter field, and the configuration parameter field includes configuration parameters of the configuration mode; or, the configuration mode includes configuration parameters.
  • the transceiver module 802 is further configured to receive the first value candidate set from the network device.
  • the transceiver module 802 before the transceiver module 802 receives the first value candidate set from the network device, it is also used to send first request information to the network device; wherein, the first request information is used to request the RRC parameter corresponding to the terminal type.
  • the transceiver module 802 is further configured to send the first feature information to the network device, wherein the first feature information is used to indicate the terminal type.
  • the types of RRC parameters corresponding to the eMBB include data transmission configuration parameters, channel state information CSI measurement feedback configuration parameters, initial access configuration parameters, mobile characteristic configuration parameters, power control configuration parameters and beam management configuration parameters; and/or; when the terminal type is an ultra-reliable low-latency communication device URLLC, the type of RRC parameters corresponding to the URLLC includes data transmission configuration parameters, channel Configuration parameters of status information CSI measurement feedback and configuration parameters of beam management; and/or; when the terminal type is IoT device IoT, the types of RRC parameters corresponding to IoT include configuration parameters for data transmission, configuration parameters for initial access, Mobility configuration parameters; and/or; when the terminal type is customer premise equipment CPE, the types of RRC parameters corresponding to the CPE include configuration parameters for data transmission and configuration parameters for channel state information CSI measurement feedback.
  • the terminal type is an enhanced mobile broadband device eMBB
  • the types of RRC parameters corresponding to the eMBB include data transmission configuration parameters, channel state information CSI measurement feedback configuration parameters, initial access configuration parameters, mobile
  • the candidate set of subcarrier spacing configuration parameters in the configuration parameters of data transmission are 15kHz, 30kHz, 120kHz, and 240kHz;
  • the configuration parameters for CSI measurement feedback The candidate sets for the value of the CSI reporting time domain configuration parameter are periodic reporting, aperiodic reporting, and semi-persistent reporting;
  • the candidate sets for the value of the beam failure recovery timing parameter in the configuration parameters of beam management are 10ms, 20ms, 40ms, 60ms, 80ms, 100ms, 150ms, 200ms; and/or;
  • the candidate set of subcarrier spacing configuration parameters in the configuration parameters of data transmission is 30kHz, 60kHz, 120kHz;
  • the candidate set of the value of the CSI reporting time domain configuration parameter in the configuration parameters of the CSI measurement feedback is aperiodic reporting;
  • the terminal type is determined according to one or more of the following factors: service type, mobility, transmission delay requirements, channel environment, reliability requirements, coverage requirements, and communication scenarios.
  • processing module 801 and the transceiver module 802 in the terminal device 80 shown in FIG. 8 can also be used for:
  • the transceiver module 802 is configured to receive the first downlink control information DCI from the network device; the first DCI includes values of multiple DCI parameters; the DCI parameters included in the first DCI correspond to the terminal type of the terminal device; the values of the DCI parameters The candidate set of values corresponds to the terminal type; the candidate set includes at least one value of a DCI parameter corresponding to the terminal type; the processing module 801 is configured to communicate according to the first DCI.
  • the processing module 801 is further configured to determine the first DCI format; the first DCI format corresponds to the terminal type; the transceiver module 802 is further configured to receive the first DCI format from the network device according to the first DCI format. a DCI.
  • the processing module 801 is further configured to determine the candidate set of the value of the DCI parameter according to the corresponding relationship between the DCI format and the candidate set of the value of the DCI parameter, and the first DCI format.
  • the transceiver module 802 is further configured for the terminal device to receive indication information from the network device, wherein the indication information is used to indicate the DCI parameter corresponding to the terminal type and a candidate set of DCI parameter values.
  • the transceiver module 802 before the transceiver module 802 receives the indication information from the network device, it is also used for the terminal device to send second request information to the network device; wherein, the second request information is used to request the DCI parameter and DCI corresponding to the terminal type.
  • a candidate set of parameter values before the transceiver module 802 receives the indication information from the network device, it is also used for the terminal device to send second request information to the network device; wherein, the second request information is used to request the DCI parameter and DCI corresponding to the terminal type.
  • the transceiver module 802 is further configured to send second feature information to the network device, wherein the second feature information is used to indicate the terminal type.
  • the DCI parameters corresponding to eMBB include time domain resource allocation, frequency domain resource allocation, bandwidth part BWP indication, modulation and coding mode MCS, new data indication, redundancy redundant version, HARQ process number, HARQ timing, transmission power control TPC command, antenna port, precoding and number of layers, sounding reference signal SRS request, channel state information CSI request; and/or;
  • the terminal type is When the ultra-reliable and low-latency communication device URLLC is used, the DCI parameters corresponding to URLLC include time domain resource indication, frequency domain resource indication, modulation and coding mode MCS, new data indication, hybrid automatic repeat request HARQ process number, transmission power control command, Sounding reference signal SRS request, channel state information CSI request; and/or;
  • the DCI parameters corresponding to IoT include frequency domain resource indication, modulation and coding mode MCS, hybrid automatic repeat request HARQ process and/or;
  • the terminal type is enhanced mobile broadband equipment eMBB
  • the number of bits corresponding to the candidate set of the value of the MCS parameter is 5; the number of bits corresponding to the candidate set of the value of the HARQ process number parameter is 4;
  • the terminal type is an ultra-reliable low-latency communication device URLLC
  • the number of bits corresponding to the candidate set of the value of the MCS parameter is 2 or 3
  • the number of bits corresponding to the candidate set of the value of the HARQ process number parameter is 1
  • the number of bits corresponding to the candidate set of the value of the sounding reference signal SRS request parameter is 1
  • the number of bits corresponding to the candidate set of the value of the channel state information CSI request parameter is 1
  • the terminal type is the Internet of Things
  • the device is IoT
  • the number of bits corresponding to the candidate set of the value of the MCS parameter is 2 or 3; the number of bits corresponding to the candidate set of the value of the HARQ process number parameter is 1 or 2
  • the DCI format corresponding to the eMBB is format 1, wherein the DCI parameters corresponding to format 1 and the candidate sets of the values of the DCI parameters are as follows: Modulation and coding mode MCS The number of bits corresponding to the candidate set of the value of the parameter is 5; the number of bits corresponding to the candidate set of the value of the HARQ process ID parameter of the hybrid automatic repeat request is 4; and/or; when the terminal type is ultra-reliable and low-latency communication
  • the DCI format corresponding to URLLC is format 2, wherein the DCI parameter corresponding to format 2 and the candidate set of DCI parameter values are as follows: 3; the number of bits corresponding to the candidate set of the value of the HARQ process number parameter of the hybrid automatic repeat request is 1; the number of bits corresponding to the candidate set of the value of the sounding reference signal SRS request parameter is 1, and the The number of bits corresponding to the candidate set of values is 1
  • the terminal type is determined according to one or more of the following factors: service type, mobility, transmission delay requirement, channel environment, reliability requirement, coverage requirement, and communication scenario.
  • the processing module 801 in FIG. 8 can be replaced by a processor, which can integrate the functions of the processing module 801; the transceiver module 802 can be replaced by a transceiver, which can integrate the functions of the transceiver module 802.
  • the terminal device 80 shown in FIG. 8 may further include a memory.
  • the processing module 801 is replaced by a processor and the transceiver module 802 is replaced by a transceiver, the terminal device 80 involved in this embodiment of the present application may be the communication device shown in FIG. 2 .
  • FIG. 9 shows a network device
  • the network device 90 may include a processing module 901 and a transceiver module 902 .
  • the network device 90 may be a network device, or may be a chip applied in the network device or other combined devices, components and the like having the functions of the above-mentioned network device.
  • the transceiver module 902 may be a transceiver, and the transceiver may include an antenna and a radio frequency circuit, etc.
  • the processing module 901 may be a processor (or a processing circuit), such as a baseband processor.
  • One or more CPUs may be included.
  • the transceiver module 902 may be a radio frequency unit, and the processing module 901 may be a processor (or a processing circuit), such as a baseband processor.
  • the transceiver module 902 may be an input/output interface of a chip (eg, a baseband chip), and the processing module 901 may be a processor (or a processing circuit) of the chip system, which may include one or more central processing units unit.
  • transceiver module 902 in this embodiment of the present application may be implemented by a transceiver or a transceiver-related circuit component
  • processing module 901 may be implemented by a processor or a processor-related circuit component (or referred to as a processing circuit).
  • processing module 901 may be used to perform all the operations performed by the network device in the embodiments shown in Figures 3a-7, except for the transceiving operations, and/or other processes to support the techniques described herein.
  • Transceive module 902 may be used to perform all of the transceive operations performed by network devices in the embodiments shown in Figures 3a-7, and/or for other processes in support of the techniques described herein.
  • the processing module 901 is used to determine the first value; the transceiver module 902902 is used to send the first value to the terminal device; wherein, the first value includes a set of RRC parameter values in the first value candidate set; the first value The value candidate set corresponds to the terminal type of the terminal device; the first value candidate set includes the value candidate set of the radio resource control RRC parameter corresponding to the terminal type.
  • the types of RRC parameters corresponding to the terminal type include one or more of the following: configuration parameters for data transmission, configuration parameters for channel state information CSI measurement feedback, configuration parameters for initial access, mobile configuration parameters for power control, configuration parameters for power control, and configuration parameters for beam management.
  • the RRC parameter value candidate set is used to indicate the configuration mode of the RRC parameter; wherein, the configuration mode includes a configuration parameter field, and the configuration parameter field includes configuration parameters of the configuration mode; or, the configuration mode includes configuration parameters.
  • the transceiver module 902 is further configured to send the first value candidate set to the terminal device.
  • the transceiver module 902 before the transceiver module 902 sends the first value candidate set to the terminal device, it is also used to receive the first request information from the terminal device; wherein, the first request information is used to request the RRC parameter corresponding to the terminal type.
  • the transceiver module 902 is further configured to receive first feature information from the terminal device, wherein the first feature information is used to indicate the terminal type.
  • the types of RRC parameters corresponding to the eMBB include data transmission configuration parameters, channel state information CSI measurement feedback configuration parameters, initial access configuration parameters, mobile characteristic configuration parameters, power control configuration parameters and beam management configuration parameters; and/or; when the terminal type is an ultra-reliable low-latency communication device URLLC, the type of RRC parameters corresponding to the URLLC includes data transmission configuration parameters, channel Configuration parameters of status information CSI measurement feedback and configuration parameters of beam management; and/or; when the terminal type is IoT device IoT, the types of RRC parameters corresponding to IoT include configuration parameters for data transmission, configuration parameters for initial access, Mobility configuration parameters; and/or; when the terminal type is customer premise equipment CPE, the types of RRC parameters corresponding to the CPE include configuration parameters for data transmission and configuration parameters for channel state information CSI measurement feedback.
  • the terminal type is an enhanced mobile broadband device eMBB
  • the types of RRC parameters corresponding to the eMBB include data transmission configuration parameters, channel state information CSI measurement feedback configuration parameters, initial access configuration parameters, mobile
  • the candidate set of subcarrier spacing configuration parameters in the configuration parameters of data transmission are 15kHz, 30kHz, 120kHz, and 240kHz;
  • the configuration parameters for CSI measurement feedback The candidate sets for the value of the CSI reporting time domain configuration parameter are periodic reporting, aperiodic reporting, and semi-persistent reporting;
  • the candidate sets for the value of the beam failure recovery timing parameter in the configuration parameters of beam management are 10ms, 20ms, 40ms, 60ms, 80ms, 100ms, 150ms, 200ms; and/or;
  • the candidate set of subcarrier spacing configuration parameters in the configuration parameters of data transmission is 30kHz, 60kHz, 120kHz;
  • the candidate set of the value of the CSI reporting time domain configuration parameter in the configuration parameters of the CSI measurement feedback is aperiodic reporting;
  • the terminal type is determined according to one or more of the following factors: service type, mobility, transmission delay requirement, channel environment, reliability requirement, coverage requirement, and communication scenario.
  • processing module 901 and the transceiver module 902 in the terminal device 90 shown in FIG. 9 can also be used for:
  • a processing module 901 configured to determine a first DCI; the first DCI includes values of multiple DCI parameters; the DCI parameters included in the first DCI correspond to the terminal type of the terminal device; the candidate set of DCI parameter values corresponds to the terminal type ; The candidate set includes at least one value of the DCI parameter corresponding to the terminal type; the transceiver module 902 is configured to send the first DCI to the terminal device.
  • the transceiver module 902 is also used for the network device to send the first DCI format to the terminal device; so that the terminal device receives the first DCI from the network device according to the first DCI format; wherein, the first DCI format Corresponds to the terminal type.
  • the transceiver module 902 before sending the first DCI to the terminal device, is also used to send indication information to the terminal device; wherein, the indication information is used to indicate the DCI parameter corresponding to the terminal type and the candidate for the value of the DCI parameter. set.
  • the transceiver module 902 before sending the indication information to the terminal device, is also used to receive the second request information from the terminal device; wherein, the second request information is used to request the DCI parameter corresponding to the terminal type and the difference of the DCI parameter.
  • a candidate set of values before sending the indication information to the terminal device, the transceiver module 902 is also used to receive the second request information from the terminal device; wherein, the second request information is used to request the DCI parameter corresponding to the terminal type and the difference of the DCI parameter.
  • a candidate set of values before sending the indication information to the terminal device.
  • the transceiver module 902 is further configured to receive second feature information from the terminal device, wherein the second feature information is used to indicate the terminal type.
  • the DCI parameters corresponding to eMBB include time domain resource allocation, frequency domain resource allocation, bandwidth part BWP indication, modulation and coding mode MCS, new data indication, redundancy redundant version, HARQ process number, HARQ timing, transmission power control TPC command, antenna port, precoding and number of layers, sounding reference signal SRS request, channel state information CSI request; and/or;
  • the terminal type is When the ultra-reliable and low-latency communication device URLLC is used, the DCI parameters corresponding to URLLC include time domain resource indication, frequency domain resource indication, modulation and coding mode MCS, new data indication, hybrid automatic repeat request HARQ process number, transmission power control command, Sounding reference signal SRS request, channel state information CSI request; and/or;
  • the DCI parameters corresponding to IoT include frequency domain resource indication, modulation and coding mode MCS, hybrid automatic repeat request HARQ process and/or;
  • the terminal type is enhanced mobile broadband equipment eMBB
  • the number of bits corresponding to the candidate set of the value of the MCS parameter is 5; the number of bits corresponding to the candidate set of the value of the HARQ process number parameter is 4;
  • the terminal type is an ultra-reliable low-latency communication device URLLC
  • the number of bits corresponding to the candidate set of the value of the MCS parameter is 2 or 3
  • the number of bits corresponding to the candidate set of the value of the HARQ process number parameter is 1
  • the number of bits corresponding to the candidate set of the value of the sounding reference signal SRS request parameter is 1
  • the number of bits corresponding to the candidate set of the value of the channel state information CSI request parameter is 1
  • the terminal type is the Internet of Things
  • the device is IoT
  • the number of bits corresponding to the candidate set of the value of the MCS parameter is 2 or 3
  • the number of bits corresponding to the candidate set of the value of the HARQ process ID parameter is 1 or 2
  • the DCI format corresponding to the eMBB is format 1, wherein the DCI parameters corresponding to format 1 and the candidate sets of the values of the DCI parameters are as follows: Modulation and coding mode MCS The number of bits corresponding to the candidate set of the value of the parameter is 5; the number of bits corresponding to the candidate set of the value of the HARQ process ID parameter of the hybrid automatic repeat request is 4; and/or; when the terminal type is ultra-reliable and low-latency communication
  • the DCI format corresponding to URLLC is format 2, wherein the DCI parameter corresponding to format 2 and the candidate set of DCI parameter values are as follows: 3; the number of bits corresponding to the candidate set of the value of the HARQ process number parameter of the hybrid automatic repeat request is 1; the number of bits corresponding to the candidate set of the value of the sounding reference signal SRS request parameter is 1, and the The number of bits corresponding to the candidate set of values is 1
  • the terminal type is determined according to one or more of the following factors: service type, mobility, transmission delay requirement, channel environment, reliability requirement, coverage requirement, and communication scenario.
  • the transceiver module 902 in FIG. 9 can be replaced by a transceiver, which can integrate the functions of the transceiver module 902; the processing module 901 can be replaced by a processor, which can integrate the functions of the processing module 901.
  • the network device 90 shown in FIG. 9 may further include a memory.
  • the network device 90 involved in this embodiment of the present application may be the communication device shown in FIG. 2 .
  • Embodiments of the present application also provide a computer-readable storage medium. All or part of the processes in the above method embodiments can be completed by instructing the relevant hardware by a computer program, the program can be stored in the above computer-readable storage medium, and when the program is executed, it can include the processes in the above method embodiments.
  • the computer-readable storage medium may be an internal storage unit of the terminal (including the data sending end and/or the data receiving end) in any of the foregoing embodiments, such as a hard disk or a memory of the terminal.
  • the above-mentioned computer-readable storage medium can also be an external storage device of the above-mentioned terminal, such as a plug-in hard disk equipped on the above-mentioned terminal, a smart memory card (smart media card, SMC), a secure digital (secure digital, SD) card, flash memory card (flash card) etc. Further, the above-mentioned computer-readable storage medium may also include both an internal storage unit of the above-mentioned terminal and an external storage device.
  • the above-mentioned computer-readable storage medium is used for storing the above-mentioned computer program and other programs and data required by the above-mentioned terminal.
  • the above-mentioned computer-readable storage medium can also be used to temporarily store data that has been output or is to be output.
  • At least one (item) refers to one or more
  • multiple refers to two or more
  • at least two (item) refers to two or three And three or more
  • "and/or” is used to describe the association relationship of related objects, indicating that three kinds of relationships can exist, for example, “A and/or B” can mean: only A exists, only B exists, and A exists at the same time and B three cases, where A, B can be singular or plural.
  • the character “/” generally indicates that the associated objects are an "or” relationship.
  • At least one item(s) below” or similar expressions thereof refer to any combination of these items, including any combination of single item(s) or plural items(s).
  • At least one (a) of a, b or c can mean: a, b, c, "a and b", “a and c", “b and c", or "a and b and c" ", where a, b, c can be single or multiple.
  • the disclosed apparatus and method may be implemented in other manners.
  • the device embodiments described above are only illustrative.
  • the division of the modules or units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be Incorporation may either be integrated into another device, or some features may be omitted, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place, or may be distributed to multiple different places . Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.
  • the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a readable storage medium.
  • the technical solutions of the embodiments of the present application can be embodied in the form of software products in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, which are stored in a storage medium , including several instructions to make a device (may be a single chip microcomputer, a chip, etc.) or a processor (processor) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk and other mediums that can store program codes.

Landscapes

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

Abstract

本申请实施例提供了一种通信方法、装置及系统，涉及通信技术领域，能够改善网络设备在为终端设备配置多个RRC参数时，需要将每个RRC参数的取值全集发送给终端设备，导致RRC信令开销较大，终端设备的存储开销较大，终端设备的功耗也较大的技术问题。方法包括：终端设备确定第一取值候选集；其中，第一取值候选集与终端设备的终端类型对应；第一取值候选集包括终端类型对应的无线资源控制RRC参数的取值候选集；终端设备接收来自网络设备的第一取值；第一取值包括第一取值候选集中的一组RRC参数取值；终端设备根据第一取值进行通信。

Description

通信方法、装置及系统
本申请要求于2020年10月31日提交中国国家知识产权局、申请号为202011198190.4、申请名称为“通信方法、装置及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信技术领域，尤其是涉及一种通信方法、装置及系统。
背景技术
现有新无线(new radio，NR)通信系统中，网络设备可以通过无线资源控制(radio resource control，RRC)信令为终端设备配置多个RRC参数，以使终端设备根据多个RRC参数进行通信。
具体的，网络设备可以通过物理层的调度，如可以通过控制下行控制信息(downlink control information，DCI)的收发以及数据信道的收发，调度RRC信令向终端设备发送多个RRC参数。
但是，由于RRC信令中携带的多个RRC参数是通信协议预先规定的，RRC参数较多，同一RRC参数的取值也较多，网络设备在为终端设备配置多个RRC参数时，需要将每个RRC参数的取值全集发送给终端设备，导致RRC信令开销较大，终端设备的存储开销较大，终端设备的功耗也较大。
另外，当网络设备通过向终端设备发送DCI以调度RRC信令或数据信号时，由于DCI的格式是通信协议预先规定的固定格式，该DCI的信令开销较大，导致通信系统频谱效率较低，终端设备功耗较大。
发明内容
有鉴于此，本申请的目的在于提供一种通信方法、装置及系统，能够改善网络设备在为终端设备配置多个RRC参数时，需要将每个RRC参数的取值全集发送给终端设备，导致RRC信令开销较大，终端设备的存储开销较大，终端设备的功耗也较大的技术问题。
第一方面，本申请实施例提供了一种通信方法，该方法包括：终端设备确定第一取值候选集；第一取值候选集与终端设备的终端类型对应；第一取值候选集包括终端类型对应的无线资源控制RRC参数的取值候选集；终端设备接收来自网络设备的第一取值；其中，第一取值包括第一取值候选集中的一组RRC参数取值；终端设备根据第一取值进行通信。
基于第一方面，通过根据终端类型确定终端类型对应的第一取值候选集，可以使得网络设备从第一取值候选集中为终端设备确定第一取值，从而避免网络设备将每个RRC参数取值的全集发送给终端设备，降低RRC信令开销，降低终端设备的存储开销，同时降低终端设备的功耗。
一种可能的设计中，终端类型对应的RRC参数的类型包括下述中的一种或多种：数据传输的配置参数、信道状态信息CSI测量反馈的配置参数、初始接入的配置参数、移动性的配置参数、功率控制的配置参数、波束管理的配置参数。
一种可能的设计中，RRC参数的取值候选集用于指示RRC参数的配置方式；其中，配置方式包括配置参数域，配置参数域包括配置方式的配置参数；或者，配置方式包括配 置参数。
基于该可能的设计，为RRC参数的取值候选集的设计提供了可行性方案。
一种可能的设计中，终端设备接收来自网络设备的第一取值候选集。
一种可能的设计中，终端设备接收来自网络设备的第一取值候选集之前，方法还包括：
终端设备向网络设备发送第一请求信息；其中，第一请求信息用于请求终端类型对应的RRC参数的取值候选集。
一种可能的设计中，终端设备向网络设备发送第一特征信息；其中，第一特征信息用于指示终端类型。
基于上述三种可能的设计，网络设备可以根据终端设备发送的第一请求信息或者第一特征信息，确定终端设备的终端类型对应的第一取值候选集，并将第一取值候选集发送给终端设备，为终端设备确定第一取值候选集提供了可行性方案。
一种可能的设计中，当终端类型为增强移动宽带设备eMBB时，eMBB对应的RRC参数的类型包括数据传输的配置参数、信道状态信息CSI测量反馈的配置参数、初始接入的配置参数、移动性的配置参数、功率控制的配置参数和波束管理的配置参数；和/或；当终端类型为超可靠低时延通信设备URLLC时，URLLC对应的RRC参数的类型包括数据传输的配置参数、信道状态信息CSI测量反馈的配置参数和波束管理的配置参数；和/或；当终端类型为物联网设备IoT时，IoT对应的RRC参数的类型包括数据传输的配置参数、初始接入的配置参数、移动性的配置参数；和/或；当终端类型为客户前置设备CPE时，CPE对应的RRC参数的类型包括数据传输的配置参数和信道状态信息CSI测量反馈的配置参数。
基于该可能的设计，可以根据终端类型，确定终端类型对应的RRC参数的类型，实现终端类型的RRC参数定制化，满足终端设备的通信需求的同时可以降低信令开销。
一种可能的设计中，当终端类型为增强移动宽带设备eMBB时，数据传输的配置参数中的子载波间隔配置参数取值的候选集为15kHz、30kHz、120kHz、240kHz；CSI测量反馈的配置参数中的CSI上报时域配置参数取值的候选集为周期性上报、非周期性上报、半持续性上报；波束管理的配置参数中的波束失败恢复定时参数取值的候选集为10ms，20ms，40ms，60ms，80ms，100ms，150ms，200ms；和/或；当终端类型为超可靠低时延通信设备URLLC时，数据传输的配置参数中的子载波间隔配置参数取值的候选集为30kHz、60kHz、120kHz；CSI测量反馈的配置参数中的CSI上报时域配置参数取值的候选集为非周期性上报；波束管理的配置参数中的波束失败恢复定时参数取值的候选集为10ms，20ms，40ms；和/或；当终端类型为物联网设备IoT时，数据传输的配置参数中的子载波间隔配置参数取值的候选集为15kHz、120kHz；和/或；当终端类型为客户前置设备CPE时，数据传输的配置参数中的子载波间隔配置参数的取值为15kHz、120kHz；CSI测量反馈的配置参数中的CSI上报时域配置参数取值的候选集为周期性上报。
基于该可能的设计，可以根据终端类型，确定终端类型对应的RRC参数的取值候选集，实现终端类型的RRC参数的取值候选集定制化，满足终端设备的通信需求的同时可以降低信令开销。
一种可能的设计中，终端类型根据下述一种或多种因素确定：业务类型、移动性、传输时延需求、信道环境、可靠性需求、覆盖需求、通信场景。
基于该可能的设计，网络设备和/或终端设备可以基于上述因素确定终端类型，从而为终端类型确定满足通信需求的RRC参数，降低信令开销。
第二方面，本申请实施例提供了一种终端设备，终端设备可以实现上述第一方面或者第一方面可能的设计中终端设备所执行的功能，所述功能可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个上述功能相应的模块。如，处理模块和收发模块。处理模块，用于确定第一取值候选集；第一取值候选集与终端设备的终端类型对应；第一取值候选集包括终端类型对应的无线资源控制RRC参数的取值候选集；收发模块，用于接收来自网络设备的第一取值；其中，第一取值包括第一取值候选集中的一组RRC参数取值；处理模块，用于根据第一取值进行通信。
一种可能的设计中，终端类型对应的RRC参数的类型包括下述中的一种或多种：数据传输的配置参数、信道状态信息CSI测量反馈的配置参数、初始接入的配置参数、移动性的配置参数、功率控制的配置参数、波束管理的配置参数。
一种可能的设计中，RRC参数的取值候选集用于指示RRC参数的配置方式；其中，配置方式包括配置参数域，配置参数域包括配置方式的配置参数；或者，配置方式包括配置参数。
一种可能的设计中，收发模块，还用于接收来自网络设备的第一取值候选集。
一种可能的设计中，收发模块接收来自网络设备的第一取值候选集之前，还用于向网络设备发送第一请求信息；其中，第一请求信息用于请求终端类型对应的RRC参数的取值候选集。
一种可能的设计中，收发模块，还用于向网络设备发送第一特征信息；其中，第一特征信息用于指示终端类型。
一种可能的设计中，当终端类型为增强移动宽带设备eMBB时，eMBB对应的RRC参数的类型包括数据传输的配置参数、信道状态信息CSI测量反馈的配置参数、初始接入的配置参数、移动性的配置参数、功率控制的配置参数和波束管理的配置参数；和/或；当终端类型为超可靠低时延通信设备URLLC时，URLLC对应的RRC参数的类型包括数据传输的配置参数、信道状态信息CSI测量反馈的配置参数和波束管理的配置参数；和/或；当终端类型为物联网设备IoT时，IoT对应的RRC参数的类型包括数据传输的配置参数、初始接入的配置参数、移动性的配置参数；和/或；当终端类型为客户前置设备CPE时，CPE对应的RRC参数的类型包括数据传输的配置参数和信道状态信息CSI测量反馈的配置参数。
一种可能的设计中，当终端类型为增强移动宽带设备eMBB时，数据传输的配置参数中的子载波间隔配置参数取值的候选集为15kHz、30kHz、120kHz、240kHz；CSI测量反馈的配置参数中的CSI上报时域配置参数取值的候选集为周期性上报、非周期性上报、半持续性上报；波束管理的配置参数中的波束失败恢复定时参数取值的候选集为10ms，20ms，40ms，60ms，80ms，100ms，150ms，200ms；和/或；当终端类型为超可靠低时延通信设备URLLC时，数据传输的配置参数中的子载波间隔配置参数取值的候选集为30kHz、60kHz、120kHz；CSI测量反馈的配置参数中的CSI上报时域配置参数取值的候选集为非周期性上报；波束管理的配置参数中的波束失败恢复定时参数取值的候选集为10ms，20ms，40ms；和/或；当终端类型为物联网设备IoT时，数据传输的配置参数中的子载波间隔配置 参数取值的候选集为15kHz、120kHz；和/或；当终端类型为客户前置设备CPE时，数据传输的配置参数中的子载波间隔配置参数的取值为15kHz、120kHz；CSI测量反馈的配置参数中的CSI上报时域配置参数取值的候选集为周期性上报。
一种可能的设计中，终端类型根据下述一种或多种因素确定：业务类型、移动性、传输时延需求、信道环境、可靠性需求、覆盖需求、通信场景。
第三方面，本申请实施例提供了一种终端设备，该终端设备可以为终端设备或者终端设备中的芯片或者片上系统。该终端设备可以实现上述各方面或者各可能的设计中终端设备所执行的功能，所述功能可以通过硬件实现。一种可能的设计中，该终端设备可以包括：收发器和处理器。收发器和处理器可以用于支持终端设备实现上述第一方面或者第一方面的任一种可能的设计中所涉及的功能。例如：处理器用于确定第一取值候选集；第一取值候选集与终端设备的终端类型对应；第一取值候选集包括终端类型对应的无线资源控制RRC参数的取值候选集；收发器用于接收来自网络设备的第一取值；其中，第一取值包括第一取值候选集中的一组RRC参数取值；处理器用于根据第一取值进行通信。在又一种可能的设计中，所述终端设备还可以包括存储器，存储器，用于保存终端设备必要的计算机执行指令和数据。当该终端设备运行时，该收发器和处理器执行该存储器存储的该计算机执行指令，以使该终端设备执行如上述第一方面或者第一方面的任一种可能的设计所述的通信方法。
其中，第二方面与第三方面中终端设备的具体实现方式可参考第一方面或第一方面的任一种可能的设计提供的通信方法中终端设备的行为功能。
第四方面，本申请实施例提供了一种通信方法，该方法包括：网络设备确定第一取值；网络设备向终端设备发送第一取值；其中，第一取值包括第一取值候选集中的一组RRC参数取值；第一取值候选集与终端设备的终端类型对应；第一取值候选集包括终端类型对应的无线资源控制RRC参数的取值候选集。
基于第四方面，通过根据终端类型确定终端类型对应的第一取值候选集，可以使得网络设备从第一取值候选集中为终端设备确定第一取值，从而避免网络设备将每个RRC参数取值的全集发送给终端设备，降低RRC信令开销，降低终端设备的存储开销，同时降低终端设备的功耗。
一种可能的设计中，终端类型对应的RRC参数的类型包括下述中的一种或多种：数据传输的配置参数、信道状态信息CSI测量反馈的配置参数、初始接入的配置参数、移动性的配置参数、功率控制的配置参数、波束管理的配置参数。
一种可能的设计中，RRC参数的取值候选集用于指示RRC参数的配置方式；其中，配置方式包括配置参数域，配置参数域包括配置方式的配置参数；或者，配置方式包括配置参数。
基于该可能的设计，为RRC参数的取值候选集的设计提供了可行性方案。
一种可能的设计中，网络设备向终端设备发送第一取值候选集。
一种可能的设计中，网络设备向终端设备发送第一取值候选集之前，方法还包括：
网络设备接收来自终端设备的第一请求信息；其中，第一请求信息用于请求终端类型对应的RRC参数的取值候选集。
一种可能的设计中，网络设备接收来自终端设备的第一特征信息；其中，第一特征信 息用于指示终端类型。
基于上述三种可能的设计，网络设备可以根据终端设备发送的第一请求信息或者第一特征信息，确定终端设备的终端类型对应的第一取值候选集，并将第一取值候选集发送给终端设备，为终端设备确定第一取值候选集提供了可行性方案。
一种可能的设计中，当终端类型为增强移动宽带设备eMBB时，eMBB对应的RRC参数的类型包括数据传输的配置参数、信道状态信息CSI测量反馈的配置参数、初始接入的配置参数、移动性的配置参数、功率控制的配置参数和波束管理的配置参数；和/或；当终端类型为超可靠低时延通信设备URLLC时，URLLC对应的RRC参数的类型包括数据传输的配置参数、信道状态信息CSI测量反馈的配置参数和波束管理的配置参数；和/或；当终端类型为物联网设备IoT时，IoT对应的RRC参数的类型包括数据传输的配置参数、初始接入的配置参数、移动性的配置参数；和/或；当终端类型为客户前置设备CPE时，CPE对应的RRC参数的类型包括数据传输的配置参数和信道状态信息CSI测量反馈的配置参数。
基于该可能的设计，可以根据终端类型，确定终端类型对应的RRC参数的类型，实现终端类型的RRC参数定制化，满足终端设备的通信需求的同时可以降低信令开销。
一种可能的设计中，当终端类型为增强移动宽带设备eMBB时，数据传输的配置参数中的子载波间隔配置参数取值的候选集为15kHz、30kHz、120kHz、240kHz；CSI测量反馈的配置参数中的CSI上报时域配置参数取值的候选集为周期性上报、非周期性上报、半持续性上报；波束管理的配置参数中的波束失败恢复定时参数取值的候选集为10ms，20ms，40ms，60ms，80ms，100ms，150ms，200ms；和/或；当终端类型为超可靠低时延通信设备URLLC时，数据传输的配置参数中的子载波间隔配置参数取值的候选集为30kHz、60kHz、120kHz；CSI测量反馈的配置参数中的CSI上报时域配置参数取值的候选集为非周期性上报；波束管理的配置参数中的波束失败恢复定时参数取值的候选集为10ms，20ms，40ms；和/或；当终端类型为物联网设备IoT时，数据传输的配置参数中的子载波间隔配置参数取值的候选集为15kHz、120kHz；和/或；当终端类型为客户前置设备CPE时，数据传输的配置参数中的子载波间隔配置参数的取值为15kHz、120kHz；CSI测量反馈的配置参数中的CSI上报时域配置参数取值的候选集为周期性上报。
基于该可能的设计，可以根据终端类型，确定终端类型对应的RRC参数的取值候选集，实现终端类型的RRC参数的取值候选集定制化，满足终端设备的通信需求的同时可以降低信令开销。
一种可能的设计中，终端类型根据下述一种或多种因素确定：业务类型、移动性、传输时延需求、信道环境、可靠性需求、覆盖需求、通信场景。
基于该可能的设计，网络设备和/或终端设备可以基于上述因素确定终端类型，从而为终端类型确定满足通信需求的RRC参数，降低信令开销。
第五方面，本申请实施例提供了一种网络设备，网络设备可以实现上述第四方面或者第四方面可能的设计中网络设备所执行的功能，所述功能可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个上述功能相应的模块。如，处理模块和收发模块，处理模块，用于确定第一取值；收发模块，用于向终端设备发送第一取值；其中，第一取值包括第一取值候选集中的一组RRC参数取值；第一取值候选集与终端设备的终端类型对 应；第一取值候选集包括终端类型对应的无线资源控制RRC参数的取值候选集。
一种可能的设计中，终端类型对应的RRC参数的类型包括下述中的一种或多种：数据传输的配置参数、信道状态信息CSI测量反馈的配置参数、初始接入的配置参数、移动性的配置参数、功率控制的配置参数、波束管理的配置参数。
一种可能的设计中，RRC参数的取值候选集用于指示RRC参数的配置方式；其中，配置方式包括配置参数域，配置参数域包括配置方式的配置参数；或者，配置方式包括配置参数。
一种可能的设计中，收发模块，还用于向终端设备发送第一取值候选集。
一种可能的设计中，收发模块向终端设备发送第一取值候选集之前，还用于接收来自终端设备的第一请求信息；其中，第一请求信息用于请求终端类型对应的RRC参数的取值候选集。
一种可能的设计中，收发模块，还用于接收来自终端设备的第一特征信息；其中，第一特征信息用于指示终端类型。
一种可能的设计中，当终端类型为增强移动宽带设备eMBB时，eMBB对应的RRC参数的类型包括数据传输的配置参数、信道状态信息CSI测量反馈的配置参数、初始接入的配置参数、移动性的配置参数、功率控制的配置参数和波束管理的配置参数；和/或；当终端类型为超可靠低时延通信设备URLLC时，URLLC对应的RRC参数的类型包括数据传输的配置参数、信道状态信息CSI测量反馈的配置参数和波束管理的配置参数；和/或；当终端类型为物联网设备IoT时，IoT对应的RRC参数的类型包括数据传输的配置参数、初始接入的配置参数、移动性的配置参数；和/或；当终端类型为客户前置设备CPE时，CPE对应的RRC参数的类型包括数据传输的配置参数和信道状态信息CSI测量反馈的配置参数。
一种可能的设计中，当终端类型为增强移动宽带设备eMBB时，数据传输的配置参数中的子载波间隔配置参数取值的候选集为15kHz、30kHz、120kHz、240kHz；CSI测量反馈的配置参数中的CSI上报时域配置参数取值的候选集为周期性上报、非周期性上报、半持续性上报；波束管理的配置参数中的波束失败恢复定时参数取值的候选集为10ms，20ms，40ms，60ms，80ms，100ms，150ms，200ms；和/或；当终端类型为超可靠低时延通信设备URLLC时，数据传输的配置参数中的子载波间隔配置参数取值的候选集为30kHz、60kHz、120kHz；CSI测量反馈的配置参数中的CSI上报时域配置参数取值的候选集为非周期性上报；波束管理的配置参数中的波束失败恢复定时参数取值的候选集为10ms，20ms，40ms；和/或；当终端类型为物联网设备IoT时，数据传输的配置参数中的子载波间隔配置参数取值的候选集为15kHz、120kHz；和/或；当终端类型为客户前置设备CPE时，数据传输的配置参数中的子载波间隔配置参数的取值为15kHz、120kHz；CSI测量反馈的配置参数中的CSI上报时域配置参数取值的候选集为周期性上报。
一种可能的设计中，终端类型根据下述一种或多种因素确定：业务类型、移动性、传输时延需求、信道环境、可靠性需求、覆盖需求、通信场景。
第六方面，本申请实施例提供了一种网络设备，该网络设备可以为网络设备或者网络设备中的芯片或者片上系统。该网络设备可以实现上述各方面或者各可能的设计中网络设备所执行的功能，所述功能可以通过硬件实现。一种可能的设计中，该网络设备可以包括： 收发器和处理器。收发器和处理器可以用于支持网络设备实现上述第四方面或者第四方面的任一种可能的设计中所涉及的功能。例如：处理器用于确定第一取值；收发器用于向终端设备发送第一取值；其中，第一取值包括第一取值候选集中的一组RRC参数取值；第一取值候选集与终端设备的终端类型对应；第一取值候选集包括终端类型对应的无线资源控制RRC参数的取值候选集。在又一种可能的设计中，所述网络设备还可以包括存储器，存储器，用于保存网络设备必要的计算机执行指令和数据。当该网络设备运行时，该收发器和处理器执行该存储器存储的该计算机执行指令，以使该网络设备执行如上述第四方面或者第四方面的任一种可能的设计所述的通信方法。
其中，第五方面与第六方面中网络设备的具体实现方式可参考第四方面或第四方面的任一种可能的设计提供的通信方法中网络设备的行为功能。
第七方面，本申请实施例提供了一种通信方法，该方法包括：终端设备接收来自网络设备的第一下行控制信息DCI；第一DCI包括多个DCI参数的取值；第一DCI包括的DCI参数与终端设备的终端类型对应；DCI参数的取值的候选集与终端类型对应；候选集包括终端类型对应的DCI参数的至少一个取值；终端设备根据第一DCI进行通信。
基于第七方面，通过根据终端类型以定制化方式为终端设备确定终端设备对应的DCI，可以降低DCI的信令开销，提高通信系统频谱效率，同时降低终端设备功耗。
一种可能的设计中，终端设备接收来自网络设备的第一DCI，包括：终端设备确定第一DCI格式；其中，第一DCI格式与终端类型对应；终端设备根据第一DCI格式，接收来自网络设备的第一DCI。
基于该可能的设计，通过根据终端类型以定制化的方式为终端设备确定终端设备对应的DCI格式，可以使得终端设备根据终端设备对应的DCI格式，接收来自网络设备的DCI，提高通信可靠性。
一种可能的设计中，终端设备根据DCI格式与DCI参数的取值的候选集的对应关系、第一DCI格式，确定DCI参数的取值的候选集。
基于该可能的设计，终端设备可以根据DCI格式与DCI参数的取值的候选集的对应关系，对网络设备发送的第一DCI进行解析。
一种可能的设计中，终端设备接收来自网络设备的第一DCI之前，方法还包括：终端设备接收来自网络设备的指示信息；其中，指示信息用于指示终端类型对应的DCI参数和DCI参数的取值的候选集。
基于该可能的设计，终端设备可以根据网络设备发送的指示信息，确定终端类型对应的DCI参数和DCI参数的取值的候选集，进而对接收到的第一DCI进行解析。
一种可能的设计中，终端设备接收来自网络设备的指示信息之前，方法还包括：终端设备向网络设备发送第二请求信息；其中，第二请求信息用于请求终端类型对应的DCI参数和DCI参数的取值的候选集。
一种可能的设计中，终端设备向网络设备发送第二特征信息；其中，第二特征信息用于指示终端类型。
基于上述两种可能的设计，终端设备可以通过向网络设备发送第二请求信息或第二特征信息，以使网络设备根据第二请求信息或第二特征信息，为终端设备确定终端设备的终端类型对应的DCI参数和DCI参数的取值的候选集。
一种可能的设计中，当终端类型为增强移动宽带设备eMBB时，eMBB对应的DCI参数包括时域资源分配、频域资源分配、带宽部分BWP指示、调制和编码方式MCS、新数据指示、冗余版本、混合自动重传请求HARQ进程号、HARQ定时、传输功率控制TPC命令、天线端口、预编码和层数、探测参考信号SRS请求、信道状态信息CSI请求；和/或；当终端类型为超可靠低时延通信设备URLLC时，URLLC对应的DCI参数包括时域资源指示、频域资源指示、调制和编码方式MCS、新数据指示、混合自动重传请求HARQ进程号、传输功率控制命令、探测参考信号SRS请求、信道状态信息CSI请求；和/或；当终端类型为物联网设备IoT时，IoT对应的DCI参数包括频域资源指示、调制和编码方式MCS、混合自动重传请求HARQ进程号；和/或；当终端类型为客户前置设备CPE时，CPE对应的DCI参数包括时域资源分配、频域资源分配、带宽部分BWP指示、调制和编码方式MCS、新数据指示、冗余版本、混合自动重传请求HARQ进程号、HARQ定时、传输功率控制TPC命令、天线端口、预编码和层数、探测参考信号SRS请求、信道状态信息CSI请求。
基于该可能的设计，可以根据终端类型，确定终端类型对应的DCI参数，实现终端类型的DCI定制化，满足终端设备的通信需求的同时可以降低信令开销。
一种可能的设计中，当终端类型为增强移动宽带设备eMBB时，MCS参数的取值的候选集对应的比特数为5；HARQ进程号参数的取值的候选集对应的比特数为4；和/或；当终端类型为超可靠低时延通信设备URLLC时，MCS参数的取值的候选集对应的比特数为2或3；HARQ进程号参数的取值的候选集对应的比特数为1；探测参考信号SRS请求参数的取值的候选集对应的比特数为1；信道状态信息CSI请求参数的取值的候选集对应的比特数为1；和/或；当终端类型为物联网设备IoT时，MCS参数的取值的候选集对应的比特数为2或3；HARQ进程号参数的取值的候选集对应的比特数为1或2；和/或；当终端类型为客户前置设备CPE时，MCS参数的取值的候选集对应的比特数为2、3、4或5；HARQ进程号参数的取值的候选集对应的比特数为4。
基于该可能的设计，可以根据终端类型，确定终端类型对应的DCI参数的取值的候选集，实现终端类型的DCI参数的取值的候选集定制化，满足终端设备的通信需求的同时可以降低信令开销。
一种可能的设计中，当终端类型为增强移动宽带设备eMBB时，eMBB对应的DCI格式为格式一，其中格式一对应的DCI参数以及DCI参数的取值的候选集如下：调制和编码方式MCS参数的取值的候选集对应的比特数为5；混合自动重传请求HARQ进程号参数的取值的候选集对应的比特数为4；和/或；当终端类型为超可靠低时延通信设备URLLC时，URLLC对应的DCI格式为格式二，其中格式二对应的DCI参数以及DCI参数的取值的候选集如下：调制和编码方式MCS参数的取值的候选集对应的比特数为2或3；混合自动重传请求HARQ进程号参数的取值的候选集对应的比特数为1；探测参考信号SRS请求参数的取值的候选集对应的比特数为1、信道状态信息CSI请求参数的取值的候选集对应的比特数为1；和/或；当终端类型为物联网设备IoT时，IoT对应的DCI格式为格式三，其中格式三对应的DCI参数以及DCI参数的取值的候选集如下：调制和编码方式MCS参数的取值的候选集对应的比特数为2或3；混合自动重传请求HARQ进程号参数的取值的候选集对应的比特数为1或2；和/或；当终端类型为客户前置设备CPE时，IoT对应的 DCI格式为格式四，其中格式四对应的DCI参数以及DCI参数的取值的候选集如下：调制和编码方式MCS参数的取值的候选集对应的比特数为2、3、4或5；混合自动重传请求HARQ进程号参数的取值的候选集对应的比特数为4。
基于该可能的设计，可以根据终端类型，确定终端类型对应的DCI格式，实现终端类型的DCI格式定制化，便于终端设备根据终端设备对应的DCI格式接收DCI，满足终端设备的通信需求的同时可以降低信令开销。
一种可能的设计中，终端类型根据下述一种或多种因素确定：业务类型、移动性、传输时延需求、信道环境、可靠性需求、覆盖需求、通信场景。
基于该可能的设计，网络设备和/或终端设备可以基于上述因素确定终端类型，从而为终端类型确定满足通信需求的DCI，降低信令开销。
第八方面，本申请实施例提供了一种终端设备，终端设备可以实现上述第七方面或者第七方面可能的设计中终端设备所执行的功能，所述功能可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个上述功能相应的模块。如，收发模块和处理模块。收发模块，用于接收来自网络设备的第一下行控制信息DCI；第一DCI包括多个DCI参数的取值；第一DCI包括的DCI参数与终端设备的终端类型对应；DCI参数的取值的候选集与终端类型对应；候选集包括终端类型对应的DCI参数的至少一个取值；处理模块，用于根据第一DCI进行通信。
一种可能的设计中，处理模块，还用于确定第一DCI格式；其中，第一DCI格式与终端类型对应；收发模块，还用于根据第一DCI格式，接收来自网络设备的第一DCI。
一种可能的设计中，处理模块，还用于根据DCI格式与DCI参数的取值的候选集的对应关系、第一DCI格式，确定DCI参数的取值的候选集。
一种可能的设计中，收发模块，还用于终端设备接收来自网络设备的指示信息；其中，指示信息用于指示终端类型对应的DCI参数和DCI参数的取值的候选集。
一种可能的设计中，收发模块接收来自网络设备的指示信息之前，还用于终端设备向网络设备发送第二请求信息；其中，第二请求信息用于请求终端类型对应的DCI参数和DCI参数的取值的候选集。
一种可能的设计中，收发模块，还用于向网络设备发送第二特征信息；其中，第二特征信息用于指示终端类型。
一种可能的设计中，当终端类型为增强移动宽带设备eMBB时，eMBB对应的DCI参数包括时域资源分配、频域资源分配、带宽部分BWP指示、调制和编码方式MCS、新数据指示、冗余版本、混合自动重传请求HARQ进程号、HARQ定时、传输功率控制TPC命令、天线端口、预编码和层数、探测参考信号SRS请求、信道状态信息CSI请求；和/或；当终端类型为超可靠低时延通信设备URLLC时，URLLC对应的DCI参数包括时域资源指示、频域资源指示、调制和编码方式MCS、新数据指示、混合自动重传请求HARQ进程号、传输功率控制命令、探测参考信号SRS请求、信道状态信息CSI请求；和/或；当终端类型为物联网设备IoT时，IoT对应的DCI参数包括频域资源指示、调制和编码方式MCS、混合自动重传请求HARQ进程号；和/或；当终端类型为客户前置设备CPE时，CPE对应的DCI参数包括时域资源分配、频域资源分配、带宽部分BWP指示、调制和编码方式MCS、新数据指示、冗余版本、混合自动重传请求HARQ进程号、HARQ定时、 传输功率控制TPC命令、天线端口、预编码和层数、探测参考信号SRS请求、信道状态信息CSI请求。
一种可能的设计中，当终端类型为增强移动宽带设备eMBB时，MCS参数的取值的候选集对应的比特数为5；HARQ进程号参数的取值的候选集对应的比特数为4；和/或；当终端类型为超可靠低时延通信设备URLLC时，MCS参数的取值的候选集对应的比特数为2或3；HARQ进程号参数的取值的候选集对应的比特数为1；探测参考信号SRS请求参数的取值的候选集对应的比特数为1；信道状态信息CSI请求参数的取值的候选集对应的比特数为1；和/或；当终端类型为物联网设备IoT时，MCS参数的取值的候选集对应的比特数为2或3；HARQ进程号参数的取值的候选集对应的比特数为1或2；和/或；当终端类型为客户前置设备CPE时，MCS参数的取值的候选集对应的比特数为2、3、4或5；HARQ进程号参数的取值的候选集对应的比特数为4。
一种可能的设计中，当终端类型为增强移动宽带设备eMBB时，eMBB对应的DCI格式为格式一，其中格式一对应的DCI参数以及DCI参数的取值的候选集如下：调制和编码方式MCS参数的取值的候选集对应的比特数为5；混合自动重传请求HARQ进程号参数的取值的候选集对应的比特数为4；和/或；当终端类型为超可靠低时延通信设备URLLC时，URLLC对应的DCI格式为格式二，其中格式二对应的DCI参数以及DCI参数的取值的候选集如下：调制和编码方式MCS参数的取值的候选集对应的比特数为2或3；混合自动重传请求HARQ进程号参数的取值的候选集对应的比特数为1；探测参考信号SRS请求参数的取值的候选集对应的比特数为1、信道状态信息CSI请求参数的取值的候选集对应的比特数为1；和/或；当终端类型为物联网设备IoT时，IoT对应的DCI格式为格式三，其中格式三对应的DCI参数以及DCI参数的取值的候选集如下：调制和编码方式MCS参数的取值的候选集对应的比特数为2或3；混合自动重传请求HARQ进程号参数的取值的候选集对应的比特数为1或2；和/或；当终端类型为客户前置设备CPE时，IoT对应的DCI格式为格式四，其中格式四对应的DCI参数以及DCI参数的取值的候选集如下：调制和编码方式MCS参数的取值的候选集对应的比特数为2、3、4或5；混合自动重传请求HARQ进程号参数的取值的候选集对应的比特数为4。
一种可能的设计中，终端类型根据下述一种或多种因素确定：业务类型、移动性、传输时延需求、信道环境、可靠性需求、覆盖需求、通信场景。
第九方面，本申请实施例提供了一种终端设备，该终端设备可以为终端设备或者终端设备中的芯片或者片上系统。该终端设备可以实现上述各方面或者各可能的设计中终端设备所执行的功能，所述功能可以通过硬件实现。一种可能的设计中，该终端设备可以包括：收发器和处理器。收发器和处理器可以用于支持终端设备实现上述第七方面或者第七方面的任一种可能的设计中所涉及的功能。例如：收发器用于接收来自网络设备的第一下行控制信息DCI；第一DCI包括多个DCI参数的取值；第一DCI包括的DCI参数与终端设备的终端类型对应；DCI参数的取值的候选集与终端类型对应；候选集包括终端类型对应的DCI参数的至少一个取值；处理器用于根据第一DCI进行通信。在又一种可能的设计中，所述终端设备还可以包括存储器，存储器，用于保存终端设备必要的计算机执行指令和数据。当该终端设备运行时，该收发器和处理器执行该存储器存储的该计算机执行指令，以使该终端设备执行如上述第七方面或者第七方面的任一种可能的设计所述的通信方法。
其中，第八方面与第九方面中终端设备的具体实现方式可参考第七方面或第七方面的任一种可能的设计提供的通信方法中终端设备的行为功能。
第十方面，本申请实施例提供了一种通信方法，该方法包括：网络设备确定第一DCI；第一DCI包括多个DCI参数的取值；第一DCI包括的DCI参数与终端设备的终端类型对应；DCI参数的取值的候选集与终端类型对应；候选集包括终端类型对应的DCI参数的至少一个取值；网络设备向终端设备发送第一DCI。
基于第十方面，通过根据终端类型以定制化方式为终端设备确定终端设备对应的DCI，可以降低DCI的信令开销，提高通信系统频谱效率，同时降低终端设备功耗。
一种可能的设计中，网络设备向终端设备发送第一DCI，包括：网络设备向终端设备发送第一DCI格式；以使终端设备根据第一DCI格式，接收来自网络设备的第一DCI；其中，第一DCI格式与终端类型对应。
基于该可能的设计，通过根据终端类型以定制化的方式为终端设备确定终端设备对应的DCI格式，可以使得终端设备根据终端设备对应的DCI格式，接收来自网络设备的DCI，提高通信可靠性。
一种可能的设计中，网络设备向终端设备发送第一DCI之前，方法还包括：网络设备向终端设备发送指示信息；其中，指示信息用于指示终端类型对应的DCI参数和DCI参数的取值的候选集。
基于该可能的设计，终端设备可以根据网络设备发送的指示信息，确定终端类型对应的DCI参数和DCI参数的取值的候选集，进而对接收到的第一DCI进行解析。
一种可能的设计中，网络设备向终端设备发送指示信息之前，方法还包括：网络设备接收来自终端设备的第二请求信息；其中，第二请求信息用于请求终端类型对应的DCI参数和DCI参数的取值的候选集。
一种可能的设计中，网络设备接收来自终端设备的第二特征信息；其中，第二特征信息用于指示终端类型。
基于上述两种可能的设计，终端设备可以通过向网络设备发送第二请求信息或第二特征信息，以使网络设备根据第二请求信息或第二特征信息，为终端设备确定终端设备的终端类型对应的DCI参数和DCI参数的取值的候选集。
一种可能的设计中，当终端类型为增强移动宽带设备eMBB时，eMBB对应的DCI参数包括时域资源分配、频域资源分配、带宽部分BWP指示、调制和编码方式MCS、新数据指示、冗余版本、混合自动重传请求HARQ进程号、HARQ定时、传输功率控制TPC命令、天线端口、预编码和层数、探测参考信号SRS请求、信道状态信息CSI请求；和/或；当终端类型为超可靠低时延通信设备URLLC时，URLLC对应的DCI参数包括时域资源指示、频域资源指示、调制和编码方式MCS、新数据指示、混合自动重传请求HARQ进程号、传输功率控制命令、探测参考信号SRS请求、信道状态信息CSI请求；和/或；当终端类型为物联网设备IoT时，IoT对应的DCI参数包括频域资源指示、调制和编码方式MCS、混合自动重传请求HARQ进程号；和/或；当终端类型为客户前置设备CPE时，CPE对应的DCI参数包括时域资源分配、频域资源分配、带宽部分BWP指示、调制和编码方式MCS、新数据指示、冗余版本、混合自动重传请求HARQ进程号、HARQ定时、传输功率控制TPC命令、天线端口、预编码和层数、探测参考信号SRS请求、信道状态 信息CSI请求。
基于该可能的设计，可以根据终端类型，确定终端类型对应的DCI参数，实现终端类型的DCI定制化，满足终端设备的通信需求的同时可以降低信令开销。
一种可能的设计中，当终端类型为增强移动宽带设备eMBB时，MCS参数的取值的候选集对应的比特数为5；HARQ进程号参数的取值的候选集对应的比特数为4；和/或；当终端类型为超可靠低时延通信设备URLLC时，MCS参数的取值的候选集对应的比特数为2或3；HARQ进程号参数的取值的候选集对应的比特数为1；探测参考信号SRS请求参数的取值的候选集对应的比特数为1；信道状态信息CSI请求参数的取值的候选集对应的比特数为1；和/或；当终端类型为物联网设备IoT时，MCS参数的取值的候选集对应的比特数为2或3；HARQ进程号参数的取值的候选集对应的比特数为1或2；和/或；当终端类型为客户前置设备CPE时，MCS参数的取值的候选集对应的比特数为2、3、4或5；HARQ进程号参数的取值的候选集对应的比特数为4。
基于该可能的设计，可以根据终端类型，确定终端类型对应的DCI参数的取值的候选集，实现终端类型的DCI参数的取值的候选集定制化，满足终端设备的通信需求的同时可以降低信令开销。
一种可能的设计中，当终端类型为增强移动宽带设备eMBB时，eMBB对应的DCI格式为格式一，其中格式一对应的DCI参数以及DCI参数的取值的候选集如下：调制和编码方式MCS参数的取值的候选集对应的比特数为5；混合自动重传请求HARQ进程号参数的取值的候选集对应的比特数为4；和/或；当终端类型为超可靠低时延通信设备URLLC时，URLLC对应的DCI格式为格式二，其中格式二对应的DCI参数以及DCI参数的取值的候选集如下：调制和编码方式MCS参数的取值的候选集对应的比特数为2或3；混合自动重传请求HARQ进程号参数的取值的候选集对应的比特数为1；探测参考信号SRS请求参数的取值的候选集对应的比特数为1、信道状态信息CSI请求参数的取值的候选集对应的比特数为1；和/或；当终端类型为物联网设备IoT时，IoT对应的DCI格式为格式三，其中格式三对应的DCI参数以及DCI参数的取值的候选集如下：调制和编码方式MCS参数的取值的候选集对应的比特数为2或3；混合自动重传请求HARQ进程号参数的取值的候选集对应的比特数为1或2；和/或；当终端类型为客户前置设备CPE时，IoT对应的DCI格式为格式四，其中格式四对应的DCI参数以及DCI参数的取值的候选集如下：调制和编码方式MCS参数的取值的候选集对应的比特数为2、3、4或5；混合自动重传请求HARQ进程号参数的取值的候选集对应的比特数为4。
基于该可能的设计，可以根据终端类型，确定终端类型对应的DCI格式，实现终端类型的DCI格式定制化，便于终端设备根据终端设备对应的DCI格式接收DCI，满足终端设备的通信需求的同时可以降低信令开销。
一种可能的设计中，终端类型根据下述一种或多种因素确定：业务类型、移动性、传输时延需求、信道环境、可靠性需求、覆盖需求、通信场景。
基于该可能的设计，网络设备和/或终端设备可以基于上述因素确定终端类型，从而为终端类型确定满足通信需求的DCI，降低信令开销。
第十一方面，本申请实施例提供了一种网络设备，网络设备可以实现上述第十方面或者第十方面可能的设计中网络设备所执行的功能，所述功能可以通过硬件执行相应的软件 实现。所述硬件或软件包括一个或多个上述功能相应的模块。如，处理模块和收发模块，处理模块，用于确定第一DCI；第一DCI包括多个DCI参数的取值；第一DCI包括的DCI参数与终端设备的终端类型对应；DCI参数的取值的候选集与终端类型对应；候选集包括终端类型对应的DCI参数的至少一个取值；收发模块，用于向终端设备发送第一DCI。
一种可能的设计中，收发模块，还用于网络设备向终端设备发送第一DCI格式；以使终端设备根据第一DCI格式，接收来自网络设备的第一DCI；其中，第一DCI格式与终端类型对应。
一种可能的设计中，收发模块向终端设备发送第一DCI之前，还用于向终端设备发送指示信息；其中，指示信息用于指示终端类型对应的DCI参数和DCI参数的取值的候选集。
一种可能的设计中，收发模块向终端设备发送指示信息之前，还用于接收来自终端设备的第二请求信息；其中，第二请求信息用于请求终端类型对应的DCI参数和DCI参数的取值的候选集。
一种可能的设计中，收发模块，还用于接收来自终端设备的第二特征信息；其中，第二特征信息用于指示终端类型。
一种可能的设计中，当终端类型为增强移动宽带设备eMBB时，eMBB对应的DCI参数包括时域资源分配、频域资源分配、带宽部分BWP指示、调制和编码方式MCS、新数据指示、冗余版本、混合自动重传请求HARQ进程号、HARQ定时、传输功率控制TPC命令、天线端口、预编码和层数、探测参考信号SRS请求、信道状态信息CSI请求；和/或；当终端类型为超可靠低时延通信设备URLLC时，URLLC对应的DCI参数包括时域资源指示、频域资源指示、调制和编码方式MCS、新数据指示、混合自动重传请求HARQ进程号、传输功率控制命令、探测参考信号SRS请求、信道状态信息CSI请求；和/或；当终端类型为物联网设备IoT时，IoT对应的DCI参数包括频域资源指示、调制和编码方式MCS、混合自动重传请求HARQ进程号；和/或；当终端类型为客户前置设备CPE时，CPE对应的DCI参数包括时域资源分配、频域资源分配、带宽部分BWP指示、调制和编码方式MCS、新数据指示、冗余版本、混合自动重传请求HARQ进程号、HARQ定时、传输功率控制TPC命令、天线端口、预编码和层数、探测参考信号SRS请求、信道状态信息CSI请求。
一种可能的设计中，当终端类型为增强移动宽带设备eMBB时，MCS参数的取值的候选集对应的比特数为5；HARQ进程号参数的取值的候选集对应的比特数为4；和/或；当终端类型为超可靠低时延通信设备URLLC时，MCS参数的取值的候选集对应的比特数为2或3；HARQ进程号参数的取值的候选集对应的比特数为1；探测参考信号SRS请求参数的取值的候选集对应的比特数为1；信道状态信息CSI请求参数的取值的候选集对应的比特数为1；和/或；当终端类型为物联网设备IoT时，MCS参数的取值的候选集对应的比特数为2或3；HARQ进程号参数的取值的候选集对应的比特数为1或2；和/或；当终端类型为客户前置设备CPE时，MCS参数的取值的候选集对应的比特数为2、3、4或5；HARQ进程号参数的取值的候选集对应的比特数为4。
一种可能的设计中，当终端类型为增强移动宽带设备eMBB时，eMBB对应的DCI格式为格式一，其中格式一对应的DCI参数以及DCI参数的取值的候选集如下：调制和编码方式MCS参数的取值的候选集对应的比特数为5；混合自动重传请求HARQ进程号参 数的取值的候选集对应的比特数为4；和/或；当终端类型为超可靠低时延通信设备URLLC时，URLLC对应的DCI格式为格式二，其中格式二对应的DCI参数以及DCI参数的取值的候选集如下：调制和编码方式MCS参数的取值的候选集对应的比特数为2或3；混合自动重传请求HARQ进程号参数的取值的候选集对应的比特数为1；探测参考信号SRS请求参数的取值的候选集对应的比特数为1、信道状态信息CSI请求参数的取值的候选集对应的比特数为1；和/或；当终端类型为物联网设备IoT时，IoT对应的DCI格式为格式三，其中格式三对应的DCI参数以及DCI参数的取值的候选集如下：调制和编码方式MCS参数的取值的候选集对应的比特数为2或3；混合自动重传请求HARQ进程号参数的取值的候选集对应的比特数为1或2；和/或；当终端类型为客户前置设备CPE时，IoT对应的DCI格式为格式四，其中格式四对应的DCI参数以及DCI参数的取值的候选集如下：调制和编码方式MCS参数的取值的候选集对应的比特数为2、3、4或5；混合自动重传请求HARQ进程号参数的取值的候选集对应的比特数为4。
一种可能的设计中，终端类型根据下述一种或多种因素确定：业务类型、移动性、传输时延需求、信道环境、可靠性需求、覆盖需求、通信场景。
第十二方面，本申请实施例提供了一种网络设备，该网络设备可以为网络设备或者网络设备中的芯片或者片上系统。该网络设备可以实现上述各方面或者各可能的设计中网络设备所执行的功能，所述功能可以通过硬件实现。一种可能的设计中，该网络设备可以包括：收发器和处理器。收发器和处理器可以用于支持网络设备实现上述第十方面或者第十方面的任一种可能的设计中所涉及的功能。例如：处理器用于确定第一DCI；第一DCI包括多个DCI参数的取值；第一DCI包括的DCI参数与终端设备的终端类型对应；DCI参数的取值的候选集与终端类型对应；候选集包括终端类型对应的DCI参数的至少一个取值；收发器用于向终端设备发送第一DCI。在又一种可能的设计中，所述网络设备还可以包括存储器，存储器，用于保存网络设备必要的计算机执行指令和数据。当该网络设备运行时，该收发器和处理器执行该存储器存储的该计算机执行指令，以使该网络设备执行如上述第十方面或者第十方面的任一种可能的设计所述的通信方法。
其中，第十一方面与第十二方面中网络设备的具体实现方式可参考第十方面或第十方面的任一种可能的设计提供的通信方法中网络设备的行为功能。
第十三方面，提供了一种通信装置，该通信装置包括一个或多个处理器和一个或多个存储器；一个或多个存储器与一个或多个处理器耦合，一个或多个存储器用于存储计算机程序代码或计算机指令；当一个或多个处理器执行计算机指令时，使得通信装置执行如第一方面或者第一方面的任一可能的设计所述的通信方法，或者执行如第四方面或者第四方面的任一可能的设计所述的通信方法，或者执行如第七方面或者第七方面的任一可能的设计所述的通信方法，或者执行如第十方面或者第十方面的任一可能的设计所述的通信方法。
第十四方面，提供了一种计算机可读存储介质，该计算机可读存储介质存储有计算机指令或程序，当计算机指令或程序在计算机上运行时，使得计算机执行如第一方面或者第一方面的任一可能的设计所述的通信方法，或者执行如第四方面或者第四方面的任一可能的设计所述的通信方法，或者执行如第七方面或者第七方面的任一可能的设计所述的通信方法，或者执行如第十方面或者第十方面的任一可能的设计所述的通信方法。
第十五方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得 计算机执行如第一方面或者第一方面的任一可能的设计所述的通信方法，或者执行如第四方面或者第四方面的任一可能的设计所述的通信方法，或者执行如第七方面或者第七方面的任一可能的设计所述的通信方法，或者执行如第十方面或者第十方面的任一可能的设计所述的通信方法。
第十六方面，提供了一种通信装置，所述通信装置包括处理器和通信接口；处理器用于读取指令，当通信装置为芯片时，可以执行如第一方面或者第一方面的任一可能的设计所述的通信方法，或者执行如第四方面或者第四方面的任一可能的设计所述的通信方法，或者执行如第七方面或者第七方面的任一可能的设计所述的通信方法，或者执行如第十方面或者第十方面的任一可能的设计所述的通信方法，当通信装置为终端设备时，可以执行如第一方面或者第一方面的任一可能的设计所述的通信方法，或者执行如第七方面或者第七方面的任一可能的设计所述的通信方法；当通信装置为网络设备时，可以执行如第四方面或者第四方面的任一可能的设计所述的通信方法，或者执行如第十方面或者第十方面的任一可能的设计所述的通信方法。
其中，第十三方面至第十六方面中任一种设计方式所带来的技术效果可参见上述第一方面的任一种可能的设计所带来的技术效果，或者参见上述第四方面的任一种可能的设计所带来的技术效果，或者参见上述第七方面的任一种可能的设计所带来的技术效果，或者参见上述第十方面的任一种可能的设计所带来的技术效果，不予赘述。
第十七方面，提供了一种通信系统，该通信系统包括如第二方面至第三方面的任一方面所述的终端设备以及如第五方面至第六方面任一方面所述网络设备，或者包括如第八方面至第九方面的任一方面所述的终端设备以及如第十一方面至第十二方面任一方面所述网络设备。
附图说明
图1a为本申请实施例提供的一种通信系统的组成示意图；
图1b为本申请实施例提供的一种终端设备与网络设备的协议栈示意图；
图1c为本申请实施例提供的一种通信系统的组成示意图；
图2为本申请实施例提供的一种通信装置的组成示意图；
图3a为本申请实施例提供的一种通信方法的流程图；
图3b为本申请实施例提供的一种通信方法的流程图；
图3c为本申请实施例提供的一种通信方法的流程图；
图4为本申请实施例提供的一种终端类型的示意图；
图5a为本申请实施例提供的一种通信方法的流程图；
图5b为本申请实施例提供的一种通信方法的流程图；
图5c为本申请实施例提供的一种通信方法的流程图；
图6为本申请实施例提供的一种DCI参数的示意图；
图7为本申请实施例提供的一种符号示意图；
图8为本申请实施例提供的一种终端设备的组成示意图；
图9为本申请实施例提供的一种网络设备的组成示意图。
具体实施方式
在描述本申请实施例之前，对本申请实施例涉及的技术术语进行描述。
现有新无线(new radio，NR)通信系统中，网络设备可以通过无线资源控制(radio resource control，RRC)信令为终端设备配置多个RRC参数，以使终端设备根据多个RRC参数进行通信。但是，由于RRC信令中携带的多个RRC参数的取值是通信协议预先规定的，RRC参数较多，同一RRC参数的取值也较多，网络设备在为终端设备配置多个RRC参数时，需要将每个RRC参数从该RRC参数的取值全集中指示一个取值发送给终端设备，导致RRC信令开销较大，终端设备的存储开销较大，终端设备的功耗也较大。
另外，网络设备向终端设备发送RRC参数时，可以通过物理层的调度，如可以通过控制下行控制信息(downlink control information，DCI)的收发以及数据信道的收发，调度RRC信令向终端设备发送多个RRC参数。但是，当网络设备通过向终端设备发送DCI以调度RRC信令时，由于DCI的格式是通信协议预先规定的固定格式，该DCI的信令开销较大，导致通信系统频谱效率较低，终端设备功耗较大。
为解决上述网络设备为终端设备配置多个RRC参数时，需要将每个RRC参数从该RRC参数的取值全集中指示一个取值发送给终端设备，导致RRC信令开销较大，终端设备的存储开销较大，终端设备的功耗也较大的技术问题，本申请实施例提供了一种通信方法，该方法包括：终端设备确定第一取值候选集；第一取值候选集与终端设备的终端类型对应；第一取值候选集包括终端类型对应的RRC参数的取值候选集；终端设备接收来自网络设备的第一取值；第一取值包括第一取值候选集中的一组RRC参数取值；终端设备根据第一取值进行通信。本申请实施例中，通过根据终端类型确定终端类型对应的第一取值候选集，可以使得网络设备从第一取值候选集中为终端设备确定第一取值，相比于网络设备将每个RRC参数从该RRC参数的取值的全集中指示第一取值发送给终端设备，降低RRC信令开销，降低终端设备的存储开销，同时降低终端设备的功耗。
为解决上述网络设备通过向终端设备发送DCI以调度RRC信令或数据信号时，由于DCI的格式是通信协议预先规定的固定格式，DCI的信令开销较大，导致通信系统频谱效率较低，终端设备功耗较大的技术问题，本申请实施例提供了一种通信方法，该方法包括：终端设备接收来自网络设备的第一DCI；第一DCI包括多个DCI参数的取值；第一DCI包括的DCI参数与终端设备的终端类型对应；DCI参数的取值的候选集与终端类型对应；候选集包括终端类型对应的DCI参数的至少一个取值；终端设备根据第一DCI进行通信。本申请实施例中，通过根据终端类型为终端设备确定终端设备对应的DCI，可以降低DCI的信令开销，提高通信系统频谱效率，同时降低终端设备功耗。
下面结合说明书附图对本申请实施例的实施方式进行详细描述。
本申请实施例提供的通信方法可以用于任一通信系统，该通信系统可以为第三代合作伙伴计划(third generation partnership project，3GPP)通信系统，例如，长期演进(long term evolution，LTE)系统，又可以为第五代(fifth generation，5G)移动通信系统、新空口(new radio，NR)系统、NR V2X系统，还可以应用于LTE和5G混合组网的系统中，或者设备到设备(device-to-device，D2D)通信系统、机器到机器(machine to machine，M2M)通信系统、物联网(Internet of Things，IoT)、频分双工(frequency division duplex，FDD)系统、时分双工(time division duplex，TDD)系统、卫星通信系统，以及其他下一代通信系统，也可以为非3GPP通信系统，不予限制。
本申请实施例提供的通信方法可以应用于各种通信场景，例如可以应用于以下通信场 景中的一种或多种：增强移动宽带(enhanced mobile broadband，eMBB)、超可靠低时延通信(ultra reliable low latency communication，URLLC)、机器类型通信(machine type communication，MTC)、物联网(internet of things，IoT)、窄带物联网(narrow band internet of thing，NB-IoT)、客户前置设备(customer premise equipment，CPE)、增强现实(augmented reality，AR)、虚拟现实(virtual reality，VR)、大规模机器类型通信(massive machine type communications，mMTC)、设备到设备(device to device，D2D)、车联网(vehicle to everything，V2X)、车辆到车辆(vehicle to vehicle，V2V)等。
需要说明的是，本申请实施例中，IoT(internet of thing，IoT)可以包括NB-IoT、MTC、mMTC等中的一项或多项，不予限制。
本申请实施例对于同构网络与异构网络的场景均适用，同时对于传输点也无限制，可以是宏基站与宏基站、微基站与微基站和宏基站与微基站间的多点协同传输，对频分复用系统，时分复用系统，双工系统，接入回传系统，中继系统等均适用。本申请实施例适用于低频场景(sub 6G)，也适用于高频场景(6G以上)，太赫兹，光通信等。
其中，eMBB，可以是指三维(three-dimensional，3D)/超高清视频等大流量移动宽带业务。具体的，eMBB可以基于移动宽带业务，对网速、用户体验等性能做进一步的提升。例如，当用户观看4K高清视频时，网速峰值可以达到10Gbps。
URLLC，可以指高可靠性、低时延、极高可用性的业务。具体的，URLLC可以包括下述通信场景及应用：工业应用和控制、交通安全和控制、远程制造、远程培训、远程手术、无人驾驶、工业自动化、安防行业等。
MTC，可以指低成本，覆盖增强的业务，也可以称为M2M。mMTC指大规模物联网业务。
NB-IoT，可以是具备覆盖广、连接多、速率低、成本低、功耗低、架构优等特点的业务。具体的，NB-IoT可以包括智能水表、智能停车、宠物智能跟踪、智能自行车、智能烟雾检测器、智能马桶、智能售货机等等。
CPE，可以指接收移动信号并以无线保真(wireless fidelity，WiFi)信号转发出来的移动信号接入设备，也可以指将高速4G或者5G信号转换成WiFi信号的设备，可以同时支持较多上网的移动终端数量。CPE可以大量应用于农村，城镇，医院，单位，工厂，小区等无线网络接入，可以节省铺设有线网络的费用。
V2X，可以使得车与车、车与网络设备、网络设备与网络设备之间能够通信，从而获得实时路况、道路信息、行人信息等一系列交通信息，同时提供车载娱乐信息，提高驾驶安全性、减少拥堵、提高交通效率。
下面以图1a为例，对本申请实施例提供的通信方法进行描述。
图1a为本申请实施例提供的一种通信系统的示意图，如图1a所示，该通信系统可以包括终端设备和网络设备。
其中，图1a中终端设备可以位于网络设备的小区覆盖范围内。其中，终端设备可以通过上行链路(uplink，UL)或下行链路(downlink，DL)与网络设备进行空口通信，在UL方向上，终端设备可以通过上行链路物理层共享信道(physical sidelink share channel，PUSCH)向网络设备发送数据；在DL方向上，网络设备可以向终端设备发送承载有DCI的PDCCH，也可以通过下行链路物理层共享信道(physical downlink share channel，PDSCH) 向终端发送数据。
其中，上行链路物理层共享信道也可以简称为物理上行共享信道。下行链路物理层共享信道也可以简称为物理下行共享信道。
具体的，网络架构示意图如图1b所示，终端设备可以包括物理层(physical layer,PHY)，媒体接入控制层(medium access control，MAC)，无线链路管理层(radio link control，RLC)，分组数据汇聚协议层(packet data convergence protocol，PDCP)，业务数据适配协议层(service data adaptation protocol，SDAP)、无线资源控制层(radio resource control，RRC)。终端设备可以包括用户面协议(user plane)和控制面协议(control plane)，
示例性的，图1a中的终端设备可以称为终端(terminal)或者用户设备(user equipment，UE)或者移动台(mobile station，MS)或者移动终端(mobile terminal，MT)等，可以是指向用户提供语音和/或数据连通性的设备。具体的，图1a中的终端设备可以是手机(mobile phone)、无人机、平板电脑，或带无线收发功能的电脑，或具有无线连接功能的手持式设备、车载设备等。终端设备还可以是掌上电脑、移动互联网设备(mobile internet device，MID)、可穿戴设备、eMBB终端、URLLC终端、MTC终端、NB-IoT终端、CPE终端、VR终端、AR终端、V2X终端、工业控制中的无线终端、无人驾驶中的无线终端、远程医疗中的无线终端、智能电网中的无线终端、运输安全中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端、传感器、蜂窝电话、无绳电话、会话启动协议(SIP，session initiation protocol)电话、无线本地环路(WLL，wireless local loop)站、个人数字助理(PDA，personal digital assistant)、计算设备或连接到无线调制解调器的其它处理设备、车载终端、具有车与车的通信(vehicle to vehicle，V2V)能力的车辆、有无人机(unmanned aerial vehicle，UAV)对无人机通信能力的无人机、5G网络中的终端设备或者未来演进的公用陆地移动通信网络(PLMN，public land mobile network)中的终端设备等等，不予限制。
其中，可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
此外，终端设备还可以是物联网(IoT，internet of things)系统中的终端设备。IoT是未来信息技术发展的重要组成部分，其主要技术特点是将物品通过通信技术与网络连接，从而实现人机互连，物物互连的智能化网络。IoT技术可以通过例如窄带(NB，narrow band)技术，做到海量连接，深度覆盖，终端省电。
此外，终端设备还可以包括智能打印机、火车探测器、加油站等传感器，主要功能包括收集数据、接收网络设备的控制信息与下行数据，并发送电磁波，向网络设备传输上行数据。
其中，图1a中的网络设备可以是任意一种具有无线收发功能的设备，可以用于负责空中接口相关的功能，例如，无线链路维护功能、无线资源管理功能、部分移动性管理功能。 其中，无线链路维护功能用于保持与终端设备间的无线链路，同时负责无线链路数据和互联网协议(internet protocol，IP)数据之间的协议转换；无线资源管理功能可以包括无线链路的建立和释放、无线资源的调度和分配等功能；部分移动性管理功能可以包括配置终端设备进行测量、评估终端设备无线链路质量、决策终端设备在小区间的切换等。
具体的，终端设备与网络设备的协议栈示意图可以如图1b所示，网络设备的协议栈可以包括PHY层、MAC层、RLC层、PDCP层、SDAP层和RRC层。其中，网络设备的协议栈也包括用户面协议和控制面协议，终端设备与网络设备的各个层可以相互连接，进行信息传输。
示例性的，网络设备可以为支持有线接入的设备，也可以为支持无线接入的设备。示例性的，该网络设备可以为接入网(access network，AN)/无线接入网(radio access network，RAN)设备，由多个AN/RAN节点组成。AN/RAN节点可以为：接入点(access point，AP)、基站(nodeB，NB)、增强型基站(enhance nodeB，eNB)、下一代基站(NR nodeB，gNB)、传输接收点(transmission reception point，TRP)、传输点(transmission point，TP)或某种其它接入节点等。
目前，一些RAN节点的举例可以为：继续演进的节点B(gNB)、传输接收点(transmission reception point，TRP)、演进型节点B(evolved Node B，eNB)、无线网络控制器(radio network controller，RNC)、家庭基站(例如，home evolved NodeB，或home Node B，HNB)、无线保真(wireless fidelity，Wifi)接入点(access point，AP)、无线中继节点、无线回传节点、传输点(transmission point，TP)或者发送接收点(transmission and reception point，TRP)等，还可以为5G，如，NR系统中的ngNB，或，传输点(TRP或TP)，5G系统中的基站的一个或一组天线面板，或者，还可以为构成gNB或传输点的网络节点，如基带单元(baseband unit，BBU)，或，分布式单元(distributed unit，DU)，D2D、V2X、机器到机器(machine-to-machine，M2M)通信中承担基站功能的设备，或者未来的通信系统中的基站等。
在一些部署中，gNB可以包括集中式单元(centralized unit，CU)和DU，gNB还可以包括有源天线单元(active antenna unit，AAU)。CU可以实现gNB的部分功能，DU可以实现gNB的部分功能，示例性地，CU负责处理非实时协议和服务，实现无线资源控制RRC，分组数据汇聚层协议(packet data convergence protocol，PDCP)层的功能。DU负责处理物理层协议和实时服务，实现无线链路控制(radio link control，RLC)层、介质接入控制(medium access control，MAC)层和物理(physical，PHY)层的功能。AAU实现部分物理层处理功能、射频处理及有源天线的相关功能。由于RRC层的信息最终会变成PHY层的信息，或者，由PHY层的信息转变而来，因而，在这种架构下，高层信令，如RRC层信令，也可以认为是由DU发送的，或者，由DU和AAU发送的。可以理解的是，网络设备可以为包括CU节点、DU节点、AAU节点中一项或多项的设备。此外，可以将CU划分为接入网(radio access network，RAN)中的网络设备，也可以将CU划分为核心网(core network，CN)中的网络设备，本申请对此不做限定。
网络设备可以为小区提供服务，终端设备通过网络设备分配的传输资源(例如，频域资源，或者说，频谱资源)与小区进行通信，该小区可以属于宏基站(例如，宏eNB或宏gNB等)，也可以属于小小区(small cell)对应的基站，这里的小小区可以包括：城市小 区(metro cell)、微小区(micro cell)、微微小区(pico cell)、毫微微小区(femto cell)等，这些小小区具有覆盖范围小、发射功率低的特点，适用于提供高速率的数据传输服务。
本申请实施例中，通信的时域的衡量单位可以称为时间单元或时间调度单位。时间调度单位或者时间单元可以是无线帧，子帧，时隙(slot)，微时隙(mini-slot)或者子时隙等。时间调度单位或时间单元也可以是一个或者多个符号等等，其中符号是一种时域上的基本单元。
本申请实施例中，通信的频域的衡量单位可以称为频域资源单元或频域调度单位。其中，频域资源单元可以是基本资源单元(resource element，RE)，资源块(resource block)，资源块组(resource block group)等。其中，一个资源块可以包括一个或多个资源单元。一个资源块组可以包括一个或多个资源块。比如，用于进行数据传输的频域资源单元可以包括若干个基本资源单元，一个RE可以对应于一个子载波，一个物理资源块(physical resource block,PRB)中有X1个基本资源单元，X1为大于等于1的整数。示例性地，X1为12。
需要说明的是，本申请实施例的终端设备、网络设备都可以为一个或多个芯片，也可以为片上系统(system on chip，SOC)等。图1a仅为示例性附图，其包括的设备数量不受限制。图1a中各个设备的名称、各个链路的命名不受限制，除图1a所示名称之外，各个设备、各个链路还可以命名为其他名称，如：终端设备与网络设备之间通过用户设备(user equipment，Uu)接口进行通信，UL还可以命名为Uu链路等，不予限制。
此外，除图1a所示设备之外，如图1c所示，该通信系统还可以包括核心网和外部网络。
示例性的，可以将移动网络划分为三个部分，分别是基站子系统，网络子系统，和系统支撑部分。其中，网络设备可以位于基站子系统内，核心网可以位于网络子系统内。
具体的，核心网可以用于将来自空口的呼叫请求或数据请求，传输到不同的外部网络上。其中，核心网可以作为承载网提供给外部网络的接口，可以提供用户连接、用户管理、承载连接等功能。
示例性的，用户连接的建立可以包括移动性管理(mobility management，MM)、呼叫管理(calling management，CM)、交换/路由、录音通知等功能。用户管理可以包括用户的描述、服务质量(quality of service，QoS)、用户通信记录(accounting)、虚拟家庭环境(virtual home environment，VHE)(例如，通过与智能网平台的对话提供虚拟居家环境)、安全性(例如，由鉴权中心提供相应的安全性措施，包括对移动业务的安全性管理和对外部网络访问的安全性处理)等功能。承载连接(access to)包括到外部的公共交互电话网(public switched telephone network，PSTN)、外部电路数据网和分组数据网、因特网(internet)和企业内部网(intranets)、以及移动自己的短信息服务(short message service，SMS)服务器等功能。核心网提供的基本业务可以包括移动办公、电子商务、通信、娱乐性业务、旅行和基于位置的服务、遥感业务(telemetry)-简单消息传递业务(监视控制)等。
其中，外部网络可以为向用户提供数据传输服务的运营商网络，如：可以为向用户提供IP多媒体业务(IP multi-media service，IMS)的运营商网络等。DN中可以部署有应用服务器，该应用服务器可以向用户提供数据传输服务。具体的，运营商可以包括公共陆地移动网络(public land mobile network，PLMN)，PLMN为政府或政府所批准的经营者， 为公众提供陆地移动通信业务而建立和经营的网络，例如，可以是移动运营商、联通运营商或电信运营商等。
具体实现时，图1a所示，如：各个终端设备、网络设备均可以采用图2所示的组成结构，或者包括图2所示的部件。图2为本申请实施例提供的一种通信装置200的组成示意图，该通信装置200可以为终端设备或者终端设备中的芯片或者片上系统；也可以为网络设备或者网络设备中的芯片或者片上系统。如图2所示，该通信装置200包括处理器201，收发器202以及通信线路203。
进一步的，该通信装置200还可以包括存储器204。其中，处理器201，存储器204以及收发器202之间可以通过通信线路203连接。
其中，处理器201是中央处理器(central processing unit，CPU)、通用处理器网络处理器(network processor，NP)、数字信号处理器(digital signal processing，DSP)、微处理器、微控制器、可编程逻辑器件(programmable logic device，PLD)或它们的任意组合。处理器201还可以是其它具有处理功能的装置，例如电路、器件或软件模块，不予限制。
收发器202，用于与其他设备或其它通信网络进行通信。该其它通信网络可以为以太网，无线接入网(radio access network，RAN)，无线局域网(wireless local area networks，WLAN)等。收发器202可以是模块、电路、收发器或者任何能够实现通信的装置。
通信线路203，用于在通信装置200所包括的各部件之间传送信息。
存储器204，用于存储指令。其中，指令可以是计算机程序。
其中，存储器204可以是只读存储器(read-only memory，ROM)或可存储静态信息和/或指令的其他类型的静态存储设备，也可以是随机存取存储器(random access memory，RAM)或可存储信息和/或指令的其他类型的动态存储设备，还可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或其他磁存储设备等，不予限制。
需要指出的是，存储器204可以独立于处理器201存在，也可以和处理器201集成在一起。存储器204可以用于存储指令或者程序代码或者一些数据等。存储器204可以位于通信装置200内，也可以位于通信装置200外，不予限制。处理器201，用于执行存储器204中存储的指令，以实现本申请下述实施例提供的通信方法。
在一种示例中，处理器201可以包括一个或多个CPU，例如图2中的CPU0和CPU1。
作为一种可选的实现方式，通信装置200包括多个处理器，例如，除图2中的处理器201之外，还可以包括处理器207。
作为一种可选的实现方式，通信装置200还包括输出设备205和输入设备206。示例性地，输入设备206是键盘、鼠标、麦克风或操作杆等设备，输出设备205是显示屏、扬声器(speaker)等设备。
需要指出的是，通信装置200可以是台式机、便携式电脑、网络服务器、移动手机、平板电脑、无线终端、嵌入式设备、芯片系统或有图2中类似结构的设备。此外，图2中示出的组成结构并不构成对该通信装置的限定，除图2所示部件之外，该通信装置可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。
本申请实施例中，芯片系统可以由芯片构成，也可以包括芯片和其他分立器件。
此外，本申请的各实施例之间涉及的动作、术语等均可以相互参考，不予限制。本申请的实施例中各个设备之间交互的消息名称或消息中的参数名称等只是一个示例，具体实现中也可以采用其他的名称，不予限制。
本申请实施例所示的通信方法可以应用于第一通信装置与第二通信装置之间的通信，其中，第一通信装置可以为终端设备或网络设备。第二通信装置可以为终端设备或网络设备。如下实施例以第一通信装置为终端设备，第二通信装置为网络设备举例进行说明。需要说明的是，本申请实施例所示的通信方法可以应用于终端设备与网络设备之间的通信，也可以适用于终端设备与终端设备之间的通信，还可以应用于网络设备与网络设备之间的通信。其中，网络设备与网络设备之间的通信可以是宏基站与宏基站、微基站与微基站、宏基站与微基站之间的多点协同传输。
下面结合图1a所示通信系统，以本申请实施例所示的通信方法应用于终端设备与网络设备之间的通信为例，对本申请实施例提供的通信方法进行描述，其中，终端设备可以为通信系统中的任一终端设备；网络设备可以为通信系统中的任一网络设备。下述实施例所述的终端设备、网络设备可以具备图2所示部件。
图3a为本申请实施例提供的一种通信方法的流程图，如图3a所示，该方法可以包括：
步骤301、终端设备确定第一取值候选集。
其中，第一取值候选集可以与终端设备的终端类型对应；第一取值候选集可以包括终端类型对应的RRC参数的取值候选集。
可选的，RRC参数的类型可以为下述一种或多种：数据传输的配置参数、信道状态信息(channel state information，CSI)测量反馈的配置参数、初始接入的配置参数、移动性的配置参数、功率控制的配置参数、波束管理的配置参数、其他类型的配置参数等。具体的，本申请对此不做限定。
可选的，RRC参数包括下述一种或多种：子载波间隔(subcarrier spacing，SCS)配置参数、CSI上报频域配置参数、CSI上报时域配置参数、信道质量信息(channel quality information，CQI)表格、波束失败恢复定时、配置准许配置参数、子带大小指示、部分带宽(bandwidth part，BWP)配置参数、码块组(code block group，CBG)配置参数、波束失败实例最大个数(beam-failure-instance-maxcount)配置参数、CSI测量配置参数、物理上行控制信道(physical uplink control channel，PUCCH)格式配置参数、协议38.331中的RRC参数、其他RRC参数等。具体的，本申请对此不做限定。
其中，配置准许配置参数可以包括下述一种或多种：频域跳频指示(frequency hopping)、调制和编码方案(modulation and coding scheme，MCS)表格、资源分配(resource allocation)、重复次数、重复K次的冗余版本、周期、协议38.331中的配置准许配置参数、其他配置准许配置参数等。具体的，本申请对此不做限定。
可选的，每个RRC参数的取值候选集为该RRC参数取值的全集的子集。
例如，对于SCS配置参数，SCS包括15kHz，30kHz，60kHz，120kHz和240kHz，其他子载波间隔等。具体的，本申请对此不做限定。举例来说，SCS配置参数取值可以包括至少一个候选集，每个候选集可以包括15kHz，30kHz，60kHz，120kHz和240kHz，其他子载波间隔取值等中的一种或多种。
例如，在CSI上报频域配置参数中，CSI上报频域方式可以是全带上报(wideband)， 子带上报(subband)，子带上报指示(csi-reporting band)，其他CSI上报频域方式等。具体的，本申请对此不做限定。举例来说，CSI上报频域配置参数可以包括至少一个候选集，每个候选集可以包括全带上报，子带上报，子带上报指示，其他CSI上报频域配置参数等中的一种或多种。
例如，CQI表格可以包括table1，table2，table3，其他CQI表格等。具体的，本申请对此不做限定。举例来说，CQI表格可以包括至少一个候选集，每个候选集可以包括table1，table2，table3，其他CQI表格等中的一种或多种。比如，table1为64QAM正常码率的CQI表格，table2为256QAM的CQI表格，table3为64QAM低码率的CQI表格等，具体的，本申请对此不做限定。需要说明的是，对table1，table2，table3的具体描述可以参照现有通信协议对CQI表格的相关描述，不予赘述。
例如，在子带大小指示中，子带大小可以包括value1，value2，其他子带大小等。具体的，本申请对此不做限定。举例来说，子带大小指示可以包括至少一个候选集，每个候选集可以包括value1，value2，其他子带大小等中的一种或多种。
例如，在波束失败恢复定时中，定时器取值可以包括10ms，20ms，40ms，60ms，80ms，100ms，150ms，200ms，其他定时器取值等。具体的，本申请对此不做限定。举例来说，波束失败恢复定时可以包括至少一个候选集，每个候选集可以包括10ms，20ms，40ms，60ms，80ms，100ms，150ms，200ms，其他定时器取值等中的一种或多种。
例如，频域跳频指示可以包括时隙内跳频(intraslot)和时隙间跳频(interslot)。具体的，本申请对此不做限定。举例来说，频域跳频指示可以包括至少一个候选集，每个候选集可以包括时隙内跳频，时隙间跳频中的一种或多种。
例如，MCS表格可以为256QAM，正常码率64QAM和低码率64QAM，其他MCS表格等。具体的，本申请对此不做限定。举例来说，MCS表格可以包括至少一个候选集，每个候选集可以包括256QAM，正常码率64QAM和低码率64QAM，其他MCS表格等中的一种或多种。
例如，资源分配可以包括类型0，类型1和动态切换，其他资源分配方式等。具体的，本申请对此不做限定。举例来说，资源分配可以包括至少一个候选集，每个候选集可以包括类型0，类型1和动态切换，其他资源分配方式等中的一种或多种。
例如，重复次数可以包括重复1次，2次，4次，8次，其他次数等。具体的，本申请对此不做限定。举例来说，重复次数可以包括至少一个候选集，每个候选集可以包括重复1次，2次，4次，8次中的一种或多种。
例如，重复K次的冗余版本可以为0，2，3，1，或者，0，3，0，3，或者，0，0，0，0，其他冗余版本等。具体的，本申请对此不做限定。举例来说，重复K次的冗余版本可以包括至少一个候选集，每个候选集可以包括0，2，3，1，或者，0，3，0，3，或者，0，0，0，0中的一种或多种。
例如，周期可以包括多种取值。周期可以包括至少一个候选集，每个候选集可以包括一种或多种周期取值。
可选的，RRC参数的取值候选集用于指示RRC参数的配置方式。
其中，配置方式包括配置参数域，配置参数域包括配置方式的配置参数；或者，配置方式包括配置参数。
例如，以RRC参数为配置准许配置参数为例，配置准许配置参数取值的候选集可以用于指示配置准许配置参数的配置方式，配置方式可以包括配置参数域，配置参数域可以包括频域跳频指示、MCS表格、资源分配、重复次数、重复K次的冗余版本、周期中的一种或多种，以配置参数域包括频域跳频指示为例，配置参数域可以包括频域跳频指示的配置参数。
又例如，以RRC参数为SCS配置参数为例，SCS配置参数取值的候选集可以用于指示SCS配置参数的配置方式，配置方式可以包括配置参数，例如配置方式可以包括15kHz、30kHz、60kHz、120kHz和240kHz中的一种或多种。
可选的，在确定终端设备对应的终端类型时，根据下述因素中的一种或多种确定终端设备对应的终端类型：业务类型、移动性、传输时延需求、信道环境、可靠性需求、覆盖需求、通信场景。
其中，业务类型可以根据业务数据的大小确定，例如，业务类型可以包括大包数据、中包数据、小包数据等。移动性可以包括移动、固定；其中，移动也可以包括不规律移动、沿固定路线移动、超短距离移动等。传输时延需求可以包括高传输时延、低传输时延和传输时延一般等。信道环境可以包括信道环境多变、信道环境稳定、信道环境相对稳定等。可靠性需求可以包括高可靠性、低可靠性、可靠性一般等。覆盖需求可以包括广覆盖、强覆盖、弱覆盖、一般覆盖、深覆盖等。通信场景可以包括前述对通信系统进行描述时所包括的通信场景，或者通信场景也可以包括上行通信、下行通信、上下行通信、旁链路通信、回传通信、接入通信、中继通信、卫星通信、太赫兹通信、光通信、绿色通信等，不予限制。
示例性的，如图4所示，以终端类型包括eMBB设备、URLLC设备、NB-IoT设备、CPE设备为例，其中，eMBB设备主要用于传输大包数据，也可以用于传输小包数据，一般处于移动状态，对于传输时延和可靠性的需求一般，上下行通信均有，信道环境比较复杂多变，可以室内通信，也可以室外通信，例如，eMBB设备可以为手机。URLLC设备主要用于传输小包数据，也可以传输中包数据，一般属于非移动状态，或者可以沿固定路线移动，对于传输时延和可靠性的需求较高，即要求低传输时延和高可靠性，上下行通信均有，信道环境稳定，例如，URLLC设备可以为工厂设备。NB-IoT设备主要用于传输小数据，一般处于非移动状态，且位置已知，对于传输时延和可靠性需求中等，上行通信较多，信道环境相对稳定，例如，NB-IoT设备可以是智能水表、传感器。CPE设备主要用于传输大包数据，一般处于非移动状态，或者可以进行超短距离移动，对于传输时延和可靠性的需求中等，上下行通信均有，信道环境相对稳定，例如，CPE设备可以是智慧家庭中的终端设备、AR、VR等。当确定终端设备的终端类型时，可以根据终端设备的业务类型、移动性、传输时延需求、可靠性需求、信道环境和通信场景，将终端设备对应的终端类型确定为eMBB设备、URLLC设备、NB-IoT设备或CPE设备。
需要说明的是，eMBB设备也可以描述为eMBB，URLLC设备也可以描述为URLLC，NB-IoT设备也可以描述为NB-IoT，CPE设备也可以描述为CPE，V2X设备也可以描述为V2X，不予限制。
可选的，根据终端类型确定终端类型对应的第一取值候选集。其中，第一取值候选集可以包括终端类型对应的RRC参数的取值候选集。
可选的，不同的终端类型对应不同的第一取值候选集。
其中，RRC参数的取值候选集用于指示RRC参数的配置方式；其中，配置方式包括配置参数域，配置参数域包括配置方式的配置参数；或者，配置方式包括配置参数。
具体的，终端类型与RRC参数的取值候选集具有对应关系，也可以包括如下一项或多项：终端类型与RRC参数的类型具有对应关系，终端类型与RRC参数对应的配置方式具有对应关系，终端类型与RRC参数对应的配置方式的配置参数域具有对应关系，终端类型与RRC参数的配置参数具有对应关系。
如下实施例为一种通信的方法，该方法中可以根据终端类型定制化RRC参数，实现功能与终端匹配，最优满足各类设备需求，降低信令开销，降低参数切换下的时延，可以降低通信复杂度，降低芯片成本。本申请实施例可以作为独立的实施例，也可以与本发明中的其他实施例相结合，具体的，本申请对此不做限定。
作为一种可能的实现方式，终端类型与RRC参数的类型具有对应关系。
如下实施例为一种RRC参数类型的设计方法，该方法中可以根据终端类型定制化RRC参数类型，实现功能类型与终端匹配，最优满足各类设备需求，降低信令开销，降低参数切换下的时延，可以降低通信复杂度，降低芯片成本。本申请实施例可以作为独立的实施例，也可以与本发明中的其他实施例相结合，具体的，本申请对此不做限定。
具体的，对于不同的终端类型，终端类型对应的通信需求可能不同，因此终端设备可以不用支持上述RRC参数类型中的至少一种，因此可以根据终端类型确定适用于终端设备进行通信的RRC参数类型，以满足不同终端类型的终端设备对通信的不同需求，同时降低信令开销。
可选的，终端设备和/或网络设备可以根据终端类型确定RRC参数的类型的候选集。
比如，终端类型与RRC参数的类型的候选集具有对应关系，其中，对应关系可以是协议预定义的，也可以是网络设备通过高层信令或物理层信令告知终端设备的，具体的，本申请对此不做限定。
示例性的，当终端设备始终处于静止状态时，该终端设备可以不用支持波束管理，网络设备可以不用为该终端设备配置波束管理的配置参数。当终端设备始终进行小包传输或近距离传输时，该终端设备可以不用支持功率控制，网络设备可以不用为该终端设备配置功率控制的配置参数。
示例性的，当终端类型为eMBB时，eMBB对应的RRC参数的类型可以包括数据传输的配置参数、CSI测量反馈的配置参数、初始接入的配置参数、移动性的配置参数、功率控制的配置参数和波束管理的配置参数。
例如，eMBB中，数据传输的配置参数可以包括SCS配置参数；CSI测量反馈的配置参数可以包括波束失败恢复定时；波束管理的配置参数可以包括CSI上报时域配置参数。
示例性的，当终端类型为URLLC时，URLLC对应的RRC参数的类型可以包括数据传输的配置参数、信道状态信息CSI测量反馈的配置参数和波束管理的配置参数。
通过上述设计，因为URLLC主要是小包业务传输，因此可以不进行功率控制，降低复杂度。另外URLLC主要是静止场景或固定路径的移动场景，信道状态相对稳定，因此也可以不进行CSI测量反馈，采用低速率传输，降低功耗，提高通信效率。另外，为了机械手臂等类型的URLLC场景下，可以进行波束管理实现波束对准，位置预测，提前准备 数据传输，可以降低时延，满足业务的精准操作和时延的需求，提高通信效率。
例如，URLLC中，数据传输的配置参数可以包括SCS配置参数等；CSI测量反馈的配置参数可以包括CSI上报时域配置参数等；波束管理的配置参数可以包括CSI上报时域配置参数等。
示例性的，当终端类型为NB-IoT时，NB-IoT对应的RRC参数的类型包括数据传输的配置参数、初始接入的配置参数、移动性的配置参数。
通过上述设计，因为NB-Iot的应用场景可以是高速移动的场景，因此可以进行移动性管理，可以不进行功率控制，降低复杂度。另外，也可以不进行CSI测量反馈，采用低速率传输，降低功耗，提高通信效率。
例如，NB-IoT中，数据传输的配置参数可以包括SCS配置参数等。
示例性的，当终端类型为CPE时，CPE对应的RRC参数的类型可以包括数据传输的配置参数和信道状态信息CSI测量反馈的配置参数。
例如，CPE中，数据传输的配置参数可以包括SCS配置参数；CSI测量反馈的配置参数可以包括CSI上报时域配置参数。
通过上述设计，因为CPE的应用场景主要是静止的大数据传输，因此可以采用高功耗模式，不需要进行功率控制，比如以最大功率发送。高速率传输，没有移动性，没有波束管理，降低复杂度，降低功耗，提高通信效率。
具体的，可以进一步根据终端类型的通信需求为终端类型确定终端类型对应的各个RRC参数的取值候选集，终端类型对应的第一取值候选集即终端类型对应的各个RRC参数的取值候选集的集合。
示例性的，以RRC参数为SCS配置参数，且SCS配置参数取值的全集包括15kHz，30kHz，60kHz，120kHz，240kHz为例，可以根据终端类型确定终端类型对应的SCS配置参数取值的候选集。
可选的，终端设备和/或网络设备可以根据终端类型确定SCS配置参数取值的候选集。本申请实施例可以作为独立的实施例，也可以与本申请中的其他实施例相结合，具体的，本申请对此不做限定。
比如，终端类型与SCS配置参数取值的候选集具有对应关系，其中，对应关系可以是协议预定义的，也可以是网络设备通过高层信令或物理层信令告知终端设备的，具体的，本申请对此不做限定。
如，终端类型A可以对应SCS配置参数取值的候选集A，终端类型B可以对应SCS配置参数取值的候选集B，…，终端类型X可以对应SCS配置参数取值的候选集X。
例如，当终端类型为eMBB时，SCS配置参数取值的候选集可以包括15kHz，30kHz，120kHz，240kHz。
通过上述设计，因为eMBB主要是中大包业务传输，且不需要满足低时延可靠性的需求，因此可以针对FR1频段采用15kHz，30kHz等比较小的子载波间隔进行数据传输，提高通信效率。
例如，当终端类型为URLLC时，SCS配置参数取值的候选集可以包括30kHz，60kHz，120kHz或240kHz。
通过上述设计，因为URLLC主要是小包业务传输，且需要满足低时延可靠性的需求， 因此可以针对FR1频段采用相对较大的子载波间隔进行数据传输，比如30kHz，60kHz等，针对FR2频段采用120kHz等比较大的子载波间隔进行数据传输可以满足低时延需求，在一定时间单元内多次重复传输。
例如，当终端类型为NB-IoT时，SCS配置参数取值的候选集可以包括15kHz，120kHz。
通过上述设计，因为NB-IoT主要是小包业务传输，且不需要满足低时延可靠性的需求，因此可以针对FR1频段采用15kHz等比较小的子载波间隔，针对FR2频段采用120kHz等比较小的子载波间隔进行数据传输，提高通信效率。
例如，当终端类型为CPE时，SCS配置参数取值的第一候选集可以包括15kHz，120kHz，SCS配置参数取值的第二候选集可以包括30kHz，240kHz。
通过上述设计，因为CPE主要是大包业务传输，当不需要满足低时延可靠性的需求，因此可以针对FR1频段采用15kHz等比较小的子载波间隔，针对FR2频段采用120kHz等比较小的子载波间隔进行数据传输，提高通信效率；当需要满足低时延可靠性的需求，因此可以针对FR1频段采用30kHz等比较小的子载波间隔，针对FR2频段采用240kHz等比较大的子载波间隔进行数据传输，满足时延需求，提高通信效率。
进一步的，不同频点的频带可以对应不同的SCS配置参数取值的全集。
例如，对于频率范围1(frequency range 1，FR1)，SCS配置参数取值的全集可以包括15kHz，30kHz，60kHz等；对于频率范围2(frequency range 2，FR2)，SCS配置参数取值的全集可以包括60kHz，120kHz，240kHz等；其中，FR1可以为6G以下的频带；FR2可以为6G以上的频带。
可选的，终端设备和/或网络设备可以根据终端类型和频带确定SCS配置参数取值的候选集。本申请实施例可以作为独立的实施例，也可以与本申请中的其他实施例相结合，具体的，本申请对此不做限定。
比如，终端类型，频带与SCS配置参数取值的候选集具有对应关系，其中，对应关系可以是协议预定义的，也可以是网络设备通过高层信令或物理层信令告知终端设备的，具体的，本申请对此不做限定。
如，终端类型A对于FR1可以对应SCS配置参数取值的候选集A1，对于FR2可以对应SCS配置参数取值的候选集A2；终端类型B对于FR1可以对应SCS配置参数取值的候选集B1，对于FR2可以对应SCS配置参数取值的候选集B2；…；终端类型X对于FR1可以对应SCS配置参数取值的候选集X1，对于FR2可以对应SCS配置参数取值的候选集X2。
例如，当终端类型为eMBB时，对于FR1，SCS配置参数取值的候选集可以包括15kHz，30kHz；对于FR2，SCS配置参数取值的候选集可以包括120kHz，240kHz。具体的分析描述可以如上，在此不再赘述。
例如，当终端类型为URLLC时，对于FR1，SCS配置参数取值的候选集可以包括30kHz，60kHz；对于FR2，SCS配置参数取值的候选集可以包括120kHz。具体的分析描述可以如上，在此不再赘述。
例如，当终端类型为NB-IoT时，对于FR1，SCS配置参数取值的候选集可以包括15kHz；对于FR2，SCS配置参数取值的候选集可以包括120kHz。具体的分析描述可以如上，在此不再赘述。
例如，当终端类型为CPE时，对于FR1，SCS配置参数取值的候选集可以包括15kHz；对于FR2，SCS配置参数取值的候选集可以包括120kHz。具体的分析描述可以如上，在此不再赘述。
上述实施例中，针对终端类型以及频带设计SCS配置参数取值的候选集，相比于仅根据终端类型设计SCS配置参数取值的候选集，可以进一步降低信令开销。
示例性的，以RRC参数为CSI上报频域配置参数，且CSI上报频域配置参数取值的全集包括全带上报，子带上报，子带上报指示为例，可以根据终端类型确定终端类型对应的CSI上报频域配置参数取值的候选集。
可选的，终端设备和/或网络设备可以根据终端类型确定CSI上报频域配置参数取值的候选集。本申请实施例可以作为独立的实施例，也可以与本申请中的其他实施例相结合，具体的，本申请对此不做限定。
比如，终端类型与CSI上报频域配置参数取值的候选集具有对应关系，其中，对应关系可以是协议预定义的，也可以是网络设备通过高层信令或物理层信令告知终端设备的，具体的，本申请对此不做限定。
如，终端类型A可以对应CSI上报频域配置参数取值的候选集AC，终端类型B可以对应CSI上报频域配置参数取值的候选集BC，…，终端类型X可以对应CSI上报频域配置参数取值的候选集XC。
例如，当终端类型为eMBB时，CSI上报频域配置参数取值的候选集可以包括全带上报，子带上报，子带上报指示。
通过上述设计，因为eMBB的通信场景包括室内，室外，高移动速度的场景，低移动速度的场景，静止场景等等。因此信道状态相对比较复杂，因此可以采用的CSI测量反馈的CSI上报频域配置参数取值可以包括全带上报，子带上报，子带上报指示，满足各种场景下的需求，按需指示，降低功耗，提高通信效率。
例如，当终端类型为URLLC时，CSI上报频域配置参数取值的候选集可以包括全带上报或者子带上报。
通过上述设计，因为URLLC主要是静止场景或固定路径的移动场景，信道状态相对稳定，因此可以采用的CSI测量反馈的CSI上报频域配置参数可以是全带上报或者子带上报，降低功耗，提高通信效率。
例如，当终端类型为NB-IoT时，CSI上报频域配置参数取值的候选集可以包括全带上报，子带上报。
通过上述设计，因为NB-IoT的应用场景主要是静止场景比如智能水表等，信道状态相对稳定，因此可以采用的CSI测量反馈的CSI上报频域配置参数可以是全带上报。而针对NB-IoT的高速场景下可以采用的CSI测量反馈的CSI上报频域配置参数可以是子带上报，满足各种场景下的需求，按需指示，降低功耗，提高通信效率。
例如，当终端类型为CPE时，CSI上报频域配置参数取值的候选集可以包括全带上报。
通过上述设计，因为CPE的应用场景主要是静止的大数据传输，因此采用的CSI测量反馈的CSI上报频域配置参数可以是全带上报，降低复杂度，降低功耗，提高通信效率。
示例性的，以RRC参数为CQI表格，且CQI表格取值的全集包括table1，table2，table3为例，可以根据终端类型确定终端类型对应的CQI表格取值的候选集。如，终端类型A可 以对应CQI表格取值的候选集AQ，终端类型B可以对应CQI表格取值的候选集BQ，…，终端类型X可以对应CQI表格取值的候选集XQ。
例如，当终端类型为eMBB时，CQI表格取值的候选集可以包括table1，table2，table3。
通过上述设计，因为eMBB主要是中大包业务传输，也有小包业务传输，因此考虑多种应用场景，可以设计eMBB的CQI表格取值的候选集可以包括table1，table2，table3，满足不同场景下的需求，提高通信效率。
例如，当终端类型为URLLC时，CQI表格取值的候选集可以包括table3。
通过上述设计，因为URLLC主要是小包业务传输，且需要满足低时延可靠性的需求，因此可以设计URLLC的CQI表格取值的候选集可以包括table3，即64QAM低码率的CQI表格，可以满足高可靠性需求，提高通信效率。
例如，当终端类型为NB-IoT时，CQI表格取值的候选集可以包括table1。
通过上述设计，因为NB-IoT主要是小包业务传输，且不需要满足低时延可靠性的需求，因此可以设计URLLC的CQI表格取值的候选集可以包括table1，即64QAM正常码率的CQI表格，可以满足通信需求，提高通信效率。
例如，当终端类型为CPE时，CQI表格取值的候选集可以包括table2，table3。
通过上述设计，因为CPE主要是大包业务传输，当不需要满足低时延可靠性的需求，可以设计CQI表格取值的候选集可以包括table2，即256QAM的CQI表格，实现大包快速传输，提高通信效率；当需要满足低时延可靠性的需求，可以设计CQI表格取值的候选集可以包括table3，即64QAM低码率的CQI表格，满足可靠性需求，提高通信效率。
示例性的，以RRC参数为波束失败恢复定时，且波束失败恢复定时取值的全集包括10ms，20ms，40ms，60ms，80ms，100ms，150ms，200ms为例，可以根据终端类型确定终端类型对应的波束失败恢复定时取值的候选集。
可选的，终端设备和/或网络设备可以根据终端类型确定波束失败恢复定时取值的候选集。本申请实施例可以作为独立的实施例，也可以与本申请中的其他实施例相结合，具体的，本申请对此不做限定。
比如，终端类型与波束失败恢复定时取值的候选集具有对应关系，其中，对应关系可以是协议预定义的，也可以是网络设备通过高层信令或物理层信令告知终端设备的，具体的，本申请对此不做限定。
如，终端类型A可以对应波束失败恢复定时取值的候选集AT，终端类型B可以对应波束失败恢复定时取值的候选集BT，…，终端类型X可以对应波束失败恢复定时取值的候选集XT。
例如，当终端类型为eMBB时，波束失败恢复定时取值的候选集可以包括10ms，20ms，40ms，60ms，80ms，100ms，150ms，200ms。
通过上述设计，因为eMBB的通信场景包括室内，室外，高移动速度的场景，低移动速度的场景，静止场景等等。因此信道状态相对比较复杂，可以波束失败恢复定时取值的候选集可以包括10ms，20ms，40ms，60ms，80ms，100ms，150ms，200ms等多种取值，满足各种场景下的需求，按需指示，降低功耗，提高通信效率。
例如，当终端类型为URLLC时，波束失败恢复定时取值的候选集可以包括10ms，20ms，40ms。
通过上述设计，因为URLLC主要是静止场景或固定路径的移动场景，但是需要满足低时延高可靠的需求，因此可以采用的波束失败恢复定时取值的候选集可以包括10ms，20ms，40ms，快速实现波束恢复，降低时延，提高通信效率。
例如，当终端类型为NB-IoT时，波束失败恢复定时取值的候选集可以包括80ms，100ms，150ms，200ms。
通过上述设计，因为NB-Iot的应用场景主要是静止场景比如智能水表等，信道状态相对稳定，因此可以采用的波束失败恢复定时取值的候选集可以包括80ms，100ms，150ms，200ms，波束失败恢复定时的取值较大，按需指示，可以降低功耗，提高通信效率。
例如，当终端类型为CPE时，波束失败恢复定时取值的候选集可以包括20ms，60ms，80ms。
通过上述设计，因为CPE的应用场景主要是静止的大数据传输，但是某些场景下需要满足低时延高可靠的需求，因此采用的波束失败恢复定时取值的候选集可以包括20ms，60ms，80ms，降低复杂度，降低时延，提高通信效率。
示例性的，以RRC参数为CSI上报时域配置参数，且CSI上报时域配置参数取值的全集包括周期性上报、非周期性上报、半持续性上报为例，可以根据终端类型确定终端类型对应的CSI上报时域配置参数取值的候选集。
可选的，终端设备和/或网络设备可以根据终端类型确定CSI上报时域配置参数取值的候选集。本申请实施例可以作为独立的实施例，也可以与本申请中的其他实施例相结合，具体的，本申请对此不做限定。
比如，终端类型与CSI上报时域配置参数取值的候选集具有对应关系，其中，对应关系可以是协议预定义的，也可以是网络设备通过高层信令或物理层信令告知终端设备的，具体的，本申请对此不做限定。
如，终端类型A可以对应CSI上报时域配置参数取值的候选集AS，终端类型B可以对应CSI上报时域配置参数取值的候选集BS，…，终端类型X可以对应CSI上报时域配置参数取值的候选集XS。
例如，当终端类型为eMBB时，CSI上报时域配置参数取值的候选集可以包括周期性上报、非周期性上报、半持续性上报。
通过上述设计，因为eMBB的通信场景包括室内，室外，高移动速度的场景，低移动速度的场景，静止场景等等。因此信道状态相对比较复杂，因此可以采用的CSI上报时域配置参数取值的候选集可以包括周期性上报、非周期性上报、半持续性上报，满足各种场景下的需求，按需指示，降低功耗，提高通信效率。
例如，当终端类型为URLLC时，CSI上报时域配置参数取值的候选集可以包括非周期性上报。
通过上述设计，因为URLLC主要是静止场景或固定路径的移动场景，信道状态相对稳定，但是需要满足低时延的需求，因此可以采用的CSI测量反馈的CSI上报时域配置参数可以是非周期性上报，按需指示，降低功耗，降低时延，提高通信效率。
例如，当终端类型为CPE时，CSI上报时域配置参数取值的候选集可以包括周期性上报。
通过上述设计，因为CPE的应用场景主要是静止的大数据传输，信道状态相对稳定， 因此采用的CSI测量反馈的CSI上报时域配置参数可以是周期性上报，降低复杂度，降低功耗，提高通信效率。
基于上述终端类型与各个RRC参数的取值候选集的对应关系，可以将终端类型对应的各个RRC参数的取值候选集的集合确定为终端类型对应的第一取值候选集。
基于上述终端类型与第一取值候选集之间的对应关系，终端设备可以根据下述方式一至方式四中的至少一种确定终端设备的终端类型对应的第一取值候选集。
方式一：第一取值候选集是通信协议预先规定的。
其中，可以采用机器学习、神经网络等训练模型为终端类型确定终端类型对应的RRC参数，以及终端类型对应的各个RRC参数的取值候选集。或者，可以根据网络设备在一段时间内根据各个终端设备的通信需求为各个终端设备配置的RRC参数取值，确定终端类型对应的RRC参数，以及终端类型对应的各个RRC参数的取值候选集。或者，也可以根据通信经验确定终端类型对应的RRC参数，以及终端类型对应的各个RRC参数的取值候选集。
例如，可以通过机器学习或神经网络等训练模型确定终端设备在不同RRC参数组合和/或RRC参数取值的不同候选集下的通信质量，根据通信质量确定终端类型对应的RRC参数，以及终端类型对应的各个RRC参数的取值候选集。
又例如，以终端类型A包括终端设备1、终端设备2和终端设备3为例，可以根据网络设备在一段时间内为终端设备1、终端设备2和终端设备3配置的RRC参数取值，确定终端类型A对应的RRC参数，以及终端类型对应的各个RRC参数的取值候选集。
具体的，可以将各个终端类型对应的第一取值候选集写入通信协议中，便于网络设备与终端设备根据通信协议确定终端设备的终端类型对应的第一取值候选集，避免网络设备向终端设备发送第一取值候选集，节省信令开销，降低通信时延，降低终端功耗。
方式二：网络设备向终端设备发送第一取值候选集。
其中，网络设备可以在随机接入过程中或者在终端设备初始接入网络时，根据终端设备的终端类型确定终端设备对应的第一取值候选集，并将该第一取值候选集下发给终端设备。
或者，网络设备可以通过高层信令或物理层信令发送第一取值候选集，终端设备根据网络设备的指示确定第一取值候选集。
通过上述方案，网络设备可以配置第一取值候选集，实现第一取值候选集的配置灵活性，更好的适应的不同场景，满足不同场景的需求，降低取值指示的开销，提高通信效率。
方式三、终端设备向网络设备发送第一请求信息，网络设备根据该第一请求信息，向终端设备发送第一取值候选集。
其中，第一请求信息用于请求终端设备的终端类型对应的RRC参数的取值候选集。
可选的，第一请求信息包括终端设备确定的终端类型对应的RRC参数的取值候选集。
具体的，终端设备可以根据自身的通信需求，确定适合于自身进行通信的RRC参数的取值候选集，并将该RRC参数的取值候选集发送给网络设备。当网络设备接收到终端设备发送的RRC参数的取值候选集后，判断终端设备是否可以使用该RRC参数的取值候选集，如果可以，则将该RRC参数的取值候选集作为第一取值候选集发送给终端设备，如果不可以，则网络设备可以根据终端设备的终端类型，确定终端设备对应的第一取值候 选集，并将第一取值候选集发送给终端设备。
通过上述方案，终端设备可以向网络设备发送建议的第一取值候选集，实现第一取值候选集的配置灵活性，更好的满足终端设备的通信需求，更好的适应的不同场景，满足不同场景的需求，降低取值指示的开销，提高通信效率。
方式四、终端设备向网络设备发送第一特征信息，网络设备根据该第一特征信息，向终端设备发送第一取值候选集。
其中，第一特征信息可以用于指示终端设备的终端类型。
可选的，第一特征信息可以为终端设备的终端类型，或者为用于指示终端设备的终端类型的通信需求，该通信需求可以为业务类型、移动性、传输时延需求、信道环境、可靠性需求、覆盖需求、通信场景中的一种或多种。
具体的，网络设备可以根据终端设备发送的第一特征信息，确定终端设备的终端类型，并确定终端类型对应的第一取值候选集，并将第一取值候选集发送给终端设备。
通过上述方案，终端设备可以向网络设备发送第一特征信息，通过第一特征信息确定第一取值候选集，实现第一取值候选集的配置灵活性，更好的满足终端设备的通信需求，更好的适应的不同场景，满足不同场景的需求，降低取值指示的开销，提高通信效率。
步骤302、网络设备向终端设备发送第一取值。相应的，终端设备接收第一取值。
其中，第一取值包括第一取值候选集中的一组RRC参数取值。
可选的，当第一取值候选集中包括一个取值时，比如第一取值候选集中仅包括第一取值，网络设备可以不向终端设备发送第一取值。此时，终端设备和网络设备可以确定该RRC参数取值为第一取值。
可选的，当第一取值候选集中包括多个取值时，比如第一取值候选集中包括第一取值，第二取值等，网络设备可以不向终端设备发送第一取值。此时，终端设备和网络设备可以确定该RRC参数取值为默认取值。其中，默认取值包括第一取值候选集中终端类型对应的RRC参数取值。即，当网络设备没有向终端设备指示RRC参数取值时，RRC参数取值为默认取值，或者，当终端设备没有收到网络设备指示的RRC参数取值时，RRC参数取值为默认取值。
进一步的，RRC参数取值的默认取值可以是协议预定义的，也可以是网络设备通过高层信令或物理层信令告知终端设备的。
通过上述方式，可以当RRC参数取值为默认取值时，可以降低信令开销，提高通信性能。
具体的，网络设备可以根据终端设备对应的第一取值候选集，从第一取值候选集中确定第一取值，并将第一取值发送给终端设备。
示例性的，以终端设备A对应的第一取值候选集包括SCS配置参数和CSI上报频域配置参数，且SCS配置参数取值的候选集包括15kHz，30kHz，120kHz，240kHz，CSI上报频域配置参数取值的候选集包括全带上报，子带上报，子带上报指示为例，网络设备可以根据终端设备的通信需求为终端设备A确定第一取值，如，第一取值包括SCS配置参数、CSI上报频域配置参数，且SCS配置参数取值为15kHz，CSI上报频域配置参数取值为全带上报。
步骤303、终端设备根据第一取值进行通信。
基于上述图3a所示的方法，通过根据终端类型确定终端类型对应的第一取值候选集，可以使得网络设备从第一取值候选集中为终端设备确定第一取值，降低RRC信令开销，降低终端设备的存储开销，同时降低终端设备的功耗。
基于上述图3a所示的方法，可替换的，如图3b所示，可以从第一通信装置的角度对本申请实施例提供的通信方法进行描述。
图3b为本申请实施例提供的一种通信方法的流程图，如图3b所示，该方法可以包括：
步骤301a、第一通信装置确定第一通信装置的终端类型对应的RRC参数的取值候选集。
具体的，对第一通信装置确定第一通信装置的终端类型对应的RRC参数的取值候选集的具体描述可以参照上述步骤301中终端设备确定终端设备的终端类型对应的RRC参数的取值候选集的具体描述，不予赘述。
需要说明的是，该步骤可以省略。
步骤302a、第一通信装置发送第一请求信息和/或第一特征信息。
具体的，对第一通信装置发送第一请求信息和/或第一特征信息的具体描述可以参照上述步骤301中终端设备发送第一请求信息和/或第一特征信息的具体描述，不予赘述。
需要说明的是，该步骤可以省略。
步骤303a、第一通信装置确定第一取值候选集。
具体的，对第一通信装置确定第一取值候选集的具体描述可以参照上述步骤301中终端设备确定第一取值候选集的相关描述，不予赘述。
步骤304a、第一通信装置接收第一取值。
具体的，对第一通信装置接收第一取值的具体描述可以参照上述步骤302中终端设备接收第一取值的相关描述，不予赘述。
步骤305a、第一通信装置根据第一取值进行通信。
具体的，对第一通信装置根据第一取值进行通信的具体描述可以参照上述步骤303中终端设备根据第一取值进行通信的相关描述，不予赘述。
基于上述图3a和图3b所示的方法，可替换的，如图3c所示，可以从第二通信装置的角度对本申请实施例提供的通信方法进行描述。
图3c为本申请实施例提供的一种通信方法的流程图，如图3c所示，该方法可以包括：
步骤301b、第二通信装置接收第一请求信息和/或第一特征信息。
具体的，对第二通信装置接收第一请求信息和/或第一特征信息的具体描述可以参照上述步骤301中网络设备对第一请求信息和/或第一特征信息的具体描述，不予赘述。
需要说明的是，该步骤可以省略。
步骤302b、第二通信装置确定第一取值候选集。
具体的，对第二通信装置确定第一取值候选集的具体描述可以参照上述步骤301中网络设备确定第一取值候选集的具体描述，不予赘述。
步骤303b、第二通信装置发送第一取值候选集。
具体的，对第二通信装置发送第一取值候选集的具体描述可以参照上述步骤301中网络设备发送第一取值候选集的具体描述，不予赘述。
步骤304b、第二通信装置发送第一取值。
体的，对第二通信装置发送第一取值的具体描述可以参照上述步骤302中网络设备发送第一取值的具体描述，不予赘述。
本申请实施例可以作为独立的实施例，也可以与本申请中的其他实施例相结合，具体的，本申请对此不做限定。
与上述图3a所示的方法改善网络设备为终端设备配置多个RRC参数时，需要将每个RRC参数从该RRC参数的取值全集中确定第一取值并发送给终端设备，导致RRC信令开销较大，终端设备的存储开销较大，终端设备的功耗也较大的技术问题类似，如图5a所示，本申请实施例还提供了一种通信方法，用于改善网络设备通过向终端设备发送DCI以调度RRC信令和/或数据信号时，由于DCI的格式是通信协议预先规定的固定格式，DCI的信令开销较大，导致通信系统频谱效率较低，终端设备功耗较大的技术问题。
图5a为本申请实施例提供的一种通信方法的流程图，本申请实施例可以作为独立的实施例，也可以与本申请中的其他实施例相结合，具体的，本申请对此不做限定。如图5a所示，该方法可以包括：
步骤501、网络设备向终端设备发送第一DCI。相应的，终端设备接收第一DCI。
其中，第一DCI可以包括多个DCI参数的取值；第一DCI包括的DCI参数与终端设备的终端类型对应；DCI参数的取值的候选集与终端类型对应；候选集包括终端类型对应的DCI参数的至少一个取值。
可选的，如图6所示，DCI参数可以包括下述一种或多种：DCI格式指示(上下行指示)、载波指示域(carrier indicator)、带宽部分指示(bandwidth part indicator)、频域资源分配、时域资源分配、频域跳频指示、虚拟资源块到物理资源块的映射(virtual resource block to physical resource block mapping，VRB-to-PRB mapping)、物理资源块捆绑大小指示(PRB bundling size indicator)、MCS、新数据指示(new data indicator)、冗余版本(redundancy version)、混合自动重传请求进程号(hybrid automatic repeat request process number，HARQ process number)、HARQ定时、调度物理上行共享信道的传输功率控制命令(transmit power control command for scheduled physical uplink shared channel，TPC command for scheduled PUSCH)、上行或补充上行指示(uplink/supplementary uplink indicator，UL/SUL indicator)、预编码和层数(precoding information and number of layers)、天线端口(antenna ports)、探测参考信号资源指示(sounding reference signal resource indicator，SRS resource indicator)、SRS请求(SRS request)、CSI请求(CSI request)、CBG传输信息(CBG transmission information，CBGTI)、相位追踪参考信号与解调参考信号关联(phase tracking reference signal-demodulation reference signal association，PTRS-DMRS association)、DMRS序列初始化(DMRS sequence initialization)、开环功控参数集合指示(open-loop power control parameter set indication)、优先级指示(priority indicator)、无效符号图案指示(invalid symbol pattern indicator)、最小适用的调度偏移指示(minimum applicable scheduling offset indicator)、辅小区休眠指示(secondary cell dormancy indication，SCell dormancy indication)、下行分配指示(downlink assignment index)、偏移指示(beta_offset indicator)、上行同步信道指示(uplink synchronization channel indicator，UL-SCH indicator)、PUCCH资源指示(PUCCH resource indicator)、信道接入(ChannelAccess-CPext)、速率匹配指示(rate matching indicator)、零功率信道状态信息 参考信号触发(zero power channel state information-reference siganal trigger，ZP CSI-RS trigger)、一次HARQ-ACK请求(One-shot HARQ-ACK request)、PDSCH组标识、新反馈指示(new feedback indicator)、PDSCH请求组数(number of requested PDSCH group(s))、传输配置指示(transmission configuration indication)等。
其中，可以根据终端类型确定终端类型对应的DCI参数。
可选的，终端设备和/或网络设备可以根据终端类型确定DCI参数。本申请实施例可以作为独立的实施例，也可以与本申请中的其他实施例相结合，具体的，本申请对此不做限定。
比如，终端类型与DCI参数具有对应关系，其中，对应关系可以是协议预定义的，也可以是网络设备通过高层信令或物理层信令告知终端设备的，具体的，本申请对此不做限定。
需要说明的是，对终端类型的描述可以参照上述步骤301中对终端类型的描述，不予赘述。
具体的，对于不同的终端类型，终端类型对应的通信需求可能不同，导致终端设备可以不用支持上述DCI参数中的一种或多种，因此可以根据终端类型确定适用于终端设备进行通信的DCI参数，以满足不同终端类型的终端设备对通信的不同需求，同时降低DCI信令开销。
可选的，不同的终端类型对应不同的DCI参数集合，DCI参数集合可以包括上述DCI参数中的一种或多种。例如，终端类型A可以对应DCI参数集合AD，终端类型B可以对应DCI参数集合BD，…，终端类型X可以对应DCI参数集合XD。
示例性的，当终端类型为eMBB时，eMBB对应的DCI参数可以包括时域资源分配、频域资源分配、BWP指示、MCS、新数据指示、冗余版本、HARQ进程数、HARQ定时、TPC命令、天线端口、预编码和层数、SRS请求、CSI请求。
示例性的，eMBB对应的DCI参数也可以包括DCI格式指示(上下行指示)、载波指示域、BWP指示、频域资源分配、时域资源分配、频域跳频指示、VRB-to-PRB映射、PRB捆绑大小指示、MCS、新数据指示、冗余版本、HARQ进程号、HARQ定时、TPC命令、上行或补充上行指示、预编码信息和层数、天线端口。
示例性的，当终端类型为URLLC时，URLLC对应的DCI参数可以包括时域资源指示、频域资源指示、MCS、新数据指示、HARQ进程号、TPC命令、SRS请求、CSI请求。
通过上述设计，因为URLLC主要是小包业务传输。另外URLLC主要是静止场景或固定路径的移动场景，信道状态相对稳定，因此可以不进行频域跳频和VRB-to-PRB的交织映射，即DCI参数可以不包括频域跳频指示、VRB-to-PRB映射，降低信令开销。另外，URLLC为了满足低时延高可靠性的需求，一般可以采用低速率传输，因此可以仅用单天线端口进行秩为1的传输，降低功耗，降低信令开销，提高通信效率。即DCI参数可以不包括预编码信息和层数、天线端口，降低信令开销。另外，为了机械手臂等类型的URLLC场景下，可以进行波束管理实现波束对准，位置预测，提前准备数据传输，因此DCI参数可以包括SRS请求、CSI请求。可以降低时延，满足业务的精准操作和时延的需求，提高通信效率。
示例性的，URLLC对应的DCI参数也可以包括频域资源分配、MCS、新数据指示、 冗余版本。
另外，静止场景或固定路径的移动场景，信道状态相对稳定，因此DCI参数可以不包括SRS请求、CSI请求。可以降低复杂度，降低信令开销，满足通信需求，提高通信效率。
示例性的，当终端类型为NB-IoT时，NB-IoT对应的DCI参数可以包括频域资源指示、MCS、HARQ进程号。
通过上述设计，因为NB-Iot的应用场景可以是小包数据传输，静止的场景，因此可DCI中可以不包括SRS请求、CSI请求，频域跳频指示、VRB-to-PRB映射，预编码信息和层数、天线端口，采用低速率传输，降低信令开销，降低功耗，提高通信效率。
示例性的，NB-IoT对应的DCI参数也可以包括MCS、新数据指示、冗余版本。
通过上述设计，因为NB-Iot的应用场景可以是小包数据传输，可以设计HARQ进程数为1，因此可DCI中可以不包括HARQ进程号，降低信令开销，降低功耗，提高通信效率。
示例性的，当终端类型为CPE时，CPE对应的DCI参数可以包括时域资源分配、频域资源分配、BWP指示、MCS、新数据指示、冗余版本、HARQ进程号、HARQ定时、TPC命令、天线端口、预编码和层数、SRS请求、CSI请求。
通过上述设计，因为CPE主要是大包业务传输。另外CPE主要是静止场景，信道状态相对稳定，因此可以不进行频域跳频和VRB-to-PRB的交织映射，即DCI参数可以不包括频域跳频指示、VRB-to-PRB映射，降低信令开销。
示例性的，CPE对应的DCI参数也可以包括频域资源分配、时域资源分配、频域跳频指示、VRB-to-PRB映射、PRB捆绑大小指示、MCS、新数据指示、冗余版本、预编码和层数、天线端口。
另外，静止场景，信道状态相对稳定，因此DCI参数可以不包括SRS请求、CSI请求。可以降低复杂度，降低信令开销，满足通信需求，提高通信效率。
通过上述实施例，可以设计DCI中包含的DCI参数定制化，根据终端类型或终端设备定制化DCI包含的DCI参数，实现参数需求与终端类型的通信需求匹配，最优满足各类设备的通信需求，降低信令开销，降低储存开销，提高频谱效率。
进一步的，还可以根据终端类型的上行通信需求为终端类型确定上行通信对应的DCI参数集合，和/或，根据终端类型的下行通信需求为终端类型确定下行通信对应的DCI参数集合。
可选的，终端设备和/或网络设备可以根据终端类型以及通信链路确定DCI参数。本申请实施例可以作为独立的实施例，也可以与本申请中的其他实施例相结合，具体的，本申请对此不做限定。
本申请实施例中的通信链路可以包括如下一种或多种：上行通信链路，下行通信链路，双工通信链路，回传通信链路，旁链路，接入链路，中继通信链路等。本申请实施例中的描述以上行和下行进行举例说明。
可选的，不同的通信链路可以对应不同的DCI。所述通信链路DCI可以是指用于调度所述通信链路的数据传输的DCI。比如可以包括如下一种或多种，上行DCI，下行DCI，双工DCI，回传DCI，旁链路DCI，接入链路DCI，中继DCI等。
比如，终端类型，通信链路与DCI参数具有对应关系，其中，对应关系可以是协议预 定义的，也可以是网络设备通过高层信令或物理层信令告知终端设备的，具体的，本申请对此不做限定。
例如，终端类型A可以对应上行DCI参数集合AD1，对应下行DCI参数集合AD2；终端类型B可以对应上行DCI参数集合BD1，对应下行DCI参数集合BD2；…；终端类型X可以对应上行DCI参数集合XD1，对应下行DCI参数集合XD2。
示例性的，当终端类型为eMBB时，eMBB对应的上行DCI参数可以包括DCI格式指示(上下行指示)、载波指示域、BWP指示、频域资源分配、时域资源分配、频域跳频指示、VRB-to-PRB映射、PRB捆绑大小指示、MCS、新数据指示、冗余版本、HARQ进程号、HARQ定时、TPC命令、上行或补充上行指示、预编码和层数、天线端口。
示例性的，eMBB对应的下行DCI参数可以包括DCI格式指示(上下行指示)、载波指示域、BWP指示、频域资源分配、时域资源分配、频域跳频指示、VRB-to-PRB映射、PRB捆绑大小指示、MCS、新数据指示、冗余版本、HARQ进程号、HARQ定时、TPC命令、上行或补充上行指示、预编码和层数、天线端口、SRS请求、CSI请求、CBG传输信息。
示例性的，当终端类型为URLLC时，URLLC对应的上行DCI参数可以包括频域资源分配、MCS、新数据指示、冗余版本。
示例性的，URLLC对应的下行DCI参数可以包括频域资源分配、MCS、新数据指示、冗余版本、CSI请求。
示例性的，当终端类型为IoT时，IoT对应的上行DCI参数可以包括MCS、新数据指示、冗余版本。
示例性的，NB-IoT对应的下行DCI参数可以包括MCS、新数据指示、冗余版本、CSI请求。
示例性的，当终端类型为CPE时，CPE对应的上行DCI参数可以包括频域资源分配、时域资源分配、频域跳频指示、VRB-to-PRB映射、PRB捆绑大小指示、MCS、新数据指示、冗余版本、预编码和层数、天线端口。
示例性的，CPE对应的下行DCI参数可以包括频域资源分配、时域资源分配、频域跳频指示、VRB-to-PRB映射、PRB捆绑大小指示、MCS、新数据指示、冗余版本、预编码和层数、天线端口、SRS请求、CSI请求。
通过上述实施例，可以设计不同通信链路的DCI中包含的DCI参数定制化，根据终端类型或终端设备的不同的通信链路的需求定制化DCI包含的DCI参数，实现参数需求与终端类型的通信链路需求匹配，最优满足各类设备的通信链路需求，降低信令开销，降低储存开销，提高频谱效率。
具体的，可以进一步根据终端类型的通信需求为终端类型确定终端类型对应的各个DCI参数的取值的候选集。
可选的，终端设备和/或网络设备可以根据终端类型确定DCI参数的取值的候选集。本申请实施例可以作为独立的实施例，也可以与本申请中的其他实施例相结合，具体的，本申请对此不做限定。
比如，终端类型与DCI参数的取值的候选集具有对应关系，其中，对应关系可以是协议预定义的，也可以是网络设备通过高层信令或物理层信令告知终端设备的，具体的，本 申请对此不做限定。其中，根据终端类型的通信需求为终端类型确定终端类型对应的各个DCI参数的取值的候选集包括：根据终端类型确定终端类型对应的DCI参数的取值的候选集对应的比特数，以及根据终端类型确定终端类型对应的DCI参数的取值的候选集中的至少一个取值。
示例性的，以DCI参数为TPC命令为例，可以根据终端类型确定终端类型对应的TPC命令的取值的候选集对应的比特数，以及终端类型对应的TPC命令的取值的候选集。
可选的，终端设备和/或网络设备可以根据终端类型确定TPC命令的取值的候选集对应的比特数，以及终端类型对应的TPC命令的取值的候选集。本申请实施例可以作为独立的实施例，也可以与本申请中的其他实施例相结合，具体的，本申请对此不做限定。
比如，终端类型与DCI参数的取值的候选集对应的比特数，以及终端类型对应的TPC命令的取值的候选集具有对应关系，其中，对应关系可以是协议预定义的，也可以是网络设备通过高层信令或物理层信令告知终端设备的，具体的，本申请对此不做限定。
例如，终端类型A对应的TPC命令的取值的候选集对应的比特数为AT1，对应的TPC命令的取值的候选集为候选集T1；终端类型B对应的TPC命令的取值的候选集对应的比特数为AT2，对应的TPC命令的取值的候选集为候选集T2；…；终端类型X对应的TPC命令的取值的候选集对应的比特数为ATX，对应的TPC命令的取值的候选集为候选集TX。
其中，TPC命令的取值的候选集对应的比特数可以为至少1比特。当TPC命令的取值的候选集对应的比特数为1比特时，TPC命令的取值的候选集可以包括取值1和取值2；当TPC命令的取值的候选集对应的比特数为2比特时，TPC命令的取值的候选集可以包括取值1、取值2、取值3和取值4。
示例性的，当终端类型为eMBB时，可以根据eMBB的通信需求确定eMBB对应的TPC命令的取值的候选集对应的比特数。
例如，eMBB对应的TPC命令的取值的候选集对应的比特数可以为2比特，TPC命令的取值的候选集可以包括取值1、取值2、取值3和取值4。当TPC命令为00时，可以指示TPC命令的取值为取值1；当TPC命令为01时，可以指示TPC命令的取值为取值2；当TPC命令为10时，可以指示TPC命令的取值为取值3；当TPC命令为11时，可以指示TPC命令的取值为取值4。
进一步的，可以根据eMBB的通信需求确定eMBB对应的TPC命令的取值的候选集中的取值。
例如，当TPC命令用于指示δ PUSCH,b,f,c或δ SRS,b,f,c的累计值时，取值1可以为-1dB，取值2可以为0dB；取值3可以为1dB；取值4可以为3dB。
又例如，当TPC命令用于指示δ PUSCH,b,f,c或δ SRS,b,f,c的绝对值时，取值1可以为-4dB，取值2可以为-1dB；取值3可以为1dB；取值4可以为4dB。
示例性的，当终端类型为URLLC时，可以根据URLLC的通信需求确定URLLC对应的TPC命令的取值的候选集对应的比特数。
例如，URLLC对应的TPC命令的取值的候选集对应的比特数可以为1比特，TPC命令的取值的候选集可以包括取值1、取值2。当TPC命令为0时，可以指示TPC命令的取值为取值1；当TPC命令为1时，可以指示TPC命令的取值为取值2。
进一步的，可以根据URLLC的通信需求确定URLLC对应的TPC命令的取值的候选 集中的取值。
例如，当TPC命令用于指示δ PUSCH,b,f,c或δ SRS,b,f,c的累计值时，取值1可以为-1dB，取值2可以为0dB。
又例如，当TPC命令用于指示δ PUSCH,b,f,c或δ SRS,b,f,c的绝对值时，取值1可以为-1dB，取值2可以为1dB。
示例性的，当终端类型为NB-IoT时，可以根据NB-IoT的通信需求确定NB-IoT对应的TPC命令的取值的候选集对应的比特数。
例如，NB-IoT对应的TPC命令的取值的候选集对应的比特数可以为1比特，TPC命令的取值的候选集可以包括取值1、取值2。当TPC命令为0时，可以指示TPC命令的取值为取值1；当TPC命令为1时，可以指示TPC命令的取值为取值2。
进一步的，可以根据NB-IoT的通信需求确定NB-IoT对应的TPC命令的取值的候选集中的取值。
例如，当TPC命令用于指示δ PUSCH,b,f,c或δ SRS,b,f,c的累计值时，取值1可以为0dB，取值2可以为1dB。
又例如，当TPC命令用于指示δ PUSCH,b,f,c或δ SRS,b,f,c的绝对值时，取值1可以为1dB，取值2可以为4dB。
示例性的，当终端类型为CPE时，可以根据CPE的通信需求确定CPE对应的TPC命令的取值的候选集对应的比特数。
例如，CPE对应的TPC命令的取值的候选集对应的比特数可以为1比特，TPC命令的取值的候选集可以包括取值1、取值2。当TPC命令为0时，可以指示TPC命令的取值为取值1；当TPC命令为1时，可以指示TPC命令的取值为取值2。
进一步的，可以根据CPE的通信需求确定CPE对应的TPC命令的取值的候选集中的取值。
例如，当TPC命令用于指示δ PUSCH,b,f,c或δ SRS,b,f,c的累计值时，取值1可以为-1dB，取值2可以为0dB。
又例如，当TPC命令用于指示δ PUSCH,b,f,c或δ SRS,b,f,c的绝对值时，取值1可以为-1dB，取值2可以为1dB。
通过上述实施例，可以设计DCI中包含的TPC命令的取值的候选集定制化，根据终端类型或终端设备定制化DCI包含的TPC命令的取值的候选集，实现参数需求与终端类型的通信需求匹配，最优满足各类设备的通信需求，降低信令开销，降低储存开销，提高频谱效率。
示例性的，以DCI参数为MCS为例，可以根据终端类型确定终端类型对应的MCS的取值的候选集对应的比特数，以及终端类型对应的MCS的取值的候选集。例如，终端类型A对应的MCS的取值的候选集对应的比特数为AM1，对应的MCS的取值的候选集为候选集M1；终端类型B对应的MCS的取值的候选集对应的比特数为AM2，对应的MCS的取值的候选集为候选集M2；…；终端类型X对应的MCS的取值的候选集对应的比特数为AMX，对应的MCS的取值的候选集为候选集MX。
其中，MCS的取值的候选集对应的比特数可以为至少1比特。当MCS的取值的候选集对应的比特数为1比特时，MCS的取值的候选集可以包括取值1和取值2；当MCS的 取值的候选集对应的比特数为2比特时，MCS的取值的候选集可以包括取值1、取值2、取值3和取值4；当MCS的取值的候选集对应的比特数为3比特时，MCS的取值的候选集可以包括取值1、取值2、取值3、取值4、取值5、取值6、取值7、取值8。
示例性的，当终端类型为eMBB时，可以根据eMBB的通信需求确定eMBB对应的MCS的取值的候选集对应的比特数。
例如，eMBB对应的MCS的取值的候选集对应的比特数可以为5比特，MCS的取值的候选集可以包括取值0、取值1、…、取值31。当MCS为00000时，可以指示MCS的取值为取值0；当MCS为00001时，可以指示MCS的取值为取值1；…；当MCS为11111时，可以指示MCS的取值为取值31。
进一步的，可以根据eMBB的通信需求确定eMBB对应的MCS的取值的候选集中的取值。
例如，MCS的取值的候选集可以为下述表1至表3中的一种或多种。具体的，MCS取值的候选集可以包括下述表1至表3中一行或多行。
表1(PDSCH MCS索引表1)
Figure PCTCN2021125901-appb-000001
Figure PCTCN2021125901-appb-000002
表2(PDSCH MCS索引表2)
Figure PCTCN2021125901-appb-000003
Figure PCTCN2021125901-appb-000004
表3(PDSCH MCS索引表3)
Figure PCTCN2021125901-appb-000005
Figure PCTCN2021125901-appb-000006
示例性的，当终端类型为URLLC时，可以根据URLLC的通信需求确定URLLC对应的MCS的取值的候选集对应的比特数。
例如，URLLC对应的MCS的取值的候选集对应的比特数可以为3比特，MCS的取值的候选集可以包括取值0、取值1、…、取值7。当MCS为000时，可以指示MCS的取值为取值0；当MCS为001时，可以指示MCS的取值为取值1；…；当MCS为111时，可以指示MCS的取值为取值7。
进一步的，可以根据URLLC的通信需求确定URLLC对应的MCS的取值的候选集中的取值。
例如，MCS的取值的候选集可以为下述表4。
表4
MCS 调制阶数 目标码率Rx[1024] 频谱效率
0 2 78 0.1523
1 2 120 0.2344
2 2 193 0.3770
3 2 251 0.4902
4 4 340 1.3281
5 4 378 1.4766
6 6 438 2.5664
7 6 466 2.7305
示例性的，当终端类型为NB-IoT时，可以根据NB-IoT的通信需求确定NB-IoT对应的MCS的取值的候选集对应的比特数。
例如，NB-IoT对应的MCS的取值的候选集对应的比特数可以为2比特，MCS的取值的候选集可以包括取值0、取值1、取值2、取值3。当MCS为00时，可以指示MCS的取值为取值0；当MCS为01时，可以指示MCS的取值为取值1；当MCS为10时，可以指示MCS的取值为取值2；当MCS为11时，可以指示MCS的取值为取值3。
进一步的，可以根据NB-IoT的通信需求确定NB-IoT对应的MCS的取值的候选集中的取值。
例如，MCS的取值的候选集可以为下述表5。
表5
MCS 调制阶数 目标码率Rx[1024] 频谱效率
0 2 120 0.2344
1 2 193 0.3770
2 2 308 0.6016
3 2 449 0.8770
需要说明的是，MCS的取值的候选集对应的比特数为2比特或3比特时，可以对应特定的MCS的取值，适用于人工智能训练(artificial intelligence training，AI training)、工厂场景等信道和干扰比较稳定的场景。
通过上述实施例，可以设计DCI中包含的MCS的取值的候选集定制化，根据终端类 型或终端设备定制化DCI包含的MCS的取值的候选集，实现参数需求与终端类型的通信需求匹配，最优满足各类设备的通信需求，降低信令开销，降低储存开销，提高频谱效率。
可选的，对于特定的MCS的取值，网络设备向终端设备发送上行的特定的MCS的取值，终端设备向网络设备发送下行的特定的MCS的取值；或者网络设备向终端设备发送上行的特定的MCS的取值和下行的特定的MCS的取值。
需要说明的是，除上述举例说明的DCI参数外，还可以参照上述描述根据终端类型确定终端类型对应的其他DCI参数的取值的候选集，以及该DCI参数的取值的候选集对应的比特数。
基于上述终端类型与DCI参数的对应关系，以及终端类型与DCI参数的取值的候选集的对应关系，对应终端设备对应的每个DCI参数，网络设备和/或终端设备都可以采用下述方式一至方式四中的一种或多种方式，确定终端类型对应的DCI参数和DCI参数的取值的候选集。
方式一：终端类型对应的DCI参数和DCI参数的取值的候选集是通信协议预先规定的。
其中，可以采用机器学习、神经网络等训练模型为终端类型确定终端类型对应的RRC参数，以及终端类型对应的各个DCI参数和DCI参数的取值的候选集。或者，可以根据网络设备在一段时间内根据各个终端设备的通信需求为各个终端设备配置的DCI参数的取值，确定终端类型对应的DCI参数，以及终端类型对应的各个DCI参数的取值的候选集。或者，也可以根据通信经验确定终端类型对应的DCI参数，以及终端类型对应的各个DCI参数的取值的候选集。
例如，可以通过机器学习或神经网络等训练模型确定终端设备在不同DCI参数组合和/或DCI参数的取值的不同候选集下的通信质量，根据通信质量确定终端类型对应的DCI参数，以及终端类型对应的各个DCI参数的取值的候选集。
又例如，以终端类型A包括终端设备1、终端设备2和终端设备3为例，可以根据网络设备在一段时间内为终端设备1、终端设备2和终端设备3配置的DCI参数取值，确定终端类型A对应的DCI参数，以及终端类型对应的各个DCI参数的取值的候选集。
具体的，可以将各个终端类型对应的DCI参数和DCI参数的取值的候选集写入通信协议中，便于网络设备与终端设备根据通信协议确定终端设备的终端类型对应的DCI参数和DCI参数的取值的候选集，避免网络设备向终端设备发送终端类型对应的DCI参数和DCI参数的取值的候选集，节省信令开销，降低通信时延，降低终端功耗。
方式二：网络设备向终端设备发送指示信息。
其中，指示信息可以用于指示终端类型对应的DCI参数和DCI参数的取值的候选集。
其中，网络设备可以在随机接入过程中或者在终端设备初始接入网络时，根据终端设备的终端类型确定终端类型对应的DCI参数和DCI参数的取值的候选集，并将该终端类型对应的DCI参数和DCI参数的取值的候选集下发给终端设备。
或者，网络设备可以通过高层信令或物理层信令发送DCI参数和DCI参数的取值的候选集，终端设备根据网络设备的指示确定DCI参数和DCI参数的取值的候选集。
通过上述方案，网络设备可以配置DCI参数和DCI参数的取值的候选集，实现DCI参数和DCI参数的取值的候选集的配置灵活性，更好的适应的不同场景，满足不同场景的需求，降低取值指示的开销，提高通信效率。
具体的，网络设备可以采用如方式一所示的方法确定终端类型对应的DCI参数和DCI参数的取值的候选集，不予赘述。
示例性的，以DCI参数包括TPC命令为例，网络设备可以在随机接入过程中或者在终端设备初始接入网络时，根据终端设备的终端类型，确定终端类型对应的TPC命令的取值的候选集对应的比特数和该候选集中TPC命令的取值，并发送给终端设备。
示例性的，以DCI参数包括MSC为例，网络设备可以在随机接入过程中或者在终端设备初始接入网络时，根据终端设备的终端类型，确定终端类型对应的MSC的取值的候选集对应的比特数和该候选集中MSC的取值，并发送给终端设备。
方式三、终端设备向网络设备发送第二请求信息，网络设备根据该第二请求信息，向终端设备发送终端类型对应的DCI参数和DCI参数的取值的候选集。
其中，第二请求信息用于请求终端设备的终端类型对应的DCI参数和DCI参数的取值的候选集。
可选的，第二请求信息包括终端设备确定的终端类型对应的DCI参数和DCI参数的取值的候选集。
具体的，终端设备可以根据自身的通信需求，确定适合于自身进行通信的DCI参数和DCI参数的取值的候选集，并将该DCI参数和DCI参数的取值的候选集发送给网络设备。当网络设备接收到终端设备发送的DCI参数和DCI参数的取值的候选集后，判断终端设备是否可以使用该DCI参数和DCI参数的取值的候选集，如果可以，则将该DCI参数和DCI参数的取值的候选集作为终端类型对应的DCI参数和DCI参数的取值的候选集发送给终端设备，如果不可以，则网络设备可以根据终端设备的终端类型，确定终端类型对应的DCI参数和DCI参数的取值的候选集，并将该DCI参数和DCI参数的取值的候选集发送给终端设备。
其中，网络设备与终端设备均可以采用如上述方式一所述的方法确定终端类型对应的DCI参数和DCI参数的取值的候选集，不予赘述。
示例性的，以DCI参数包括TPC命令为例，终端设备可以向网络设备发送终端设备确定的TPC命令的取值的候选集对应的比特数和该候选集中TPC命令的取值，网络设备根据终端设备发送的TPC命令的取值的候选集对应的比特数和该候选集中TPC命令的取值，判断终端设备是否可以使用该TPC命令的取值的候选集对应的比特数和该候选集中TPC命令的取值，如果可以，则将该TPC命令的取值的候选集对应的比特数和该候选集中TPC命令的取值作为终端类型对应的TPC命令的取值的候选集对应的比特数和该候选集中TPC命令的取值发送给终端设备，如果不可以，则网络设备可以根据终端设备的终端类型，确定终端类型对应的TPC命令的取值的候选集对应的比特数和该候选集中TPC命令的取值，并将该TPC命令的取值的候选集对应的比特数和该候选集中TPC命令的取值发送给终端设备。
示例性的，以DCI参数包括MCS为例，终端设备可以向网络设备发送终端设备确定的MCS的取值的候选集对应的比特数和该候选集中MCS的取值，网络设备根据终端设备发送的MCS的取值的候选集对应的比特数和该候选集中MCS的取值，判断终端设备是否可以使用该MCS的取值的候选集对应的比特数和该候选集中MCS的取值，如果可以，则将该MCS的取值的候选集对应的比特数和该候选集中MCS的取值作为终端类型对应的 MCS的取值的候选集对应的比特数和该候选集中MCS的取值发送给终端设备，如果不可以，则网络设备可以根据终端设备的终端类型，确定终端类型对应的MCS的取值的候选集对应的比特数和该候选集中MCS的取值，并将该MCS的取值的候选集对应的比特数和该候选集中MCS的取值发送给终端设备。
通过上述方案，终端设备可以向网络设备发送建议的DCI参数和DCI参数的取值的候选集，实现DCI参数和DCI参数的取值的候选集的配置灵活性，更好的满足终端设备的通信需求，更好的适应的不同场景，满足不同场景的需求，降低取值指示的开销，提高通信效率。
方式四、终端设备向网络设备发送第二特征信息，网络设备根据该第二特征信息，向终端设备发送终端类型对应的DCI参数和DCI参数的取值的候选集。
其中，第二特征信息可以用于指示终端设备的终端类型。
可选的，第二特征信息可以为终端设备的终端类型，或者为用于指示终端设备的终端类型的通信需求，该通信需求可以为业务类型、移动性、传输时延需求、信道环境、可靠性需求、覆盖需求、通信场景中的一种或多种。
具体的，网络设备可以根据终端设备发送的第二特征信息，确定终端设备的终端类型，并确定终端类型对应的DCI参数和DCI参数的取值的候选集，并将DCI参数和DCI参数的取值的候选集发送给终端设备。
示例性的，以DCI参数包括TPC命令为例，终端设备可以向网络设备发送第二特征信息，网络设备根据该第二特征信息，确定终端设备的终端类型，并确定终端类型对应的TPC命令的取值的候选集对应的比特数和该候选集中TPC命令的取值，并将TPC命令的取值的候选集对应的比特数和该候选集中TPC命令的取值发送给终端设备。
示例性的，以DCI参数包括MCS为例，终端设备可以向网络设备发送第二特征信息，网络设备根据该第二特征信息，确定终端设备的终端类型，并确定终端类型对应的MCS的取值的候选集对应的比特数和该候选集中MCS的取值，并将MCS的取值的候选集对应的比特数和该候选集中MCS的取值发送给终端设备。
通过上述方案，可以根据终端设备可以向网络设备发送第二特征信息，通过第二特征信息确定DCI参数和DCI参数的取值的候选集，实现DCI参数和DCI参数的取值的候选集的配置灵活性，更好的满足终端设备的通信需求，更好的适应的不同场景，满足不同场景的需求，降低取值指示的开销，提高通信效率。
基于上述终端类型与DCI参数的对应关系，以及终端类型与DCI参数的取值的候选集的对应关系，可以为终端类型确定终端类型对应的DCI参数的取值的候选集，并根据终端类型对应的DCI参数的取值的候选集确定终端类型对应的第一DCI。本申请实施例可以作为独立的实施例，也可以与本申请中的其他实施例相结合，具体的，本申请对此不做限定。
示例性的，当终端类型为eMBB时，第一DCI可以包括MCS参数和HARQ进程号，其中，MCS参数的取值的候选集对应的比特数为5；HARQ进程号的取值的候选集对应的比特数为4。
示例性的，当终端类型为URLLC时，第一DCI可以包括MCS参数、HARQ进程号、SRS请求、CSI请求，其中，MCS参数的取值的候选集对应的比特数为2或3；HARQ进程号的取值的候选集对应的比特数为1；SRS请求的取值的候选集对应的比特数为1；CSI 请求的取值的候选集对应的比特数为1。
通过上述设计，因为URLLC主要是小包业务传输。另外URLLC主要是静止场景或固定路径的移动场景，信道状态相对稳定，因此MCS参数的取值的候选集可以包括4个或者8个取值，即对应的比特数为2或3，相比于比特数为5，可以降低信令开销。另外，URLLC为了满足低时延高可靠性的需求，一般可以采用低速率传输，因此可以仅用单天线端口进行秩为1的传输，降低功耗，降低信令开销，提高通信效率。即DCI参数可以不包括预编码信息和层数、天线端口，降低信令开销。另外，为了机械手臂等类型的URLLC场景下，可以进行波束管理实现波束对准，位置预测，提前准备数据传输，因此DCI参数可以包括SRS请求、CSI请求。另外，测量的情况比较简单，可以配置1比特的SRS请求、1比特的CSI请求即可，相比于eMBB较多的SRS或CSI配置，可以降低信令开销，提高通信效率。另外，URLLC的数据包主要是小包，因此可以采用较少的HARQ进程数，在进行HARQ进程号指示时，可以降低信令开销，提高通信效率。
示例性的，当终端类型为IoT时，第一DCI可以包括MCS参数和HARQ进程号，其中，MCS参数的取值的候选集对应的比特数为2或3；HARQ进程号参数的取值的候选集对应的比特数为1或2。
通过上述设计，因为Iot的应用场景可以是小包数据传输，静止的场景，因此MCS参数的取值的候选集可以包括4个或者8个取值，即对应的比特数为2或3，相比于比特数为5，可以降低信令开销。另外，URLLC的数据包主要是小包，因此可以采用较少的HARQ进程数，在进行HARQ进程号指示时，可以降低信令开销，提高通信效率。
示例性的，当终端类型为CPE时，第一DCI可以包括MCS参数和HARQ进程号，其中，MCS参数的取值的候选集对应的比特数为2、3、4或5；HARQ进程号参数的取值的候选集对应的比特数为4。
通过上述设计，因为CPE主要是大包业务传输。另外CPE主要是静止场景，信道状态相对稳定，因此MCS参数的取值的候选集可以包括4个或者8个取值，即对应的比特数为2或3，相比于比特数为5，可以降低信令开销。另外，可以灵活配置MCS参数的取值候选集中的取值个数，适用于不同的通信场景，满足不同的通信需求的同时，降低信令开销。另外，CPE的数据包主要是大包，因此可以采用较多的HARQ进程数，提高通信效率。
通过上述方案，可以根据终端类型确定DCI参数和DCI参数的取值的候选集，实现DCI参数和DCI参数的取值的候选集的配置灵活性，更好的满足终端设备的通信需求，更好的适应的不同场景，满足不同场景的需求，降低取值指示的开销，提高通信效率。
步骤502、终端设备根据第一DCI进行通信。
具体的，终端设备可以根据终端设备的终端类型对应的DCI参数的取值的候选集、以及第一DCI，确定第一DCI中各个DCI参数的取值，并根据第一DCI中各个DCI参数的取值进行通信。
可选的，当DCI参数的取值的候选集中包括一个取值时，比如第一DCI参数的取值候选集中仅包括第一DCI参数的第一取值，网络设备可以不向终端设备发送第一DCI参数。此时，终端设备和网络设备可以确定该第一DCI参数的取值为第一取值。
可选的，当DCI参数的取值的候选集中包括多个取值时，比如第一DCI参数的取值的 候选集中包括第一取值，第二取值等，网络设备可以不向终端设备发送第一取值。此时，终端设备和网络设备可以确定该第一DCI参数的取值为默认取值。其中，默认取值包括第一DCI参数的取值候选集中终端类型对应的第一DCI参数的取值。即，当网络设备没有向终端设备指示第一DCI参数的取值时，第一DCI参数的取值为默认取值，或者，当终端设备没有收到网络设备指示的第一DCI参数的取值时，第一DCI参数的取值为默认取值。
进一步的，第一DCI参数的默认取值可以是协议预定义的，也可以是网络设备通过高层信令或物理层信令告知终端设备的。
通过上述方式，可以当第一DCI参数的取值为默认取值时，可以降低信令开销，提高通信性能。
本申请实施例中，通过根据终端类型确定终端类型对应的DCI中包括的DCI参数以及DCI参数的取值的候选集，可以使得网络设备从DCI参数的取值的候选集中为终端设备确定DCI参数，降低信令开销，降低终端设备的存储开销，满足不同终端类型的通信需求，同时降低终端设备的功耗。
示例性的，如图7所示，第一DCI可以与数据信道在同一个符号上，即单符号传输。本申请实施例可以作为独立的实施例，也可以与本申请中的其他实施例相结合，具体的，本申请对此不做限定。
可选的，控制信道的DMRS与数据信道的DMRS可以共用。
可选的，控制信道的频域位置与数据信道的频域位置具有对应关系。
比如，可以预定义数据信道的频域位置与控制信道的频域位置的关系，降低数据信道的频域位置的指示开销，提高通信效率。
比如，可以通过指示数据信道的频域位置与控制信道的频域位置的偏移确定数据信道的频域位置，降低数据信道的频域位置的指示开销，提高通信效率。
本申请实施例中，通过共用DMRS解调，可以降低导频开销，如采用配置1(configuration 1)，可以提升50％的导频开销，采用配置2(configuration2)，可以提升33％的导频开销。同时，可以采用频域位置指示或固定位置的方式确定DCI的频域位置，如可以采用频域交织/不交织的方式。且无需时域位置指示，可以快速实现小数据的调度与传输，节省通信时延。
基于上述图5a所示的方法，通过根据终端类型确定终端类型对应的DCI参数以及DCI参数的取值的候选集，并根据DCI参数的取值的候选集确定终端设备对应的第一DCI，可以降低DCI的信令开销，提高通信系统频谱效率，同时降低终端设备功耗。
基于上述图5a所示的方法，可替换的，如图5b所示，可以从第一通信装置的角度对本申请实施例提供的通信方法进行描述。
图5b为本申请实施例提供的一种通信方法的流程图，如图5b所示，该方法可以包括：
步骤501a、第一通信装置确定第一通信装置的终端类型对应的DCI参数以及DCI参数的取值的候选集。
具体的，对第一通信装置确定第一通信装置的终端类型对应的DCI参数以及DCI参数的取值的候选集的具体描述可以参照上述步骤501中终端设备确定终端设备的终端类型对应的DCI参数以及DCI参数的取值的候选集的具体描述，不予赘述。
需要说明的是，该步骤可以省略。
步骤502a、第一通信装置发送第二请求信息和/或第二特征信息。
具体的，对第一通信装置发送第二请求信息和/或第二特征信息的具体描述可以参照上述步骤501中终端设备发送第二请求信息和/或第二特征信息的具体描述，不予赘述。
需要说明的是，该步骤可以省略。
步骤503a、第一通信装置接收终端类型对应的DCI参数以及DCI参数的取值的候选集。
具体的，对第一通信装置接收终端类型对应的DCI参数以及DCI参数的取值的候选集的具体描述可以参照上述步骤501中终端设备接收终端类型对应的DCI参数以及DCI参数的取值的候选集的相关描述，不予赘述。
步骤504a、第一通信装置接收第一DCI。
具体的，对第一通信装置接收第一DCI的具体描述可以参照上述步骤501中终端设备接收第一DCI的相关描述，不予赘述。
步骤505a、第一通信装置根据第一DCI进行通信。
具体的，对第一通信装置根据第一DCI进行通信的具体描述可以参照上述步骤502中终端设备根据第一DCI进行通信的相关描述，不予赘述。
基于上述图5a和图5b所示的方法，可替换的，如图5c所示，可以从第二通信装置的角度对本申请实施例提供的通信方法进行描述。
图5c为本申请实施例提供的一种通信方法的流程图，如图5c所示，该方法可以包括：
步骤501b、第二通信装置接收第二请求信息和/或第二特征信息。
具体的，对第二通信装置接收第二请求信息和/或第二特征信息的具体描述可以参照上述步骤501中网络设备对第二请求信息和/或第二特征信息的具体描述，不予赘述。
需要说明的是，该步骤可以省略。
步骤502b、第二通信装置确定终端类型对应的DCI参数以及DCI参数的取值的候选集。
具体的，对第二通信装置确定终端类型对应的DCI参数以及DCI参数的取值的候选集的具体描述可以参照上述步骤501中网络设备确定终端类型对应的DCI参数以及DCI参数的取值的候选集的具体描述，不予赘述。
步骤503b、第二通信装置发送终端类型对应的DCI参数以及DCI参数的取值的候选集。
具体的，对第二通信装置发送终端类型对应的DCI参数以及DCI参数的取值的候选集的具体描述可以参照上述步骤501中网络设备发送终端类型对应的DCI参数以及DCI参数的取值的候选集的具体描述，不予赘述。
步骤504b、第二通信装置发送第一DCI。
体的，对第二通信装置发送第一DCI的具体描述可以参照上述步骤501中网络设备发送第一DCI的具体描述，不予赘述。
本申请实施例可以作为独立的实施例，也可以与本申请中的其他实施例相结合，具体的，本申请对此不做限定。
基于上述图5a所示的通信方法，本申请实施例还可以基于上述终端类型对应的DCI参数以及DCI参数的取值的候选集，确定终端类型对应的DCI格式。本申请实施例可以作 为独立的实施例，也可以与本申请中的其他实施例相结合，具体的，本申请对此不做限定。
例如，对于终端类型1，可以根据终端类型1对应的DCI参数以及DCI参数的取值的候选集，确定终端类型1对应的DCI格式F1；对于终端类型2，可以根据终端类型2对应的DCI参数以及DCI参数的取值的候选集，确定终端类型1对应的DCI格式F2；…；对于终端类型X，可以根据终端类型1对应的DCI参数以及DCI参数的取值的候选集，确定终端类型1对应的DCI格式FX。
进一步的，对应于上行通信和下行通信，可以为终端类型确定对应的上行DCI格式和下行DCI格式。例如，对于终端类型1，可以根据终端类型1上行通信时对应的DCI参数以及DCI参数的取值的候选集，确定终端类型1对应的上行DCI格式UF1，根据终端类型1下行通信时对应的DCI参数以及DCI参数的取值的候选集，确定终端类型1对应的上行DCI格式DF1；对于终端类型2，可以根据终端类型2上行通信时对应的DCI参数以及DCI参数的取值的候选集，确定终端类型1对应的上行DCI格式UF2，根据终端类型2下行通信时对应的DCI参数以及DCI参数的取值的候选集，确定终端类型2对应的上行DCI格式DF2；…；对于终端类型X，可以根据终端类型X上行通信时对应的DCI参数以及DCI参数的取值的候选集，确定终端类型X对应的上行DCI格式UF1，根据终端类型X下行通信时对应的DCI参数以及DCI参数的取值的候选集，确定终端类型X对应的上行DCI格式DFX。
其中，终端类型1、终端类型2、…、终端类型X可以是上述终端类型中的至少一种，比如eMBB，URLLC，IoT，CPE，V2X，AR/VR等。
可选的，本申请实施例还可以基于终端类型确定DCI格式，并基于DCI格式确定DCI对应的DCI参数以及DCI参数的取值的候选集。本申请实施例可以作为独立的实施例，也可以与本申请中的其他实施例相结合，具体的，本申请对此不做限定。
可选的，终端类型和/或网络设备可以根据终端类型确定DCI格式，并根据DCI格式确定DCI对应的DCI参数以及DCI参数的取值的候选集。
可选的，终端类型与DCI格式具有对应关系。其中，对应关系可以是协议预定义的，也可以是网络设备通过高层信令或物理层信令告知终端设备的，具体的，本申请对此不做限定。
可选的，DCI格式和DCI参数以及DCI参数的取值的候选集具有对应关系。其中，对应关系可以是协议预定义的，也可以是网络设备通过高层信令或物理层信令告知终端设备的，具体的，本申请对此不做限定。
例如，对于终端类型1，可以根据终端类型1确定终端类型1对应的DCI格式F1，根据DCI格式F1确定的DCI对应的DCI参数以及DCI参数的取值的候选集；对于终端类型2，可以根据终端类型2确定终端类型1对应的DCI格式F2，根据DCI格式F2确定DCI对应的DCI参数以及DCI参数的取值的候选集；…；对于终端类型X，可以根据终端类型X确定终端类型X对应的DCI格式FX，根据DCI格式FX确定DCI对应的DCI参数以及DCI参数的取值的候选集。
进一步的，对应于上行通信和下行通信，可以为终端类型确定对应的上行DCI格式和下行DCI格式。
可选的，本申请实施例还可以基于终端类型和通信链路确定DCI格式，并基于DCI 格式确定DCI对应的DCI参数以及DCI参数的取值的候选集。本申请实施例可以作为独立的实施例，也可以与本申请中的其他实施例相结合，具体的，本申请对此不做限定。
可选的，终端类型和/或网络设备可以根据终端类型和通信链路确定DCI格式，并根据DCI格式确定DCI对应的DCI参数以及DCI参数的取值的候选集。
可选的，终端类型和通信链路与DCI格式具有对应关系。其中，对应关系可以是协议预定义的，也可以是网络设备通过高层信令或物理层信令告知终端设备的，具体的，本申请对此不做限定。
可选的，DCI格式和DCI参数以及DCI参数的取值的候选集具有对应关系。其中，对应关系可以是协议预定义的，也可以是网络设备通过高层信令或物理层信令告知终端设备的，具体的，本申请对此不做限定。
例如，对于终端类型1，可以根据终端类型1确定终端类型1对应的上行DCI格式UF1，根据上行DCI格式UF1确定上行通信时DCI对应的DCI参数以及DCI参数的取值的候选集，根据终端类型1确定终端类型1对应下行DCI格式DF1，根据下行DCI格式DF1确定下行通信时DCI对应的DCI参数以及DCI参数的取值的候选集；对于终端类型2，可以根据终端类型2确定终端类型2对应的上行DCI格式UF2，根据上行DCI格式UF2确定上行通信时DCI对应的DCI参数以及DCI参数的取值的候选集，根据终端类型2确定终端类型2对应的下行DCI格式DF2，根据下行DCI格式DF2确定下行通信时DCI对应的DCI参数以及DCI参数的取值的候选集；…；对于终端类型X，可以根据终端类型X确定终端类型X对应的上行DCI格式UF1，根据上行DCI格式UF1确定上行通信时对应的DCI参数以及DCI参数的取值的候选集，根据终端类型X确定终端类型X对应的下行DCI格式DFX，根据下行DCI格式DFX确定下行通信时对应的DCI参数以及DCI参数的取值的候选集。
其中，终端类型1、终端类型2、…、终端类型X可以是上述终端类型中的至少一种，比如eMBB，URLLC，IoT，CPE，V2X，AR/VR等。
示例性的，当终端类型为eMBB时，eMBB对应的DCI格式可以为格式一，其中格式一对应的DCI参数以及DCI参数的取值的候选集如下：MCS参数的取值的候选集对应的比特数为5；HARQ进程号参数的取值的候选集对应的比特数为4。
示例性的，当终端类型为URLLC时，URLLC对应的DCI格式可以为格式二，其中格式二对应的DCI参数以及DCI参数的取值的候选集如下：MCS参数的取值的候选集对应的比特数为2或3；HARQ进程号参数的取值的候选集对应的比特数为1；SRS请求参数的取值的候选集对应的比特数为1、CSI请求参数的取值的候选集对应的比特数为1。
示例性的，当终端类型为IoT时，IoT对应的DCI格式可以为格式三，其中格式三对应的DCI参数以及DCI参数的取值的候选集如下：MCS参数的取值的候选集对应的比特数为2或3；HARQ进程号参数的取值的候选集对应的比特数为1或2。
示例性的，当终端类型为CPE时，IoT对应的DCI格式可以为格式四，其中格式四对应的DCI参数以及DCI参数的取值的候选集如下：MCS参数的取值的候选集对应的比特数为2、3、4或5；HARQ进程号参数的取值的候选集对应的比特数为4。
进一步的，网络设备可以将终端设备的终端类型对应的DCI格式发送给终端设备，以使终端设备根据终端设备的终端类型对应的DCI格式，接收网络设备发送的DCI。
更进一步的，终端设备还可以根据DCI格式与DCI参数的取值的候选集的对应关系、以及网络设备发送的DCI格式，确定网络设备发送的DCI格式中DCI参数的取值的候选集，进而根据该DCI参数的取值的候选集以及网络设备发送的DCI，对DCI进行解析。
示例性的，以终端设备1对应的DCI格式为第一DCI格式为例，网络设备可以将第一DCI格式发送给终端设备，以使终端设备根据该第一DCI格式接收网络设备发送的第一DCI，并根据DCI格式与DCI参数的取值的候选集的对应关系、第一DCI格式，确定第一DCI中DCI参数的取值的候选集，并根据第一DCI中DCI参数的取值的候选集、第一DCI，确定第一DCI中各个DCI参数的取值，基于第一DCI中各个DCI参数的取值进行通信。
基于上述所示方法，网络设备通过根据终端类型确定终端类型对应的DCI格式，便于终端设备根据网络设备发送的DCI格式接收DCI，提高终端设备接收DCI的成功率，同时便于终端设备根据DCI格式与DCI参数的取值的候选集的对应关系，对接收到的DCI进行解析，满足不同终端类型的通信需求，降低信令开销，提高通信质量。
上述主要从设备之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，各个设备为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对各个设备进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在采用对应各个功能划分各个功能模块的情况下，图8示出了一种终端设备，终端设备80可以包括处理模块801和收发模块802。示例性地，终端设备80可以是终端设备，也可以是应用于终端设备中的芯片或者其他具有上述终端设备功能的组合器件、部件等。当终端设备80是终端设备时，处理模块801可以是处理器(或者，处理电路)，例如基带处理器，基带处理器中可以包括一个或多个CPU，收发模块802可以是收发器，收发器可以包括天线和射频电路等。当终端设备80是具有上述终端设备功能的部件时，处理模块801可以是处理器(或者，处理电路)，例如基带处理器，收发模块802可以是射频单元。当终端设备80是芯片系统时，处理模块801可以是芯片系统的处理器(或者，处理电路)，可以包括一个或多个中央处理单元，收发模块802可以是芯片(例如基带芯片)的输入输出接口。应理解，本申请实施例中的处理模块801可以由处理器或处理器相关电路组件(或者，称为处理电路)实现，收发模块802可以由收发器或收发器相关电路组件实现。
例如，处理模块801可以用于执行图3a-图7所示的实施例中由终端设备所执行的除了收发操作之外的全部操作，和/或用于支持本文所描述的技术的其它过程，收发模块802可以用于执行图3a-图7所示的实施例中由终端设备所执行的全部收发操作，和/或用于支 持本文所描述的技术的其它过程。
其中，处理模块801，用于确定第一取值候选集；第一取值候选集与终端设备的终端类型对应；第一取值候选集包括终端类型对应的无线资源控制RRC参数的取值候选集；收发模块802，用于接收来自网络设备的第一取值；其中，第一取值包括第一取值候选集中的一组RRC参数取值；处理模块801，用于根据第一取值进行通信。
一种可能的设计中，终端类型对应的RRC参数的类型包括下述中的一种或多种：数据传输的配置参数、信道状态信息CSI测量反馈的配置参数、初始接入的配置参数、移动性的配置参数、功率控制的配置参数、波束管理的配置参数。
一种可能的设计中，RRC参数的取值候选集用于指示RRC参数的配置方式；其中，配置方式包括配置参数域，配置参数域包括配置方式的配置参数；或者，配置方式包括配置参数。
一种可能的设计中，收发模块802，还用于接收来自网络设备的第一取值候选集。
一种可能的设计中，收发模块802接收来自网络设备的第一取值候选集之前，还用于向网络设备发送第一请求信息；其中，第一请求信息用于请求终端类型对应的RRC参数的取值候选集。
一种可能的设计中，收发模块802，还用于向网络设备发送第一特征信息；其中，第一特征信息用于指示终端类型。
一种可能的设计中，当终端类型为增强移动宽带设备eMBB时，eMBB对应的RRC参数的类型包括数据传输的配置参数、信道状态信息CSI测量反馈的配置参数、初始接入的配置参数、移动性的配置参数、功率控制的配置参数和波束管理的配置参数；和/或；当终端类型为超可靠低时延通信设备URLLC时，URLLC对应的RRC参数的类型包括数据传输的配置参数、信道状态信息CSI测量反馈的配置参数和波束管理的配置参数；和/或；当终端类型为物联网设备IoT时，IoT对应的RRC参数的类型包括数据传输的配置参数、初始接入的配置参数、移动性的配置参数；和/或；当终端类型为客户前置设备CPE时，CPE对应的RRC参数的类型包括数据传输的配置参数和信道状态信息CSI测量反馈的配置参数。
一种可能的设计中，当终端类型为增强移动宽带设备eMBB时，数据传输的配置参数中的子载波间隔配置参数取值的候选集为15kHz、30kHz、120kHz、240kHz；CSI测量反馈的配置参数中的CSI上报时域配置参数取值的候选集为周期性上报、非周期性上报、半持续性上报；波束管理的配置参数中的波束失败恢复定时参数取值的候选集为10ms，20ms，40ms，60ms，80ms，100ms，150ms，200ms；和/或；当终端类型为超可靠低时延通信设备URLLC时，数据传输的配置参数中的子载波间隔配置参数取值的候选集为30kHz、60kHz、120kHz；CSI测量反馈的配置参数中的CSI上报时域配置参数取值的候选集为非周期性上报；波束管理的配置参数中的波束失败恢复定时参数取值的候选集为10ms，20ms，40ms；和/或；当终端类型为物联网设备IoT时，数据传输的配置参数中的子载波间隔配置参数取值的候选集为15kHz、120kHz；和/或；当终端类型为客户前置设备CPE时，数据传输的配置参数中的子载波间隔配置参数的取值为15kHz、120kHz；CSI测量反馈的配置参数中的CSI上报时域配置参数取值的候选集为周期性上报。
一种可能的设计中，终端类型根据下述一种或多种因素确定：业务类型、移动性、传 输时延需求、信道环境、可靠性需求、覆盖需求、通信场景。
作为又一种可实现方式，图8所示终端设备80中的处理模块801和收发模块802还可以用于：
收发模块802，用于接收来自网络设备的第一下行控制信息DCI；第一DCI包括多个DCI参数的取值；第一DCI包括的DCI参数与终端设备的终端类型对应；DCI参数的取值的候选集与终端类型对应；候选集包括终端类型对应的DCI参数的至少一个取值；处理模块801，用于根据第一DCI进行通信。
一种可能的设计中，处理模块801，还用于确定第一DCI格式；其中，第一DCI格式与终端类型对应；收发模块802，还用于根据第一DCI格式，接收来自网络设备的第一DCI。
一种可能的设计中，处理模块801，还用于根据DCI格式与DCI参数的取值的候选集的对应关系、第一DCI格式，确定DCI参数的取值的候选集。
一种可能的设计中，收发模块802，还用于终端设备接收来自网络设备的指示信息；其中，指示信息用于指示终端类型对应的DCI参数和DCI参数的取值的候选集。
一种可能的设计中，收发模块802接收来自网络设备的指示信息之前，还用于终端设备向网络设备发送第二请求信息；其中，第二请求信息用于请求终端类型对应的DCI参数和DCI参数的取值的候选集。
一种可能的设计中，收发模块802，还用于向网络设备发送第二特征信息；其中，第二特征信息用于指示终端类型。
一种可能的设计中，当终端类型为增强移动宽带设备eMBB时，eMBB对应的DCI参数包括时域资源分配、频域资源分配、带宽部分BWP指示、调制和编码方式MCS、新数据指示、冗余版本、混合自动重传请求HARQ进程号、HARQ定时、传输功率控制TPC命令、天线端口、预编码和层数、探测参考信号SRS请求、信道状态信息CSI请求；和/或；当终端类型为超可靠低时延通信设备URLLC时，URLLC对应的DCI参数包括时域资源指示、频域资源指示、调制和编码方式MCS、新数据指示、混合自动重传请求HARQ进程号、传输功率控制命令、探测参考信号SRS请求、信道状态信息CSI请求；和/或；当终端类型为物联网设备IoT时，IoT对应的DCI参数包括频域资源指示、调制和编码方式MCS、混合自动重传请求HARQ进程号；和/或；当终端类型为客户前置设备CPE时，CPE对应的DCI参数包括时域资源分配、频域资源分配、带宽部分BWP指示、调制和编码方式MCS、新数据指示、冗余版本、混合自动重传请求HARQ进程号、HARQ定时、传输功率控制TPC命令、天线端口、预编码和层数、探测参考信号SRS请求、信道状态信息CSI请求。
一种可能的设计中，当终端类型为增强移动宽带设备eMBB时，MCS参数的取值的候选集对应的比特数为5；HARQ进程号参数的取值的候选集对应的比特数为4；和/或；当终端类型为超可靠低时延通信设备URLLC时，MCS参数的取值的候选集对应的比特数为2或3；HARQ进程号参数的取值的候选集对应的比特数为1；探测参考信号SRS请求参数的取值的候选集对应的比特数为1；信道状态信息CSI请求参数的取值的候选集对应的比特数为1；和/或；当终端类型为物联网设备IoT时，MCS参数的取值的候选集对应的比特数为2或3；HARQ进程号参数的取值的候选集对应的比特数为1或2；和/或；当终端类型为客户前置设备CPE时，MCS参数的取值的候选集对应的比特数为2、3、4或5； HARQ进程号参数的取值的候选集对应的比特数为4。
一种可能的设计中，当终端类型为增强移动宽带设备eMBB时，eMBB对应的DCI格式为格式一，其中格式一对应的DCI参数以及DCI参数的取值的候选集如下：调制和编码方式MCS参数的取值的候选集对应的比特数为5；混合自动重传请求HARQ进程号参数的取值的候选集对应的比特数为4；和/或；当终端类型为超可靠低时延通信设备URLLC时，URLLC对应的DCI格式为格式二，其中格式二对应的DCI参数以及DCI参数的取值的候选集如下：调制和编码方式MCS参数的取值的候选集对应的比特数为2或3；混合自动重传请求HARQ进程号参数的取值的候选集对应的比特数为1；探测参考信号SRS请求参数的取值的候选集对应的比特数为1、信道状态信息CSI请求参数的取值的候选集对应的比特数为1；和/或；当终端类型为物联网设备IoT时，IoT对应的DCI格式为格式三，其中格式三对应的DCI参数以及DCI参数的取值的候选集如下：调制和编码方式MCS参数的取值的候选集对应的比特数为2或3；混合自动重传请求HARQ进程号参数的取值的候选集对应的比特数为1或2；和/或；当终端类型为客户前置设备CPE时，CPE对应的DCI格式为格式四，其中格式四对应的DCI参数以及DCI参数的取值的候选集如下：调制和编码方式MCS参数的取值的候选集对应的比特数为2、3、4或5；混合自动重传请求HARQ进程号参数的取值的候选集对应的比特数为4。
一种可能的设计中，终端类型根据下述一种或多种因素确定：业务类型、移动性、传输时延需求、信道环境、可靠性需求、覆盖需求、通信场景。
作为又一种可实现方式，图8中的处理模块801可以由处理器代替，该处理器可以集成处理模块801的功能；收发模块802可以由收发器代替，该收发器可以集成收发模块802的功能。进一步的，图8所示终端设备80还可以包括存储器。当处理模块801由处理器代替，收发模块802由收发器代替时，本申请实施例所涉及的终端设备80可以为图2所示通信装置。
在采用对应各个功能划分各个功能模块的情况下，图9示出了一种网络设备，网络设备90可以包括处理模块901和收发模块902。示例性地，网络设备90可以是网络设备，也可以是应用于网络设备中的芯片或者其他具有上述网络设备功能的组合器件、部件等。当网络设备90是网络设备时，收发模块902可以是收发器，收发器可以包括天线和射频电路等，处理模块901可以是处理器(或者，处理电路)，例如基带处理器，基带处理器中可以包括一个或多个CPU。当网络设备90是具有上述网络设备功能的部件时，收发模块902可以是射频单元，处理模块901可以是处理器(或者，处理电路)，例如基带处理器。当网络设备90是芯片系统时，收发模块902可以是芯片(例如基带芯片)的输入输出接口，处理模块901可以是芯片系统的处理器(或者，处理电路)，可以包括一个或多个中央处理单元。应理解，本申请实施例中的收发模块902可以由收发器或收发器相关电路组件实现，处理模块901可以由处理器或处理器相关电路组件(或者，称为处理电路)实现。
例如，处理模块901可以用于执行图3a-图7所示的实施例中由网络设备所执行的除了收发操作之外的全部操作，和/或用于支持本文所描述的技术的其它过程。收发模块902可以用于执行图3a-图7所示的实施例中由网络设备所执行的全部收发操作，和/或用于支持本文所描述的技术的其它过程。
处理模块901，用于确定第一取值；收发模块902902，用于向终端设备发送第一取值；其中，第一取值包括第一取值候选集中的一组RRC参数取值；第一取值候选集与终端设备的终端类型对应；第一取值候选集包括终端类型对应的无线资源控制RRC参数的取值候选集。
一种可能的设计中，终端类型对应的RRC参数的类型包括下述中的一种或多种：数据传输的配置参数、信道状态信息CSI测量反馈的配置参数、初始接入的配置参数、移动性的配置参数、功率控制的配置参数、波束管理的配置参数。
一种可能的设计中，RRC参数的取值候选集用于指示RRC参数的配置方式；其中，配置方式包括配置参数域，配置参数域包括配置方式的配置参数；或者，配置方式包括配置参数。
一种可能的设计中，收发模块902，还用于向终端设备发送第一取值候选集。
一种可能的设计中，收发模块902向终端设备发送第一取值候选集之前，还用于接收来自终端设备的第一请求信息；其中，第一请求信息用于请求终端类型对应的RRC参数的取值候选集。
一种可能的设计中，收发模块902，还用于接收来自终端设备的第一特征信息；其中，第一特征信息用于指示终端类型。
一种可能的设计中，当终端类型为增强移动宽带设备eMBB时，eMBB对应的RRC参数的类型包括数据传输的配置参数、信道状态信息CSI测量反馈的配置参数、初始接入的配置参数、移动性的配置参数、功率控制的配置参数和波束管理的配置参数；和/或；当终端类型为超可靠低时延通信设备URLLC时，URLLC对应的RRC参数的类型包括数据传输的配置参数、信道状态信息CSI测量反馈的配置参数和波束管理的配置参数；和/或；当终端类型为物联网设备IoT时，IoT对应的RRC参数的类型包括数据传输的配置参数、初始接入的配置参数、移动性的配置参数；和/或；当终端类型为客户前置设备CPE时，CPE对应的RRC参数的类型包括数据传输的配置参数和信道状态信息CSI测量反馈的配置参数。
一种可能的设计中，当终端类型为增强移动宽带设备eMBB时，数据传输的配置参数中的子载波间隔配置参数取值的候选集为15kHz、30kHz、120kHz、240kHz；CSI测量反馈的配置参数中的CSI上报时域配置参数取值的候选集为周期性上报、非周期性上报、半持续性上报；波束管理的配置参数中的波束失败恢复定时参数取值的候选集为10ms，20ms，40ms，60ms，80ms，100ms，150ms，200ms；和/或；当终端类型为超可靠低时延通信设备URLLC时，数据传输的配置参数中的子载波间隔配置参数取值的候选集为30kHz、60kHz、120kHz；CSI测量反馈的配置参数中的CSI上报时域配置参数取值的候选集为非周期性上报；波束管理的配置参数中的波束失败恢复定时参数取值的候选集为10ms，20ms，40ms；和/或；当终端类型为物联网设备IoT时，数据传输的配置参数中的子载波间隔配置参数取值的候选集为15kHz、120kHz；和/或；当终端类型为客户前置设备CPE时，数据传输的配置参数中的子载波间隔配置参数的取值为15kHz、120kHz；CSI测量反馈的配置参数中的CSI上报时域配置参数取值的候选集为周期性上报。
一种可能的设计中，终端类型根据下述一种或多种因素确定：业务类型、移动性、传输时延需求、信道环境、可靠性需求、覆盖需求、通信场景。
作为又一种可实现方式，图9所示终端设备90中的处理模块901和收发模块902还可以用于：
处理模块901，用于确定第一DCI；第一DCI包括多个DCI参数的取值；第一DCI包括的DCI参数与终端设备的终端类型对应；DCI参数的取值的候选集与终端类型对应；候选集包括终端类型对应的DCI参数的至少一个取值；收发模块902，用于向终端设备发送第一DCI。
一种可能的设计中，收发模块902，还用于网络设备向终端设备发送第一DCI格式；以使终端设备根据第一DCI格式，接收来自网络设备的第一DCI；其中，第一DCI格式与终端类型对应。
一种可能的设计中，收发模块902向终端设备发送第一DCI之前，还用于向终端设备发送指示信息；其中，指示信息用于指示终端类型对应的DCI参数和DCI参数的取值的候选集。
一种可能的设计中，收发模块902向终端设备发送指示信息之前，还用于接收来自终端设备的第二请求信息；其中，第二请求信息用于请求终端类型对应的DCI参数和DCI参数的取值的候选集。
一种可能的设计中，收发模块902，还用于接收来自终端设备的第二特征信息；其中，第二特征信息用于指示终端类型。
一种可能的设计中，当终端类型为增强移动宽带设备eMBB时，eMBB对应的DCI参数包括时域资源分配、频域资源分配、带宽部分BWP指示、调制和编码方式MCS、新数据指示、冗余版本、混合自动重传请求HARQ进程号、HARQ定时、传输功率控制TPC命令、天线端口、预编码和层数、探测参考信号SRS请求、信道状态信息CSI请求；和/或；当终端类型为超可靠低时延通信设备URLLC时，URLLC对应的DCI参数包括时域资源指示、频域资源指示、调制和编码方式MCS、新数据指示、混合自动重传请求HARQ进程号、传输功率控制命令、探测参考信号SRS请求、信道状态信息CSI请求；和/或；当终端类型为物联网设备IoT时，IoT对应的DCI参数包括频域资源指示、调制和编码方式MCS、混合自动重传请求HARQ进程号；和/或；当终端类型为客户前置设备CPE时，CPE对应的DCI参数包括时域资源分配、频域资源分配、带宽部分BWP指示、调制和编码方式MCS、新数据指示、冗余版本、混合自动重传请求HARQ进程号、HARQ定时、传输功率控制TPC命令、天线端口、预编码和层数、探测参考信号SRS请求、信道状态信息CSI请求。
一种可能的设计中，当终端类型为增强移动宽带设备eMBB时，MCS参数的取值的候选集对应的比特数为5；HARQ进程号参数的取值的候选集对应的比特数为4；和/或；当终端类型为超可靠低时延通信设备URLLC时，MCS参数的取值的候选集对应的比特数为2或3；HARQ进程号参数的取值的候选集对应的比特数为1；探测参考信号SRS请求参数的取值的候选集对应的比特数为1；信道状态信息CSI请求参数的取值的候选集对应的比特数为1；和/或；当终端类型为物联网设备IoT时，MCS参数的取值的候选集对应的比特数为2或3；HARQ进程号参数的取值的候选集对应的比特数为1或2；和/或；当终端类型为客户前置设备CPE时，MCS参数的取值的候选集对应的比特数为2、3、4或5；HARQ进程号参数的取值的候选集对应的比特数为4。
一种可能的设计中，当终端类型为增强移动宽带设备eMBB时，eMBB对应的DCI格式为格式一，其中格式一对应的DCI参数以及DCI参数的取值的候选集如下：调制和编码方式MCS参数的取值的候选集对应的比特数为5；混合自动重传请求HARQ进程号参数的取值的候选集对应的比特数为4；和/或；当终端类型为超可靠低时延通信设备URLLC时，URLLC对应的DCI格式为格式二，其中格式二对应的DCI参数以及DCI参数的取值的候选集如下：调制和编码方式MCS参数的取值的候选集对应的比特数为2或3；混合自动重传请求HARQ进程号参数的取值的候选集对应的比特数为1；探测参考信号SRS请求参数的取值的候选集对应的比特数为1、信道状态信息CSI请求参数的取值的候选集对应的比特数为1；和/或；当终端类型为物联网设备IoT时，IoT对应的DCI格式为格式三，其中格式三对应的DCI参数以及DCI参数的取值的候选集如下：调制和编码方式MCS参数的取值的候选集对应的比特数为2或3；混合自动重传请求HARQ进程号参数的取值的候选集对应的比特数为1或2；和/或；当终端类型为客户前置设备CPE时，CPE对应的DCI格式为格式四，其中格式四对应的DCI参数以及DCI参数的取值的候选集如下：调制和编码方式MCS参数的取值的候选集对应的比特数为2、3、4或5；混合自动重传请求HARQ进程号参数的取值的候选集对应的比特数为4。
一种可能的设计中，终端类型根据下述一种或多种因素确定：业务类型、移动性、传输时延需求、信道环境、可靠性需求、覆盖需求、通信场景。
作为又一种可实现方式，图9中的收发模块902可以由收发器代替，该收发器可以集成收发模块902的功能；处理模块901可以由处理器代替，该处理器可以集成处理模块901的功能。进一步的，图9所示网络设备90还可以包括存储器。当收发模块902由收发器代替，处理模块901由处理器代替时，本申请实施例所涉及的网络设备90可以为图2所示通信装置。
本申请实施例还提供了一种计算机可读存储介质。上述方法实施例中的全部或者部分流程可以由计算机程序来指令相关的硬件完成，该程序可存储于上述计算机可读存储介质中，该程序在执行时，可包括如上述各方法实施例的流程。计算机可读存储介质可以是前述任一实施例的终端(包括数据发送端和/或数据接收端)的内部存储单元，例如终端的硬盘或内存。上述计算机可读存储介质也可以是上述终端的外部存储设备，例如上述终端上配备的插接式硬盘，智能存储卡(smart media card,SMC)，安全数字(secure digital,SD)卡，闪存卡(flash card)等。进一步地，上述计算机可读存储介质还可以既包括上述终端的内部存储单元也包括外部存储设备。上述计算机可读存储介质用于存储上述计算机程序以及上述终端所需的其他程序和数据。上述计算机可读存储介质还可以用于暂时地存储已经输出或者将要输出的数据。
需要说明的是，本申请的说明书、权利要求书及附图中的术语“第一”和“第二”等是用于区别不同对象，而不是用于描述特定顺序。此外，术语“包括”和“具有”以及它们任何变形，意图在于覆盖不排他的包含。例如包含了一系列步骤或单元的过程、方法、系统、产品或设备没有限定于已列出的步骤或单元，而是可选地还包括没有列出的步骤或单元，或可选地还包括对于这些过程、方法、产品或设备固有的其它步骤或单元。
应当理解，在本申请中，“至少一个(项)”是指一个或者多个，“多个”是指两个或两个以上，“至少两个(项)”是指两个或三个及三个以上，“和/或”，用于描述关联 对象的关联关系，表示可以存在三种关系，例如，“A和/或B”可以表示：只存在A，只存在B以及同时存在A和B三种情况，其中A，B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。“以下至少一项(个)”或其类似表达，是指这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a，b或c中的至少一项(个)，可以表示：a，b，c，“a和b”，“a和c”，“b和c”，或“a和b和c”，其中a，b，c可以是单个，也可以是多个。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将装置的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述模块或单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个装置，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是一个物理单元或多个物理单元，即可以位于一个地方，或者也可以分布到多个不同地方。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个可读取存储介质中。基于这样的理解，本申请实施例的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该软件产品存储在一个存储介质中，包括若干指令用以使得一个设备(可以是单片机，芯片等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。

Claims (89)

  1. 一种通信方法，其特征在于，包括：
    终端设备确定第一取值候选集；其中，所述第一取值候选集与所述终端设备的终端类型对应；所述第一取值候选集包括所述终端类型对应的无线资源控制RRC参数的取值候选集；
    所述终端设备接收来自网络设备的第一取值；其中，所述第一取值包括所述第一取值候选集中的一组所述RRC参数取值；
    所述终端设备根据所述第一取值进行通信。
  2. 根据权利要求1所述的方法，其特征在于，
    所述终端类型对应的所述RRC参数的类型包括下述中的一种或多种：数据传输的配置参数、信道状态信息CSI测量反馈的配置参数、初始接入的配置参数、移动性的配置参数、功率控制的配置参数、波束管理的配置参数。
  3. 根据权利要求1或2所述的方法，其特征在于，
    所述RRC参数的取值候选集用于指示所述RRC参数的配置方式；其中，
    所述配置方式包括配置参数域，所述配置参数域包括所述配置方式的配置参数；或者，
    所述配置方式包括配置参数。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，所述终端设备确定所述第一取值候选集，包括：
    所述终端设备接收来自所述网络设备的所述第一取值候选集。
  5. 根据权利要求4所述的方法，其特征在于，所述终端设备接收来自所述网络设备的所述第一取值候选集之前，所述方法还包括：
    所述终端设备向所述网络设备发送第一请求信息；其中，所述第一请求信息用于请求所述终端类型对应的所述RRC参数的取值候选集。
  6. 根据权利要求1-5任一项所述的方法，其特征在于，
    所述终端设备向所述网络设备发送第一特征信息；其中，所述第一特征信息用于指示所述终端类型。
  7. 根据权利要求2-6任一项所述的方法，其特征在于，
    当所述终端类型为增强移动宽带设备eMBB时，所述eMBB对应的RRC参数的类型包括所述数据传输的配置参数、所述信道状态信息CSI测量反馈的配置参数、所述初始接入的配置参数、所述移动性的配置参数、所述功率控制的配置参数和所述波束管理的配置参数；和/或
    当所述终端类型为超可靠低时延通信设备URLLC时，所述URLLC对应的RRC参数的类型包括所述数据传输的配置参数、所述信道状态信息CSI测量反馈的配置参数和所述波束管理的配置参数；和/或
    当所述终端类型为物联网设备IoT时，所述IoT对应的RRC参数的类型包括所述数据传输的配置参数、所述初始接入的配置参数、所述移动性的配置参数；和/或
    当所述终端类型为客户前置设备CPE时，所述CPE对应的RRC参数的类型包括所述数据传输的配置参数和所述信道状态信息CSI测量反馈的配置参数。
  8. 根据权利要求7所述的方法，其特征在于，
    当所述终端类型为增强移动宽带设备eMBB时，所述数据传输的配置参数中的子载波间隔配置参数取值的候选集为15kHz、30kHz、120kHz、240kHz；所述CSI测量反馈的配置参数中的CSI上报时域配置参数取值的候选集为周期性上报、非周期性上报、半持续性上报；所述波束管理的配置参数中的波束失败恢复定时参数取值的候选集为10ms，20ms，40ms，60ms，80ms，100ms，150ms，200ms；和/或
    当所述终端类型为超可靠低时延通信设备URLLC时，所述数据传输的配置参数中的子载波间隔配置参数取值的候选集为30kHz、60kHz、120kHz；所述CSI测量反馈的配置参数中的CSI上报时域配置参数取值的候选集为非周期性上报；所述波束管理的配置参数中的波束失败恢复定时参数取值的候选集为10ms，20ms，40ms；和/或
    当所述终端类型为物联网设备IoT时，所述数据传输的配置参数中的子载波间隔配置参数取值的候选集为15kHz、120kHz；和/或
    当所述终端类型为客户前置设备CPE时，所述数据传输的配置参数中的子载波间隔配置参数的取值为15kHz、120kHz；所述CSI测量反馈的配置参数中的CSI上报时域配置参数取值的候选集为周期性上报。
  9. 根据权利要求1-8任一项所述的方法，其特征在于，
    所述终端类型根据下述一种或多种因素确定：业务类型、移动性、传输时延需求、信道环境、可靠性需求、覆盖需求、通信场景。
  10. 一种通信方法，其特征在于，包括：
    终端设备接收来自网络设备的第一下行控制信息DCI；其中，所述第一DCI包括多个DCI参数的取值；所述第一DCI包括的DCI参数与所述终端设备的终端类型对应；所述DCI参数的取值的候选集与所述终端类型对应；所述候选集包括所述终端类型对应的所述DCI参数的至少一个取值；
    所述终端设备根据所述第一DCI进行通信。
  11. 根据权利要求10所述的方法，其特征在于，所述终端设备接收来自所述网络设备的所述第一DCI，包括：
    所述终端设备确定第一DCI格式；其中，所述第一DCI格式与所述终端类型对应；
    所述终端设备根据所述第一DCI格式，接收来自所述网络设备的所述第一DCI。
  12. 根据权利要求11所述的方法，其特征在于，
    所述终端设备根据DCI格式与DCI参数的取值的候选集的对应关系、所述第一DCI格式，确定所述DCI参数的取值的候选集。
  13. 根据权利要求10-12任一项所述的方法，其特征在于，所述终端设备接收来自所述网络设备的第一DCI之前，所述方法还包括：
    所述终端设备接收来自所述网络设备的指示信息；其中，所述指示信息用于指示所述终端类型对应的DCI参数和所述DCI参数的取值的候选集。
  14. 根据权利要求13所述的方法，其特征在于，所述终端设备接收来自所述网络设备的所述指示信息之前，所述方法还包括：
    所述终端设备向所述网络设备发送第二请求信息；其中，所述第二请求信息用于请求所述终端类型对应的DCI参数和所述DCI参数的取值的候选集。
  15. 根据权利要求10-14任一项所述的方法，其特征在于，所述方法还包括：
    所述终端设备向所述网络设备发送第二特征信息；其中，所述第二特征信息用于指示所述终端类型。
  16. 根据权利要求10-15任一项所述的方法，其特征在于，
    当所述终端类型为增强移动宽带设备eMBB时，所述eMBB对应的DCI参数包括时域资源分配、频域资源分配、带宽部分BWP指示、调制和编码方式MCS、新数据指示、冗余版本、混合自动重传请求HARQ进程号、HARQ定时、传输功率控制TPC命令、天线端口、预编码和层数、探测参考信号SRS请求、信道状态信息CSI请求；和/或
    当所述终端类型为超可靠低时延通信设备URLLC时，所述URLLC对应的DCI参数包括时域资源指示、频域资源指示、调制和编码方式MCS、新数据指示、混合自动重传请求HARQ进程号、传输功率控制命令、探测参考信号SRS请求、信道状态信息CSI请求；和/或
    当所述终端类型为物联网设备IoT时，所述IoT对应的DCI参数包括频域资源指示、调制和编码方式MCS、混合自动重传请求HARQ进程号；和/或
    当所述终端类型为客户前置设备CPE时，所述CPE对应的DCI参数包括时域资源分配、频域资源分配、带宽部分BWP指示、调制和编码方式MCS、新数据指示、冗余版本、混合自动重传请求HARQ进程号、HARQ定时、传输功率控制TPC命令、天线端口、预编码和层数、探测参考信号SRS请求、信道状态信息CSI请求。
  17. 根据权利要求16所述的方法，其特征在于，
    当所述终端类型为增强移动宽带设备eMBB时，MCS参数的取值的候选集对应的比特数为5；HARQ进程号参数的取值的候选集对应的比特数为4；和/或
    当所述终端类型为超可靠低时延通信设备URLLC时，MCS参数的取值的候选集对应的比特数为2或3；HARQ进程号参数的取值的候选集对应的比特数为1；探测参考信号SRS请求参数的取值的候选集对应的比特数为1；信道状态信息CSI请求参数的取值的候选集对应的比特数为1；和/或
    当所述终端类型为物联网设备IoT时，MCS参数的取值的候选集对应的比特数为2或3；HARQ进程号参数的取值的候选集对应的比特数为1或2；和/或
    当所述终端类型为客户前置设备CPE时，MCS参数的取值的候选集对应的比特数为2、3、4或5；HARQ进程号参数的取值的候选集对应的比特数为4。
  18. 根据权利要求11所述的方法，其特征在于，
    当所述终端类型为增强移动宽带设备eMBB时，所述eMBB对应的DCI格式为格式一，其中格式一对应的DCI参数以及所述DCI参数的取值的候选集如下：调制和编码方式MCS参数的取值的候选集对应的比特数为5；混合自动重传请求HARQ进程号参数的取值的候选集对应的比特数为4；和/或
    当所述终端类型为超可靠低时延通信设备URLLC时，所述URLLC对应的DCI格式为格式二，其中格式二对应的DCI参数以及所述DCI参数的取值的候选集如下：调制和编码方式MCS参数的取值的候选集对应的比特数为2或3；混合自动重传请求HARQ进程号参数的取值的候选集对应的比特数为1；探测参考信号SRS请求参数的取值的候选集对应的比特数为1、信道状态信息CSI请求参数的取值的候选集对应的比特数为1；和/或
    当所述终端类型为物联网设备IoT时，所述IoT对应的DCI格式为格式三，其中格式三对应的DCI参数以及所述DCI参数的取值的候选集如下：调制和编码方式MCS参数的取值的候选集对应的比特数为2或3；混合自动重传请求HARQ进程号参数的取值的候选集对应的比特数为1或2；和/或
    当所述终端类型为客户前置设备CPE时，所述CPE对应的DCI格式为格式四，其中格式四对应的DCI参数以及所述DCI参数的取值的候选集如下：调制和编码方式MCS参数的取值的候选集对应的比特数为2、3、4或5；混合自动重传请求HARQ进程号参数的取值的候选集对应的比特数为4。
  19. 根据权利要求10-18任一项所述的方法，其特征在于，
    所述终端类型根据下述一种或多种因素确定：业务类型、移动性、传输时延需求、信道环境、可靠性需求、覆盖需求、通信场景。
  20. 一种通信方法，其特征在于，包括：
    网络设备确定第一取值；其中，所述第一取值包括第一取值候选集中的一组无线资源控制RRC参数取值；所述第一取值候选集与终端设备的终端类型对应；所述第一取值候选集包括所述终端类型对应的RRC参数的取值候选集；
    所述网络设备向所述终端设备发送所述第一取值。
  21. 根据权利要求20所述的方法，其特征在于，
    所述终端类型对应的所述RRC参数的类型包括下述中的一种或多种：数据传输的配置参数、信道状态信息CSI测量反馈的配置参数、初始接入的配置参数、移动性的配置参数、功率控制的配置参数、波束管理的配置参数。
  22. 根据权利要求20或21所述的方法，其特征在于，
    所述RRC参数的取值候选集用于指示所述RRC参数的配置方式；其中，
    所述配置方式包括配置参数域，所述配置参数域包括所述配置方式的配置参数；或者，
    所述配置方式包括配置参数。
  23. 根据权利要求20-22任一项所述的方法，其特征在于，
    所述网络设备向所述终端设备发送所述第一取值候选集。
  24. 根据权利要求23所述的方法，其特征在于，所述网络设备向所述终端设备发送所述第一取值候选集之前，所述方法还包括：
    所述网络设备接收来自所述终端设备的第一请求信息；其中，所述第一请求信息用于请求所述终端类型对应的所述RRC参数的取值候选集。
  25. 根据权利要求20-24任一项所述的方法，其特征在于，
    所述网络设备接收来自所述终端设备的第一特征信息；其中，所述第一特征信息用于指示所述终端类型。
  26. 根据权利要求21-25任一项所述的方法，其特征在于，
    当所述终端类型为增强移动宽带设备eMBB时，所述eMBB对应的RRC参数的类型包括所述数据传输的配置参数、所述信道状态信息CSI测量反馈的配置参数、所述初始接入的配置参数、所述移动性的配置参数、所述功率控制的配置参数和所述波束管理的配置参数；和/或
    当所述终端类型为超可靠低时延通信设备URLLC时，所述URLLC对应的RRC参数 的类型包括所述数据传输的配置参数、所述信道状态信息CSI测量反馈的配置参数和所述波束管理的配置参数；和/或
    当所述终端类型为物联网设备IoT时，所述IoT对应的RRC参数的类型包括所述数据传输的配置参数、所述初始接入的配置参数、所述移动性的配置参数；和/或
    当所述终端类型为客户前置设备CPE时，所述CPE对应的RRC参数的类型包括所述数据传输的配置参数和所述信道状态信息CSI测量反馈的配置参数。
  27. 根据权利要求26所述的方法，其特征在于，
    当所述终端类型为增强移动宽带设备eMBB时，所述数据传输的配置参数中的子载波间隔配置参数取值的候选集为15kHz、30kHz、120kHz、240kHz；所述CSI测量反馈的配置参数中的CSI上报时域配置参数取值的候选集为周期性上报、非周期性上报、半持续性上报；所述波束管理的配置参数中的波束失败恢复定时参数取值的候选集为10ms，20ms，40ms，60ms，80ms，100ms，150ms，200ms；和/或
    当所述终端类型为超可靠低时延通信设备URLLC时，所述数据传输的配置参数中的子载波间隔配置参数取值的候选集为30kHz、60kHz、120kHz；所述CSI测量反馈的配置参数中的CSI上报时域配置参数取值的候选集为非周期性上报；所述波束管理的配置参数中的波束失败恢复定时参数取值的候选集为10ms，20ms，40ms；和/或
    当所述终端类型为物联网设备IoT时，所述数据传输的配置参数中的子载波间隔配置参数取值的候选集为15kHz、120kHz；和/或
    当所述终端类型为客户前置设备CPE时，所述数据传输的配置参数中的子载波间隔配置参数的取值为15kHz、120kHz；所述CSI测量反馈的配置参数中的CSI上报时域配置参数取值的候选集为周期性上报。
  28. 根据权利要求20-27任一项所述的方法，其特征在于，
    所述终端类型根据下述一种或多种因素确定：业务类型、移动性、传输时延需求、信道环境、可靠性需求、覆盖需求、通信场景。
  29. 一种通信方法，其特征在于，包括：
    网络设备确定第一下行控制信息DCI；其中，所述第一DCI包括多个DCI参数的取值；所述第一DCI包括的DCI参数与终端设备的终端类型对应；所述DCI参数的取值的候选集与所述终端类型对应；所述候选集包括所述终端类型对应的所述DCI参数的至少一个取值；
    所述网络设备向所述终端设备发送所述第一DCI。
  30. 根据权利要求29所述的方法，其特征在于，所述网络设备向所述终端设备发送所述第一DCI，包括：
    所述网络设备向所述终端设备发送第一DCI格式；以使所述终端设备根据所述第一DCI格式，接收来自所述网络设备的所述第一DCI；其中，所述第一DCI格式与所述终端类型对应。
  31. 根据权利要求29或30所述的方法，其特征在于，所述网络设备向所述终端设备发送所述第一DCI之前，所述方法还包括：
    所述网络设备向所述终端设备发送指示信息；其中，所述指示信息用于指示所述终端类型对应的DCI参数和所述DCI参数的取值的候选集。
  32. 根据权利要求31所述的方法，其特征在于，所述网络设备向所述终端设备发送所述指示信息之前，所述方法还包括：
    所述网络设备接收来自所述终端设备的第二请求信息；其中，所述第二请求信息用于请求所述终端类型对应的DCI参数和所述DCI参数的取值的候选集。
  33. 根据权利要求29-32任一项所述的方法，其特征在于，所述方法还包括：
    所述网络设备接收来自所述终端设备的第二特征信息；其中，所述第二特征信息用于指示所述终端类型。
  34. 根据权利要求29-33任一项所述的方法，其特征在于，
    当所述终端类型为增强移动宽带设备eMBB时，所述eMBB对应的DCI参数包括时域资源分配、频域资源分配、带宽部分BWP指示、调制和编码方式MCS、新数据指示、冗余版本、混合自动重传请求HARQ进程号、HARQ定时、传输功率控制TPC命令、天线端口、预编码和层数、探测参考信号SRS请求、信道状态信息CSI请求；和/或
    当所述终端类型为超可靠低时延通信设备URLLC时，所述URLLC对应的DCI参数包括时域资源指示、频域资源指示、调制和编码方式MCS、新数据指示、混合自动重传请求HARQ进程号、传输功率控制命令、探测参考信号SRS请求、信道状态信息CSI请求；和/或
    当所述终端类型为物联网设备IoT时，所述IoT对应的DCI参数包括频域资源指示、调制和编码方式MCS、混合自动重传请求HARQ进程号；和/或
    当所述终端类型为客户前置设备CPE时，所述CPE对应的DCI参数包括时域资源分配、频域资源分配、带宽部分BWP指示、调制和编码方式MCS、新数据指示、冗余版本、混合自动重传请求HARQ进程号、HARQ定时、传输功率控制TPC命令、天线端口、预编码和层数、探测参考信号SRS请求、信道状态信息CSI请求。
  35. 根据权利要求34所述的方法，其特征在于，
    当所述终端类型为增强移动宽带设备eMBB时，MCS参数的取值的候选集对应的比特数为5；HARQ进程号参数的取值的候选集对应的比特数为4；和/或
    当所述终端类型为超可靠低时延通信设备URLLC时，MCS参数的取值的候选集对应的比特数为2或3；HARQ进程号参数的取值的候选集对应的比特数为1；探测参考信号SRS请求参数的取值的候选集对应的比特数为1；信道状态信息CSI请求参数的取值的候选集对应的比特数为1；和/或
    当所述终端类型为物联网设备IoT时，MCS参数的取值的候选集对应的比特数为2或3；HARQ进程号参数的取值的候选集对应的比特数为1或2；和/或
    当所述终端类型为客户前置设备CPE时，MCS参数的取值的候选集对应的比特数为2、3、4或5；HARQ进程号参数的取值的候选集对应的比特数为4。
  36. 根据权利要求30所述的方法，其特征在于，
    当所述终端类型为增强移动宽带设备eMBB时，所述eMBB对应的DCI格式为格式一，其中格式一对应的DCI参数以及所述DCI参数的取值的候选集如下：调制和编码方式MCS参数的取值的候选集对应的比特数为5；混合自动重传请求HARQ进程号参数的取值的候选集对应的比特数为4；和/或
    当所述终端类型为超可靠低时延通信设备URLLC时，所述URLLC对应的DCI格式 为格式二，其中格式二对应的DCI参数以及所述DCI参数的取值的候选集如下：调制和编码方式MCS参数的取值的候选集对应的比特数为2或3；混合自动重传请求HARQ进程号参数的取值的候选集对应的比特数为1；探测参考信号SRS请求参数的取值的候选集对应的比特数为1、信道状态信息CSI请求参数的取值的候选集对应的比特数为1；和/或
    当所述终端类型为物联网设备IoT时，所述IoT对应的DCI格式为格式三，其中格式三对应的DCI参数以及所述DCI参数的取值的候选集如下：调制和编码方式MCS参数的取值的候选集对应的比特数为2或3；混合自动重传请求HARQ进程号参数的取值的候选集对应的比特数为1或2；和/或
    当所述终端类型为客户前置设备CPE时，所述CPE对应的DCI格式为格式四，其中格式四对应的DCI参数以及所述DCI参数的取值的候选集如下：调制和编码方式MCS参数的取值的候选集对应的比特数为2、3、4或5；混合自动重传请求HARQ进程号参数的取值的候选集对应的比特数为4。
  37. 根据权利要求29-36任一项所述的方法，其特征在于，
    所述终端类型根据下述一种或多种因素确定：业务类型、移动性、传输时延需求、信道环境、可靠性需求、覆盖需求、通信场景。
  38. 一种终端设备，其特征在于，包括：
    处理模块，用于确定第一取值候选集；其中，所述第一取值候选集与所述终端设备的终端类型对应；所述第一取值候选集包括所述终端类型对应的无线资源控制RRC参数的取值候选集；
    收发模块，用于接收来自网络设备的第一取值；其中，所述第一取值包括所述第一取值候选集中的一组所述RRC参数取值；
    所述终端设备根据所述第一取值进行通信。
  39. 根据权利要求38所述的终端设备，其特征在于，
    所述终端类型对应的所述RRC参数的类型包括下述中的一种或多种：数据传输的配置参数、信道状态信息CSI测量反馈的配置参数、初始接入的配置参数、移动性的配置参数、功率控制的配置参数、波束管理的配置参数。
  40. 根据权利要求38或39所述的终端设备，其特征在于，
    所述RRC参数的取值候选集用于指示所述RRC参数的配置方式；其中，
    所述配置方式包括配置参数域，所述配置参数域包括所述配置方式的配置参数；或者，
    所述配置方式包括配置参数。
  41. 根据权利要求38-40任一项所述的终端设备，其特征在于，
    所述收发模块，还用于接收来自所述网络设备的所述第一取值候选集。
  42. 根据权利要求41所述的终端设备，其特征在于，
    所述收发模块接收来自所述网络设备的所述第一取值候选集之前，还用于向所述网络设备发送第一请求信息；其中，所述第一请求信息用于请求所述终端类型对应的所述RRC参数的取值候选集。
  43. 根据权利要求38-42任一项所述的终端设备，其特征在于，
    所述收发模块，还用于向所述网络设备发送第一特征信息；其中，所述第一特征信息用于指示所述终端类型。
  44. 根据权利要求39-43任一项所述的终端设备，其特征在于，
    当所述终端类型为增强移动宽带设备eMBB时，所述eMBB对应的RRC参数的类型包括所述数据传输的配置参数、所述信道状态信息CSI测量反馈的配置参数、所述初始接入的配置参数、所述移动性的配置参数、所述功率控制的配置参数和所述波束管理的配置参数；和/或
    当所述终端类型为超可靠低时延通信设备URLLC时，所述URLLC对应的RRC参数的类型包括所述数据传输的配置参数、所述信道状态信息CSI测量反馈的配置参数和所述波束管理的配置参数；和/或
    当所述终端类型为物联网设备IoT时，所述IoT对应的RRC参数的类型包括所述数据传输的配置参数、所述初始接入的配置参数、所述移动性的配置参数；和/或
    当所述终端类型为客户前置设备CPE时，所述CPE对应的RRC参数的类型包括所述数据传输的配置参数和所述信道状态信息CSI测量反馈的配置参数。
  45. 根据权利要求44所述的终端设备，其特征在于，
    当所述终端类型为增强移动宽带设备eMBB时，所述数据传输的配置参数中的子载波间隔配置参数取值的候选集为15kHz、30kHz、120kHz、240kHz；所述CSI测量反馈的配置参数中的CSI上报时域配置参数取值的候选集为周期性上报、非周期性上报、半持续性上报；所述波束管理的配置参数中的波束失败恢复定时参数取值的候选集为10ms，20ms，40ms，60ms，80ms，100ms，150ms，200ms；和/或
    当所述终端类型为超可靠低时延通信设备URLLC时，所述数据传输的配置参数中的子载波间隔配置参数取值的候选集为30kHz、60kHz、120kHz；所述CSI测量反馈的配置参数中的CSI上报时域配置参数取值的候选集为非周期性上报；所述波束管理的配置参数中的波束失败恢复定时参数取值的候选集为10ms，20ms，40ms；和/或
    当所述终端类型为物联网设备IoT时，所述数据传输的配置参数中的子载波间隔配置参数取值的候选集为15kHz、120kHz；和/或
    当所述终端类型为客户前置设备CPE时，所述数据传输的配置参数中的子载波间隔配置参数的取值为15kHz、120kHz；所述CSI测量反馈的配置参数中的CSI上报时域配置参数取值的候选集为周期性上报。
  46. 根据权利要求38-45任一项所述的终端设备，其特征在于，
    所述终端类型根据下述一种或多种因素确定：业务类型、移动性、传输时延需求、信道环境、可靠性需求、覆盖需求、通信场景。
  47. 一种终端设备，其特征在于，包括：
    收发模块，用于接收来自网络设备的第一下行控制信息DCI；其中，所述第一DCI包括多个DCI参数的取值；所述第一DCI包括的DCI参数与所述终端设备的终端类型对应；所述DCI参数的取值的候选集与所述终端类型对应；所述候选集包括所述终端类型对应的所述DCI参数的至少一个取值；
    处理模块，用于根据所述第一DCI进行通信。
  48. 根据权利要求47所述的终端设备，其特征在于，
    所述处理模块，还用于确定第一DCI格式；其中，所述第一DCI格式与所述终端类型对应；
    所述收发模块，还用于根据所述第一DCI格式，接收来自所述网络设备的所述第一DCI。
  49. 根据权利要求48所述的终端设备，其特征在于，
    所述处理模块，还用于根据DCI格式与DCI参数的取值的候选集的对应关系、所述第一DCI格式，确定所述DCI参数的取值的候选集。
  50. 根据权利要求47-49任一项所述的终端设备，其特征在于，
    所述收发模块接收来自所述网络设备的第一DCI之前，还用于接收来自所述网络设备的指示信息；其中，所述指示信息用于指示所述终端类型对应的DCI参数和所述DCI参数的取值的候选集。
  51. 根据权利要求50所述的终端设备，其特征在于，
    所述收发模块接收来自所述网络设备的所述指示信息之前，还用于向所述网络设备发送第二请求信息；其中，所述第二请求信息用于请求所述终端类型对应的DCI参数和所述DCI参数的取值的候选集。
  52. 根据权利要求47-51任一项所述的终端设备，其特征在于，
    所述收发模块，还用于向所述网络设备发送第二特征信息；其中，所述第二特征信息用于指示所述终端类型。
  53. 根据权利要求47-52任一项所述的终端设备，其特征在于，
    当所述终端类型为增强移动宽带设备eMBB时，所述eMBB对应的DCI参数包括时域资源分配、频域资源分配、带宽部分BWP指示、调制和编码方式MCS、新数据指示、冗余版本、混合自动重传请求HARQ进程号、HARQ定时、传输功率控制TPC命令、天线端口、预编码和层数、探测参考信号SRS请求、信道状态信息CSI请求；和/或
    当所述终端类型为超可靠低时延通信设备URLLC时，所述URLLC对应的DCI参数包括时域资源指示、频域资源指示、调制和编码方式MCS、新数据指示、混合自动重传请求HARQ进程号、传输功率控制命令、探测参考信号SRS请求、信道状态信息CSI请求；和/或
    当所述终端类型为物联网设备IoT时，所述IoT对应的DCI参数包括频域资源指示、调制和编码方式MCS、混合自动重传请求HARQ进程号；和/或
    当所述终端类型为客户前置设备CPE时，所述CPE对应的DCI参数包括时域资源分配、频域资源分配、带宽部分BWP指示、调制和编码方式MCS、新数据指示、冗余版本、混合自动重传请求HARQ进程号、HARQ定时、传输功率控制TPC命令、天线端口、预编码和层数、探测参考信号SRS请求、信道状态信息CSI请求。
  54. 根据权利要求53所述的终端设备，其特征在于，
    当所述终端类型为增强移动宽带设备eMBB时，MCS参数的取值的候选集对应的比特数为5；HARQ进程号参数的取值的候选集对应的比特数为4；和/或
    当所述终端类型为超可靠低时延通信设备URLLC时，MCS参数的取值的候选集对应的比特数为2或3；HARQ进程号参数的取值的候选集对应的比特数为1；探测参考信号SRS请求参数的取值的候选集对应的比特数为1；信道状态信息CSI请求参数的取值的候选集对应的比特数为1；和/或
    当所述终端类型为物联网设备IoT时，MCS参数的取值的候选集对应的比特数为2或 3；HARQ进程号参数的取值的候选集对应的比特数为1或2；和/或
    当所述终端类型为客户前置设备CPE时，MCS参数的取值的候选集对应的比特数为2、3、4或5；HARQ进程号参数的取值的候选集对应的比特数为4。
  55. 根据权利要求48所述的终端设备，其特征在于，
    当所述终端类型为增强移动宽带设备eMBB时，所述eMBB对应的DCI格式为格式一，其中格式一对应的DCI参数以及所述DCI参数的取值的候选集如下：调制和编码方式MCS参数的取值的候选集对应的比特数为5；混合自动重传请求HARQ进程号参数的取值的候选集对应的比特数为4；和/或
    当所述终端类型为超可靠低时延通信设备URLLC时，所述URLLC对应的DCI格式为格式二，其中格式二对应的DCI参数以及所述DCI参数的取值的候选集如下：调制和编码方式MCS参数的取值的候选集对应的比特数为2或3；混合自动重传请求HARQ进程号参数的取值的候选集对应的比特数为1；探测参考信号SRS请求参数的取值的候选集对应的比特数为1、信道状态信息CSI请求参数的取值的候选集对应的比特数为1；和/或
    当所述终端类型为物联网设备IoT时，所述IoT对应的DCI格式为格式三，其中格式三对应的DCI参数以及所述DCI参数的取值的候选集如下：调制和编码方式MCS参数的取值的候选集对应的比特数为2或3；混合自动重传请求HARQ进程号参数的取值的候选集对应的比特数为1或2；和/或
    当所述终端类型为客户前置设备CPE时，所述CPE对应的DCI格式为格式四，其中格式四对应的DCI参数以及所述DCI参数的取值的候选集如下：调制和编码方式MCS参数的取值的候选集对应的比特数为2、3、4或5；混合自动重传请求HARQ进程号参数的取值的候选集对应的比特数为4。
  56. 根据权利要求47-55任一项所述的终端设备，其特征在于，
    所述终端类型根据下述一种或多种因素确定：业务类型、移动性、传输时延需求、信道环境、可靠性需求、覆盖需求、通信场景。
  57. 一种网络设备，其特征在于，包括：
    处理模块，用于确定第一取值；其中，所述第一取值包括第一取值候选集中的一组无线资源控制RRC参数取值；所述第一取值候选集与终端设备的终端类型对应；所述第一取值候选集包括所述终端类型对应的RRC参数的取值候选集；
    收发模块，用于向所述终端设备发送所述第一取值。
  58. 根据权利要求57所述的网络设备，其特征在于，
    所述终端类型对应的所述RRC参数的类型包括下述中的一种或多种：数据传输的配置参数、信道状态信息CSI测量反馈的配置参数、初始接入的配置参数、移动性的配置参数、功率控制的配置参数、波束管理的配置参数。
  59. 根据权利要求57或58所述的网络设备，其特征在于，
    所述RRC参数的取值候选集用于指示所述RRC参数的配置方式；其中，
    所述配置方式包括配置参数域，所述配置参数域包括所述配置方式的配置参数；或者，
    所述配置方式包括配置参数。
  60. 根据权利要求57-59任一项所述的网络设备，其特征在于，
    所述收发模块，还用于向所述终端设备发送所述第一取值候选集。
  61. 根据权利要求60所述的网络设备，其特征在于，
    所述收发模块向所述终端设备发送所述第一取值候选集之前，还用于接收来自所述终端设备的第一请求信息；其中，所述第一请求信息用于请求所述终端类型对应的所述RRC参数的取值候选集。
  62. 根据权利要求57-61任一项所述的网络设备，其特征在于，
    所述收发模块，还用于接收来自所述终端设备的第一特征信息；其中，所述第一特征信息用于指示所述终端类型。
  63. 根据权利要求58-62任一项所述的网络设备，其特征在于，
    当所述终端类型为增强移动宽带设备eMBB时，所述eMBB对应的RRC参数的类型包括所述数据传输的配置参数、所述信道状态信息CSI测量反馈的配置参数、所述初始接入的配置参数、所述移动性的配置参数、所述功率控制的配置参数和所述波束管理的配置参数；和/或
    当所述终端类型为超可靠低时延通信设备URLLC时，所述URLLC对应的RRC参数的类型包括所述数据传输的配置参数、所述信道状态信息CSI测量反馈的配置参数和所述波束管理的配置参数；和/或
    当所述终端类型为物联网设备IoT时，所述IoT对应的RRC参数的类型包括所述数据传输的配置参数、所述初始接入的配置参数、所述移动性的配置参数；和/或
    当所述终端类型为客户前置设备CPE时，所述CPE对应的RRC参数的类型包括所述数据传输的配置参数和所述信道状态信息CSI测量反馈的配置参数。
  64. 根据权利要求63所述的网络设备，其特征在于，
    当所述终端类型为增强移动宽带设备eMBB时，所述数据传输的配置参数中的子载波间隔配置参数取值的候选集为15kHz、30kHz、120kHz、240kHz；所述CSI测量反馈的配置参数中的CSI上报时域配置参数取值的候选集为周期性上报、非周期性上报、半持续性上报；所述波束管理的配置参数中的波束失败恢复定时参数取值的候选集为10ms，20ms，40ms，60ms，80ms，100ms，150ms，200ms；和/或
    当所述终端类型为超可靠低时延通信设备URLLC时，所述数据传输的配置参数中的子载波间隔配置参数取值的候选集为30kHz、60kHz、120kHz；所述CSI测量反馈的配置参数中的CSI上报时域配置参数取值的候选集为非周期性上报；所述波束管理的配置参数中的波束失败恢复定时参数取值的候选集为10ms，20ms，40ms；和/或
    当所述终端类型为物联网设备IoT时，所述数据传输的配置参数中的子载波间隔配置参数取值的候选集为15kHz、120kHz；和/或
    当所述终端类型为客户前置设备CPE时，所述数据传输的配置参数中的子载波间隔配置参数的取值为15kHz、120kHz；所述CSI测量反馈的配置参数中的CSI上报时域配置参数取值的候选集为周期性上报。
  65. 根据权利要求57-64任一项所述的网络设备，其特征在于，
    所述终端类型根据下述一种或多种因素确定：业务类型、移动性、传输时延需求、信道环境、可靠性需求、覆盖需求、通信场景。
  66. 一种网络设备，其特征在于，包括：
    处理模块，用于确定第一下行控制信息DCI；其中，所述第一DCI包括多个DCI参数 的取值；所述第一DCI包括的DCI参数与终端设备的终端类型对应；所述DCI参数的取值的候选集与所述终端类型对应；所述候选集包括所述终端类型对应的所述DCI参数的至少一个取值；
    收发模块，用于向所述终端设备发送所述第一DCI。
  67. 根据权利要求66所述的网络设备，其特征在于，
    所述收发模块，还用于向所述终端设备发送第一DCI格式；以使所述终端设备根据所述第一DCI格式，接收来自所述网络设备的所述第一DCI；其中，所述第一DCI格式与所述终端类型对应。
  68. 根据权利要求66或67所述的网络设备，其特征在于，
    所述收发模块向所述终端设备发送所述第一DCI之前，还用于向所述终端设备发送指示信息；其中，所述指示信息用于指示所述终端类型对应的DCI参数和所述DCI参数的取值的候选集。
  69. 根据权利要求68所述的网络设备，其特征在于，
    所述收发模块向所述终端设备发送所述指示信息之前，还用于接收来自所述终端设备的第二请求信息；其中，所述第二请求信息用于请求所述终端类型对应的DCI参数和所述DCI参数的取值的候选集。
  70. 根据权利要求66-69任一项所述的网络设备，其特征在于，
    所述收发模块，还用于接收来自所述终端设备的第二特征信息；其中，所述第二特征信息用于指示所述终端类型。
  71. 根据权利要求66-70任一项所述的网络设备，其特征在于，
    当所述终端类型为增强移动宽带设备eMBB时，所述eMBB对应的DCI参数包括时域资源分配、频域资源分配、带宽部分BWP指示、调制和编码方式MCS、新数据指示、冗余版本、混合自动重传请求HARQ进程号、HARQ定时、传输功率控制TPC命令、天线端口、预编码和层数、探测参考信号SRS请求、信道状态信息CSI请求；和/或
    当所述终端类型为超可靠低时延通信设备URLLC时，所述URLLC对应的DCI参数包括时域资源指示、频域资源指示、调制和编码方式MCS、新数据指示、混合自动重传请求HARQ进程号、传输功率控制命令、探测参考信号SRS请求、信道状态信息CSI请求；和/或
    当所述终端类型为物联网设备IoT时，所述IoT对应的DCI参数包括频域资源指示、调制和编码方式MCS、混合自动重传请求HARQ进程号；和/或
    当所述终端类型为客户前置设备CPE时，所述CPE对应的DCI参数包括时域资源分配、频域资源分配、带宽部分BWP指示、调制和编码方式MCS、新数据指示、冗余版本、混合自动重传请求HARQ进程号、HARQ定时、传输功率控制TPC命令、天线端口、预编码和层数、探测参考信号SRS请求、信道状态信息CSI请求。
  72. 根据权利要求71所述的网络设备，其特征在于，
    当所述终端类型为增强移动宽带设备eMBB时，MCS参数的取值的候选集对应的比特数为5；HARQ进程号参数的取值的候选集对应的比特数为4；和/或
    当所述终端类型为超可靠低时延通信设备URLLC时，MCS参数的取值的候选集对应的比特数为2或3；HARQ进程号参数的取值的候选集对应的比特数为1；探测参考信号 SRS请求参数的取值的候选集对应的比特数为1；信道状态信息CSI请求参数的取值的候选集对应的比特数为1；和/或
    当所述终端类型为物联网设备IoT时，MCS参数的取值的候选集对应的比特数为2或3；HARQ进程号参数的取值的候选集对应的比特数为1或2；和/或
    当所述终端类型为客户前置设备CPE时，MCS参数的取值的候选集对应的比特数为2、3、4或5；HARQ进程号参数的取值的候选集对应的比特数为4。
  73. 根据权利要求67所述的网络设备，其特征在于，
    当所述终端类型为增强移动宽带设备eMBB时，所述eMBB对应的DCI格式为格式一，其中格式一对应的DCI参数以及所述DCI参数的取值的候选集如下：调制和编码方式MCS参数的取值的候选集对应的比特数为5；混合自动重传请求HARQ进程号参数的取值的候选集对应的比特数为4；和/或
    当所述终端类型为超可靠低时延通信设备URLLC时，所述URLLC对应的DCI格式为格式二，其中格式二对应的DCI参数以及所述DCI参数的取值的候选集如下：调制和编码方式MCS参数的取值的候选集对应的比特数为2或3；混合自动重传请求HARQ进程号参数的取值的候选集对应的比特数为1；探测参考信号SRS请求参数的取值的候选集对应的比特数为1、信道状态信息CSI请求参数的取值的候选集对应的比特数为1；和/或
    当所述终端类型为物联网设备IoT时，所述IoT对应的DCI格式为格式三，其中格式三对应的DCI参数以及所述DCI参数的取值的候选集如下：调制和编码方式MCS参数的取值的候选集对应的比特数为2或3；混合自动重传请求HARQ进程号参数的取值的候选集对应的比特数为1或2；和/或
    当所述终端类型为客户前置设备CPE时，所述CPE对应的DCI格式为格式四，其中格式四对应的DCI参数以及所述DCI参数的取值的候选集如下：调制和编码方式MCS参数的取值的候选集对应的比特数为2、3、4或5；混合自动重传请求HARQ进程号参数的取值的候选集对应的比特数为4。
  74. 根据权利要求66-73任一项所述的网络设备，其特征在于，
    所述终端类型根据下述一种或多种因素确定：业务类型、移动性、传输时延需求、信道环境、可靠性需求、覆盖需求、通信场景。
  75. 一种通信装置，其特征在于，所述通信装置包括处理器和存储器；所述存储器与所述处理器耦合，所述存储器用于存储计算机程序代码或计算机指令；所述处理器用于执行所述计算机程序代码或计算机指令，以执行如权利要求1-9任一项所述的通信方法，或者执行如权利要求10-19任一项所述的通信方法，或者执行如权利要求20-28任一项所述的通信方法，或者执行如权利要求29-37任一项所述的通信方法。
  76. 一种通信装置，其特征在于，所述通信装置包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行计算机程序或指令，以实现如权利要求1-9任一项所述的通信方法，或者执行如权利要求10-19任一项所述的通信方法，或者执行如权利要求20-28任一项所述的通信方法，或者执行如权利要求29-37任一项所述的通信方法，所述通信接口用于与所述通信装置之外的其它模块进行通信。
  77. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储有计算机指令或程序，当计算机指令或程序在计算机上运行时，以执行如权利要求1-9任一项所述的 通信方法，或者执行如权利要求10-19任一项所述的通信方法，或者执行如权利要求20-28任一项所述的通信方法，或者执行如权利要求29-37任一项所述的通信方法。
  78. 一种计算机程序产品，其特征在于，所述计算机程序产品包括计算机指令；当部分或全部所述计算机指令在计算机上运行时，以执行如权利要求1-9任一项所述的通信方法，或者执行如权利要求10-19任一项所述的通信方法，或者执行如权利要求20-28任一项所述的通信方法，或者执行如权利要求29-37任一项所述的通信方法。
  79. 一种计算机程序，其特征在于，当所述计算机程序在计算机上运行时，以执行如权利要求1-9任一项所述的通信方法，或者执行如权利要求10-19任一项所述的通信方法，或者执行如权利要求20-28任一项所述的通信方法，或者执行如权利要求29-37任一项所述的通信方法。
  80. 一种通信系统，其特征在于，所述通信系统包括网络设备和终端设备；
    所述终端设备，用于确定第一取值候选集；其中，所述第一取值候选集与所述终端设备的终端类型对应；所述第一取值候选集包括所述终端类型对应的无线资源控制RRC参数的取值候选集；
    所述网络设备，用于向所述终端设备发送第一取值；其中，所述第一取值包括所述第一取值候选集中的一组所述RRC参数取值；
    所述终端设备，还用于接收所述第一取值，并根据所述第一取值进行通信。
  81. 根据权利要求80所述的通信系统，其特征在于，
    所述终端类型对应的所述RRC参数的类型包括下述中的一种或多种：数据传输的配置参数、信道状态信息CSI测量反馈的配置参数、初始接入的配置参数、移动性的配置参数、功率控制的配置参数、波束管理的配置参数。
  82. 根据权利要求80或81所述的通信系统，其特征在于，
    所述RRC参数的取值候选集用于指示所述RRC参数的配置方式；其中，所述配置方式包括配置参数域，所述配置参数域包括所述配置方式的配置参数；或者，所述配置方式包括配置参数。
  83. 根据权利要求81或82所述的通信系统，其特征在于，
    当所述终端类型为增强移动宽带设备eMBB时，所述eMBB对应的RRC参数包括所述数据传输的配置参数、所述信道状态信息CSI测量反馈的配置参数、所述初始接入的配置参数、所述移动性的配置参数、所述功率控制的配置参数和所述波束管理的配置参数；和/或
    当所述终端类型为超可靠低时延通信设备URLLC时，所述URLLC对应的RRC参数包括所述数据传输的配置参数、所述信道状态信息CSI测量反馈的配置参数和所述波束管理的配置参数；和/或
    当所述终端类型为物联网设备IoT时，所述IoT对应的RRC参数包括所述数据传输的配置参数、所述初始接入的配置参数、所述移动性的配置参数；和/或
    当所述终端类型为客户前置设备CPE时，所述CPE对应的RRC参数包括所述数据传输的配置参数和所述信道状态信息CSI测量反馈的配置参数。
  84. 根据权利要求83所述的通信系统，其特征在于，
    当所述终端类型为增强移动宽带设备eMBB时，所述数据传输的配置参数中的子载波 间隔配置参数取值的候选集为15kHz、30kHz、120kHz、240kHz；所述CSI测量反馈的配置参数中的CSI上报时域配置参数取值的候选集为周期性上报、非周期性上报、半持续性上报；所述波束管理的配置参数中的波束失败恢复定时参数取值的候选集为10ms，20ms，40ms，60ms，80ms，100ms，150ms，200ms；和/或
    当所述终端类型为超可靠低时延通信设备URLLC时，所述数据传输的配置参数中的子载波间隔配置参数取值的候选集为30kHz、60kHz、120kHz；所述CSI测量反馈的配置参数中的CSI上报时域配置参数取值的候选集为非周期性上报；所述波束管理的配置参数中的波束失败恢复定时参数取值的候选集为10ms，20ms，40ms；和/或
    当所述终端类型为物联网设备IoT时，所述数据传输的配置参数中的子载波间隔配置参数取值的候选集为15kHz、120kHz；和/或
    当所述终端类型为客户前置设备CPE时，所述数据传输的配置参数中的子载波间隔配置参数的取值为15kHz、120kHz；所述CSI测量反馈的配置参数中的CSI上报时域配置参数取值的候选集为周期性上报。
  85. 一种通信系统，其特征在于，所述通信系统包括网络设备和终端设备；
    所述网络设备，用于向所述终端设备发送第一下行控制信息DCI；其中，所述第一DCI包括多个DCI参数的取值；所述第一DCI包括的DCI参数与所述终端设备的终端类型对应；所述DCI参数的取值的候选集与所述终端类型对应；所述候选集包括所述终端类型对应的所述DCI参数的至少一个取值；
    所述终端设备，用于接收所述第一DCI，并根据所述第一DCI进行通信。
  86. 根据权利要求85所述的通信系统，其特征在于，所述终端设备接收所述第一DCI，包括：
    所述终端设备确定第一DCI格式；其中，所述第一DCI格式与所述终端类型对应；
    所述终端设备根据所述第一DCI格式，接收来自所述网络设备的所述第一DCI。
  87. 根据权利要求86所述的通信系统，其特征在于，
    所述终端设备根据DCI格式与DCI参数的取值的候选集的对应关系、所述第一DCI格式，确定所述DCI参数的取值的候选集。
  88. 根据权利要求85-87任一项所述的通信系统，其特征在于，
    当所述终端类型为增强移动宽带设备eMBB时，所述eMBB对应的DCI参数包括时域资源分配、频域资源分配、带宽部分BWP指示、调制和编码方式MCS、新数据指示、冗余版本、混合自动重传请求HARQ进程号、HARQ定时、传输功率控制TPC命令、天线端口、预编码和层数、探测参考信号SRS请求、信道状态信息CSI请求；和/或
    当所述终端类型为超可靠低时延通信设备URLLC时，所述URLLC对应的DCI参数包括时域资源指示、频域资源指示、调制和编码方式MCS、新数据指示、混合自动重传请求HARQ进程号、传输功率控制命令、探测参考信号SRS请求、信道状态信息CSI请求；和/或
    当所述终端类型为物联网设备IoT时，所述IoT对应的DCI参数包括频域资源指示、调制和编码方式MCS、混合自动重传请求HARQ进程号；和/或
    当所述终端类型为客户前置设备CPE时，所述CPE对应的DCI参数包括时域资源分配、频域资源分配、带宽部分BWP指示、调制和编码方式MCS、新数据指示、冗余版本、 混合自动重传请求HARQ进程号、HARQ定时、传输功率控制TPC命令、天线端口、预编码和层数、探测参考信号SRS请求、信道状态信息CSI请求。
  89. 根据权利要求88所述的通信系统，其特征在于，
    当所述终端类型为增强移动宽带设备eMBB时，MCS参数的取值的候选集对应的比特数为5；HARQ进程号参数的取值的候选集对应的比特数为4；和/或
    当所述终端类型为超可靠低时延通信设备URLLC时，MCS参数的取值的候选集对应的比特数为2或3；HARQ进程号参数的取值的候选集对应的比特数为1；探测参考信号SRS请求参数的取值的候选集对应的比特数为1；信道状态信息CSI请求参数的取值的候选集对应的比特数为1；和/或
    当所述终端类型为物联网设备IoT时，MCS参数的取值的候选集对应的比特数为2或3；HARQ进程号参数的取值的候选集对应的比特数为1或2；和/或
    当所述终端类型为客户前置设备CPE时，MCS参数的取值的候选集对应的比特数为2、3、4或5；HARQ进程号参数的取值的候选集对应的比特数为4。
PCT/CN2021/125901 2020-10-31 2021-10-22 通信方法、装置及系统 WO2022089335A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US18/309,104 US20230319860A1 (en) 2020-10-31 2023-04-28 Communication Method, Apparatus, and System

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202011198190.4A CN114448579A (zh) 2020-10-31 2020-10-31 通信方法、装置及系统
CN202011198190.4 2020-10-31

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/309,104 Continuation US20230319860A1 (en) 2020-10-31 2023-04-28 Communication Method, Apparatus, and System

Publications (1)

Publication Number Publication Date
WO2022089335A1 true WO2022089335A1 (zh) 2022-05-05

Family

ID=81356835

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/125901 WO2022089335A1 (zh) 2020-10-31 2021-10-22 通信方法、装置及系统

Country Status (3)

Country Link
US (1) US20230319860A1 (zh)
CN (1) CN114448579A (zh)
WO (1) WO2022089335A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180115966A1 (en) * 2016-10-21 2018-04-26 Qualcomm Incorporated Service type based control search space monitoring
CN108668369A (zh) * 2018-04-10 2018-10-16 华为技术有限公司 下行控制信息的传输方法、设备及系统
CN109863797A (zh) * 2016-11-04 2019-06-07 Oppo广东移动通信有限公司 传输数据的方法、终端设备和网络设备
CN110140322A (zh) * 2017-01-06 2019-08-16 瑞典爱立信有限公司 用于根据无线设备的位置调整参数集的方法、设备和节点

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180115966A1 (en) * 2016-10-21 2018-04-26 Qualcomm Incorporated Service type based control search space monitoring
CN109863797A (zh) * 2016-11-04 2019-06-07 Oppo广东移动通信有限公司 传输数据的方法、终端设备和网络设备
CN110140322A (zh) * 2017-01-06 2019-08-16 瑞典爱立信有限公司 用于根据无线设备的位置调整参数集的方法、设备和节点
CN108668369A (zh) * 2018-04-10 2018-10-16 华为技术有限公司 下行控制信息的传输方法、设备及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
LG ELECTRONICS: "DCI contents and formats for URLLC", 3GPP DRAFT; R1-1806619 URLLC DCI_V1, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Busan, Korea; 20180521 - 20180525, 20 May 2018 (2018-05-20), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051441821 *

Also Published As

Publication number Publication date
US20230319860A1 (en) 2023-10-05
CN114448579A (zh) 2022-05-06

Similar Documents

Publication Publication Date Title
CN109588064B (zh) 用于无线通信网络的网络架构、方法和设备
CN109588059B (zh) 用于无线通信网络的网络架构、方法和设备
CN110537384A (zh) 用于长期演进通信系统的多技术聚合架构
US11197223B2 (en) Method and apparatus for determining transmission path of packet in wireless communication
CN105992398B (zh) 一种通信系统、通信网络、通信设备和通信方法
US20230308141A1 (en) Communication Method, Device, and System
CN116235631A (zh) 新空口（nr）旁路发现消息的用户面协议设计
CN109041078A (zh) 一种业务数据传输方法及装置
CN116746219A (zh) 用于通过侧向链路中继系统信息的技术
WO2022089335A1 (zh) 通信方法、装置及系统
KR20210150231A (ko) 무선 통신 시스템에서 iab 노드의 이중 접속을 이용한 데이터 송수신 방법 및 장치
WO2022024427A1 (ja) 端末及び通信方法
WO2024067869A1 (zh) 通信方法和通信装置
WO2022089558A1 (zh) 模式切换方法及相关装置
WO2023071621A1 (zh) 通信方法、装置及系统
WO2022089561A1 (zh) 模式切换方法及相关装置
EP4344329A1 (en) Communication method and apparatus
WO2022089146A1 (zh) 通信方法、装置及系统
WO2023125417A1 (zh) 通信方法、装置、计算机可读存储介质、计算机程序产品和芯片
WO2023231965A1 (zh) 数据传输的方法、装置和系统
WO2024131885A1 (zh) 通信方法与装置、终端设备、网络设备和芯片
WO2022141332A1 (zh) 一种通信方法及装置
WO2023102813A1 (zh) 无线通信的方法、终端设备和网络设备
WO2022213328A1 (zh) 侧行链路资源配置的方法和通信装置
WO2022030040A1 (ja) 端末およびサイドリンク通信制御方法

Legal Events

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

Ref document number: 21885062

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21885062

Country of ref document: EP

Kind code of ref document: A1