Method and device for configuring time domain resource allocation

Abstract

Method, system, and device for configuring time domain resource allocation (TDRA) of a physical uplink shared channel (PUSCH) for a user equipment. The method includes receiving, by the user equipment, a radio resource control (RRC) that configures a TDRA type corresponding to a TDRA table. Another method includes transmitting, by a network base station, an RRC that configures a TDRA type corresponding to a TDRA table for the user equipment.

Description

Technical Field

[0001] The present disclosure generally relates to wireless communication. In particular, the present disclosure relates to methods and apparatuses for configuring time domain resource allocation (TDRA). Background Art

[0002] Wireless communication technologies are driving the world towards an increasingly interconnected and networked society. High-speed and low-latency wireless communication relies on efficient network resource management and allocation between user equipment and wireless access network nodes (including but not limited to wireless base stations). The new generation of networks is expected to provide high-speed, low-latency, and ultra-reliable communication capabilities and meet the needs from different industries and users. Ultra-reliable low-latency communication (URLLC) can provide fast response with low-latency communication between user equipment and wireless access network nodes. URLLC can be supported on authorized frequency carriers. There are some problems in configuring time domain resource allocation (TDRA) associated with URLLC on authorized and / or unauthorized frequency carriers. The present disclosure can solve at least some of the problems associated with existing systems to improve the performance of wireless communication. Summary of the Invention

[0003] This application relates to methods, systems, and apparatuses for wireless communication, and more particularly, to methods, systems, and apparatuses for configuring time domain resource allocation (TDRA).

[0004] In one embodiment, the present disclosure describes a method for wireless communication. The method includes: receiving, by a user equipment, radio resource control (RRC). The RRC configures a time domain resource allocation (TDRA) type corresponding to a TDRA table of a channel.

[0005] In another embodiment, the present disclosure describes a method for wireless communication. The method includes: transmitting, by a network base station, radio resource control (RRC). The RRC configures a time domain resource allocation (TDRA) type corresponding to a TDRA table of a channel.

[0006] In some other embodiments, an apparatus for wireless communication may include a memory storing instructions and a processing circuit communicating with the memory. When the processing circuit executes the instructions, the processing circuit is configured to perform the above method.

[0007] In some other embodiments, a device for wireless communication may include a memory storing instructions and a processing circuit communicating with the memory. When the processing circuit executes the instructions, the processing circuit is configured to perform the above method.

[0008] In some other embodiments, a computer-readable medium comprising instructions that, when executed by a computer, cause the computer to perform the above method.

[0009] The above and other aspects and their implementations are described in more detail in the drawings, the description, and the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 An example of a wireless communication system including a wireless network node and one or more user equipments is shown.

[0011] Figure 2 An example of a network node is shown.

[0012] Figure 3 An example of a user equipment is shown.

[0013] Figure 4A A flowchart of a method for wireless communication is shown.

[0014] Figure 4B Shown for Figure 4A an optional step of the method in

[0015] Figure 5 An exemplary embodiment of a time domain resource allocation (TDRA) table is shown.

[0016] Figure 6 Another exemplary embodiment of a TDRA table is shown.

[0017] Figure 7 Another exemplary embodiment of a TDRA table is shown.

[0018] Figure 8 Another exemplary embodiment of a TDRA table is shown.

[0019] Figure 9 Another exemplary embodiment of a TDRA table is shown.

[0020] Figure 10 Another exemplary embodiment of a TDRA table is shown. DETAILED DESCRIPTION

[0021] The present disclosure will now be described in detail below with reference to the drawings, which form a part of the present disclosure and illustrate specific examples of embodiments by way of illustration. However, note that the present disclosure may be embodied in various different forms, and thus, the subject matter covered or claimed is intended to be construed as not limited to any of the embodiments set forth below.

[0022] Throughout the specification and claims, terms may have nuanced meanings that are suggested or implied in context in addition to the explicitly stated meanings. Similarly, as used herein, the phrase "in one embodiment" or "in some embodiments" does not necessarily refer to the same embodiment, and the phrase "in another embodiment" or "in other embodiments" does not necessarily refer to different embodiments. As used herein, the phrase "in one implementation" or "in some implementations" does not necessarily refer to the same implementation, and the phrase "in another implementation" or "in other implementations" does not necessarily refer to different implementations. For example, the claimed subject matter is intended to include, in whole or in part, combinations of exemplary embodiments or implementations.

[0023] Generally speaking, terms can be understood, at least in part, from their usage in context. For example, terms such as "and", "or", or "and / or" as used herein can include a variety of meanings, which can depend, at least in part, on the context in which they are used. Generally, "or" when used to relate a list (such as A, B, or C) is intended to mean A, B, and C (used in an inclusive sense here), as well as A, B, or C (used in an exclusive sense here). Additionally, the term "one or more" or "at least one" as used herein (at least in part depending on the context) can be used to describe any feature, structure, or property in a singular sense, or can be used to describe a combination of features, structures, or properties in a plural sense. Similarly, terms such as "a", "an", or "the" can also be understood to convey singular usage or convey plural usage, at least in part depending on the context. Further, the term "based on" or "determined by" can be understood to not necessarily convey an exclusive set of factors, and can alternatively allow for the presence of additional factors that are not necessarily explicitly described, which also depends, at least in part, on the context.

[0024] The present disclosure describes methods and devices for configuring time domain resource allocation (TDRA).

[0025] The new generation (NG) mobile communication system is pushing the world towards an increasingly interconnected and networked society. High-speed and low-latency wireless communication relies on efficient network resource management and allocation between user equipment and wireless access network nodes (including but not limited to wireless base stations). The new generation network is expected to provide high-speed, low-latency, and ultra-reliable communication capabilities and meet the needs of different industries and users. Ultra-reliable low-latency communication (URLLC) can provide fast response with low-latency communication between user equipment and wireless access network nodes. To increase bandwidth, reduce latency, and / or increase speed, wireless communication can be carried out on licensed bands and / or new wireless unlicensed (NR-U) bands.

[0026] In the fifth generation (5G) communication system, the URLLC dynamic grant (DG) physical uplink shared channel (PUSCH) may have a different transmission scheme from the NR-U DG PUSCH. In the URLLC DG PUSCH, a single transport block (TB) may be repeated a plurality of repetition times; and the number of repetition times (which may also be described as the repetition count) may be dynamically indicated. The TDRA of the URLLC DG PUSCH may be configured to include a parameter indicating the repetition count. The NR-U DG PUSCH may support data transmission over one or more transmission time intervals (TTIs), and each TTI is used to transmit a different TB. The TDRA of the NR-U DG PUSCH may be configured to include one or more start and length indicator values (SLIVs).

[0027] The present disclosure describes methods and apparatuses for configuring time domain resource allocation (TDRA) to transmit DG PUSCH when URLLC operates in an unlicensed frequency band. The present disclosure may provide methods such that the configuration for transmitting DG PUSCH has high flexibility and supports dynamic configuration of repetitions, multiple scheduling gaps, and / or combinations thereof. The present disclosure solves at least some of the problems associated with URLLC operating on an unlicensed frequency band in order to improve reliability, increase transmission opportunities, and enhance scheduling flexibility for URLLC transmissions using the unlicensed frequency band.

[0028] Figure 1 A wireless communication system 100 including a wireless network node 118 and one or more user equipments (UEs) 110 is shown. The wireless network node may include a network base station, which may be a nodeB (e.g., gNB) in a mobile telecommunications environment. Each of the UEs may wirelessly communicate with the wireless network node via one or more wireless channels 115. For example, the first UE 110 may wirelessly communicate with the wireless network node 118 via a channel including a plurality of wireless channels during a specific time period. The network base station 118 may send radio resource control (RRC) to the user equipment 110 such that the RRC may include information for configuring the TDRA type corresponding to the TDRA table.

[0029] Figure 2An example of an electronic device 200 for implementing a network base station is shown. The example electronic device 200 may include a wireless transmit / receive (Tx / Rx) circuit 208 to transmit / receive communications with a UE and / or other base stations. The electronic device 200 may also include a network interface circuit 209 to enable the base station to communicate with other base stations and / or a core network (e.g., optical or wired interconnects, Ethernet, and / or other data transmission media / protocols). The electronic device 200 may optionally include an input / output (I / O) interface 206 to communicate with an operator, etc.

[0030] The electronic device 200 may also include a system circuit 204. The system circuit 204 may include one or more processors 221 and / or a memory 222. The memory 222 may include an operating system 224, instructions 226, and parameters 228. The instructions 226 may be configured for one or more of the processors 124 to perform functions of a network node. The parameters 228 may include parameters that support the execution of the instructions 226. For example, the parameters may include network protocol settings, bandwidth parameters, radio frequency mapping assignments, and / or other parameters.

[0031] Figure 3An example of an electronic device for implementing a terminal device 300 (e.g., a user equipment (UE)) is shown. The UE 300 may be a mobile device, e.g., a smart phone or a mobile communication module installed in a vehicle. The UE 300 may include a communication interface 302, a system circuit 304, an input / output interface (I / O) 306, a display circuit 308, and a storage device 309. The display circuit may include a user interface 310. The system circuit 304 may include any combination of hardware, software, firmware, or other logic / circuits. The system circuit 304 may be implemented, for example, using one or more system-on-chips (SoCs), application-specific integrated circuits (ASICs), discrete analog and digital circuits, and other circuits. The system circuit 304 may be part of the implementation of any desired function in the UE 300. In this regard, the system circuit 304 may include, for example, logic for facilitating the following operations: decoding and playing music and videos (e.g., MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV decoding and playback); running applications; accepting user input; saving and retrieving application data; establishing, maintaining, and terminating cellular phone calls or data connections (as an example, for an Internet connection); establishing, maintaining, and terminating wireless network connections, Bluetooth connections, or other connections; and displaying relevant information on the user interface 310. The user interface 310 and the input / output (I / O) interface 306 may include a graphical user interface, a touch-sensitive display, haptic feedback, or other haptic output, voice or facial recognition input, buttons, switches, speakers, and other user interface elements. Other examples of the I / O interface 306 may include a microphone, video and still image cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headphone and microphone input / output jacks, universal serial bus (USB) connectors, memory card slots, radiation sensors (e.g., IR sensors), and other types of inputs.

[0032] Reference Figure 3, the communication interface 302 may include radio frequency (RF) transmit (Tx) and receive (Rx) circuitry 316 that processes the transmission and reception of signals via one or more antennas 314. The communication interface 302 may include one or more transceivers. The transceiver may be a wireless transceiver that includes modulation / demodulation circuitry, a digital to analog converter (DAC), a shaping table, an analog to digital converter (ADC), filters, a waveform shaper, filters, a preamplifier, a power amplifier, and / or other logic for transmitting and receiving via one or more antennas or (for some devices) via a physical (e.g., wired) medium. The signals transmitted and received may conform to any of a variety of formats, protocols, modulations (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM), frequency channels, bit rates, and codings. As a specific example, the communication interface 302 may include transceivers that support transmission and reception under 2G, 3G, BT, WiFi, Universal Mobile Telecommunications System (UMTS), High-Speed Packet Access (HSPA)+, 4G / Long Term Evolution (LTE), and 5G standards. However, the techniques described below are applicable to other wireless communication technologies, regardless of whether the other wireless communication technology is from the Third Generation Partnership Project (3GPP), GSM Association, 3GPP2, IEEE, or other partners or standards bodies.

[0033] Reference Figure 3 , the system circuitry 304 may include one or more processors 321 and a memory 322. The memory 322 stores, for example, an operating system 324, instructions 326, and parameters 328. The processor 321 is configured to execute the instructions 326 for performing the desired functions of the UE 300. The parameters 328 may provide and specify configuration and operation options for the instructions 326. The memory 322 may also store any BT, WiFi, 3G, 4G, 5G, or other data that the UE 300 will transmit or has received via the communication interface 302. In various embodiments, the system power of the UE 300 may be provided by a power storage device such as a battery or a transformer.

[0034] This disclosure describes several embodiments that may be implemented, in part or in whole, on the aforementioned network base stations and / or user equipment.

[0035] Refer to Figure 4A, this disclosure describes embodiments of method 400 for configuring time-domain resource allocation (TDRA) for a physical uplink shared channel (PUSCH) in a user equipment. Method 400 may include step 410: receiving, by the user equipment, a radio resource control (RRC), where the RRC configures a TDRA type corresponding to a TDRA table. The RRC may be sent by a network base station (e.g., gNB) to the user equipment. There may be a set of TDRA types, and each TDRA type may be configured based on a corresponding TDRA table.

[0036] In some embodiments, the set of TDRA types may be set X, and set X may include {Type I RRC, Type II RRC, Type III RRC}. The TDRA table may correspond to each type in set X. In one implementation, Type I RRC may refer to the URLLC mode, and the corresponding TDRA table includes a column of repetition times; Type II RRC may refer to the new radio-unlicensed (NR-U) mode, and the corresponding TDRA table includes one or more pairs of start and length indicators; while Type III RRC may refer to the NR legacy mode.

[0037] Refer to Figure 5 , the TDRA table 500 may be configured according to Type I RRC. In one implementation, the RRC received by the user equipment may include the format of PUSCH-TimeDomainResourceAllocationList-ForDCIformat0_2. In another implementation, the RRC received by the user equipment may include the format of PUSCH-TimeDomainResourceAllocationList-ForDCIformat0_1.

[0038] The TDRA table 500 may include multiple entries 510. The number of entries 510 in the TDRA table 500 is up to 64. For example, when the TDRA index is represented by a 4-bit value, the number of entries may be 16; while when the TDRA index is represented by a 6-bit value, the number of entries may be 64.

[0039] The TDRA table 500 may include multiple columns, which include a TDRA index 550, K2 552, a pair of start and length values (S, L) 554, a mapping type 556, and a repetition number 558.

[0040] The TDRA index 550 can indicate the index of each entry in the TDRA table 500, and the TDRA index can include a range starting from 0 and ending at (N - 1), where N is the number of entries in the TDRA table 500. Optionally, in one implementation, the TDRA index can be specified by the network base station. Refer to Figure 4B , method 400 may further include step 420: receiving, by the user equipment, downlink control information (DCI) from the network base station. The DCI may include an index corresponding to the entry index in the TDRA table. Method 400 may further include step 430: configuring, by the user equipment, the TDRA of the PUSCH based on the entry in the TDRA table.

[0041] K2 552 can be the time slot or sub - time slot number configured for the physical uplink shared channel (PUSCH) after the corresponding uplink (UL) grant, and this time slot or sub - time slot number indicates the scheduling timing between the UL grant and the PUSCH.

[0042] The pair of start and length values (S, L) 554 can indicate the start symbol (S) and the length (L) of the symbols in the time slot indicated by K2 552 of the transport block (TB). In another implementation, column 554 may include a pair of start and length indicators respectively including an S indicator and an L indicator.

[0043] The mapping type 556 only includes mapping type B.

[0044] The repetition number 558 can indicate the number of times of repeating the TB specified by the pair of start and length values in 554. For example, for the entry 512 with a TDRA index of 1, the TDRA may include repeating the TB on symbols 0 - 1, 2 - 3, 3 - 4, and 4 - 5 in the first time slot after the corresponding UL grant with mapping type B.

[0045] Refer to Figure 6 , the TDRA table can be configured according to type II RRC to support one or more TTIs. In one implementation, the RRC received by the user equipment may include the format of PUSCH - TimeDomainAllocationList - r16.

[0046] The TDRA table 600 can include multiple entries 610. The number of entries 610 in the TDRA table 600 is up to 16. For example, when the TDRA index is represented by a 2 - bit value, the number of entries can be 4; while when the TDRA index is represented by a 4 - bit value, the number of entries can be 16.

[0047] The TDRA table 600 may include multiple columns, which include a TDRA index 650, K2 652, at least one pair of start and length values (S, L) 654, and at least one mapping type 656. The mapping type in 656 may include mapping type A and / or mapping type B. In one implementation, the number of pairings of at least one pair of start and length values is equal to the number of at least one mapping type.

[0048] The TDRA index 650 may indicate the index of an entry in the TDRA table 600, and the TDRA index may include a range starting from 0 to (N - 1), where N is the number of entries in the TDRA table 600. Optionally, in one implementation, the TDRA index may be specified in the DCI sent from a network base station, and the TDRA of the PUSCH is configured based on the specified entry in the TDRA table, as Figure 4B shown. For example, for the entry 612 with a TDRA index of 1, the TDRA may include TB1 on symbols 7 to 13 of the first time slot after the corresponding UL grant with mapping type B, TB2 on symbols 0 to 6 of the second time slot after the corresponding UL grant with mapping type A, TB3 on symbols 7 to 13 of the second time slot after the corresponding UL grant with mapping type B, and TB4 on symbols 0 to 6 of the third time slot after the corresponding UL grant with mapping type A. TB1, TB2, TB3, and TB4 may be different TBs. For another example, for the entry 614 with a TDRA index of 3, the TDRA may include a TB on symbols 0 to 13 of the first time slot after the corresponding UL grant with mapping type A.

[0049] Refer to Figure 7 , the TDRA table 700 may be configured according to type III RRC. In one implementation, the RRC received by the user equipment may include the format of PUSCH - TimeDomainAllocationList. In another implementation, the PUSCH transmission mode according to type III RRC may indicate the new radio (NR) legacy mode.

[0050] The TDRA table 700 may include multiple entries 710. The number of entries 710 in the TDRA table 700 is up to 16. For example, when the TDRA index is represented by a 2 - bit value, the number of entries may be 4; while when the TDRA index is represented by a 4 - bit value, the number of entries may be 16.

[0051] The TDRA table 700 may include multiple columns, which include a TDRA index 750, K2 752, a pair of start and length values 754, and a mapping type 756. The mapping type in 756 may include mapping type A or mapping type B.

[0052] The TDRA index 750 may indicate the index of an entry in the TDRA table 700, and the TDRA index may include a range starting from 0 to (N - 1), where N is the number of entries in the TDRA table 700. Optionally, in one implementation, the TDRA index may be specified in the DCI sent from the network base station, and the TDRA of the PUSCH is configured based on the specified entry in the TDRA table, as Figure 4B shown. For example, for the entry 712 with a TDRA index of 1, the TDRA may include the TB on symbols 0 to 6 of the first time slot after the corresponding UL grant with mapping type A. For another example, for the entry 714 with a TDRA index of 3, the TDRA may include the TB on symbols 7 to 13 of the first time slot after the corresponding UL grant with mapping type B.

[0053] Refer to Figure 8 , the TDRA table 800 may be configured according to type IV RRC. The TDRA table 800 may include multiple entries 810. The number of entries 810 in the TDRA table 800 is up to 16 or 64. For example, when the TDRA index is represented by a 2-bit value, the number of entries may be 4; while when the TDRA index is represented by a 6-bit value, the number of entries may be 64.

[0054] The TDRA table 800 may include multiple columns, which include a TDRA index 850, K2 852, at least a pair of start and length (S, L) values or SLIV 854, at least one mapping type 856, and a repetition number 858. The mapping type in 856 may include mapping type A and / or mapping type B.

[0055] In the TDRA table 800, for any entry including a repetition number greater than 1, the entry may include a pair of start and length values and a mapping type. For example, for the entry 814 with a repetition number of 4, the entry 814 includes a pair of (S, L) values and a mapping type B. For another example, for the entry 815 with a repetition number of 8, the entry 815 includes a pair of (S, L) values and a mapping type B.

[0056] In TDRA table 800, for any entry including a repetition count equal to 1, the entry can include one or more pairs of start and length values and one or more mapping types; and the number of pairings of start and length values can be equal to the number of mapping types. For example, for entry 811 with a repetition count of 1, entry 811 includes four pairs of (S, L) values and four mapping types including {A, A, A, A}. For another example, for entry 813 with a repetition count of 1, entry 813 includes one pair of (S, L) values and one mapping type B.

[0057] The TDRA index 850 can indicate the index of an entry in TDRA table 800, and the TDRA index can include a range starting from 0 to (N - 1) ending, where N is the number of entries in TDRA table 800. Optionally, in one implementation, the TDRA index can be specified in DCI sent from a network base station, and the TDRA of PUSCH is configured based on the specified entry in the TDRA table, as Figure 4B shown. For example, for entry 812 with a TDRA index of 1 and a repetition count of 1, the TDRA can include TB1 on symbols 7 to 13 of the first time slot after the corresponding UL grant with mapping type B, TB2 on symbols 0 to 6 of the second time slot after the corresponding UL grant with mapping type A, TB3 on symbols 7 to 13 of the second time slot after the corresponding UL grant with mapping type B, and TB4 on symbols 0 to 6 of the third time slot after the corresponding UL grant with mapping type A.

[0058] Optionally, in one implementation, the RRC received by the user equipment can be one of set X, and set X can include {Type I RRC, Type II RRC, Type III RRC}. When Type I RRC includes PUSCH-TimeDomainResourceAllocationList-ForDCIformat0_2, the PUSCH transmission mode can be the URLLC mode, which has a repetition count in the configured TDRA. When Type II RRC includes pusch-TimeDomainAllocationList-r16, the PUSCH transmission mode can be the NR-U mode with multiple TTIs. When Type III RRC includes pusch-TimeDomainAllocationList, the PUSCH transmission mode can be the traditional NR mode, which may not support dynamic repetition or multiple TTIs.

[0059] Reference Figure 9, TDRA Table 900 can be configured according to Type V RRC. TDRA Table 900 can include multiple entries 910. The number of entries 910 in TDRA Table 800 can be up to 16 or 64. For example, when the TDRA index is represented by a 2-bit value, the number of entries can be 4; while when the TDRA index is represented by a 6-bit value, the number of entries can be 64.

[0060] TDRA Table 900 can include multiple columns, which include TDRA index 950, K2 952, at least one pair of start and length (S, L) values or SLIV 954, at least one mapping type 956, and number of repetitions 858. The mapping type in 856 can include one or more mapping types A and / or one or more mapping types B.

[0061] In TDRA Table 900, for any entry that includes a number of repetitions equal to 1, the entry can include one or more pairs of start and length values and one or more mapping types; and the number of pairings of start and length values can be equal to the number of mapping types. For example, for entry 911 with a number of repetitions of 1, entry 911 includes one pair of (S, L) values and one mapping type. For example, for entry 912 with a number of repetitions of 1, entry 813 includes four pairs of (S, L) values and four mapping types including {B, A, B, A}.

[0062] In TDRA Table 900, for any entry that includes a number of repetitions greater than 1, the entry can include one or more pairs of start and length values and one or more mapping types. In one implementation, the number of pairings of start and length values can be equal to the number of mapping types. For example, for entry 913 with a number of repetitions of 4, entry 913 includes one pair of (S, L) values and one mapping type B. In one implementation, the number of pairings of start and length values can not be equal to the number of mapping types. For example, for entry 914 with a number of repetitions of 2, entry 914 includes four pairs of (S, L) values and two mapping types including {B, B}.

[0063] TDRA index 950 can indicate the index of an entry in TDRA Table 900, and the TDRA index can include a range starting from 0 to ending at (N - 1), where N is the number of entries in TDRA Table 900. Optionally, in one implementation, the TDRA index can be specified in the DCI sent from the network base station, and the TDRA of PUSCH is configured based on the specified entry in the TDRA table, as Figure 4B shown.

[0064] In one embodiment, for a specified entry, the number of pairs of at least one start and length value is greater than one, and the TDRA of PUSCH can be configured in a hybrid mode based on the entry in the TDRA table.

[0065] In another embodiment, the number of pairs of at least one start and length value is equal to the number of at least one mapping type; and the repetition number is the number of the repetition times of each pair of start and length values of the transport block having the corresponding mapping type. For example, for entry 912 with a TDRA index of 1 and a repetition number of 1, the TDRA may include TB1 on symbols 7 to 13 of the first time slot after the corresponding UL grant with mapping type B, TB2 on symbols 0 to 6 of the second time slot after the corresponding UL grant with mapping type A, TB3 on symbols 7 to 13 of the second time slot after the corresponding UL grant with mapping type B, and TB4 on symbols 0 to 6 of the third time slot after the corresponding UL grant with mapping type A.

[0066] In another embodiment, the number of pairs of at least one start and length value is not equal to the number of at least one mapping type; and the number of transport blocks having all corresponding mapping types at the repetition number is equal to the number of corresponding start and length value pairs. The repetition of the transport block may include the following configurations. For example, when there are three transport blocks (TB1, TB2, and TB3) and the repetition number is 2, the first repetition configuration may be to transmit TB1, TB2, and TB3 once, and then the same transmission sequence for the second repetition; the second repetition configuration may include transmitting TB1 continuously twice, then transmitting TB2 continuously twice, and finally transmitting TB3 continuously twice. In one embodiment, the RRC may include an indicator specifying which configuration to use. In another embodiment, the DCI may include an indicator specifying which configuration to use.

[0067] In the case of using the first repetition configuration, for example, for entry 914 with a TDRA index of 3 and a repetition number of 2, the TDRA may include TB1 from 7 to 13 of the first time slot after the corresponding UL grant with mapping type B, TB2 from 0 to 6 of the second time slot after the corresponding UL grant with mapping type B, TB1 from 7 to 13 of the second time slot after the corresponding UL grant with mapping type B, and TB2 from 0 to 6 of the third time slot after the corresponding UL grant with mapping type B.

[0068] In the case of using the second repetition configuration, for example, for entry 914 with a TDRA index of 3 and a repetition number of 2, the TDRA may include TB2 from 7 to 13 of the first time slot after the corresponding UL grant with mapping type B, TB1 from 0 to 6 of the second time slot after the corresponding UL grant with mapping type B, TB1 from 7 to 13 of the second time slot after the corresponding UL grant with mapping type B, and TB2 from 0 to 6 of the third time slot after the corresponding UL grant with mapping type B.

[0069] In another embodiment, for example, for entry 915 with a TDRA index of 4, the repetition number of entry 915 is greater than 1, and the number of pairs of start and length values of entry 915 is equal to the number of mapping types. Therefore, for entry 915, four transport blocks (TB1, TB2, TB3, and TB4) with a repetition number of 2 can be transmitted in at least two different configurations. In the first configuration, the transmission sequence can be TB1 - TB2 - TB3 - TB4, followed by TB1 - TB2 - TB3 - TB4. In the second configuration, the transmission sequence can be TB1 - TB1 - TB2 - TB2 - TB3 - TB3 - TB4 - TB4.

[0070] Optionally, in one embodiment, the RRC received by the user equipment may be one of the set X, and the set X may include {Type I RRC, Type II RRC, Type III RRC}. When Type I RRC includes PUSCH - TimeDomainResourceAllocationList - ForDCIformat0_2, the PUSCH transmission mode may be the URLLC mode, which has a repetition number in the configured TDRA. When Type II RRC includes pusch - TimeDomainAllocationList - r16, the PUSCH transmission mode may be the NR - U mode with multiple TTIs. When Type III RRC includes pusch - TimeDomainAllocationList, the PUSCH transmission mode may be the traditional NR mode, which may not support dynamic repetition or multiple TTIs.

[0071] Optionally, a gap of at least one symbol may exist between at least two pairs of consecutive start and length values. Refer to Figure 6 and Figure 10, the TDRA table 600 can be modified to be configured as the TDRA table 1000. The TDRA table 1000 can include multiple entries 1010. The TDRA table 1000 can include multiple columns, and the multiple columns include a TDRA index 1050, K2 1052, at least a pair of start and length values (S, L) 1054, and at least one mapping type 1056. The mapping type in 1056 can include mapping type A and / or mapping type B.

[0072] For example, for the entry 1012 with a TDRA index of 1, the TDRA can include TB1 on symbols 7 to 12 of the first time slot after the corresponding UL grant with mapping type B, TB2 on symbols 0 to 5 of the second time slot after the corresponding UL grant with mapping type A, TB3 on symbols 7 to 12 of the second time slot after the corresponding UL grant with mapping type B, and TB4 on symbols 0 to 5 of the third time slot after the corresponding UL grant with mapping type A. For example, there is a gap of at least one symbol (i.e., symbol #6) between TB2 on symbols 0 to 5 of the second time slot and TB3 on symbols 7 to 12 of the second time slot after the corresponding UL grant.

[0073] This disclosure describes embodiments that can reduce the waiting latency time when using NR-U bands for URLLC transmissions under frame-based device (FBE) contention, and thus improve the efficiency and performance of URLLC transmissions.

[0074] In one implementation, the enhanced mobile broadband (eMBB) service and the URLLC service can configure different time periods for the FBE frame period, so as to provide more contention opportunities for the URLLC service to reduce the waiting latency time. Specifically, when the user equipment (UE) uses one of the eMBB service or the URLLC service, different time periods can be respectively configured as the FBE frame periods for the eMBB UE and the URLLC UE. When the UE uses both the eMBB service and the URLLC service simultaneously, different FBE frame periods can be configured for the eMBB UE and the URLLC UE, such that more than one FBE frame period can be configured for the UE.

[0075] In another embodiment, to avoid or reduce the waiting latency associated with URLLC services, the URLLC clear channel assessment (CCA) time window can be randomized so that the URLLC service can start competing for resources immediately upon reception. Specifically, an FBE contention mode can be configured for eMBB services, and a load-based device (LBE) contention mode can be configured for URLLC services. Optionally, the eMBB service can occupy discontinuous resources in the time domain so that the URLLC service can compete. After the gap, if the resources are idle, the eMBB service can continue transmission, or if the resources are busy, the transmission can be suspended. In another embodiment, the eMBB service can occupy discontinuous TTI transmissions, where a gap of at least one symbol can exist between at least two pairs of consecutive start and length values.

[0076] The present disclosure describes methods, apparatuses, and computer-readable media for wireless communication. The present disclosure solves the problem of time-domain resource allocation (TDRA) of the physical uplink shared channel (PUSCH) configured for a user equipment. The methods, apparatuses, and computer-readable media described in the present disclosure can facilitate the performance of URLLC transmissions between the user equipment and the base station, thereby improving efficiency and overall performance. The methods, apparatuses, and computer-readable media described in the present disclosure can improve the overall efficiency of a wireless communication system.

[0077] References throughout this specification to features, advantages, or similar language do not imply that all features and advantages that can be realized with the solution should or are included in any single embodiment of the solution. Instead, the language referring to the features and advantages is understood to mean that a particular feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the solution. Thus, the discussions of the features and advantages throughout this specification, and similar language, may, but do not necessarily, refer to the same embodiment.

[0078] In addition, in one or more embodiments, the features, advantages, and characteristics of the solution can be combined in any suitable manner. Given the description herein, those of ordinary skill in the relevant art will recognize that the solution can be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized that may not exist in all embodiments of the solution.

Claims

1. A method for wireless communication, comprising: receiving, by a user equipment, a Radio Resource Control (RRC), wherein a Time Domain Resource Allocation (TDRA) type configured by the RRC corresponds to a TDRA table of a channel, wherein: the TDRA type includes Type IV RRC, the TDRA table configured by the Type IV RRC includes a plurality of entries, each entry of the plurality of entries includes K2, at least one pair of start and length values, at least one mapping type, and a repetition number, for any entry including a repetition number greater than 1, the entry includes a unique pair of start and length values and one mapping type; and for any entry including a repetition number equal to 1, the entry includes at least one pair of start and length values, at least one mapping type, wherein a number of pairings of the at least one pair of start and length values is equal to a number of the at least one mapping type.

2. The method according to claim 1, wherein: the TDRA type includes one of a group of TDRA types, wherein the group of TDRA types includes Type I RRC, Type II RRC, and Type III RRC; the TDRA table configured by the Type I RRC includes a plurality of entries, wherein each entry of the plurality of entries includes K2, a pair of start and length values, a mapping type, and a repetition number; the TDRA table configured by the Type II RRC includes a plurality of entries, wherein each entry of the plurality of entries includes K2, at least one pair of start and length values, and at least one mapping type, wherein a number of pairings of the at least one pair of start and length values is equal to a number of the at least one mapping type; and the TDRA table configured by the Type III RRC includes a plurality of entries, wherein each entry of the plurality of entries includes K2, a pair of start and length values, and a mapping type.

3. The method according to claim 1, wherein: the channel includes a Physical Uplink Shared Channel (PUSCH); the TDRA type includes Type V RRC; the TDRA table configured by the Type V RRC includes a plurality of entries, wherein: each entry of the plurality of entries includes K2 and a repetition number, for any entry including a repetition number greater than 1, the entry includes at least one pair of start and length values and at least one mapping type.

4. The method according to claim 3, wherein: a number of pairings of the at least one pair of start and length values is greater than one; and based on an entry in the TDRA table, configuring the TDRA of the PUSCH in a hybrid mode.

5. The method according to claim 4, wherein: a number of pairings of the at least one pair of start and length values is equal to a number of the at least one mapping type; and the repetition number is a number of repetitions of each pair of start and length values of a transport block having a corresponding mapping type.

6. The method according to claim 4, wherein: a number of pairings of the at least one pair of start and length values is not equal to a number of the at least one mapping type; and The number of transport blocks having all corresponding mapping types multiplied by the repetition number is equal to the number of corresponding start and length value pairs.

7. The method according to any one of claims 2 to 6, wherein: There is a gap of at least one symbol between at least two consecutive pairs of start and length values.

8. A method for wireless communication, comprising: Sending, by a network base station, a radio resource control (RRC), the time domain resource allocation (TDRA) type configured by the RRC corresponding to a TDRA table of a channel, wherein: The TDRA type includes type IV RRC, The TDRA table configured by the type IV RRC includes a plurality of entries, and Each entry in the plurality of entries includes K2, at least one pair of start and length values, at least one mapping type, and a repetition number, For any entry including a repetition number greater than 1, the entry includes a unique pair of start and length values and a mapping type; and For any entry including a repetition number equal to 1, the entry includes at least one pair of start and length values, at least one mapping type, wherein the number of pairs of the at least one pair of start and length values is equal to the number of the at least one mapping type.

9. The method according to claim 8, wherein: The TDRA type includes one of a group of TDRA types, wherein the group of TDRA types includes type I RRC, type II RRC, and type III RRC; The TDRA table configured by the type I RRC includes a plurality of entries, wherein each entry in the plurality of entries includes K2, a pair of start and length values, a mapping type, and a repetition number; The TDRA table configured by the type II RRC includes a plurality of entries, wherein each entry in the plurality of entries includes K2, at least one pair of start and length values, and at least one mapping type, wherein the number of pairs of the at least one pair of start and length values is equal to the number of the at least one mapping type; and The TDRA table configured by the type III RRC includes a plurality of entries, wherein each entry in the plurality of entries includes K2, a pair of start and length values, and a mapping type.

10. The method according to claim 8, wherein: The channel includes a physical uplink shared channel (PUSCH); The TDRA type includes type V RRC; The TDRA table configured by the type V RRC includes a plurality of entries, wherein: Each entry in the plurality of entries includes K2 and a repetition number, For any entry including a repetition number greater than 1, the entry includes at least one pair of start and length values and at least one mapping type.

11. The method according to claim 10, wherein: The number of pairs of the at least one pair of start and length values is greater than one; and Based on the entries in the TDRA table, the TDRA of the PUSCH is configured in a hybrid mode.

12. The method according to claim 11, wherein: The number of pairs of the at least one pair of start and length values is equal to the number of the at least one mapping type; and The number of repetitions is the number of repetitions for each pair of start and length values of a transport block having a corresponding mapping type.

13. The method according to claim 11, wherein: The number of pairings of the at least one pair of start and length values is not equal to the number of the at least one mapping type; and The number of transport blocks having all corresponding mapping types multiplied by the number of repetitions is equal to the number of pairings of the corresponding start and length values.

14. The method according to any one of claims 9 to 13, wherein: There is a gap of at least one symbol between at least two consecutive pairs of start and length values.

15. A wireless communication device, the wireless communication device comprising a processor and a memory, wherein the processor is configured to read code from the memory and implement the method according to any one of claims 1 to 14.

16. A computer program product, the computer program product comprising computer-readable program medium code stored thereon, the code, when executed by a processor, causing the processor to implement the method according to any one of claims 1 to 14.

Images