Multi-tti scheduling dcI design

Abstract

In one aspect, a network node is configured for multi-interval scheduling of downlink or uplink transmissions to or from a wireless device. The network node sends (702) configuration information to the wireless device, the configuration information indicating one or both of a maximum number of scheduling intervals that can be scheduled with a single scheduling message and a time domain resource allocation data structure to be used when multi-interval scheduling is used. Alternatively, the network node schedules (802) one or more downlink or uplink transmissions to or from a wireless communication device using a single scheduling message that schedules the transmissions in each of a plurality of scheduling intervals. The number of scheduling intervals is indicated in the scheduling message by a dedicated field or by a time resource assignment indication that implicitly or explicitly indicates the number of scheduling intervals.

Description

Technical Field

[0001] This disclosure generally relates to the field of wireless network communications, and more specifically to network nodes that schedule downlink or uplink transmissions to or from wireless communication devices at multiple intervals. Background Technology

[0002] The New Radio (NR) standard, developed by members of the 3rd Generation Partnership Project (3GPP), is designed to provide services for a variety of scenarios, such as enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and machine-type communication (MTC). Each of these services has different technical requirements. For example, the general requirements for eMBB are high data rates with medium latency and medium coverage, while URLLC services require low-latency, high-reliability transmission, but perhaps with medium data rates.

[0003] One solution for low-latency data transmission is shorter transmission time intervals (TTIs). In NR, in addition to transmissions within time slots, mini-slot transmissions are also allowed to reduce latency. A mini-slot can consist of any number of Orthogonal Frequency Division Multiplexing (OFDM) symbols from 1 to 14. It should be noted that the concepts of time slots and mini-slots are not specific to any particular service, meaning that mini-slots can be used for eMBB, URLLC, or other services.

[0004] resource blocks

[0005] Figure 1 This illustrates an example of radio resources in NR. In Rel-15 NR, a radio device (User Equipment or UE) can be configured with up to four carrier bandwidth portions in the downlink, where a single downlink carrier bandwidth portion is active at a given time. A UE can be configured with up to four carrier bandwidth portions in the uplink, where a single uplink carrier bandwidth portion is active at a given time. If the UE is configured with a supplementary uplink, the UE can additionally be configured with up to four carrier bandwidth portions in the supplementary uplink, where a single supplementary uplink carrier bandwidth portion is active at a given time.

[0006] For a given set of parameters μ i The carrier bandwidth portion defines a set of adjacent physical resource blocks (PRBs), ranging from 0 to... The numbering is used, where i is the index of the carrier bandwidth portion. A resource block (RB) is defined in the frequency domain as 12 consecutive subcarriers.

[0007] Parameter set

[0008] As shown in Table 1, NR supports multiple OFDM parameter sets. μ The subcarrier spacing Δ for the carrier bandwidth portion is configured by different higher-level parameters for the downlink and uplink respectively. f and cyclic prefix.

[0009]

[0010] physical channel

[0011] Downlink physical channels correspond to a set of resource elements carrying information originating from higher layers. The following downlink physical channels are defined: Physical Downlink Shared Channel (PDSCH); Physical Broadcast Channel (PBCH); and Physical Downlink Control Channel (PDCCH).

[0012] The PDSCH is the primary physical channel for unicast downlink data transmission, and it is also used for the transmission of RAR (Random Access Response), certain system information blocks, and paging information. The PBCH carries basic system information required for UE access to the network. The PDCCH is used to transmit downlink control information (DCI) (mainly scheduling decisions required to receive the PDSCH), and uplink scheduling authorizations for transmission on the PUSCH.

[0013] Uplink physical channels correspond to a set of resource elements carrying information originating from higher layers. The following uplink physical channels are defined: Physical Uplink Shared Channel (PUSCH); Physical Uplink Control Channel (PUCCH); and Physical Random Access Channel (PRACH).

[0014] PUSCH is the uplink counterpart of PDSCH. The UE uses PUCCH to transmit uplink control information, including Hybrid Automatic Repeat Request (HARQ) acknowledgments and channel state information reports. PRACH is used for random access preamble transmission.

[0015] Frequency resource allocation for PUSCH

[0016] Generally, the UE should use the resource allocation field in the DCI carried in the detected PDCCH to determine the RB assignment in the frequency domain for the PUSCH or PDSCH. For PUSCH carrying msg3 during random access, the frequency domain resource assignment is signaled by using uplink (UL) permission included in the RAR.

[0017] In NR, two frequency resource allocation schemes are supported for PUSCH and PDSCH: Type 0 and Type 1. Which type is used for PUSCH / PDSCH transmission is defined by parameters configured by Radio Resource Control (RRC), or directly specified in the corresponding DCI or UL approval in the RAR (in which case, Type 1 is used).

[0018] Within the UE's active carrier bandwidth portion, the RB index arrangement for uplink / downlink type 0 and type 1 resource allocation is determined. Upon detecting a PDCCH intended for the UE, the UE should first determine the uplink / downlink carrier bandwidth portion (BWP), and then determine the resource allocation within that portion. The ULBWP for the PUSCH carrying msg3 is configured by higher-layer parameters.

[0019] Time resource allocation for PUSCH

[0020] When a UE is scheduled to transmit a transport block, the time-domain resource assignment field value of the DCI... m Provide row indexes to the tables configured by the assigned RRC. m +1. Indexed row definition: slot offset K 2. Start and length indicators SLIV Or simply the start symbol. S and allocation length L And the PUSCH mapping type to be applied in PUSCH transmission.

[0021] The time slot that the UE should use to transmit PUSCH is determined by K2. Where n is the time slot with DCI scheduling, K 2 is a parameter set based on PUSCH, and μ PUSCH and μ PDCCH These are the subcarrier spacing configurations used for PUSCH and PDCCH, respectively.

[0022] Determine the start symbol relative to the start of the time slot from the start and length indicator SLIV of the indexed line. S and the symbols assigned to PUSCH S Count of consecutive symbols L :

[0023] if ,but ,otherwise ,in .

[0024] The UE should consider the S and L combinations defined in Table 2 as valid PUSCH assignments.

[0025]

[0026] Either apply the default PUSCH time-domain allocation A according to Table 3, or apply... pusch-ConfigCommon or pusch-Config Higher-level configurations in pusch-AllocationList .value j It depends on the subcarrier spacing and is defined in Table 4.

[0027]

[0028]

[0029] It can be transmitted via higher-level signaling pusch-AllocationList The configuration is as follows:

[0030]

[0031] These fields are defined as follows. Field k2 corresponds to L1 parameter "K2" (see TS 38.214, Clause 6.1.2.1). When this field is not present, the UE applies value 1 when PUSCH SCS is 15 / 30kHz, value 2 when PUSCH SCS is 60kHz, and value 3 when PUSCH SCS is 120kHz. The fields are defined in Clause 6.1.2.1 of TS 38.214. mappingType Field startSymbolAndLength It is an index that gives a valid combination of (jointly encoded) start symbol and length as a start and length indicator (SLIV). The network configures this field so that allocations do not cross slot boundaries (see TS38.214, Clause 6.1.2.1).

[0032] Modulation order, redundancy version, and transport block size are determined.

[0033] To determine the modulation order, target code rate, redundancy version, and transport block size of the physical uplink shared channel, the UE should first read the 5-bit modulation and coding scheme field from the DCI. I MCS To determine the modulation order ( O m ) and target bitrate R Next, the Redundancy Version (RV) field in the DCI will be read to determine the redundancy version, and the "CSI Request" bit field will be checked. The UE should use the layer number ( ), the total number of PRBs allocated ( nPRB (This is used to determine the transport block size.)

[0034] In the 3GPP NR standard, DCI is received via PDCCH. PDCCH can carry DCI in messages with different formats. DCI formats 0_0 and 0_1 are used to convey uplink clearance for transmitting physical layer data channels in the uplink (PUSCH) to the UE, while DCI formats 1_0 and 1_1 are used to convey downlink clearance for transmitting physical layer data channels in the downlink (PDSCH). Other DCI formats (2_0, 2_1, 2_2, and 2_3) are used for other purposes, such as transmitting time slot format information, reserved resources, and transmit power control information.

[0035] Time slot structure

[0036] NR time slots consist of several OFDM symbols (7 or 14 symbols when the OFDM subcarrier spacing is ≤60kHz, and 14 symbols when the OFDM subcarrier spacing is >60kHz). Figure 2 This shows a subframe with 14 OFDM symbols. Figure 2 In the middle, T s and T symb These represent the time slot and OFDM symbol duration, respectively. Additionally, the time slot can be shortened to accommodate a DL / UL transition period or both DL and UL transmissions. Figure 3 The text indicates potential changes.

[0037] In addition, NR defines Type B scheduling, also known as microslots. Microslots are shorter than time slots (from 1 or 2 symbols to 1 less than the number of symbols in a time slot, according to the current protocol) and can begin at any symbol. Microslots are used if the transmission duration of a time slot is too long or the start of the next time slot (time slot alignment) occurs too late. Applications of microslots include delay-critical transmissions (in which case both the microslot length and the frequency of microslots are important) and unlicensed spectrum, where transmissions should begin immediately after a successful listen-before-speak (here, the frequency of microslots is particularly important). Figure 4 An example of a microtimeslot is shown in the image.

[0038] Time slot structure

[0039] For a node to be permitted to transmit in unlicensed spectrum (e.g., the 5 GHz band), it typically needs to perform a free channel assessment (CCA). This process usually involves sensing medium freeness for a certain time interval. Medium freeness can be sensed in different ways, such as through energy detection, preamble detection, or virtual carrier sensing. The latter means that the node reads control information from other transmitting nodes that notify it when transmission has ended. After sensing medium freeness, the node is usually allowed to transmit for a certain amount of time, sometimes called a transmission opportunity (TXOP). The length of the TXOP depends on the type and specifications of the CCA performed, but typically varies from 1 ms to 10 ms.

[0040] Compared to, for example, Long Term Evolution (LTE) Licensed Assisted Access (LAA) (where access to the channel is limited to 500µs intervals), the microslot concept in NR allows nodes to access the channel with much finer granularity. Using, for example, a 60kHz subcarrier spacing and two-symbol microslots in NR, access to the channel can be achieved at 36µs intervals. Summary of the Invention

[0041] NR allows scheduling of multiple time slots, each with its own UL (Upper Limit) grant. This can easily exhaust PDCCH resources when the scheduled UL bursts are long and / or when the number of UEs to be scheduled is large. The latter increases the constraints on the scheduler and unnecessarily wastes PDCCH resources.

[0042] Some solutions involve scheduling multiple time slots; however, the focus is on how to signal time resource allocation. These solutions do not consider behavioral changes when multi-slot scheduling is activated in conjunction with other features, or how to signal parameters other than time resource allocation.

[0043] The embodiments described herein pertain to techniques that can schedule either one or multiple PUSCHs using a single scheduling message (e.g., a single DCI). Advantages include reduced overhead on the PDCCH by using a single permission to send scheduling information for multiple time slots, enabling efficient UL scheduling and transmission when multiple start / end positions are supported. Another advantage is increased flexibility when scheduling multiple time slots.

[0044] According to some embodiments, a method in a network node of a wireless communication system for multi-interval scheduling of downlink or uplink transmissions to or from a wireless communication device includes sending configuration information to the wireless device, the configuration information specifying a maximum number of scheduling intervals that can be scheduled with a single scheduling message and one or both of a time-domain resource allocation data structure to be used when using multi-interval scheduling.

[0045] "Scheduling interval" can refer to time slots, micro-time slots, subframes, etc. The key point is that each of these intervals can be scheduled individually within a scheduling message (at least in the frequency domain). The scheduling message can refer to DCI or similar dynamic scheduling messages.

[0046] According to some embodiments, a method in a network node of a wireless communication system for multi-interval scheduling of downlink or uplink transmissions to or from a wireless communication device includes: scheduling one or more downlink or uplink transmissions to or from the wireless communication device using a single scheduling message, the single scheduling message scheduling the transmissions in each of a plurality of scheduling intervals. The number of scheduling intervals is indicated in the scheduling message by a dedicated field or by a time resource allocation indicator, the time resource allocation indicator implicitly or explicitly indicating the number of scheduling intervals.

[0047] According to some embodiments, a method in a wireless communication device operating in a wireless communication system for multi-interval scheduling of downlink or uplink transmissions to or from the wireless communication device includes: receiving configuration information from a network node in the wireless communication system, the configuration information indicating one or both of a time-domain resource allocation data structure to be used when using multi-interval scheduling.

[0048] According to some embodiments, a method in a wireless communication device operating in a wireless communication system for multi-interval scheduling of downlink or uplink transmissions to or from the wireless communication device includes: receiving, in a single scheduling message, scheduling information for one or more downlink or uplink transmissions to or from the wireless communication device, the single scheduling message transmitting transmissions scheduled in each of a plurality of scheduling intervals. The number of scheduling intervals is indicated in the scheduling message by a dedicated field or by a time resource allocation indication, the time resource allocation indication implicitly or explicitly indicating the number of scheduling intervals.

[0049] Of course, the present invention is not limited to the features and advantages described above. Those skilled in the art will recognize other features and advantages after reading the following detailed description and viewing the accompanying drawings. Attached Figure Description

[0050] Figure 1 An example of radio resources in NR is shown.

[0051] Figure 2 The subframe is shown.

[0052] Figure 3 This shows the time slot change.

[0053] Figure 4 The micro-timeslots of two OFDM symbols are shown.

[0054] Figure 5 The use of the TDRA table is shown according to some embodiments.

[0055] Figure 6 The diagram shown is a block diagram of a network node according to some embodiments.

[0056] Figure 7 A flowchart illustrating a method for use in a network node according to some embodiments is shown.

[0057] Figure 8 A flowchart is shown for another method for use in a network node according to some embodiments.

[0058] Figure 9 The diagram shown is a block diagram of a wireless device according to some embodiments.

[0059] Figure 10 A flowchart illustrating a method for use in a wireless device according to some embodiments is shown.

[0060] Figure 11 A flowchart is shown for another method in a wireless device according to some embodiments.

[0061] Figure 12 A telecommunications network connected to a host computer via an intermediate network is illustrated schematically according to some embodiments.

[0062] Figure 13 This is a general block diagram of a host computer that communicates with a user equipment via a base station through a partial wireless connection, according to some embodiments.

[0063] Figure 14 , Figure 15 , Figure 16 and Figure 17 This is a flowchart illustrating an example method implemented in a communication system comprising a host computer, a base station, and user equipment.

[0064] Figure 18 This is a block diagram illustrating the functional implementation of a network node according to some embodiments.

[0065] Figure 19 This is a block diagram illustrating the functional implementation of a wireless device according to some embodiments. Detailed Implementation

[0066] Exemplary embodiments of the present disclosure will now be described more fully below with reference to the accompanying drawings, in which examples of embodiments of the inventive concept are illustrated. However, the inventive concept may be implemented in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete and will fully convey the scope of the inventive concept to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be implicitly assumed to be present / used in another embodiment. Any two or more embodiments described herein may be combined with each other. The embodiments are described in relation to LTE or NR, but are applicable to other radio access technologies or alternatives that may be relevant.

[0067] The embodiments described herein pertain to techniques for scheduling one or more PUSCHs using a single scheduling message (e.g., a single DCI). The term PUSCH is used to refer to uplink transmissions within a specific interval. Therefore, PUSCH transmissions in consecutive intervals (e.g., consecutive time slots) are referred to herein as both "multi-time slot" transmissions and "multi-PUSCH" transmissions. These are intended to refer to the same thing. Similarly, multi-time slot scheduling and multi-PUSCH scheduling are intended to refer to the same thing, while "multi-interval scheduling" is slightly broader (as it can include other types of physical channels). Although PUSCH scheduling is discussed in the embodiments, the techniques described herein can also be applied to multi-time slot PDSCH scheduling.

[0068] In one embodiment, the functionality to schedule multiple PUSCHs using a single DCI is enabled or disabled via RRC. The RRC configuration includes one or more of the following parameters: the maximum number of PUSCHs that can be scheduled using a single DCI; and the number of PUSCHs used when this functionality is enabled. PUSCH-TimeDomainResourceAllocation Data structure. If this functionality is enabled via RRC, the same DCI format indicates whether one or more PUSCHs are scheduled. As a non-restrictive example, DCI 0_1 can schedule one or more PUSCHs.

[0069] According to some embodiments, via DCI, or through: a dedicated field, wherein the bit width of the field can be based on maxNumberOfSchedSlots (For example, log2( maxNumberOfSchedSlots The number of PUSCHs to be scheduled is configured either implicitly or explicitly within the time resource allocation; or it is signaled to notify the scheduler of the number of PUSCHs. Nslots As an example, PUSCH-TimeDomainResourceAllocation It contains a column that specifies the number of PUSCHs scheduled.

[0070] In some embodiments, if a dedicated field is used to send a signal notification Nslots Then at least two situations can exist. If NslotsSpecifying 1 maps time resource allocation to the existing PUSCH-allocation table (Rel-15). If Nslots If the value is greater than 1, then the time resource allocation is mapped to the new... PUSCH-MultiSlotTimeDomainResourceAllocation . PUSCH- MultiSlotTimeDomainResourceAllocation It contains one or more of the following: row index; PUSCH mapping type (mapping type for the first number of scheduling slots); PUSCH mapping type 2 (mapping type for the remaining scheduling slots); K2, slot offset for the first scheduling PUSCH; S (Start symbol); L (The length of the pusch); and startAndEndSlot (A flag indicating one of two options). Option 1 is the possibility of using a single DCI to schedule one or more PUSCHs with gaps in between. Start symbol S and length L The value is applied to each scheduling slot using the corresponding DCI. Option 2 schedules one or more PUSCHs using a single DCI without any gaps in between. (Start symbol) S It can be the first scheduling slot, and the length of the PUSCH L It can be the last scheduled slot. Implicitly, it indicates that for all other scheduled slots in a multi-slot scheduling, the start symbol is #0, and the length is the same as the slot.

[0071]

[0072] Instead of specifying PUSCH mapping types 1 and 2 separately, one of the following alternatives can be used: specifying a single PUSCH mapping type applicable to all scheduled PUSCHs; and specifying a single PUSCH mapping type, using mapping type B to transmit a first number of scheduled time slots, with the specified mapping type applicable starting from the second time slot.

[0073] In some embodiments, if code block group feedback is configured and activated, at least two scenarios exist. If Nslots Specifying 1 indicates the Redundancy Version (RV) and New Data Indicator (NDI) for a time slot (i.e., RV is two bits, NDI is one bit), and DCI indicates the code block group (CBG) transmission information (CBGTI) corresponding to the scheduled PUSCH. If Nslots If the value is >1, CBGTI is not supported when multiple PUSCHs are being scheduled in the DCI. The DCI does not contain this field, and each of the RV and NDI bit widths is equal to the maximum number of scheduled slots in the RRC configuration. Zero padding may be required to align the DCI length for both cases.

[0074] In some embodiments, the Time Domain Resource Allocation (TDRA) table for multi-slot scheduling can be constructed as a simple extension of single-slot scheduling. The TDRA table provides information for each individual PUSCH. A separate K2 table exists corresponding to each PUSCH. S , L Mapping type. As a variation of these embodiments, the number of columns depends on the maximum number of scheduled PUSCHs. For example, if the maximum number of scheduled PUSCHs is 4, then the table provides four K2, S , L Mapping type values, each corresponding to a schedulable PUSCH.

[0075] The number of scheduled PUSCHs is implicitly specified by the TDRA table. If a PUSCH is not to be scheduled, the corresponding (K2, S , L Set the mapping type to an invalid or null value. Figure 5 This example shows a TDRA table that provides time resource allocation for up to four PUSCHs. Each row specifies the (K2, ...) corresponding to each PUSCH. S , L (Mapping type). In this setting, the number of scheduled slots is obtained from the table configured by RRC. For example, in lines 0 to 5, four PUSCHs are scheduled. In lines 6 to 8, the number of scheduled PUSCHs is three. To indicate that point, the entry corresponding to the fourth PUSCH is left blank or set to an invalid value.

[0076] In another variation of these embodiments, instead of increasing the number of columns in the table, one or more of the following fields are replaced with a list of values, with one list entry for each of the specified number of scheduling slots: PUSCH mapping type; S (Start symbol); L (The length of the PUSCH); and K2 (the offset of the scheduled PUSCH). In yet another change, the RCC configuration... PUSCH-TimeDomainResourceAllocation It is (K2, mapping type and) startSymbolAndLength The sequence is expanded—so that gNB provides PUSCH- TimeDomainResourceAllocation A list. This list can be of fixed or variable size. The maximum size of the list depends on the maximum number of schedulable PUSCHs.

[0077] In some embodiments, if the data structure PUSCH-MultiSlotTimeDomainResourceAllocati on The number of entries is 2 N Where N is used to specify PUSCH-MultiSlotTimeDomainResourceAllocat ionIf the available DCI bit depth is specified for a given line, then the Media Access Control Command Element (MAC CE) message is used to "activate" or "select". PUSCH-MultiSlotTimeDomainResourceAllocation A subset of N or fewer entries in the data structure. Then, the available DCI code points are mapped to the entries in the selected subset.

[0078] In some embodiments, allocations are assigned consecutively (i.e., without gaps in between), and each allocation can be shorter than or longer than (or equal to) a time slot. A start symbol S is provided for the first allocation, and then only the length of each allocation is needed. This can be a single parameter applicable to all allocations (i.e., they all have the same length, i.e., the same number of symbols), or a length indicator for each allocation (i.e., a list of lengths). In these embodiments, Nslots The parameter specifies the number of allocations, not the number of time slots. Therefore, in this embodiment, Nslots Parameters can be obtained from Nallocations Parameter substitution.

[0079] In some embodiments, allocations (each allocation may contain fewer or more symbols than a time slot, or an equal number of symbols as a time slot (i.e., 14)) are allocated with gaps between allocations (the length of which may be zero or more symbols). The length of each intermediate gap and each allocation can be the same for all allocations, requiring only a single length indicator and a single gap length indicator. Alternatively, the allocation length can be the same for all allocations (i.e., a single allocation length indicator), but the gap length is specified for each gap (e.g., as a list). Another alternative is that the gap length is the same for all gaps (i.e., a single gap length indicator), but the allocation length is specified for each allocation (e.g., as a list). Yet another alternative is that both the allocation length and the gap length are provided as multiple parameters or values ​​(e.g., as a list), one for each allocation and one for each gap. In these embodiments, Nslots The parameter specifies the number of allocations, not the number of time slots. Therefore, in these embodiments, Nslots Parameters can be Nallocations The parameter has been replaced.

[0080] In another variation of the foregoing embodiment, there are multiple assignments with potentially varying lengths and intermediate gaps of varying lengths. The symbols for the assignments are designated as bitmaps (e.g., where 0 represents a gap and 1 represents an assignment). This embodiment is constrained to non-zero gaps in all locations. The reason for constraining these embodiments to assignments with non-zero intermediate gaps is that if there is no gap between two assignments, some further indication would be needed to specify the boundary between the two assignments. As a further enhancement, such indications and / or rules could be provided to enable multiple assignments with non-zero intermediate gaps.

[0081] One way to do this is to provide a single maxAllocationLength The instruction, which should be interpreted as such, states that if a series of consecutive bits set to one includes a... maxAllocationLength More bits, but less than 2× maxAllocationLength The series of bits is then divided into two equal-sized allocations. If the number of bits in the series is odd, the first allocation has one more bit than the second allocation (equivalently, the rule could also be that the second allocation has one more bit than the first allocation). This can be generalized to more than two consecutive allocations, and for example, the following rule / algorithm can be applied. N is the number of symbols in consecutive allocations (i.e., the number of consecutive bits set to 1 in the bitmap). D is the CEILING(N / maxAllocationLength (i.e., N / ) maxAllocationLength The symbols in this series of allocations are divided into D separate allocations: Allocation1, ..., AllocationD. The length of each allocation, in terms of the number of symbols, is determined as follows: B = FLOOR(N / D) (i.e., N / D is rounded to the nearest smaller integer, also known as integer division); and R = MODULO(N / D). Each allocation (1...D) is assigned B consecutive symbols. Then, if R > 0, the remaining R symbols (which are less than D) are distributed one symbol to each consecutive allocation (starting from allocation 1) until all R bits are used up.

[0082] In some embodiments, which may be applied as an extension of any or all other embodiments, the DCI indicates whether the UE is allowed to use only one of the multiple allocations (i.e., providing redundant allocations to proactively compensate for potential Listen-After-Speak (LBT) failures) or all or a subset thereof. If the UE is allowed to use only one or a subset of the allocations, then which / which of these allocations is predetermined, as it depends on the outcome of the LBT process. Once the UE has managed to utilize as many of the allocations it is allowed to utilize (or less if it has emptied its UL buffer of pending UL data) of the allocations, it can ignore any remaining allocations.

[0083] Where the UE is allowed to use multiple allocations, a HARQ procedure ID and possible RVs can be provided for each allocation. An alternative to providing a HARQ procedure ID for each allocation could be to specify a single HARQ procedure ID for all allocations, or to specify a HARQ procedure ID for the first allocation and then specify for the remaining consecutive allocations that a sequential loop should be used to progressively process the other configured HARQ procedures. For RV indications, an alternative to providing RV indications for each allocation could be, in the case of a single HARQ procedure ID, to provide only one RV indication to be used for the first allocation, and then RVs for the remaining allocations in the order specified in Table 6.1.2.1-2 of TS 38.214 (hereinafter referred to as Table 5).

[0084]

[0085] If multiple HARQ procedures are used, a first RV will be provided for each allocation, and then each HARQ procedure will follow the table mentioned (and documented) above for the remaining allocations. Another piece of information, which can be provided for each allocation or all allocations at once, is the circular prefix (CP) to be used.

[0086] In all the above cases where additional information is provided for each allocation, this can be applied to all allocations, i.e., providing the same number of information instances as the number of allocations (ignoring information provided only once for all allocations), or per allowed allocation, i.e., the same number of information instances as the allocations allowed for the UE to use (ignoring information provided only once for all allocations). In the latter case, since parameters (such as HARQ procedure ID or RV) are not bound to the actual time / frequency resource allocation, the gNB must keep track of the order in which it receives transmissions from the UE in order to be able to apply the correct configuration parameters (e.g., HARQ procedure ID or RV) to the received PUSCH transmissions.

[0087] An additional option available when the UE is allowed to use multiple assignments is to specify the LBT category (if any) to be used before each assignment (excluding assignments that are immediately preceding them without any gaps). The same LBT category can be specified for all assignments (requiring only a single indication), or the LBT category can be specified for each assignment (e.g., as a list). A possible simplification of this indication could be, for example, configuring two different LBT categories, and a bitmap (one bit per assignment) indicating which of the two LBT categories should be applied to each assignment.

[0088] Another piece of information that can be provided—either the same single indication for all allocations or for each allocation—is the LBT priority (in the case of LBT category 4). Yet another piece of information that can be provided—either the same single indication for all allocations or for each allocation—is the energy detection threshold to be used during the LBT process. Devices such as UEs use the energy detection threshold when monitoring the radio channel during the LBT process, and if the detected energy is above the threshold, the device determines that the channel is occupied and avoids transmission. Conversely, if the detected energy is below the threshold, the device determines that the channel is idle and begins transmission using the channel.

[0089] A possible use case for providing an energy detection threshold per allocation could be for later allocations than earlier ones, for example, by increasing the threshold (raising it to make it more lenient) in the following ways: increasing the threshold in small steps for each allocation; or having the same energy detection threshold for all allocations except the last one, while increasing the threshold for the last allocation. The purpose of increasing the threshold for later allocations is to increase the chance of a successful LBT process (because the UE may have already failed LBT for earlier allocations) and thus the UE can successfully access the channel.

[0090] In various other embodiments, multiple allocation scheduling configurations, which may be quite detailed, are configured via RRC signaling (system information or dedicated signaling) or MAC signaling, or even specified in the standard. The configuration can be referenced using an index in the DCI. This can be applied to the entire multiple allocation (all parameters) or a portion thereof (some of the parameters). This type of indication is particularly useful when a multiple allocation contains so much information that explicitly providing the multiple allocation in the DCI would exceed the available bits in the DCI. When the UE is allowed to use multiple allocations and configuration information is provided for each allocation, as described above in the preceding embodiments, the multiple allocation can be an example of a type of multiple allocation that can benefit from this type of index-based indication in the DCI. An example of this type of index indication would be an index that points to the entire multiple allocation configuration (containing parameters for all PUSCH transport resource allocations).

[0091] In some embodiments that may complement any other embodiments, different frequency resources may be allocated for different allocations in a DCI that comprises multiple resource allocations. Different allocations may, for example, specify frequency resources on another subband (i.e., another portion of the spectrum), where, for example, channel occupancy may be different if per-subband LBT is used. Another conceivable use case is to avoid some other activity occupying frequency resources. For example, a UE may be allocated four allocations, where the first three use frequencies of the DRS (but do not overlap with the DRS in time), while the fourth allocation overlaps with the DRS in time and is therefore allocated other frequency resources that do not overlap with the DRS. This could be a frequency on one side of the DRS or a frequency that spans the DRS on both sides, and the UE is assumed (or instructed) to perform rate matching around the DRS.

[0092] Frequency resources can be specified for each allocation in the DCI (e.g., as a list). Alternatively (to save bits), two frequency allocations can be provided, and for each allocation, there is an indication of which of the two frequency allocations applies. An attractive approach would be to expand the frequency domain resource allocation table from a single column to multiple columns, similar to how the time domain resource allocation table was expanded to multiple columns. Thus, a single (table row) index would indicate the frequency resource allocations used for multiple PUSCH allocations (where each column represents one allocation). If compared with... Figure 5 In the multi-column TDRA table combination, in both the multi-column time-domain resource allocation table and the multi-column frequency-domain resource allocation table, the columns should be ordered in the same way and associated with the PUSCH resource allocation, such that the nth column is associated with the nth PUSCH resource allocation in the DCI. The principle is the same in both multi-tables. In some embodiments, the energy detection threshold may increase with later allocations.

[0093] The above embodiments can be implemented by network nodes and corresponding wireless devices. Figure 6 This network node 30 is shown; it can be called a "base station". Network node 30 can be a gNB. Although Figure 6 Network node 30 is shown, but network node operation can be performed by other types of network access nodes or relay nodes. In the non-limiting embodiments described below, network node 30 will be described as being configured to operate as a cellular network access node in an NR network, but these embodiments are not limited to NR or cellular-only technologies.

[0094] Those skilled in the art will readily understand how each type of node can be adapted, for example, by modifying and / or adding suitable program instructions for the processing circuit 32 to execute, to implement one or more of the methods and signaling processes described herein.

[0095] Network node 30 facilitates communication between wireless terminals, other network access nodes, and / or the core network. Network node 30 may include communication interface circuitry 38, which includes circuitry for communicating with other nodes in the core network, radio nodes, and / or other types of nodes in the network for the purpose of providing data and / or cellular communication services. Network node 30 communicates with wireless devices using antenna 34 and transceiver circuitry 36. Transceiver circuitry 36 may include transmitter circuitry, receiver circuitry, and associated control circuitry, which are collectively configured to transmit and receive signals according to radio access technology for the purpose of providing cellular communication services.

[0096] Network node 30 also includes one or more processing circuits 32 operatively associated with transceiver circuitry 36 and, in some cases, with communication interface circuitry 38. Processing circuitry 32 includes one or more digital processors 42, such as one or more microprocessors, microcontrollers, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), complex programmable logic devices (CPLDs), application-specific integrated circuits (ASICs), or any combination thereof. More generally, processing circuitry 32 may include fixed circuitry or programmable circuitry specifically configured via the execution of program instructions to implement the functionality taught herein, or may include some mixture of fixed circuitry and programmable circuitry. Processor 42 may be multi-core, i.e., having two or more processor cores utilized for enhanced performance, reduced power consumption, and more efficient simultaneous processing of multiple tasks.

[0097] The processing circuitry 32 also includes a memory 44. In some embodiments, the memory 44 stores one or more computer programs 46 and optional configuration data 48. The memory 44 provides non-transitory storage for the computer programs 46 and may include one or more types of computer-readable media, such as disk storage devices, solid-state storage devices, or any combination thereof. Here, “non-transitory” means permanent, semi-permanent, or at least temporarily persistent storage and encompasses both long-term storage in non-volatile memory and storage in working memory (e.g., for program execution). As a non-limiting example, the memory 44 includes any one or more of SRAM, DRAM, EEPROM, and FLASH memory, which may be in and / or separate from the processing circuitry 32. The memory 44 may also store any configuration data 48 used by the network access node 30. For example, by using appropriate program code stored in the memory 44, the processing circuitry 32 may be configured to implement one or more of the methods and / or signaling processes detailed below.

[0098] According to some embodiments, the processing circuitry 32 of network node 30 is configured for multi-interval scheduling of downlink or uplink transmissions to or from a wireless communication device. The processing circuitry 32 is configured to send configuration information to the wireless device, specifying the maximum number of scheduling intervals that can be scheduled with a single scheduling message and one or both of the time-domain resource allocation data structures to be used when employing multi-interval scheduling. The scheduling intervals can be time slots or micro-time slots.

[0099] Processing circuit 32 can be configured to perform actions such as those caused by Figure 7The flowchart illustrates method 700. Method 700 includes sending configuration information to a wireless device that specifies the maximum number of scheduling intervals that can be scheduled with a single scheduling message and one or both of the time-domain resource allocation data structures to be used when using multi-interval scheduling (block 702). Method 700 may also include scheduling one or more downlink or uplink transmissions to or from the wireless communication device based on the configuration information. This scheduling can be performed using a single scheduling message, which will be transmitted in each of the multiple scheduling intervals.

[0100] According to other embodiments, processing circuitry 32 is configured to schedule one or more downlink or uplink transmissions to or from a wireless communication device using a single scheduling message, the single scheduling message being transmitted in each of a plurality of scheduling intervals. The number of scheduling intervals is indicated in the scheduling message by a dedicated field or by a time resource allocation indication, which implicitly or explicitly indicates the number of scheduling intervals.

[0101] Therefore, the processing circuit 32 can be configured to perform Figure 8 Another method 800 is shown. Method 800 includes scheduling one or more downlink or uplink transmissions to or from a wireless communication device using a single scheduling message, the single scheduling message scheduling the transmissions in each of a plurality of scheduling intervals, wherein the number of scheduling intervals is indicated in the scheduling message by a dedicated field or by a time resource assignment indicator, the time resource assignment indicator implicitly or explicitly indicating the number of scheduling intervals (box 802).

[0102] Method 800 may further include sending one or more downlink transmissions to a wireless device or receiving one or more uplink transmissions from a wireless communication device according to a scheduling message. The number of scheduling intervals may be specified by a dedicated field in the scheduling message, and the time resource allocation indication in the scheduling message may be mapped to a first predetermined table of time resource allocations, wherein the first predetermined table of time resource allocations differs from a second predetermined table of time resource allocations applicable when the number of scheduling intervals is 1. The time resource allocation indication may refer here to a time-domain resource allocation, or more specifically, to a time-domain resource allocation index.

[0103] Each entry in one or more entries in the first predefined table may contain any one or more of the following: a mapping type applicable to a first number of scheduling intervals; a mapping type applicable to scheduling slots other than the first number of scheduling intervals; an interval offset for the first scheduling interval; a start symbol applicable to one or more scheduling intervals; a transmission length applicable to one or more scheduling intervals; and a flag indicating whether the start symbol and length value are applied to each scheduling slot or to a subset of slots.

[0104] In some embodiments, code block group feedback can be configured and activated, and the scheduling message may not include a code block group transmission indication field, and each of the RV and NDI bit widths is equal to the maximum number of scheduling time slots specified in the configuration information that signals the wireless communication device.

[0105] In some embodiments, for the time resource allocation indication in the scheduling message, the first predetermined table provides separate scheduling information for each scheduling interval. The number of scheduling intervals for the time resource allocation indication in the scheduling message can be specified by the first predetermined table.

[0106] Method 800 may include sending a message to the wireless device identifying a subset of a first predetermined table to which the time resource assignment indication in the scheduling message applies. This message may be a MAC CE as discussed in previous embodiments. This claim is tied to “Embodiment 2e” in the description. In some embodiments, the scheduling message schedules uplink transmissions and includes an indication of whether the wireless communication device is allowed to use fewer than all of the multiple intervals scheduled by the scheduling message. In other embodiments, the scheduling message schedules uplink transmissions and includes an indication of allowing the wireless communication device to use only one of the multiple intervals scheduled by the scheduling message. The scheduling message may include an indication of Listen-After-Talk (LBT) priority, wherein the indication applies to one or all of the scheduling intervals. The scheduling message may include an indication of an energy detection threshold for LBT operation, wherein the indication applies to one or all of the scheduling intervals.

[0107] Method 800 may include sending configuration information to a wireless communication device specifying multiple multi-interval scheduling configurations, each multi-interval scheduling configuration may include one or more allocation parameters, and a scheduling message may indicate one of the multiple multi-interval scheduling configurations. The scheduling message may indicate different frequency resources used for different scheduling intervals.

[0108] In some embodiments, the resource assignment indication in the scheduling message is mapped to a first predetermined table of resource allocations, and the resource allocations in the first predetermined table of resource allocations identified by the resource assignment indication specify different frequency resources for different scheduling intervals.

[0109] Figure 9An example wireless device 50 (e.g., a UE) configured to perform the techniques described herein for wireless communication devices is shown. Wireless device 50 can also be considered as any wireless device that can operate in a network and is capable of communicating with a network node or another wireless device via radio signals. Wireless device 50 may also be referred to in various contexts as a radio communication device, target device, device-to-device (D2D) UE, machine-type UE or UE capable of machine-to-machine (M2M) communication, sensor-equipped UE, PDA (Personal Digital Assistant), wireless tablet, mobile terminal, smartphone, on-lamp embedded device (LEE), on-lamp mounted device (LME), wireless USB dongle, client device (CPE), etc.

[0110] The wireless device 50 communicates with one or more radio nodes or base stations, such as one or more network nodes 30, via antenna 54 and transceiver circuitry 56. Transceiver circuitry 56 may include transmitter circuitry, receiver circuitry, and associated control circuitry, which are collectively configured for the purpose of providing cellular communication services, transmitting and receiving signals in accordance with radio access technology.

[0111] The wireless device 50 also includes processing circuitry 52 operatively associated with and controlling the radio transceiver circuitry 56. Processing circuitry 52 includes one or more digital processing circuits 62, such as one or more microprocessors, microcontrollers, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), complex programmable logic devices (CPLDs), application-specific integrated circuits (ASICs), or any combination thereof. More generally, processing circuitry 52 may include fixed circuitry or programmable circuitry specifically adapted via the execution of program instructions that implement the functionality taught herein, or may include some mixture of fixed circuitry and programmable circuitry. Processing circuitry 52 may be multi-core.

[0112] The processing circuitry 52 also includes a memory 64. In some embodiments, the memory 64 stores one or more computer programs 66 and optional configuration data 68. The memory 64 provides non-transitory storage for the computer program 66 and may include one or more types of computer-readable media, such as disk storage devices, solid-state storage devices, or any mixture thereof. As a non-limiting example, the memory 64 includes any one or more of SRAM, DRAM, EEPROM, and FLASH memory, which may be in and / or separate from the processing circuitry 52. ​​Generally, the memory 64 includes one or more types of computer-readable storage media that provide non-transitory storage for the computer program 66 and any configuration data 68 used by the wireless device 50.

[0113] Therefore, in some embodiments, the processing circuitry 52 of the wireless device 50 is configured for multi-interval scheduling of downlink or uplink transmissions to or from the wireless communication device. The processing circuitry 52 is configured to receive configuration information from a network node in the wireless communication system, specifying the maximum number of scheduling intervals that can be scheduled with a single scheduling message and one or both of the time-domain resource allocation data structures to be used when employing multi-interval scheduling. The scheduling intervals can be time slots or micro-time slots.

[0114] Processing circuit 52 can also be configured to perform a multi-interval scheduling method 1000 for downlink or uplink transmissions to or from wireless device 50, as shown in Figure 10 Method 1000 includes receiving configuration information from a network node in a wireless communication system, the configuration information specifying the maximum number of scheduling intervals that can be scheduled using a single scheduling message and one or both of the time-domain resource allocation data structures to be used when using multi-interval scheduling (block 1002). Method 1000 may include receiving scheduling information for one or more downlink or uplink transmissions to or from a wireless communication device, based on the configuration information. The scheduling information may be received in a single scheduling message, which will be transmitted in each of the multiple scheduling intervals.

[0115] According to other embodiments, processing circuitry 52 is configured to receive, in a single scheduling message, scheduling information for one or more downlink or uplink transmissions to or from a wireless communication device, the single scheduling message transmitting data in each of a plurality of scheduling intervals. The number of scheduling intervals is indicated in the scheduling message by a dedicated field or by a time resource allocation indication, which implicitly or explicitly indicates the number of scheduling intervals.

[0116] Processing circuitry 52 may be configured to perform a method 1100 for multi-interval scheduling of downlink or uplink transmissions to or from wireless device 50. Method 1100 includes receiving, in a single scheduling message, scheduling information for one or more downlink or uplink transmissions to or from wireless communication devices, the single scheduling message transmitting the transmissions in each of a plurality of scheduling intervals, wherein the number of scheduling intervals is indicated in the scheduling message by a dedicated field or by a time resource allocation indication, the time resource allocation indication implicitly or explicitly indicating the number of scheduling intervals (block 1102).

[0117] Method 1100 may include sending one or more uplink transmissions or receiving one or more downlink transmissions according to a scheduling message. The number of scheduling intervals may be specified by a dedicated field in the scheduling message, and the time resource allocation indication in the scheduling message may be mapped to a first predetermined table of time resource allocations, wherein the first predetermined table of time resource allocations differs from a second predetermined table of time resource allocations applicable when the number of scheduling intervals is 1. In some embodiments, each entry in one or more entries in the first predetermined table includes any one or more of the following: a mapping type applicable to a first number of scheduling intervals; a mapping type applicable to scheduling slots other than the first number of scheduling intervals; an interval offset for the first scheduling interval; a start symbol applicable to one or more scheduling intervals; a transmission length applicable to one or more scheduling intervals; and a flag indicating whether the start symbol and length value are applied to each scheduling slot or to a subset of slots.

[0118] In some embodiments, block group feedback is configured and activated, and the scheduling message does not include a block group transmission indication field, and each of the RV and NDI bit widths is equal to the maximum number of scheduling slots specified in the configuration information signaled to the wireless communication device. For the time resource allocation indication in the scheduling message, a first predetermined table can provide separate scheduling information for each scheduling interval. The number of scheduling intervals for the time resource allocation indication in the scheduling message can be specified by the first predetermined table.

[0119] Method 1100 may include receiving a message identifying a subset of a first predetermined table to which the time resource assignment indication in the scheduling message applies. In some embodiments, the scheduling message schedules uplink transmissions and includes an indication of whether the wireless communication device is allowed to use fewer than all of the multiple intervals scheduled by the scheduling message. In other embodiments, the scheduling message schedules uplink transmissions and includes an indication of allowing the wireless communication device to use only one of the multiple intervals scheduled by the scheduling message.

[0120] In some embodiments, the scheduling message includes an indication of a listen-before-speak priority, wherein the indication applies to one or all of the scheduling intervals. In other embodiments, the scheduling message includes an indication of an energy detection threshold for the listen-before-speak operation, wherein the indication applies to one or all of the scheduling intervals.

[0121] Method 1100 may include receiving configuration information specifying multiple multi-interval scheduling configurations, each multi-interval scheduling configuration including one or more allocation parameters. A scheduling message may specify one of the multiple multi-interval scheduling configurations. A scheduling message may specify different frequency resources for different scheduling intervals.

[0122] In some embodiments, the resource assignment indication in the scheduling message is mapped to a first predetermined table of resource allocations, and the resource allocations in the first predetermined table of resource allocations identified by the resource assignment indication specify different frequency resources for different scheduling intervals.

[0123] Figure 12 A communication system is illustrated according to some embodiments, comprising a telecommunications network 1210 such as a 3GPP-type cellular network, an access network 1211 such as a radio access network, and a core network 1214. The access network 1211 includes multiple base stations 1212a, 1212b, 1212c, such as NBs, eNBs, gNBs, or other types of radio access points, each base station defining a corresponding coverage area 1213a, 1213b, 1213c. Each base station 1212a, 1212b, 1212c can be connected to the core network 1214 via a wired or wireless connection 1215. A first UE 1291 located in coverage area 1213c is configured to wirelessly connect to or be paged by the corresponding base station 1212c. A second UE 1292 located in coverage area 1213a can wirelessly connect to the corresponding base station 1212a. Although multiple UEs 1291 and 1292 are shown in this example, the disclosed embodiments are equally applicable to situations where a single UE is in the coverage area or a single UE is connected to the corresponding base station 1212.

[0124] Telecommunications network 1210 is itself connected to host computer 1230, which may be implemented in the hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as a processing resource in a server farm. Host computer 1230 may be owned or controlled by a service provider, or may be operated by or on behalf of a service provider. Connections 1221, 1222 between telecommunications network 1210 and host computer 1230 may extend directly from core network 1214 to host computer 1230, or may be made via optional intermediate network 1220. Intermediate network 1220 may be one or a combination of public, private, or takeover networks; intermediate network 1220 (if any) may be a backbone network or the Internet; in particular, intermediate network 1220 may include two or more subnetworks (not shown).

[0125] Figure 12The communication system as a whole enables connectivity between one of the connected UEs 1291 and 1292 and the host computer 1230. This connectivity can be described as an over-the-top (OTT) connection 1250. The host computer 1230 and the connected UEs 1291 and 1292 are configured to transmit data and / or signaling via the OTT connection 1250, using access network 1211, core network 1214, any intermediate network 1220, and possible further infrastructure (not shown) as intermediaries. The OTT connection 1250 can be transparent in the sense that the participating communication devices traversed by the OTT connection 1250 are unaware of the routing of uplink and downlink communications. For example, it may not be necessary or required to notify the base station 1212 of the past routing of incoming downlink communications containing data originating from the host computer 1230 to be forwarded (e.g., handed over) to the connected UE 1291. Similarly, base station 1212 does not need to know the future routing of uplink communication originating from UE 1291 toward host computer 1230.

[0126] According to the embodiments, reference will now be made to Figure 13 Example implementations of the UE, base station, and host computer discussed in the preceding paragraphs are described. In the communication system 1300, the host computer 1310 includes hardware 1315, which includes a communication interface 1316 configured to establish and maintain wired or wireless connections with interfaces of different communication devices of the communication system 1300. The host computer 1310 further includes processing circuitry 1318, which may have storage and / or processing capabilities. In particular, the processing circuitry 1318 may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) suitable for executing instructions. The host computer 1310 further includes software 1311, which is stored in or accessible by the host computer 1310 and executable by the processing circuitry 1318. The software 1311 includes a host application 1312. Host application 1312 is operable to provide services to remote users, such as UE 1330 connected via OTT connection 1350 terminated between UE 1330 and host computer 1310. When providing services to remote users, host application 1312 can provide user data, which is transmitted using OTT connection 1350.

[0127] The communication system 1300 further includes a base station 1320, which is disposed in the telecommunications system and includes hardware 1325 enabling it to communicate with a host computer 1310 and a UE 1330. Hardware 1325 may include a communication interface 1326 for establishing and maintaining wired or wireless connections with different communication devices of the communication system 1300, and for establishing and maintaining connections with the coverage area served by the base station 1320. Figure 13 The UE 1330 (not shown) has at least a radio interface 1327 for a wireless connection 1370. A communication interface 1326 can be configured to facilitate a connection 1360 to a host computer 1310. The connection 1360 can be direct, or it can be via the core network of a telecommunications system (…). Figure 13 (Not shown) and / or via one or more intermediate networks outside the telecommunications system. In the illustrated embodiment, the hardware 1325 of base station 1320 further includes processing circuitry 1328, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) suitable for executing instructions. Base station 1320 also has software 1321 stored internally or accessible via an external connection.

[0128] The communication system 1300 further includes the already mentioned UE 1330, whose hardware 1335 may include a radio interface 1337 configured to establish and maintain a wireless connection 1370 with a base station serving the coverage area currently occupied by the UE 1330. The hardware 1335 of the UE 1330 further includes processing circuitry 1338, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) suitable for executing instructions. The UE 1330 further includes software 1331 stored in or accessible to the UE 1330 and executable by the processing circuitry 1338. The software 1331 includes a client application 1332. The client application 1332 may be operable to provide services to human or non-human users via the UE 1330 with the support of a host computer 1310. In host computer 1310, the executing host application 1312 can communicate with the executing client application 1332 via OTT connection 1350 terminated between UE 1330 and host computer 1310. When providing services to a user, client application 1332 can receive request data from host application 1312 and provide user data in response to the request data. OTT connection 1350 can transmit request data and user data. Client application 1332 can interact with the user to generate the user data it provides.

[0129] Notice, Figure 13The host computer 1310, base station 1320, and UE 1330 shown can be respectively connected to... Figure 13 The host computer 1330, one of the base stations 1312a, 1312b, and 1312c, and one of the UEs 1391 and 1392 are identical. That is to say, the internal operation of these entities can be as follows: Figure 13 As shown, and independently, the surrounding network topology can be Figure 12 As it is.

[0130] exist Figure 13 The diagram abstractly depicts OTT connection 1350 to illustrate communication between host computer 1310 and user equipment 1330 via base station 1320, without explicitly mentioning any intermediate devices or the precise routing of messages via these devices. The network infrastructure can determine the routing, which can be configured to be hidden from the UE 1330, the service provider operating the host computer 1310, or both. When OTT connection 1350 is active, the network infrastructure can make further decisions (e.g., based on load balancing considerations or network reconfiguration), through which it dynamically changes the routing.

[0131] The wireless connection 1370 between UE 1330 and base station 1320 is provided according to the teachings of the embodiments described throughout this disclosure, such as through nodes like wireless devices and relay nodes 30, along with corresponding methods 800. The embodiments described herein provide a DCI design that schedules both a single DCI and multiple PUSCHs. Advantages include reduced overhead on the PDCCH by using a single permission to transmit scheduling information for multiple time slots, enabling efficient UL scheduling and transmission when multiple start / end positions are supported. Another advantage is the flexibility in scheduling multiple time slots. The teachings of these embodiments can use OTT connection 1350 to improve the reliability, connectivity, data rate, capacity, latency, and / or power consumption of the network and UE 1330.

[0132] For the purpose of monitoring data rate, latency, and other factors (as improved in one or more embodiments), a measurement process may be provided. Optional network functionality may further exist for reconfiguring the OTT connection 1350 between host computer 1310 and UE 1330 in response to changes in the measurement results. The measurement process and / or the network functionality for reconfiguring the OTT connection 1350 may be implemented in software 1311 of host computer 1310, or in software 1331 of UE 1330, or both. In embodiments, sensors (not shown) may be deployed in or associated with communication devices through which the OTT connection 1350 traverses; the sensors may participate in the measurement process by being supplied with values ​​of the monitored quantities exemplified above or values ​​of other physical quantities (based on which software 1311, 1331 may calculate or estimate the monitored quantities). Reconfiguration of the OTT connection 1350 may include message formatting, retransmission settings, preferred routing, etc.; reconfiguration does not need to affect base station 1320, and it may be unknown or imperceptible to base station 1320. Such processes and functionalities can be known and practiced in the art. In some embodiments, the measurement may involve proprietary UE signaling, which facilitates the host computer 1310 to measure throughput, propagation time, latency, etc. The measurement is possible because software 1311 and 1331, while monitoring propagation time, errors, etc., cause messages (especially empty or 'fake' messages) to be transmitted using OTT connection 1350.

[0133] Figure 14 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be referenced... Figure 12 and Figure 13 Those described. For the sake of brevity in this disclosure, this section will only include descriptions of... Figure 14 The accompanying drawings are referenced. In the first step 1410 of the method, the host computer provides user data. In an optional sub-step 1411 of the first step 1410, the host computer provides user data by executing a host application. In the second step 1420, the host computer initiates a transmission carrying user data to the UE. In an optional third step 1430, in accordance with the teachings of the embodiments described throughout this disclosure, the base station transmits to the UE the user data already carried in the transmission initiated by the host computer. In an optional fourth step 1440, the UE executes a client application associated with the host application executed by the host computer.

[0134] Figure 15 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be referenced... Figure 12 and Figure 13Those described. For the sake of brevity in this disclosure, this section will only include descriptions of... Figure 15 The accompanying drawings are referenced. In the first step 1510 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides user data by executing a host application. In the second step 1520, the host computer initiates a transmission carrying user data to the UE. According to the teachings of the embodiments described throughout this disclosure, the transmission can be performed via a base station. In an optional third step 1530, the UE receives the user data carried in the transmission.

[0135] Figure 16 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be referenced... Figure 12 and Figure 13 Those described. For the sake of brevity in this disclosure, this section will only include descriptions of... Figure 16 The accompanying drawings are referenced. In an optional first step 1610 of the method, the UE receives input data provided by the host computer. Additionally or alternatively, in an optional second step 1620, the UE provides user data. In an optional sub-step 1621 of the second step 1620, the UE provides user data by executing a client application. In an additional optional sub-step 1611 of the first step 1610, the UE responds to the received input data provided by the host computer by executing a client application that provides user data. When providing user data, the executed client application may further consider user input received from the user. Regardless of the specific method used to provide user data, in an optional third sub-step 1630, the UE initiates the transmission of user data to the host computer. In a fourth step 1640 of the method, the host computer receives user data transmitted from the UE in accordance with the teachings of the embodiments described throughout this disclosure.

[0136] Figure 17 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be referenced... Figure 12 and Figure 13 Those described. For the sake of brevity in this disclosure, this section will only include descriptions of... Figure 17 The accompanying drawings are referenced. In an optional first step 1710 of the method, the base station receives user data from the UE in accordance with the teachings of the embodiments described throughout this disclosure. In an optional second step 1720, the base station initiates a transmission of the received user data to the host computer. In a third step 1730, the host computer receives the user data carried in the transmission initiated by the base station.

[0137] As discussed in detail above, for example, such as Figure 7-8The techniques described herein, as illustrated in the process flowcharts 10-11, can be implemented wholly or partially using computer program instructions executed by one or more processors. It will be understood that the functional implementation of these techniques can be represented as functional modules, where each functional module corresponds to a functional unit of software executed in a suitable processor, or to a functional digital hardware circuit, or some combination of both.

[0138] Figure 18 An example functional module or circuit architecture of a wireless device 50 for multi-interval scheduling of downlink or uplink transmissions to or from a wireless communication device is shown. This functional implementation includes a transmitting module 1802 for sending configuration information to the wireless device, the configuration information specifying the maximum number of scheduling intervals that can be scheduled with a single scheduling message and one or both of the time-domain resource allocation data structures to be used when using multi-interval scheduling.

[0139] Another functional implementation in the wireless device 50 includes a scheduling module 1804 for scheduling one or more downlink or uplink transmissions to or from the wireless communication device using a single scheduling message. The single scheduling message schedules the transmissions in each of a plurality of scheduling intervals, wherein the number of scheduling intervals is indicated in the scheduling message by a dedicated field or by a time resource allocation indication, which implicitly or explicitly indicates the number of scheduling intervals.

[0140] Figure 19 An example functional module or circuit architecture of a wireless device 50 for multi-interval scheduling of downlink or uplink transmissions to or from a wireless communication device is shown. This functional implementation includes a receiving module 1902 for receiving configuration information from a network node in the wireless communication system. The configuration information specifies the maximum number of scheduling intervals that can be scheduled with a single scheduling message and one or both of the time-domain resource allocation data structures to be used when employing multi-interval scheduling.

[0141] Another implementation includes a scheduling module 1904 for receiving, in a single scheduling message, scheduling information for one or more downlink or uplink transmissions to or from a wireless communication device, the single scheduling message transmitting in each of a plurality of scheduling intervals, wherein the number of scheduling intervals is indicated in the scheduling message by a dedicated field or by a time resource assignment indicator, the time resource assignment indicator implicitly or explicitly indicating the number of scheduling intervals.

[0142] Example Implementation

[0143] Example implementations may include, but are not limited to, the following examples:

[0144] 1. A method in a network node of a wireless communication system for multi-interval scheduling of downlink or uplink transmissions to or from a wireless communication device, the method comprising:

[0145] Send configuration information to the wireless device, which specifies the maximum number of scheduling intervals that can be scheduled with a single scheduling message and one or both of the time-domain resource allocation data structures to be used when using multi-interval scheduling.

[0146] 2. The method of Example 1, wherein the scheduling interval is a time slot or a micro-time slot.

[0147] 3. The method of Example Embodiment 1 or 2, further comprising:

[0148] Based on the configuration information, schedule one or more downlink or uplink transmissions to or from wireless communication devices.

[0149] 4. The method of Example 3, wherein the scheduling is performed using a single scheduling message, which is transmitted in each of a plurality of scheduling intervals.

[0150] 5. A method in a network node of a wireless communication system for multi-interval scheduling of downlink or uplink transmissions to or from a wireless communication device, the method comprising:

[0151] A single scheduling message is used to schedule one or more downlink or uplink transmissions to or from a wireless communication device. The single scheduling message schedules the transmissions in each of multiple scheduling intervals.

[0152] The number of scheduling intervals is specified in the scheduling message by a dedicated field or by a time resource allocation indicator, which implicitly or explicitly specifies the number of scheduling intervals.

[0153] 6. The method of Example 5, wherein the scheduling interval is a time slot or a micro-time slot.

[0154] 7. The method of Example 5 or 6, further comprising:

[0155] Based on the scheduling message, send one or more downlink transmissions to the wireless device, or receive one or more uplink transmissions from the wireless communication device.

[0156] 8. The method of any one of Example 5-7, wherein the number of scheduling intervals is indicated by a dedicated field in the scheduling message, and wherein the time resource allocation indication in the scheduling message is mapped to a first predetermined table of time resource allocation, wherein the first predetermined table of time resource allocation is different from the second predetermined table of time resource allocation applicable when the number of scheduling intervals is 1.

[0157] 9. The method of Example Embodiment 8, wherein each entry in one or more entries of a first predetermined table includes any one or more of the following:

[0158] The mapping type applicable to the first number of scheduling intervals;

[0159] Mapping type applicable to scheduling slots other than the first number of scheduling intervals;

[0160] Interval offset for the first scheduling interval;

[0161] The start symbol applicable to one or more scheduling intervals;

[0162] The transmission length applicable to one or more scheduling intervals; and

[0163] A flag indicating whether the start symbol and length value apply to each scheduled slot or to a subset of slots.

[0164] 10. A method of any one of Example 5-9, wherein code block group feedback is configured and activated, and wherein:

[0165] The scheduling message does not contain a code block group transmission indication field, and each of the RV and NDI bit widths is equal to the maximum number of scheduling time slots specified in the configuration information that signals the wireless communication device.

[0166] 11. The method of Example Embodiments 5-10, wherein, for the time resource allocation indication in the scheduling message, the first pre-defined table provides separate scheduling information for each scheduling interval.

[0167] 12. The method of Example 11, wherein the number of scheduling intervals is specified by a first predetermined table for the time resource allocation indication in the scheduling message.

[0168] 13. A method of any one of Example Embodiments 5-12, wherein the method further comprises sending a message to a wireless device identifying a subset of a first predetermined table to which the time resource assignment indication in the scheduling message applies.

[0169] 14. A method of any one of Example Embodiments 5-13, wherein the scheduling message schedules uplink transmissions and includes an indication of whether the wireless communication device is allowed to use fewer than the total number of intervals scheduled by the scheduling message.

[0170] 15. A method of any one of Example Embodiments 5-13, wherein the scheduling message schedules uplink transmissions and includes an indication that allows the wireless communication device to use only one of the multiple intervals scheduled by the scheduling message.

[0171] 16. A method of any one of Example 5-15, wherein the scheduling message includes an indication of a listen-before-speak priority, wherein the indication applies to one or all of the scheduling intervals.

[0172] 17. The method of any one of Example 5-16, wherein the scheduling message includes an indication of an energy detection threshold for a listen-before-speak operation, wherein the indication applies to one or all of the scheduling intervals.

[0173] 18. A method of any one of Example Embodiments 5-7, wherein the method includes sending configuration information to a wireless communication device specifying a plurality of multi-interval scheduling configurations, each multi-interval scheduling configuration including one or more allocation parameters, and wherein a scheduling message indicates one of the plurality of multi-interval scheduling configurations.

[0174] 19. The method of any one of Example 5-18, wherein the scheduling message specifies different frequency resources for different scheduling intervals.

[0175] 20. A method of any one of Example Embodiments 5-7, wherein a resource assignment indication in a scheduling message is mapped to a first predetermined table of resource allocations, and wherein the resource allocations in the first predetermined table of resource allocations identified by the resource assignment indication specify different frequency resources for different scheduling intervals.

[0176] 21. A method in a wireless communication apparatus operating in a wireless communication system for multi-interval scheduling of downlink or uplink transmissions to or from the wireless communication apparatus, the method comprising:

[0177] Configuration information is received from network nodes in a wireless communication system. The configuration information specifies the maximum number of scheduling intervals that can be scheduled with a single scheduling message and one or both of the time-domain resource allocation data structures to be used when using multi-interval scheduling.

[0178] 22. The method of Example 21, wherein the scheduling interval is a time slot or a micro-time slot.

[0179] 23. The method of Example Embodiment 21 or 22, further comprising:

[0180] Based on the configuration information, receive scheduling information for downlink or uplink transmissions to or from one or more wireless communication devices.

[0181] 24. The method of Example 23, wherein the scheduling information is received in a single scheduling message, the single scheduling message being transmitted in each of a plurality of scheduling intervals.

[0182] 25. A method in a wireless communication apparatus operating in a wireless communication system for multi-interval scheduling of downlink or uplink transmissions to or from the wireless communication apparatus, the method comprising:

[0183] A single scheduling message receives scheduling information for one or more downlink or uplink transmissions to or from a wireless communication device. This single scheduling message transmits information scheduled for each of multiple scheduling intervals.

[0184] The number of scheduling intervals is specified in the scheduling message by a dedicated field or by a time resource allocation indicator, which implicitly or explicitly specifies the number of scheduling intervals.

[0185] 26. The method of Example 25, wherein the scheduling interval is a time slot or a micro-time slot.

[0186] 27. The method of Example Embodiment 25 or 26, further comprising:

[0187] Based on the scheduling message, send one or more uplink transmissions or receive one or more downlink transmissions.

[0188] 28. A method of any one of Example 25-27, wherein the number of scheduling intervals is indicated by a dedicated field in a scheduling message, and wherein a time resource allocation indication in the scheduling message is mapped to a first predetermined table of time resource allocation, wherein the first predetermined table of time resource allocation is different from a second predetermined table of time resource allocation applicable when the number of scheduling intervals is 1.

[0189] 29. The method of Example Embodiment 28, wherein each entry in one or more entries of a first predetermined table includes any one or more of the following:

[0190] The mapping type applicable to the first number of scheduling intervals;

[0191] Mapping type applicable to scheduling slots other than the first number of scheduling intervals;

[0192] Interval offset for the first scheduling interval;

[0193] The start symbol applicable to one or more scheduling intervals;

[0194] The transmission length applicable to one or more scheduling intervals; and

[0195] A flag indicating whether the start symbol and length value apply to each scheduled slot or to a subset of slots.

[0196] 30. A method of any one of Example 25-29, wherein code block group feedback is configured and activated, and wherein:

[0197] The scheduling message does not contain a code block group transmission indication field, and each of the RV and NDI bit widths is equal to the maximum number of scheduling time slots specified in the configuration information that signals the wireless communication device.

[0198] 31. The method of Example Embodiments 25-30, wherein, for the time resource allocation indication in the scheduling message, the first pre-defined table provides separate scheduling information for each scheduling interval.

[0199] 32. The method of Example 31, wherein the number of scheduling intervals is specified by a first predetermined table for the time resource allocation indication in the scheduling message.

[0200] 33. A method of any one of Example Embodiments 25-32, wherein the method further comprises receiving a message identifying a subset of a first predetermined table to which a time resource assignment indication in a scheduling message applies.

[0201] 34. A method of any one of Example Embodiments 25-33, wherein the scheduling message schedules uplink transmissions and includes an indication of whether the wireless communication device is allowed to use fewer than the total number of intervals scheduled by the scheduling message.

[0202] 35. A method of any one of Example Embodiments 25-33, wherein the scheduling message schedules uplink transmissions and includes an indication that allows the wireless communication device to use only one of the multiple intervals scheduled by the scheduling message.

[0203] 36. The method of any one of Example 25-35, wherein the scheduling message includes an indication of a listen-before-speak priority, wherein the indication applies to one or all of the scheduling intervals.

[0204] 37. The method of any one of Example 25-36, wherein the scheduling message includes an indication of an energy detection threshold for a listen-before-speak operation, wherein the indication applies to one or all of the scheduling intervals.

[0205] 38. A method of any one of Example Embodiments 25-27, wherein the method includes receiving configuration information specifying a plurality of multi-interval scheduling configurations, each multi-interval scheduling configuration including one or more allocation parameters, and wherein a scheduling message indicates one of the plurality of multi-interval scheduling configurations.

[0206] 39. The method of any one of Example 25-38, wherein the scheduling message specifies different frequency resources for different scheduling intervals.

[0207] 40. A method of any one of Example Embodiments 25-27, wherein a resource assignment indication in a scheduling message is mapped to a first predetermined table of resource allocations, and wherein the resource allocations in the first predetermined table of resource allocations identified by the resource assignment indication specify different frequency resources for different scheduling intervals.

[0208] 41. A network node adapted to perform a method according to any one of Example Embodiments 1-20.

[0209] 42. A network node comprising transceiver circuitry and processing circuitry operatively associated with the transceiver circuitry, and configured to perform a method according to any one of Example Embodiments 1-20.

[0210] 43. A wireless device adapted to perform a method according to any one of Example Embodiments 21-40.

[0211] 44. A wireless device comprising transceiver circuitry and processing circuitry operatively associated with the transceiver circuitry, and configured to perform a method according to any one of Example Embodiments 21-40.

[0212] 45. A computer program comprising instructions that, when executed on at least one processing circuit, cause the at least one processing circuit to perform a method according to any one of Example Embodiments 1-40.

[0213] 46. ​​A carrier comprising the computer program of Example Embodiment 45, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium.

[0214] A1. A communication system including a host computer, comprising:

[0215] Configured to provide user data processing circuitry; and

[0216] A communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE), wherein the cellular network includes a base station having a radio interface and processing circuitry, the processing circuitry of which is configured to perform any of the operations described in Examples 1-20.

[0217] A2. The communication system of the foregoing embodiments further includes a base station.

[0218] A3. The communication system of the first two embodiments further includes a UE, wherein the UE is configured to communicate with a base station.

[0219] A4. The communication system of the first three embodiments, wherein:

[0220] The host computer's processing circuitry is configured to execute host applications, thereby providing user data; and

[0221] The UE includes processing circuitry configured to execute client applications associated with the host application.

[0222] A5. A method implemented in a communication system comprising a host computer, a base station, and a user equipment (UE), the method comprising:

[0223] Providing user data on the host computer; and

[0224] When a host computer initiates a transmission carrying user data to a UE via a cellular network including a base station, the base station performs any one of the steps in any of embodiments 1-20.

[0225] A6. The method of the foregoing embodiments further includes transmitting user data at the base station.

[0226] A7. The method of the first two embodiments, wherein user data is provided by executing a host application on a host computer, the method further includes executing a client application associated with the host application on the UE.

[0227] A8. A user equipment (UE) configured to communicate with a base station, the UE including a radio interface and processing circuitry configured to perform any of the first three embodiments.

[0228] A9. A communication system including a host computer, comprising:

[0229] Configured to provide user data processing circuitry; and

[0230] A communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE).

[0231] The UE includes a radio interface and processing circuitry, and the components of the UE are configured to perform any one of the steps in any of embodiments 21-40.

[0232] A10. The communication system of the foregoing embodiments, wherein the cellular network further includes a base station configured to communicate with the UE.

[0233] A11. The communication system of the first two embodiments, wherein:

[0234] The host computer's processing circuitry is configured to execute host applications, thereby providing user data; and

[0235] The UE's processing circuitry is configured to execute client applications associated with the host application.

[0236] A12. A method implemented in a communication system comprising a host computer, a base station, and a user equipment (UE), the method comprising:

[0237] Providing user data on the host computer; and

[0238] When a host computer initiates a transmission carrying user data to a UE via a cellular network including a base station, the UE performs any one of the steps in any of embodiments 21-40.

[0239] A13. The method of the foregoing embodiments further includes the UE receiving user data from the base station.

[0240] A14. A communication system including a host computer, comprising:

[0241] A communication interface configured to receive user data originating from transmissions from a user equipment (UE) to a base station.

[0242] The UE includes a radio interface and processing circuitry, and the processing circuitry of the UE is configured to perform any one of the steps in any of embodiments 21-40.

[0243] A15. The communication system of the foregoing embodiments further includes a UE.

[0244] A16. The communication system of the first two embodiments further includes a base station, wherein the base station includes a radio interface configured to communicate with a UE and a communication interface configured to forward user data carried by transmissions from the UE to the base station to a host computer.

[0245] A17. The communication system of the first three embodiments, wherein:

[0246] The host computer's processing circuitry is configured to execute host applications; and

[0247] The UE's processing circuitry is configured to execute client applications associated with the host application, thereby providing user data.

[0248] A18. The communication system of the first four embodiments, wherein:

[0249] The host computer's processing circuitry is configured to execute host applications, thereby providing requested data; and

[0250] The UE's processing circuitry is configured to execute client applications associated with the host application, thereby providing user data in response to requested data.

[0251] A19. A method implemented in a communication system comprising a host computer, a base station, and a user equipment (UE), the method comprising:

[0252] The host computer receives user data transmitted from the UE to the base station, wherein the UE performs any one of the steps in any of embodiments 21-40.

[0253] A20. The method of the foregoing embodiments further includes providing user data to the base station by the UE.

[0254] A21. The method of the first two embodiments further includes:

[0255] The UE executes a client application, thereby providing the user data to be transmitted; and

[0256] The host application associated with the client application is executed on the host computer.

[0257] A22. The method of the first three embodiments further includes:

[0258] Executing client applications in UE; and

[0259] When the UE receives input data to the client application, the input data is provided by the host computer by executing a host application associated with the client application.

[0260] The user data to be transmitted is provided by the client application in response to the input data.

[0261] A23. A communication system including a host computer, the host computer including a communication interface configured to receive user data originating from transmissions from a user equipment (UE) to a base station, the base station including a radio interface and processing circuitry configured to communicate with the base station and cooperatively perform the operations of any one of embodiments 1-20.

[0262] A24. The communication system of the foregoing embodiments further includes a base station.

[0263] A25. The communication system of the first two embodiments further includes a UE, wherein the UE is configured to communicate with a base station.

[0264] A26. The communication system of the first three embodiments, wherein:

[0265] The host computer's processing circuitry is configured to execute host applications; and

[0266] The UE is further configured to execute client applications associated with the host application, thereby providing user data to be received by the host computer.

[0267] A27. A method implemented in a communication system comprising a host computer, a base station, and a user equipment (UE), the method comprising:

[0268] When the host computer receives user data from the base station, the user data originating from a transmission already received by the base station from the UE, the UE performs any one of the steps in any of embodiments 21-40.

[0269] A28. The method of the foregoing embodiments further includes receiving user data from the UE at the base station.

[0270] A29. The methods of the first two embodiments further include initiating the transmission of received user data from the base station to the host computer.

[0271] Many changes and modifications can be made to the embodiments without substantially departing from the principles of the inventive concept. All such changes and modifications are intended to be included within the scope of the inventive concept herein. Therefore, the subject matter disclosed above is to be considered illustrative rather than restrictive, and the examples of embodiments are intended to cover all such modifications, enhancements, and other embodiments falling within the spirit and scope of the inventive concept. Thus, to the fullest extent permitted by law, the scope of the inventive concept should be determined by the widest permissible interpretation of this disclosure, including examples of embodiments and their equivalents, and should not be constrained or limited by the foregoing detailed description.

Claims

1. A method in a network node of a wireless communication system for multi-interval scheduling of downlink or uplink transmissions to or from a wireless communication device, the method comprising: (702) Configuration information is sent to the wireless communication device, the configuration information specifying the maximum number of scheduling intervals that can be scheduled with a single scheduling message and one or both of the time-domain resource allocation data structures to be used when using multi-interval scheduling. The number of scheduling intervals is specified in the scheduling message by a dedicated field or by a time resource allocation indicator, which implicitly or explicitly specifies the number of scheduling intervals. Wherein, the time resource allocation indication in the scheduling message is mapped to a first predetermined table for time resource allocation, and the first predetermined table includes: The start symbol relative to the start of the scheduling interval; Transmission length, the number of consecutive symbols counted from the start symbol; and The flag indicates whether, when multiple scheduling intervals are scheduled with a single scheduling message, (a) the start symbol and the transmission length are applied to each scheduling interval such that there is a gap between the scheduling intervals, or (b) the start symbol is applied to the first scheduling interval among a plurality of scheduling intervals without gaps in between, and the transmission length is the transmission length for the last scheduling interval among the plurality of scheduling intervals, while all scheduling intervals between the first scheduling interval and the last scheduling interval have a transmission length equal to the scheduling interval length.

2. The method as described in claim 1, wherein, The scheduling interval is a time slot or a micro-time slot.

3. The method of claim 1 or 2, further comprising: Based on the configuration information, schedule one or more downlink or uplink transmissions to or from the wireless communication device.

4. The method of claim 3, wherein, The scheduling is performed using a single scheduling message, which is transmitted in each of the multiple scheduling intervals.

5. A method in a network node of a wireless communication system for multi-interval scheduling of downlink or uplink transmissions to or from a wireless communication device, the method comprising: Using a single scheduling message, one or more downlink or uplink transmissions to or from the wireless communication device are scheduled (802). The number of scheduling intervals is specified in the scheduling message by a dedicated field or by a time resource allocation indicator, which implicitly or explicitly specifies the number of scheduling intervals. Wherein, the time resource allocation indication in the scheduling message is mapped to a first predetermined table for time resource allocation, and the first predetermined table includes: The start symbol relative to the start of the scheduling interval; Transmission length, the number of consecutive symbols counted from the start symbol; and The flag indicates whether, when multiple scheduling intervals are scheduled with a single scheduling message, (a) the start symbol and the transmission length are applied to each scheduling interval such that there is a gap between the scheduling intervals, or (b) the start symbol is applied to the first scheduling interval among a plurality of scheduling intervals without gaps in between, and the transmission length is the transmission length for the last scheduling interval among the plurality of scheduling intervals, while all scheduling intervals between the first scheduling interval and the last scheduling interval have a transmission length equal to the scheduling interval length.

6. The method of claim 5, wherein, The scheduling interval is a time slot or a micro-time slot.

7. The method of claim 5 or 6, further comprising: According to the scheduling message, send one or more downlink transmissions to the wireless communication device, or receive one or more uplink transmissions from the wireless communication device.

8. The method according to any one of claims 5-7, wherein, The number of scheduling intervals is specified by a dedicated field in the scheduling message, wherein the first predetermined table for time resource allocation is different from the second predetermined table for time resource allocation applicable when the number of scheduling intervals is 1.

9. The method of claim 8, wherein, Each entry in one or more entries in the first predefined table includes any one or more of the following: The mapping type applicable to the first number of scheduling intervals; Mapping types applicable to scheduling intervals other than the first number of scheduling intervals; and Interval offset used for the first scheduling interval.

10. The method according to any one of claims 5-9, wherein, The single scheduling message will be transmitted and scheduled in each of the multiple scheduling intervals, wherein code block group feedback is configured and activated, and wherein: The scheduling message does not contain a code block group transmission indication field, and each of the RV and NDI bit widths is equal to the maximum number of scheduling time slots specified in the configuration information that signals the wireless communication device.

11. The method according to any one of claims 5-9, wherein, The single scheduling message will transmit the schedule within a single scheduling interval, wherein code block group feedback is configured and activated, and wherein: For a scheduling interval, specify RV and NDI; and The single scheduling message contains code block group transmission information (CGGTI) for the single scheduling interval.

12. The method according to any one of claims 5-7, wherein, The time resource allocation indication in the scheduling message is mapped to a first predetermined table of time resource allocation, wherein, for the time resource allocation indication in the scheduling message, the first predetermined table provides separate scheduling information for each scheduling interval.

13. The method of claim 12, wherein, For the time resource allocation indication in the scheduling message, the number of scheduling intervals is implicitly indicated by the first predetermined table, and invalid or null values ​​indicate scheduling information for any unscheduled interval.

14. The method according to any one of claims 5-13, wherein, The method further includes sending a message to the wireless communication device identifying a subset of a first predetermined table to which the time resource assignment indication in the scheduling message applies.

15. The method according to any one of claims 5-14, wherein, The scheduling message schedules uplink transmissions and includes an indication of whether the wireless communication device is allowed to use fewer than the total number of intervals scheduled by the scheduling message.

16. The method according to any one of claims 5-14, wherein, The scheduling message schedules uplink transmissions and includes an indication that the wireless communication device may use only one of the intervals scheduled by the scheduling message.

17. The method according to any one of claims 5-16, wherein, The scheduling message includes an indication of a listen-before-speak priority, wherein the indication applies to one or all of the scheduling intervals.

18. The method according to any one of claims 5-17, wherein, The scheduling message includes an indication of an energy detection threshold for the listen-before-speak operation, wherein the indication applies to one or all of the scheduling intervals.

19. The method according to any one of claims 5-7, wherein, The method includes sending configuration information to the wireless communication device specifying a plurality of multi-interval scheduling configurations, each multi-interval scheduling configuration including one or more allocation parameters, wherein the scheduling message indicates one of the plurality of multi-interval scheduling configurations.

20. The method according to any one of claims 5-19, wherein, The scheduling message specifies different frequency resources for different scheduling intervals.

21. The method according to any one of claims 5-7, wherein, The resource assignment indication in the scheduling message is mapped to a first predetermined table of resource allocations, wherein the resource allocation in the first predetermined table of resource allocations identified by the resource assignment indication specifies different frequency resources for different scheduling intervals.

22. A method in a wireless communication apparatus operating in a wireless communication system for multi-interval scheduling of downlink or uplink transmissions to or from said wireless communication apparatus, said method comprising: (1002) Configuration information is received from a network node in the wireless communication system. This configuration information specifies the maximum number of scheduling intervals that can be scheduled with a single scheduling message and one or both of the time-domain resource allocation data structures to be used when using multi-interval scheduling. The number of scheduling intervals is specified in the scheduling message by a dedicated field or by a time resource allocation indicator, which implicitly or explicitly specifies the number of scheduling intervals. Wherein, the time resource allocation indication in the scheduling message is mapped to a first predetermined table for time resource allocation, and the first predetermined table includes: The start symbol relative to the start of the scheduling interval; Transmission length, the number of consecutive symbols counted from the start symbol; and The flag indicates whether, when multiple scheduling intervals are scheduled with a single scheduling message, (a) the start symbol and the transmission length are applied to each scheduling interval such that there is a gap between the scheduling intervals, or (b) the start symbol is applied to the first scheduling interval among a plurality of scheduling intervals without gaps in between, and the transmission length is the transmission length for the last scheduling interval among the plurality of scheduling intervals, while all scheduling intervals between the first scheduling interval and the last scheduling interval have a transmission length equal to the scheduling interval length.

23. The method of claim 22, wherein, The scheduling interval is a time slot or a micro-time slot.

24. The method of claim 22 or 23, further comprising: Based on the configuration information, receive scheduling information for one or more downlink or uplink transmissions to or from the wireless communication device.

25. The method of claim 24, wherein, The scheduling information is received in a single scheduling message, which is transmitted in each of the multiple scheduling intervals.

26. A method in a wireless communication apparatus operating in a wireless communication system for multi-interval scheduling of downlink or uplink transmissions to or from said wireless communication apparatus, said method comprising: In a single scheduling message, (1102) scheduling information is received for one or more downlink or uplink transmissions to or from the wireless communication device. The number of scheduling intervals is specified in the scheduling message by a dedicated field or by a time resource allocation indicator, which implicitly or explicitly specifies the number of scheduling intervals. Wherein, the time resource allocation indication in the scheduling message is mapped to a first predetermined table for time resource allocation, and the first predetermined table includes: The start symbol relative to the start of the scheduling interval; Transmission length, the number of consecutive symbols counted from the start symbol; and The flag indicates whether, when multiple scheduling intervals are scheduled with a single scheduling message, (a) the start symbol and the transmission length are applied to each scheduling interval such that there is a gap between the scheduling intervals, or (b) the start symbol is applied to the first scheduling interval among a plurality of scheduling intervals without gaps in between, and the transmission length is the transmission length for the last scheduling interval among the plurality of scheduling intervals, while all scheduling intervals between the first scheduling interval and the last scheduling interval have a transmission length equal to the scheduling interval length.

27. The method of claim 26, wherein, The scheduling interval is a time slot or a micro-time slot.

28. The method of claim 26 or 27, further comprising: According to the scheduling message, send one or more uplink transmissions or receive one or more downlink transmissions.

29. The method according to any one of claims 26-28, wherein, The number of scheduling intervals is specified by a dedicated field in the scheduling message, wherein the first predetermined table for time resource allocation is different from the second predetermined table for time resource allocation applicable when the number of scheduling intervals is 1.

30. The method of claim 29, wherein, Each entry in one or more entries in the first predefined table includes any one or more of the following: The mapping type applicable to the first number of scheduling intervals; Mapping types applicable to scheduling intervals other than the first number of scheduling intervals; and Interval offset used for the first scheduling interval.

31. The method according to any one of claims 26-30, wherein, The single scheduling message will be transmitted and scheduled in each of the multiple scheduling intervals, wherein code block group feedback is configured and activated, and wherein: The scheduling message does not contain a code block group transmission indication field, and each of the RV and NDI bit widths is equal to the maximum number of scheduling time slots specified in the configuration information that signals the wireless communication device.

32. The method according to any one of claims 26-30, wherein, The single scheduling message will transmit the schedule within a single scheduling interval, wherein code block group feedback is configured and activated, and wherein: For a scheduling interval, specify RV and NDI; and The single scheduling message contains code block group transmission information (CGGTI) for the single scheduling interval.

33. The method according to any one of claims 26-32, wherein, The time resource allocation indication in the scheduling message is mapped to a first predetermined table of time resource allocation, wherein, for the time resource allocation indication in the scheduling message, the first predetermined table provides separate scheduling information for each scheduling interval.

34. The method of claim 33, wherein, For the time resource allocation indication in the scheduling message, the number of scheduling intervals is implicitly indicated by the first predetermined table, and invalid or null values ​​indicate scheduling information for any unscheduled interval.

35. The method according to any one of claims 26-34, wherein, The method further includes receiving a message identifying a subset of a first pre-defined table to which the time resource assignment indication in the scheduling message applies.

36. The method according to any one of claims 26-35, wherein, The scheduling message schedules uplink transmissions and includes an indication of whether the wireless communication device is allowed to use fewer than the total number of intervals scheduled by the scheduling message.

37. The method according to any one of claims 26-35, wherein, The scheduling message schedules uplink transmissions and includes an indication that the wireless communication device may use only one of the intervals scheduled by the scheduling message.

38. The method according to any one of claims 26-37, wherein, The scheduling message includes an indication of a listen-before-speak priority, wherein the indication applies to one or all of the scheduling intervals.

39. The method according to any one of claims 26-38, wherein, The scheduling message includes an indication of an energy detection threshold for the listen-before-speak operation, wherein the indication applies to one or all of the scheduling intervals.

40. The method according to any one of claims 26-28, wherein, The method includes receiving configuration information specifying a plurality of multi-interval scheduling configurations, each multi-interval scheduling configuration including one or more allocation parameters, wherein the scheduling message indicates one of the plurality of multi-interval scheduling configurations.

41. The method according to any one of claims 26-40, wherein, The scheduling message specifies different frequency resources for different scheduling intervals.

42. The method according to any one of claims 26-28, wherein, The resource assignment indication in the scheduling message is mapped to a first predetermined table of resource allocations, wherein the resource allocation in the first predetermined table of resource allocations identified by the resource assignment indication specifies different frequency resources for different scheduling intervals.

43. A network node adapted to perform the method according to any one of claims 1-21.

44. A network node comprising transceiver circuitry and processing circuitry operatively associated with the transceiver circuitry, and configured to perform the method according to any one of claims 1-21.

45. A wireless communication device adapted to perform the method according to any one of claims 22-42.

46. ​​A wireless communication device comprising transceiver circuitry and processing circuitry operatively associated with the transceiver circuitry, and configured to perform the method according to any one of claims 22-42.

47. A computer program product comprising instructions that, when executed on at least one processing circuit, cause the at least one processing circuit to perform the method according to any one of claims 1-42.

48. A computer-readable storage medium comprising a computer program that, when executed on at least one processing circuit, causes the at least one processing circuit to perform the method according to any one of claims 1-42.

Images