WO2021027753A1 - 信息确定方法、装置和存储介质 - Google Patents

信息确定方法、装置和存储介质 Download PDF

Info

Publication number
WO2021027753A1
WO2021027753A1 PCT/CN2020/108091 CN2020108091W WO2021027753A1 WO 2021027753 A1 WO2021027753 A1 WO 2021027753A1 CN 2020108091 W CN2020108091 W CN 2020108091W WO 2021027753 A1 WO2021027753 A1 WO 2021027753A1
Authority
WO
WIPO (PCT)
Prior art keywords
dci
size
format
starting point
sliv
Prior art date
Application number
PCT/CN2020/108091
Other languages
English (en)
French (fr)
Inventor
石靖
郝鹏
李儒岳
韩祥辉
魏兴光
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP20852512.1A priority Critical patent/EP3829245A4/en
Priority to KR1020217005438A priority patent/KR20210028261A/ko
Priority to MX2021002136A priority patent/MX2021002136A/es
Priority to JP2021510309A priority patent/JP7129555B2/ja
Priority to US17/158,861 priority patent/US11792790B2/en
Publication of WO2021027753A1 publication Critical patent/WO2021027753A1/zh
Priority to US18/487,332 priority patent/US20240163873A1/en

Links

Images

Classifications

    • 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
    • H04W72/1273—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of downlink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0078—Timing of allocation
    • 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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
    • H04W72/566—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient
    • H04W72/569—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient of the traffic information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • 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
    • H04L5/0092—Indication of how the channel is divided

Definitions

  • This application relates to a wireless communication network, for example, to an information determination method, device, and storage medium.
  • the transmission is carried out with a shorter transmission time interval and a lower code rate.
  • the shorter transmission time interval can be single or multiple orthogonal frequency division multiplexing (Orthogonal Frequency Division Multiplexing). Frequency Division Multiplexing, OFDM) symbol.
  • OFDM Frequency Division Multiplexing
  • the aggregation level guarantees highly reliable transmission. Therefore, how to allocate time domain resources is an urgent problem to be solved.
  • the embodiments of the present application provide an information determination method, device, and storage medium, which reduce the overhead required for time domain resource allocation.
  • the embodiment of the present application provides an information determination method, including:
  • the embodiment of the present application provides an information determination method, including:
  • An embodiment of the present application provides an information determination method.
  • the method for determining the priority corresponding to the traffic channel includes one of the following:
  • the priority corresponding to the first DCI format of the scheduling traffic channel is higher than the priority corresponding to the second DCI format
  • the lowest priority corresponding to the first DCI format of the scheduled traffic channel is equal to the priority corresponding to the second DCI format.
  • the embodiment of the present application provides an information determination method, including:
  • the new DCI format includes: format 0_2 for scheduling uplink traffic channels and format 1_2 for scheduling downlink traffic channels; where the size threshold is each The DCI size types handled by the UE in the cell are less than or equal to 4, and the cell radio network temporary identifier C-RNTI scrambles no more than 3 types; or the size threshold is the DCI size type handled by the UE in each cell Less than or equal to 5 types, and no more than 4 types of C-RNTI scrambling.
  • the embodiment of the present application provides an information determination method, including:
  • An embodiment of the present application provides an information determination device, including:
  • the first determining module is configured to determine the time domain resource allocation table TDRA table with the physical downlink control channel PDCCH related symbols as the starting point length indicator value SLIV reference starting point.
  • An embodiment of the present application provides a storage medium that stores a computer program, and when the computer program is executed by a processor, the method described in any of the foregoing embodiments is implemented.
  • Fig. 1 is a flowchart of an information determination method provided by an embodiment of the present application
  • Fig. 2 is a structural block diagram of an information determining device provided by an embodiment of the present application.
  • Fig. 3 is a schematic structural diagram of a device provided by an embodiment of the present application.
  • the mechanism of time domain resource allocation can be: using radio resource control (Radio Resource Control, RRC) to configure the time domain resource allocation table (Time Domain Resource Allocation table, TDRA table).
  • RRC Radio Resource Control
  • TDRA table includes multiple row indexes (Row index)
  • each Row index includes: slot offset, start symbol, length (number of symbols), traffic channel mapping type, which can be passed through the downlink control information (Downlink Control Information, DCI) dynamically indicate one of the Row index.
  • the index of the start symbol can be the slot boundary as the reference starting point, that is, the symbol index in a slot with 14 symbols is 0-13.
  • time-domain resource allocation usually allocates shorter time-domain resources, and control overhead and allocation flexibility
  • URLLC usually Support multiple PDCCH transmission opportunities in a time slot.
  • One way is to assign the physical downlink shared channel (Physical Downlink Shared Channel, PDSCH) time domain resource allocation starting point length indicator value (Start Length Indicator Value, SLIV) reference starting point from the time slot boundary Change to PDCCH related symbols (for example, PDCCH start symbol, PDCCH end symbol, etc.) to save unnecessary RRC configuration, that is, save DCI overhead. Therefore, for the time domain resource allocation of URLLC, the configuration and use of the TDRA Table configured by RRC is an urgent problem to be solved.
  • PDSCH Physical Downlink Shared Channel
  • SLIV Start Length Indicator Value
  • an information determination method is provided, which saves the DCI overhead required for time domain resource allocation.
  • Fig. 1 is a flowchart of an information determination method provided by an embodiment of the present application. As shown in FIG. 1, the method provided in this embodiment includes S120.
  • the PDCCH related symbols include at least one of the following: PDCCH start symbol, PDCCH end symbol, the sum of the PDCCH start symbol and the first preset number of symbols, the PDCCH end symbol and the first preset number of symbols , Where the PDCCH start symbol is the first symbol in the time domain symbols used for PDCCH transmission, and the PDCCH end symbol is the last symbol in the time domain symbols used for PDCCH transmission.
  • the PDCCH start symbol is the first symbol in the time domain symbols used to transmit the PDCCH, that is, the first symbol in the control resource set (Control Resource Set, CORESET) corresponding to the search space where the PDCCH is transmitted; the PDCCH ends The symbol is the last symbol in the time domain symbol used to transmit the PDCCH, that is, the last symbol in the CORESET corresponding to the search space where the PDCCH is transmitted.
  • the candidate allocation results can be configured through the high-level signaling RRC, and then one of the candidate allocation results of the RRC configuration can be dynamically indicated through the DCI to determine the time domain resources of the current traffic channel.
  • RRC configuration parameters include: slot offset K0, SLIV (or independently indicating the starting point S and length L), and the PDSCH mapping type.
  • the parameters configured by RRC include: slot offset K2, SLIV (or independently indicating starting point S and length L), and PUSCH mapping type.
  • DLSCH time domain resources Allocate the reference starting point of SLIV or S (the reference starting point of time-domain resource allocation SLIV or S will be referred to as the reference starting point), adjusted from the slot boundary to the PDCCH start symbol of the scheduled traffic channel, the PDCCH end symbol, and the PDCCH start symbol+X Symbols, or one of the PDCCH end symbols + X symbols, to save unnecessary RRC configuration and save DCI overhead.
  • X is an integer. In the embodiment, taking the PDCCH start symbol as an example, the configuration of the reference start point is described.
  • determining the TDRA table with PDCCH related symbols as the SLIV reference starting point includes: determining the TDRA table with PDCCH related symbols as the SLIV reference starting point according to an independent configuration method.
  • the TDRA table configured by RRC uses the slot boundary as the reference starting point for SLIV.
  • the TDRA table based on PDCCH related symbols as the SLIV reference starting point can be independently configured. Exemplarily, taking the PDCCH related symbol as the PDCCH starting symbol as an example, the independent configuration of the TDRA table with the PDCCH related symbol as the SLIV reference starting point is described. Two sets of RRC configurations are used to configure the TDRA table with the slot boundary as the SLIV reference starting point, and the TDRA table with the PDCCH starting symbol as the SLIV reference starting point.
  • Table 1 is an RRC-configured TDRA table with a slot boundary as the SLIV reference starting point provided in an embodiment of the application.
  • each Row index includes slot offset (K0), start symbol (S), length (L), traffic channel mapping type (Mapping type), and one of the Row index is dynamically indicated through DCI , 8 Row indexes are set in Table 1, then 3 bits are required in the DCI to indicate one of the Row indexes.
  • the TDRA table has 16 row indexes, 4 bits are needed in the DCI to indicate one of the row indexes; if the TDRA table has 4 row indexes, 2 bits are needed in the DCI to indicate one of the row indexes; if the TDRA table has 2 row indexes , Then 1 bit is required in the DCI to indicate one of the Row indexes; if the TDRA table has 1 Row index, there is no need for a bit in the DCI to indicate one of the Row indexes, which is equivalent to requiring 0 bits.
  • the index of the start symbol S is based on the slot boundary as the reference starting point, that is, the symbol index in a slot with 14 symbols is 0 to 13. Among them, if the PUSCH is scheduled, the time slot offset in Table 1 is adjusted from K0 to K2, and the rest of the types will not be repeated. Among them, the starting symbol S in Table 1 is the above-mentioned reference starting point.
  • Table 1 A RRC-configured TDRA table with slot boundaries as the reference starting point for SLIV
  • Table 2-1 and Table 2-2 are TDRA Tables provided by an RRC configuration with the PDCCH starting symbol as the SLIV reference starting point provided in an embodiment of the present application.
  • each Row index includes the slot offset (K0), start symbol (S), length (L), traffic channel mapping type (Mapping type), through DCI Dynamically indicate one of Row index.
  • the index of the start symbol S is based on the PDCCH start symbol as the reference starting point.
  • This embodiment only takes the PDCCH start symbol as an example for description, that is, a start symbol index of 0 indicates that it is the first symbol in the time domain symbols used to transmit the PDCCH.
  • the SLIV reference start point can also be the PDCCH end symbol, or the PDCCH end symbol + X symbols, or the PDCCH start symbol + X symbols as the reference start point. If the PDCCH end symbol is used as the reference start point, the start The symbol index of 0 indicates the last symbol in the time domain symbols used for transmitting the PDCCH, and the rest will not be repeated. If PUSCH is scheduled, K0 in Table 2-1 and Table 2-2 is changed to K2, and the rest of the types will not be repeated.
  • Table 2-1 A RRC-configured TDRA with the PDCCH starting symbol as the SLIV reference starting point
  • Table 2-2 A RRC-configured TDRA Table with the PDCCH starting symbol as the SLIV reference starting point
  • the resource allocation of multiple time domain locations with the same length can be realized with less overhead, improving reliability Or allocate multiple length resource allocations under the same cost to improve scheduling flexibility.
  • determining the TDRA table with PDCCH related symbols as the SLIV reference starting point includes: setting the TDRA table configured with the slot boundary as the SLIV reference starting point as the TDRA table configured with the PDCCH related symbols as the SLIV reference starting point.
  • the TDRA table based on the PDCCH related symbols as the SLIV reference starting point can be implicitly obtained through the TDRA table.
  • the TDRA table is the TDRA table configured with the slot boundary as the SLIV reference starting point.
  • each Row index includes slot offset, start symbol, length (number of symbols) and traffic channel mapping type, and one of the Row index is dynamically indicated through DCI.
  • the index of the start symbol (S) is based on the slot boundary as the reference starting point, that is, the symbol index in a slot with 14 symbols is 0 to 13.
  • Table 3 A RRC-configured TDRA Table with the slot boundary as the SLIV reference starting point
  • the start symbol S can be 0 to 3; when the Mapping type is Type B, the length L is limited.
  • the length L is 2, 4, 7.
  • the way to implicitly obtain the TDRA table with PDCCH related symbols as the SLIV reference starting point from the TDRA table includes one of the following: still use the TDRA table as the TDRA table with PDCCH related symbols as the SLIV reference starting point, and for The invalid state is not indicated by DCI; select part of the row index in the TDRA table as the TDRA table with PDCCH related symbols as the SLIV reference starting point; for each Row index in the TDRA table, reconfigure the PDCCH related symbols as the SLIV reference starting point, or The slot boundary serves as the starting point of SLIV reference.
  • determining the TDRA table with the PDCCH related symbols as the SLIV reference starting point also includes: determining that the PDCCH related symbols are used as the SLIV Refer to whether the starting point is in an invalid state; if it is not in an invalid state, indicate the corresponding Row index in the TDRA table through DCI.
  • the TDRA table configured with the slot boundary as the SLIV reference starting point is used as the TDRA table configured with the PDCCH related symbols as the SLIV reference starting point, and then the row index in the invalid state is not indicated by the DCI.
  • the invalid state includes at least one of the following: the case where the SLIV reference starting point exceeds the slot boundary, or the case where the sum of the SLIV reference starting point and the length exceeds the slot boundary.
  • the Row index is invalid; for PUSCH repetition scheduling, when S+L exceeds the slot, then The Row index is in a valid state.
  • the meaning of crossing/beyond the slot boundary can be S>13 (that is, the reference starting point S is crossing/beyond the slot boundary), or S+L>14 (that is, the time domain resource allocation determined by referring to the starting point and the length is crossing/being beyond the slot boundary ).
  • each Row index in the TDRA table configure whether it is the PDCCH related symbol as the reference starting point or the slot boundary as the reference starting point, that is, to reconfigure each Row index in the TDRA table, and then Row index with PDCCH related symbols as the SLIV reference starting point is regarded as a TDRA table with PDCCH related symbols as the SLIV reference starting point.
  • determining the TDRA table with PDCCH related symbols as the SLIV reference starting point includes: selecting a part of the row index of the TDRA table configured with the slot boundary as the SLIV reference starting point; taking the part of the row index as the PDCCH related symbols as the SLIV reference TDRA table of the starting point.
  • part of the row index in the TDRA table configured with the slot boundary as the SLIV reference starting point can be directly selected as the TDRA table with the PDCCH related symbols as the SLIV reference starting point.
  • selecting a partial row index of the TDRA table configured with the slot boundary as the SLIV reference starting point includes: selecting the first preset number Row index as the partial row index, or selecting the part in the form of a bitmap bitmap Row index.
  • the bitmap is selected. Taking Table 3 as an example, assuming that the bitmap is 8bit 00001100, it indicates that Row index #4 and #5 in Table 3 are used as the TDRA table with PDCCH related symbols as the SLIV reference starting point. At this time, 1bit can be used in DCI to indicate two Row indexes in the corresponding TDRA table (including Row index #4 and #5).
  • the reference starting point S can be reinterpreted as 0, that is, the traffic channel starting symbol and The PDCCH start symbols are the same.
  • the TDRA table with the PDCCH related symbols as the SLIV reference starting point is obtained from the TDRA table in the above implicit manner, and then the result is The start symbol S in the TDRA table with the PDCCH related symbol as the SLIV reference start point is reinterpreted and reinterpreted as 0, that is, the traffic channel start symbol is the same as the PDCCH start symbol.
  • the TDRA table with the PDCCH related symbols as the SLIV reference starting point is obtained from the TDRA table in an implicit manner, which can realize resource allocation of multiple time domain locations of the same length with less overhead and improve reliability; or The resource allocation of multiple lengths is allocated under the same cost to improve scheduling flexibility.
  • the PDCCH usage of different PDCCH related symbol positions or different time spans is not all the same. TDRA table.
  • different PDCCH related symbol positions or PDCCHs of different spans use different TDRA tables, including one of the following: PDCCH at each position or PDCCH of each span uses one TDRA table; X starting symbols The set uses X TDRA tables, and the elements in the X starting symbol sets are different and the union includes all symbols in the slot, or the elements of the X starting symbol set are independently configured; X span sets use X respectively In a TDRA table, the elements in the X span sets are different from each other and the union includes all the spans in the span pattern, or the elements of X span sets are independently configured.
  • the TDRA table of the existing RRC configuration uses the slot boundary as the reference starting point.
  • the TDRA table based on the PDCCH related symbols as the SLIV reference starting point can be obtained through independent configuration or implicitly obtained through the table in the related technology, and there can be one One or more TDRA tables based on PDCCH related symbols as the reference starting point.
  • PDCCH related symbol as the PDCCH start symbol
  • different PDCCH related symbol positions or different spans of PDCCHs are described using different TDRA tables.
  • TDRA tables different PDCCH start symbol positions/span PDCCHs use different TDRA tables.
  • the slot is divided into 7 non-overlapping 2OS (OFDM Symbol) spans.
  • set 0 contains the PDCCHs in the first 3 spans
  • set 1 contains the PDCCHs in the last 4 spans.
  • Each set uses 1 TDRA table. .
  • the length of L in at least one RRC TDRA table is limited. For example, if L is less than the threshold P, the optional P is 2, 4, and 7.
  • the TDRA table with the PDCCH start symbol as the reference starting point is implicitly obtained from the table in the related technology, which can realize the resource allocation of multiple time domain locations of the same length with less overhead, and improve reliability ; Or allocate multiple lengths of resource allocation under the same overhead to improve scheduling flexibility.
  • an information determination method includes: determining a reference starting point of SLIV, where the reference starting point includes a slot boundary or PDCCH related symbols.
  • the reference starting point of SLIV when there is more than one possibility for the reference starting point of SLIV, it includes at least one of the following methods: PDCCH start symbol, or PDCCH end symbol, or start symbol of CORESET where PDCCH is located, or PDCCH The end symbol of the CORESET; the time slot boundary, where the time slot boundary is the time slot boundary determined according to the scheduling timing K0 or K2; the start symbol of the first available traffic channel, where the traffic channel is PDSCH or PUSCH; starting from PDCCH Start symbol + X symbols, or PDCCH end symbol + X symbols.
  • determining the reference starting point of SLIV includes one of the following: determining the reference starting point of SLIV according to the traffic channel type, the traffic channel types include Type A and Type B; PDCCH related symbols are used as the reference starting point of SLIV by default; in SLIV When the sum of the reference starting point and the length exceeds the slot boundary, the SLIV reference starting point is determined as the slot boundary; the SLIV reference starting point is determined according to the PDCCH related symbol position; or the SLIV reference starting point is determined according to the downlink control information DCI format of the scheduled traffic channel .
  • the reference starting point of SLIV can be determined according to preset rules or the method notified by the base station. In one embodiment, taking the reference starting point of SLIV as the PDCCH starting symbol or slot boundary as an example, the reference starting point of SLIV Confirm the way to explain. Wherein, the reference starting point of SLIV may also be the PDCCH end symbol, the PDCCH start symbol + X symbols, the PDCCH end symbol + X symbols, the start symbol of the first available traffic channel, which is not limited. In this embodiment, taking the reference starting point of SLIV as the PDCCH start symbol or slot boundary, the manner of determining the reference starting point of SLIV includes one of the following:
  • the SLIV reference starting point is determined according to the traffic channel type. For example, when the traffic channel is Type A, the slot boundary is used as the SLIV reference starting point; when the traffic channel is Type B, the PDCCH start symbol is used as the SLIV reference starting point.
  • the PDCCH start symbol is used as the reference starting point of SLIV by default.
  • the slot boundary is used as the SLIV reference starting point, and the slot boundary is used to determine S and S+L again.
  • the reference starting point of the SLIV is determined according to the PDCCH time domain symbol position. Exemplarily, when the PDCCH start symbol is located in the first three symbols, the slot boundary is used as the SLIV reference starting point, and the PDCCH starting symbol is used as the reference starting point in other cases, which is not limited.
  • determining the SLIV reference starting point according to the DCI format of the scheduled traffic channel includes: determining the TDRA table with PDCCH related symbols as the SLIV reference starting point for the first DCI format, and the first DCI format includes one of the following: new
  • the DCI format is a DCI format for scheduling ultra-reliable low-latency communication URLLC.
  • the DCI size is less than the preset threshold.
  • the time domain resource allocation domain size in the DCI is less than the preset threshold.
  • the SLIV reference starting point is determined according to the DCI format of the scheduling traffic channel.
  • the PDCCH starting symbol is used as the SLIV reference starting point
  • the first DCI format may be the DCI for scheduling URLLC
  • the format is either a Compact DCI format, or a DCI format with a DCI size smaller than a predetermined/preset threshold, or a DCI format with a time domain resource allocation domain size in the DCI smaller than a predetermined/preset threshold.
  • the inconsistent understanding between the base station and the terminal can prevent the data from being received incorrectly, so that the scheduling can be guaranteed under different conditions.
  • the flexibility and time-domain resource allocation overhead is reduced, ensuring low-latency and high-reliability service transmission.
  • the PDCCH starting from the second or third symbol in the slot cannot be scheduled for Type A PDSCH with the start symbol earlier than the PDCCH start symbol.
  • This embodiment can be used The method described above can avoid the above scheduling restrictions by flexibly selecting the reference starting point of SLIV.
  • TDRA table that uses PDCCH related symbols as the SLIV reference starting point.
  • PDCCH related symbols taking the PDCCH related symbol as the PDCCH starting symbol as an example, the relationship between the SLIV reference starting point and the TDRA table is described.
  • the TDRA table used with the slot boundary as the SLIV reference starting point is a table independently configured by RRC, and the PDCCH starting symbol is used as the SLIV reference starting point.
  • TDRA table methods include one of the following:
  • the used TDRA table is part of the row index in the TDRA table that uses the slot boundary as the SLIV reference starting point, for example, the first X row indexes, or the part of the row index determined by the bitmap.
  • the TDRA table used at the starting point that is, the TDRA table with the PDCCH starting symbol as the SLIV reference starting point is the same as the TDRA table with the slot boundary as the SLIV reference starting point, and the row index whose SLIV reference starting point is invalid is not indicated. Yes, or the UE does not expect to indicate the time domain resource allocation across slot boundaries.
  • the base station and the terminal have the same understanding of time domain resource allocation and avoid the terminal from receiving data incorrectly.
  • the SLIV reference starting point configuration method includes one of the following: independent configuration of the SLIV reference starting point; PDCCH related symbols as the SLIV reference starting point by default; repeating when scheduling PUSCH In the case of transmission, the reference starting point of the SLIV is determined as the slot boundary; in the case of scheduling PUSCH repeated transmission, the reference starting point of the SLIV is determined as the PDCCH related symbol.
  • the PDCCH related symbol as the PDCCH starting symbol as an example, the method for determining the SLIV reference starting point in the TDRA table used for scheduling the PUSCH will be described.
  • the TDRA table used for scheduling PUSCH can be determined by one of the following methods:
  • the TDRA table used is determined according to whether the PUSCH is repeatedly transmitted. For example, for PUSCH repeated transmission and non-repetitive transmission, different TDRA tables are used. Among them, the TDRA table used for scheduling the non-repetitive transmission PUSCH uses the PDCCH start symbol as the SLIV reference starting point, and the TDRA table used for scheduling the repeated transmission PUSCH is Take the slot boundary as the reference starting point for SLIV. Another example: using a TDRA table, but the Row index that crosses the slot boundary is valid for repeated transmission but invalid for non-repetitive transmission.
  • the PDCCH start symbol is used as the SLIV reference starting point
  • the slot boundary is used as the SLIV reference starting point
  • the SLIV reference starting point when there is more than one possibility for the SLIV reference starting point, it includes at least one of the following methods: PDCCH start symbol, PDCCH end symbol, start symbol of CORESET where PDCCH is located, and end symbol of CORESET where PDCCH is located; Time slot boundary, where the time slot boundary is the time slot boundary determined according to the scheduling timing K0 or K2; the start symbol of the first available traffic channel, where the traffic channel is PDSCH or PUSCH; the PDCCH start symbol + X symbols , Or PDCCH end symbol + X symbols.
  • This embodiment discloses a method for determining the SLIV reference starting point according to preset rules and/or notification by the base station.
  • One of the two methods is determined, including at least one of the following methods, taking the PDCCH starting symbol and slot boundary as examples. Description, but not limited to this, can be any two ways.
  • which method is used is determined according to whether the PUSCH is repeatedly transmitted. For example, the slot boundary is used as the SLIV reference starting point for repeated transmission, and the PDCCH starting symbol is used as the SLIV reference starting point for non-repetitive transmission. In one embodiment, the PDCCH start symbol is used as the SLIV reference starting point by default. When PUSCH repeated transmission is scheduled, the slot boundary is used as the SLIV reference starting point, and the slot boundary is used to determine S and S+L again.
  • the method of determining one of the SLIV reference starting points can avoid the inconsistent understanding between the base station and the terminal.
  • the data cannot be received correctly, thereby ensuring scheduling flexibility and reducing the time domain resource allocation overhead under different conditions, and ensuring low-latency and high-reliability service transmission.
  • the method for determining the TDRA table used for time-domain resource allocation in at least two different DCI formats includes one of the following: the second DCI format uses TDRA configured by RRC table, the first DCI format uses the default TDRA table; the default TDRA table is independently set for at least two different DCI formats; the TDRA table is independently configured for at least two different DCI formats.
  • the first DCI format is the DCI format used by URLLC as an example (the first DCI format may be the DCI format for scheduling URLLC, or the Compact DCI format, or the DCI size is smaller than the predetermined/predetermined Set the threshold DCI format, or the DCI format in which the size of the time domain resource allocation domain in DCI is smaller than the predetermined/preset threshold), the second DCI format is the DCI format used by Enhanced Mobile Broadband (eMBB) .
  • eMBB Enhanced Mobile Broadband
  • URLLC can reuse the same DCI format as eMBB, or use a new format.
  • the second DCI format and the first DCI format are different, that is, one of the second DCI format and the first DCI format is the new DCI format, and the other is the original DCI format.
  • the TDRA table used for time domain resource allocation in the new DCI format and the original DCI format needs to be determined.
  • the TDRA table determination method used for time-domain resource allocation in different DCI formats includes one of the following:
  • one of the DCI formats uses the TDRA table configured by RRC
  • the other DCI format uses the default TDRA table.
  • the time domain resource allocation in the DCI format 1_1 of R15 uses the TDRA table configured by RRC
  • the time domain resource allocation in the newly introduced DCI format 1_2 of R16 uses the default TDRA table PDSCH.
  • the default TDRA table can be configured as a table with less than 16 rows.
  • the bit size of the time domain resource allocation in the DCI can be less than 4 bits.
  • the PDCCH related symbols for example, the PDCCH start symbol
  • the default TDRA table are used as the SLIV reference starting point.
  • different default TDRA tables are configured for different DCI formats. For example, taking PDSCH scheduling as an example, the time domain resource allocation in the DCI format 1_1 of R15 uses the default TDRA table and is configured as 16 rows, and the time domain resource allocation in the newly introduced DCI format 1_2 of R16 uses the default TDRA table and is configured to 4. Row.
  • the information determination method described in this embodiment uses a specific DCI format to determine the use of a TDRA table with the PDCCH start symbol as the SLIV reference starting point, which can achieve resource allocation for multiple time domain locations of the same length with less overhead. Improve reliability; or allocate multiple lengths of resource allocation under the same overhead to improve scheduling flexibility.
  • a method for determining information When the first DCI format and the second DCI format are used for traffic channel scheduling, the method for determining the priority corresponding to the traffic channel includes one of the following: The priority corresponding to the DCI format is higher than the priority corresponding to the second DCI format; or, the lowest priority corresponding to the first DCI format of the scheduled traffic channel is equal to the priority corresponding to the second DCI format.
  • the first DCI format is the DCI format used by eMBB.
  • the second DCI format is the DCI format used by eMBB
  • the first DCI format is the DCI format used by URLLC.
  • URLLC can reuse the same DCI format as eMBB, or use a new DCI format.
  • the second DCI format and the first DCI format are different, that is, one of the second DCI format and the first DCI format is the new DCI format, and the other is the original DCI format.
  • the new DCI format and the original DCI format can be used for traffic channel scheduling at the same time.
  • the priority of the traffic channel is determined and based on the priority of the traffic channel Perform subsequent operations.
  • the method for determining the priority of traffic channels scheduled in different DCI formats includes one of the following:
  • the priority of the traffic channel scheduled in the original DCI format is lower than any priority indicated by the priority in the new DCI format.
  • the priority of the service scheduled by non-fallback DCI ie, DCI format 0_1, DCI format 1_1 is lower than any priority indicated by the priority in the new DCI. That is to say, the priority of the service scheduled by R15 non-fallback DCI is the lowest at this time.
  • the priority of the traffic channel scheduled in the original DCI format is equal to the lowest priority indicated by the priority in the new DCI format. For example, if the priority indicator in the new DCI has 1 bit indicating that the priority is high and low, then the priority corresponding to the traffic channel scheduled by R15 non-fallback DCI is equal to the low priority of the priority indicator in the new DCI level.
  • the information determination method in this embodiment determines the priority levels corresponding to the traffic channels scheduled in different DCI formats, so that the base station and the terminal can perform the same subsequent operations according to the priority levels, ensuring consistent understanding between the two parties.
  • URLLC can reuse the same DCI format as eMBB, or can use a new DCI format.
  • the types of DCI sizes will increase. Therefore, how to determine the DCI size threshold (budget) and how to perform DCI size alignment (alignment) is an urgent problem to be solved.
  • the size threshold is the size budget.
  • the DCI format of the introduced new scheduling PUSCH is defined as DCI format 0_2
  • the DCI format of the introduced new scheduling PDSCH is defined as DCI format 1_2.
  • the DCI size budget is "3+1", that is, for a cell, the UE handles no more than 4 types of sizes. Among them, the Cell-Radio Network Temporary Identifier (C-RNTI) plus No more than 3 kinds of disturbance.
  • C-RNTI Cell-Radio Network Temporary Identifier
  • the size alignment steps in related technologies include: Step0: align format 0_0 with format 1_0 in the Common Search Space (CSS); Step1: align format 0_0 with format 1_0 in USS; Step2: If format 0_1 in USS is aligned with proprietary If the size of format 0_0/1_0 in the search space (UE-Specific Search Space, USS) is the same, the format 0_1 is filled with 1 bit zero padding; the same is true for format 1_1.
  • Step3 If it is satisfied that "the types of sizes to be processed do not exceed 4, and the C-RNTI scrambled does not exceed 3", then the step is over (step over). Otherwise, continue to step 4.
  • Step4 Remove the padding in step2. Re-calculate format 1_0/0_0 in USS with CORESET0/Bandwidth part (Bandwidth part, BWP), and align the size of format 0_0 and format 1_0 in USS. At this time, CSS and format 1_0/0_0 size in USS are aligned.
  • the UE does not want to process more than 4 types of sizes, of which more than 3 types are C-RNTI scrambled.
  • the UE does not want the size of format 0_0 and format 0_1 in the USS to be the same, and it does not want the size of format 1_0 and format 1_1 in the USS to be the same.
  • a method for determining information includes: performing a DCI size alignment operation when a new DCI format is added; the new DCI format includes: format 0_2 for scheduling uplink traffic channels and format 0_2 for scheduling downlink traffic channels format 1_2; where the size threshold is that the DCI processed by the UE in each cell is less than or equal to 4 types of size, and the cell radio network temporary identification C-RNTI scrambles no more than 3 types; or, the size threshold The value is less than or equal to 5 types of DCI size processed by the UE in each cell, and no more than 4 types of C-RNTI scrambling.
  • URLLC DCI includes format 0_2 size and format 1_2 size.
  • the DCI format for scheduling URLLC uplink services is DCI format 0_2
  • the DCI format for scheduling URLLC downlink services is DCI format 1_2
  • URLLC DCI UL is format 0_2
  • URLLC DCI DL is format 1_2.
  • the DCI size alignment operation is performed, including : Align the size of format0_0 and format1_0; align the size of format 0_1 and format 1_1; align the size of format 0_2 and format 1_2.
  • the format 0_0 and 1_0 size of fallback DCI are aligned
  • the format 0_1 and 1_1 size of non-fallback DCI are aligned
  • the format 0_2 and 1_2 size of URLLC DCI are aligned, that is, a total of 3 Kind. If the size of the three DCI formats is equal, zero padding needs to be added. In one embodiment, this method does not allow URLLC DCI size to be the same as R15 DCI size.
  • the DCI size alignment step includes: Step0: aligning format 0_0 and format 1_0 in CSS; Step1: format 0_0 and format 1_0 in USS Alignment; Step2: If the size of format 0_1 in USS and format 0_0/1_0 in USS are equal, add 1 bit of zero padding to format 0_1; the same is true for format 1_1; the same is true for format 0_2; the same is true for format 1_2.
  • Step3 If it is satisfied that "the types of processed sizes are not more than 4, among which C-RNTI scrambling is not more than 3", then step over. Otherwise, continue to step 4.
  • Step4 Remove the padding in step2.
  • Step 5 If it is satisfied that "the types of processed sizes are not more than 4, among which C-RNTI scrambling is not more than 3", then step over. Otherwise, continue to step 6.
  • Step6 Format 0_2 in USS is aligned with format 1_2; Step7: If it is satisfied that "the types of sizes processed do not exceed 4, among which C-RNTI scrambling does not exceed 3", then step over. Otherwise, continue to step 8.
  • Step8 Format 0_1 is aligned with format 1_1 in USS.
  • the UE does not want to process more than 4 types of sizes, of which more than 3 types are C-RNTI scrambled.
  • the UE does not want format 0_0 and format 0_1 in the USS to be the same size as format 0_2, and does not want format 1_0 and format 1_1 in the USS to be the same size as format 1_2.
  • the DCI size alignment operation is performed, including : Align the size of format 0_2 and format 1_2 to the first size; align the first size with the size of fallback DCI or non-fallback DCI.
  • URLLC DCI size is aligned with R15 fallback DCI size or non-fallback DCI size, that is, there are no more than 3 types, that is, URLLC DCI format 0_2size and format 1_2size are aligned, and aligned to the first size, which is equivalent to URLLC DCI UL size and URLLC DCI DL size are aligned as the first size. Then, align the first type of size with fallback DCI size or non-fallback DCI size to achieve the effect that the types of DCI sizes do not exceed 3 types.
  • aligning the first type of size with the size of fallback DCI or non-fallback DCI includes one of the following: configuring the first type of size to align with the size of fallback DCI or non-fallback DCI according to high-level signaling; or Align the first type of size to fallback DCI or non-fallback DCI size according to the size closest principle.
  • the first size is configured to be aligned with a format of R15 according to high-layer signaling.
  • the corresponding DCI size alignment steps are as follows: Step0: Format 0_0 in CSS is aligned with format 1_0; Step1: Format 0_0 in USS is aligned with format 1_0; Step2: If USS The size of format 0_1 and format 0_0/1_0 in USS are equal, so add 1 bit of zero padding to format 0_1; the same is true for format 1_1. Among them, format 0_2 and format 1_2 are not processed.
  • Step3 If it is satisfied that "the size types processed at the same time do not exceed 4 types, and the C-RNTI scrambled types do not exceed 3 types", then step over. Otherwise, continue to step 4.
  • Step4 Format 0_2 in USS is aligned with format 1_2;
  • Step5 If it is satisfied that "the types of sizes processed at the same time do not exceed 4, and the C-RNTI scrambled does not exceed 3 types", then step over. Otherwise, continue to step 6.
  • Step6 Align format 0_2/1_2 in USS with format 0_0/1_0 in USS.
  • Step7 If it is satisfied that "the types of sizes processed at the same time do not exceed 4, and the C-RNTI scrambled does not exceed 3", then step over.
  • Step8 Remove the padding in step 2, re-calculate format 1_0/0_0 in USS with CORESET0/initial BWP, align the size of format 0_0 and format 1_0 in USS, then format 1_0/0_0 size in CSS and USS are aligned; remove padding in step 6 , Realign 0_2/1_2 and format 0_0/1_0.
  • the UE does not want to process more than 4 types of sizes at the same time, of which more than 3 types are scrambled by C-RNTI.
  • the UE does not want format 0_0/0_2 in the USS to have the same size as format 0_1, and does not want format 1_0/1_2 in the USS to have the same size as format 1_1.
  • aligning the first type of size to the size of fallback DCI or non-fallback DCI according to the size closest principle includes: when the DCI size of the scheduling traffic channel is smaller than the fallback DCI size, the URLLC DCI size is not executed The operation of aligning to the fallback DCI size; when the DCI size of the scheduled traffic channel is greater than the fallback DCI size, the operation of aligning to the fallback DCI size or non-fallback DCI size is performed according to the size closest principle.
  • the URLLC DCI size when the URLLC DCI size is smaller than the fallback DCI size, the URLLC DCI is not aligned to the fallback DCI operation; when the URLLC DCI size is greater than the fallback DCI size, the size alignment is performed according to the size closest principle.
  • the size alignment operation is performed according to the size closest principle, and the corresponding DCI size alignment steps include: Step0: format 0_0 in CSS is aligned with format 1_0; Step1: format 0_0 in USS is aligned with format 1_0; Step2: if format in USS 0_1 is equal to the size of format 0_0/1_0 in USS, so add 1 bit of zero padding to format 0_1; the same is true for format 1_1; among them, format 0_2 and format 1_2 do not do any processing. Step3: If it is satisfied that "the size types processed at the same time do not exceed 4 types, and the C-RNTI scrambled types do not exceed 3 types", then step over. Otherwise, continue to step 4.
  • Step4 Format 0_2 in USS is aligned with format 1_2; Step5: If it is satisfied that "the types of sizes processed at the same time do not exceed 4, and the C-RNTI scrambled does not exceed 3 types", then step over. Otherwise, continue to step 6.
  • Step6 Align the URLLC DCI size with the size closest principle, that is, align it to the fallback DCI size or non-fallback DCI size in R15 according to the conditions satisfied by the DCI size in Table 4.
  • Table 4 is a relational table for size alignment according to the size closest principle provided by the embodiment of the present application.
  • URLLC DCI size is N1bits
  • fallback DCI size is M bits
  • DCI size of one scheduling direction of non-fallback DCI is P bits
  • DCI size of another scheduling direction of non-fallback DCI is Q bits
  • M is about 40 bits
  • P and Q are about 60 bits
  • the scheduling direction refers to UL, DL
  • Table 4 A relationship table for size alignment according to the size closest principle
  • the UE does not want to process more than 4 types of sizes at the same time, and more than 3 types of C-RNTI scrambled.
  • the UE does not want the format 0_0/0_2 in the USS to have the same size as the format 0_1, and it does not want the format 1_0/1_2 in the USS to have the same size as the format 1_1, or in the URLLC DCI size If the size is the same as format 0_1, the UE does not want format 0_0 in USS to have the same size as format 0_1/0_2/1_2, or if URLLC DCI size and format 1_1 size are the same, it does not want format 1_0 and format 1_1/ in USS.
  • the DCI size alignment operation is performed, including : Within the time range of each time span, the types of DCI sizes processed by the UE in each cell are less than or equal to 4 types, of which no more than 3 types are scrambled by C-RNTI.
  • the size budget is not allowed to increase, for example, the size budget still maintains "3+1", that is, for a cell, the UE handles no more than 4 types of sizes, and the C-RNTI scrambling is not allowed. More than 3 kinds.
  • the method of executing size alignment remains unchanged, but it is executed according to a smaller time granularity.
  • "3+1" is maintained at the granularity of per span, that is, for a cell, the size types processed by the UE in per span do not exceed 4 types, and the C-RNTI scrambled does not exceed 3 types.
  • the overall DCI size type can be more than 4 types.
  • the size budget is allowed to increase, for example, the size budget can be increased to "4+1", that is, for a cell, the UE handles no more than 5 types of sizes, and no more than 4 types of C-RNTI scramble.
  • the DCI size alignment operation is performed, including One of the following: align the format 0_2 and format1_2 of the DCI of the scheduled traffic channel; align the size of the DCI format 0_2 or format1_2 of the scheduled traffic channel to the fallback DCI size; align the size of the DCI format 0_2 or format1_2 of the scheduled traffic channel Align to non-fallback DCI size; align non-fallback UL DCI size with non-fallback DL DCI size; align the DCI size of the scheduled traffic channel to fallback DCI size or non-fallback DCI size according to the pre-configuration method; Set up rules to align the DCI size of the scheduled traffic channel to fallback DCI size or non-fallback DCI size.
  • the size alignment operation is performed on the format 0_2 and format 1_2 of the DCI of the scheduled traffic channel, that is, the size alignment operation is performed on the URLLC DCI format 0_2 and format 1_2.
  • the corresponding DCI size alignment step may include: Step0: Format 0_0 in CSS is aligned with format 1_0; Step1: Format 0_0 in USS is aligned with format 1_0; Step2: If format 0_1 in USS is aligned with format 0_0/1_0 in USS If the size is equal, then add 1 bit of zero padding to format 0_1; format 1_1 is the same; format 0_2 and format 1_2 do not do any processing.
  • Step3 If it is satisfied that "the types of sizes to be processed do not exceed 5, and the C-RNTI scrambling does not exceed 4", then step over. Otherwise, continue to step 4; Step 4: USS format 0_2 is aligned with format 1_2; Step 5: If it is satisfied that "the types of sizes processed are not more than 5, and the C-RNTI scrambled is not more than 4 types", then step over. Otherwise, continue to step 6. Step6: Remove the padding in step2, recalculate format 1_0/0_0 in USS with CORESET0/initial BWP, and align the size of format 0_0 and format 1_0 in USS.
  • format 1_0/0_0 size in CSS and USS are aligned; after the above steps, The UE does not want to process more than 5 types of sizes, of which more than 4 types are C-RNTI scrambled.
  • the UE does not want format 0_0 and format 0_1 in the USS to be the same size as format 0_2, and does not want format 1_0 and format 1_1 in the USS to be the same size as format 1_2.
  • step6 and step4 can also be interchanged.
  • the size of the DCI format 0_2 or format1_2 of the scheduling traffic channel is aligned to the fallback DCI size, that is, one of the URLLC DCI is aligned to the fallback DCI.
  • select URLLC DCI whose size is close to 40bit to fallback DCI, and the corresponding DCI size alignment steps include: Step0: align format 0_0 with format 1_0 in CSS; Step1: align format 0_0 with format 1_0 in USS; Step2: If in USS Format 0_1 is equal to the size of format 0_0/1_0 in USS, so add 1 bit of zero padding to format 0_1; the same is true for format 1_1; format 0_2 and format 1_2 do not do any processing.
  • Step3 If it is satisfied that "the types of sizes to be processed do not exceed 5, and the C-RNTI scrambling does not exceed 4", then step over. Otherwise, continue with step4; Step4: Remove the padding in step2, recalculate format 1_0/0_0 in USS with CORESET0/initial BWP, and align the size of format 0_0 and format 1_0 in USS, and then format 1_0/0_0 size in CSS and USS are aligned; Step5: If it is satisfied that "the types of sizes processed are not more than 5, among which C-RNTI scrambling is not more than 4", then step over. Otherwise, continue to step 6.
  • Step6 align the smallest size of format 0_2 and format 1_2 with format 1_0/0_0size; after the above steps, the UE does not want to process the size There are more than 5 types, of which more than 4 are C-RNTI scrambled.
  • format 1_2 is aligned with fallback DCI size
  • UE does not want format 0_0 and format 0_1 in USS to be the same size as format 0_2; when format 0_2 is aligned with fallback DCI size, it does not want format 1_0 and format in USS 1_1, the same size as format 1_2.
  • step6 and step4 can also be interchanged.
  • the description in step 4 needs to be supplemented with "remove the padding before URLLC DCI, and re-set the format 0_2 and format 1_2 with the smallest size (ie min ⁇ size of format 0_2, size of format 1_2 ⁇ ) Align with format 1_0/0_0size".
  • the size of the DCI format 0_2 or format1_2 of the scheduled traffic channel may be aligned to the non-fallback DCI size, that is, one URLLC DCI may be aligned to one of the R15 non-fallback DCI. For example, if URLLC DCI size is greater than fallback DCI size, and the larger size in URLLC DCI is selected and aligned to one of R15non-fallback DCI.
  • URLLC DL DCI is aligned to eMBB UL DCI, or URLLC UL DCI is aligned to eMBB DL DCI.
  • the corresponding DCI size alignment steps include: Step0: Format 0_0 in CSS is aligned with format 1_0; Step1: Format 0_0 in USS is aligned with format 1_0; Step2: If format 0_1 in USS is aligned with format 0_0/1_0 in USS If they are equal, add 1-bit zero padding to format 0_1; format 1_1 is the same; format 0_2 and format 1_2 do not do any processing. Step3: If it is satisfied that "the types of sizes to be processed do not exceed 5, and the C-RNTI scrambling does not exceed 4", then step over.
  • Step4 Remove the padding in step2, recalculate format 1_0/0_0 in USS with CORESET0/initial BWP, and align the size of format 0_0 and format 1_0 in USS, and then format 1_0/0_0 size in CSS and USS are aligned;
  • Step5 If it is satisfied that "the types of sizes processed are not more than 5, among which C-RNTI scrambling is not more than 4", then step over. Otherwise, continue to step 6 (for example, only DL or UL requires URLLC scheduling, and the step ends after Step 5).
  • Step6 Align the largest format among format 0_2size and format 1_2size (ie max ⁇ size of format 0_2, size of format 1_2 ⁇ ) with format 1_1 or 0_1size; after the above steps, the UE does not want to process more than 5 types of sizes. Among them, there are more than 4 types of C-RNTI scrambling.
  • format 1_2size is aligned with format 0_1size, the UE does not want format 0_0 and format 0_1 and format 0_2 in the USS to have the same size.
  • format 0_2size is aligned with format 1_1size, it is not expected that format 1_0 and format 1_1 and format in USS are aligned.
  • step6 and step4 can also be interchanged. However, after step 6 and step 4 are exchanged, the description of step 4 should be supplemented accordingly: "Remove the padding before URLLC DCI, and re-set the format with the largest size among format 0_2size and format 1_2size (that is, max ⁇ size of format 0_2, size of format 1_2) ) Align with format 1_1 or 0_1size".
  • the non-fallback UL DCI size is aligned with the non-fallback DL DCI size, that is, R15non-fallback UL DCI is aligned with R15non-fallback DL DCI.
  • the corresponding DCI size alignment steps include: Step0: Format 0_0 in CSS is aligned with format 1_0; Step1: Format 0_0 in USS is aligned with format 1_0; Step2: If format 0_1 in USS is aligned with format 0_0/1_0 in USS If they are equal, add 1-bit zero padding to format 0_1; format 1_1 is the same; format 0_2 is the same; format 1_2 is the same.
  • Step3 If it is satisfied that "the types of sizes to be processed do not exceed 5, and the C-RNTI scrambling does not exceed 4", then step over. Otherwise, continue to step 4.
  • Step4 Remove the padding in step2, recalculate format 1_0/0_0 in USS with CORESET0/initial BWP, and align the size of format 0_0 and format 1_0 in USS. At this time, CSS and format 1_0/0_0 size in USS are aligned.
  • Step5 If it is satisfied that "the types of sizes processed are not more than 5, among which C-RNTI scrambling is not more than 4", then step over. Otherwise, continue to step 6.
  • Step6 Format 0_1 and format 1_1 in the USS are aligned; after the above steps, the UE does not want to process more than 5 types of sizes, of which more than 4 types of C-RNTI scramble.
  • the UE does not want format 0_0 and format 0_1 in the USS to be the same size as format 0_2, and does not want format 1_0 and format 1_1 in the USS to be the same size as format 1_2.
  • the DCI size of the scheduled traffic channel is aligned to the fallback DCI size or the non-fallback DCI size
  • the URLLC DCI can be aligned to one of the formats of R15 through the configuration method. That is, RRC configures the format to be aligned with URLLC DCI size.
  • the corresponding DCI size alignment step may include: Step0: Format 0_0 in CSS is aligned with format 1_0; Step1: Format 0_0 in USS is aligned with format 1_0; Step2: If format 0_1 in USS is aligned with format 0_0/1_0 in USS If the size is equal, add 1 bit of zero padding to format 0_1; the same is true for format 1_1; the same is true for format 0_2; the same is true for format 1_2. Step3: If it is satisfied that "the types of sizes to be processed do not exceed 5, and the C-RNTI scrambling does not exceed 4", then step over. Otherwise, continue to step 4.
  • Step4 Remove the padding in step2, recalculate format 1_0/0_0 in USS with CORESET0/initial BWP, and align the size of format 0_0 and format 1_0 in USS. At this time, CSS and format 1_0/0_0 size in USS are aligned.
  • Step5 If it is satisfied that "the types of sizes processed are not more than 5, among which C-RNTI scrambling is not more than 4", then step over. Otherwise, continue to step 6.
  • Step6 According to RRC configuration, align URLLC DL DCI size or URLLC UL DCI size to one of R15 formats configured by RRC.
  • the UE does not want to process more than 5 types of sizes, of which more than 4 types are C-RNTI scrambled.
  • format 0_2 does not use the zero padding operation
  • the UE does not want format 0_0 in the USS to have the same size as format 0_1 and format 0_2.
  • format 1_2 does not use the zero padding operation, it does not want format 1_0 and format 1_1 in the USS. Same as the size of format 1_2.
  • the DCI size of the scheduled traffic channel is aligned to fallback DCI size or non-fallback DCI size according to a preset rule, that is, URLLC DCI size is aligned to one of the formats of R15 according to a preset rule, for example,
  • the setting principle can be: the size is the closest.
  • the URLLC DCI size is smaller than the fallback DCI size, the URLLC DCI alignment to the fallback DCI operation is not performed; when the URLLC DCI size is greater than the fallback DCI size, the size alignment operation is performed according to the size closest principle.
  • the corresponding DCI size alignment step may include: Step0: Format 0_0 in CSS is aligned with format 1_0; Step1: Format 0_0 in USS is aligned with format 1_0; Step2: If format 0_1 in USS is aligned with format 0_0/1_0 in USS If the size is equal, add 1 bit of zero padding to format 0_1; the same is true for format 1_1; the same is true for format 0_2; the same is true for format 1_2. Step3: If it is satisfied that "the types of sizes to be processed do not exceed 5, and the C-RNTI scrambling does not exceed 4", then step over. Otherwise, continue to step 4.
  • Step4 Remove the padding in step2, recalculate format 1_0/0_0 in USS with CORESET0/initial BWP, and align the size of format 0_0 and format 1_0 in USS. At this time, CSS and format 1_0/0_0 size in USS are aligned.
  • Step5 If it is satisfied that "the types of sizes processed are not more than 5, among which C-RNTI scrambling is not more than 4", then step over. Otherwise, continue to step 6.
  • Step6 align the URLLC DCI size to the fallback DCI size or non-fallback DCI size of R15 according to the condition that the DCI size meets the conditions in Table 5.
  • Table 5 is a relational table for size alignment according to the size closest principle provided by the embodiment of the present application. For example, suppose that the DCI size of one scheduling direction in URLLC DCI is N1bits, the DCI size of another scheduling direction in URLLC DCI is N2bits, the fallback DCI size is M bits, and the DCI size of one scheduling direction in non-fallback DCI is Is P bits, and the DCI size of another scheduling direction in non-fallback DCI is Q bits, where M is about 40 bits, P and Q are about 60 bits, and the scheduling directions can include: UL and DL, and assuming that URLLC DCI size is not Will be larger than eMBB DCI size.
  • Table 5 A relationship table for size alignment according to the size closest principle
  • the UE does not want to process more than 5 types of sizes, of which more than 4 types are C-RNTI scrambled.
  • format 0_2 does not use the zero padding operation
  • the UE does not want format 0_0 and format 0_1 and format 0_2 in the USS to have the same size; when format 1_2 does not use the zero padding operation, it does not want format 1_0 and format 1_1 in the USS Same as the size of format 1_2.
  • the information determining method further includes: configuring a format identifier indication field for at least one DCI format.
  • the format identifier indication field is used to indicate one of the DCI formats. For example, when the format identifier indication field is a 1-bit indication field, 0 means UL DCI and 1 means DL DCI; for another example, when the format identifier indication field is a 2-bit indication field, where 00 means format 0_1, 01 means format 1_1, 10 means format 0_2, 11 means format 1_2; for another example, when the format identifier indication field is a 2-bit indication field, 00 means format 0_1, 01 means format 0_2, 10 means format 1_1, 11 means format 1_2 .
  • the method for distinguishing different DCI formats may include: configuring the two DCI formats for performing DCI alignment Identifies the bit field.
  • the identification bit field may be 1 bit, which is used to indicate whether the new DCI format or the original DCI format; or, the identification bit field may be 2 bits, which are used to indicate the DL of the new DCI format and the UL of the new DCI format.
  • the identification bit field may be 1 bit, which is used to indicate whether the new DCI format or the original DCI format; or, the identification bit field may be 2 bits, which are used to indicate the DL of the new DCI format and the UL of the new DCI format.
  • the identification bit field may be 1 bit, which is used to indicate whether the new DCI format or the original DCI format; or, the identification bit field may be 2 bits, which are used to indicate the DL of the new DCI format and the UL of the new DCI format.
  • the format identification indication field may be configured for all DCI formats, the format identification indication field may be configured for the newly added DCI format, and the format identification indication may be configured for the newly added DCI format and fallback DCI. Field, it is also possible to configure the format identifier indication field for the two DCI formats that perform the DCI alignment operation.
  • the method for determining information further includes: distinguishing two DCI formats for performing DCI alignment operations through a format indication flag.
  • the method for distinguishing different DCI formats may include: distinguishing eMBB UL through the format indicator flag carried in the DCI format DCI is aligned with URLLC DL DCI, and eMBB DL DCI is aligned with URLLC UL DCI.
  • the number of blind detection thresholds (Maximum number of Blind Decode, BD threshold) and/or the threshold of the number of non-overlapping control resource units for channel estimation (maximum number of non-overlapping CCEs for channel estimation, CCE threshold), and define the BD threshold and/or CCE threshold with the granularity of span.
  • the CCE threshold is taken as an example to describe how to raise the CCE threshold. For the method of raising the BD threshold, the following method can also be used, which will not be repeated here.
  • (X, Y) includes at least one of the following: (1,1), (2,1), (2,2), (4,1), (4,2), (4,3) , (7,1), (7,2), (7,3).
  • the (X, Y) set of candidates reported by the UE includes at least one of the following: ⁇ (7,3),(4,3)and(7,3),(2,2)and(4,3) and(7,3) ⁇ .
  • DCI dynamic notification or RRC configuration determines the control channel element (Control Channel Element, CCE) threshold (ie C CCE) corresponding to each (X, Y), exemplarily, Table 6 Table 7 and Table 8 are all tables of relationships between X, Y, and C in an RRC configuration provided in an embodiment of the present application.
  • CCE Control Channel Element
  • Table 6 Table 7 and Table 8 are all tables of relationships between X, Y, and C in an RRC configuration provided in an embodiment of the present application.
  • an information determination method is proposed to determine the CCE threshold.
  • the information determination method includes: determining the maximum number of CCEs (denoted as max CCE per span) for each time span.
  • determining the maximum number of CCEs for each span includes one of the following: determining the maximum CCE for each span according to the number of spans in the time span pattern, the actual number of spans in the slot, and the number of restricted CCEs for each span Quantity; The maximum number of CCEs in each span is determined according to the number of restricted CCEs in each slot, the actual number of spans in the slot, and the number of restricted CCEs in each span.
  • determining the maximum number of CCEs for each span includes: determining the maximum number of CCEs for each span according to the number of spans in the time span pattern, the actual number of spans in the slot, and the number of restricted CCEs for each span.
  • the maximum number of CCEs for each span is determined by the number of spans in the span pattern (denoted as number of spans in span pattern), the actual/non-empty span number in the slot (denoted as number of monitoring spans in slot j, or , Number of non-empty spans in slot j) and the number of restricted CCEs in each span (denoted as CCE limit per span) are determined.
  • the maximum number of CCEs for each span is determined by the number of spans in the span pattern (denoted as number of spans in span pattern), the actual/non-empty span number in the slot (denoted as number of monitoring spans in slot j, or , Number of non-empty spans in slot j) and the number of restricted C
  • determining the maximum number of CCEs in each span includes: determining the maximum number of CCEs in each span according to the number of restricted CCEs in each slot, the actual number of spans in the slot, and the number of restricted CCEs in each span.
  • the maximum number of CCEs per span is determined by the number of restricted CCEs per slot (CCE limit per slot), the number of actual/non-empty spans in the slot (denoted as number of monitoring spans in slot j, or number of non-empty spans in slot j) and the number of restricted CCEs per span (denoted as CCE limit per span).
  • the value of the CCE limit per slot can be obtained by multiplying the CCE limit per span by the number of spans in the span pattern.
  • the information determination method in this embodiment obtains the maximum number of CCEs in each span through the limited number of CCEs in each span, which is applicable to different scenarios.
  • the capacity of the span in the slot can be shared with other actual spans or the space in the slot.
  • the span capability cannot be shared with other scenarios such as actual span, which increases scheduling flexibility without exceeding the UE capability.
  • the method for determining the number of restricted CCEs for each span includes: configuring the number of restricted CCEs for each span (denoted as C1).
  • the number of restricted CCEs for each span is the same and is greater than the CCE threshold of each span reported by the UE.
  • the number of restricted CCEs configured with one or more spans is greater than the CCE threshold of each span reported by the UE.
  • the base station can configure C1 of per span, and allow C1>C, where C is the CCE threshold of per span reported by the UE (that is, according to the C corresponding to the (X, Y) set reported by the UE) ).
  • C is the CCE threshold of per span reported by the UE (that is, according to the C corresponding to the (X, Y) set reported by the UE) ).
  • the number of restricted CCEs (ie C1) of each span is the same, and C1 can be greater than C; or, in the actual span of the span pattern/slot, one span, some spans, or all spans can be configured.
  • the C1 of the span is greater than the maximum number of CCEs for each span reported by the UE.
  • the capabilities of each span can be shared to different services, which improves scheduling flexibility.
  • the method for determining the number of restricted CCEs for each span may include: taking the sum of the CCE threshold of each span reported by the UE and the maximum number of CCEs in each slot as one or more spans.
  • the maximum number of CCEs in each slot is the maximum number of CCEs in each slot of R15 or the maximum number of CCEs for scheduling eMBB per slot.
  • the restricted CCE number of the span (ie C1) is obtained by superimposing the CCE threshold value (ie C) of each span reported by the UE and the maximum number of CCEs of each slot, and , C1 of the remaining spans may be equal to the CCE threshold value (ie C) of each span reported by the UE.
  • the number of restricted CCEs in the first span in the slot is equal to the sum of the maximum number of CCEs in each slot in R15 and the CCE threshold (ie C) of each span reported by the UE, and the remaining spans are limited
  • the number of CCEs (ie, C1) is equal to the CCE threshold (ie, C) of each span reported by the UE.
  • the maximum number of CCEs supported by eMBB is not allowed to be shared with the maximum number of CCEs supported by URLLC, only spans with eMBB scheduling or public message scheduling are superimposed with the CCE threshold, and the remaining spans still maintain the maximum number of CCEs supported by URLLC.
  • determining/distinguishing the CCE used by per span and the CCE used by per slot includes one of the following methods: In the case of using new DCI , Determine the respective CCEs through different search spaces; in the case of reusing normal DCI, determine the respective CCEs through different search spaces and different radio network temporary identifiers (Radio Network Temporary Identifier, RNTI)/information fields; hide through different control resource sets Include to determine the respective CCE.
  • the respective CCEs are implicitly determined through different control resource sets, and the respective search spaces are respectively associated with CORESETs within the respective CCE thresholds.
  • URLLC is associated with 16CCE CORESET
  • eMBB is associated with 56CCE CORESET. That is, it is determined by the control resource set Id number (ControlResourceSetId) in the search space (Search Space, SS) configuration parameter.
  • the CCE threshold of each span is determined by the same value or different values, which is applicable to different scenarios, such as URLLC and eMBB sharing the maximum CCE capability, or eMBB and URLLC not sharing Maximum CCE capability, thus achieving increased scheduling flexibility without exceeding the UE capability.
  • Fig. 2 is a structural block diagram of an information determination device provided by an embodiment of the present application. As shown in FIG. 2, the information determining device includes: a first determining module 220.
  • the first determining module 220 is configured to determine a time domain resource allocation table TDRA table with a physical downlink control channel PDCCH related symbol as a starting point length indicator value SLIV reference starting point.
  • the information determining device provided in this embodiment is configured to implement the information determining method of the embodiment shown in FIG. 1.
  • the implementation principle and technical effect of the information determining device provided in this embodiment are similar, and will not be repeated here.
  • the PDCCH related symbols include at least one of the following: PDCCH start symbol, PDCCH end symbol, the sum of the PDCCH start symbol and the first preset number of symbols, the PDCCH end symbol and the first preset number of symbols , Where the PDCCH start symbol is the first symbol in the time domain symbols used for PDCCH transmission, and the PDCCH end symbol is the last symbol in the time domain symbols used for PDCCH transmission.
  • determining the TDRA table with PDCCH related symbols as the SLIV reference starting point includes: determining the TDRA table with PDCCH related symbols as the SLIV reference starting point according to an independent configuration method.
  • determining the TDRA table with PDCCH related symbols as the SLIV reference starting point includes: setting the TDRA table configured with the slot boundary as the SLIV reference starting point as the TDRA table configured with the PDCCH related symbols as the SLIV reference starting point.
  • determining the TDRA table with PDCCH related symbols as the SLIV reference starting point further includes: determining whether the PDCCH related symbols as the SLIV reference starting point is in an invalid state; in the case of not being in an invalid state, using the downlink control information DCI Indicates the row index Row index in TDRA talbe.
  • the invalid state when the physical downlink shared channel PDSCH or the physical uplink shared channel PUSCH is used for scheduling, the invalid state includes at least one of the following: the SLIV reference starting point exceeds the slot boundary, or the sum of the SLIV reference starting point and length The situation beyond the slot boundary.
  • determining the TDRA table with PDCCH related symbols as the SLIV reference starting point includes: selecting a part of the row index of the TDRA table configured with the slot boundary as the SLIV reference starting point; taking the part of the row index as the PDCCH related symbols as the SLIV reference TDRA table of the starting point.
  • selecting a partial row index of the TDRA table configured with the slot boundary as the SLIV reference starting point includes: selecting the first preset number Row index as the partial row index, or selecting the part in the form of a bitmap bitmap Row index.
  • different PDCCH related symbol positions or different time spans of PDCCH use different TDRA table.
  • different PDCCH related symbol positions or different time spans use different TDRA tables, including one of the following:
  • the PDCCH of each position or the PDCCH of each span uses one TDRA table
  • X start symbol sets use X TDRA tables respectively, and the elements in the X start symbol sets are different from each other and the union includes all symbols in the slot, or the elements of X start symbol sets are independently configured;
  • X span sets use X TDRA tables, and the elements in the X span sets are different from each other and the union includes all the spans in the span pattern, or the elements of the X span sets are independently configured.
  • the embodiment of the present application also provides an information determining device, which includes: a second determining module.
  • the second determining module is set to determine the reference starting point of SLIV, the reference starting point includes: slot boundary or PDCCH related symbols.
  • determining the reference starting point of SLIV includes one of the following: determining the reference starting point of SLIV according to the traffic channel type, the traffic channel types include Type A and Type B; PDCCH related symbols are used as the reference starting point of SLIV by default; in SLIV When the sum of the reference starting point and the length exceeds the slot boundary, the SLIV reference starting point is determined as the slot boundary; the SLIV reference starting point is determined according to the PDCCH related symbol position; the SLIV reference starting point is determined according to the downlink control information DCI format of the scheduled traffic channel.
  • determining the SLIV reference starting point according to the DCI format of the scheduled traffic channel includes: determining the TDRA table with PDCCH related symbols as the SLIV reference starting point for the first DCI format, and the first DCI format includes one of the following: new
  • the DCI format is a DCI format for scheduling ultra-reliable low-latency communication URLLC.
  • the DCI size is smaller than the preset threshold, or the time domain resource allocation domain size in the DCI is smaller than the preset threshold.
  • the SLIV reference starting point configuration method includes one of the following: independent configuration of the SLIV reference starting point; PDCCH related symbols as the SLIV reference starting point by default; repeating when scheduling PUSCH In the case of transmission, the reference starting point of the SLIV is determined as the slot boundary; in the case of scheduling PUSCH repeated transmission, the reference starting point of the SLIV is determined as the PDCCH related symbol.
  • the TDRA table used for time domain resource allocation in at least two different DCI formats is determined including one of the following:
  • the second DCI format uses the TDRA table configured by Radio Resource Control RRC, the first DCI format uses the default TDRA table; the default TDRA table is independently set for at least two different DCI formats; the TDRA table is independently configured for at least two different DCI formats .
  • the embodiment of the present application also provides an information determining device.
  • the method for determining the priority corresponding to the traffic channel includes one of the following : The priority corresponding to the first DCI format of the scheduling traffic channel is higher than the priority corresponding to the second DCI format; the lowest priority corresponding to the first DCI format of the scheduling traffic channel is equal to the priority corresponding to the second DCI format.
  • an embodiment of the present application further provides an information determination device, including: an execution module.
  • the execution module is set to perform the DCI size alignment operation when a new DCI format is added;
  • the new DCI format includes: format 0_2 for scheduling uplink traffic channels and format 1_2 for scheduling downlink traffic channels; among them, size gate
  • the limit is that the type of DCI size handled by the UE in each cell is less than or equal to 4, and the cell radio network temporary identification C-RNTI scrambles no more than 3; or the size threshold is the UE in each cell
  • the processed DCI size types are less than or equal to 5 types, and the C-RNTI scrambled types do not exceed 4 types.
  • the DCI size alignment operation is performed, including : Align the size of format 0_0 and format 1_0; align the size of format 0_1 and format 1_1; align the size of format 0_2 and format 1_2.
  • the DCI size alignment operation is performed, including :
  • aligning the first type of size with the size of fallback DCI or non-fallback DCI includes one of the following:
  • aligning the first type of size to the fallback DCI or non-fallback DCI size according to the size closest principle includes:
  • the URLLC DCI size will not be aligned to the fallback DCI size
  • the alignment to the fallback DCI size or the non-fallback DCI size is performed according to the size closest principle.
  • the DCI size alignment operation is performed, including :
  • the types of DCI sizes processed by the UE in each cell are less than or equal to 4 types, of which no more than 3 types are scrambled by C-RNTI.
  • the DCI size alignment operation is performed, including One of the following: align the format 0_2 and format1_2 of the DCI of the scheduled traffic channel; align the size of the DCI format 0_2 or format1_2 of the scheduled traffic channel to the fallback DCI size; align the size of the DCI format 0_2 or format1_2 of the scheduled traffic channel Align to non-fallback DCI size; align non-fallback UL DCI size with non-fallback DL DCI size; align the DCI size of the scheduled traffic channel to fallback DCI size or non-fallback DCI size according to the pre-configuration method; Set up rules to align the DCI size of the scheduled traffic channel to fallback DCI size or non-fallback DCI size.
  • the information determining apparatus further includes: a configuration module configured to configure a format identifier indication field for at least one DCI format.
  • the information determining device further includes: a distinguishing module configured to distinguish between two DCI formats for performing a DCI alignment operation through a format indication flag.
  • an embodiment of the present application further provides an information determining device, including: a third determining module configured to determine the maximum number of CCEs for each time span.
  • determining the maximum number of CCEs for each span includes one of the following:
  • the method for determining the number of restricted CCEs for each span includes: configuring the number of restricted CCEs for each span.
  • the number of restricted CCEs for each span is the same and is greater than the CCE threshold of each span reported by the UE.
  • the number of restricted CCEs configured with one or more spans is greater than the CCE threshold of each span reported by the UE.
  • the method for determining the number of restricted CCEs for each span includes:
  • the sum of the CCE threshold of each span reported by the UE and the maximum number of CCEs in each slot is used as the number of restricted CCEs for one or more spans.
  • Fig. 3 is a schematic structural diagram of a device provided by an embodiment of the present application.
  • the device provided by this application includes a processor 310 and a memory 320.
  • the number of processors 310 in the device may be one or more.
  • One processor 310 is taken as an example in FIG. 3.
  • the number of memories 320 in the device may be one or more, and one memory 320 is taken as an example in FIG. 3.
  • the processor 310 and the memory 320 of the device may be connected through a bus or in other ways. In FIG. 3, the connection through a bus is taken as an example.
  • the device may be a base station.
  • the memory 320 can be configured to store software programs, computer-executable programs, and modules, such as program instructions/modules corresponding to the device described in any embodiment of the present application (for example, the information determining device The first determination module 220).
  • the memory 320 may mainly include a program storage area and a data storage area.
  • the program storage area may store an operating system and an application program required by at least one function; the data storage area may store data created according to the use of the device, and the like.
  • the memory 320 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state storage devices.
  • the memory 320 may include memories remotely provided with respect to the processor 310, and these remote memories may be connected to the device through a network.
  • Examples of the aforementioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.
  • the above-provided device can be configured to execute the information determination method applied to the base station provided by any of the above-mentioned embodiments, and has corresponding functions and beneficial effects.
  • the embodiment of the present application also provides a storage medium containing computer-executable instructions.
  • the computer-executable instructions are used to execute an information determination method when executed by a computer processor.
  • the method is applied to the base station side, and the method includes:
  • the physical downlink control channel PDCCH related symbols are used as the starting point length indicator value SLIV to refer to the time domain resource allocation table TDRA table of the starting point.
  • the embodiment of the present application also provides a storage medium containing computer-executable instructions.
  • the computer-executable instructions are used to execute an information determination method when executed by a computer processor.
  • the method is applied to the base station side, and the method includes: determining The reference starting point of SLIV, which includes: slot boundary or PDCCH related symbols.
  • the embodiment of the present application also provides a storage medium containing computer-executable instructions.
  • the computer-executable instructions are used to perform an information determination method when executed by a computer processor.
  • the method is applied to the base station side, and the method includes:
  • the method for determining the priority corresponding to the traffic channel includes one of the following: the priority corresponding to the first DCI format of the scheduling traffic channel is higher than that of the second DCI format Corresponding priority; the lowest priority corresponding to the first DCI format of the scheduling traffic channel is equal to the priority corresponding to the second DCI format.
  • the embodiment of the present application also provides a storage medium containing computer-executable instructions.
  • the computer-executable instructions are used to perform an information determination method when executed by a computer processor.
  • the method is applied to the base station side, and the method includes: When a new DCI format is added, the DCI size alignment operation is performed; the new DCI format includes: format 0_2 for scheduling uplink traffic channels and format 1_2 for scheduling downlink traffic channels; where the size threshold is the user in each cell
  • the type of DCI size processed by the terminal UE is less than or equal to 4, and the cell radio network temporary identification C-RNTI scrambles no more than 3 types; or the size threshold is the DCI processed by the UE in each cell size type is less than or equal to 5 types, and no more than 4 types of C-RNTI scrambling.
  • the embodiment of the present application also provides a storage medium containing computer-executable instructions.
  • the computer-executable instructions are used to execute an information determination method when executed by a computer processor.
  • the method is applied to the base station side, and the method includes: determining The maximum number of CCEs per span.
  • user equipment encompasses any suitable type of wireless user equipment, such as a mobile phone, a portable data processing device, a portable web browser, or a vehicle-mounted mobile station.
  • the various embodiments of the present application can be implemented in hardware or dedicated circuits, software, logic or any combination thereof.
  • some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor or other computing device, although the application is not limited thereto.
  • the embodiments of the present application may be implemented by executing computer program instructions by a data processor of a mobile device, for example, in a processor entity, or by hardware, or by a combination of software and hardware.
  • Computer program instructions can be assembly instructions, instruction set architecture (Instruction Set Architecture, ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or written in any combination of one or more programming languages Source code or object code.
  • the block diagram of any logical flow in the drawings of the present application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions.
  • the computer program can be stored on the memory.
  • the memory can be of any type suitable for the local technical environment and can be implemented by any suitable data storage technology, such as but not limited to read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), optical Memory devices and systems (Digital Video Disc (DVD) or Compact Disk (CD)), etc.
  • Computer-readable media may include non-transitory storage media.
  • the data processor can be any type suitable for the local technical environment, such as but not limited to general-purpose computers, special-purpose computers, microprocessors, digital signal processors (Digital Signal Processing, DSP), application specific integrated circuits (ASICs) ), programmable logic devices (Field-Programmable Gate Array, FGPA), and processors based on multi-core processor architecture.
  • DSP Digital Signal Processing
  • ASICs application specific integrated circuits
  • FGPA programmable logic devices

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请提出一种信息确定方法、装置和存储介质。该信息确定方法包括：确定以物理下行控制信道PDCCH相关符号作为起点长度指示值SLIV参考起点的时域资源分配表TDRA table。

Description

信息确定方法、装置和存储介质
本申请要求在2019年08月15日提交中国专利局、申请号为201910754997.2的中国专利申请的优先权，该申请的全部内容通过引用结合在本申请中。
技术领域
本申请涉及无线通信网络，例如涉及一种信息确定方法、装置和存储介质。
背景技术
为了支持超高可靠性和超低时延传输的特征，以较短传输时间间隔，以及以较低码率进行传输，较短传输时间间隔可以是单个或多个正交频分复用(Orthogonal Frequency Division Multiplexing，OFDM)符号。对于物理下行控制信道(Physical Downlink Control Channel，PDCCH)，可通过在时隙(slot)内多个occasion位置提供发送机会，以降低数据到达之后的等待时间，进而保证低时延传输，并通过高聚合等级保证高可靠传输。因此，如何对时域资源进行分配，是一个亟待解决的问题。
发明内容
本申请实施例提供一种信息确定方法、装置和存储介质，降低了时域资源分配所需的开销。
本申请实施例提供一种信息确定方法，包括：
确定以物理下行控制信道PDCCH相关符号作为起点长度指示值SLIV参考起点的时域资源分配表TDRA table。
本申请实施例提供一种信息确定方法，包括：
确定SLIV的参考起点，所述参考起点包括：slot边界或PDCCH相关符号。
本申请实施例提供一种信息确定方法，第一DCI格式与第二DCI格式用于业务信道调度的情况下，确定业务信道对应的优先级的方法包括以下之一：
调度业务信道的第一DCI格式所对应优先级高于第二DCI格式所对应优先级；
调度业务信道的第一DCI格式所对应最低优先级等于第二DCI格式所对应优先级。
本申请实施例提供一种信息确定方法，包括：
在增加新的DCI格式的情况下，执行DCI size对齐操作；所述新的DCI格式包括：调度上行业务信道的格式format 0_2和调度下行业务信道的format 1_2；其中，size门限值为每个小区中用户终端UE处理的DCI size种类小于或等于4种，且小区无线网络临时标识C-RNTI加扰的不超过3种；或者，size门限值为每个小区中UE处理的DCI size种类小于或等于5种，且C-RNTI加扰的不超过4种。
本申请实施例提供一种信息确定方法，包括：
确定每个时间跨度span的最大CCE数量。
本申请实施例提供一种信息确定装置，包括：
第一确定模块，设置为确定以物理下行控制信道PDCCH相关符号作为起点长度指示值SLIV参考起点的时域资源分配表TDRA table。
本申请实施例提供了一种存储介质，所述存储介质存储有计算机程序，所述计算机程序被处理器执行时实现上述任一实施例所述的方法。
附图说明
图1是本申请实施例提供的一种信息确定方法的流程图；
图2是本申请实施例提供的一种信息确定装置的结构框图；
图3是本申请实施例提供的一种设备的结构示意图。
具体实施方式
下文中将结合附图对本申请的实施例进行说明。在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互任意组合。
在新空口(New Radio，NR)R15(Release 15)系统中，时域资源分配的机制可以为：利用无线资源控制(Radio Resource Control，RRC)配置时域资源分配表(Time Domain Resource Allocation table，TDRA table)。其中，每个TDRA table包括多个行索引(Row index)，每个Row index包括：时隙偏移、起始符号、长度(符号数目)、业务信道映射类型，可通过下行控制信息(Downlink Control Information，DCI)动态指示其中一个Row index。其中，起始符号的索引可以slot边界作为参考起点，即一个具有14个符号的slot中的符号索引为0～13。为了支持超可靠低时延通信(Ultra Reliable Low Latency Communication，URLLC)的低时延高可靠需求，时域资源分配通常分配的时域资源较短，并且控制开销和分配的灵活性，以及URLLC通常支持时隙内多个PDCCH传输机会，一种方 式为将物理下行共享信道(Physical Downlink Shared Channel，PDSCH)时域资源分配起点长度指示值(Start Length Indicator Value，SLIV)的参考起点由时隙边界改为PDCCH相关符号(比如，PDCCH起始符号、PDCCH结束符号等)，以节省不必要的RRC配置，即节省DCI开销。因此，针对URLLC的时域资源分配，RRC配置的TDRA Table的配置和使用是一个亟待解决的问题。
为了节省DCI开销，本申请实施例中，提供了一种信息确定方法，节省了时域资源分配所需的DCI开销。
图1是本申请实施例提供的一种信息确定方法的流程图。如图1所示，本实施例提供的方法包括S120。
S120、确定以物理下行控制信道PDCCH相关符号作为起点长度指示值SLIV参考起点的时域资源分配表TDRA table。
在一实施例中，PDCCH相关符号至少包括以下之一：PDCCH起始符号，PDCCH结束符号，PDCCH起始符号与第一预设数量符号之和，PDCCH结束符号与第一预设数量符号之和，其中，PDCCH起始符号为传输PDCCH所使用的时域符号中的首个符号，PDCCH结束符号为传输PDCCH所使用的时域符号中的最后一个符号。在实施例中，PDCCH起始符号为传输PDCCH所使用的时域符号中的首个符号，即传输PDCCH所在搜索空间对应的控制资源集(Control Resource Set，CORESET)中的首个符号；PDCCH结束符号为传输PDCCH所使用的时域符号中的最后一个符号，即传输PDCCH所在搜索空间对应的CORESET中的最后一个符号。
可通过高层信令RRC配置候选的分配结果，然后通过DCI动态指示RRC配置的候选分配结果中的其中之一，确定本次业务信道的时域资源。其中，对于PDSCH的时域资源分配，RRC配置的参数包括：时隙偏移K0，SLIV(或者独立指示起点S和长度L)，PDSCH映射类型。其中，对于物理上行共享信道(Physical Uplink Shared Channel，PUSCH)的时域资源分配，RRC配置的参数包括：时隙偏移K2，SLIV(或者独立指示起点S和长度L)，PUSCH映射类型。对于URLLC的时域资源分配，由于通常分配的时域资源较短，并且控制开销和分配的灵活性，以及URLLC通常支持时隙内多个PDCCH传输机会，一种方式为可将PDSCH时域资源分配SLIV或S的参考起点(后续将时域资源分配SLIV或S的参考起点简称为参考起点)，由slot边界调整为调度业务信道的PDCCH起始符号，PDCCH结束符号，PDCCH起始符号+X个符号，或PDCCH结束符号+X个符号的其中一种，以节省不必要的RRC配置，节省DCI开销。其中，X为整数。在实施例中，以PDCCH起始符号为例，对参考起点的配置进行说明。
在一实施例中，确定以PDCCH相关符号作为SLIV参考起点的TDRA table，包括：按照独立配置方式，确定以PDCCH相关符号作为SLIV参考起点的TDRA table。其中，RRC配置的TDRA table是以slot边界作为SLIV的参考起点。在实施例中，可以独立配置基于PDCCH相关符号作为SLIV参考起点的TDRA table。示例性地，以PDCCH相关符号为PDCCH起始符号为例，对独立配置以PDCCH相关符号作为SLIV参考起点的TDRA table进行说明。采用两套RRC配置分别以slot边界作为SLIV参考起点的TDRA table，和以PDCCH起始符号作为SLIV参考起点的TDRA table。
示例性地，表1是本申请实施例提供的一种RRC配置的以slot边界作为SLIV参考起点的TDRA table。如表1所示，其中，每一个Row index包括时隙偏移(K0)、起始符号(S)、长度(L)、业务信道映射类型(Mapping type)，通过DCI动态指示其中一个Row index，在表1中设置有8个Row index，则DCI中需要3比特指示其中一个Row index。如果TDRA table有16个Row index，则DCI中需要4比特指示其中一个Row index；如果TDRA table有4个Row index，则DCI中需要2比特指示其中一个Row index；如果TDRA table有2个Row index，则DCI中需要1比特指示其中一个Row index；如果TDRA table有1个Row index，则DCI中无需比特指示其中一个Row index，即等同于需要0比特。在表1中，起始符号S的索引是以slot边界作为参考起点，即一个具有14个符号的slot中的符号索引为0至13。其中，如果调度PUSCH，则表1中时隙偏移从K0调整为K2，其余类型，不再赘述。其中，表1中的起始符号S即上述的参考起点。
表1 一种RRC配置的以slot边界作为SLIV参考起点的TDRA table
行索引 时隙偏移 起始符号 长度 业务信道映射类型
0 0 2 12 Type A
1 0 3 11 Type A
2 0 2 10 Type A
3 0 3 9 Type A
4 0 2 4 Type B
5 0 10 4 Type B
6 0 4 4 Type B
7 0 6 4 Type B
示例性地，表2-1和表2-2是本申请实施例提供的一种RRC配置的以PDCCH 起始符号作为SLIV参考起点的TDRA Table。如表2-1和表2-2所示，其中每一个Row index包括时隙偏移(K0)、起始符号(S)、长度(L)、业务信道映射类型(Mapping type)，通过DCI动态指示其中一个Row index。其中，起始符号S的索引是以PDCCH起始符号作为参考起点。本实施例仅以PDCCH起始符号为例进行说明，即起始符号索引为0表示为传输PDCCH所使用的时域符号中的首个符号。在一实施例中，SLIV参考起点还可以是PDCCH结束符号，或PDCCH结束符号+X个符号，或PDCCH起始符号+X个符号作为参考起点，若以PDCCH结束符号作为参考起点，则起始符号索引为0表示传输PDCCH所使用的时域符号中的最后一个符号，其余不再赘述。如果是调度PUSCH，则表2-1和表2-2中的K0换为K2，其余类型，不再赘述。
表2-1 一种RRC配置的以PDCCH起始符号作为SLIV参考起点的TDRA Table
Row index K0 S L Mapping type
0 0 0 7 Type B
1 0 0 4 Type B
2 0 0 2 Type B
3 0 0 10 Type B
4 0 1 9 Type B
5 0 1 7 Type B
6 0 1 4 Type B
7 0 1 2 Type B
表2-2 一种RRC配置的以PDCCH起始符号作为SLIV参考起点的TDRA Table
Row index K0 S L Mapping type
0 0 0 4 Type B
1 0 1 4 Type B
如表2-1和表2-2所示，通过独立配置以PDCCH起始符号作为SLIV参考起点的TDRA table，能够以更小的开销实现相同长度的多个时域位置的资源分配，提升可靠性；或者在相同开销的情况下分配多种长度的资源分配，提升调度灵活性。
在一实施例中，确定以PDCCH相关符号作为SLIV参考起点的TDRA table，包括：将以slot边界作为SLIV参考起点配置的TDRA table，作为以PDCCH相关符号作为SLIV参考起点配置的TDRA table。在实施例中，在只有一张TDRA table的基础上，基于PDCCH相关符号作为SLIV参考起点的TDRA table，可以通过TDRA table隐含得到。其中，TDRA table为以slot边界作为SLIV参考起点配置的TDRA table。在实施例中，以PDCCH相关符号为PDCCH起始符号为例，对隐含得到以PDCCH起始符号作为SLIV参考起点配置的TDRA table进行说明。表3是本申请实施例提供的一种RRC配置的以slot边界作为SLIV参考起点的TDRA Table。其中，每一个Row index包括时隙偏移、起始符号、长度(符号数目)和业务信道映射类型，通过DCI动态指示其中一个Row index。其中，起始符号(S)的索引是以slot边界作为参考起点，即一个具有14个符号的slot中的符号索引为0至13。
表3 一种RRC配置的以slot边界作为SLIV参考起点的TDRA Table
Row index K0 S L Mapping type
0 0 2 12 Type A
1 0 3 11 Type A
2 0 2 10 Type A
3 0 3 9 Type A
4 0 2 4 Type B
5 0 0 4 Type B
6 0 4 4 Type B
7 0 6 4 Type B
示例性地，如表3所示，在Mapping type为Type A的情况下，起始符号S可以为0～3；在在Mapping type为Type B的情况下，长度L有限制，可选地，长度L为2，4，7。
在一实施例中，从TDRA table中隐含得到以PDCCH相关符号作为SLIV参考起点的TDRA table的方式包括以下之一：仍然以TDRA table作为以PDCCH相关符号作为SLIV参考起点的TDRA table，并且对于无效状态不通过DCI指示；选取TDRA table中部分Row index作为以PDCCH相关符号作为SLIV参考起点的TDRA table；对TDRA table中的每一个Row index，重新配置以PDCCH相关符号作为SLIV参考起点，或者以slot边界作为SLIV参考起点。
在一实施例中，在仍然以TDRA table作为以PDCCH相关符号作为SLIV 参考起点的TDRA table的情况下，确定以PDCCH相关符号作为SLIV参考起点的TDRA table，还包括：确定以PDCCH相关符号作为SLIV参考起点是否为无效状态；在未处于无效状态的情况下，通过DCI指示TDRA table中对应的Row index。在实施例中，以以slot边界作为SLIV参考起点配置的TDRA table，作为以PDCCH相关符号作为SLIV参考起点配置的TDRA table，然后对处于无效状态的Row index不通过DCI指示。
在一实施例中，在采用PDSCH或PUSCH调度的情况下，无效状态至少包括以下一项：SLIV参考起点超出slot边界的情况，或者，SLIV参考起点与长度的总和超出slot边界的情况。示例性地，针对PDSCH或PUSCH调度，在S或S+L超出slot边界的情况下，则该Row index是无效状态；针对PUSCH重复(Repetition)调度，在S+L超出slot的情况下，则该Row index是有效状态。其中，跨/超出slot边界的含义可以为，S>13(即参考起点S跨/超出slot边界)，或S+L>14(即参考起点与长度确定的时域资源分配跨/超出slot边界)。
在一实施例中，将以slot边界作为SLIV参考起点配置的TDRA table，作为以PDCCH相关符号作为SLIV参考起点配置的TDRA table，包括以下之一：配置TDRA table中的每个Row index的SLIV参考起点为PDCCH相关符号或slot边界；对SLIV参考起点进行重解释，重解释起始符号S且S＝0。在实施例中，对TDRA table中的每个Row index，配置其是以PDCCH相关符号作为参考起点，还是以slot边界作为参考起点，即对TDRA table中每个Row index进行重新配置，然后可以将以PDCCH相关符号作为SLIV参考起点的Row index看做是以PDCCH相关符号作为SLIV参考起点的TDRA table。在一实施例中，可直接对TDRA table中的起始符号S进行重解释，即S＝0。
在一实施例中，确定以PDCCH相关符号作为SLIV参考起点的TDRA table，包括：选取以slot边界为SLIV参考起点配置的TDRA table的部分Row index；将部分Row index作为以PDCCH相关符号作为SLIV参考起点的TDRA table。在实施例中，可以直接选取以slot边界为SLIV参考起点配置的TDRA table中的部分Row index，作为以PDCCH相关符号作为SLIV参考起点的TDRA table。
在一实施例中，选取以slot边界为SLIV参考起点配置的TDRA table的部分Row index，包括：选取前第一预设数量Row index作为部分Row index，或者，以比特位图bitmap的形式选取部分Row index。在实施例中，以bitmap方式选取，以表3为例，假设bitmap为8bit的00001100，则指示表3中的Row index#4和#5作为以PDCCH相关符号作为SLIV参考起点的TDRA table，此时DCI中可使用1bit指示对应的TDRA table中的两个Row index(包括Row index#4和#5)。示例性地，直接选取前X个Row index作为以PDCCH相关符号作为参考 起点的TDRA table。在一实施例中，在通过上述隐含方式从TDRA table中得到以PDCCH相关符号作为SLIV参考起点的TDRA table的情况下，可以将参考起点S都重解释为0，即业务信道起始符号与PDCCH起始符号相同。
在一实施例中，在K0＝2的情况下，即时隙偏移为K2的情况下，通过上述隐含方式从TDRA table中得到的以PDCCH相关符号作为SLIV参考起点的TDRA table，然后对得到的以PDCCH相关符号作为SLIV参考起点的TDRA table中的起始符号S进行重解释，并重解释为0，即业务信道起始符号与PDCCH起始符号相同。
上述实施例，通过隐含方式从TDRA table中得到以PDCCH相关符号作为SLIV参考起点的TDRA table，能够以更小的开销实现相同长度的多个时域位置的资源分配，提升可靠性；或者在相同开销的情况下分配多种长度的资源分配，提升调度灵活性。
在一实施例中，在存在一个以上的TDRA table的情况下，且至少一个是以PDCCH相关符号作为SLIV参考起点的TDRA table，不同PDCCH相关符号位置或不同时间跨度(span)的PDCCH使用不全相同的TDRA table。
在一实施例中，不同PDCCH相关符号位置或不同span的PDCCH使用不全相同的TDRA table，包括以下之一：每个位置的PDCCH或每个span的PDCCH使用1种TDRA table；X个起始符号set分别使用X个TDRA table，X个起始符号set内的元素互不相同且并集为包含slot内的所有符号，或者独立配置X个起始符号set的元素；X个span set分别使用X个TDRA table，X个span set内的元素互不相同且并集为包含span pattern内的所有span，或者独立配置X个span set的元素。在实施例中，已有RRC配置的TDRA table是以slot边界作为参考起点，假设基于PDCCH相关符号作为SLIV参考起点的TDRA table可以通过独立配置或通过相关技术中的表格隐含得到，并且可以有一张或多张基于PDCCH相关符号作为参考起点的TDRA table。在实施例中，以PDCCH相关符号为PDCCH起始符号为例，对不同PDCCH相关符号位置或不同span的PDCCH使用不全相同的TDRA table进行说明。
假设有X个TDRA table，不同PDCCH起始符号位置/span的PDCCH使用不全相同的TDRA table。示例性地，假设有X种起始符号位置或X个span的PDCCH，每种起始符号位置的PDCCH或每个span的PDCCH使用1种TDRA table，共计使用X个TDRA table。比如，X＝7，此时1个slot中划分出7个互不重叠的2OS span，每个span中的PDCCH使用1种TDRA table。又如，X个RRC TDRA table分别使用X个起始符号set，X个起始符号set内的元素互不相同且并集为包含slot内的所有符号，比如，X＝2，此时1个slot中划分出7个互 不重叠的2OS(OFDM Symbol)span，此时set 0包含前3个span中的PDCCH，set 1包含后4个span中的PDCCH，两个set分别使用1种TDRA table。
在一实施例中，当RRC TDRA table有1个以上时，其中至少一个RRC TDRA table中的L长度受限。比如，L小于门限值P，可选的P为2,4,7。
本实施例中，通过隐含方式从相关技术中的表格得到以PDCCH起始符号作为参考起点的TDRA表格，能够以更小的开销实现相同长度的多个时域位置的资源分配，提升可靠性；或者在相同开销的情况下分配多种长度的资源分配，提升调度灵活性。
在一实施例中，一种信息确定方法，包括：确定SLIV的参考起点，参考起点包括：slot边界或PDCCH相关符号。其中，slot边界为slot的起始，比如，相对于slot边界的情况下，若S＝0，指的是slot内第1个符号；又如，相对于slot边界的情况下，若S＝2，指的是slot内第3个符号，依次类推，在此不再一一赘述。在一实施例中，在SLIV的参考起点存在一种以上的可能性的情况下，包括以下方式至少之一：PDCCH起始符号，或PDCCH结束符号，或PDCCH所在CORESET的起始符号，或PDCCH所在CORESET的结束符号；时隙边界，其中，时隙边界为根据调度定时K0或K2确定的时隙边界；第一个可用业务信道的起始符号，其中，业务信道为PDSCH或PUSCH；PDCCH起始符号+X个符号，或PDCCH结束符号+X个符号。在一实施例中，确定SLIV的参考起点，包括以下之一：根据业务信道类型确定SLIV的参考起点，业务信道类型包括Type A和Type B；默认以PDCCH相关符号作为SLIV的参考起点；在SLIV参考起点与长度的总和超出slot边界的情况下，确定SLIV的参考起点为slot边界；根据PDCCH相关符号位置确定SLIV的参考起点；或者，根据调度业务信道的下行控制信息DCI格式确定SLIV的参考起点。
在一实施例中，可根据预设规则或基站通知的方式确定SLIV的参考起点，在一实施例中，以SLIV的参考起点为PDCCH起始符号或slot边界为例，对SLIV的参考起点的确定方式进行说明。其中，SLIV的参考起点也可以为PDCCH结束符号，PDCCH起始符号+X个符号，PDCCH结束符号+X个符号，第一个可用业务信道的起始符号，对此并不进行限定。本实施例中，以SLIV的参考起点为PDCCH起始符号或slot边界，确定SLIV的参考起点的方式包括以下之一：
一个实施例中，根据业务信道类型确定SLIV的参考起点。比如，在业务信道为Type A的情况下，以slot边界作为SLIV参考起点；在业务信道为Type B的情况下，以PDCCH起始符号作为SLIV参考起点。
一个实施例中，默认以PDCCH起始符号作为SLIV的参考起点，当计算出现S+L超出slot边界时，回退至以slot边界作为SLIV参考起点，并重新以slot 边界确定S和S+L。
一个实施例中，根据PDCCH时域符号位置确定SLIV的参考起点。示例性地，PDCCH起始符号位于前三符号时以slot边界作为SLIV参考起点，其余情况以PDCCH起始符号作为参考起点，对此并不进行限定。
在一实施例中，根据调度业务信道的DCI格式确定SLIV的参考起点，包括：确定以PDCCH相关符号作为SLIV参考起点的TDRA table用于第一DCI格式，第一DCI格式包括以下之一：新DCI格式，调度超可靠低时延通信URLLC的DCI格式，DCI size小于预设门限值的DCI格式，DCI中时域资源分配域size小于预设门限值的DCI格式。在实施例中，根据调度业务信道的DCI格式确定SLIV的参考起点，比如，使用第一DCI格式的情况下，以PDCCH起始符号作为SLIV参考起点，其中第一DCI格式可以为调度URLLC的DCI格式，或者是Compact DCI格式，或者是DCI size小于预定/预设门限值的DCI格式，或者是DCI中时域资源分配域size小于预定/预设门限值的DCI格式。
通过本实施例所述的当存在大于一种的SLIV参考起点时，确定其中一种SLIV参考起点的方法，可以避免基站和终端理解不一致造成数据无法正确接收，从而在不同条件时可分别保证调度灵活性和时域资源分配开销降低，保证低时延高可靠的业务传输。同时，如果仅支持以PDCCH起始符号为SLIV参考起点，则对于slot中位于第2或第3符号起始的PDCCH无法调度起始符号早于PDCCH起始符号的TypeA PDSCH，可通过本实施例所述方法，通过灵活性选取SLIV的参考起点，可以避免上述调度限制。
在一实施例中，针对以PDCCH相关符号作为SLIV参考起点的TDRA table进行说明。其中，以PDCCH相关符号为PDCCH起始符号为例，对SLIV参考起点和TDRA table之间的关系进行说明。当同时存在以PDCCH起始符号和以slot边界作为SLIV参考起点时，以slot边界作为SLIV参考起点所使用的TDRA table为RRC独立配置的表格，确定以PDCCH起始符号为SLIV参考起点所使用的TDRA table的方式包括以下之一：
使用独立配置的TDRA table；使用的TDRA table为以slot边界为SLIV参考起点所使用的TDRA table中的部分Row index，比如，前X个Row index，或通过bitmap确定出的部分Row index。在一实施例中，可对得到的以PDCCH起始符号作为SLIV参考起点所使用的TDRA table中的起始符号S进行重解释，且默认S＝0；使用TDRA table为以slot边界作为SLIV参考起点所使用的TDRA table，即以PDCCH起始符号作为SLIV参考起点的TDRA table与以slot边界作为SLIV参考起点的TDRA table是相同的，并对SLIV参考起点处于无效状态的Row index不进行指示即可，或者UE不期望指示跨slot边界的时域资源分配。 本实施例中信息确定的方法，通过确定不同SLIV参考起点所对应的TDRA table，使得基站与终端对于时域资源分配的理解一致，避免终端错误接收数据。
在一实施例中，在调度PUSCH所使用的TDRA table的情况下，SLIV参考起点的配置方式，包括以下之一：独立配置SLIV参考起点；默认以PDCCH相关符号作为SLIV参考起点；在调度PUSCH重复传输的情况下，确定SLIV的参考起点为slot边界；在调度PUSCH重复传输的情况下，确定SLIV的参考起点为PDCCH相关符号。其中，以PDCCH相关符号为PDCCH起始符号为例，对调度PUSCH所使用的TDRA table中SLIV参考起点的确定方式进行说明。
在实施例中，对于调度PUSCH所使用的TDRA table，可通过以下方法之一确定：
一个实施例中，根据PUSCH是否重复传输确定使用的TDRA table。例如：对于PUSCH重复传输和非重复传输，使用不同的TDRA table，其中，调度非重复传输的PUSCH使用的TDRA table是以PDCCH起始符号作为SLIV参考起点，调度重复传输的PUSCH使用的TDRA table是以slot边界作为SLIV参考起点。又例如：使用一张TDRA table，但是跨越slot边界的Row index对重复传输有效而对非重复传输无效。
一个实施例中，对于PUSCH，默认使用PDCCH结束符号+X个符号，作为S＝0的参考起点，其中，X不小于N2，即X不小于准备PUSCH的最小时间。
一个实施例中，在调度PDSCH的情况下，使用PDCCH起始符号作为SLIV参考起点，而在调度PUSCH的情况下，使用slot边界作为SLIV参考起点。
在一实施例中，当SLIV参考起点存在一种以上的可能性时，包括以下方式至少之一：PDCCH起始符号，PDCCH结束符号，PDCCH所在CORESET的起始符号，PDCCH所在CORESET的结束符号；时隙边界，其中，时隙边界为根据调度定时K0或K2确定的时隙边界；第一个可用业务信道的起始符号，其中，业务信道为PDSCH或PUSCH；PDCCH起始符号+X个符号，或PDCCH结束符号+X个符号。
本实施例公开一种根据预设规则和/或基站通知的方式确定SLIV参考起点，在两种方式中确定其中之一，包括以下方法至少之一，以PDCCH起始符号和slot边界为例进行说明，但不限于此，可以是任意两种方式。一个实施例中，根据PUSCH是否重复传输确定使用哪种方式。例如：重复传输时以slot边界作为SLIV参考起点，非重复传输时以PDCCH起始符号作为SLIV参考起点。一个实施例中，默认都以PDCCH起始符号作为SLIV参考起点，当调度PUSCH重复传输时，回退至以slot边界作为SLIV参考起点，并重新以slot边界确定S和 S+L。
通过本实施例所述的确定PUSCH重复传输和非重复传输使用不同的TDRA table，以及当存在大于一种SLIV参考起点时，确定其中一种SLIV参考起点的方法，可以避免基站和终端理解不一致造成数据无法正确接收，从而在不同条件时分别保证了调度灵活性和降低了时域资源分配开销，保证低时延高可靠业务的传输。
在一实施例中，在增加新的DCI格式的情况下，至少两个不同的DCI格式中时域资源分配所使用的TDRA table的确定方式包括以下之一：第二DCI格式使用RRC配置的TDRA table，第一DCI格式使用默认的TDRA table；为至少两个不同的DCI格式独立设置默认的TDRA table；至少两个不同的DCI格式独立配置TDRA table。
在一实施例中，在以第一DCI格式为URLLC使用的DCI格式的情况下为例(第一DCI格式可以为调度URLLC的DCI格式，或者是Compact DCI格式，或者是DCI size小于预定/预设门限值的DCI格式，或者是DCI中时域资源分配域size小于预定/预设门限值的DCI格式)，第二DCI格式为增强移动宽带(Enhanced Mobile Broadband，eMBB)使用的DCI格式。一个实施例中，在第一DCI格式为eMBB使用的DCI格式的情况下，第二DCI格式为URLLC使用的DCI格式。其中，URLLC可以重用与eMBB相同的DCI格式，也可以使用新格式。在URLLC使用新的DCI格式的情况下，第二DCI格式和第一DCI格式是不相同的，即第二DCI格式和第一DCI格式中的其中一个为新的DCI格式，而另一个为原有的DCI格式，此时，新的DCI格式和原有的DCI格式中时域资源分配使用的TDRA table需要确定。其中，为不同DCI格式中时域资源分配使用的TDRA table确定方法包括以下之一：
一个实施例中，其中一种DCI格式(比如，第二DCI格式)使用RRC配置的TDRA table，另一种DCI格式(比如，第一DCI格式)使用默认(default)的TDRA table。例如，以调度PDSCH为例，R15的DCI format 1_1中的时域资源分配使用RRC配置的TDRA table，R16新引入的DCI format 1_2中的时域资源分配使用default TDRA table PDSCH。其中，default TDRA table可以配置为小于16行的表格，此时DCI中时域资源分配的比特size可以小于4比特。可选的，default TDRA table中以PDCCH相关符号(比如，PDCCH起始符号)作为SLIV参考起点。
一个实施例中，为不同的DCI格式配置不同的default TDRA table。例如，以调度PDSCH为例，R15的DCI format 1_1中的时域资源分配使用default TDRA table且配置为16行，R16新引入的DCI format 1_2中的时域资源分配使用default  TDRA table且配置为4行。
本实施例中所述的信息确定方法，通过特定的DCI格式确定使用以PDCCH起始符号作为SLIV参考起点的TDRA table，能够以更小的开销实现相同长度的多个时域位置的资源分配，提升可靠性；或者在相同开销的情况下分配多种长度的资源分配，提升调度灵活性。
在一实施例中，一种信息确定方法，第一DCI格式与第二DCI格式用于业务信道调度的情况下，确定业务信道对应的优先级的方法包括以下之一：调度业务信道的第一DCI格式所对应优先级高于第二DCI格式所对应优先级；或者，调度业务信道的第一DCI格式所对应最低优先级等于第二DCI格式所对应优先级。
在一实施例中，在第二DCI格式为URLLC使用的DCI格式的情况下，第一DCI格式为eMBB使用的DCI格式。一个实施例中，在第二DCI格式为eMBB使用的DCI格式的情况下，第一DCI格式为URLLC使用的DCI格式。其中，URLLC可以重用与eMBB相同的DCI格式，也可以使用新的DCI格式。在URLLC使用新的DCI格式的情况下，第二DCI格式和第一DCI格式是不相同的，即第二DCI格式和第一DCI格式中的其中一个为新的DCI格式，而另一个为原有的DCI格式，此时，新的DCI格式和原有的DCI格式可以同时用于业务信道调度，若发生时域上碰撞的情况下，确定业务信道的优先级，并根据业务信道的优先级执行后续操作。在实施例中，对于不同DCI格式调度的业务信道优先级的确定方法包括以下之一：
一个实施例中，原有的DCI格式调度的业务信道优先级低于新的DCI格式中优先级指示的任意一种优先级。比如，non-fallback DCI(即DCI format 0_1、DCI format 1_1)调度的业务所对应的优先级低于新DCI中优先级指示的任意一种优先级。即此时R15non-fallback DCI调度的业务优先级最低。
一个实施例中，原有的DCI格式调度的业务信道优先级等于新的DCI格式中优先级指示的最低优先级。比如，若新的DCI中优先级指示有1bit指示优先级为高和低两种情况，则此时R15non-fallback DCI调度的业务信道所对应的优先级等于新的DCI中优先级指示的低优先级。本实施例中的信息确定方法，通过确定不同DCI格式调度的业务信道对应的优先级，能够使得基站和终端根据优先级执行相同的后续操作，保证双方理解一致。
在实施例中，URLLC可以重用与eMBB相同的DCI格式，也可以使用新的DCI格式。当URLLC使用新的DCI格式的情况下，会出现DCI size的种类增加的情况，因此，如何确定DCI size门限值(budget)以及如何进行DCI size对齐(alignment)，是一个亟待解决的问题。其中，size门限值即为size budget。 在实施例中，为了便于说明，定义引入的新的调度PUSCH的DCI格式为DCI format 0_2，定义引入的新的调度PDSCH的DCI格式为DCI format 1_2。
在R15中，DCI size budget为“3+1”即对于一个小区(cell)，UE处理的size种类不超过4种，其中小区无线网络临时标识(Cell-Radio Network Temporary Identifier，C-RNTI)加扰的不超过3种。相关技术中的size alignment步骤包括：Step0：公共搜索空间(Common Search Space，CSS)中format 0_0与format 1_0对齐；Step1：USS中format 0_0与format 1_0对齐；Step2：如果USS中format 0_1与专有搜索空间(UE-Specific Search Space，USS)中format 0_0/1_0的size相等，则对format 0_1补1bit的零填充(zero padding)；format 1_1同理。Step3：如果满足“处理的size种类不超过4种，其中C-RNTI加扰的不超过3种”，则步骤结束(step over)。否则，继续step4。Step4：去除step2中的padding。重新以CORESET0/初始带宽部分(Bandwidth part，BWP)计算USS中format 1_0/0_0，对齐USS中format 0_0与format 1_0的size，此时CSS和USS中format 1_0/0_0size对齐。经过上述步骤后，UE不希望处理的size种类超过4种，其中C-RNTI加扰的超过3种。同时，UE不希望USS中format 0_0与format 0_1的size相同，不希望USS中format 1_0与format 1_1的size相同。
在一实施例中，一种信息确定方法，包括：在增加新的DCI格式的情况下，执行DCI size对齐操作；新的DCI格式包括：调度上行业务信道的格式format 0_2和调度下行业务信道的format 1_2；其中，size门限值为每个小区中用户终端UE处理的DCI size种类小于或等于4种，且小区无线网络临时标识C-RNTI加扰的不超过3种；或者，size门限值为每个小区中UE处理的DCI size种类小于或等于5种，且C-RNTI加扰的不超过4种。
在一实施例中，URLLC DCI包括format 0_2size和format 1_2size。在一实施例中，调度URLLC上行业务的DCI格式为DCI format 0_2，调度URLLC下行业务的DCI格式为DCI format 1_2，即URLLC DCI UL为format 0_2，URLLC DCI DL为format 1_2。当size budget不允许增加的情况下，例如，size budget仍然维持“3+1”，即对于一个cell，UE处理的size种类不超过4种，其中C-RNTI加扰的不超过3种。此时执行size alignment的方法包括以下之一：
在一实施例中，在size门限值为每个小区中UE处理的DCI size种类小于或等于4种，且C-RNTI加扰的不超过3种的情况下，执行DCI size对齐操作，包括：将format0_0和format1_0的size对齐；将format 0_1和format 1_1的size对齐；将format 0_2和format 1_2的size对齐。在实施例中，将fallback DCI(即DCI format 0_0、DCI format 1_0)的format 0_0和1_0size对齐，将non-fallback DCI的format 0_1和1_1size对齐，将URLLC DCI的format 0_2和1_2size对 齐，即共计3种。若这三种DCI格式之间出现size相等的情况，则需要补zero padding。在一实施例中，该方法不允许URLLC DCI size与R15的DCI size相同，示例性地，DCI size alignment步骤包括：Step0：CSS中format 0_0与format 1_0对齐；Step1：USS中format 0_0与format 1_0对齐；Step2：如果USS中format 0_1与USS中format 0_0/1_0的size相等，则对format 0_1补1bit的zero padding；format 1_1同理；format 0_2同理；format 1_2同理。Step3：如果满足“处理的size种类不超过4种，其中C-RNTI加扰的不超过3种”，则step over。否则，继续step4。Step4：去除step2中的padding。重新以CORESET0/初始BWP计算USS中format 1_0/0_0，对齐USS中format 0_0与format 1_0的size，此时CSS和USS中format 1_0/0_0size对齐。Step5：如果满足“处理的size种类不超过4种，其中C-RNTI加扰的不超过3种”，则step over。否则，继续step6。Step6：USS中format 0_2与format 1_2对齐；Step7：如果满足“处理的size种类不超过4种，其中C-RNTI加扰的不超过3种”，则step over。否则，继续step8。Step8：USS中format 0_1与format 1_1对齐。经过上述步骤后，UE不希望处理的size种类超过4种，其中C-RNTI加扰的超过3种。UE不希望USS中format 0_0和format 0_1，与format 0_2的size相同，不希望USS中format 1_0和format 1_1，与format 1_2的size相同。
在一实施例中，在size门限值为每个小区中UE处理的DCI size种类小于或等于4种，且C-RNTI加扰的不超过3种的情况下，执行DCI size对齐操作，包括：将format 0_2和format 1_2的size对齐，对齐为第一种size；将第一种size与fallback DCI或non-fallback DCI的size对齐。在一实施例中，URLLC DCI size与R15fallback DCI size或non-fallback DCI size对齐，即不超出3种，即将URLLC DCI的format 0_2size和format 1_2size对齐，对齐为第一种size，相当于将URLLC DCI UL size与URLLC DCI DL size对齐为第一种size。然后，将第一种size与fallback DCI size或non-fallback DCI size对齐，以达到DCI size种类不超出3种的效果。
在一实施例中，将第一种size与fallback DCI或non-fallback DCI的size对齐，包括以下之一：根据高层信令配置第一种size与fallback DCI或non-fallback DCI的size对齐；或者，根据size最接近原则将第一种size对齐至fallback DCI或non-fallback DCI的size。
在一实施例中，根据高层信令配置第一种size与R15的一种format对齐。以将第一种size对齐到R15的fallback DCI size为例，对应的DCI size alignment步骤如下：Step0：CSS中format 0_0与format 1_0对齐；Step1：USS中format 0_0与format 1_0对齐；Step2：如果USS中format 0_1与USS中format 0_0/1_0的size相等，则对format 0_1补1bit的zero padding；format 1_1同理。其中，对 format 0_2与format 1_2不做任何处理。Step3：如果满足“同时处理的size种类不超过4种，其中C-RNTI加扰的不超过3种”，则step over。否则，继续step4。Step4：USS中format 0_2与format 1_2对齐；Step5：如果满足“同时处理的size种类不超过4种，其中C-RNTI加扰的不超过3种”，则step over。否则，继续step6。Step6：将USS中format 0_2/1_2与USS中format 0_0/1_0对齐。Step7：如果满足“同时处理的size种类不超过4种，其中C-RNTI加扰的不超过3种”，则step over。否则，继续step8。Step8：去除step2中的padding，重新以CORESET0/初始BWP计算USS中format 1_0/0_0，对齐USS中format 0_0与format 1_0的size，此时CSS和USS中format 1_0/0_0size对齐；去除step6中的padding，重新对齐0_2/1_2与format 0_0/1_0。经过上述步骤后，UE不希望同时处理的size种类超过4种，其中C-RNTI加扰的超过3种。UE不希望USS中format 0_0/0_2与format 0_1的size相同，不希望USS中format 1_0/1_2与format 1_1的size相同。
在一实施例中，根据size最接近原则将第一种size对齐至fallback DCI或non-fallback DCI的size，包括：在调度业务信道的DCI size小于fallback DCI size的情况下，不对URLLC DCI size执行对齐至fallback DCI size的操作；在调度业务信道的DCI size大于fallback DCI size的情况下，以size最接近原则执行对齐至fallback DCI size或non-fallback DCI size的操作。在实施例中，当URLLC DCI size小于fallback DCI size时，不对URLLC DCI执行对齐至fallback DCI操作；当URLLC DCI size大于fallback DCI size时，以size最接近原则执行size对齐。示例性地，根据size最接近原则执行size对齐操作，对应的DCI size alignment步骤包括：Step0：CSS中format 0_0与format 1_0对齐；Step1：USS中format 0_0与format 1_0对齐；Step2：如果USS中format 0_1与USS中format 0_0/1_0的size相等，则对format 0_1补1bit的zero padding；format 1_1同理；其中，format 0_2与format 1_2不做任何处理。Step3：如果满足“同时处理的size种类不超过4种，其中C-RNTI加扰的不超过3种”，则step over。否则，继续step4。Step4：USS中format 0_2与format 1_2对齐；Step5：如果满足“同时处理的size种类不超过4种，其中C-RNTI加扰的不超过3种”，则step over。否则，继续step6。Step6：将URLLC DCI size，以size最接近原则，即根据表4中DCI size满足的条件，对齐至R15中的fallback DCI size或non-fallback DCI size。其中，表4是本申请实施例提供的一种按照size最接近原则进行size对齐的关系表。示例性地，假设URLLC DCI size为N1bits，fallback DCI size为M bits，non-fallback DCI一种调度方向的DCI size为P bits，non-fallback DCI另一种调度方向的DCI size为Q bits，其中，M大约为40bits，P、Q大约为60bits，调度方向指UL，DL，并且假设URLLC DCI size不会大于eMBB DCI size。
表4 一种按照size最接近原则进行size对齐的关系表
Figure PCTCN2020108091-appb-000001
在上述步骤之后，UE不希望同时处理的size种类超过4种，其中C-RNTI加扰的超过3种。在URLLC DCI size和fallback DCI size相同的情况下，UE不希望USS中format 0_0/0_2与format 0_1的size相同，不希望USS中format 1_0/1_2与format 1_1的size相同，或者，在URLLC DCI size和format 0_1size相同的情况下，UE不希望USS中format 0_0与format 0_1/0_2/1_2的size相同，或者，在URLLC DCI size和format 1_1size相同的情况下，不希望USS中format 1_0与format 1_1/0_2/1_2的size相同。通过本实施例所述的DCI size alignment方法，保证基站和终端在能够保证DCI size budget要求的前提下，执行相同的size对齐方法使得双方理解一致，并且不超出终端处理能力。
在一实施例中，在size门限值为每个小区中UE处理的DCI size种类小于或等于4种，且C-RNTI加扰的不超过3种的情况下，执行DCI size对齐操作，包括：在每个时间跨度的时间范围内，每个小区中UE处理的DCI size种类小于或等于4种，其中，C-RNTI加扰的不超过3种。在实施例中，当size budget不允许增加的情况下，例如，size budget仍然维持“3+1”，即对于一个cell，UE处理的size种类不超过4种，其中C-RNTI加扰的不超过3种。此时执行size alignment的方法不变，但是按照更小的时间颗粒度执行。一个实施例中，以per span的粒度维持“3+1”，即对于一个cell，UE在per span处理的size种类不超过4种，其中C-RNTI加扰的不超过3种。而总体处理的DCI size种类可以大于4种。通过本实施例所述的维持DCI size budget不变的方法，保证基站和终端在per span的粒度上能够维持DCI size budget不变的前提下，使得双方理解一致，并且不超出终端处理能力。
在size budget允许增加的情况下，例如，size budget可增加到“4+1”，即对于一个cell，UE处理的size种类不超过5种，其中C-RNTI加扰的不超过4种。
在一实施例中，在size门限值为每个小区中UE处理的DCI size种类小于或等于5种，且C-RNTI加扰的不超过4种的情况下，执行DCI size对齐操作，包括以下之一：对调度业务信道的DCI的format 0_2和format1_2执行size对齐操作；对调度业务信道的DCI format 0_2或format1_2的size对齐至fallback DCI size；对调度业务信道的DCI format 0_2或format1_2的size对齐至non-fallback DCI size；将non-fallback UL DCI size与non-fallback DL DCI size对齐；按照预先配置方式，将调度业务信道的DCI size对齐至fallback DCI size或non-fallback DCI size；根据预设规则，将调度业务信道的DCI size对齐至fallback DCI size或non-fallback DCI size。
在一实施例中，对调度业务信道的DCI的format 0_2和format1_2执行size对齐操作，即对URLLC DCI format 0_2和format 1_2执行size对齐操作。示例性地，对应的DCI size alignment步骤可以包括：Step0：CSS中format 0_0与format 1_0对齐；Step1：USS中format 0_0与format 1_0对齐；Step2：如果USS中format 0_1与USS中format 0_0/1_0的size相等，则对format 0_1补1bit的zero padding；format 1_1同理；format 0_2与format 1_2不做任何处理。Step3：如果满足“处理的size种类不超过5种，其中C-RNTI加扰的不超过4种”，则step over。否则，继续step4；Step4：USS中format 0_2与format 1_2对齐；Step5：如果满足“处理的size种类不超过5种，其中C-RNTI加扰的不超过4种”，则step over。否则，继续step6。Step6：去除step2中的padding，重新以CORESET0/初始BWP计算USS中format 1_0/0_0，对齐USS中format 0_0与format 1_0的size，此时CSS和USS中format 1_0/0_0size对齐；经过上述步骤后，UE不希望处理的size种类超过5种，其中C-RNTI加扰的超过4种。UE不希望USS中format 0_0和format 0_1，与format 0_2的size相同，不希望USS中format 1_0和format 1_1，与format 1_2的size相同。其中，step6与step4也可以互换。
在一实施例中，对调度业务信道的DCI format 0_2或format1_2的size对齐至fallback DCI size，即将其中一种URLLC DCI对齐到fallback DCI。例如，选择URLLC DCI中size接近40bit的对齐到fallback DCI，对应的DCI size alignment步骤包括：Step0：CSS中format 0_0与format 1_0对齐；Step1：USS中format 0_0与format 1_0对齐；Step2：如果USS中format 0_1与USS中format 0_0/1_0的size相等，则对format 0_1补1bit的zero padding；format 1_1同理；format 0_2与format 1_2不做任何处理。Step3：如果满足“处理的size种类不超过5种，其中C-RNTI加扰的不超过4种”，则step over。否则，继续step4；Step4：去除step2中的padding，重新以CORESET0/初始BWP计算USS中format 1_0/0_0，对齐USS中format 0_0与format 1_0的size，此时CSS和USS中format 1_0/0_0size对齐；Step5：如果满足“处理的size种类不超过5种，其中C-RNTI加扰 的不超过4种”，则step over。否则，继续step6。(例如，仅有DL或UL需要URLLC调度，则将step5作为结束步骤)Step6：将format 0_2与format 1_2中size最小的格式与format 1_0/0_0size对齐；经过上述步骤后，UE不希望处理的size种类超过5种，其中C-RNTI加扰的超过4种。在format 1_2与fallback DCI size对齐的情况下，UE不希望USS中format 0_0和format 0_1，与format 0_2的size相同；在format 0_2与fallback DCI size对齐的情况下，不希望USS中format 1_0和format 1_1，与format 1_2的size相同。其中，上述步骤中，step6与step4也可以互换。但在step6和step4互换之后，step4中的描述需要补充“去除URLLC DCI之前的padding，重新将format 0_2和format 1_2中size最小的格式(即min{size of format 0_2,size of format 1_2})与format 1_0/0_0size对齐”。
在一实施例中，可将调度业务信道的DCI format 0_2或format1_2的size对齐至non-fallback DCI size，即将其中一种URLLC DCI对齐到R15non-fallback DCI中之一。例如，在URLLC DCI size大于fallback DCI size，并且选择URLLC DCI中size较大的对齐到R15non-fallback DCI中之一。在一实施例中，将URLLC DL DCI对齐至eMBB UL DCI，或者将URLLC UL DCI对齐至eMBB DL DCI。示例性地，对应的DCI size alignment步骤包括：Step0：CSS中format 0_0与format 1_0对齐；Step1：USS中format 0_0与format 1_0对齐；Step2：如果USS中format 0_1与USS中format 0_0/1_0的size相等，则对format 0_1补1bit的zero padding；format 1_1同理；format 0_2与format 1_2不做任何处理。Step3：如果满足“处理的size种类不超过5种，其中C-RNTI加扰的不超过4种”，则step over。否则，继续step4；Step4：去除step2中的padding，重新以CORESET0/初始BWP计算USS中format 1_0/0_0，对齐USS中format 0_0与format 1_0的size，此时CSS和USS中format 1_0/0_0size对齐；Step5：如果满足“处理的size种类不超过5种，其中C-RNTI加扰的不超过4种”，则step over。否则，继续step6，(例如，仅有DL或UL需要URLLC调度，在Step5之后结束步骤)。Step6：将format 0_2size和format 1_2size中最大的格式(即max{size of format 0_2,size of format 1_2})与format 1_1或0_1size对齐；经过上述步骤后，UE不希望处理的size种类超过5种，其中C-RNTI加扰的超过4种。在format 1_2size与format 0_1size对齐的情况下，UE不希望USS中format 0_0与format 0_1与format 0_2的size相同，在format 0_2size与format 1_1size对齐的情况下，不希望USS中format 1_0与format 1_1与format 1_2的size相同。其中，上述步骤中，step6与step4也可以互换。但是在step6与step4互换之后，step4的描述也要相应补充“去除URLLC DCI之前的padding，重新将format 0_2size和format 1_2size中size最大的格式(即max{size of format 0_2,size of format 1_2})与format 1_1或0_1size对齐”。
在一实施例中，将non-fallback UL DCI size与non-fallback DL DCI size对齐，即将R15non-fallback UL DCI与R15non-fallback DL DCI对齐。示例性地，对应的DCI size alignment步骤包括：Step0：CSS中format 0_0与format 1_0对齐；Step1：USS中format 0_0与format 1_0对齐；Step2：如果USS中format 0_1与USS中format 0_0/1_0的size相等，则对format 0_1补1bit的zero padding；format 1_1同理；format 0_2同理；format 1_2同理。Step3：如果满足“处理的size种类不超过5种，其中C-RNTI加扰的不超过4种”，则step over。否则，继续step4。Step4：去除step2中的padding，重新以CORESET0/初始BWP计算USS中format 1_0/0_0，对齐USS中format 0_0与format 1_0的size，此时CSS和USS中format 1_0/0_0size对齐。Step5：如果满足“处理的size种类不超过5种，其中C-RNTI加扰的不超过4种”，则step over。否则，继续step6。Step6：USS中format 0_1与format 1_1对齐；经过上述步骤后，UE不希望处理的size种类超过5种，其中C-RNTI加扰的超过4种。UE不希望USS中format 0_0和format 0_1，与format 0_2的size相同，不希望USS中format 1_0和format 1_1，与format 1_2的size相同。
在一实施例中，按照预先配置方式，将调度业务信道的DCI size对齐至fallback DCI size或non-fallback DCI size，即可通过配置方式将URLLC DCI对齐至R15的formats其中之一。即RRC配置URLLC DCI size所要对齐的format。示例性地，对应的DCI size alignment步骤可以包括：Step0：CSS中format 0_0与format 1_0对齐；Step1：USS中format 0_0与format 1_0对齐；Step2：如果USS中format 0_1与USS中format 0_0/1_0的size相等，则对format 0_1补1bit的zero padding；format 1_1同理；format 0_2同理；format 1_2同理。Step3：如果满足“处理的size种类不超过5种，其中C-RNTI加扰的不超过4种”，则step over。否则，继续step4。Step4：去除step2中的padding，重新以CORESET0/初始BWP计算USS中format 1_0/0_0，对齐USS中format 0_0与format 1_0的size，此时CSS和USS中format 1_0/0_0size对齐。Step5：如果满足“处理的size种类不超过5种，其中C-RNTI加扰的不超过4种”，则step over。否则，继续step6。Step6：根据RRC配置，将URLLC DL DCI size或URLLC UL DCI size对齐至RRC配置的R15formats之一。经过上述步骤后，UE不希望处理的size种类超过5种，其中C-RNTI加扰的超过4种。在format 0_2未采用零填充操作的情况下，UE不希望USS中format 0_0与format 0_1与format 0_2的size相同，在format 1_2未采用零填充操作的情况下，不希望USS中format 1_0与format 1_1与format 1_2的size相同。
在一实施例中，根据预设规则，将调度业务信道的DCI size对齐至fallback DCI size或non-fallback DCI size，即根据预设规则将URLLC DCI size对齐至R15 的formats之一，例如，预设原则可以为：以size最接近为准。在一实施例中，当URLLC DCI size小于fallback DCI size时，不对URLLC DCI执行对齐至fallback DCI操作；当URLLC DCI size大于fallback DCI size时，以size最接近原则执行size对齐操作。示例性地，对应的DCI size alignment步骤可以包括：Step0：CSS中format 0_0与format 1_0对齐；Step1：USS中format 0_0与format 1_0对齐；Step2：如果USS中format 0_1与USS中format 0_0/1_0的size相等，则对format 0_1补1bit的zero padding；format 1_1同理；format 0_2同理；format 1_2同理。Step3：如果满足“处理的size种类不超过5种，其中C-RNTI加扰的不超过4种”，则step over。否则，继续step4。Step4：去除step2中的padding，重新以CORESET0/初始BWP计算USS中format 1_0/0_0，对齐USS中format 0_0与format 1_0的size，此时CSS和USS中format 1_0/0_0size对齐。Step5：如果满足“处理的size种类不超过5种，其中C-RNTI加扰的不超过4种”，则step over。否则，继续step6。Step6：以size最接近原则，即根据表5中DCI size满足的条件，将URLLC DCI size对齐至R15的fallback DCI size或non-fallback DCI size。其中，表5是本申请实施例提供的一种按照size最接近原则进行size对齐的关系表。示例性地，假设URLLC DCI中一种调度方向的DCI size为N1bits，URLLC DCI中另一种调度方向DCI size为N2bits，fallback DCI size为M bits，non-fallback DCI中一种调度方向的DCI size为P bits，non-fallback DCI中另一种调度方向的DCI size为Q bits，其中，M大约为40bits，P、Q大约为60bits，调度方向可以包括：UL和DL，并且假设URLLC DCI size不会大于eMBB DCI size。
表5 一种按照size最接近原则进行size对齐的关系表
Figure PCTCN2020108091-appb-000002
Figure PCTCN2020108091-appb-000003
经过上述步骤后，UE不希望处理的size种类超过5种，其中C-RNTI加扰的超过4种。在format 0_2未采用零填充操作的情况下，UE不希望USS中format 0_0与format 0_1与format 0_2的size相同；在format 1_2未采用零填充操作的情况下，不希望USS中format 1_0与format 1_1与format 1_2的size相同。通过本实施例所述的DCI size alignment方法，保证基站和终端在能够保证DCI size budget要求的前提下，执行相同的size对齐方法使得双方理解一致，并且不超出终端处理能力。
在一实施例中，信息确定方法，还包括：对至少一种DCI格式配置格式标识指示域。在实施例中，格式标识指示域用于指示其中一种DCI格式。例如，在格式标识指示域为1bit指示域的情况下，其中，0表示UL DCI，1表示DL DCI；又例如，在格式标识指示域为2bit指示域的情况下，其中，00表示format 0_1，01表示format 1_1，10表示format 0_2，11表示format 1_2；又例如，在格式标识指示域为2bit指示域的情况下，00表示format 0_1，01表示format 0_2，10表示format 1_1，11表示format 1_2。在实施例中，在出现新的DCI格式的size与fallback DCI(或non-fallback DCI)的size相同的情况下，不同DCI格式的区分方法可以包括：通过对执行DCI alignment的两种DCI格式配置标识比特域。在一实施例中，该标识比特域可以为1bit，用于指示新DCI格式还是原有DCI格式；或者，该标识比特域可以为2bit，用于指示新DCI格式的DL、新DCI格式的UL、原有DCI格式的DL和原有DCI格式的UL中之一。在一实施例中，可以对所有DCI格式都允许配置格式标识指示域，也可以对新增加的DCI格式允许配置格式标识指示域，也可以对新增加的DCI格式和fallback DCI允许配置格式标识指示域，也可以对执行DCI对齐操作的两种DCI格式允许配置格式标识指示域。
在一实施例中，信息确定方法，还包括：通过格式指示flag区分执行DCI 对齐操作的两种DCI格式。在实施例中，当出现新的DCI格式的size与fallback DCI(或non-fallback DCI)的size相同时，不同DCI格式的区分方法可以包括：通过DCI格式中自带的格式指示flag区分eMBB UL DCI与URLLC DL DCI对齐，eMBB DL DCI与URLLC UL DCI对齐。对于non-fallback DCI，由于UL和DL无需对齐size，即当eMBB DL DCI size为N bits，eMBB UL DCI size为M bits，且M不等N，此时将URLLC(其中，URLLC不需要高可靠且size大于fallback size)的DL DCI对齐到M bits，将URLLC的UL DCI对齐到N bits。即同为M bits的DCI在flag＝DL表示URLLC，flag＝UL表示eMBB；同为N bits的DCI在flag＝DL表示eMBB，flag＝UL表示URLLC。通过本实施例所述的具有相同size的DCI格式区分方法，保证终端在size相同的前提下准确获知具体的DCI格式，使得双方理解一致同时不增加UE处理复杂度。
在一实施例中，示例性地，对于R16URLLC终端，相对于R15，提升盲检测次数门限(Maximum number of Blind Decode，BD门限)和/或用于信道估计的非重叠控制资源单元数量门限(maximum number of non-overlapping CCEs for channel estimation，CCE门限)，并且，以span的粒度定义BD门限和/或CCE门限。在一实施例中，以CCE门限为例，对提升CCE门限进行描述。对提升BD门限的方式，也可以采用如下方法，在此不再赘述。
在一实施例中，span确定方式可以包括：通过UE上报候选的(X,Y)集合，以及PDCCH控制资源集(PDCCH CORESET)和搜索空间(search space)确定出slot中的时间跨度图样(span pattern)。其中，span之间不允许重叠，两个span起点之间的间隔不小于X个符号。其中，span时长(span duration)＝Maximum(配置的最大CORESET duration，UE上报的最小Y)，span pattern中只有最后一个span可以是较短时长(shorter duration)。其中，span的数量不超过14/X的向下取整的数值(即floor(14/X))，其中X是UE上报X取值中的最小值。示例性地，(X,Y)包含以下至少之一：(1,1)，(2,1)，(2,2)，(4,1)，(4,2)，(4,3)，(7,1)，(7,2)，(7,3)。示例性地，UE上报候选的(X,Y)集合包含以下至少之一：{(7,3),(4,3)and(7,3),(2,2)and(4,3)and(7,3)}。
在实施例中，通过预定义，DCI动态通知或RRC配置确定各个(X,Y)对应的控制信道单元(Control Channel Element，CCE)门限值(即C个CCE)，示例性地，表6、表7、表8均为本申请实施例提供的一种RRC配置的X、Y和C之间的关系表。
表6
X Y C
2 2 16
4 3 36
7 3 56
表7
X Y C
1 1 16
2 2 16
4 3 36
7 3 56
表8
X Y C
1 1 16
2 1 16
2 2 16
4 1 16
4 2 24
4 3 36
7 1 36
7 2 48
7 3 56
在一实施例中，在UE上报不同(X，Y)集合之后，如何确定每个span的最大CCE数量(即C)，是一个亟待解决的问题。
在实施例中，提出了一种信息确定方法，以确定CCE门限值。在一实施例中，信息确定方法，包括：确定每个时间跨度span的最大CCE数量(记为max CCE per span)。
在一实施例中，确定每个span的最大CCE数量，包括以下之一：根据时间跨度图样中的span数量、slot中实际span数量和每个span的受限CCE数量确定每个span的最大CCE数量；根据每个slot的受限CCE数量、slot中实际span数量和每个span的受限CCE数量确定每个span的最大CCE数量。
在一实施例中，确定每个span的最大CCE数量包括：根据时间跨度图样中 的span数量、slot中实际span数量和每个span的受限CCE数量确定每个span的最大CCE数量。在实施例中，每个span的最大CCE数量通过span pattern中的span数量(记为number of spans in span pattern)、slot中实际/非空span数量(记为number of monitoring spans in slot j，或，number of non-empty spans in slot j)和每个span的受限CCE数量(记为CCE limit per span)确定。示例性地，
Figure PCTCN2020108091-appb-000004
Figure PCTCN2020108091-appb-000005
或，
Figure PCTCN2020108091-appb-000006
在一实施例中，确定每个span的最大CCE数量，包括：根据每个slot的受限CCE数量、slot中实际span数量和每个span的受限CCE数量确定每个span的最大CCE数量。在实施例中，每个span的最大CCE数量通过每个slot的受限CCE数量(CCE limit per slot)、slot中实际/非空span数量(记为number of monitoring spans in slot j，或，number of non-empty spans in slot j)和每个span的受限CCE数量(记为CCE limit per span)确定。示例性地，
Figure PCTCN2020108091-appb-000007
Figure PCTCN2020108091-appb-000008
或，
Figure PCTCN2020108091-appb-000009
在一实施例中，CCE limit per slot的取值可以通过CCE limit per span乘以span pattern中span数量而得到。
在一实施例中，每个span的最大CCE数量可以通过每个span的受限CCE数量(CCE limit per span)确定。在一实施例中，max CCE per span＝CCE limit per span。在一实施例中，根据slot内空span能力是否可以共享给其他实际span(actual span)分别确定每个span的最大CCE数量。在不允许共享给其它实际span的情况下，可以通过每个span的受限CCE数量确定每个span的最大CCE数量；当允许共享给其它实际span的情况下，可使用除通过每个span的受限CCE数量确定每个span的最大CCE数量的任一方式，来确定每个span的最大 CCE数量。
本实施例中的信息确定方法，通过每个span的受限CCE数量得到每个span的最大CCE数量，适用于不同场景，比如，slot内空span能力可以共享给其他actual span，或者slot内空span能力不能共享给其他actual span等场景，实现了在不超出UE能力的前提下增加了调度灵活性。
在一实施例中，为了确定每个span的最大CCE数量，首先确定每个span的受限CCE数量。在一实施例中，每个span的受限CCE数量的确定方式，包括：配置每个span的受限CCE数量(记为C1)。
在一实施例中，每个span的受限CCE数量相同且大于UE上报的每个span的CCE门限值。
在一实施例中，在span pattern或slot的实际span中，配置一个或多个span的受限CCE数量大于UE上报的每个span的CCE门限值。
在一实施例中，可以通过基站配置per span的C1，且允许C1>C，其中，C为UE上报的per span的CCE门限值(即根据UE上报的(X,Y)集合对应的C)。在一实施例中，每个span的受限CCE数量(即C1)相同，且C1均可以大于C；或者，在span pattern/slot的实际span中，可以配置其中一个span，部分span，或所有span的C1为大于UE上报的每个span的最大CCE数量。本实施例，在允许eMBB支持的最大CCE数量与URLLC支持的最大CCE数量可以共享时，可以将每个span的能力共享给不同业务，提升了调度灵活性。
在一实施例中，每个span的受限CCE数量的确定方式可以包括：按照将UE上报的每个span的CCE门限值与每个slot的最大CCE数量之和，作为一个或多个span的受限CCE数量，其中所述每个slot的最大CCE数量为R15的每个slot的最大CCE数量或调度eMBB的最大CCE数量per slot。在一实施例中，在部分span中，通过叠加UE上报的每个span的CCE门限值(即C)与每个slot的最大CCE数量得到该span的受限CCE数量(即C1)，并且，其余span的C1可以等于UE上报的每个span的CCE门限值(即C)。例如：slot中首个span的受限CCE数量(即C1)等于R15中每个slot的最大CCE数量与UE上报的每个span的CCE门限值(即C)的总和，其余span的受限CCE数量(即C1)等于UE上报的每个span的CCE门限值(即C)。本实施例，在不允许eMBB支持的最大CCE数量与URLLC支持的最大CCE数量共享时，仅对于存在eMBB调度或公有消息调度的span叠加CCE门限值，其余span仍然维持URLLC支持的最大CCE数量，便于终端分类处理不同协议版本或不同业务类型，降低了终端处理复杂度。
在一实施例中，确定/区分per span使用的CCE与per slot使用的CCE(或者是确定/区分URLLC使用的CCE和eMBB使用的CCE)，包括以下方式之一：在使用new DCI的情况下，通过不同搜索空间确定各自的CCE；在重用normal DCI的情况下，通过不同搜索空间且不同无线网络临时标识(Radio Network Temporary Identifier，RNTI)/信息域确定各自的CCE；通过不同控制资源集隐含确定各自的CCE。在一实施例中，通过不同控制资源集隐含确定各自的CCE，为各自搜索空间分别关联到各自CCE门限范围内的CORESET，例如，URLLC的关联到16CCE的CORESET，而eMBB的关联到56CCE的CORESET。即通过搜索空间(Search Space，SS)配置参数中控制资源集Id号(ControlResourceSetId)确定。通过本实施例所述的一种信息确定方法，通过相同取值或非相同取值确定每个span的CCE门限，适用于不同场景，如URLLC与eMBB共享最大CCE能力，或者eMBB和URLLC不共享最大CCE能力，从而实现了在不超出UE能力的前提下，增加了调度灵活性。
图2是本申请实施例提供的一种信息确定装置的结构框图。如图2所示，信息确定装置包括：第一确定模块220。
第一确定模块220，设置为确定以物理下行控制信道PDCCH相关符号作为起点长度指示值SLIV参考起点的时域资源分配表TDRA table。
本实施例提供的信息确定装置设置为实现图1所示实施例的信息确定方法，本实施例提供的信息确定装置实现原理和技术效果类似，此处不再赘述。
在一实施例中，PDCCH相关符号至少包括以下之一：PDCCH起始符号，PDCCH结束符号，PDCCH起始符号与第一预设数量符号之和，PDCCH结束符号与第一预设数量符号之和，其中，PDCCH起始符号为传输PDCCH所使用的时域符号中的首个符号，PDCCH结束符号为传输PDCCH所使用的时域符号中的最后一个符号。
在一实施例中，确定以PDCCH相关符号作为SLIV参考起点的TDRA table，包括：按照独立配置方式，确定以PDCCH相关符号作为SLIV参考起点的TDRA table。
在一实施例中，确定以PDCCH相关符号作为SLIV参考起点的TDRA table，包括：将以slot边界作为SLIV参考起点配置的TDRA table，作为以PDCCH相关符号作为SLIV参考起点配置的TDRA table。
在一实施例中，确定以PDCCH相关符号作为SLIV参考起点的TDRA table，还包括：确定以PDCCH相关符号作为SLIV参考起点是否为无效状态；在未处于无效状态的情况下，通过下行控制信息DCI指示TDRA talbe中的行索引Row  index。
在一实施例中，在采用物理下行共享信道PDSCH或物理上行共享信道PUSCH调度的情况下，无效状态至少包括以下一项：SLIV参考起点超出slot边界的情况，或者，SLIV参考起点与长度的总和超出slot边界的情况。
在一实施例中，将以时隙slot边界作为SLIV参考起点配置的TDRA table，作为以PDCCH相关符号作为SLIV参考起点配置的TDRA table，包括以下之一：配置TDRA table中的每个Row index的SLIV参考起点为PDCCH相关符号或slot边界；对SLIV参考起点进行重解释，重解释起始符号S且S＝0。
在一实施例中，确定以PDCCH相关符号作为SLIV参考起点的TDRA table，包括：选取以slot边界为SLIV参考起点配置的TDRA table的部分Row index；将部分Row index作为以PDCCH相关符号作为SLIV参考起点的TDRA table。
在一实施例中，选取以slot边界为SLIV参考起点配置的TDRA table的部分Row index，包括：选取前第一预设数量Row index作为部分Row index，或者，以比特位图bitmap的形式选取部分Row index。
在一实施例中，在存在一个以上的TDRA table的情况下，且至少一个是以PDCCH相关符号作为SLIV参考起点的TDRA table，不同PDCCH相关符号位置或不同时间跨度span的PDCCH使用不全相同的TDRA table。
在一实施例中，不同PDCCH相关符号位置或不同时间跨度span的PDCCH使用不全相同的TDRA table，包括以下之一：
每个位置的PDCCH或每个span的PDCCH使用1种TDRA table；
X个起始符号set分别使用X个TDRA table，X个起始符号set内的元素互不相同且并集为包含slot内的所有符号，或者独立配置X个起始符号set的元素；
X个span set分别使用X个TDRA table，X个span set内的元素互不相同且并集为包含span pattern内的所有span，或者独立配置X个span set的元素。
本申请实施例还提供了一种信息确定装置，该信息确定装置包括：第二确定模块。
其中，第二确定模块，设置为确定SLIV的参考起点，参考起点包括：slot边界或PDCCH相关符号。
在一实施例中，确定SLIV的参考起点，包括以下之一：根据业务信道类型确定SLIV的参考起点，业务信道类型包括Type A和Type B；默认以PDCCH相关符号作为SLIV的参考起点；在SLIV参考起点与长度的总和超出slot边界的情况下，确定SLIV的参考起点为slot边界；根据PDCCH相关符号位置确定 SLIV的参考起点；根据调度业务信道的下行控制信息DCI格式确定SLIV的参考起点。
在一实施例中，根据调度业务信道的DCI格式确定SLIV的参考起点，包括：确定以PDCCH相关符号作为SLIV参考起点的TDRA table用于第一DCI格式，第一DCI格式包括以下之一：新DCI格式，调度超可靠低时延通信URLLC的DCI格式，DCI size小于预设门限值的DCI格式，或DCI中时域资源分配域size小于预设门限值的DCI格式。
在一实施例中，在调度PUSCH所使用的TDRA table的情况下，SLIV参考起点的配置方式，包括以下之一：独立配置SLIV参考起点；默认以PDCCH相关符号作为SLIV参考起点；在调度PUSCH重复传输的情况下，确定SLIV的参考起点为slot边界；在调度PUSCH重复传输的情况下，确定SLIV的参考起点为PDCCH相关符号。
在一实施例中，在增加新的DCI格式的情况下，至少两个不同的DCI格式中时域资源分配所使用的TDRA table的确定方式包括以下之一：
第二DCI格式使用无线资源控制RRC配置的TDRA table，第一DCI格式使用默认的TDRA table；为至少两个不同的DCI格式独立设置默认的TDRA table；至少两个不同的DCI格式独立配置TDRA table。
在一实施例中，本申请实施例还提供了一种信息确定装置，第二DCI格式与第一DCI格式用于业务信道调度的情况下，确定业务信道对应的优先级的方法包括以下之一：调度业务信道的第一DCI格式所对应优先级高于第二DCI格式所对应优先级；调度业务信道的第一DCI格式所对应最低优先级等于第二DCI格式所对应优先级。
在一实施例中，本申请实施例还提供了一种信息确定装置，包括：执行模块。
其中，执行模块，设置为在增加新的DCI格式的情况下，执行DCI size对齐操作；新的DCI格式包括：调度上行业务信道的格式format 0_2和调度下行业务信道的format 1_2；其中，size门限值为每个小区中用户终端UE处理的DCI size种类小于或等于4种，且小区无线网络临时标识C-RNTI加扰的不超过3种；或者，size门限值为每个小区中UE处理的DCI size种类小于或等于5种，且C-RNTI加扰的不超过4种。
在一实施例中，在size门限值为每个小区中UE处理的DCI size种类小于或等于4种，且C-RNTI加扰的不超过3种的情况下，执行DCI size对齐操作，包括：将format 0_0和format 1_0的size对齐；将format 0_1和format 1_1的size 对齐；将format 0_2和format 1_2的size对齐。
在一实施例中，在size门限值为每个小区中UE处理的DCI size种类小于或等于4种，且C-RNTI加扰的不超过3种的情况下，执行DCI size对齐操作，包括：
将format 0_2和format 1_2的size对齐，对齐为第一种size；将第一种size与fallback DCI或non-fallback DCI的size对齐。
在一实施例中，将第一种size与fallback DCI或non-fallback DCI的size对齐，包括以下之一：
根据高层信令配置与fallback DCI或non-fallback DCI的size对齐；
根据size最接近原则将第一种size对齐至fallback DCI或non-fallback DCI的size。
在一实施例中，根据size最接近原则将第一种size对齐至fallback DCI或non-fallback DCI的size，包括：
在调度业务信道的DCI size小于fallback DCI size的情况下，不对URLLC DCI size执行对齐至fallback DCI size的操作；
在调度业务信道的DCI size大于fallback DCI size的情况下，以size最接近原则执行对齐至fallback DCI size或non-fallback DCI size的操作。
在一实施例中，在size门限值为每个小区中UE处理的DCI size种类小于或等于4种，且C-RNTI加扰的不超过3种的情况下，执行DCI size对齐操作，包括：
在每个时间跨度的时间范围内，每个小区中UE处理的DCI size种类小于或等于4种，其中，C-RNTI加扰的不超过3种。
在一实施例中，在size门限值为每个小区中UE处理的DCI size种类小于或等于5种，且C-RNTI加扰的不超过4种的情况下，执行DCI size对齐操作，包括以下之一：对调度业务信道的DCI的format 0_2和format1_2执行size对齐操作；对调度业务信道的DCI format 0_2或format1_2的size对齐至fallback DCI size；对调度业务信道的DCI format 0_2或format1_2的size对齐至non-fallback DCI size；将non-fallback UL DCI size与non-fallback DL DCI size对齐；按照预先配置方式，将调度业务信道的DCI size对齐至fallback DCI size或non-fallback DCI size；根据预设规则，将调度业务信道的DCI size对齐至fallback DCI size或non-fallback DCI size。
在一实施例中，信息确定装置，还包括：配置模块，设置为对至少一种DCI 格式配置格式标识指示域。
在一实施例中，信息确定装置，还包括：区分模块，设置为通过格式指示flag区分执行DCI对齐操作的两种DCI格式。
在一实施例中，本申请实施例还提供了一种信息确定装置，包括：第三确定模块，设置为确定每个时间跨度span的最大CCE数量。
在一实施例中，确定每个span的最大CCE数量，包括以下之一：
根据时间跨度图样中的span数量、slot中实际span数量和每个span的受限CCE数量确定每个span的最大CCE数量；根据每个slot的受限CCE数量、slot中实际span数量和每个span的受限CCE数量确定每个span的最大CCE数量。
在一实施例中，每个span的受限CCE数量的确定方式，包括：配置每个span的受限CCE数量。
在一实施例中，每个span的受限CCE数量相同且大于UE上报的每个span的CCE门限值。
在一实施例中，在时间跨度图样span pattern或slot的实际span中，配置一个或多个span的受限CCE数量大于UE上报的每个span的CCE门限值。
在一实施例中，每个span的受限CCE数量的确定方式包括：
按照将UE上报的每个span的CCE门限值与每个slot的最大CCE数量的之和，作为一个或多个span的受限CCE数量。
图3是本申请实施例提供的一种设备的结构示意图。如图3所示，本申请提供的设备，包括：处理器310以及存储器320。该设备中处理器310的数量可以是一个或者多个，图3中以一个处理器310为例。该设备中存储器320的数量可以是一个或者多个，图3中以一个存储器320为例。该设备的处理器310以及存储器320可以通过总线或者其他方式连接，图3中以通过总线连接为例。实施例中，该设备可以为基站。
存储器320作为一种计算机可读存储介质，可用于设置为存储软件程序、计算机可执行程序以及模块，如本申请任意实施例所述的设备对应的程序指令/模块(例如，信息确定装置中的第一确定模块220)。存储器320可主要包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序；存储数据区可存储根据设备的使用所创建的数据等。此外，存储器320可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。在一些实例中，存储器320可包括相对于处理器310远程设置的存储器，这些远程存储器 可以通过网络连接至设备。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
上述提供的设备可用于设置为执行上述任意实施例提供的应用于基站的信息确定方法，具备相应的功能和有益效果。
本申请实施例还提供一种包含计算机可执行指令的存储介质，计算机可执行指令在由计算机处理器执行时用于执行一种信息确定方法，该方法应用于基站侧，该方法包括：确定以物理下行控制信道PDCCH相关符号作为起点长度指示值SLIV参考起点的时域资源分配表TDRA table。
本申请实施例还提供了一种包含计算机可执行指令的存储介质，计算机可执行指令在由计算机处理器执行时用于执行一种信息确定方法，该方法应用于基站侧，该方法包括：确定SLIV的参考起点，参考起点包括：slot边界或PDCCH相关符号。
本申请实施例还提供了一种包含计算机可执行指令的存储介质，计算机可执行指令在由计算机处理器执行时用于执行一种信息确定方法，该方法应用于基站侧，该方法包括：第二DCI格式与第一DCI格式用于业务信道调度的情况下，确定业务信道对应的优先级的方法包括以下之一：调度业务信道的第一DCI格式所对应优先级高于第二DCI格式所对应优先级；调度业务信道的第一DCI格式所对应最低优先级等于第二DCI格式所对应优先级。
本申请实施例还提供了一种包含计算机可执行指令的存储介质，计算机可执行指令在由计算机处理器执行时用于执行一种信息确定方法，该方法应用于基站侧，该方法包括：在增加新的DCI格式的情况下，执行DCI size对齐操作；新的DCI格式包括：调度上行业务信道的格式format 0_2和调度下行业务信道的format 1_2；其中，size门限值为每个小区中用户终端UE处理的DCI size种类小于或等于4种，且小区无线网络临时标识C-RNTI加扰的不超过3种；或者，size门限值为每个小区中UE处理的DCI size种类小于或等于5种，且C-RNTI加扰的不超过4种。
本申请实施例还提供了一种包含计算机可执行指令的存储介质，计算机可执行指令在由计算机处理器执行时用于执行一种信息确定方法，该方法应用于基站侧，该方法包括：确定每个时间跨度span的最大CCE数量。
以上所述，仅为本申请的示例性实施例而已，并非用于限定本申请的保护范围。
本领域内的技术人员应明白，术语用户设备涵盖任何适合类型的无线用户设备，例如移动电话、便携数据处理装置、便携网络浏览器或车载移动台。
一般来说，本申请的多种实施例可以在硬件或专用电路、软件、逻辑或其任何组合中实现。例如，一些方面可以被实现在硬件中，而其它方面可以被实现在可以被控制器、微处理器或其它计算装置执行的固件或软件中，尽管本申请不限于此。
本申请的实施例可以通过移动装置的数据处理器执行计算机程序指令来实现，例如在处理器实体中，或者通过硬件，或者通过软件和硬件的组合。计算机程序指令可以是汇编指令、指令集架构(Instruction Set Architecture，ISA)指令、机器指令、机器相关指令、微代码、固件指令、状态设置数据、或者以一种或多种编程语言的任意组合编写的源代码或目标代码。
本申请附图中的任何逻辑流程的框图可以表示程序步骤，或者可以表示相互连接的逻辑电路、模块和功能，或者可以表示程序步骤与逻辑电路、模块和功能的组合。计算机程序可以存储在存储器上。存储器可以具有任何适合于本地技术环境的类型并且可以使用任何适合的数据存储技术实现，例如但不限于只读存储器(Read-Only Memory，ROM)、随机访问存储器(Random Access Memory，RAM)、光存储器装置和系统(数码多功能光碟(Digital Video Disc，DVD)或光盘(Compact Disk，CD)光盘)等。计算机可读介质可以包括非瞬时性存储介质。数据处理器可以是任何适合于本地技术环境的类型，例如但不限于通用计算机、专用计算机、微处理器、数字信号处理器(Digital Signal Processing，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、可编程逻辑器件(Field-Programmable Gate Array，FGPA)以及基于多核处理器架构的处理器。

Claims (34)

  1. 一种信息确定方法，包括：
    确定以物理下行控制信道PDCCH相关符号作为起点长度指示值SLIV参考起点的时域资源分配表TDRA table。
  2. 根据权利要求1所述的方法，其中，所述PDCCH相关符号包括以下至少之一：PDCCH起始符号，PDCCH结束符号，PDCCH起始符号与第一预设数量符号之和，PDCCH结束符号与第一预设数量符号之和，其中，所述PDCCH起始符号为传输PDCCH所使用的时域符号中的首个符号，所述PDCCH结束符号为传输PDCCH所使用的时域符号中的最后一个符号。
  3. 根据权利要求2所述的方法，其中，所述确定以PDCCH相关符号作为SLIV参考起点的TDRA table，包括：
    按照独立配置方式，确定以所述PDCCH相关符号作为所述SLIV参考起点的TDRA table。
  4. 根据权利要求2所述的方法，其中，所述确定以PDCCH相关符号作为SLIV参考起点的TDRA table，包括：
    将以时隙slot边界作为所述SLIV参考起点配置的TDRA table，作为以所述PDCCH相关符号作为所述SLIV参考起点配置的TDRA table。
  5. 根据权利要求4所述的方法，其中，所述确定以PDCCH相关符号作为SLIV参考起点的TDRA table，还包括：
    确定所述以PDCCH相关符号作为SLIV参考起点是否为无效状态；
    在所述以PDCCH相关符号作为SLIV参考起点未处于所述无效状态的情况下，通过下行控制信息DCI指示所述TDRA table中的行索引Row index。
  6. 根据权利要求5所述的方法，其中，在采用物理下行共享信道PDSCH或物理上行共享信道PUSCH调度的情况下，所述无效状态包括以下至少之一：所述SLIV参考起点超出所述slot边界的情况，所述SLIV参考起点与长度的总和超出所述slot边界的情况。
  7. 根据权利要求4所述的方法，其中，所述将以时隙slot边界作为所述SLIV参考起点配置的TDRA table，作为以所述PDCCH相关符号作为所述SLIV参考起点配置的TDRA table，包括以下之一：
    配置所述TDRA table中的每个Row index的SLIV参考起点为所述PDCCH相关符号或所述slot边界；
    对所述SLIV参考起点进行重解释，重解释起始符号S且S＝0。
  8. 根据权利要求2所述的方法，其中，所述确定以PDCCH相关符号作为SLIV参考起点的TDRA table，包括：
    选取以slot边界为所述SLIV参考起点配置的TDRA table的部分行索引；
    将所述部分行索引作为以所述PDCCH相关符号作为所述SLIV参考起点的TDRA table。
  9. 根据权利要求8所述的方法，其中，所述选取以slot边界为所述SLIV参考起点配置的TDRA table的部分行索引，包括：
    选取前第一预设数量的行索引作为所述部分行索引，或者，以比特位图bitmap的形式选取所述部分行索引。
  10. 根据权利要求2所述的方法，其中，在存在一个以上的TDRA table，且至少一个TDRA table是以所述PDCCH相关符号作为所述SLIV参考起点的情况下，不同PDCCH相关符号位置的PDCCH或不同时间跨度span的PDCCH使用不全相同的TDRA table。
  11. 根据权利要求10所述的方法，其中，所述不同PDCCH相关符号位置的PDCCH或不同时间跨度span的PDCCH使用不全相同的TDRA table，包括以下之一：
    每个位置的PDCCH或每个span的PDCCH使用1种TDRA table；
    X个起始符号集合set分别使用X个TDRA table，所述X个起始符号set内的元素互不相同且并集为包含slot内的所有符号，或者独立配置所述X个起始符号set的元素；
    X个span set分别使用X个TDRA table，所述X个span set内的元素互不相同且并集为包含时间跨度图样span pattern内的所有span，或者独立配置所述X个span set的元素。
  12. 一种信息确定方法，包括：
    确定起点长度指示值SLIV或起始符号S的参考起点，所述参考起点包括：时隙slot边界或物理下行控制信道PDCCH相关符号。
  13. 根据权利要求12所述的方法，其中，所述确定SLIV参考起点，包括以下之一：
    根据业务信道类型确定所述SLIV或S的参考起点，所述业务信道类型包括Type A和Type B；
    默认以所述PDCCH相关符号作为所述SLIV参考起点；在所述SLIV参考起点与长度的总和超出所述slot边界的情况下，确定所述SLIV参考起点为所述 slot边界；
    根据PDCCH相关符号位置确定所述SLIV参考起点；
    根据调度业务信道的下行控制信息DCI格式确定所述SLIV参考起点。
  14. 根据权利要求13所述的方法，其中，所述根据调度业务信道的DCI格式确定所述SLIV参考起点，包括：
    确定以所述PDCCH相关符号作为所述SLIV参考起点的时域资源分配表TDRA table用于第一DCI格式，所述第一DCI格式包括以下之一：新DCI格式，调度超可靠低时延通信URLLC的DCI格式，下行控制信息大小DCI size小于预设门限值的DCI格式，或DCI中时域资源分配域size小于预设门限值的DCI格式。
  15. 根据权利要求12所述的方法，其中，在调度物理下行共享信道PUSCH所使用的TDRA table的情况下，所述SLIV参考起点的配置方式，包括以下之一：
    独立配置所述SLIV参考起点；
    默认以所述PDCCH相关符号作为所述SLIV参考起点；
    在调度PUSCH重复传输的情况下，确定所述SLIV参考起点为所述slot边界；
    在调度PUSCH非重复传输的情况下，确定所述SLIV参考起点为所述PDCCH相关符号。
  16. 根据权利要求14所述的方法，其中，在增加新的DCI格式的情况下，至少两个不同的DCI格式中时域资源分配所使用的TDRA table的确定方式包括以下之一：
    第二DCI格式使用无线资源控制RRC配置的TDRA table，所述第一DCI格式使用默认的TDRA table；
    为至少两个不同的DCI格式独立设置默认的TDRA table；
    为至少两个不同的DCI格式独立配置TDRA table。
  17. 一种信息确定方法，在第一下行控制信息DCI格式与第二DCI格式用于业务信道调度的情况下，确定业务信道对应的优先级的方法包括以下之一：
    调度业务信道的所述第一DCI格式所对应优先级高于所述第二DCI格式所对应优先级；
    调度业务信道的所述第一DCI格式所对应最低优先级等于所述第二DCI格 式所对应优先级。
  18. 一种信息确定方法，包括：
    在增加新的下行控制信息DCI格式的情况下，执行下行控制信息大小DCI size对齐操作；所述新的DCI格式包括：调度上行业务信道的格式format 0_2和调度下行业务信道的格式format 1_2；其中，size门限值为每个小区中用户终端UE处理的DCI size种类小于或等于4种，且小区无线网络临时标识C-RNTI加扰的DCI size种类不超过3种；或者，size门限值为每个小区中UE处理的DCI size种类小于或等于5种，且C-RNTI加扰的DCI size种类不超过4种。
  19. 根据权利要求18所述的方法，其中，在所述size门限值为每个小区中UE处理的DCI size种类小于或等于4种，且C-RNTI加扰的DCI size种类不超过3种的情况下，所述执行DCI size对齐操作，包括：
    将format 0_0和format 1_0的size对齐；
    将format 0_1和format 1_1的size对齐；
    将format 0_2和format 1_2的size对齐。
  20. 根据权利要求18所述的方法，其中，在所述size门限值为每个小区中UE处理的DCI size种类小于或等于4种，且C-RNTI加扰的DCI size种类不超过3种的情况下，所述执行DCI size对齐操作，包括：
    将format 0_2和format 1_2的size对齐，对齐为第一种size；
    将所述第一种size与回退fallback DCI或非回退non-fallback DCI的size对齐。
  21. 根据权利要求20所述的方法，其中，所述将所述第一种size与fallback DCI或non-fallback DCI的size对齐，包括以下之一：
    根据高层信令配置所述第一种size与所述fallback DCI或所述non-fallback DCI的size对齐；
    根据size最接近原则将所述第一种size对齐至所述fallback DCI或所述non-fallback DCI的size。
  22. 根据权利要求21所述的方法，其中，所述根据size最接近原则将所述第一种size对齐至所述fallback DCI或所述non-fallback DCI的size，包括：
    在调度业务信道的DCI size小于fallback DCI size的情况下，不对超可靠低时延通信URLLC DCI size执行对齐至fallback DCI size的操作；
    在调度业务信道的DCI size大于fallback DCI size的情况下，以所述size最 接近原则执行对齐至fallback DCI size或non-fallback DCI size的操作。
  23. 根据权利要求18所述的方法，其中，在所述size门限值为每个小区中UE处理的DCI size种类小于或等于4种，且C-RNTI加扰的DCI size种类不超过3种的情况下，所述执行DCI size对齐操作，包括：
    在每个时间跨度的时间范围内，每个小区中UE处理的DCI size种类小于或等于4种，其中，C-RNTI加扰的DCI size种类不超过3种。
  24. 根据权利要求18所述的方法，其中，在所述size门限值为每个小区中UE处理的DCI size种类小于或等于5种，且C-RNTI加扰的DCI size种类不超过4种的情况下，所述执行DCI size对齐操作，包括以下之一：
    对调度业务信道的DCI format 0_2和format 1_2执行size对齐操作；
    对调度业务信道的DCI format 0_2或format 1_2的size对齐至fallback DCI size；
    对调度业务信道的DCI format 0_2或format1_2的size对齐至non-fallback DCI size；
    将non-fallback UL DCI size与non-fallback DL DCI size对齐；
    按照预先配置方式，将调度业务信道的DCI size对齐至fallback DCI size或non-fallback DCI size；
    根据预设规则，将调度业务信道的DCI size对齐至fallback DCI size或non-fallback DCI size。
  25. 根据权利要求18所述的方法，还包括：对至少一种DCI格式配置格式标识指示域。
  26. 根据权利要求25所述的方法，还包括：
    通过格式指示flag区分执行DCI对齐操作的两种DCI格式。
  27. 一种信息确定方法，包括：
    确定每个时间跨度span的最大控制信道单元CCE数量。
  28. 根据权利要求27所述的方法，其中，所述确定每个span的最大CCE数量，包括以下之一：
    根据时间跨度图样中的span数量、时隙slot中实际span数量和每个span的受限CCE数量确定每个span的最大CCE数量；
    根据每个slot的受限CCE数量、slot中实际span数量和每个span的受限CCE数量确定每个span的最大CCE数量。
  29. 根据权利要求28所述的方法，其中，所述每个span的受限CCE数量的确定方式，包括：
    配置所述每个span的受限CCE数量。
  30. 根据权利要求29所述的方法，其中，各个span的受限CCE数量均相同且大于UE上报的每个span的CCE门限值。
  31. 根据权利要求29所述的方法，其中，在时间跨度图样span pattern或slot的实际span中，配置至少一个span的受限CCE数量大于UE上报的每个span的CCE门限值。
  32. 根据权利要求28所述的方法，其中，所述每个span的受限CCE数量的确定方式包括：
    将UE上报的每个span的CCE门限值与每个slot的最大CCE数量之和，作为至少一个span的受限CCE数量。
  33. 一种信息确定装置，包括：
    第一确定模块，设置为确定以物理下行控制信道PDCCH相关符号作为起点长度指示值SLIV参考起点的时域资源分配表TDRA table。
  34. 一种存储介质，所述存储介质存储有计算机程序，所述计算机程序被处理器执行时实现权利要求1-32中任一项所述的信息确定方法。
PCT/CN2020/108091 2019-08-15 2020-08-10 信息确定方法、装置和存储介质 WO2021027753A1 (zh)

Priority Applications (6)

Application Number Priority Date Filing Date Title
EP20852512.1A EP3829245A4 (en) 2019-08-15 2020-08-10 INFORMATION DETERMINATION PROCESS, APPARATUS AND MEMORY MEDIA
KR1020217005438A KR20210028261A (ko) 2019-08-15 2020-08-10 정보 결정 방법 및 디바이스, 그리고 저장 매체
MX2021002136A MX2021002136A (es) 2019-08-15 2020-08-10 Metodo y dispositivo de determinacion de informacion y medio de almacenamiento.
JP2021510309A JP7129555B2 (ja) 2019-08-15 2020-08-10 情報決定方法およびデバイスならびに記憶媒体
US17/158,861 US11792790B2 (en) 2019-08-15 2021-01-26 Information determination method and device, and storage medium
US18/487,332 US20240163873A1 (en) 2019-08-15 2023-10-16 Information determination method and device, and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910754997.2 2019-08-15
CN201910754997.2A CN110536448A (zh) 2019-08-15 2019-08-15 一种信息确定方法、装置和存储介质

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/158,861 Continuation US11792790B2 (en) 2019-08-15 2021-01-26 Information determination method and device, and storage medium

Publications (1)

Publication Number Publication Date
WO2021027753A1 true WO2021027753A1 (zh) 2021-02-18

Family

ID=68663522

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/108091 WO2021027753A1 (zh) 2019-08-15 2020-08-10 信息确定方法、装置和存储介质

Country Status (8)

Country Link
US (2) US11792790B2 (zh)
EP (1) EP3829245A4 (zh)
JP (1) JP7129555B2 (zh)
KR (1) KR20210028261A (zh)
CN (2) CN112911721B (zh)
MX (1) MX2021002136A (zh)
TW (1) TW202112112A (zh)
WO (1) WO2021027753A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022192442A1 (en) * 2021-03-12 2022-09-15 Intel Corporation Time domain resource allocation for data transmissions
WO2022204159A1 (en) * 2021-03-23 2022-09-29 Intel Corporation Time-domain resource allocation for transport block over multiple slot (tboms) transmissions

Families Citing this family (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111867074B (zh) * 2019-04-30 2023-04-18 华为技术有限公司 接收数据和发送数据的方法、通信装置
CN112911721B (zh) 2019-08-15 2023-06-09 中兴通讯股份有限公司 一种信息确定方法、装置和存储介质
US11729786B2 (en) * 2020-01-07 2023-08-15 Qualcomm Incorporated Physical downlink control channel for low complexity operation
KR20220140481A (ko) * 2020-02-12 2022-10-18 지티이 코포레이션 시간 도메인 자원 할당을 구성하기 위한 방법 및 장치
US11711817B2 (en) * 2020-04-10 2023-07-25 Qualcomm Incorporated Rate matching for a physical downlink shared channel (PDSCH)
CN113517946A (zh) * 2020-04-10 2021-10-19 华为技术有限公司 一种通信方法及装置
CN113541901A (zh) * 2020-04-22 2021-10-22 维沃移动通信有限公司 非周期srs的时隙偏移指示方法和设备
US20220039141A1 (en) * 2020-07-30 2022-02-03 Qualcomm Incorporated Downlink control information size configuration for multiple carrier scheduling scenarios
CN114070491B (zh) * 2020-08-07 2023-01-20 大唐移动通信设备有限公司 一种半静态反馈码本的确定方法、装置及存储介质
CN112235868B (zh) * 2020-12-16 2021-04-13 京信通信系统（中国）有限公司 资源调度方法、装置、基站、终端设备和存储介质
CN113163494B (zh) * 2020-12-24 2024-04-30 浪潮通信技术有限公司 Nr物理共享信道时域参数的自适应配置方法、装置及介质
CN112637958B (zh) * 2020-12-30 2024-02-02 京信网络系统股份有限公司 资源调度方法、装置、基站、用户设备和存储介质
CN115333689A (zh) * 2021-05-10 2022-11-11 维沃移动通信有限公司 Dci大小对齐方法和设备
CN113453361B (zh) * 2021-06-28 2022-07-05 中信科移动通信技术股份有限公司 一种上行时域资源指示方法及系统
CN115622667A (zh) * 2021-07-13 2023-01-17 维沃移动通信有限公司 下行控制信息发送、获取方法、装置、终端及网络侧设备
WO2023075519A1 (en) * 2021-10-29 2023-05-04 Samsung Electronics Co., Ltd. Method and apparatus for harq-ack feedback in wireless communication system

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190149365A1 (en) * 2018-01-12 2019-05-16 Intel Corporation Time domain resource allocation for mobile communication
CN110536448A (zh) * 2019-08-15 2019-12-03 中兴通讯股份有限公司 一种信息确定方法、装置和存储介质

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8169956B2 (en) * 2007-01-26 2012-05-01 Qualcomm Incorporated Mapping uplink acknowledgement transmission based on downlink virtual resource blocks
US20180199229A1 (en) * 2015-07-26 2018-07-12 Lg Electronics Inc. Method for transmitting information on priority for d2d link with relay ue in wireless communication system and apparatus therefor
CN109475000B (zh) * 2017-09-08 2022-08-26 展讯半导体(南京)有限公司 共享信道资源分配方法、装置及网络侧设备
CN110771197B (zh) * 2017-11-24 2022-11-29 Lg 电子株式会社 无线通信系统中用于报告信道状态信息的方法及其装置
CN110022193B (zh) * 2018-01-09 2020-08-11 维沃移动通信有限公司 解调参考信号的传输方法及网络设备
US10863494B2 (en) * 2018-01-22 2020-12-08 Apple Inc. Control signaling for uplink multiple input multiple output, channel state information reference signal configuration and sounding reference signal configuration
CN110138525B (zh) * 2018-02-09 2022-07-08 维沃移动通信有限公司 解调参考信号的配置方法、传输方法、终端及网络侧设备

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190149365A1 (en) * 2018-01-12 2019-05-16 Intel Corporation Time domain resource allocation for mobile communication
CN110536448A (zh) * 2019-08-15 2019-12-03 中兴通讯股份有限公司 一种信息确定方法、装置和存储介质

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Benefits of Enhanced PDCCH Monitoring Capability for URLLC", 3GPP DRAFT; R1-1906109 BENEFITS OF ENHANCED PDCCH MONITORING CAPABILITY FOR URLLC, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Reno, Nevada, US; 20190513 - 20190517, 13 May 2019 (2019-05-13), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051727566 *
HUAWEI, HISILICON: "Remaining issues on DCI contents and formats", 3GPP DRAFT; R1-1803707 REMAINING ISSUES ON DCI CONTENTS AND FORMATS FINAL, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Sanya, China; 20180416 - 20180420, 15 April 2018 (2018-04-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051426004 *
NOKIA, NOKIA SHANGHAI BELL: "Summary of contributions on PUSCH enhancements for NR eURLLC (AI 7.2.6.3)", 3GPP DRAFT; R1-1907695_SUMMARY OF CONTRIBUTIONS ON 7.2.6.3_EURLLC PUSCH ENH, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Reno, Nevada, US; 20190513 - 20190517, 16 May 2019 (2019-05-16), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051739981 *
WILUS INC.: "On DCI enhancement for NR URLLC", 3GPP DRAFT; R1-1907384_DCI_FINAL, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Reno, USA; 20190513 - 20190517, 13 May 2019 (2019-05-13), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051728822 *
ZTE: "On PDCCH enhancements for NR URLLC", 3GPP DRAFT; R1-1910100 ON PDCCH ENHANCEMENTS FOR NR URLLC, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Chongqing, China; 20191014 - 20191020, 8 October 2019 (2019-10-08), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051788907 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022192442A1 (en) * 2021-03-12 2022-09-15 Intel Corporation Time domain resource allocation for data transmissions
WO2022204159A1 (en) * 2021-03-23 2022-09-29 Intel Corporation Time-domain resource allocation for transport block over multiple slot (tboms) transmissions

Also Published As

Publication number Publication date
EP3829245A4 (en) 2021-12-15
US20210153228A1 (en) 2021-05-20
US11792790B2 (en) 2023-10-17
CN112911721B (zh) 2023-06-09
JP2021536179A (ja) 2021-12-23
KR20210028261A (ko) 2021-03-11
EP3829245A1 (en) 2021-06-02
TW202112112A (zh) 2021-03-16
CN110536448A (zh) 2019-12-03
US20240163873A1 (en) 2024-05-16
MX2021002136A (es) 2021-04-28
CN112911721A (zh) 2021-06-04
JP7129555B2 (ja) 2022-09-01

Similar Documents

Publication Publication Date Title
WO2021027753A1 (zh) 信息确定方法、装置和存储介质
US10820338B2 (en) User equipments, base stations and methods for RNTI-based PDSCH downlink slot aggregation
US11395291B2 (en) Allocating transmission resources in communication networks that provide low latency services
CN108521321B (zh) 用于发送和接收下行链路控制信息的方法和装置
US8095141B2 (en) Use of supplemental assignments
TWI699132B (zh) 用於行動通訊系統之基地台及使用者裝置
AU2018328285B2 (en) User equipments, base stations and methods for RNTI-based PDSCH downlink slot aggregation
US11039448B2 (en) Resource scheduling method and apparatus
US20190281623A1 (en) Granting Resources To A Wireless Device
WO2021018196A1 (zh) 免调度传输资源的配置方法、装置、发送设备及接收设备
US11902185B2 (en) Sidelink information transmission method, communications device, and network device
WO2017045180A1 (zh) 一种控制信息的传输方法、装置以及系统
US11212707B2 (en) Allocation of resources to a wireless device
WO2021062580A1 (zh) 确定侧行链路传输资源的方法和装置
WO2019191966A1 (zh) 可靠性传输方法及相关产品
US11949630B2 (en) Information processing method, device, equipment, and computer readable storage medium
JP2022107029A (ja) 端末デバイス及び端末デバイスにより実行される方法
WO2021082956A1 (zh) 一种pdcch调度方法、基站及存储介质
WO2020030142A1 (zh) 确定调制编码阶数表类型的方法及装置
WO2023206306A1 (zh) 数据接收方法、数据发送方法以及装置
TW202329667A (zh) 數據傳輸的終止方法、裝置、設備及存儲介質
OA17520A (en) Method and apparatus for sending and receiving downlink control information.

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 20217005438

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2021510309

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2020852512

Country of ref document: EP

Effective date: 20210226

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

Ref document number: 20852512

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE