WO2019161622A1 - 动态配置方法、终端设备、网络设备及计算机存储介质 - Google Patents

动态配置方法、终端设备、网络设备及计算机存储介质 Download PDF

Info

Publication number
WO2019161622A1
WO2019161622A1 PCT/CN2018/087924 CN2018087924W WO2019161622A1 WO 2019161622 A1 WO2019161622 A1 WO 2019161622A1 CN 2018087924 W CN2018087924 W CN 2018087924W WO 2019161622 A1 WO2019161622 A1 WO 2019161622A1
Authority
WO
WIPO (PCT)
Prior art keywords
mcs table
scheduling information
mcs
type
correspondence
Prior art date
Application number
PCT/CN2018/087924
Other languages
English (en)
French (fr)
Inventor
陈文洪
Original Assignee
Oppo广东移动通信有限公司
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 Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to EP18906809.1A priority Critical patent/EP3694168B1/en
Priority to KR1020207014338A priority patent/KR102565646B1/ko
Priority to AU2018410421A priority patent/AU2018410421A1/en
Priority to CN201880052397.5A priority patent/CN111034144A/zh
Priority to JP2020528041A priority patent/JP7286643B2/ja
Priority to TW108105884A priority patent/TW201939986A/zh
Publication of WO2019161622A1 publication Critical patent/WO2019161622A1/zh
Priority to US16/846,080 priority patent/US11184212B2/en
Priority to US17/453,379 priority patent/US20220060366A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H04L27/32—Carrier systems characterised by combinations of two or more of the types covered by groups H04L27/02, H04L27/10, H04L27/18 or H04L27/26
    • H04L27/34—Amplitude- and phase-modulated carrier systems, e.g. quadrature-amplitude modulated carrier systems
    • H04L27/36—Modulator circuits; Transmitter circuits
    • 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/0091—Signaling for the administration of the divided path
    • 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/0015—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the adaptation strategy
    • H04L1/0016—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the adaptation strategy involving special memory structures, e.g. look-up tables
    • 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/0002—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission rate
    • H04L1/0003—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission rate by switching between different modulation schemes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0023—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the signalling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • 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/0027—Scheduling of signalling, e.g. occurrence thereof
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0036—Systems modifying transmission characteristics according to link quality, e.g. power backoff arrangements specific to the receiver
    • H04L1/0039—Systems modifying transmission characteristics according to link quality, e.g. power backoff arrangements specific to the receiver other detection of signalling, e.g. detection of TFCI explicit signalling
    • 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/12—Wireless traffic scheduling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • 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
    • 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/0009—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the channel coding

Definitions

  • the present invention relates to the field of information processing technologies, and in particular, to a dynamic configuration method, a terminal device, a network device, and a computer storage medium.
  • the 5G NR system supports enhanced mobile broadband (eMBB, Enhance Mobile Broadband) and high reliability communication (uRLLC) services.
  • eMBB enhanced mobile broadband
  • uRLLC high reliability communication
  • MCS Modulation and Coding Scheme
  • the coding strategy) configuration is usually different, and the scope of the MCS configuration is also different.
  • an embodiment of the present invention provides a dynamic configuration method, a terminal device, a network device, and a computer storage medium.
  • the embodiment of the invention provides a dynamic configuration method, which is applied to a terminal device, and the method includes:
  • the terminal device receives configuration information of at least two modulation and coding policy MCS tables, where the configuration information is used to determine the at least two MCS tables;
  • the terminal device determines a target MCS table from the at least two MCS tables based on the correspondence between the scheduling information, the scheduling information, and the MCS table.
  • the embodiment of the invention provides a dynamic configuration method, which is applied to a network device, and the method includes:
  • the embodiment of the invention provides a terminal device, where the terminal device includes:
  • a first communication unit configured to receive configuration information of at least two modulation and coding policy MCS tables, where the configuration information is used to determine the at least two MCS tables; and receive scheduling information sent by the network side;
  • the first processing unit determines the target MCS table from the at least two MCS tables based on the correspondence between the scheduling information, the scheduling information, and the MCS table.
  • the embodiment of the invention provides a network device, where the network device includes:
  • a second communication unit configured to send configuration information of at least two modulation and coding policy MCS tables to the terminal device, where the configuration information is used to determine the at least two MCS tables; and send scheduling information to the terminal device; There is a correspondence between the scheduling information and the MCS table.
  • a terminal device provided by an embodiment of the present invention includes: a processor and a memory for storing a computer program capable of running on a processor,
  • processor is configured to perform the steps of the foregoing method when the computer program is run.
  • a network device provided by an embodiment of the present invention includes: a processor and a memory for storing a computer program capable of running on a processor,
  • processor is configured to perform the steps of the foregoing method when the computer program is run.
  • a computer storage medium is provided by the embodiment of the present invention.
  • the computer storage medium stores computer executable instructions, and the foregoing method steps are implemented when the computer executable instructions are executed.
  • At least two MCS table configuration information can be acquired in advance, and then the target MCS table is selected according to the scheduling information, and then the target MCS table is used for subsequent processing. Therefore, the dynamic configuration of the MCS table can be implemented to adapt to the dynamic scheduling of the URLLC and the eMBB service. Moreover, by adopting the implicit indication method, the physical layer signaling overhead is reduced, and the reliability of the physical layer signaling is improved.
  • FIG. 1 is a schematic flowchart 1 of a dynamic configuration method according to an embodiment of the present invention.
  • FIG. 2 is a schematic flowchart 2 of a dynamic configuration method according to an embodiment of the present invention.
  • FIG. 3 is a schematic structural diagram of a terminal device according to an embodiment of the present invention.
  • FIG. 4 is a schematic structural diagram of a network device according to an embodiment of the present invention.
  • FIG. 5 is a schematic diagram of a hardware architecture according to an embodiment of the present invention.
  • the embodiment of the invention provides a dynamic configuration method, which is applied to a terminal device, as shown in FIG. 1 , and includes:
  • Step 101 The terminal device receives configuration information of at least two modulation and coding policy MCS tables, where the configuration information is used to determine the at least two MCS tables.
  • Step 102 The terminal device receives scheduling information sent by a network side.
  • Step 103 The terminal device determines a target MCS table from the at least two MCS tables based on the correspondence between the scheduling information, scheduling information, and an MCS table.
  • the terminal receives the scheduling information, and then the terminal determines the MCS table based on the scheduling information.
  • the terminal device receives at least two MCS table configuration information from the network side.
  • the at least two modulation and coding policy MCS tables include at least: a first MCS table, and a second MCS table.
  • the first MCS table is part of the content of the second MCS table
  • the first MCS table is composed of elements corresponding to odd or even index values in the second MCS table.
  • the first MCS table is part of the content of the second MCS table, and is:
  • the first MCS table is the first half of the content of the second MCS table.
  • the first MCS table may also be the content of the second half of the second MCS table, and may also be the content of the middle portion, which is not exhaustive in this embodiment.
  • the first half of the content may be half of the entries included in the second MCS table, specifically the first half of the entries; correspondingly, the latter half of the content and the middle portion of the content are not described in detail.
  • the scheduling information includes at least one of the following: a control resource set; a search space set; a search space; a time domain resource indication type; a time domain resource length; an MCS table indication information; and a downlink control information (DCI, Downlink Control Information) format; Aggregation level; service indication; cyclic redundancy check (CRC); Radio Network Tempory Identity (RNTI).
  • DCI Downlink Control Information
  • CRC cyclic redundancy check
  • RNTI Radio Network Tempory Identity
  • the control resource set may be a CORESET (Control Resource Set); the search space set may be a search space set; the search space may be a search space; the time domain resource indication type, for example, may be Type A or Type B; the time domain resource length , can be Short TTI or long TTI; MCS table instructions.
  • CORESET Control Resource Set
  • the search space set may be a search space set
  • the search space may be a search space
  • the time domain resource indication type for example, may be Type A or Type B
  • the time domain resource length can be Short TTI or long TTI
  • MCS table instructions can be Short TTI or long TTI
  • the method further includes:
  • the correspondence between the scheduling information and the MCS table is determined based on the protocol, or the correspondence between the scheduling information and the MCS table is determined based on the high layer configuration. Specifically, the relationship between the MCS table and the above information is agreed by the agreement or the high layer configuration.
  • the method further includes configuring a corresponding MCS table for each of the scheduling information of each type of scheduling information.
  • the determining the target MCS table based on the correspondence between the scheduling information and the MCS table includes:
  • the type of the scheduling information may include: the scheduling information is a control resource set; the search space set; the search space; the time domain resource indication type; the time domain resource length; and one of the MCS table indication information.
  • the scheduling information is a control resource set; the search space set; the search space; the time domain resource indication type; the time domain resource length; and one of the MCS table indication information.
  • there are different kinds of scheduling information such as a control resource set A, a control resource set B, and the like; and a search space set A, a search space set B, and the like. It can be understood as different kinds of scheduling information in different types of scheduling information. In general, it can be understood as different kinds of scheduling information.
  • the first, based on the CORESET (Control Resource Set) configuration determines the MCS (Modulation and Coding Strategy) table:
  • the MCS table corresponding to the scheduling information of the different control resource sets may be configured by a protocol or a higher layer; wherein the scheduling information of the different control resource sets may be understood as different types of scheduling information.
  • the scheduling information of the CORESET 1 has a correspondence relationship with the MCS table 1
  • the scheduling information of the CORESET 2 has a correspondence relationship with the MCS table 2.
  • the terminal device receives the scheduling information sent by the network side, which may be:
  • the terminal device receives the scheduling information at CORESET 1. It can be understood that the type corresponding to the scheduling information is CORESET 1.
  • the determining, by the terminal device, the target MCS table from the at least two MCS tables based on the correspondence between the scheduling information, the scheduling information, and the MCS table may include:
  • the target MCS table is determined as the MCS table 1 from the MCS table 1 and the MCS table 2 based on the correspondence between the scheduling information of the CORESET1 and the scheduling information of the CORESET1 and the MCS table.
  • step 102 scheduling information received by the terminal device at the CORESET 2. It can be understood that the type corresponding to the scheduling information is CORESET 2.
  • step 103 is specifically: determining that the target MCS table is the MCS table 2 based on the correspondence between the scheduling information of the CORESET2 and the MCS table, based on the type corresponding to the scheduling information being CORESET2.
  • the corresponding MCS table can be set in the CORESET, or the corresponding CORESET type can be set in the MCS table through protocol agreement or high-level configuration.
  • the configuration can be indicated by high layer/physical layer signaling or by protocol agreement.
  • the CORESET that does not have the MCS table configured corresponds to the default MCS table.
  • the default MCS form is agreed by the protocol, or signaled.
  • a high density CORESET is configured with a smaller MCS table, or a lower order MCS table.
  • the default MCS table may be used for subsequent processing.
  • the default MCS table may be one of the multiple MCS tables.
  • the two tables MCS1 and MCS2 are currently configured, and may be specified by the network side or by a protocol.
  • the default MCS table is MCS1 (or MCS2).
  • the MCS table is determined based on the Search Space set/Search Space configuration.
  • the network side configures the MCS table corresponding to the scheduling information of different Search Space Set/Search Spaces through protocol agreement or high layer configuration; wherein the scheduling information of different Search Space Set/Search Spaces can be understood as different types. Scheduling information.
  • the scheduling information of the Search Space Set/Search Space 1 has a correspondence relationship with the MCS table 1
  • the scheduling information of the Search Space Set/Search Space 2 has a correspondence relationship with the MCS table 2.
  • the terminal device receives the scheduling information sent by the network side, which may be:
  • the scheduling information received by the terminal device in Search Space Set/Search Space 1. It can be understood that the type corresponding to the scheduling information is Search Space Set/Search Space 1.
  • the determining, by the terminal device, the target MCS table from the at least two MCS tables based on the correspondence between the scheduling information, the scheduling information, and the MCS table may include:
  • the target MCS table may be determined as the MCS table 1.
  • step 102 the scheduling information received by the terminal in the Search Space Set/Search Space 2. It can be understood that the type corresponding to the scheduling information is CORESET 2.
  • step 103 is specifically: determining, according to the correspondence between the scheduling information of the search space Set/Search Space 2 and the search space Set/Search Space 2 and the MCS table, the target MCS can be determined.
  • the form is MCS Form 2.
  • one configuration may be: a high aggregation level Search space set/Search space configures a smaller MCS table, or a lower order MCS table.
  • the MCS table corresponding to the scheduling information corresponding to the different time domain resource finger types is configured by the protocol, or the higher time domain resource refers to the type of scheduling information. Understand different types of scheduling information. For example, the scheduling information of the Type A has a correspondence relationship with the MCS table 1, and the scheduling information of the Type B has a correspondence relationship with the MCS table 2.
  • the terminal device receives the scheduling information sent by the network side, which may be:
  • the scheduling information received by the terminal device in Type A it can be understood that the type corresponding to the scheduling information is Type A.
  • the determining, by the terminal device, the target MCS table from the at least two MCS tables based on the correspondence between the scheduling information, the scheduling information, and the MCS table may include:
  • the target MCS table may be determined as the MCS table 1.
  • step 102 scheduling information received by the terminal at Type B. It can be understood that the type corresponding to the scheduling information is Type B.
  • step 103 is specifically: determining that the target MCS table is the MCS table 2 based on the correspondence between the scheduling information of the Type B and the Type B and the MCS table corresponding to the scheduling information.
  • the MCS table is used.
  • Type A uses a regular MCS form
  • Type B uses an MCS form that covers an ultra-low bit rate, or a smaller MCS form.
  • the MCS table corresponding to the scheduling information of the different time domain resource length/time domain length range is configured by the protocol, or the high layer, and the scheduling information of different time domain resource length/time domain length range can be understood as different types of scheduling. information.
  • the scheduling information of the time domain resource length/time domain length range 1 has a corresponding relationship with the MCS table 1
  • the scheduling information of the time domain resource length/time domain length range 2 has a corresponding relationship with the MCS table 2.
  • the terminal device receives the scheduling information sent by the network side, which may be:
  • the time domain resource length/time domain length at which the terminal device receives the scheduling information is in the range 1. It can be understood that the type corresponding to the scheduling information is the time domain resource length/time domain length range 1.
  • the determining, by the terminal device, the target MCS table from the at least two MCS tables based on the correspondence between the scheduling information, the scheduling information, and the MCS table may include:
  • the MCS table 1 corresponding to the scheduling information of the time domain resource length/time domain length range 1 is the target MCS table; according to the MCS table 1 Analyze the MCS level.
  • step 102 the time domain resource length/time domain length of the terminal device receiving the scheduling information is in the range 2. It can be understood that the type corresponding to the scheduling information is the time domain resource length/time domain length range 1.
  • the step 103 is specifically: the type corresponding to the scheduling information is the time domain resource length/time domain length range 2, and the time domain resource length/time domain length range 2 scheduling information corresponding to the MCS table 2 is Target MCS form; then MCS level is parsed according to MCS Form 2.
  • the fifth type determines the MCS table based on the DCI format, or can be specifically understood as the DCI format length to determine the MCS table:
  • the MCS table corresponding to the scheduling information of different DCI formats may be configured by a protocol or by a higher layer.
  • the scheduling information of different DCI formats may be understood as different types of scheduling information.
  • the scheduling information of the compressed DCI format has a corresponding relationship with the MCS table 1
  • the conventional DCI format has a corresponding relationship with the MCS table 2.
  • the terminal device receives the scheduling information sent by the network side, which may be:
  • the terminal compresses the scheduling information received in the DCI format. It can be understood that the type corresponding to the scheduling information is a compressed DCI format.
  • the determining, by the terminal device, the target MCS table from the at least two MCS tables based on the correspondence between the scheduling information, the scheduling information, and the MCS table may include:
  • the target MCS table is determined to be the MCS table 1.
  • step 102 scheduling information received by the terminal device in the regular DCI format. It can be understood that the type corresponding to the scheduling information is a conventional DCI format.
  • step 103 is specifically: determining, according to the correspondence type of the scheduling information, that the target MCS table is the MCS table 2, based on the correspondence between the scheduling information of the regular DCI format and the MCS table.
  • the compressed DCI format may correspond to a smaller MCS table, which may correspond to a larger MCS table.
  • the sixth type determines the MCS table based on the aggregation level:
  • the MCS table corresponding to the scheduling information of different Aggregation levels is configured by the protocol or by the higher layer.
  • the scheduling information of different aggregation levels can be understood as different types of scheduling information.
  • the scheduling information of the low aggregation level has a correspondence relationship with the MCS table 1
  • the scheduling information of the high aggregation level has a correspondence relationship with the MCS table 2.
  • the terminal device receives the scheduling information sent by the network side, which may be:
  • the scheduling information received by the terminal device on the downlink control channel with a low aggregation level is a low aggregation level.
  • the determining, by the terminal device, the target MCS table from the at least two MCS tables based on the correspondence between the scheduling information, the scheduling information, and the MCS table may include:
  • the target MCS table may be determined as the MCS table 1.
  • step 102 the scheduling information received by the terminal on the downlink control channel with a high aggregation level. It can be understood that the type corresponding to the scheduling information is a high aggregation level.
  • step 103 is specifically: determining that the target MCS table is the MCS table 2 based on the correspondence between the scheduling information corresponding to the scheduling information and the high aggregation level and the high aggregation level and the MCS table.
  • a low aggregation level configuration includes a high spectral efficiency MCS table
  • a high aggregation level configuration includes a low spectral efficiency MCS table
  • the division of the low aggregation level and the high aggregation level may be a base station configuration, or a protocol convention.
  • One type of aggregation level can include one or more aggregation levels.
  • aggregation levels 1, 2, 4 correspond to MCS tables containing high spectral efficiency
  • aggregation levels 8, 16 correspond to MCS tables containing low frequency efficiency.
  • the seventh type based on the business instructions to determine the MCS form:
  • the correspondence between the scheduling information corresponding to the different service indications and the MCS table is configured by the protocol, or the high-level configuration, wherein the scheduling information corresponding to the different service indications can be understood as different types of scheduling information.
  • the scheduling information of the URLLC has a correspondence relationship with the MCS table 1
  • the scheduling information of the eMBB has a corresponding relationship with the MCS table 2.
  • the terminal device receives the scheduling information sent by the network side, which may be:
  • the scheduling information received by the terminal is downlink control information for scheduling the URLLC. It can be understood that the type corresponding to the scheduling information is URLLC.
  • the determining, by the terminal device, the target MCS table from the at least two MCS tables based on the correspondence between the scheduling information, the scheduling information, and the MCS table may include:
  • the target MCS table may be determined as the MCS table 1.
  • step 102 is that the scheduling information received by the terminal is the downlink control information for scheduling the eMBB, it can be understood that the type corresponding to the scheduling information is eMBB.
  • step 103 is specifically: determining, based on the correspondence between the scheduling information of the eMBB and the eMBB and the MCS table, that the target MCS table is the MCS table 2.
  • the eighth type determines the MCS table based on the control channel CRC:
  • the MCS table corresponding to the scheduling information corresponding to the different control channel CRCs is configured by a protocol or a higher layer; wherein scheduling information of different control channel CRCs can be understood as different types of scheduling information.
  • the scheduling information of the control channel CRC type 1 has a correspondence relationship with the MCS table 1
  • the scheduling information of the control channel CRC type 2 has a correspondence relationship with the MCS table 2.
  • the terminal device receives the scheduling information sent by the network side, which may be:
  • the scheduling information received by the terminal is the downlink control information of the CRC type 1 of the control channel. It can be understood that the type corresponding to the scheduling information is the control channel CRC type 1.
  • the determining, by the terminal device, the target MCS table from the at least two MCS tables based on the correspondence between the scheduling information, the scheduling information, and the MCS table may include:
  • the target MCS table may be determined as the MCS table 1.
  • the terminal device receives the scheduling information sent by the network side, and may be:
  • the scheduling information received by the terminal is the downlink control information of the control channel CRC type 2; it can be understood that the type corresponding to the scheduling information is the control channel CRC type 2.
  • the determining, by the terminal device, the target MCS table from the at least two MCS tables based on the correspondence between the scheduling information, the scheduling information, and the MCS table may include:
  • the target MCS table may be determined as the MCS table 2.
  • control channel CRC type can be distinguished by CRC length, and/or CRC generation.
  • control channel CRC Type 1 is used for URLLC traffic scheduling, which is configured with an MCS table for URLLC;
  • Control Channel CRC Type 2 is used for eMBB traffic scheduling, for which an MCS table for eMBB is configured.
  • the ninth type determines the MCS table based on the control channel RNTI:
  • the MCS table corresponding to the scheduling information of the different control channel RNTIs is configured by a protocol or a higher layer; wherein the scheduling information corresponding to different control channels RNTI can be understood as different kinds of scheduling information.
  • the scheduling information of the control channel RNTI type 1 has a correspondence relationship with the MCS table 1
  • the scheduling information of the control channel RNTI type 2 has a corresponding relationship with the MCS table 2.
  • the terminal device receives the scheduling information sent by the network side, which may be:
  • the scheduling information received by the terminal is the downlink control information that is scrambled by the control channel RNTI type 1; it can be understood that the type corresponding to the scheduling information is the control channel RNTI type 1.
  • the determining, by the terminal device, the target MCS table from the at least two MCS tables based on the correspondence between the scheduling information, the scheduling information, and the MCS table may include:
  • the target MCS table may be determined as the MCS table 1.
  • the terminal device receives the scheduling information sent by the network side, and may be:
  • the scheduling information received by the terminal is downlink control information that is scrambled by the control channel RNTI type 2; it can be understood that the type corresponding to the scheduling information is the control channel RNTI type 2.
  • the determining, by the terminal device, the target MCS table from the at least two MCS tables based on the correspondence between the scheduling information, the scheduling information, and the MCS table may include:
  • the target MCS table may be determined as the MCS table 1.
  • control channel RNTI type can be distinguished by RNTI values.
  • control channel RNTI type 1 is used for URLLC traffic scheduling, which is configured with an MCS table for URLLC;
  • control channel RNTI type 2 is used for eMBB traffic scheduling, for which an MCS table for eMBB is configured.
  • the dynamic configuration of the MCS table can be implemented to adapt to the dynamic scheduling of the URLLC and the eMBB service.
  • the implicit indication method the physical layer signaling overhead is reduced, and the reliability of the physical layer signaling is improved.
  • the embodiment of the invention provides a dynamic configuration method, which is applied to a network device. As shown in FIG. 2, the method includes:
  • Step 201 Send configuration information of at least two modulation and coding policy MCS tables to the terminal device, where the configuration information is used to determine the at least two MCS tables;
  • Step 202 Send scheduling information to the terminal device, where the scheduling information has a corresponding relationship with the MCS table.
  • the terminal receives the scheduling information, and then the terminal determines the MCS table based on the scheduling information.
  • the terminal device receives at least two MCS table configuration information from the network side.
  • the at least two modulation and coding policy MCS tables include at least: a first MCS table, and a second MCS table.
  • the first MCS table is part of the content of the second MCS table
  • the first MCS table is composed of elements corresponding to odd or even index values in the second MCS table.
  • the first MCS table is part of the content of the second MCS table, and is:
  • the first MCS table is the first half of the content of the second MCS table.
  • the first MCS table may also be the content of the second half of the second MCS table, and may also be the content of the middle portion, which is not exhaustive in this embodiment.
  • the first half of the content may be half of the entries included in the second MCS table, specifically the first half of the entries; correspondingly, the latter half of the content and the middle portion of the content are not described in detail.
  • the scheduling information includes at least one of the following: a control resource set; a search space set; a search space; a time domain resource indication type; a time domain resource length; an MCS table indication information; a DCI format; an aggregation level (Aggregation level); ; Cyclic Redundancy Check (CRC); Radio Network Tempory Identity (RNTI).
  • a control resource set a search space set; a search space; a time domain resource indication type; a time domain resource length; an MCS table indication information; a DCI format; an aggregation level (Aggregation level); ; Cyclic Redundancy Check (CRC); Radio Network Tempory Identity (RNTI).
  • a control resource set includes at least one of the following: a control resource set; a search space set; a search space; a time domain resource indication type; a time domain resource length; an MCS table indication information; a DCI format; an aggregation level (Aggregation level); ; Cyclic Redundancy Check
  • CORESET Control Resource Set
  • Search space set search space set
  • Search space Search space
  • Time domain resource indication type Type A or Type B
  • Time domain resource length Short TTI or long TTI
  • the method further includes:
  • the correspondence between the scheduling information and the MCS table is determined based on the protocol, or the correspondence between the scheduling information and the MCS table is determined based on the high layer configuration. Specifically, the relationship between the MCS table and the above information is agreed by the agreement or the high layer configuration.
  • the method further includes configuring a corresponding MCS table for each of the scheduling information of each type of scheduling information.
  • the first based on the CORESET (Control Resource Set) configuration determines the MCS (Modulation and Coding Strategy) table.
  • the MCS table corresponding to the scheduling information of the different control resource sets may be configured by a protocol or a higher layer; wherein the scheduling information of the different control resource sets may be understood as different types of scheduling information.
  • the scheduling information of the CORESET 1 has a correspondence relationship with the MCS table 1
  • the scheduling information of the CORESET 2 has a correspondence relationship with the MCS table 2.
  • the scheduling information received by the terminal at the CORESET 1 can be understood as: the type corresponding to the scheduling information is CORESET 1; the type corresponding to the scheduling information by the terminal is CORESET1, and the scheduling information of the CORESET1 and the MCS table.
  • the correspondence between the MCS table 1 and the MCS table 2 is determined as the MCS table 1.
  • the target MCS table is determined to be the MCS table 2.
  • the corresponding MCS table can be set in the CORESET, or the corresponding CORESET type can be set in the MCS table through protocol agreement or high-level configuration.
  • the configuration can be indicated by high layer/physical layer signaling or by protocol agreement.
  • the CORESET that does not have the MCS table configured corresponds to the default MCS table.
  • the default MCS form is agreed by the protocol, or signaled.
  • a high density CORESET is configured with a smaller MCS table, or a lower order MCS table.
  • the default MCS table can be used for subsequent processing.
  • the default MCS table may be one of the multiple MCS tables.
  • the two tables MCS1 and MCS2 are currently configured, and may be specified by the network side or by a protocol.
  • the default MCS table is MCS1 (or MCS2).
  • the MCS table is determined based on the Search Space set/Search Space configuration.
  • the network side configures the MCS table corresponding to the scheduling information of different Search Space Set/Search Spaces through protocol agreement or high layer configuration; wherein the scheduling information of different Search Space Set/Search Spaces can be understood as different types. Scheduling information.
  • the scheduling information of the Search Space Set/Search Space 1 has a correspondence relationship with the MCS table 1
  • the scheduling information of the Search Space Set/Search Space 2 has a correspondence relationship with the MCS table 2.
  • the scheduling information received by the terminal device in the Search Space Set/Search Space 1 is based on the scheduling information of the Search Space Set/Search Space 1 and the Search Space Set/Search Space 1 and the MCS.
  • the correspondence between the tables can be determined that the target MCS table is MCS Table 1.
  • the scheduling information received by the terminal in the Search Space Set/Search Space 2 is based on the type of the scheduling information corresponding to the Search Space Set/Search Space 2 and the Search Space Set/Search Space 2 and the MCS table.
  • it can be determined that the target MCS table is MCS Table 2.
  • a high aggregation level of Search space set/Search space configures a smaller MCS table, or a lower order MCS table.
  • the MCS table corresponding to the scheduling information corresponding to the different time domain resource finger types is configured by the protocol, or the higher time domain resource refers to the type of scheduling information. Understand different types of scheduling information. For example, the scheduling information of the Type A has a correspondence relationship with the MCS table 1, and the scheduling information of the Type B has a correspondence relationship with the MCS table 2.
  • the scheduling information received by the terminal device in the Type A is understood to be that the type corresponding to the scheduling information is Type A, and the type corresponding to the scheduling information is Type A and Search Space Set/Search Space 1
  • the correspondence between the scheduling information and the MCS table can determine that the target MCS table is MCS Table 1.
  • the scheduling information received by the terminal in Type B It can be understood that the type corresponding to the scheduling information is Type B, and the target MCS table can be determined as the MCS based on the correspondence between the scheduling information of the Type B and the Type B and the MCS table corresponding to the scheduling information.
  • Type A uses a regular MCS form
  • Type B uses an MCS form that covers an ultra-low bit rate, or a smaller MCS form.
  • the MCS table corresponding to the scheduling information of the different time domain resource length/time domain length range is configured by the protocol, or the high layer, and the scheduling information of different time domain resource length/time domain length range can be understood as different types of scheduling. information.
  • the scheduling information of the time domain resource length/time domain length range 1 has a corresponding relationship with the MCS table 1
  • the scheduling information of the time domain resource length/time domain length range 2 has a corresponding relationship with the MCS table 2.
  • the time domain resource length/time domain length of the terminal device receiving the scheduling information is in the range 1. It can be understood that the type corresponding to the scheduling information is the time domain resource length/time domain length range 1. If the type corresponding to the scheduling information is the time domain resource length/time domain length range 1, the MCS table 1 corresponding to the scheduling information of the time domain resource length/time domain length range 1 is the target MCS table; according to the MCS table 1 Analyze the MCS level.
  • the time domain resource length/time domain length at which the terminal device receives the scheduling information is in the range 2. It can be understood that the type corresponding to the scheduling information is the time domain resource length/time domain length range 1. If the type corresponding to the scheduling information is the time domain resource length/time domain length range 2, the MCS table 2 corresponding to the scheduling information of the time domain resource length/time domain length range 2 is the target MCS table; 2 Analyze the MCS level.
  • the fifth type determines the MCS table based on the DCI format, or can be specifically understood as the DCI format length to determine the MCS table:
  • the MCS table corresponding to the scheduling information of different DCI formats may be configured by a protocol or by a higher layer.
  • the scheduling information of different DCI formats may be understood as different types of scheduling information.
  • the scheduling information of the compressed DCI format has a corresponding relationship with the MCS table 1
  • the conventional DCI format has a corresponding relationship with the MCS table 2.
  • the terminal compresses the scheduling information received in the DCI format. It can be understood that the type corresponding to the scheduling information is a compressed DCI format. Based on the type corresponding to the scheduling information, the compressed DCI format, and the correspondence between the scheduling information of the compressed DCI format and the MCS table, from the MCS table 1 and the MCS table 2, the target MCS table is determined to be the MCS table 1.
  • the terminal device receives scheduling information in the regular DCI format.
  • the type corresponding to the scheduling information is a conventional DCI format.
  • the target MCS table is determined to be the MCS table 2 based on the correspondence between the scheduling information of the regular DCI format and the MCS table, based on the type corresponding to the scheduling information being a conventional DCI format.
  • the compressed DCI format may correspond to a smaller MCS table, which may correspond to a larger MCS table.
  • the sixth type determines the MCS table based on the aggregation level:
  • the MCS table corresponding to the scheduling information of different Aggregation levels is configured by the protocol or by the higher layer.
  • the scheduling information of different aggregation levels can be understood as different types of scheduling information.
  • the scheduling information of the low aggregation level has a correspondence relationship with the MCS table 1
  • the scheduling information of the high aggregation level has a correspondence relationship with the MCS table 2.
  • the scheduling information received by the terminal device on the downlink control channel with a low aggregation level is a low aggregation level.
  • the target MCS table may be determined as the MCS table 1.
  • the target MCS table may be determined as the MCS table 2 based on the correspondence between the scheduling information corresponding to the scheduling information and the high aggregation level and the high aggregation level and the MCS table.
  • a low aggregation level configuration includes a high spectral efficiency MCS table
  • a high aggregation level configuration includes a low spectral efficiency MCS table
  • the division of the low aggregation level and the high aggregation level may be a base station configuration, or a protocol convention.
  • One type of aggregation level can include one or more aggregation levels.
  • aggregation levels 1, 2, 4 correspond to MCS tables containing high spectral efficiency
  • aggregation levels 8, 16 correspond to MCS tables containing low frequency efficiency.
  • the seventh type based on the business instructions to determine the MCS form:
  • the correspondence between the scheduling information corresponding to the different service indications and the MCS table is configured by the protocol, or the high-level configuration, wherein the scheduling information corresponding to the different service indications can be understood as different types of scheduling information.
  • the scheduling information of the URLLC has a correspondence relationship with the MCS table 1
  • the scheduling information of the eMBB has a corresponding relationship with the MCS table 2.
  • the scheduling information received by the terminal is downlink control information for scheduling the URLLC. It can be understood that the type corresponding to the scheduling information is URLLC. Based on the correspondence between the type of the URL information and the scheduling information of the URLLC and the MCS table, the target MCS table may be determined as the MCS table 1.
  • the scheduling information received by the terminal is the downlink control information for scheduling the eMBB
  • the type corresponding to the scheduling information is eMBB.
  • the target MCS table may be determined as the MCS table 2.
  • the eighth type determines the MCS table based on the control channel CRC:
  • the MCS table corresponding to the scheduling information corresponding to the different control channel CRCs is configured by a protocol or a higher layer; wherein scheduling information of different control channel CRCs can be understood as different types of scheduling information.
  • the scheduling information of the control channel CRC type 1 has a correspondence relationship with the MCS table 1
  • the scheduling information of the control channel CRC type 2 has a correspondence relationship with the MCS table 2.
  • the scheduling information received by the terminal is the downlink control information of the CRC type 1 of the control channel. It can be understood that the type corresponding to the scheduling information is the control channel CRC type 1. Based on the correspondence between the scheduling information of the control channel CRC type 1 and the control channel CRC type 1 and the MCS table, the target MCS table may be determined as the MCS table 1.
  • the scheduling information received by the terminal is the downlink control information of the control channel CRC type 2; it can be understood that the type corresponding to the scheduling information is the control channel CRC type 2.
  • the target MCS table may be determined as the MCS table 2.
  • control channel CRC type can be distinguished by CRC length, and/or CRC generation.
  • control channel CRC Type 1 is used for URLLC traffic scheduling, which is configured with an MCS table for URLLC;
  • Control Channel CRC Type 2 is used for eMBB traffic scheduling, for which an MCS table for eMBB is configured.
  • the ninth type determines the MCS table based on the control channel RNTI:
  • the MCS table corresponding to the scheduling information of the different control channel RNTIs is configured by a protocol or a higher layer; wherein the scheduling information corresponding to different control channels RNTI can be understood as different kinds of scheduling information.
  • the scheduling information of the control channel RNTI type 1 has a correspondence relationship with the MCS table 1
  • the scheduling information of the control channel RNTI type 2 has a corresponding relationship with the MCS table 2.
  • the scheduling information received by the terminal is the downlink control information that is scrambled by the control channel RNTI type 1; it can be understood that the type corresponding to the scheduling information is the control channel RNTI type 1.
  • the target MCS table may be determined as the MCS table 1.
  • the scheduling information received by the terminal is downlink control information that is scrambled by the control channel RNTI type 2; it can be understood that the type corresponding to the scheduling information is the control channel RNTI type 2.
  • the target MCS table may be determined as the MCS table 1.
  • control channel RNTI type can be distinguished by RNTI values.
  • control channel RNTI type 1 is used for URLLC traffic scheduling, which is configured with an MCS table for URLLC;
  • control channel RNTI type 2 is used for eMBB traffic scheduling, for which an MCS table for eMBB is configured.
  • the dynamic configuration of the MCS table can be implemented to adapt to the dynamic scheduling of the URLLC and the eMBB service.
  • the implicit indication method the physical layer signaling overhead is reduced, and the reliability of the physical layer signaling is improved.
  • An embodiment of the present invention provides a terminal device, as shown in FIG. 3, including:
  • the first communication unit 31 receives configuration information of at least two modulation and coding policy MCS tables, where the configuration information is used to determine the at least two MCS tables; and receives scheduling information sent by the network side;
  • the first processing unit 32 determines a target MCS table from the at least two MCS tables based on the correspondence between the scheduling information, the scheduling information, and the MCS table.
  • the terminal receives the scheduling information, and then the terminal determines the MCS table based on the scheduling information.
  • the terminal device receives at least two MCS table configuration information from the network side.
  • the at least two modulation and coding policy MCS tables include at least: a first MCS table, and a second MCS table.
  • the first MCS table is part of the content of the second MCS table
  • the first MCS table is composed of elements corresponding to odd or even index values in the second MCS table.
  • the first MCS table is part of the content of the second MCS table, and is:
  • the first MCS table is the first half of the content of the second MCS table.
  • the first MCS table may also be the content of the second half of the second MCS table, and may also be the content of the middle portion, which is not exhaustive in this embodiment.
  • the first half of the content may be half of the entries included in the second MCS table, specifically the first half of the entries; correspondingly, the latter half of the content and the middle portion of the content are not described in detail.
  • the scheduling information includes at least one of the following: a control resource set; a search space set; a search space; a time domain resource indication type; a time domain resource length; an MCS table indication information; and a downlink control information (DCI, Downlink Control Information) format; Aggregation level; service indication; cyclic redundancy check (CRC); Radio Network Tempory Identity (RNTI).
  • DCI Downlink Control Information
  • CRC cyclic redundancy check
  • RNTI Radio Network Tempory Identity
  • the control resource set may be a CORESET (Control Resource Set); the search space set may be a search space set; the search space may be a search space; the time domain resource indication type, for example, may be Type A or Type B; the time domain resource length , can be Short TTI or long TTI; MCS table instructions.
  • CORESET Control Resource Set
  • the search space set may be a search space set
  • the search space may be a search space
  • the time domain resource indication type for example, may be Type A or Type B
  • the time domain resource length can be Short TTI or long TTI
  • MCS table instructions can be Short TTI or long TTI
  • the first processing unit 32 determines a correspondence between the scheduling information and the MCS table based on the protocol, or determines a correspondence between the scheduling information and the MCS table based on the high layer configuration. Specifically, the relationship between the MCS table and the above information is agreed by the agreement or the high layer configuration.
  • the first processing unit 32 configures a corresponding MCS table for each of the scheduling information of each type of scheduling information.
  • the first processing unit 32 determines the type corresponding to the received scheduling information
  • the type of the scheduling information may include: the scheduling information is a control resource set; the search space set; the search space; the time domain resource indication type; the time domain resource length; and one of the MCS table indication information.
  • the scheduling information is a control resource set; the search space set; the search space; the time domain resource indication type; the time domain resource length; and one of the MCS table indication information.
  • there are different kinds of scheduling information such as a control resource set A, a control resource set B, and the like; and a search space set A, a search space set B, and the like. It can be understood as different kinds of scheduling information in different types of scheduling information. In general, it can be understood as different kinds of scheduling information.
  • the first, based on the CORESET (Control Resource Set) configuration determines the MCS (Modulation and Coding Strategy) table:
  • the MCS table corresponding to the scheduling information of the different control resource sets may be configured by a protocol or a higher layer; wherein the scheduling information of the different control resource sets may be understood as different types of scheduling information.
  • the scheduling information of the CORESET 1 has a correspondence relationship with the MCS table 1
  • the scheduling information of the CORESET 2 has a correspondence relationship with the MCS table 2.
  • the scheduling information is received at CORESET 1. It can be understood that the type corresponding to the scheduling information is CORESET 1.
  • the first processing unit 32 determines the target MCS table as the MCS table 1 from the MCS table 1 and the MCS table 2 based on the correspondence between the scheduling information and the MCS table, and the correspondence between the scheduling information of the CORESET1 and the MCS table. .
  • the first processing unit 32 determines that the target MCS table is the MCS table 2 based on the correspondence between the scheduling information of the CORESET2 and the MCS table based on the type corresponding to the scheduling information being CORESET2.
  • the corresponding MCS table can be set in the CORESET, or the corresponding CORESET type can be set in the MCS table through protocol agreement or high-level configuration.
  • the configuration can be indicated by high layer/physical layer signaling or by protocol agreement.
  • the CORESET that does not have the MCS table configured corresponds to the default MCS table.
  • the default MCS form is agreed by the protocol, or signaled.
  • a high density CORESET is configured with a smaller MCS table, or a lower order MCS table.
  • the default MCS table may be used for subsequent processing.
  • the default MCS table may be one of the multiple MCS tables.
  • the two tables MCS1 and MCS2 are currently configured, and may be specified by the network side or by a protocol.
  • the default MCS table is MCS1 (or MCS2).
  • the MCS table is determined based on the Search Space set/Search Space configuration.
  • the network side configures the MCS table corresponding to the scheduling information of different Search Space Set/Search Spaces through protocol agreement or high layer configuration; wherein the scheduling information of different Search Space Set/Search Spaces can be understood as different types. Scheduling information.
  • the scheduling information of the Search Space Set/Search Space 1 has a correspondence relationship with the MCS table 1
  • the scheduling information of the Search Space Set/Search Space 2 has a correspondence relationship with the MCS table 2.
  • the scheduling information received in the Search Space Set/Search Space 1 is as follows. It can be understood that the type corresponding to the scheduling information is Search Space Set/Search Space 1.
  • the first processing unit 32 may determine that the target MCS table is determined based on the correspondence between the scheduling information of the search space Set/Search Space 1 and the search space Set/Search Space 1 and the MCS table. MCS Form 1.
  • the first communication unit receives the scheduling information in the Search Space Set/Search Space 2. It can be understood that the type corresponding to the scheduling information is CORESET 2.
  • the first processing unit 32 can determine the target based on the correspondence between the scheduling information of the Search Space Set/Search Space 2 and the Search Space Set/Search Space 2 and the MCS table according to the type corresponding to the scheduling information.
  • the MCS form is MCS Form 2.
  • one configuration may be: a high aggregation level Search space set/Search space configures a smaller MCS table, or a lower order MCS table.
  • the MCS table corresponding to the scheduling information corresponding to the different time domain resource finger types is configured by the protocol, or the higher time domain resource refers to the type of scheduling information. Understand different types of scheduling information. For example, the scheduling information of the Type A has a correspondence relationship with the MCS table 1, and the scheduling information of the Type B has a correspondence relationship with the MCS table 2.
  • the scheduling information received by the first communication unit 31 in the Type A is as follows: It can be understood that the type corresponding to the scheduling information is Type A.
  • the first processing unit 32 may determine that the target MCS table is the MCS table 1 based on the correspondence between the scheduling information of the type A and the search space Set/Search Space 1 and the MCS table.
  • the first communication unit 31 receives the scheduling information at Type B. It can be understood that the type corresponding to the scheduling information is Type B.
  • the first processing unit 32 may determine that the target MCS table is the MCS table 2 based on the correspondence between the scheduling information of the Type B and the Type B corresponding to the scheduling information and the MCS table.
  • the MCS table is used.
  • Type A uses a regular MCS form
  • Type B uses an MCS form that covers an ultra-low bit rate, or a smaller MCS form.
  • the MCS table corresponding to the scheduling information of the different time domain resource length/time domain length range is configured by the protocol, or the high layer, and the scheduling information of different time domain resource length/time domain length range can be understood as different types of scheduling. information.
  • the scheduling information of the time domain resource length/time domain length range 1 has a corresponding relationship with the MCS table 1
  • the scheduling information of the time domain resource length/time domain length range 2 has a corresponding relationship with the MCS table 2.
  • the time domain resource length/time domain length of the first communication unit 31 receiving the scheduling information is in the range 1. It can be understood that the type corresponding to the scheduling information is the time domain resource length/time domain length range 1.
  • the first processing unit 32 is based on the time domain resource length/time domain length range 1 of the scheduling information, and the MCS table 1 corresponding to the scheduling information of the time domain resource length/time domain length range 1 is the target MCS. Form; parse the MCS level according to MCS Form 1.
  • the time domain resource length/time domain length is in the range 2. It can be understood that the type corresponding to the scheduling information is the time domain resource length/time domain length range 1.
  • the first processing unit 32 is based on the time domain resource length/time domain length range 2 corresponding to the scheduling information, and the MCS table 2 corresponding to the scheduling information of the time domain resource length/time domain length range 2 For the target MCS table; the MCS level is resolved according to MCS Table 2.
  • the fifth type determines the MCS table based on the DCI format, or can be specifically understood as the DCI format length to determine the MCS table:
  • the MCS table corresponding to the scheduling information of different DCI formats may be configured by a protocol or by a higher layer.
  • the scheduling information of different DCI formats may be understood as different types of scheduling information.
  • the scheduling information of the compressed DCI format has a corresponding relationship with the MCS table 1
  • the conventional DCI format has a corresponding relationship with the MCS table 2.
  • the scheduling information received in the compressed DCI format is received in the compressed DCI format.
  • the type corresponding to the scheduling information is a compressed DCI format.
  • the first processing unit 32 determines the target MCS table from the MCS table 1 and the MCS table 2 based on the type corresponding to the scheduling information being the compressed DCI format and the correspondence between the scheduling information of the compressed DCI format and the MCS table. For MCS Form 1.
  • the scheduling information is received in the regular DCI format. It can be understood that the type corresponding to the scheduling information is a conventional DCI format.
  • the first processing unit 32 determines that the target MCS table is the MCS table 2 based on the correspondence between the scheduling information of the regular DCI format and the MCS table, based on the type corresponding to the scheduling information being a conventional DCI format.
  • the compressed DCI format may correspond to a smaller MCS table, which may correspond to a larger MCS table.
  • the sixth type determines the MCS table based on the aggregation level:
  • the MCS table corresponding to the scheduling information of different Aggregation levels is configured by the protocol or by the higher layer.
  • the scheduling information of different aggregation levels can be understood as different types of scheduling information.
  • the scheduling information of the low aggregation level has a correspondence relationship with the MCS table 1
  • the scheduling information of the high aggregation level has a correspondence relationship with the MCS table 2.
  • the scheduling information received by the first communication unit 31 on the downlink control channel of the low aggregation level is as follows. It can be understood that the type corresponding to the scheduling information is a low aggregation level.
  • the first processing unit 32 may determine that the target MCS table is the MCS table 1 based on the correspondence between the scheduling information of the low aggregation level and the low aggregation level and the MCS table.
  • the first communication unit 31 is in the scheduling information received by the downlink control channel of the high aggregation level. It can be understood that the type corresponding to the scheduling information is a high aggregation level.
  • the first processing unit 32 may determine that the target MCS table is the MCS table 2 based on the correspondence between the scheduling information corresponding to the scheduling information and the high aggregation level and the high aggregation level and the MCS table.
  • a low aggregation level configuration includes a high spectral efficiency MCS table
  • a high aggregation level configuration includes a low spectral efficiency MCS table
  • the division of the low aggregation level and the high aggregation level may be a base station configuration, or a protocol convention.
  • One type of aggregation level can include one or more aggregation levels.
  • aggregation levels 1, 2, 4 correspond to MCS tables containing high spectral efficiency
  • aggregation levels 8, 16 correspond to MCS tables containing low frequency efficiency.
  • the seventh type based on the business instructions to determine the MCS form:
  • the correspondence between the scheduling information corresponding to the different service indications and the MCS table is configured by the protocol, or the high-level configuration, wherein the scheduling information corresponding to the different service indications can be understood as different types of scheduling information.
  • the scheduling information of the URLLC has a correspondence relationship with the MCS table 1
  • the scheduling information of the eMBB has a corresponding relationship with the MCS table 2.
  • the scheduling information received by the first communication unit 31 is downlink control information for scheduling the URLLC. It can be understood that the type corresponding to the scheduling information is URLLC.
  • the first processing unit 32 may determine that the target MCS table is the MCS table 1 based on the correspondence between the type of the URL information and the scheduling information of the URLLC and the MCS table.
  • the scheduling information received by the first communication unit 31 is the downlink control information for scheduling the eMBB, it can be understood that the type corresponding to the scheduling information is eMBB.
  • the first processing unit 32 may determine that the target MCS table is the MCS table 2 based on the correspondence between the scheduling information of the eMBB and the eMBB and the MCS table.
  • the eighth type determines the MCS table based on the control channel CRC:
  • the MCS table corresponding to the scheduling information corresponding to the different control channel CRCs is configured by a protocol or a higher layer; wherein scheduling information of different control channel CRCs can be understood as different types of scheduling information.
  • the scheduling information of the control channel CRC type 1 has a correspondence relationship with the MCS table 1
  • the scheduling information of the control channel CRC type 2 has a correspondence relationship with the MCS table 2.
  • the scheduling information received by the first communication unit 31 is the downlink control information of the control channel CRC type 1; it can be understood that the type corresponding to the scheduling information is the control channel CRC type 1.
  • the first processing unit 32 may determine that the target MCS table is the MCS table 1 based on the correspondence between the scheduling information of the control channel CRC type 1 and the control channel CRC type 1 and the MCS table.
  • the scheduling information received by the first communication unit 31 is the downlink control information of the control channel CRC type 2, it can be understood that the type corresponding to the scheduling information is the control channel CRC type 2.
  • the first processing unit 32 may determine that the target MCS table is the MCS table 2 based on the correspondence between the scheduling information of the control channel CRC type 2 and the control channel CRC type 2 and the MCS table.
  • control channel CRC type can be distinguished by CRC length, and/or CRC generation.
  • control channel CRC Type 1 is used for URLLC traffic scheduling, which is configured with an MCS table for URLLC;
  • Control Channel CRC Type 2 is used for eMBB traffic scheduling, for which an MCS table for eMBB is configured.
  • the ninth type determines the MCS table based on the control channel RNTI:
  • the MCS table corresponding to the scheduling information of the different control channel RNTIs is configured by a protocol or a higher layer; wherein the scheduling information corresponding to different control channels RNTI can be understood as different kinds of scheduling information.
  • the scheduling information of the control channel RNTI type 1 has a correspondence relationship with the MCS table 1
  • the scheduling information of the control channel RNTI type 2 has a corresponding relationship with the MCS table 2.
  • the scheduling information received by the first communication unit 31 is the downlink control information that is scrambled by the control channel RNTI type 1; it can be understood that the type corresponding to the scheduling information is the control channel RNTI type 1.
  • the first processing unit 32 may determine that the target MCS table is the MCS table 1 based on the correspondence between the scheduling information of the control channel RNTI type 1 and the control channel RNTI type 1 and the MCS table.
  • the scheduling information received by the first communication unit 31 is the downlink control information that is scrambled by the control channel RNTI type 2, it can be understood that the type corresponding to the scheduling information is the control channel RNTI type 2.
  • the first processing unit 32 may determine that the target MCS table is the MCS table 1 based on the correspondence between the scheduling information of the control channel RNTI type 2 and the control channel RNTI type 2 and the MCS table.
  • control channel RNTI type can be distinguished by RNTI values.
  • control channel RNTI type 1 is used for URLLC traffic scheduling, which is configured with an MCS table for URLLC;
  • control channel RNTI type 2 is used for eMBB traffic scheduling, for which an MCS table for eMBB is configured.
  • the dynamic configuration of the MCS table can be implemented to adapt to the dynamic scheduling of the URLLC and the eMBB service.
  • the implicit indication method the physical layer signaling overhead is reduced, and the reliability of the physical layer signaling is improved.
  • the embodiment of the invention provides a network device. As shown in FIG. 4, the method includes:
  • the second communication unit 41 sends configuration information of at least two modulation and coding policy MCS tables to the terminal device, where the configuration information is used to determine the at least two MCS tables; and the scheduling information is sent to the terminal device; There is a correspondence between the scheduling information and the MCS table.
  • the terminal receives the scheduling information, and then the terminal determines the MCS table based on the scheduling information.
  • the terminal device receives at least two MCS table configuration information from the network side.
  • the at least two modulation and coding policy MCS tables include at least: a first MCS table, and a second MCS table.
  • the first MCS table is part of the content of the second MCS table
  • the first MCS table is composed of elements corresponding to odd or even index values in the second MCS table.
  • the first MCS table is part of the content of the second MCS table, and is:
  • the first MCS table is the first half of the content of the second MCS table.
  • the first MCS table may also be the content of the second half of the second MCS table, and may also be the content of the middle portion, which is not exhaustive in this embodiment.
  • the first half of the content may be half of the entries included in the second MCS table, specifically the first half of the entries; corresponding, the latter half of the content and the middle portion of the content are not described in detail.
  • the scheduling information includes at least one of the following: a control resource set; a search space set; a search space; a time domain resource indication type; a time domain resource length; an MCS table indication information; a DCI format; an aggregation level (Aggregation level); ; Cyclic Redundancy Check (CRC); Radio Network Tempory Identity (RNTI).
  • a control resource set a search space set; a search space; a time domain resource indication type; a time domain resource length; an MCS table indication information; a DCI format; an aggregation level (Aggregation level); ; Cyclic Redundancy Check (CRC); Radio Network Tempory Identity (RNTI).
  • a control resource set includes at least one of the following: a control resource set; a search space set; a search space; a time domain resource indication type; a time domain resource length; an MCS table indication information; a DCI format; an aggregation level (Aggregation level); ; Cyclic Redundancy Check
  • CORESET Control Resource Set
  • Search space set search space set
  • Search space Search space
  • Time domain resource indication type Type A or Type B
  • Time domain resource length Short TTI or long TTI
  • the network device further includes:
  • the second processing unit 42 determines a correspondence between the scheduling information and the MCS table based on the protocol, or determines a correspondence between the scheduling information and the MCS table based on the high layer configuration. Specifically, the relationship between the MCS table and the above information is agreed by the agreement or the high layer configuration.
  • the second processing unit 42 configures a corresponding MCS table for each of the scheduling information of each type of scheduling information.
  • the first based on the CORESET (Control Resource Set) configuration determines the MCS (Modulation and Coding Strategy) table.
  • the MCS table corresponding to the scheduling information of the different control resource sets may be configured by a protocol or a higher layer; wherein the scheduling information of the different control resource sets may be understood as different types of scheduling information.
  • the scheduling information of the CORESET 1 has a correspondence relationship with the MCS table 1
  • the scheduling information of the CORESET 2 has a correspondence relationship with the MCS table 2.
  • the corresponding MCS table can be set in the CORESET, or the corresponding CORESET type can be set in the MCS table through protocol agreement or high-level configuration.
  • the configuration can be indicated by high layer/physical layer signaling or by protocol agreement.
  • the CORESET that does not have the MCS table configured corresponds to the default MCS table.
  • the default MCS form is agreed by the protocol, or signaled.
  • a high density CORESET is configured with a smaller MCS table, or a lower order MCS table.
  • the default MCS table may be used for subsequent processing.
  • the default MCS table may be one of the multiple MCS tables.
  • the two tables MCS1 and MCS2 are currently configured, and may be specified by the network side or by a protocol.
  • the default MCS table is MCS1 (or MCS2).
  • the MCS table is determined based on the Search Space set/Search Space configuration.
  • the network side configures the MCS table corresponding to the scheduling information of different Search Space Set/Search Spaces through protocol agreement or high layer configuration; wherein the scheduling information of different Search Space Set/Search Spaces can be understood as different types. Scheduling information.
  • the scheduling information of the Search Space Set/Search Space 1 has a correspondence relationship with the MCS table 1
  • the scheduling information of the Search Space Set/Search Space 2 has a correspondence relationship with the MCS table 2.
  • a high aggregation level of Search space set/Search space configures a smaller MCS table, or a lower order MCS table.
  • the MCS table corresponding to the scheduling information corresponding to the different time domain resource finger types is configured by the protocol, or the higher time domain resource refers to the type of scheduling information. Understand different types of scheduling information. For example, the scheduling information of the Type A has a correspondence relationship with the MCS table 1, and the scheduling information of the Type B has a correspondence relationship with the MCS table 2.
  • Type A uses a regular MCS form
  • Type B uses an MCS form that covers an ultra-low bit rate, or a smaller MCS form.
  • the MCS table corresponding to the scheduling information of the different time domain resource length/time domain length range is configured by the protocol, or the high layer, and the scheduling information of different time domain resource length/time domain length range can be understood as different types of scheduling. information.
  • the scheduling information of the time domain resource length/time domain length range 1 has a corresponding relationship with the MCS table 1
  • the scheduling information of the time domain resource length/time domain length range 2 has a corresponding relationship with the MCS table 2.
  • the fifth type determines the MCS table based on the DCI format, or can be specifically understood as the DCI format length to determine the MCS table:
  • the MCS table corresponding to the scheduling information of different DCI formats may be configured by a protocol or by a higher layer.
  • the scheduling information of different DCI formats may be understood as different types of scheduling information.
  • the scheduling information of the compressed DCI format has a corresponding relationship with the MCS table 1
  • the conventional DCI format has a corresponding relationship with the MCS table 2.
  • the compressed DCI format may correspond to a smaller MCS table, which may correspond to a larger MCS table.
  • the sixth type determines the MCS table based on the aggregation level:
  • the MCS table corresponding to the scheduling information of different Aggregation levels is configured by the protocol or by the higher layer.
  • the scheduling information of different aggregation levels can be understood as different types of scheduling information.
  • the scheduling information of the low aggregation level has a correspondence relationship with the MCS table 1
  • the scheduling information of the high aggregation level has a correspondence relationship with the MCS table 2.
  • a low aggregation level configuration includes a high spectral efficiency MCS table
  • a high aggregation level configuration includes a low spectral efficiency MCS table
  • the division of the low aggregation level and the high aggregation level may be a base station configuration, or a protocol convention.
  • One type of aggregation level can include one or more aggregation levels.
  • aggregation levels 1, 2, 4 correspond to MCS tables containing high spectral efficiency
  • aggregation levels 8, 16 correspond to MCS tables containing low frequency efficiency.
  • the seventh type based on the business instructions to determine the MCS form:
  • the correspondence between the scheduling information corresponding to the different service indications and the MCS table is configured by the protocol, or the high-level configuration, wherein the scheduling information corresponding to the different service indications can be understood as different types of scheduling information.
  • the scheduling information of the URLLC has a correspondence relationship with the MCS table 1
  • the scheduling information of the eMBB has a corresponding relationship with the MCS table 2.
  • the eighth type determines the MCS table based on the control channel CRC:
  • the MCS table corresponding to the scheduling information corresponding to the different control channel CRCs is configured by a protocol or a higher layer; wherein scheduling information of different control channel CRCs can be understood as different types of scheduling information.
  • the scheduling information of the control channel CRC type 1 has a correspondence relationship with the MCS table 1
  • the scheduling information of the control channel CRC type 2 has a correspondence relationship with the MCS table 2.
  • control channel CRC type can be distinguished by CRC length, and/or CRC generation.
  • control channel CRC Type 1 is used for URLLC traffic scheduling, which is configured with an MCS table for URLLC;
  • Control Channel CRC Type 2 is used for eMBB traffic scheduling, for which an MCS table for eMBB is configured.
  • the ninth type determines the MCS table based on the control channel RNTI:
  • the MCS table corresponding to the scheduling information of the different control channel RNTIs is configured by a protocol or a higher layer; wherein the scheduling information corresponding to different control channels RNTI can be understood as different kinds of scheduling information.
  • the scheduling information of the control channel RNTI type 1 has a correspondence relationship with the MCS table 1
  • the scheduling information of the control channel RNTI type 2 has a corresponding relationship with the MCS table 2.
  • control channel RNTI type can be distinguished by RNTI values.
  • control channel RNTI type 1 is used for URLLC traffic scheduling, which is configured with an MCS table for URLLC;
  • control channel RNTI type 2 is used for eMBB traffic scheduling, for which an MCS table for eMBB is configured.
  • the dynamic configuration of the MCS table can be implemented to adapt to the dynamic scheduling of the URLLC and the eMBB service.
  • the implicit indication method the physical layer signaling overhead is reduced, and the reliability of the physical layer signaling is improved.
  • the embodiment of the present invention further provides a hardware component architecture of a terminal device or a network device.
  • the method includes at least one processor 51, a memory 52, and at least one network interface 53.
  • the various components are coupled together by a bus system 54.
  • bus system 54 is used to implement connection communication between these components.
  • the bus system 54 includes, in addition to the data bus, a power bus, a control bus, and a status signal bus.
  • various buses are labeled as bus system 54 in FIG.
  • the memory 52 in the embodiments of the present invention may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • memory 52 stores elements, executable modules or data structures, or a subset thereof, or their extension set:
  • the processor 51 is configured to be able to process the method steps of the first embodiment or the second embodiment, and details are not described herein.
  • a computer storage medium is provided by the embodiment of the present invention.
  • the computer storage medium stores computer executable instructions. When the computer executable instructions are executed, the method steps of the first embodiment or the second embodiment are implemented.
  • Embodiments of the Invention may be stored in a computer readable storage medium if it is implemented in the form of a software function module and sold or used as a standalone product. Based on such understanding, the technical solution of the embodiments of the present invention may be embodied in the form of a software product in essence or in the form of a software product stored in a storage medium, including a plurality of instructions.
  • a computer device (which may be a personal computer, server, or network device, etc.) is caused to perform all or part of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read only memory (ROM), a magnetic disk, or an optical disk.
  • embodiments of the invention are not limited to any specific combination of hardware and software.
  • an embodiment of the present invention further provides a computer storage medium, wherein a computer program is configured, and the computer program is configured to execute a data scheduling method according to an embodiment of the present invention.

Landscapes

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

Abstract

本发明公开了一种动态配置方法、终端设备、网络设备及计算机存储介质，其中方法包括：终端设备接收至少两个调制与编码策略MCS表格的配置信息，所述配置信息用于确定所述至少两个MCS表格；所述终端设备接收网络侧发来的调度信息；所述终端设备基于所述调度信息、调度信息与MCS表格之间的对应关系，从所述至少两个MCS表格中确定目标MCS表格。

Description

动态配置方法、终端设备、网络设备及计算机存储介质 技术领域
本发明涉及信息处理技术领域，尤其涉及一种动态配置方法、终端设备、网络设备及计算机存储介质。
背景技术
目前5G NR系统支持增强移动宽带(eMBB，Enhance Mobile Broadband)和高可靠通信(uRLLC)两种业务，两者的可靠性要求是不同的，所以，两者的MCS(Modulation and Coding Scheme，调制与编码策略)配置通常也是不同，且MCS配置的范围也是不同的。一些公司提出通过高层信令为URLLC和eMBB分别配置MCS表格，但URLLC和eMBB业务是动态触发的，上述工作机制无法适用业务传输需求。
发明内容
为解决上述技术问题，本发明实施例提供了一种动态配置方法、终端设备、网络设备及计算机存储介质。
本发明实施例提供一种动态配置方法，应用于终端设备，所述方法包括：
终端设备接收至少两个调制与编码策略MCS表格的配置信息，所述配置信息用于确定所述至少两个MCS表格；
所述终端设备接收网络侧发来的调度信息；
所述终端设备基于所述调度信息、调度信息与MCS表格之间的对应关系，从所述至少两个MCS表格中确定目标MCS表格。
本发明实施例提供一种动态配置方法，应用于网络设备，所述方法包括：
向终端设备发送至少两个调制与编码策略MCS表格的配置信息，所述配置信息用于确定所述至少两个MCS表格；
向所述终端设备发送调度信息；其中，所述调度信息与MCS表格之间具备对应关系。
本发明实施例提供一种终端设备，所述终端设备包括：
第一通信单元，接收至少两个调制与编码策略MCS表格的配置信息，所述配置信息用于确定所述至少两个MCS表格；接收网络侧发来的调度信息；
第一处理单元，基于所述调度信息、调度信息与MCS表格之间的对应关系，从所述至少两个MCS表格中确定目标MCS表格。
本发明实施例提供一种网络设备，所述网络设备包括：
第二通信单元，向终端设备发送至少两个调制与编码策略MCS表格的配置信息，所述配置信息用于确定所述至少两个MCS表格；向所述终端设备发送调度信息；其中，所述调度信息与MCS表格之间具备对应关系。
本发明实施例提供的一种终端设备，包括：处理器和用于存储能够在处理器上运行的计算机程序的存储器，
其中，所述处理器用于运行所述计算机程序时，执行前述方法的步骤。
本发明实施例提供的一种网络设备，包括：处理器和用于存储能够在处理器上运行的计算机程序的存储器，
其中，所述处理器用于运行所述计算机程序时，执行前述方法的步骤。
本发明实施例提供的一种计算机存储介质，所述计算机存储介质存储有计算机可执行指令，所述计算机可执行指令被执行时实现前述方法步骤。
本发明实施例的技术方案，就能够预先获取至少两个MCS表格配置信息，然后根据调度信息选取目标MCS表格，进而采用目标MCS表格进行后续处理。从而，能够实现动态配置MCS表格，适应URLLC，eMBB业务的动态调度；并且，通过采用隐性指示的方法，降低物理层信令开销，提高物理层信令的可靠性。
附图说明
图1为本发明实施例提供的一种动态配置方法流程示意图1；
图2为本发明实施例提供的一种动态配置方法流程示意图2；
图3为本发明实施例终端设备组成结构示意图；
图4为本发明实施例网络设备组成结构示意图；
图5为本发明实施例的一种硬件架构示意图。
具体实施方式
为了能够更加详尽地了解本发明实施例的特点与技术内容，下面结合附图对本发明实施例的实现进行详细阐述，所附附图仅供参考说明之用，并非用来限定本发明实施例。
实施例一、
本发明实施例提供一种动态配置方法，应用于终端设备，如图1所示，包括：
步骤101：终端设备接收至少两个调制与编码策略MCS表格的配置信息，所述配置信息用于确定所述至少两个MCS表格；
步骤102：所述终端设备接收网络侧发来的调度信息；
步骤103：所述终端设备基于所述调度信息、调度信息与MCS表格之间的对应关系，从所述至少两个MCS表格中确定目标MCS表格。
也就是说，本实施例提供的方案中，终端接收调度信息，然后终端基于调度信息，判定MCS表格。
并且，终端设备从网络侧接收至少2个MCS表格配置信息。
所述至少两个调制与编码策略MCS表格至少包括有：第一MCS表格、以及第二MCS表格。
其中，所述第一MCS表格为第二MCS表格的部分内容；
和/或，所述第一MCS表格由第二MCS表格中奇数或偶数索引值所对应的元素组成。
所述第一MCS表格为第二MCS表格的部分内容，为：
所述第一MCS表格为第二MCS表格的前半部分内容。
当然，还可以理解的是，第一MCS表格还可以为第二MCS表格的后半部分内容，还可以为中间部分内容，本实施例中不进行穷举。并且，其中前半部分内容可以为第二MCS表格中所包含的全部条目中的半数条目，具体为前一半条目；相应的，后半部分内容以及中间部分内容以此类推不进行赘述。
所述调度信息，包括以下至少一类：控制资源集合；搜索空间集合；搜索空间；时域资源指示类型；时域资源长度；MCS表格指示信息；下行控制信息(DCI，Downlink Control Information)格式；聚合等级(Aggregation level)；业务指示；循环冗余校验(CRC)；无线网络临时标识(RNTI，Radio Network Tempory Identity)。
其中，控制资源集合可以为CORESET(Control Resource Set)；搜索空间集合可以为Search space set；搜索空间可以为Search space；时域资源指示类型，比如，可以为Type A or Type B；时域资源长度，可以为Short TTI or long TTI；MCS表格指示信息。
所述方法还包括：
基于协议确定调度信息与MCS表格之间的对应关系，或者，基于高层配置确定调度信息与MCS表格之间的对应关系。具体的，MCS表格和上述信息之间的关系由协议约定，或高层配置。
所述方法还包括：为每一类调度信息中的每一种调度信息配置对应的MCS表格。
相应的，所述基于所述调度信息与MCS表格之间的对应关系，确定目标MCS表格，包括：
确定接收到的调度信息所对应的种类；
基于所述调度信息所对应的种类、以及所述调度信息所对应的种类与MCS表格之间的对应关系，从所述至少两个MCS表格中确定目标MCS表格。
其中，调度信息所对应的种类，可以具体包括有，调度信息为控制资源集合；搜索空间集合；搜索空间；时域资源指示类型；时域资源长度；MCS表格指示信息中的一类。并且，在每一类调度信息中，还会存在不同种的调度信息，比如，控制资源集合A、控制资源集合B、等等；还可以有搜索空间集合A、搜索空间集合B等等，这些均可以理解为不同类调度信息中的不同种调度信息，总得来说，可以理解为不同种类的调度信息。
下面分别基于前述不同种类的调度信息与MCS表格的对应关系进行说明：
第一种、基于CORESET(控制资源集合)配置确定MCS(调制与编码策略)表格：
可以通过协议约定、或高层配置对应不同的控制资源集合的调度信息对应的MCS表格；其中，不同的控制资源集合的调度信息可以理解为不同种类的调度信息。例如CORESET 1的调度信息与MCS表格1之间具有对应关系，CORESET 2的调度信息与MCS表格2之间具有对应关系。
举例说明如下，前述步骤102中，所述终端设备接收网络侧发来的调度信息，可以为：
终端设备在CORESET 1收到调度信息。可以理解为，该调度信息所对应的种类为CORESET 1。
前述步骤103中，所述终端设备基于所述调度信息、调度信息与MCS表格之间的对应关系，从所述至少两个MCS表格中确定目标MCS表格，可以包括：
基于所述调度信息所对应的种类为CORESET1，以及CORESET1的调度信息与MCS表格之间的对应关系，从MCS表格1以及MCS表格2中，确定目标MCS表格为MCS表格1。
如果，前述步骤102为：终端设备在CORESET 2收到的调度信息。可以理解为，该调度信息所对应的种类为CORESET 2。
相应的，步骤103具体为：基于所述调度信息所对应的种类为CORESET2，基于CORESET2的调度信息与MCS表格之间的对应关系，确定目标MCS表格为MCS表格2。
这种方式中，可以通过在CORESET中设置对应的MCS表格，或者，通过协议约定、或高层配置MCS表格中设置其对应的CORESET的种类。配置可以通过高层/物理层信令指示，也可以通过协议约定确定。
另外，没有配置MCS表格的CORESET对应默认的MCS表格。默认的MCS表格由协议约定，或信令通知。典型地，高密度的CORESET配置较小的MCS表格，或者低阶的MCS表格。
也就是说，当接收到调度信息，该调度信息对应没有配置MCS表格的CORESET的情况下，可以采用默认MCS表格进行后续处理。
其中，默认MCS表格可以为多个MCS表格中的一个，比如，当前配置有MCS1、MCS2这两个表格，那么可以通过网络侧指定、或者通过协议规定，默认MCS表格为MCS1(或者MCS2)。
还需要理解的是，这种配置方式可以适用于后续描述的多种场景，后续不再进行赘述。
第二种、基于Search Space set(搜索空间集合)/Search Space(搜索空间)配置确定MCS表格。
这种方式中，网络侧通过协议约定、或高层配置对应不同的Search Space Set/Search Space的调度信息对应的MCS表格；其中，不同的Search Space Set/Search Space的调度信息可以理解为不同种类的调度信息。例如Search Space Set/Search Space 1的调度信息与MCS表格1之间具有对应关系，Search Space Set/Search Space 2的调度信息与MCS表格2之间具有对应关系。
举例说明如下，前述步骤102中，所述终端设备接收网络侧发来的调度信息，可以为：
终端设备在Search Space Set/Search Space 1收到的调度信息。可以理解为，该调度信息所对应的种类为Search Space Set/Search Space 1。
前述步骤103中，所述终端设备基于所述调度信息、调度信息与MCS表格之间的对应关系，从所述至少两个MCS表格中确定目标MCS表格，可以包括：
基于所述调度信息所对应的种类为Search Space Set/Search Space 1、以及Search Space Set/Search Space 1的调度信息与MCS表格之间的对应关系，可以确定目标MCS表格为MCS表格1。
如果，前述步骤102为：终端在Search Space Set/Search Space 2收到的调度信息。可以理解为，该调度信息所对应的种类为CORESET 2。
相应的，步骤103具体为：基于所述调度信息所对应的种类为Search Space Set/Search Space 2、以及Search Space Set/Search Space 2的调度信息与MCS表格之间的对应关系，可以确定目标MCS表格为MCS表格2。
典型地，一种配置方式可以为：高聚合等级的Search space set/Search space配置较小的MCS表格，或者低阶的MCS表格。
第三种、基于时域资源指示类型确定MCS表格：
通过协议约定、或高层配置对应于不同的时域资源指类型(比如，时域资源TypeA or时域资源TypeB)的调度信息对应的MCS表格；其中，不同的时域资源指类型的调度信息可以理解为不同种类的调度信息。例如Type A的调度信息与MCS表格1之间具有对应关系，Type B的调度信息与MCS表格2之间具有对应关系。
举例说明如下，前述步骤102中，所述终端设备接收网络侧发来的调度信息，可以为：
终端设备在Type A收到的调度信息；可以理解为，该调度信息所对应的种类为Type A。
前述步骤103中，所述终端设备基于所述调度信息、调度信息与MCS表格之间的对应关系，从所述至少两个MCS表格中确定目标MCS表格，可以包括：
基于所述调度信息所对应的种类为Type A、以及Search Space Set/Search Space 1的调度信息与MCS表格之间的对应关系，可以确定目标MCS表格为MCS表格1。
如果，前述步骤102为：终端在Type B收到的调度信息。可以理解为，该调度信息所对应的种类为Type B。
相应的，步骤103具体为：基于所述调度信息所对应的种类为Type B、以及Type B的调度信息与MCS表格之间的对应关系，可以确定目标MCS表格为MCS表格2。
也就是，当收到调度信息，判断该调度信息对应TypeA的时候，采用MCS表格1.
典型地，Type A采用常规MCS表格，TypeB采用覆盖超低码率的MCS表格，或者较小的MCS表格
第四种、基于时域资源长度确定MCS表格：
通过协议约定、或高层配置对应不同的时域资源长度/时域长度范围的调度信息对应的MCS表格；其中，不同的时域资源长度/时域长度范围的调度信息可以理解为不同种类的调度信息。例如时域资源长度/时域长度范围1的调度信息与MCS表格1之间具有对应关系，时域资源长度/时域长度范围2的调度信息与MCS表格2之间具有对应关系。
举例说明如下，前述步骤102中，所述终端设备接收网络侧发来的调度信息，可以为：
终端设备收到调度信息的时域资源长度/时域长度在范围1内。可以理解为调度信息所对应的种类为时域资源长度/时域长度范围1。
前述步骤103中，所述终端设备基于所述调度信息、调度信息与MCS表格之间的对应关系，从所述至少两个MCS表格中确定目标MCS表格，可以包括：
基于所述调度信息所对应的种类为时域资源长度/时域长度范围1，则时域资源长度/时域长度范围1的调度信息所对应的MCS表格1为目标MCS表格；按照MCS表格1解析MCS等级。
如果，前述步骤102为：终端设备收到调度信息的时域资源长度/时域长度在范围2内。可以理解为调度信息所对应的种类为时域资源长度/时域长度范围1。
相应的，步骤103具体为：基于所述调度信息所对应的种类为时域资源长度/时域长度范围2，则时域资源长度/时域长度范围2的调度信息所对应的MCS表格2为目标MCS表格；则按照MCS表格2解析MCS等级。
第五种、基于DCI格式确定MCS表格，或者可以具体理解为DCI格式长度来确定MCS表格：
可以通过协议约定、或高层配置对应不同的DCI格式的调度信息对应的MCS表格；其中，不同的DCI格式的调度信息可以理解为不同种类的调度信息。例如压缩DCI格式的调度信息与MCS表格1具有对应关系，常规DCI格式对应MCS表格2具有对应关系。
举例说明如下，前述步骤102中，所述终端设备接收网络侧发来的调度信息，可以为：
终端在压缩DCI格式收到的调度信息。可以理解为，该调度信息所对应的种类为压缩DCI格式。
前述步骤103中，所述终端设备基于所述调度信息、调度信息与MCS表格之间的 对应关系，从所述至少两个MCS表格中确定目标MCS表格，可以包括：
基于所述调度信息所对应的种类为压缩DCI格式，以及压缩DCI格式的调度信息与MCS表格之间的对应关系，从MCS表格1以及MCS表格2中，确定目标MCS表格为MCS表格1。
如果，前述步骤102为：终端设备在常规DCI格式收到的调度信息。可以理解为，该调度信息所对应的种类为常规DCI格式。
相应的，步骤103具体为：基于所述调度信息所对应的种类为常规DCI格式，基于常规DCI格式的调度信息与MCS表格之间的对应关系，确定目标MCS表格为MCS表格2。
典型地，压缩DCI格式可以对应较小的MCS表格，常规DCI格式可以对应较大的MCS表格。
第六种、基于aggregation level(聚合等级)确定MCS表格：
通过协议约定、或高层配置对应不同的Aggregation level的调度信息对应的MCS表格；其中，不同的聚合等级的调度信息可以理解为不同种类的调度信息。例如低聚合等级的调度信息与MCS表格1具有对应关系,高聚合等级的调度信息与MCS表格2之间具有对应关系。
举例说明如下，前述步骤102中，所述终端设备接收网络侧发来的调度信息，可以为：
终端设备在采用低聚合等级的下行控制信道收到的调度信息。可以理解为，该调度信息所对应的种类为低聚合等级。
前述步骤103中，所述终端设备基于所述调度信息、调度信息与MCS表格之间的对应关系，从所述至少两个MCS表格中确定目标MCS表格，可以包括：
基于所述调度信息所对应的种类为低聚合等级、以及低聚合等级的调度信息与MCS表格之间的对应关系，可以确定目标MCS表格为MCS表格1。
如果，前述步骤102为：终端在采用高聚合等级的下行控制信道收到的调度信息。可以理解为，该调度信息所对应的种类为高聚合等级。
相应的，步骤103具体为：基于所述调度信息所对应的种类为高聚合等级、以及高聚合等级的调度信息与MCS表格之间的对应关系，可以确定目标MCS表格为MCS表格2。
典型地，低聚合等级配置包含高频谱效率的MCS表格，高聚合等级配置包含低频谱效率的MCS表格。
低聚合等级和高聚合等级的划分，可以是基站配置，或协议约定。一类聚合等级可以包含一个或多个聚合等级。典型地，聚合等级1，2，4对应包含高频谱效率的MCS表格，聚合等级8，16对应包含低频普效率的MCS表格。当然还可以存在其他的划分方式，本实施例中不进行穷举。
第七种、基于业务指示确定MCS表格：
通过协议约定、或高层配置对应不同的业务指示对应的调度信息与MCS表格之间的对应关系，其中，不同的业务指示对应的调度信息可以理解为不同种类的调度信息。例如URLLC的调度信息与MCS表格1具有对应关系，eMBB的调度信息与MCS表格2具有对应关系。
举例说明如下，前述步骤102中，所述终端设备接收网络侧发来的调度信息，可以为：
终端收到的调度信息为用于调度URLLC的下行控制信息；可以理解为，该调度信 息所对应的种类为URLLC。
前述步骤103中，所述终端设备基于所述调度信息、调度信息与MCS表格之间的对应关系，从所述至少两个MCS表格中确定目标MCS表格，可以包括：
基于所述调度信息所对应的种类为URLLC、以及URLLC的调度信息与MCS表格之间的对应关系，可以确定目标MCS表格为MCS表格1。
如果，前述步骤102为：终端收到的调度信息为用于调度eMBB的下行控制信息；可以理解为，该调度信息所对应的种类为eMBB。
相应的，步骤103具体为：基于所述调度信息所对应的种类为eMBB、以及eMBB的调度信息与MCS表格之间的对应关系，可以确定目标MCS表格为MCS表格2。
第八种、基于控制信道CRC确定MCS表格：
通过协议约定、或高层配置对应于不同的控制信道CRC的调度信息对应的MCS表格；其中，不同的控制信道CRC的调度信息可以理解为不同种类的调度信息。例如控制信道CRC类型1的调度信息与MCS表格1具有对应关系,控制信道CRC类型2的调度信息与MCS表格2具有对应关系。
举例说明如下，前述步骤102中，所述终端设备接收网络侧发来的调度信息，可以为：
终端收到的调度信息为采用控制信道CRC类型1的下行控制信息；可以理解为，该调度信息所对应的种类为控制信道CRC类型1。
前述步骤103中，所述终端设备基于所述调度信息、调度信息与MCS表格之间的对应关系，从所述至少两个MCS表格中确定目标MCS表格，可以包括：
基于所述调度信息所对应的种类为控制信道CRC类型1、以及控制信道CRC类型1的调度信息与MCS表格之间的对应关系，可以确定目标MCS表格为MCS表格1。
前述步骤102中，所述终端设备接收网络侧发来的调度信息，可以为：
终端收到的调度信息为采用控制信道CRC类型2的下行控制信息；可以理解为，该调度信息所对应的种类为控制信道CRC类型2。
前述步骤103中，所述终端设备基于所述调度信息、调度信息与MCS表格之间的对应关系，从所述至少两个MCS表格中确定目标MCS表格，可以包括：
基于所述调度信息所对应的种类为控制信道CRC类型2、以及控制信道CRC类型2的调度信息与MCS表格之间的对应关系，可以确定目标MCS表格为MCS表格2。
典型地，控制信道CRC类型可以通过CRC长度，和/或CRC生成方式区别。
例如，控制信道CRC类型1用于URLLC业务调度，为其配置用于URLLC的MCS表格；控制信道CRC类型2用于eMBB业务调度，为其配置用于eMBB的MCS表格。
第九种、基于控制信道RNTI确定MCS表格：
通过协议约定、或高层配置对应于不同的控制信道RNTI的调度信息的MCS表格；其中，对应于不同的控制信道RNTI的调度信息可以理解为不同种类的调度信息。例如控制信道RNTI类型1的调度信息与MCS表格1具有对应关系,控制信道RNTI类型2的调度信息与MCS表格2具有对应关系。
举例说明如下，前述步骤102中，所述终端设备接收网络侧发来的调度信息，可以为：
终端收到的调度信息为采用控制信道RNTI类型1加扰的下行控制信息；可以理解为，该调度信息所对应的种类为控制信道RNTI类型1。
前述步骤103中，所述终端设备基于所述调度信息、调度信息与MCS表格之间的对应关系，从所述至少两个MCS表格中确定目标MCS表格，可以包括：
基于所述调度信息所对应的种类为控制信道RNTI类型1、以及控制信道RNTI类型1的调度信息与MCS表格之间的对应关系，可以确定目标MCS表格为MCS表格1。
前述步骤102中，所述终端设备接收网络侧发来的调度信息，可以为：
终端收到的调度信息为采用控制信道RNTI类型2加扰的下行控制信息；可以理解为，该调度信息所对应的种类为控制信道RNTI类型2。
前述步骤103中，所述终端设备基于所述调度信息、调度信息与MCS表格之间的对应关系，从所述至少两个MCS表格中确定目标MCS表格，可以包括：
基于所述调度信息所对应的种类为控制信道RNTI类型2、以及控制信道RNTI类型2的调度信息与MCS表格之间的对应关系，可以确定目标MCS表格为MCS表格1。
典型地，控制信道RNTI类型可以RNTI取值区别。
例如，控制信道RNTI类型1用于URLLC业务调度，为其配置用于URLLC的MCS表格；控制信道RNTI类型2用于eMBB业务调度，为其配置用于eMBB的MCS表格。
可见，通过采用上述方案，就能够预先获取至少两个MCS表格配置信息，然后根据调度信息选取目标MCS表格，进而采用目标MCS表格进行后续处理。从而，能够实现动态配置MCS表格，适应URLLC，eMBB业务的动态调度；并且，通过采用隐性指示的方法，降低物理层信令开销，提高物理层信令的可靠性。
实施例二、
本发明实施例提供一种动态配置方法，应用于网络设备，如图2所示，所述方法包括：
步骤201：向终端设备发送至少两个调制与编码策略MCS表格的配置信息，所述配置信息用于确定所述至少两个MCS表格；
步骤202：向所述终端设备发送调度信息；其中，所述调度信息与MCS表格之间具备对应关系。
也就是说，本实施例提供的方案中，终端接收调度信息，然后终端基于调度信息，判定MCS表格。
并且，终端设备从网络侧接收至少2个MCS表格配置信息。
所述至少两个调制与编码策略MCS表格至少包括有：第一MCS表格、以及第二MCS表格。
其中，所述第一MCS表格为第二MCS表格的部分内容；
和/或，所述第一MCS表格由第二MCS表格中奇数或偶数索引值所对应的元素组成。
所述第一MCS表格为第二MCS表格的部分内容，为：
所述第一MCS表格为第二MCS表格的前半部分内容。
当然，还可以理解的是，第一MCS表格还可以为第二MCS表格的后半部分内容，还可以为中间部分内容，本实施例中不进行穷举。并且，其中前半部分内容可以为第二MCS表格中所包含的全部条目中的半数条目，具体为前一半条目；相应的，后半部分内容以及中间部分内容以此类推不进行赘述。
所述调度信息，包括以下至少一类：控制资源集合；搜索空间集合；搜索空间；时域资源指示类型；时域资源长度；MCS表格指示信息；DCI格式；聚合等级(Aggregation level)；业务指示；循环冗余校验(CRC)；无线网络临时标识(RNTI，Radio Network Tempory Identity)。
其中，CORESET(Control Resource Set)控制资源集合；Search space set(搜索空间集 合)；Search space(搜索空间)；时域资源指示类型(Type A or Type B)；时域资源长度(Short TTI or long TTI)；MCS表格指示信息。
所述方法还包括：
基于协议确定调度信息与MCS表格之间的对应关系，或者，基于高层配置确定调度信息与MCS表格之间的对应关系。具体的，MCS表格和上述信息之间的关系由协议约定，或高层配置。
所述方法还包括：为每一类调度信息中的每一种调度信息配置对应的MCS表格。
下面分别基于前述不同种类的调度信息如何进行MCS表格的对应进行具体说明：
第一种、基于CORESET(控制资源集合)配置确定MCS(调制与编码策略)表格。
可以通过协议约定、或高层配置对应不同的控制资源集合的调度信息对应的MCS表格；其中，不同的控制资源集合的调度信息可以理解为不同种类的调度信息。例如CORESET 1的调度信息与MCS表格1之间具有对应关系，CORESET 2的调度信息与MCS表格2之间具有对应关系。
相应的，终端在CORESET 1收到的调度信息，可以理解为，该调度信息所对应的种类为CORESET 1；终端基于所述调度信息所对应的种类为CORESET1，以及CORESET1的调度信息与MCS表格之间的对应关系，从MCS表格1以及MCS表格2中，确定目标MCS表格为MCS表格1。终端设备在CORESET 2收到的调度信息。可以理解为，该调度信息所对应的种类为CORESET 2。相应的，基于所述调度信息所对应的种类为CORESET2，基于CORESET2的调度信息与MCS表格之间的对应关系，确定目标MCS表格为MCS表格2。
这种方式中，可以通过在CORESET中设置对应的MCS表格，或者，通过协议约定、或高层配置MCS表格中设置其对应的CORESET的种类。配置可以通过高层/物理层信令指示，也可以通过协议约定确定。
另外，没有配置MCS表格的CORESET对应默认的MCS表格。默认的MCS表格由协议约定，或信令通知。典型地，高密度的CORESET配置较小的MCS表格，或者低阶的MCS表格。
也就是说，当接收到调度信息，对于没有配置MCS表格的CORESET的情况下，可以采用默认MCS表格进行后续处理。
其中，默认MCS表格可以为多个MCS表格中的一个，比如，当前配置有MCS1、MCS2这两个表格，那么可以通过网络侧指定、或者通过协议规定，默认MCS表格为MCS1(或者MCS2)。
还需要理解的是，这种配置方式可以适用于后续描述的多种场景，后续不再进行赘述。
第二种、基于Search Space set(搜索空间集合)/Search Space(搜索空间)配置确定MCS表格。
这种方式中，网络侧通过协议约定、或高层配置对应不同的Search Space Set/Search Space的调度信息对应的MCS表格；其中，不同的Search Space Set/Search Space的调度信息可以理解为不同种类的调度信息。例如Search Space Set/Search Space 1的调度信息与MCS表格1之间具有对应关系，Search Space Set/Search Space 2的调度信息与MCS表格2之间具有对应关系。
相应的，终端设备在Search Space Set/Search Space 1收到的调度信息，基于所述调度信息所对应的种类为Search Space Set/Search Space 1、以及Search Space Set/Search Space 1的调度信息与MCS表格之间的对应关系，可以确定目标MCS表格为MCS表格 1。终端在Search Space Set/Search Space 2收到的调度信息，基于所述调度信息所对应的种类为Search Space Set/Search Space 2、以及Search Space Set/Search Space 2的调度信息与MCS表格之间的对应关系，可以确定目标MCS表格为MCS表格2。
典型地，高聚合等级的Search space set/Search space配置较小的MCS表格，或者低阶的MCS表格。
第三种、基于时域资源指示类型确定MCS表格：
通过协议约定、或高层配置对应于不同的时域资源指类型(比如，时域资源TypeA or时域资源TypeB)的调度信息对应的MCS表格；其中，不同的时域资源指类型的调度信息可以理解为不同种类的调度信息。例如Type A的调度信息与MCS表格1之间具有对应关系，Type B的调度信息与MCS表格2之间具有对应关系。
相应的，终端设备在Type A收到的调度信息；可以理解为，该调度信息所对应的种类为Type A，基于所述调度信息所对应的种类为Type A、以及Search Space Set/Search Space 1的调度信息与MCS表格之间的对应关系，可以确定目标MCS表格为MCS表格1。终端在Type B收到的调度信息。可以理解为，该调度信息所对应的种类为Type B，基于所述调度信息所对应的种类为Type B、以及Type B的调度信息与MCS表格之间的对应关系，可以确定目标MCS表格为MCS表格2。也就是，当收到调度信息，判断该调度信息对应TypeA的时候，采用MCS表格1.
典型地，Type A采用常规MCS表格，TypeB采用覆盖超低码率的MCS表格，或者较小的MCS表格
第四种、基于时域资源长度确定MCS表格：
通过协议约定、或高层配置对应不同的时域资源长度/时域长度范围的调度信息对应的MCS表格；其中，不同的时域资源长度/时域长度范围的调度信息可以理解为不同种类的调度信息。例如时域资源长度/时域长度范围1的调度信息与MCS表格1之间具有对应关系，时域资源长度/时域长度范围2的调度信息与MCS表格2之间具有对应关系。
相应的，终端设备收到调度信息的时域资源长度/时域长度在范围1内。可以理解为调度信息所对应的种类为时域资源长度/时域长度范围1。基于所述调度信息所对应的种类为时域资源长度/时域长度范围1，则时域资源长度/时域长度范围1的调度信息所对应的MCS表格1为目标MCS表格；按照MCS表格1解析MCS等级。
终端设备收到调度信息的时域资源长度/时域长度在范围2内。可以理解为调度信息所对应的种类为时域资源长度/时域长度范围1。基于所述调度信息所对应的种类为时域资源长度/时域长度范围2，则时域资源长度/时域长度范围2的调度信息所对应的MCS表格2为目标MCS表格；则按照MCS表格2解析MCS等级。
第五种、基于DCI格式确定MCS表格，或者可以具体理解为DCI格式长度来确定MCS表格：
可以通过协议约定、或高层配置对应不同的DCI格式的调度信息对应的MCS表格；其中，不同的DCI格式的调度信息可以理解为不同种类的调度信息。例如压缩DCI格式的调度信息与MCS表格1具有对应关系，常规DCI格式对应MCS表格2具有对应关系。
终端在压缩DCI格式收到的调度信息。可以理解为，该调度信息所对应的种类为压缩DCI格式。基于所述调度信息所对应的种类为压缩DCI格式，以及压缩DCI格式的调度信息与MCS表格之间的对应关系，从MCS表格1以及MCS表格2中，确定目标MCS表格为MCS表格1。
如果，终端设备在常规DCI格式收到的调度信息。可以理解为，该调度信息所对应 的种类为常规DCI格式。相应的，基于所述调度信息所对应的种类为常规DCI格式，基于常规DCI格式的调度信息与MCS表格之间的对应关系，确定目标MCS表格为MCS表格2。
典型地，压缩DCI格式可以对应较小的MCS表格，常规DCI格式可以对应较大的MCS表格。
第六种、基于aggregation level(聚合等级)确定MCS表格：
通过协议约定、或高层配置对应不同的Aggregation level的调度信息对应的MCS表格；其中，不同的聚合等级的调度信息可以理解为不同种类的调度信息。例如低聚合等级的调度信息与MCS表格1具有对应关系,高聚合等级的调度信息与MCS表格2之间具有对应关系。
终端设备在采用低聚合等级的下行控制信道收到的调度信息。可以理解为，该调度信息所对应的种类为低聚合等级。基于所述调度信息所对应的种类为低聚合等级、以及低聚合等级的调度信息与MCS表格之间的对应关系，可以确定目标MCS表格为MCS表格1。
如果，终端在采用高聚合等级的下行控制信道收到的调度信息。可以理解为，该调度信息所对应的种类为高聚合等级。基于所述调度信息所对应的种类为高聚合等级、以及高聚合等级的调度信息与MCS表格之间的对应关系，可以确定目标MCS表格为MCS表格2。
典型地，低聚合等级配置包含高频谱效率的MCS表格，高聚合等级配置包含低频谱效率的MCS表格。
低聚合等级和高聚合等级的划分，可以是基站配置，或协议约定。一类聚合等级可以包含一个或多个聚合等级。典型地，聚合等级1，2，4对应包含高频谱效率的MCS表格，聚合等级8，16对应包含低频普效率的MCS表格。当然还可以存在其他的划分方式，本实施例中不进行穷举。
第七种、基于业务指示确定MCS表格：
通过协议约定、或高层配置对应不同的业务指示对应的调度信息与MCS表格之间的对应关系，其中，不同的业务指示对应的调度信息可以理解为不同种类的调度信息。例如URLLC的调度信息与MCS表格1具有对应关系，eMBB的调度信息与MCS表格2具有对应关系。
终端收到的调度信息为用于调度URLLC的下行控制信息；可以理解为，该调度信息所对应的种类为URLLC。基于所述调度信息所对应的种类为URLLC、以及URLLC的调度信息与MCS表格之间的对应关系，可以确定目标MCS表格为MCS表格1。
如果，终端收到的调度信息为用于调度eMBB的下行控制信息；可以理解为，该调度信息所对应的种类为eMBB。基于所述调度信息所对应的种类为eMBB、以及eMBB的调度信息与MCS表格之间的对应关系，可以确定目标MCS表格为MCS表格2。
第八种、基于控制信道CRC确定MCS表格：
通过协议约定、或高层配置对应于不同的控制信道CRC的调度信息对应的MCS表格；其中，不同的控制信道CRC的调度信息可以理解为不同种类的调度信息。例如控制信道CRC类型1的调度信息与MCS表格1具有对应关系,控制信道CRC类型2的调度信息与MCS表格2具有对应关系。
终端收到的调度信息为采用控制信道CRC类型1的下行控制信息；可以理解为，该调度信息所对应的种类为控制信道CRC类型1。基于所述调度信息所对应的种类为控制信道CRC类型1、以及控制信道CRC类型1的调度信息与MCS表格之间的对应关 系，可以确定目标MCS表格为MCS表格1。
终端收到的调度信息为采用控制信道CRC类型2的下行控制信息；可以理解为，该调度信息所对应的种类为控制信道CRC类型2。基于所述调度信息所对应的种类为控制信道CRC类型2、以及控制信道CRC类型2的调度信息与MCS表格之间的对应关系，可以确定目标MCS表格为MCS表格2。
典型地，控制信道CRC类型可以通过CRC长度，和/或CRC生成方式区别。
例如，控制信道CRC类型1用于URLLC业务调度，为其配置用于URLLC的MCS表格；控制信道CRC类型2用于eMBB业务调度，为其配置用于eMBB的MCS表格。
第九种、基于控制信道RNTI确定MCS表格：
通过协议约定、或高层配置对应于不同的控制信道RNTI的调度信息的MCS表格；其中，对应于不同的控制信道RNTI的调度信息可以理解为不同种类的调度信息。例如控制信道RNTI类型1的调度信息与MCS表格1具有对应关系,控制信道RNTI类型2的调度信息与MCS表格2具有对应关系。
终端收到的调度信息为采用控制信道RNTI类型1加扰的下行控制信息；可以理解为，该调度信息所对应的种类为控制信道RNTI类型1。基于所述调度信息所对应的种类为控制信道RNTI类型1、以及控制信道RNTI类型1的调度信息与MCS表格之间的对应关系，可以确定目标MCS表格为MCS表格1。
终端收到的调度信息为采用控制信道RNTI类型2加扰的下行控制信息；可以理解为，该调度信息所对应的种类为控制信道RNTI类型2。基于所述调度信息所对应的种类为控制信道RNTI类型2、以及控制信道RNTI类型2的调度信息与MCS表格之间的对应关系，可以确定目标MCS表格为MCS表格1。
典型地，控制信道RNTI类型可以RNTI取值区别。
例如，控制信道RNTI类型1用于URLLC业务调度，为其配置用于URLLC的MCS表格；控制信道RNTI类型2用于eMBB业务调度，为其配置用于eMBB的MCS表格。
可见，通过采用上述方案，就能够预先获取至少两个MCS表格配置信息，然后根据调度信息选取目标MCS表格，进而采用目标MCS表格进行后续处理。从而，能够实现动态配置MCS表格，适应URLLC，eMBB业务的动态调度；并且，通过采用隐性指示的方法，降低物理层信令开销，提高物理层信令的可靠性。
实施例三、
本发明实施例提供一种终端设备，如图3所示，包括：
第一通信单元31，接收至少两个调制与编码策略MCS表格的配置信息，所述配置信息用于确定所述至少两个MCS表格；接收网络侧发来的调度信息；
第一处理单元32，基于所述调度信息、调度信息与MCS表格之间的对应关系，从所述至少两个MCS表格中确定目标MCS表格。
也就是说，本实施例提供的方案中，终端接收调度信息，然后终端基于调度信息，判定MCS表格。
并且，终端设备从网络侧接收至少2个MCS表格配置信息。
所述至少两个调制与编码策略MCS表格至少包括有：第一MCS表格、以及第二MCS表格。
其中，所述第一MCS表格为第二MCS表格的部分内容；
和/或，所述第一MCS表格由第二MCS表格中奇数或偶数索引值所对应的元素组成。
所述第一MCS表格为第二MCS表格的部分内容，为：
所述第一MCS表格为第二MCS表格的前半部分内容。
当然，还可以理解的是，第一MCS表格还可以为第二MCS表格的后半部分内容，还可以为中间部分内容，本实施例中不进行穷举。并且，其中前半部分内容可以为第二MCS表格中所包含的全部条目中的半数条目，具体为前一半条目；相应的，后半部分内容以及中间部分内容以此类推不进行赘述。
所述调度信息，包括以下至少一类：控制资源集合；搜索空间集合；搜索空间；时域资源指示类型；时域资源长度；MCS表格指示信息；下行控制信息(DCI，Downlink Control Information)格式；聚合等级(Aggregation level)；业务指示；循环冗余校验(CRC)；无线网络临时标识(RNTI，Radio Network Tempory Identity)。
其中，控制资源集合可以为CORESET(Control Resource Set)；搜索空间集合可以为Search space set；搜索空间可以为Search space；时域资源指示类型，比如，可以为Type A or Type B；时域资源长度，可以为Short TTI or long TTI；MCS表格指示信息。
所述第一处理单元32，基于协议确定调度信息与MCS表格之间的对应关系，或者，基于高层配置确定调度信息与MCS表格之间的对应关系。具体的，MCS表格和上述信息之间的关系由协议约定，或高层配置。
所述第一处理单元32，为每一类调度信息中的每一种调度信息配置对应的MCS表格。
相应的，所述第一处理单元32，确定接收到的调度信息所对应的种类；
基于所述调度信息所对应的种类、以及所述调度信息所对应的种类与MCS表格之间的对应关系，从所述至少两个MCS表格中确定目标MCS表格。
其中，调度信息所对应的种类，可以具体包括有，调度信息为控制资源集合；搜索空间集合；搜索空间；时域资源指示类型；时域资源长度；MCS表格指示信息中的一类。并且，在每一类调度信息中，还会存在不同种的调度信息，比如，控制资源集合A、控制资源集合B、等等；还可以有搜索空间集合A、搜索空间集合B等等，这些均可以理解为不同类调度信息中的不同种调度信息，总得来说，可以理解为不同种类的调度信息。
下面分别基于前述不同种类的调度信息如何进行MCS表格的对应进行具体说明：
第一种、基于CORESET(控制资源集合)配置确定MCS(调制与编码策略)表格：
可以通过协议约定、或高层配置对应不同的控制资源集合的调度信息对应的MCS表格；其中，不同的控制资源集合的调度信息可以理解为不同种类的调度信息。例如CORESET 1的调度信息与MCS表格1之间具有对应关系，CORESET 2的调度信息与MCS表格2之间具有对应关系。
举例说明如下，在CORESET 1收到调度信息。可以理解为，该调度信息所对应的种类为CORESET 1。
第一处理单元32，基于所述调度信息所对应的种类为CORESET1，以及CORESET1的调度信息与MCS表格之间的对应关系，从MCS表格1以及MCS表格2中，确定目标MCS表格为MCS表格1。
如果，在CORESET 2收到的调度信息。可以理解为，该调度信息所对应的种类为CORESET 2。第一处理单元32，基于所述调度信息所对应的种类为CORESET2，基于CORESET2的调度信息与MCS表格之间的对应关系，确定目标MCS表格为MCS表格2。
这种方式中，可以通过在CORESET中设置对应的MCS表格，或者，通过协议约 定、或高层配置MCS表格中设置其对应的CORESET的种类。配置可以通过高层/物理层信令指示，也可以通过协议约定确定。
另外，没有配置MCS表格的CORESET对应默认的MCS表格。默认的MCS表格由协议约定，或信令通知。典型地，高密度的CORESET配置较小的MCS表格，或者低阶的MCS表格。
也就是说，当接收到调度信息，该调度信息对应没有配置MCS表格的CORESET的情况下，可以采用默认MCS表格进行后续处理。
其中，默认MCS表格可以为多个MCS表格中的一个，比如，当前配置有MCS1、MCS2这两个表格，那么可以通过网络侧指定、或者通过协议规定，默认MCS表格为MCS1(或者MCS2)。
还需要理解的是，这种配置方式可以适用于后续描述的多种场景，后续不再进行赘述。
第二种、基于Search Space set(搜索空间集合)/Search Space(搜索空间)配置确定MCS表格。
这种方式中，网络侧通过协议约定、或高层配置对应不同的Search Space Set/Search Space的调度信息对应的MCS表格；其中，不同的Search Space Set/Search Space的调度信息可以理解为不同种类的调度信息。例如Search Space Set/Search Space 1的调度信息与MCS表格1之间具有对应关系，Search Space Set/Search Space 2的调度信息与MCS表格2之间具有对应关系。
举例说明如下，在Search Space Set/Search Space 1收到的调度信息。可以理解为，该调度信息所对应的种类为Search Space Set/Search Space 1。第一处理单元32，基于所述调度信息所对应的种类为Search Space Set/Search Space 1、以及Search Space Set/Search Space 1的调度信息与MCS表格之间的对应关系，可以确定目标MCS表格为MCS表格1。
如果，第一通信单元在Search Space Set/Search Space 2收到的调度信息。可以理解为，该调度信息所对应的种类为CORESET 2。
相应的，第一处理单元32，基于所述调度信息所对应的种类为Search Space Set/Search Space 2、以及Search Space Set/Search Space 2的调度信息与MCS表格之间的对应关系，可以确定目标MCS表格为MCS表格2。
典型地，一种配置方式可以为：高聚合等级的Search space set/Search space配置较小的MCS表格，或者低阶的MCS表格。
第三种、基于时域资源指示类型确定MCS表格：
通过协议约定、或高层配置对应于不同的时域资源指类型(比如，时域资源TypeA or时域资源TypeB)的调度信息对应的MCS表格；其中，不同的时域资源指类型的调度信息可以理解为不同种类的调度信息。例如Type A的调度信息与MCS表格1之间具有对应关系，Type B的调度信息与MCS表格2之间具有对应关系。
举例说明如下，第一通信单元31在Type A收到的调度信息；可以理解为，该调度信息所对应的种类为Type A。
第一处理单元32，基于所述调度信息所对应的种类为Type A、以及Search Space Set/Search Space 1的调度信息与MCS表格之间的对应关系，可以确定目标MCS表格为MCS表格1。
如果，第一通信单元31在Type B收到的调度信息。可以理解为，该调度信息所对应的种类为Type B。
相应的，第一处理单元32，基于所述调度信息所对应的种类为Type B、以及Type B的调度信息与MCS表格之间的对应关系，可以确定目标MCS表格为MCS表格2。
也就是，当收到调度信息，判断该调度信息对应TypeA的时候，采用MCS表格1.
典型地，Type A采用常规MCS表格，TypeB采用覆盖超低码率的MCS表格，或者较小的MCS表格
第四种、基于时域资源长度确定MCS表格：
通过协议约定、或高层配置对应不同的时域资源长度/时域长度范围的调度信息对应的MCS表格；其中，不同的时域资源长度/时域长度范围的调度信息可以理解为不同种类的调度信息。例如时域资源长度/时域长度范围1的调度信息与MCS表格1之间具有对应关系，时域资源长度/时域长度范围2的调度信息与MCS表格2之间具有对应关系。
举例说明如下，第一通信单元31收到调度信息的时域资源长度/时域长度在范围1内。可以理解为调度信息所对应的种类为时域资源长度/时域长度范围1。
第一处理单元32，基于所述调度信息所对应的种类为时域资源长度/时域长度范围1，则时域资源长度/时域长度范围1的调度信息所对应的MCS表格1为目标MCS表格；按照MCS表格1解析MCS等级。
如果，第一通信单元31收到调度信息的时域资源长度/时域长度在范围2内。可以理解为调度信息所对应的种类为时域资源长度/时域长度范围1。
相应的，第一处理单元32，基于所述调度信息所对应的种类为时域资源长度/时域长度范围2，则时域资源长度/时域长度范围2的调度信息所对应的MCS表格2为目标MCS表格；则按照MCS表格2解析MCS等级。
第五种、基于DCI格式确定MCS表格，或者可以具体理解为DCI格式长度来确定MCS表格：
可以通过协议约定、或高层配置对应不同的DCI格式的调度信息对应的MCS表格；其中，不同的DCI格式的调度信息可以理解为不同种类的调度信息。例如压缩DCI格式的调度信息与MCS表格1具有对应关系，常规DCI格式对应MCS表格2具有对应关系。
举例说明如下，在压缩DCI格式收到的调度信息。可以理解为，该调度信息所对应的种类为压缩DCI格式。第一处理单元32，基于所述调度信息所对应的种类为压缩DCI格式，以及压缩DCI格式的调度信息与MCS表格之间的对应关系，从MCS表格1以及MCS表格2中，确定目标MCS表格为MCS表格1。
如果，在常规DCI格式收到的调度信息。可以理解为，该调度信息所对应的种类为常规DCI格式。
相应的，第一处理单元32，基于所述调度信息所对应的种类为常规DCI格式，基于常规DCI格式的调度信息与MCS表格之间的对应关系，确定目标MCS表格为MCS表格2。
典型地，压缩DCI格式可以对应较小的MCS表格，常规DCI格式可以对应较大的MCS表格。
第六种、基于aggregation level(聚合等级)确定MCS表格：
通过协议约定、或高层配置对应不同的Aggregation level的调度信息对应的MCS表格；其中，不同的聚合等级的调度信息可以理解为不同种类的调度信息。例如低聚合等级的调度信息与MCS表格1具有对应关系,高聚合等级的调度信息与MCS表格2之间具有对应关系。
举例说明如下，第一通信单元31在采用低聚合等级的下行控制信道收到的调度信 息。可以理解为，该调度信息所对应的种类为低聚合等级。
第一处理单元32，基于所述调度信息所对应的种类为低聚合等级、以及低聚合等级的调度信息与MCS表格之间的对应关系，可以确定目标MCS表格为MCS表格1。
如果，第一通信单元31在采用高聚合等级的下行控制信道收到的调度信息。可以理解为，该调度信息所对应的种类为高聚合等级。
相应的，第一处理单元32，基于所述调度信息所对应的种类为高聚合等级、以及高聚合等级的调度信息与MCS表格之间的对应关系，可以确定目标MCS表格为MCS表格2。
典型地，低聚合等级配置包含高频谱效率的MCS表格，高聚合等级配置包含低频谱效率的MCS表格。
低聚合等级和高聚合等级的划分，可以是基站配置，或协议约定。一类聚合等级可以包含一个或多个聚合等级。典型地，聚合等级1，2，4对应包含高频谱效率的MCS表格，聚合等级8，16对应包含低频普效率的MCS表格。当然还可以存在其他的划分方式，本实施例中不进行穷举。
第七种、基于业务指示确定MCS表格：
通过协议约定、或高层配置对应不同的业务指示对应的调度信息与MCS表格之间的对应关系，其中，不同的业务指示对应的调度信息可以理解为不同种类的调度信息。例如URLLC的调度信息与MCS表格1具有对应关系，eMBB的调度信息与MCS表格2具有对应关系。
举例说明如下，第一通信单元31收到的调度信息为用于调度URLLC的下行控制信息；可以理解为，该调度信息所对应的种类为URLLC。
第一处理单元32，基于所述调度信息所对应的种类为URLLC、以及URLLC的调度信息与MCS表格之间的对应关系，可以确定目标MCS表格为MCS表格1。
如果，第一通信单元31收到的调度信息为用于调度eMBB的下行控制信息；可以理解为，该调度信息所对应的种类为eMBB。
相应的，第一处理单元32，基于所述调度信息所对应的种类为eMBB、以及eMBB的调度信息与MCS表格之间的对应关系，可以确定目标MCS表格为MCS表格2。
第八种、基于控制信道CRC确定MCS表格：
通过协议约定、或高层配置对应于不同的控制信道CRC的调度信息对应的MCS表格；其中，不同的控制信道CRC的调度信息可以理解为不同种类的调度信息。例如控制信道CRC类型1的调度信息与MCS表格1具有对应关系,控制信道CRC类型2的调度信息与MCS表格2具有对应关系。
举例说明如下，第一通信单元31收到的调度信息为采用控制信道CRC类型1的下行控制信息；可以理解为，该调度信息所对应的种类为控制信道CRC类型1。
第一处理单元32，基于所述调度信息所对应的种类为控制信道CRC类型1、以及控制信道CRC类型1的调度信息与MCS表格之间的对应关系，可以确定目标MCS表格为MCS表格1。
如果，第一通信单元31收到的调度信息为采用控制信道CRC类型2的下行控制信息；可以理解为，该调度信息所对应的种类为控制信道CRC类型2。
第一处理单元32，基于所述调度信息所对应的种类为控制信道CRC类型2、以及控制信道CRC类型2的调度信息与MCS表格之间的对应关系，可以确定目标MCS表格为MCS表格2。
典型地，控制信道CRC类型可以通过CRC长度，和/或CRC生成方式区别。
例如，控制信道CRC类型1用于URLLC业务调度，为其配置用于URLLC的MCS表格；控制信道CRC类型2用于eMBB业务调度，为其配置用于eMBB的MCS表格。
第九种、基于控制信道RNTI确定MCS表格：
通过协议约定、或高层配置对应于不同的控制信道RNTI的调度信息的MCS表格；其中，对应于不同的控制信道RNTI的调度信息可以理解为不同种类的调度信息。例如控制信道RNTI类型1的调度信息与MCS表格1具有对应关系,控制信道RNTI类型2的调度信息与MCS表格2具有对应关系。
举例说明如下第一通信单元31收到的调度信息为采用控制信道RNTI类型1加扰的下行控制信息；可以理解为，该调度信息所对应的种类为控制信道RNTI类型1。
第一处理单元32，基于所述调度信息所对应的种类为控制信道RNTI类型1、以及控制信道RNTI类型1的调度信息与MCS表格之间的对应关系，可以确定目标MCS表格为MCS表格1。
如果第一通信单元31收到的调度信息为采用控制信道RNTI类型2加扰的下行控制信息；可以理解为，该调度信息所对应的种类为控制信道RNTI类型2。
第一处理单元32，基于所述调度信息所对应的种类为控制信道RNTI类型2、以及控制信道RNTI类型2的调度信息与MCS表格之间的对应关系，可以确定目标MCS表格为MCS表格1。
典型地，控制信道RNTI类型可以RNTI取值区别。
例如，控制信道RNTI类型1用于URLLC业务调度，为其配置用于URLLC的MCS表格；控制信道RNTI类型2用于eMBB业务调度，为其配置用于eMBB的MCS表格。
可见，通过采用上述方案，就能够预先获取至少两个MCS表格配置信息，然后根据调度信息选取目标MCS表格，进而采用目标MCS表格进行后续处理。从而，能够实现动态配置MCS表格，适应URLLC，eMBB业务的动态调度；并且，通过采用隐性指示的方法，降低物理层信令开销，提高物理层信令的可靠性。
实施例四、
本发明实施例提供一种网络设备，如图4所示，所述方法包括：
第二通信单元41，向终端设备发送至少两个调制与编码策略MCS表格的配置信息，所述配置信息用于确定所述至少两个MCS表格；向所述终端设备发送调度信息；其中，所述调度信息与MCS表格之间具备对应关系。
也就是说，本实施例提供的方案中，终端接收调度信息，然后终端基于调度信息，判定MCS表格。
并且，终端设备从网络侧接收至少2个MCS表格配置信息。
所述至少两个调制与编码策略MCS表格至少包括有：第一MCS表格、以及第二MCS表格。
其中，所述第一MCS表格为第二MCS表格的部分内容；
和/或，所述第一MCS表格由第二MCS表格中奇数或偶数索引值所对应的元素组成。
所述第一MCS表格为第二MCS表格的部分内容，为：
所述第一MCS表格为第二MCS表格的前半部分内容。
当然，还可以理解的是，第一MCS表格还可以为第二MCS表格的后半部分内容，还可以为中间部分内容，本实施例中不进行穷举。并且，其中前半部分内容可以为第二MCS表格中所包含的全部条目中的半数条目，具体为前一半条目；相应的，后半部分 内容以及中间部分内容以此类推不进行赘述。
所述调度信息，包括以下至少一类：控制资源集合；搜索空间集合；搜索空间；时域资源指示类型；时域资源长度；MCS表格指示信息；DCI格式；聚合等级(Aggregation level)；业务指示；循环冗余校验(CRC)；无线网络临时标识(RNTI，Radio Network Tempory Identity)。
其中，CORESET(Control Resource Set)控制资源集合；Search space set(搜索空间集合)；Search space(搜索空间)；时域资源指示类型(Type A or Type B)；时域资源长度(Short TTI or long TTI)；MCS表格指示信息。
所述网络设备还包括：
第二处理单元42，基于协议确定调度信息与MCS表格之间的对应关系，或者，基于高层配置确定调度信息与MCS表格之间的对应关系。具体的，MCS表格和上述信息之间的关系由协议约定，或高层配置。
所述第二处理单元42，为每一类调度信息中的每一种调度信息配置对应的MCS表格。
下面分别基于前述不同种类的调度信息如何进行MCS表格的对应进行具体说明：
第一种、基于CORESET(控制资源集合)配置确定MCS(调制与编码策略)表格。
可以通过协议约定、或高层配置对应不同的控制资源集合的调度信息对应的MCS表格；其中，不同的控制资源集合的调度信息可以理解为不同种类的调度信息。例如CORESET 1的调度信息与MCS表格1之间具有对应关系，CORESET 2的调度信息与MCS表格2之间具有对应关系。
这种方式中，可以通过在CORESET中设置对应的MCS表格，或者，通过协议约定、或高层配置MCS表格中设置其对应的CORESET的种类。配置可以通过高层/物理层信令指示，也可以通过协议约定确定。
另外，没有配置MCS表格的CORESET对应默认的MCS表格。默认的MCS表格由协议约定，或信令通知。典型地，高密度的CORESET配置较小的MCS表格，或者低阶的MCS表格。
也就是说，当接收到调度信息，对应没有配置MCS表格的CORESET的情况下，可以采用默认MCS表格进行后续处理。
其中，默认MCS表格可以为多个MCS表格中的一个，比如，当前配置有MCS1、MCS2这两个表格，那么可以通过网络侧指定、或者通过协议规定，默认MCS表格为MCS1(或者MCS2)。
还需要理解的是，这种配置方式可以适用于后续描述的多种场景，后续不再进行赘述。
第二种、基于Search Space set(搜索空间集合)/Search Space(搜索空间)配置确定MCS表格。
这种方式中，网络侧通过协议约定、或高层配置对应不同的Search Space Set/Search Space的调度信息对应的MCS表格；其中，不同的Search Space Set/Search Space的调度信息可以理解为不同种类的调度信息。例如Search Space Set/Search Space 1的调度信息与MCS表格1之间具有对应关系，Search Space Set/Search Space 2的调度信息与MCS表格2之间具有对应关系。
典型地，高聚合等级的Search space set/Search space配置较小的MCS表格，或者低阶的MCS表格。
第三种、基于时域资源指示类型确定MCS表格：
通过协议约定、或高层配置对应于不同的时域资源指类型(比如，时域资源TypeA or时域资源TypeB)的调度信息对应的MCS表格；其中，不同的时域资源指类型的调度信息可以理解为不同种类的调度信息。例如Type A的调度信息与MCS表格1之间具有对应关系，Type B的调度信息与MCS表格2之间具有对应关系。
典型地，Type A采用常规MCS表格，TypeB采用覆盖超低码率的MCS表格，或者较小的MCS表格
第四种、基于时域资源长度确定MCS表格：
通过协议约定、或高层配置对应不同的时域资源长度/时域长度范围的调度信息对应的MCS表格；其中，不同的时域资源长度/时域长度范围的调度信息可以理解为不同种类的调度信息。例如时域资源长度/时域长度范围1的调度信息与MCS表格1之间具有对应关系，时域资源长度/时域长度范围2的调度信息与MCS表格2之间具有对应关系。
第五种、基于DCI格式确定MCS表格，或者可以具体理解为DCI格式长度来确定MCS表格：
可以通过协议约定、或高层配置对应不同的DCI格式的调度信息对应的MCS表格；其中，不同的DCI格式的调度信息可以理解为不同种类的调度信息。例如压缩DCI格式的调度信息与MCS表格1具有对应关系，常规DCI格式对应MCS表格2具有对应关系。
典型地，压缩DCI格式可以对应较小的MCS表格，常规DCI格式可以对应较大的MCS表格。
第六种、基于aggregation level(聚合等级)确定MCS表格：
通过协议约定、或高层配置对应不同的Aggregation level的调度信息对应的MCS表格；其中，不同的聚合等级的调度信息可以理解为不同种类的调度信息。例如低聚合等级的调度信息与MCS表格1具有对应关系,高聚合等级的调度信息与MCS表格2之间具有对应关系。
典型地，低聚合等级配置包含高频谱效率的MCS表格，高聚合等级配置包含低频谱效率的MCS表格。
低聚合等级和高聚合等级的划分，可以是基站配置，或协议约定。一类聚合等级可以包含一个或多个聚合等级。典型地，聚合等级1，2，4对应包含高频谱效率的MCS表格，聚合等级8，16对应包含低频普效率的MCS表格。当然还可以存在其他的划分方式，本实施例中不进行穷举。
第七种、基于业务指示确定MCS表格：
通过协议约定、或高层配置对应不同的业务指示对应的调度信息与MCS表格之间的对应关系，其中，不同的业务指示对应的调度信息可以理解为不同种类的调度信息。例如URLLC的调度信息与MCS表格1具有对应关系，eMBB的调度信息与MCS表格2具有对应关系。
第八种、基于控制信道CRC确定MCS表格：
通过协议约定、或高层配置对应于不同的控制信道CRC的调度信息对应的MCS表格；其中，不同的控制信道CRC的调度信息可以理解为不同种类的调度信息。例如控制信道CRC类型1的调度信息与MCS表格1具有对应关系,控制信道CRC类型2的调度信息与MCS表格2具有对应关系。
典型地，控制信道CRC类型可以通过CRC长度，和/或CRC生成方式区别。
例如，控制信道CRC类型1用于URLLC业务调度，为其配置用于URLLC的MCS表格；控制信道CRC类型2用于eMBB业务调度，为其配置用于eMBB的MCS表格。
第九种、基于控制信道RNTI确定MCS表格：
通过协议约定、或高层配置对应于不同的控制信道RNTI的调度信息的MCS表格；其中，对应于不同的控制信道RNTI的调度信息可以理解为不同种类的调度信息。例如控制信道RNTI类型1的调度信息与MCS表格1具有对应关系,控制信道RNTI类型2的调度信息与MCS表格2具有对应关系。
典型地，控制信道RNTI类型可以RNTI取值区别。
例如，控制信道RNTI类型1用于URLLC业务调度，为其配置用于URLLC的MCS表格；控制信道RNTI类型2用于eMBB业务调度，为其配置用于eMBB的MCS表格。
可见，通过采用上述方案，就能够预先获取至少两个MCS表格配置信息，然后根据调度信息选取目标MCS表格，进而采用目标MCS表格进行后续处理。从而，能够实现动态配置MCS表格，适应URLLC，eMBB业务的动态调度；并且，通过采用隐性指示的方法，降低物理层信令开销，提高物理层信令的可靠性。
本发明实施例还提供了一种终端设备或网络设备的硬件组成架构，如图5所示，包括：至少一个处理器51、存储器52、至少一个网络接口53。各个组件通过总线系统54耦合在一起。可理解，总线系统54用于实现这些组件之间的连接通信。总线系统54除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。但是为了清楚说明起见，在图5中将各种总线都标为总线系统54。
可以理解，本发明实施例中的存储器52可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。
在一些实施方式中，存储器52存储了如下的元素，可执行模块或者数据结构，或者他们的子集，或者他们的扩展集：
操作系统521和应用程序522。
其中，所述处理器51配置为：能够处理前述实施例一或二的方法步骤，这里不再进行赘述。
本发明实施例提供的一种计算机存储介质，所述计算机存储介质存储有计算机可执行指令，所述计算机可执行指令被执行时实施前述实施例一或二的方法步骤。
本发明实施例上述装置如果以软件功能模块的形式实现并作为独立的产品销售或使用时，也可以存储在一个计算机可读取存储介质中。基于这样的理解，本发明实施例的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机、服务器、或者网络设备等)执行本发明各个实施例所述方法的全部或部分。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read Only Memory)、磁碟或者光盘等各种可以存储程序代码的介质。这样，本发明实施例不限制于任何特定的硬件和软件结合。
相应地，本发明实施例还提供一种计算机存储介质，其中存储有计算机程序，该计算机程序配置为执行本发明实施例的数据调度方法。
尽管为示例目的，已经公开了本发明的优选实施例，本领域的技术人员将意识到各种改进、增加和取代也是可能的，因此，本发明的范围应当不限于上述实施例。

Claims (33)

  1. 一种动态配置方法，应用于终端设备，所述方法包括：
    终端设备接收至少两个调制与编码策略MCS表格的配置信息，所述配置信息用于确定所述至少两个MCS表格；
    所述终端设备接收网络侧发来的调度信息；
    所述终端设备基于所述调度信息、调度信息与MCS表格之间的对应关系，从所述至少两个MCS表格中确定目标MCS表格。
  2. 根据权利要求1所述的方法，其中，所述调度信息，包括以下至少一类：
    控制资源集合；
    搜索空间集合；
    搜索空间；
    时域资源指示类型；
    时域资源长度；
    MCS表格指示信息；
    下行控制信息DCI格式；
    聚合等级；
    业务指示；
    循环冗余校验CRC；
    无线网络临时标识RNTI。
  3. 根据权利要求2所述的方法，其中，所述方法还包括：
    基于协议确定调度信息与MCS表格之间的对应关系，或者，基于高层配置确定调度信息与MCS表格之间的对应关系。
  4. 根据权利要求2所述的方法，其中，所述方法还包括：
    为每一类调度信息中的每一种调度信息配置对应的MCS表格。
  5. 根据权利要求4所述的方法，其中，所述基于所述调度信息、调度信息与MCS表格之间的对应关系，从所述至少两个MCS表格中确定目标MCS表格，包括：
    确定接收到的调度信息所对应的种类；
    基于所述调度信息所对应的种类、以及所述调度信息所对应的种类与MCS表格之间的对应关系，从所述至少两个MCS表格中确定目标MCS表格。
  6. 根据权利要求1所述的方法，其中，所述至少两个调制与编码策略MCS表格至少包括有：第一MCS表格、以及第二MCS表格。
  7. 根据权利要求6所述的方法，其中，
    所述第一MCS表格为第二MCS表格的部分内容；
    和/或，所述第一MCS表格由第二MCS表格中奇数或偶数索引值所对应的元素组成。
  8. 根据权利要求7所述的方法，其中，所述第一MCS表格为第二MCS表格的部分内容，为：
    所述第一MCS表格为第二MCS表格的前半部分内容。
  9. 一种动态配置方法，应用于网络设备，所述方法包括：
    向终端设备发送至少两个调制与编码策略MCS表格的配置信息，所述配置信息用于确定所述至少两个MCS表格；
    向所述终端设备发送调度信息；其中，所述调度信息与MCS表格之间具备对应关系。
  10. 根据权利要求9所述的方法，其中，所述调度信息，包括以下至少一类：
    控制资源集合；
    搜索空间集合；
    搜索空间；
    时域资源指示类型；
    时域资源长度；
    MCS表格指示信息；
    下行控制信息DCI格式；
    聚合等级；
    业务指示；
    循环冗余校验CRC；
    无线网络临时标识RNTI。
  11. 根据权利要求10所述的方法，其中，所述方法还包括：
    基于协议确定调度信息与MCS表格之间的对应关系，或者，基于高层配置确定调度信息与MCS表格之间的对应关系。
  12. 根据权利要求10所述的方法，其中，所述方法还包括：
    为每一类调度信息中的每一种调度信息配置对应的MCS表格。
  13. 根据权利要求9所述的方法，其中，所述至少两个调制与编码策略MCS表格至少包括有：第一MCS表格、以及第二MCS表格。
  14. 根据权利要求13所述的方法，其中，
    所述第一MCS表格为第二MCS表格的部分内容；
    和/或，所述第一MCS表格由第二MCS表格中奇数或偶数索引值所对应的元素组成。
  15. 根据权利要求14所述的方法，其中，所述第一MCS表格为第二MCS表格的部分内容，为：
    所述第一MCS表格为第二MCS表格的前半部分内容。
  16. 一种终端设备，所述终端设备包括：
    第一通信单元，接收至少两个调制与编码策略MCS表格的配置信息，所述配置信息用于确定所述至少两个MCS表格；接收网络侧发来的调度信息；
    第一处理单元，基于所述调度信息、调度信息与MCS表格之间的对应关系，从所述至少两个MCS表格中确定目标MCS表格。
  17. 根据权利要求16所述的终端设备，其中，所述调度信息，包括以下至少一类：
    控制资源集合；
    搜索空间集合；
    搜索空间；
    时域资源指示类型；
    时域资源长度；
    MCS表格指示信息；
    下行控制信息DCI格式；
    聚合等级；
    业务指示；
    循环冗余校验CRC；
    无线网络临时标识RNTI。
  18. 根据权利要求17所述的终端设备，其中，所述第一处理单元，基于协议确定调度信息与MCS表格之间的对应关系，或者，基于高层配置确定调度信息与MCS表格之间的对应关系。
  19. 根据权利要求17所述的终端设备，其中，所述第一处理单元，为每一类调度信息中的每一种调度信息配置对应的MCS表格。
  20. 根据权利要求19所述的终端设备，其中，所述第一处理单元，确定接收到的调度信息所对应的种类；基于所述调度信息所对应的种类、以及所述调度信息所对应的种类与MCS表格之间的对应关系，从所述至少两个MCS表格中确定目标MCS表格。
  21. 根据权利要求16所述的终端设备，其中，所述至少两个调制与编码策略MCS表格至少包括有：第一MCS表格、以及第二MCS表格。
  22. 根据权利要求21所述的终端设备，其中，
    所述第一MCS表格为第二MCS表格的部分内容；
    和/或，所述第一MCS表格由第二MCS表格中奇数或偶数索引值所对应的元素组成。
  23. 根据权利要求22所述的终端设备，其中，所述第一MCS表格为第二MCS表格的部分内容，为：
    所述第一MCS表格为第二MCS表格的前半部分内容。
  24. 一种网络设备，所述网络设备包括：
    第二通信单元，向终端设备发送至少两个调制与编码策略MCS表格的配置信息，所述配置信息用于确定所述至少两个MCS表格；向所述终端设备发送调度信息；其中，所述调度信息与MCS表格之间具备对应关系。
  25. 根据权利要求24所述的网络设备，其中，所述调度信息，包括以下至少一类：
    控制资源集合；
    搜索空间集合；
    搜索空间；
    时域资源指示类型；
    时域资源长度；
    MCS表格指示信息；
    下行控制信息DCI格式；
    聚合等级；
    业务指示；
    循环冗余校验CRC；
    无线网络临时标识RNTI。
  26. 根据权利要求25所述的网络设备，其中，所述网络设备还包括：
    第二处理单元，基于协议确定调度信息与MCS表格之间的对应关系，或者，基于 高层配置确定调度信息与MCS表格之间的对应关系。
  27. 根据权利要求25所述的网络设备，其中，所述第二处理单元，为每一类调度信息中的每一种调度信息配置对应的MCS表格。
  28. 根据权利要求24所述的网络设备，其中，所述至少两个调制与编码策略MCS表格至少包括有：第一MCS表格、以及第二MCS表格。
  29. 根据权利要求28所述的网络设备，其中，
    所述第一MCS表格为第二MCS表格的部分内容；
    和/或，所述第一MCS表格由第二MCS表格中奇数或偶数索引值所对应的元素组成。
  30. 根据权利要求29所述的网络设备，其中，所述第一MCS表格为第二MCS表格的部分内容，为：
    所述第一MCS表格为第二MCS表格的前半部分内容。
  31. 一种终端设备，包括：处理器和用于存储能够在处理器上运行的计算机程序的存储器，
    其中，所述处理器用于运行所述计算机程序时，执行权利要求1-8任一项所述方法的步骤。
  32. 一种网络设备，包括：处理器和用于存储能够在处理器上运行的计算机程序的存储器，
    其中，所述处理器用于运行所述计算机程序时，执行权利要求9-15任一项所述方法的步骤。
  33. 一种计算机存储介质，所述计算机存储介质存储有计算机可执行指令，所述计算机可执行指令被执行时实现权利要求1-15任一项所述方法的步骤。
PCT/CN2018/087924 2018-02-23 2018-05-22 动态配置方法、终端设备、网络设备及计算机存储介质 WO2019161622A1 (zh)

Priority Applications (8)

Application Number Priority Date Filing Date Title
EP18906809.1A EP3694168B1 (en) 2018-02-23 2018-05-22 Dynamic configuration method, terminal device, network device and computer storage medium
KR1020207014338A KR102565646B1 (ko) 2018-02-23 2018-05-22 동적 구성 방법, 단말 기기, 네트워크 기기 및 컴퓨터 저장 매체
AU2018410421A AU2018410421A1 (en) 2018-02-23 2018-05-22 Dynamic configuration method, terminal device, network device and computer storage medium
CN201880052397.5A CN111034144A (zh) 2018-02-23 2018-05-22 动态配置方法、终端设备、网络设备及计算机存储介质
JP2020528041A JP7286643B2 (ja) 2018-02-23 2018-05-22 動的構成方法、端末機器、ネットワーク機器およびコンピュータ記憶媒体
TW108105884A TW201939986A (zh) 2018-02-23 2019-02-21 動態配置方法、終端設備、網路設備及電腦存儲媒介
US16/846,080 US11184212B2 (en) 2018-02-23 2020-04-10 Dynamic configuration method, terminal device, network device and computer storage medium
US17/453,379 US20220060366A1 (en) 2018-02-23 2021-11-03 Dynamic configuration method, terminal device, network device and computer storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CNPCT/CN2018/077062 2018-02-23
PCT/CN2018/077062 WO2019161547A1 (zh) 2018-02-23 2018-02-23 动态配置方法、终端设备、网络设备及计算机存储介质

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/846,080 Continuation US11184212B2 (en) 2018-02-23 2020-04-10 Dynamic configuration method, terminal device, network device and computer storage medium

Publications (1)

Publication Number Publication Date
WO2019161622A1 true WO2019161622A1 (zh) 2019-08-29

Family

ID=67687472

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/CN2018/077062 WO2019161547A1 (zh) 2018-02-23 2018-02-23 动态配置方法、终端设备、网络设备及计算机存储介质
PCT/CN2018/087924 WO2019161622A1 (zh) 2018-02-23 2018-05-22 动态配置方法、终端设备、网络设备及计算机存储介质

Family Applications Before (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/077062 WO2019161547A1 (zh) 2018-02-23 2018-02-23 动态配置方法、终端设备、网络设备及计算机存储介质

Country Status (8)

Country Link
US (2) US11184212B2 (zh)
EP (1) EP3694168B1 (zh)
JP (1) JP7286643B2 (zh)
KR (1) KR102565646B1 (zh)
CN (3) CN111034319A (zh)
AU (1) AU2018410421A1 (zh)
TW (1) TW201939986A (zh)
WO (2) WO2019161547A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114640421A (zh) * 2020-12-15 2022-06-17 维沃移动通信有限公司 信息传输方法、接收方法、装置、终端及网络侧设备

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111034319A (zh) * 2018-02-23 2020-04-17 Oppo广东移动通信有限公司 动态配置方法、终端设备、网络设备及计算机存储介质
CN115085861B (zh) * 2021-03-15 2023-11-24 维沃移动通信有限公司 传输上行mcs指示信息的方法、终端及网络侧设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101686214A (zh) * 2008-09-26 2010-03-31 大唐移动通信设备有限公司 一种进行信道质量指示估计的方法及装置
US20110143799A1 (en) * 2008-07-08 2011-06-16 Huawei Technologies Co., Ltd. Method and Apparatus for Scheduling Information
US20140153484A1 (en) * 2012-12-03 2014-06-05 Lg Electronics Inc. Method and apparatus for encoding transport block
CN103944855A (zh) * 2013-01-18 2014-07-23 中兴通讯股份有限公司 调制处理方法及装置
CN106992847A (zh) * 2016-01-20 2017-07-28 中兴通讯股份有限公司 上行数据发送、接收方法、装置、终端及基站

Family Cites Families (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9344259B2 (en) 2007-06-20 2016-05-17 Google Technology Holdings LLC Control channel provisioning and signaling
US20110069637A1 (en) 2009-09-18 2011-03-24 Futurewei Technologies, Inc. System and Method for Control Channel Search Space Location Indication for a Relay Backhaul Link
CN105846984B (zh) * 2011-11-04 2019-04-23 华为技术有限公司 接收和发送控制信道的方法、用户设备和基站
US9407417B2 (en) * 2013-01-09 2016-08-02 Qualcomm Incorporated Identifying modulation and coding schemes and channel quality indicators
CN104919772B (zh) * 2013-01-11 2018-10-12 交互数字专利控股公司 用于适应性调制的系统和方法
EP2787670A1 (en) * 2013-04-05 2014-10-08 Panasonic Intellectual Property Corporation of America MCS table adaptation for 256-QAM
EP3042520B1 (en) * 2013-09-03 2020-12-09 Samsung Electronics Co., Ltd A method for the measurement and reporting of channel quality, modulation and channel coding information, and corresponding apparatus
BR112016009761B1 (pt) * 2013-10-31 2023-02-14 Huawei Technologies Co., Ltd. Método de notificação de informação, método de relatório de informação, estação base e equipamento de usuário
JPWO2015099172A1 (ja) * 2013-12-27 2017-03-23 シャープ株式会社 端末装置および基地局装置
EP3089508A4 (en) * 2013-12-27 2017-02-01 Sharp Kabushiki Kaisha Terminal device and base station device
US9467269B2 (en) * 2014-01-06 2016-10-11 Intel IP Corporation Systems and methods for modulation and coding scheme selection and configuration
WO2015116732A1 (en) * 2014-01-29 2015-08-06 Interdigital Patent Holdings, Inc. Method of access and link adaptation for coverage enhanced wireless transmissions
US10075309B2 (en) * 2014-04-25 2018-09-11 Qualcomm Incorporated Modulation coding scheme (MCS) indication in LTE uplink
CN104202115B (zh) * 2014-05-09 2019-05-07 中兴通讯股份有限公司 高阶编码的调制处理方法及装置、基站、终端
US10063672B2 (en) * 2014-10-02 2018-08-28 Acer Incorporated Device and method of handling parameter configurations
EP3267757B1 (en) * 2015-03-04 2019-12-25 Lg Electronics Inc. Method for performing initial access in wireless communication system and device for same
US10356811B2 (en) * 2016-01-28 2019-07-16 Qualcomm Incorporated Methods and apparatus for grant processing
JPWO2017195702A1 (ja) * 2016-05-10 2019-03-14 株式会社Ｎｔｔドコモ 無線通信装置及び無線通信方法
CN108633014B (zh) * 2017-03-22 2021-02-23 华为技术有限公司 数据发送的方法、终端设备和网络设备
US11258532B2 (en) * 2018-01-11 2022-02-22 Kt Corporation Method and apparatus for data modulation and coding for new radio
US10708112B2 (en) * 2018-01-12 2020-07-07 At&T Intellectual Property I, L.P. Dynamic indication of higher order modulation and coding scheme table
JP2019134354A (ja) * 2018-02-01 2019-08-08 シャープ株式会社 端末装置、基地局装置、および、通信方法
US10567108B2 (en) * 2018-02-16 2020-02-18 At&T Intellectual Property I, L.P. Adaptive configuration of modulation and coding scheme tables for new radio
CN111034319A (zh) * 2018-02-23 2020-04-17 Oppo广东移动通信有限公司 动态配置方法、终端设备、网络设备及计算机存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110143799A1 (en) * 2008-07-08 2011-06-16 Huawei Technologies Co., Ltd. Method and Apparatus for Scheduling Information
CN101686214A (zh) * 2008-09-26 2010-03-31 大唐移动通信设备有限公司 一种进行信道质量指示估计的方法及装置
US20140153484A1 (en) * 2012-12-03 2014-06-05 Lg Electronics Inc. Method and apparatus for encoding transport block
CN103944855A (zh) * 2013-01-18 2014-07-23 中兴通讯股份有限公司 调制处理方法及装置
CN106992847A (zh) * 2016-01-20 2017-07-28 中兴通讯股份有限公司 上行数据发送、接收方法、装置、终端及基站

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114640421A (zh) * 2020-12-15 2022-06-17 维沃移动通信有限公司 信息传输方法、接收方法、装置、终端及网络侧设备

Also Published As

Publication number Publication date
CN111510254A (zh) 2020-08-07
US11184212B2 (en) 2021-11-23
KR102565646B1 (ko) 2023-08-09
US20200267043A1 (en) 2020-08-20
EP3694168A1 (en) 2020-08-12
AU2018410421A1 (en) 2020-06-11
TW201939986A (zh) 2019-10-01
CN111034144A (zh) 2020-04-17
US20220060366A1 (en) 2022-02-24
CN111510254B (zh) 2022-07-12
JP2021514551A (ja) 2021-06-10
EP3694168B1 (en) 2023-07-12
KR20200124645A (ko) 2020-11-03
WO2019161547A1 (zh) 2019-08-29
CN111034319A (zh) 2020-04-17
EP3694168A4 (en) 2020-12-16
JP7286643B2 (ja) 2023-06-05

Similar Documents

Publication Publication Date Title
US11477065B2 (en) Method and apparatus for code block division
CN102197612B (zh) 无线通信系统、移动站装置和基站装置
JP5263797B2 (ja) 無線通信システムにおける制御情報を送受信する方法及び装置
WO2019161622A1 (zh) 动态配置方法、终端设备、网络设备及计算机存储介质
JP2013509832A (ja) キャリアアグリゲーションを用いた通信のためのブラインド復号化の数の減少
US11563518B2 (en) Method and device of cyclic redundancy check
US9172496B2 (en) CQI (channel quality indication) information reporting method, and related base station and user equipment
KR100932555B1 (ko) 이동통신 시스템의 자원할당 방법
CN109150413A (zh) 发送和接收反馈信息的方法和装置
WO2019001065A1 (zh) 数据发送方法、装置及存储介质
WO2019095207A1 (zh) 时隙指示方法、终端设备、网络设备及计算机存储介质
CN112005518B (zh) 控制与数据的传输
US11050602B2 (en) Methods and communication apparatuses for bit-to-symbol mapping
WO2016145616A1 (zh) 一种信息传输方法、设备及系统
CN103685115A (zh) 发送数据的方法和装置以及发送数据和接收数据的系统
WO2016154999A1 (zh) 一种数据传输方法、设备及系统
WO2021196025A1 (zh) 数据块传输方法、装置、终端、基站以及存储介质
WO2022028121A1 (zh) 一种信息传输方法、装置、终端和网络侧设备
CN114641067A (zh) 信道重复传输的控制方法、装置和系统
WO2019214554A1 (zh) 一种mcs表格确定方法、终端和基站及可读存储介质
CN104969494B (zh) 基于速度应用错误复原的方法、装置及计算机可读媒体
CN101960764A (zh) 用于自适应地选择解码方案以对嵌入信息进行解码的系统和方法
CN109952726A (zh) 一种被用于无线通信的终端、基站中的方法和装置

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: 18906809

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2018906809

Country of ref document: EP

Effective date: 20200506

ENP Entry into the national phase

Ref document number: 2020528041

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2018410421

Country of ref document: AU

Date of ref document: 20180522

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE