Patent Description:
3GPP Draft "<NPL>, discloses a method for resource allocation and TBS determination. 3GPP Draft "<NPL>, discloses advantageous CORESET configurations.

Methods and apparatus are disclosed from the perspective of a UE (User Equipment) and a network node, and are defined in the independent claims. The dependent claims define preferred embodiments thereof. In one embodiment, the method includes the UE being configured with a control resource set (CORESET). The UE is configured with a first UE-specific table with time domain resource allocation patterns for slot based scheduling and a second UE-specific table with time domain resource allocation patterns for mini-slot based scheduling. The method further includes the UE receiving a Downlink Control Information (DCI) on the CORESET in a middle of a slot, wherein DCI formats for both slot based scheduling and min-slot based scheduling are different and the UE determines which table of the first UE-specific table and the second UE-specific table to use based on the received DCI format, and wherein an index is included in the DCI and the index is pointing to an entry in a UE-specific table determined by the UE. The method also includes the UE receiving data in Orthogonal Frequency Division Multiplexing (OFDM) symbols determined according to the time domain resource allocation pattern of the entry in the UE-specific table.

The exemplary wireless communication systems and devices described below employ a wireless communication system, supporting a broadcast service. Wireless communication systems are widely deployed to provide various types of communication such as voice, data, and so on. These systems may be based on code division multiple access (CDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), 3GPP LTE (Long Term Evolution) wireless access, 3GPP LTE-A or LTE-Advanced (Long Term Evolution Advanced), 3GPP2 UMB (Ultra Mobile Broadband), WiMax, 3GPP NR (New Radio), or some other modulation techniques.

In particular, the exemplary wireless communication systems devices described below may be designed to support one or more standards such as the standard offered by a consortium named "3rd Generation Partnership Project" referred to herein as 3GPP, including: TSG RAN WG1 AH Meeting #<NUM> RAN1 Chairman's Notes; TSG RAN WG1 Meeting #<NUM> RAN1 Chairman's Notes; TSG RAN WG1 Meeting #88bis RAN1 Chairman's Notes; TSG RAN WG1 AH Meeting #<NUM> RAN1 Chairman's Notes; TSG RAN WG1 Meeting #<NUM> RAN1 Chairman's Notes; TSG RAN WG1 AH Meeting #<NUM> RAN1 Chairman's Notes; TSG RAN WG1 Meeting #90bis RAN1 Chairman's Notes; <NPL>"; <NPL>",<NPL>"; and <NPL>". The standards and documents listed above are hereby expressly incorporated by reference in their entirety.

<FIG> shows a multiple access wireless communication system according to one embodiment of the invention. An access network <NUM> (AN) includes multiple antenna groups, one including <NUM> and <NUM>, another including <NUM> and <NUM>, and an additional including <NUM> and <NUM>. In <FIG>, only two antennas are shown for each antenna group, however, more or fewer antennas may be utilized for each antenna group. Access terminal <NUM> (AT) is in communication with antennas <NUM> and <NUM>, where antennas <NUM> and <NUM> transmit information to access terminal <NUM> over forward link <NUM> and receive information from access terminal <NUM> over reverse link <NUM>. Access terminal (AT) <NUM> is in communication with antennas <NUM> and <NUM>, where antennas <NUM> and <NUM> transmit information to access terminal (AT) <NUM> over forward link <NUM> and receive information from access terminal (AT) <NUM> over reverse link <NUM>. In a FDD system, communication links <NUM>, <NUM>, <NUM> and <NUM> may use different frequency for communication. For example, forward link <NUM> may use a different frequency then that used by reverse link <NUM>.

In communication over forward links <NUM> and <NUM>, the transmitting antennas of access network <NUM> may utilize beamforming in order to improve the signal-to-noise ratio of forward links for the different access terminals <NUM> and <NUM>. Also, an access network using beamforming to transmit to access terminals scattered randomly through its coverage causes less interference to access terminals in neighboring cells than an access network transmitting through a single antenna to all its access terminals.

An access network (AN) may be a fixed station or base station used for communicating with the terminals and may also be referred to as an access point, a Node B, a base station, an enhanced base station, an evolved Node B (eNB), or some other terminology. An access terminal (AT) may also be called user equipment (UE), a wireless communication device, terminal, access terminal or some other terminology.

<FIG> is a simplified block diagram of an embodiment of a transmitter system <NUM> (also known as the access network) and a receiver system <NUM> (also known as access terminal (AT) or user equipment (UE)) in a MIMO system <NUM>. At the transmitter system <NUM>, traffic data for a number of data streams is provided from a data source <NUM> to a transmit (TX) data processor <NUM>.

Preferably, each data stream is transmitted over a respective transmit antenna. TX data processor <NUM> formats, codes, and interleaves the traffic data for each data stream based on a particular coding scheme selected for that data stream to provide coded data.

The coded data for each data stream may be multiplexed with pilot data using OFDM techniques. The pilot data is typically a known data pattern that is processed in a known manner and may be used at the receiver system to estimate the channel response. The multiplexed pilot and coded data for each data stream is then modulated (i.e., symbol mapped) based on a particular modulation scheme (e.g., BPSK, QPSK, M-PSK, or M-QAM) selected for that data stream to provide modulation symbols. The data rate, coding, and modulation for each data stream may be determined by instructions performed by processor <NUM>.

At receiver system <NUM>, the transmitted modulated signals are received by NR antennas 252a through 252r and the received signal from each antenna <NUM> is provided to a respective receiver (RCVR) 254a through 254r. Each receiver <NUM> conditions (e.g., filters, amplifies, and downconverts) a respective received signal, digitizes the conditioned signal to provide samples, and further processes the samples to provide a corresponding "received" symbol stream.

Turning to <FIG>, this figure shows an alternative simplified functional block diagram of a communication device according to one embodiment of the invention. As shown in <FIG>, the communication device <NUM> in a wireless communication system can be utilized for realizing the UEs (or ATs) <NUM> and <NUM> in <FIG> or the base station (or AN) <NUM> in <FIG>, and the wireless communications system is preferably the NR system. The communication device <NUM> may include an input device <NUM>, an output device <NUM>, a control circuit <NUM>, a central processing unit (CPU) <NUM>, a memory <NUM>, a program code <NUM>, and a transceiver <NUM>. The control circuit <NUM> executes the program code <NUM> in the memory <NUM> through the CPU <NUM>, thereby controlling an operation of the communications device <NUM>. The communications device <NUM> can receive signals input by a user through the input device <NUM>, such as a keyboard or keypad, and can output images and sounds through the output device <NUM>, such as a monitor or speakers. The transceiver <NUM> is used to receive and transmit wireless signals, delivering received signals to the control circuit <NUM>, and outputting signals generated by the control circuit <NUM> wirelessly. The communication device <NUM> in a wireless communication system can also be utilized for realizing the AN <NUM> in <FIG>.

<FIG> is a simplified block diagram of the program code <NUM> shown in <FIG> in accordance with one embodiment of the invention. In this embodiment, the program code <NUM> includes an application layer <NUM>, a Layer <NUM> portion <NUM>, and a Layer <NUM> portion <NUM>, and is coupled to a Layer <NUM> portion <NUM>. The Layer <NUM> portion <NUM> generally performs radio resource control. The Layer <NUM> portion <NUM> generally performs link control. The Layer <NUM> portion <NUM> generally performs physical connections.

As discussed in the 3GPP TS RAN WG1 AH Meeting #<NUM> RAN1 Chairman's Notes, timing between DL assignment and corresponding DL data can be dynamically indicated by a DCI as follows:.

As discussed in the 3GPP TS RAN WG1 Meeting #<NUM> RAN1 Chairman's Notes, mini-slot definition is defined below. The first agreement describes about properties of mini-slot, such as flexible length from <NUM> to slot length-<NUM>, or starting at any OFDM (Orthogonal Frequency Division Multiplexing) symbol.

As discussed in the 3GPP TS RAN WG1 Meeting #88bis RAN1 Chairman's Notes, two agreements are described as follows:.

Two agreements, discussed in the 3GPP TS RAN AH WG1 Meeting #<NUM> RAN1 Chairman's Notes, are provided below. The first agreement (provided below) is related to the first DMRS (Demodulation Reference Signal) position of a PDSCH (Physical Downlink Shared Channel). Since DMRS of a PDSCH is used for channel estimation, DMRS position of the PDSCH is better to be transmitted on earlier scheduled OFDM symbol. In general, for slot-based scheduling, OFDM symbols for control may be transmitted on the beginning of a slot. Hence, for slot-based scheduling, DMRS position of a PDSCH is fixed on the <NUM>rd or <NUM>th symbol of the slot. The second agreement (provided below) describes parameters about CORESET configured by UE-specific higher-layer signalling.

Two agreements, discussed in the 3GPP TS RAN WG1 Meeting #<NUM> RAN1 Chairman's Notes, are provided below. In order to satisfy multiple services in NR, the first one lists possible signaling about time domain resource allocation in a scheduling DCI (Downlink Control Information). For example, for delay-sensitive services such as URLLC (Ultra-Reliable and Low Latency Communications), a DCI scheduling for non-slot (i.e. mini-slot) transmission is necessary to guarantee low latency requirements. Furthermore, the first agreement (as provided below) describes a UE can be informed of time domain resource allocation of the scheduled transmission by a scheduling DCI without prior information about DL (Donwlink)/UL (Uplink) assignment. Based on the second agreement, possible mini-slot length is <NUM>, <NUM>, <NUM> OFDM symbols are assumed. However, for future flexibility, more mini-slot lengths are expected.

Three agreements, discussed in the 3GPP TS RAN WG1 AH Meeting #<NUM> RAN1 Chairman's Notes, are provided below. In NR, coverage of a cell is still an issue needed to handle. The first agreement (as provided below) describes about TB repetition spanning multiple slots or mini-slots for grant-based transmission in order to solve above-mentioned issue. The second and third agreement (as provided below) are relative to dynamic SFI (Slot Format Information), wherein the second one describes the content of dynamic SFI and the third one emphasize on status "unknown" in dynamic SFI.

Some agreements, discussed in the 3GPP TS RAN WG1 Meeting #90bis RAN1 Chairman's Notes, are provided as follow. In <NUM> NR, time domain resource allocation of unicast transmission can be more flexible in terms of starting position and length than in LTE. The first agreement describes a DCI (Downlink Control Information) indicates an index into a UE-specific table giving OFDM symbols used for PDSCH or PUSCH (Physical Uplink Shared Channel) transmission for both slot and mini-slot scheduling. The second agreement is relative to resource set for rate matching purpose. The last three agreements are related to slot format information (SFI). In order to utilize radio resources more efficiently, it is generally better to allow NW to adjust transmission direction dynamically based on current DL and/or UL traffic.

For the UE specific single-slot/multi-slotset SFI table configuration.

Some targets of URLLC are discussed in 3GPP TR <NUM> as follows:.

Control plane latency refers to the time to move from a battery efficient state (e.g., IDLE) to start of continuous data transfer (e.g., ACTIVE).

The target for control plane latency should be <NUM>.

Analytical evaluation is used as the evaluation methodology.

The time it takes to successfully deliver an application layer packet/message from the radio protocol layer <NUM>/<NUM> SDU ingress point to the radio protocol layer <NUM>/<NUM> SDU egress point via the radio interface in both uplink and downlink directions, where neither device nor Base Station reception is restricted by DRX.

For URLLC the target for user plane latency should be <NUM> for UL, and <NUM> for DL. Furthermore, if possible, the latency should also be low enough to support the use of the next generation access technologies as a wireless transport technology that can be used within the next generation access architecture.

For eMBB, the target for user plane latency should be <NUM> for UL, and <NUM> for DL.

When a satellite link is involved in the communication with a user equipment, the target for user plane RTT can be as high as <NUM> for GEO satellite systems, up to <NUM> for MEO satellite systems, and up to <NUM> for LEO satellite systems.

Reliability can be evaluated by the success probability of transmitting X bytes within a certain delay, which is the time it takes to deliver a small data packet from the radio protocol layer <NUM>/<NUM> SDU ingress point to the radio protocol layer <NUM>/<NUM> SDU egress point of the radio interface, at a certain channel quality (e.g., coverage-edge).

A general URLLC reliability requirement for one transmission of a packet is <NUM>-<NUM>-<NUM> for <NUM> bytes with a user plane latency of <NUM>.

For eV2X, for communication availability and resilience and user plane latency of delivery of a packet of size [<NUM> bytes], the requirements are as follows:.

Note that target communication range and reliability requirement is dependent of deployment and operation scenario (e.g., the average inter-vehicle speed).

Link level evaluation with deployment scenario specific operating point and system level simulation are to be performed for the evaluations are Indoor Hotspot, Urban Macro, Highway, and Urban grid for connected car.

[Editor's notes: other KPIs and use cases for eV2X may be added if needed after progress in SA1.

A running CR is described in 3GPP R1-<NUM> as provided below. his is relative to LTE sTTI (shortened TTI). A UE can distinguish scheduling DCI is for <NUM> subframe scheduling or sTTI scheduling by different DCI formats as quotation DCI format <NUM>-0A for uplink and DCI format <NUM>-1A for downlink.

DCI format <NUM>-0A is used for the scheduling of PUSCH with slot or subslot duration in one UL cell.

The following information is transmitted by means of the DCI format <NUM>-0A:.

If the number of information bits in format <NUM>-0A mapped onto a given search space is less than the payload size of format <NUM>-1A for scheduling the same serving cell and mapped onto the same search space (including any padding bits appended to format <NUM>-1A), zeros shall be appended to format <NUM>-0A until the payload size equals that of format <NUM>-1A.

DCI format <NUM>-1A is used for the scheduling of one PDSCH codeword with slot or subslot duration in one cell.

The following information is transmitted by means of the DCI format <NUM>-1A:.

If the UE is configured to decode SPDCCH CRC scrambled by the C-RNTI and the number of information bits in format <NUM>-1A mapped onto a given search space is less than that of format <NUM>-0A for scheduling the same serving cell and mapped onto the same search space, zeros shall be appended to format <NUM>-1A until the payload size equals that of format <NUM>-0A, except when format <NUM>-1A assigns downlink resource on a secondary cell without an uplink configuration associated with the secondary cell.

In 3GPP TS <NUM>, numerology is defined as subcarrier spacing and CP length as follows:.

Throughout this specification, unless otherwise noted, the size of various fields in the time domain is expressed as a number of time units Ts =<NUM>/(Δfmax·Nf) where Δfmax=<NUM>·<NUM><NUM> Hz and Nf = <NUM>.

Multiple OFDM numerologies are supported as given by Table <NUM>-<NUM>.

One contiguous resource allocation type, as described in 3GPP TS <NUM>,<NUM>, is provided below. An RIV (Resource Indication Value) is associated with/ represents a contiguous resource allocation pattern. In addition, a RIV is calculated based on the quotation below.

In resource allocations of type <NUM>, the resource block assignment information indicates to a scheduled UE a set of contiguously allocated localized virtual resource blocks or distributed virtual resource blocks. In case of resource allocation signalled with PDCCH DCI format 1A, 1B or 1D, one bit flag indicates whether localized virtual resource blocks or distributed virtual resource blocks are assigned (value <NUM> indicates Localized and value <NUM> indicates Distributed VRB assignment) while distributed virtual resource blocks are always assigned in case of resource allocation signalled with PDCCH DCI format 1C. Localized VRB allocations for a UE vary from a single VRB up to a maximum number of VRBs spanning the system bandwidth. For DCI format 1A the distributed VRB allocations for a UE vary from a single VRB up to <MAT> VRBs, where <MAT> is defined in [<NUM>], if the DCI CRC is scrambled by P-RNTI, RA-RNTI, or SI-RNTI. With PDCCH DCI format 1B, 1D, or 1A with a CRC scrambled with C-RNTI, distributed VRB allocations for a UE vary from a single VRB up to <MAT> VRBs if <MAT> is <NUM>-<NUM> and vary from a single VRB up to <NUM> if <MAT> is <NUM>-<NUM>. With PDCCH DCI format 1C, distributed VRB allocations for a UE vary from <MAT> VRB(s) up to <MAT> VRBs with an increment step of <MAT>, where <MAT> value is determined depending on the downlink system bandwidth as shown in Table <NUM>. <NUM>-<NUM>.

[Table <NUM>. <NUM>-<NUM> of 3GPP TS <NUM>. <NUM>, entitled " <MAT> values vs. Downlink System Bandwidth", is reproduced as FIG.

For PDCCH DCI format 1A, 1B or 1D, a type <NUM> resource allocation field consists of a resource indication value (RIV) corresponding to a starting resource block (RBstart) and a length in terms of virtually contiguously allocated resource blocks LCRBs. The resource indication value is defined by
<IMG>.

For PDCCH DCI format 1C, a type <NUM> resource block assignment field consists of a resource indication value (RIV) corresponding to a starting resource block (RBstart=<NUM>, <MAT>,. , <MAT>) and a length in terms of virtually contiguously allocated resource blocks <MAT>. The resource indication value is defined by
<IMG>.

One or multiple of following terminologies may be used hereafter:.

In wireless communication system, transmission directions, including downlink from NW (e.g. BS) to a UE and uplink from UE to NW, need to be configured appropriately.

In LTE, time duration of a scheduled data channel (PDSCH or PUSCH) is within a subframe excluding OFDM symbols used for other purpose such as for transmitting downlink control information and/or GAP, UL OFDM symbol considering frame structure type <NUM> (TDD). Furthermore, UEs are configured with a frame structure type during initial access procedure and be aware of a number of OFDM symbols for downlink control information by decoding PCFICH (Physical Control Format Indicator Channel). Hence, UEs can know time duration of a scheduled data channel, and there is no need to indicate time duration of the scheduled data channel in a downlink control signal.

In <NUM> NR, multiple services with different requirements are expected to be supported. The services can be broadly and generally classified as follows: services requiring very low latency and high reliability (i.e. Ultra Reliable Low Latency Communication (URLLC)), services requiring very high data rates (i.e. Enhanced Mobile Broadband (eMBB)), and/or services with enhanced coverage (i.e. Massive Machine Type Communication (mMTC)). However, different services mentioned above may need different time duration for data channel to meet each requirement. For example, it would be beneficial to transmit on a fewer number of OFDM symbols to meet URLLC requirement; however, for other services, latency may not be the highest priority.

Hence, multiple time domain resource allocation schemes are proposed in 3GPP TSG RANWG1 Meeting #<NUM> RAN1 Chairman's Notes. Based on 3GPP TSG RAN WG1 Meeting #88bis RAN1 Chairman's Notes, in order to dynamically allocate data channel, time duration of a data channel indicated in a DCI is proposed. Based on 3GPP TSG RAN WG1 Meeting #90bis RAN1 Chairman's Notes, a UE-specific table is configured for a UE, and each entry in the table represents a time domain resource allocation pattern possibly comprising a starting OFDM symbol and length or duration for a data channel (PDSCH or PUSCH). A UE receives a scheduling DCI indicating an index of one entry in the UE-specific table for time domain resource allocation of scheduled data transmission (PDSCH or PUSCH).

Based on 3GPP TSG RAN WG1 Meeting #<NUM> RAN1 Chairman's Notes, minimum granularity for monitoring DCI may be different in case of slot scheduling and mini-slot scheduling. For slot-scheduling, CORESET(s) (control resource set) may exist at the beginning of a slot which means once per slot. For mini-slot scheduling, it would be beneficial to configure CORESET(s) starting OFDM symbol (or the first OFDM symbol) in the middle of a slot to meet delay-sensitive services (e.g. URLLC). Taking the range of each time domain resource allocation pattern equal to one slot as an example (ranges greater or smaller than one slot are also possible), the concerned problem is illustrated below.

Considering a CORESET may start in the middle of a slot, if a time domain resource allocation pattern in the UE-specific table indicates resource allocation starting before the CORESET, the UE will need to receive and buffer OFDM symbols before monitoring the CORESET. For example, as shown in <FIG>, a CORESET starts at OFDM symbol index #<NUM> and a UE receives a DCI indicating time pattern with resource allocation starting from OFDM symbol index #<NUM> with length <NUM> (e.g. the decimal index in DCI = <NUM>). Buffering the received signal/data not only induces complexity but also requires extra memories in UE. Besides, a UE in LTE generally only needs to receive data after decoding the DCI. Thus, attempting to receive data even if there is no DCI indicating the presence of data will cause UE power consumption unnecessarily. Hence, how a UE interprets the UE-specific table properly when receiving scheduling DCI on CORESET starting in the middle of a slot needs to be considered. Potential solutions are described below.

A UE is configured with at least a control resource set (CORESET). The control resource set starts at an OFDM symbol index. The UE receives a DCI on the control resource set scheduling data transmission. The DCI indicates an index pointing to an entry in a UE-specific table configured by a NW. The UE receives scheduled data on resources with time domain allocated according to the index and an offset.

A slot comprises <NUM> symbols. In one example embodiment, time domain resource allocation (e.g. within a slot) carried in DCI is contiguous in time domain. Considering contiguous time domain resource allocation of a slot, there could be <NUM> time domain resource allocation patterns. In another example embodiment, time domain resource allocation (e.g. within a slot) carried in DCI is non-contiguous in time domain.

Considering non-contiguous time domain resource allocation of a slot, a NW may configure a UE with possible non-contiguous time domain resource allocation patterns. Non-contiguous resource allocation of a slot can be indicated by a bit map, e.g. with length equal to number of OFDM symbol in a slot (<NUM>) and each bit in the bitmap indicates whether a symbol in a slot is allocated. Alternatively, non-contiguous resource allocation of a slot can be indicated by contiguous time domain resource allocation of a slot and a DL resource set.

A UE may be configured with at least one DL resource set by a NW and each DL resource set may indicate which OFDM symbols within a slot (or multiple slots) are allocated for PDSCH. More specifically, the NW can indicate the DL resource set to the UE by a DCI. Alternatively the DCI may be the scheduled DCI. If there is no indication by the NW, the UE cannot use the DL resource set.

For example, a slot with a SFI as shown in <FIG> is known by a UE. The UE is configured with a DL resource set indicating OFDM symbol index #<NUM> and index #<NUM> are reserved (i.e. not allocated for PDSCH). In <FIG>, X represents "Unknown", DL represents a downlink transmission, and UL represents an uplink transmission. As shown <FIG>, with the contiguous time domain resource allocation pattern and the resource set indicated in the DCI or an upper layer signaling, the UE can know that all the time domain resource in the contiguous time domain resource allocation pattern except OFDM symbol index #<NUM> and index #<NUM> are allocated to the UE. The UE receives the scheduled data based on the contiguous time domain resource allocation pattern and rate match around the DL resource set.

As shown in <FIG>, if the UE misses the SFI of the slot, the UE can receive scheduled data based on the contiguous time domain resource allocation pattern and the indication about the DL resource set. In <FIG>, X represents "Unknown", and DL represents a downlink transmission. As shown in <FIG>, a DL resource set can be configured in the middle of a slot in order to rate match around UL OFDM symbol index when SFI is missed.

Each time domain resource allocation pattern may be associated with or represented by a RIV (Resource Indication Value). For example, as illustrated in <FIG>, considering the range of time domain resource allocation patterns within a slot, each dot represents a time domain resource allocation pattern from a starting OFDM symbol to an ending OFDM symbol and different time domain resource allocation patterns may have different symbol lengths. Different starting OFDM symbol indexes may have different number of time domain resource patterns. For example, the starting OFDM symbol index #<NUM> has <NUM> time domain resource patterns, the starting OFDM symbol index #<NUM> has <NUM> time domain resource patterns,. , and the starting OFDM symbol index #<NUM> has <NUM> time domain resource pattern.

The RIV indexing rule is that the initial RIV value "<NUM>" is assigned to the time domain resource pattern with starting OFDM symbol index #<NUM> and symbol length of <NUM>, the RIV indexes increase by keeping the same starting OFDM symbol index and increasing the symbol lengths until the maximum symbol length of <NUM>, the next set of RIV indexes then start from the next starting OFDM symbol index (i.e. #<NUM>), and so on. For example, as shown in <FIG>, OFDM symbol index #<NUM> has <NUM> possible time domain resource allocation patterns indexed as <NUM> to <NUM>. Followed by OFDM symbol index #<NUM>, time domain resource allocation patterns are indexed as <NUM> to <NUM>.

The UE-specific table could be a subset of whole possible time domain resource allocation patterns. Alternatively, the UE-specific table could comprise whole possible time domain resource allocation patterns. Each entry of the UE-specific table represents a time domain resource allocation pattern. A number of binary bits in the DCI indicate the index. The number of bits should be able to represent all entries in the UE-specific table. Alternatively, the number of bits may represent whole possible time domain resource allocation patterns of a slot. For example, as shown in <FIG>, assuming that there are <NUM> bits in the DCI indicating the index of an entry in the UE-specific table which is a subset of whole contiguous time domain resource allocation patterns. As illustrated in <FIG>, <FIG> bits in the DCI of '<NUM>' (i.e. <NUM> in decimal) points to an entry in the UE-specific table which is a time domain resource allocation pattern with resource allocation starting from OFDM symbol index #<NUM> to #<NUM>.

The CORESET configuration comprises at least a starting OFDM symbol index of the CORESET. If the starting OFDM symbol index is #<NUM>, the offset is <NUM> and the UE interprets the UE-specific table by mapping time domain resource allocation pattern of each entry into a pattern starting from the starting OFDM symbol index of the CORESET. Considering that the CORESET may span for at most <NUM> OFDM symbols, the data may be scheduled overlapping with the CORESET region or after the CORESET region, depending on whether all CORESET resources are used. For flexibility, a number of OFDM symbols could be further added as the offset. More specifically, the number may be derived by the UE according to information received from NW. Alternatively, the number may be configured by NW or specified in the standards. For example, if the number is equal to <NUM> OFDM symbol, it means the UE could only be scheduled after the offset (i.e. <NUM> OFDM symbol) i.e. the UE will not be scheduled in OFDM symbol index #<NUM>. If the starting OFDM symbol index of the CORESET is not #<NUM>, the offset is determined according to the starting OFDM symbol index as described below.

If the starting OFDM symbol index of an entry of the UE-specific table is less than the starting OFDM symbol index of the CORESET, the UE interprets the UE-specific table based on the starting OFDM symbol index of the CORESET. For example, as shown in <FIG>, assuming time pattern of each entry of the UE-specific table is chosen from the big triangle, if the starting OFDM symbol index of the CORESET is #<NUM>, the mapping is from big triangle to small triangle in which the patterns start from OFDM symbol index #<NUM> i.e. each time domain resource allocation pattern is shifted to the right side by <NUM> OFDM symbols. In this situation, the offset is equal to <NUM> OFDM symbols. For flexibility, a number of OFDM symbols described above could be further added to the starting OFDM symbol index of the CORESET as the offset. Although the time domain resource allocation patterns shown in <FIG> are limited to one slot, it is also possible that the time domain resource allocation patterns (before or after the mapping) may cross the slot boundary so that data can be scheduled cross the slot boundary.

Preferably, a mapping way interpreted by the UE is that if the starting OFDM symbol index of time domain resource allocation pattern of an entry in the UE-specific table is smaller than the OFDM symbol index of the CORESET, the starting OFDM symbol index of the time domain resource allocation pattern of the entries adds the offset. More specifically, the offset value is equal to the starting OFDM symbol index of the CORESET. For example, as shown in <FIG>, considering the starting OFDM symbol index of the CORESET is #<NUM>, time patterns of first entry and second entry are interpreted by the UE via adding the offset to the starting OFDM symbol indexes of the first entry and the second entry. That is the time domain resource allocation pattern of the first entry spans from symbol #<NUM> to symbol #<NUM> and the time domain resource allocation pattern of the second entry spans from symbol #<NUM> to symbol #<NUM>. In other words, the time domain of the scheduled data is determined by a time domain resource allocation pattern and an offset, wherein the starting OFDM symbol of the scheduled data is equal to the starting OFDM symbol index of time domain resource allocation pattern plus the offset. More specifically, the offset value is the starting OFDM symbol index of the CORESET. For flexibility, a number of OFDM symbols could be further added to the starting OFDM symbol index of the CORESET as the offset.

Preferably, a mapping way is that RIV of time domain resource allocation pattern is interpreted based on the offset. The offset value is sum of number of RIV starting from OFDM symbol index(s) smaller than the starting OFDM symbol index of the CORESET. For example, if RIV is indexed as illustrated in <FIG> and the starting OFDM symbol index of the CORESET is #<NUM>, the offset is <NUM> calculated as sum of a respective number of RIVs of OFDM symbol indexes from #<NUM> to #<NUM>. Considering an ordinary RIV of an entry of the UE-specific table which is <NUM>, updated RIV is <NUM> based on following equation <NUM> mod (<NUM>-<NUM>) + <NUM>. Time domain of the scheduled data is indicated by the index pointing to an entry of the UE-specific table where ordinary RIV of the entry is updated based on a following calculation that performs a modulo operation on the RIV with the possible number of RIVs and adds the offset (in other words taking mod possible number of RIVs and adding the offset).

Preferably, a mapping way interpreted by the UE is that if the starting OFDM symbol index of time domain resource allocation pattern of an entry in the UE-specific table is smaller than the OFDM symbol index of the CORESET, an offset is added to the time domain resource allocation pattern for determining the time domain of the scheduled data. Otherwise, there is no need to add the offset and the time domain resource allocation pattern remains the same. More specifically, the offset value is the starting OFDM symbol index of the CORESET. For example, as shown in <FIG>, the time domain resource allocation pattern of the first entry and the second entry in the UE-specific table needs to add the offset and the last entry remains the same in case the starting OFDM symbol index of the CORESET is #<NUM>.

If the length of time domain resource allocation pattern of the entries adding the offset is larger than the slot length, the OFDM symbols with indexes exceeding the slot boundary will appear in the beginning of next slot. For example, as illustrated in <FIG>, considering the starting OFDM symbol index of the CORESET is #<NUM>, time patterns of the first entry and the second entry are interpreted by the UE via adding the offset. That is the time domain resource allocation pattern of the first entry spans from symbol #<NUM> to symbol #<NUM> and the last two OFDM symbols of the resource allocation pattern (i.e. symbols #<NUM> and #<NUM>) appear in the beginning of the next slot. <FIG> further illustrates the occupied OFDM symbols of the time domain resource allocation pattern of the first entry.

Similarly, the time domain resource allocation pattern of the second entry in <FIG> spans from symbol #<NUM> to symbol #<NUM> and the last two OFDM symbols of the resource allocation pattern (i.e. symbols #<NUM> and #<NUM>) appear in the beginning of the next slot. In other words, the time domain of the scheduled data is determined by a time domain resource allocation pattern and an offset, wherein the starting OFDM symbol of the scheduled data is equal to the starting OFDM symbol index of time domain resource allocation pattern plus the offset. More specifically, the offset value is equal to the starting OFDM symbol index of the CORESET.

Alternatively, if the length of time domain resource allocation pattern of the entries plus the offset is larger than the slot length, the OFDM symbols with indexes exceeding slot boundary may be ignored by the UE. For example, as shown in <FIG>, considering the starting OFDM symbol index of the CORESET is #<NUM>, time patterns of the first entry and the second entry is interpreted by the UE via adding the offset. That is the time domain resource allocation pattern of the first entry spans from symbol #<NUM> to symbol #<NUM> and the time domain resource allocation pattern of the second entry spans from symbol #<NUM> to symbol #<NUM>. Length of the time domain resource allocation pattern of the first entry and the second entry interpreted by the UE is reduced. Two last OFDM symbols of the time domain resource allocation pattern of the first entry and the second entry are ignored by the UE. For flexibility, a number of OFDM symbols described above could be further added to the starting OFDM symbol index of the CORESET as the offset.

Preferably, a mapping way interpreted by the UE is that an offset is added to the time domain resource allocation patterns of entries in the UE-specific table no matter whether the starting OFDM symbol index of time domain resource allocation pattern of an entry in the UE-specific table is smaller or larger than the OFDM symbol index of the CORESET. More specifically, the offset value is the starting OFDM symbol index of the CORESET. The lengths of time domain resource allocation patterns of entries in the UE-specific table remain the same. For example, as shown in <FIG>, the offset is added to all entries in the UE-specific table.

If the length of time domain resource allocation pattern plus the offset is larger than the slot length, the OFDM symbols with indexes exceeding the slot boundary appear in the beginning of the next slot. For example, as illustrated in <FIG>, considering the starting OFDM symbol index of the CORESET is #<NUM>, time patterns of the first entry and the second entry are interpreted by the UE via adding the offset. That is the time domain resource allocation pattern of the first entry includes symbol #<NUM> to symbol #<NUM> as well as two OFDM symbols in the beginning of the next slot and the time domain resource allocation pattern of the second entry includes symbol #<NUM> to symbol #<NUM> as well as two OFDM symbols in the beginning of the next slot. In other words, the time domain of the scheduled data is determined by a time domain resource allocation pattern and an offset, wherein the starting OFDM symbol of the scheduled data is equal to the starting OFDM symbol index of time domain resource allocation pattern plus the offset. More specifically, the offset value is equal to the starting OFDM symbol index of the CORESET.

Alternatively, if the length of time domain resource allocation pattern of the entries plus the offset is larger than the slot length, the OFDM symbols with indexes exceeding slot boundary may be ignored by the UE. For example, as illustrated in <FIG>, considering the starting OFDM symbol index of the CORESET is #<NUM>, time patterns of the first entry and the second entry are interpreted by the UE via adding the offset. That is the time domain resource allocation pattern of the first entry spans from symbol #<NUM> to symbol #<NUM> and the time domain resource allocation pattern of the second entry spans from symbol #<NUM> to symbol #<NUM>. Length of the time domain resource allocation pattern of the first entry and the second entry interpreted by the UE is reduced. Two last OFDM symbols of the time domain resource allocation pattern of the first entry and the second entry are ignored by the UE. For flexibility, a number of OFDM symbols described above could be further added to the starting OFDM symbol index of the CORESET as the offset.

If the number of binary bits in the DCI indicating the index can represent time domain resource allocation patterns starting from the starting OFDM symbol index of the CORESET, a default table may be used instead of the UE-specific table. For example, considering a CORESET starting at OFDM symbol index #<NUM>, number of RIVs starting from OFDM symbol indexes #<NUM> to #<NUM> is <NUM>. If the number of binary bits in the DCI indicating the index pointing to the UE-specific table is <NUM> bits which can represents <NUM> time domain resource allocation patterns, a default table different from the UE-specific table is used. More specifically, each entry in the default table represents a time domain resource allocation pattern starting from the starting OFDM symbol index of the CORESET. More specifically, the default table can represent possible time domain resource allocation patterns starting from the starting OFDM symbol index of the CORESET. The time domain of the scheduled data is indicated by the index pointing to an entry in the default table.

Preferably, if a field in the DCI indicates the timing between the starting OFDM symbol index of the CORESET and the scheduled data transmission (PUSCH or PDSCH), there is no need for the time domain resource allocation patterns in the UE-specific table to indicate the starting OFDM symbol of the scheduled data transmission. In other words, the scheduled data transmission in each time domain resource allocation pattern starts from the symbol indicated by this field, which may be among a set of values configured by higher layer. For contiguous time domain resource allocation, the time domain resource allocation patterns of entries in the UE-specific table may just provide a time length. For non-contiguous time domain resource allocation, a time domain resource allocation pattern along or combined with a DL resource set (as described above) may indicate which OFDM symbols are allocated to the UE. The UE receives the scheduled data according to the index and the timing indicated in the DCI.

The UE is configured with at least two UE-specific tables with time domain resource allocation patterns, one of which is for slot based scheduling and one of which is for min-slot based scheduling. More specifically, DCI formats for both slot based scheduling and min-slot based scheduling are different. The UE determines which table to use based on the received DCI format.

<FIG> is a flow chart <NUM> according to one exemplary embodiment from the perspective of a UE. In step <NUM>, the UE is configured with a CORESET. In step <NUM>, the UE receives a DCI on the CORESET, wherein an index is included in the DCI and the index indicates a time domain resource allocation pattern. In step <NUM>, the UE receives data in OFDM symbols determined according to the time domain resource allocation pattern, wherein a range of the time domain resource allocation pattern starts from the first OFDM symbol of the CORESET or after an offset from the first OFDM symbol of the CORESET, and the range of the time domain resource allocation pattern may end across a slot boundary.

Referring back to <FIG> and <FIG>, in one exemplary embodiment of a UE configured with a CORESET, the device <NUM> includes a program code <NUM> stored in the memory <NUM>. The CPU <NUM> could execute program code <NUM> to enable the UE (i) to receive a DCI on the CORESET, wherein an index is included in the DCI and the index indicates a time domain resource allocation pattern, and (ii) to receive data in OFDM symbols determined according to the time domain resource allocation pattern, wherein a range of the time domain resource allocation pattern starts from the first OFDM symbol of the CORESET or after an offset from the first OFDM symbol of the CORESET, and the range of the time domain resource allocation pattern may end across a slot boundary. Furthermore, the CPU <NUM> can execute the program code <NUM> to perform all of the above-described actions and steps or others described herein.

<FIG> is a flow chart <NUM> according to one exemplary embodiment from the perspective of a network node. In step <NUM>, the network node configures a UE with a control resource set. In step <NUM>, the network node transmits a DCI on the CORESET to the UE, wherein an index is included in the DCI and the index indicates a time domain resource allocation pattern. In step <NUM>, the network node transmits data to the UE in OFDM symbols determined according to the time domain resource allocation pattern, wherein a range of the time domain resource allocation pattern starts from the first OFDM symbol of the CORESET or after an offset from the first OFDM symbol of the CORESET and the range of the time domain resource allocation pattern may end across a slot boundary.

Referring back to <FIG> and <FIG>, in one exemplary embodiment of a network node, the device <NUM> includes a program code <NUM> stored in the memory <NUM>. The CPU <NUM> could execute program code <NUM> to enable the network node (i) to configure a UE with a control resource set, (ii) to transmit a DCI on the CORESET to the UE, wherein an index is included in the DCI and the index indicates a time domain resource allocation pattern, and (iii) to transmit data to the UE in OFDM symbols determined according to the time domain resource allocation pattern, wherein a range of the time domain resource allocation pattern starts from the first OFDM symbol of the CORESET or after an offset from the first OFDM symbol of the CORESET and the range of the time domain resource allocation pattern may end across a slot boundary. Furthermore, the CPU <NUM> can execute the program code <NUM> to perform all of the above-described actions and steps or others described herein.

In the context of the embodiments illustrated in <FIG> and <FIG> and described above, preferably, the offset is a number of OFDM symbol(s), wherein the number could be derived by the UE according to information received from a network node, configured by the network node, or specified in the standards. The index could point to an entry of a UE-specific table which is configured by a network (NW). Each entry of the UE-specific table could comprise a time domain resource allocation pattern.

Preferably, the time domain resource allocation in each entry of the UE-specific table could be contiguous. A slot could comprise <NUM> OFDM symbols. The offset value could be a starting OFDM symbol index of the CORESET.

Preferably, if a starting OFDM symbol index of time domain resource allocation pattern of an entry indicated by the index is smaller than the starting OFDM symbol index of the CORESET, the starting OFDM symbol index of time domain resource allocation pattern may add the offset. However, additionally or alternatively preferably, if a starting OFDM symbol index of time domain resource allocation pattern of an entry indicated by the index is larger than or equal to the starting OFDM symbol index of the CORESET, the starting OFDM symbol index of time domain resource allocation pattern may not add the offset.

Preferably, the offset value could be added for mapping time domain resource allocation pattern of each entry of the UE-specific table into starting at the starting OFDM symbol index of the CORESET.

<FIG> is a flow chart <NUM> according to one exemplary embodiment from the perspective of a UE. In step <NUM>, the UE is configured with a CORESET. In step <NUM>, the UE receives a DCI on the CORESET, wherein an index is included in the DCI and the index indicates a time domain resource allocation pattern. In step <NUM>, the UE receives data in OFDM symbols determined according to the time domain resource allocation pattern, wherein a range of the time domain resource allocation pattern starts from the first OFDM symbol of the CORESET or after an offset from the first OFDM symbol of the CORESET.

Referring back to <FIG> and <FIG>, in one exemplary embodiment of a UE that is configured with a CORESET, the device <NUM> includes a program code <NUM> stored in the memory <NUM>. The CPU <NUM> could execute program code <NUM> to enable the UE (i) to receive a DCI on the CORESET, wherein an index is included in the DCI and the index indicates a time domain resource allocation pattern, and (ii) to receive data in OFDM symbols determined according to the time domain resource allocation pattern, wherein a range of the time domain resource allocation pattern starts from the first OFDM symbol of the CORESET or after an offset from the first OFDM symbol of the CORESET. Furthermore, the CPU <NUM> can execute the program code <NUM> to perform all of the above-described actions and steps or others described herein.

<FIG> is a flow chart <NUM> according to one exemplary embodiment from the perspective of a network node. In step <NUM>, the network node configures a UE with a CORESET. In step <NUM>, the network node transmits a DCI on the CORESET to the UE, wherein an index is included in the DCI and the index indicates a time domain resource allocation pattern. In step <NUM>, the network node transmits data to the UE in OFDM symbols determined according to the time domain resource allocation pattern, wherein a range of the time domain resource allocation pattern starts from the first OFDM symbol of the CORESET or after an offset from the first OFDM symbol of the CORESET.

Referring back to <FIG> and <FIG>, in one exemplary embodiment of a network node, the device <NUM> includes a program code <NUM> stored in the memory <NUM>. The CPU <NUM> could execute program code <NUM> to enable the network node (i) to configure a UE with a CORESET, (ii) to transmit a DCI on the CORESET to the UE, wherein an index is included in the DCI and the index indicates a time domain resource allocation pattern, and (iii) to transmit data to the UE in OFDM symbols determined according to the time domain resource allocation pattern, wherein a range of the time domain resource allocation pattern starts from the first OFDM symbol of the CORESET or after an offset from the first OFDM symbol of the CORESET. Furthermore, the CPU <NUM> can execute the program code <NUM> to perform all of the above-described actions and steps or others described herein.

In the context of the embodiments illustrated in <FIG> and <NUM> and described above, preferably, the offset could be a number of OFDM symbol(s), wherein the number is derived by the UE according to information received from a network node, configured by the network node, or specified in the standards. The index could point to an entry of a UE-specific table which is configured by a NW. The index with the offset could point to an entry of the UE-specific table. The UE-specific table could include a subset of possible time domain duration of a slot, or possible time domain duration of a slot or multiple slots.

Preferably, each entry of the UE-specific table could comprise a time domain resource allocation pattern of a slot or multiple slots. A Resource Indication Value (RIV) could represent a time domain resource allocation pattern. The time domain resource allocation in each entry of the UE-specific table could be contiguous. A slot could comprise <NUM> OFDM symbols.

Preferably, if the CORESET starts at symbol index <NUM> of a slot, the offset value could be <NUM>. The offset value could be a starting OFDM symbol index of the CORESET.

Preferably, the offset value could be a sum of number of RIVs starting from OFDM symbol index(s) smaller than the starting OFDM symbol index of the CORESET. A RIV of time domain resource allocation pattern of the entry indicated by the index could add the offset. A RIV of the time domain resource allocation pattern could be subjected to a modulo operation with a number (in other words mod a number) and add the offset, wherein the number is number of sum of RIVs representing time domain resource allocation from starting OFDM symbol index of the CORESET to last OFDM symbol index of slot with different contiguous duration.

Preferably, the offset value could be added for the mapping RIV of each entry of the UE-specific table into RIV which represents a time domain resource allocation pattern starting at the starting OFDM symbol index of the CORESET. Alternatively the offset value could be added for the mapping time domain resource allocation pattern of each entry of the UE-specific table into starting at the starting OFDM symbol index of the CORESET.

Preferably, if a starting OFDM symbol index of time domain resource allocation pattern of the entry indicated by the index is smaller than the starting OFDM symbol index of the CORESET, a RIV of the time domain resource allocation pattern could be subjected to a modulo operation with a number (in other words mod a number) and add the offset, wherein the number is number of sum of RIVs representing time domain resource allocation from starting OFDM symbol index of the CORESET to last OFDM symbol index of slot with different contiguous duration. Alternatively, if a starting OFDM symbol index of the entry indicated by the index is larger than or equal to the starting OFDM symbol index of the CORESET, a RIV of the time domain resource allocation pattern could be subjected to a modulo operation with a number (in other words mod a number) and add the offset, wherein the number is number of sum of RIVs representing time domain resource allocation from starting OFDM symbol index of the CORESET to last OFDM symbol index of slot with different contiguous duration.

Preferably, a binary field in the DCI could indicate the index, wherein the size of the binary field represents a subset of the UE-specific table. If the size of the binary field in the DCI for the index can represent all RIVs from starting OFDM symbol index of the CORESET to slot boundary, the offset could be zero. However, if the size of the binary field in the DCI for the index can represent all RIV from starting OFDM symbol index of the CORESET to last OFDM symbol index of slot, the index could point to an entry of a default table, where each entry indicate a time domain resource allocation pattern starting at starting OFDM symbol index of the CORESET. The default table could be different from the UE-specific table.

Various aspects of the disclosure have been described above. It should be apparent that the teachings herein may be embodied in a wide variety of forms and that any specific structure, function, or both being disclosed herein is merely representative. Based on the teachings herein one skilled in the art should appreciate that an aspect disclosed herein may be implemented independently of any other aspects and that two or more of these aspects may be combined in various ways. As an example of some of the above concepts, in some aspects concurrent channels may be established based on pulse repetition frequencies. In some aspects concurrent channels may be established based on pulse position or offsets. In some aspects concurrent channels may be established based on time hopping sequences. In some aspects concurrent channels may be established based on pulse repetition frequencies, pulse positions or offsets, and time hopping sequences.

Those of skill would further appreciate that the various illustrative logical blocks, modules, processors, means, circuits, and algorithm steps described in connection with the aspects disclosed herein may be implemented as electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two, which may be designed using source coding or some other technique), various forms of program or design code incorporating instructions (which may be referred to herein, for convenience, as "software" or a "software module"), or combinations of both.

It is understood that any specific order or hierarchy of steps in any disclosed process is an example of a sample approach. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the processes may be rearranged while remaining within the scope of the present disclosure. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

The steps of a method or algorithm described in connection with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module (e.g., including executable instructions and related data) and other data may reside in a data memory such as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of computer-readable storage medium known in the art. A sample storage medium may be coupled to a machine such as, for example, a computer/processor (which may be referred to herein, for convenience, as a "processor") such the processor can read information (e.g., code) from and write information to the storage medium. A sample storage medium may be integral to the processor. The ASIC may reside in user equipment. In the alternative, the processor and the storage medium may reside as discrete components in user equipment. Moreover, in some aspects any suitable computer-program product may comprise a computer-readable medium comprising codes relating to one or more of the aspects of the disclosure. In some aspects a computer program product may comprise packaging materials.

Claim 1:
A method for a User Equipment (<NUM>), in the following also referred to as UE, comprising:
the UE (<NUM>) is configured with a control resource set, in the following also referred to as CORESET;
the UE (<NUM>) is configured with a first UE-specific table with time domain resource allocation patterns for slot based scheduling and a second UE-specific table with time domain resource allocation patterns for mini-slot based scheduling;
the UE (<NUM>) receives a Downlink Control Information, in the following also referred to as DCI, on the CORESET in a middle of a slot, wherein DCI formats for both slot based scheduling and mini-slot based scheduling are different and the UE (<NUM>) determines which table of the first UE-specific table and the second UE-specific table to use based on the received DCI format, and wherein the DCI includes an index pointing to an entry in a UE-specific table determined by the UE; and
the UE (<NUM>) receives data in Orthogonal Frequency Division Multiplexing, in the following also referred to as OFDM, symbols according to the time domain resource allocation pattern of the entry in the UE-specific table.