time domain repetition of a set of transport blocks

Abstract

Apparatus, methods, and systems for indicating a repetition scheme for a set of transport blocks ("TBs") scheduled for a given period are disclosed. One apparatus (800) includes a receiver (835) that receives (1005) control signaling containing scheduling information for transmitting a set of transport blocks ("TBs") across multiple transport instances, and receives (1010) repetition information for time-domain repetition of the set of TBs scheduled for a given period. The apparatus (800) includes a processor (805) that determines (1015) whether time-domain repetition should be applied for each TB in the set of TBs based on time-domain resources allocated to each TB, and controls a transmitter (830) to transmit (1020) the set of TBs according to the scheduling information and the repetition information.

Description

[0001] Cross-references to related applications

[0002] This application claims priority to U.S. Provisional Patent Application No. 63 / 034,881, filed June 4, 2020, entitled “PUSCH SCHEDULING INNR-U URLLC OPERATION”, by Ankit Bhamri, Hyejung Jung, and Alexander Johann MariaGolitschek Edler von Elbwart, which is incorporated herein by reference. Technical Field

[0003] The topics disclosed herein generally relate to wireless communications, and more specifically to scheduling resources on shared channels, for example, for coverage enhancement and / or during ultra-reliable low-latency communications (“URLLC”) services and / or during operation on unlicensed (i.e., shared) radio spectrum. Background Technology

[0004] In some wireless communication systems, user equipment (“UE”) can be allocated uplink resources on a physical uplink shared channel. After performing a PUSCH transmission of a transport block (“TB”), the UE can receive feedback, such as Hybrid Automatic Repeat Request (“HARQ”) feedback. Here, a positive acknowledgment (i.e., “ACK”) indicates successful reception of the TB, while a negative acknowledgment (i.e., “NACK”) indicates that the TB was not successfully received by the network. Upon receiving a NACK, the UE can retransmit the TB. However, the delay associated with waiting for HARQ feedback and retransmitting the TB may be unacceptable for some low-latency services.

[0005] Additionally, in some networks, UE service can be supplemented by operation on unlicensed spectrum. However, operation on unlicensed spectrum requires an idle channel assessment (“CCA”) prior to transmission, involving, for example, a listen-before-talk (“LBT”) procedure. If the CCA / LBT procedure fails immediately before the scheduled transmission, the UE must wait until a later transmission opportunity to transmit the TB. However, the delay associated with waiting for the next transmission opportunity may be unacceptable for some low-latency services. Summary of the Invention

[0006] A process is disclosed for indicating a repetition scheme for a set of scheduled transport blocks (“TB”). The process can be implemented by an apparatus, system, method, or computer program product.

[0007] A method of a user equipment (“UE”) includes receiving control signaling containing scheduling information for transmitting a set of transport blocks (“TBs”) through multiple transport scenarios. A first method includes receiving time-domain repetition information for scheduling the set of TBs and determining, for each TB in the set of TBs, whether to apply the time-domain repetition based on the time-domain resources allocated to each TB. The first method also includes transmitting the set of TBs based on the scheduling information and the repetition information.

[0008] A method for a radio access network (“RAN”) node includes determining scheduling information for a set of TBs to be transmitted over multiple transmission occasions and determining repetition information for time-domain repetition of the set of TBs. A second method includes transmitting control signaling to a UE containing the scheduling information and the repetition information, and receiving a set of TBs from the UE based on the scheduling information and the repetition information, wherein time-domain repetition is applied to the set of TBs based on time-domain resources allocated for each TB. Attached Figure Description

[0009] A more specific description of the embodiments briefly described above will be presented with reference to specific embodiments illustrated in the accompanying drawings. It should be understood that these drawings depict only a few embodiments and should therefore not be considered as limiting the scope; the embodiments will be described and explained with additional specificity and detail using the drawings, in which:

[0010] Figure 1 This is a schematic block diagram illustrating one embodiment of a wireless communication system for indicating a repetition scheme of a set of TBs for scheduling.

[0011] Figure 2 This is a block diagram illustrating one embodiment of the 5G New Radio (“NR”) protocol stack;

[0012] Figure 3 This is a diagram illustrating an embodiment of temporal resource allocation with repeating type B;

[0013] Figure 4 This is a diagram illustrating an embodiment of temporal resource allocation with repetition type A;

[0014] Figure 5 This is a diagram illustrating another embodiment of temporal resource allocation with repeating type B;

[0015] Figure 6 This is a diagram illustrating another embodiment of temporal resource allocation with repetition type A;

[0016] Figure 7 This is a diagram illustrating one embodiment of time-domain resource allocation during NDI switching;

[0017] Figure 8This is a diagram illustrating one embodiment of a user equipment device that can be used to indicate a repetition scheme for a set of TBs in a scheduling process;

[0018] Figure 9 This is a diagram illustrating one embodiment of a network device that can be used to indicate a repetition scheme for a set of scheduled TBs;

[0019] Figure 10 This is a flowchart illustrating an embodiment of a first method for indicating a repetition scheme for a set of scheduled TBs; and

[0020] Figure 11 This is a flowchart illustrating an embodiment of a second method for indicating a repetition scheme for a set of scheduled TBs. Detailed Implementation

[0021] As those skilled in the art will understand, aspects of the embodiments can be embodied as a system, apparatus, method, or program product. Therefore, embodiments can take the form of a completely hardware embodiment, a completely software embodiment (including firmware, resident software, microcode, etc.), or an embodiment combining aspects of both software and hardware.

[0022] For example, the disclosed embodiments can be implemented as hardware circuitry that includes custom-designed very large-scale integration (“VLSI”) circuitry or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. The disclosed embodiments can also be implemented in programmable hardware devices such as field-programmable gate arrays, programmable array logic, programmable logic devices, etc. As another example, the disclosed embodiments may include one or more physical or logical blocks of executable code, which may, for example, be organized as objects, procedures, or functions.

[0023] Furthermore, embodiments may take the form of a program product embodied in one or more computer-readable storage devices that store machine-readable code, computer-readable code, and / or program code, hereinafter referred to as code. The storage device may be tangible, non-transitory, and / or non-transferable. The storage device may not embody signals. In one embodiment, the storage device employs only signals for accessing the code.

[0024] Any combination of one or more computer-readable media may be used. A computer-readable medium may be a computer-readable storage medium. A computer-readable storage medium may be a storage device for storing code. A storage device may be, for example, but not limited to, electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor systems, apparatuses, or devices, or any suitable combination thereof.

[0025] More specific examples of storage devices (a non-exhaustive list) will include the following: electrical connections having one or more cables, portable computer floppy disks, hard disks, random access memory (“RAM”), read-only memory (“ROM”), erasable programmable read-only memory (“EPROM” or flash memory), portable optical disc read-only memory (“CD-ROM”), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium can be any tangible medium capable of containing or storing a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0026] The code used to perform the operations of the embodiments can be any number of lines and can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Python, Ruby, Java, Smalltalk, and C++, and traditional procedural programming languages ​​such as the "C" programming language, and / or machine languages ​​such as assembly language. The code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer via any type of network, including a local area network ("LAN"), a wireless LAN ("WLAN"), or a wide area network ("WAN"), or can be connected to an external computer (e.g., via the Internet through an Internet service provider ("ISP").

[0027] Furthermore, the features, structures, or characteristics described in the embodiments can be combined in any suitable manner. Numerous specific details, such as examples of programming, software modules, user selection, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., are provided in the following description to provide a thorough understanding of the embodiments. However, those skilled in the art will recognize that the embodiments can be practiced without one or more of these specific details or using other methods, components, materials, etc. In other instances, well-known structures, materials, or operations have not been shown or described in detail to avoid obscuring aspects of the embodiments.

[0028] Throughout this specification, references to "an embodiment," "embodiment," or similar language mean that a particular feature, structure, or characteristic described in connection with that embodiment is included in at least one embodiment. Therefore, unless expressly stated otherwise, the phrases "in an embodiment," "in an embodiment," and similar language throughout this specification may, but do not necessarily, refer to the same embodiment, but rather mean "one or more, but not all, embodiments." Unless expressly stated otherwise, the terms "comprising," "including," "having," and variations thereof mean "including, but not limited to,". Unless expressly stated otherwise, the list of enumerated items does not imply that any or all items are mutually exclusive. Unless expressly stated otherwise, the terms "a," "an," and "the" also mean "one or more."

[0029] As used herein, a list containing the conjunction “and / or” includes any single item in the list or a combination of items in the list. For example, a list of A, B, and / or C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C, or a combination of A, B, and C. As used herein, a list using the term “one or more of…” includes any single item in the list or a combination of items in the list. For example, one or more of A, B, and C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C, or a combination of A, B, and C. As used herein, a list using the term “one of…” includes one and only one of any single item in the list. For example, “one of A, B, and C” includes only A, only B, or only C and excludes combinations of A, B, and C. As used herein, “selected from the group consisting of A, B, and C” includes one and only one of A, B, or C and excludes combinations of A, B, and C. As used in this article, “selecting members of a group consisting of A, B, and C and their combinations” includes only A, only B, only C, combinations of A and B, combinations of B and C, combinations of A and C, or combinations of A, B, and C.

[0030] The following description of various aspects of the embodiments is based on schematic flowcharts and / or schematic block diagrams of methods, apparatus, systems, and program products according to the embodiments. It will be understood that individual blocks in the schematic flowcharts and / or schematic block diagrams, as well as combinations of blocks in the schematic flowcharts and / or schematic block diagrams, can be implemented by code. This code can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that instructions executable via the processor of the computer or other programmable data processing apparatus create means for implementing the functions / actions specified in the flowcharts and / or block diagrams.

[0031] The code can also be stored in a storage device that can instruct a computer, other programmable data processing device or other device to operate in a particular manner, such that the instructions stored in the storage device produce an article of art including instructions that implement the functions / actions specified in the flowchart and / or block diagram.

[0032] The code may also be loaded onto a computer, other programmable data processing apparatus or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device, thereby producing a computer-implemented process, such that the code executing on the computer or other programmable apparatus provides a process for implementing the functions / actions specified in the flowchart and / or block diagram.

[0033] The flowcharts and / or block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of apparatus, systems, methods, and program products according to various embodiments. In this regard, each block in the flowcharts and / or block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions for implementing a specified logical function.

[0034] It should also be noted that in some alternative implementations, the functions marked in the boxes may not appear in the order shown in the figures. For example, depending on the functions involved, two boxes shown successively may actually be executed substantially simultaneously, or these boxes may sometimes be executed in reverse order. Other steps and methods that are equivalent in function, logic, or effect to one or more boxes or portions thereof shown in the figures can be contemplated.

[0035] While various arrow and line types may be used in flowcharts and / or block diagrams, they are not intended to limit the scope of the corresponding embodiments. In practice, some arrows or other connectors may be used only to indicate the logical flow of the depicted embodiment. For example, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of a depicted embodiment. It will also be noted that each block in a block diagram and / or flowchart, and combinations of blocks in block diagrams and / or flowcharts, can be implemented by a system based on dedicated hardware or a combination of dedicated hardware and code that performs the specified function or action.

[0036] The description of the elements in each figure can be referenced to the elements in the preceding figures. Throughout all figures, the same reference numerals refer to the same elements, including alternative embodiments of the same elements.

[0037] Generally, this disclosure describes systems, methods, and apparatus for indicating repetition schemes for sets of TBs used for scheduling. To enhance support for Industrial Internet of Things (“IIoT”) and Ultra-Reliable Low-Latency Communication (“URLLC”), this solution addresses scheduling compatibility issues based on Physical Uplink Shared Channel (“PUSCH”) scheduling enhanced by 3GPP Release 16 (“Rel-16”) for use in unlicensed spectrum (“NR-U”) and new radio (“NR”) operation in URLLC. This solution also supports coverage enhancements.

[0038] To enhance signaling efficiency, scheduling multiple PUSCH transmissions (referred to as "multiple PUSCH") via a single control signaling instance, such as via a single DCI, is supported. This allows multiple transport blocks to use a single scheduling license (e.g., DCI or CG) for PUSCH in a sequential manner, scheduled over multiple transmit time intervals ("TTIs") such as multiple time slots. In NR-based radio access technologies ("RAT"), a TTI (also known as a transmission occasion) can be a time slot or microslot of other symbol groups. In the following description, the terms "time slot" or "multiple time slots" are used for TTIs, but they can be replaced by any other group of time-domain resources, such as subframes, microslots, shortened TTIs, transmission occasions, etc.

[0039] Additionally, the PUSCH repetition scheme can be enhanced to allow low-latency repetition of the same transport block in a continuous manner for slot-based repetition (referred to as repetition type A) and / or intra-slot repetition (referred to as repetition type B), for example, using a single scheduling license (e.g., DCI or CG) for PUSCH. It should be noted that 3GPP Releases 16 and 17 (“Rel-16 / 17”) do not specify how these two features are compatible. Therefore, this disclosure relates to how time-domain resource allocation is handled when the UE is configured and instructed to have multiple PUSCH scheduling and PUSCH repetition to meet URLLC requirements in NR-U.

[0040] Additionally, versions 15 and 16 (“Rel-15 / 16”) do not support single TB transfers across multiple TTIs. Advantageously, the solutions described herein can also be applied to schedule single TBs across multiple PUSCH / TTIs to improve coverage and reduce latency.

[0041] To remedy the aforementioned issues, a new UE and / or RAN behavior has been proposed for time-domain resource allocation when the UE is configured and / or instructed to have multiple PUSCH scheduling and PUSCH duplication using a single control signaling instance. Currently, the two features, namely multiple PUSCH scheduling and PUSCH duplication, are specified separately, and the current specification does not support behavior regarding how to handle these two features together, especially in terms of time-domain resource allocation.

[0042] The new UE and / or RAN behaviors include handling multiplexing of different PUSCHs (different TBs) and their corresponding repetition schemes. The new behaviors may also include selectively repeating certain PUSCHs depending on the following conditions:

[0043] 1. NDI bits for each PUSCH and / or

[0044] 2. Priority level of each push

[0045] 3. Mapping type (A or B) and repeating type (A or B) for each PUSCH.

[0046] The new UE and / or RAN behaviors include schemes that schedule a single TB via multiple PUSCHs through a single instance of control signaling. Additionally, such schemes can schedule duplicates of a single TB using a single instance of control signaling.

[0047] The new UE / RAN behavior may also include priority indications for PUSCHs across multiple schedules.

[0048] Figure 1 A wireless communication system 100 for indicating a repetition scheme for a set of scheduled TBs is depicted according to embodiments of the present disclosure. In one embodiment, the wireless communication system 100 includes at least one remote unit 105, a radio access network (“RAN”) 120, and a mobile core network 140. The RAN 120 and the mobile core network 140 form a mobile communication network. The RAN 120 may consist of a base station unit 121, and the remote unit 105 communicates with the base station unit 121 using a wireless communication link 123. Although in Figure 1 The document depicts a specific number of remote units 105, base station units 121, wireless communication links 123, RAN 120, and mobile core network 140, but those skilled in the art will recognize that any number of remote units 105, base station units 121, wireless communication links 123, RAN 120, and mobile core network 140 can be included in the wireless communication system 100.

[0049] In one implementation, RAN 120 conforms to the 5G system specified in the 3GPP specification. For example, RAN 120 may be an NG-RAN that implements the NR RAT and / or the Long Term Evolution (“LTE”) RAT. In another example, RAN 120 may include a non-3GPP RAT (e.g., Or an IEEE 802.11 series compliant WLAN. In another embodiment, RAN 120 conforms to the LTE system specified in the 3GPP specification. However, more generally, the wireless communication system 100 can implement some other open or proprietary communication networks, such as Global Microwave Access Interoperability (“WiMAX”) or the IEEE 802.16 series standards, as well as other networks. This disclosure is not intended to limit implementation to any particular wireless communication system architecture or protocol.

[0050] In one embodiment, remote unit 105 may include computing devices such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smartphones, smart TVs (e.g., internet-connected TVs), smart appliances (e.g., internet-connected appliances), set-top boxes, game consoles, security systems (including security cameras), in-vehicle computers, network devices (e.g., routers, switches, modems), etc. In some embodiments, remote unit 105 includes wearable devices such as smartwatches, fitness bands, optical head-mounted displays, etc. Furthermore, remote unit 105 may be referred to as UE, subscriber unit, mobile device, mobile station, user, terminal, mobile terminal, fixed terminal, subscriber station, user terminal, wireless transmit / receive unit (“WTRU”), device, or other terms used in the art. In various embodiments, remote unit 105 includes a subscriber identity and / or identification module (“SIM”) and a mobile device (“ME”) that provides mobile terminal functions (e.g., radio transmission, conversion, voice encoding and decoding, error detection and correction, signaling and access to the SIM). In some embodiments, the remote unit 105 may include a terminal device (“TE”) and / or be embedded in an electrical appliance or device (e.g., a computing device as described above).

[0051] Remote unit 105 can communicate directly with one or more base station units 121 in RAN 120 via uplink (“UL”) and downlink (“DL”) communication signals. Additionally, UL and DL communication signals can be carried on wireless communication link 123. Here, RAN 120 is an intermediate network providing remote unit 105 with access to mobile core network 140. As described in more detail below, RAN 120 (i.e., via base unit 121) can send control signaling 125 for multiple PUSCHs to remote unit 105, wherein remote unit 105 sends a set 127 of TBs to base station unit 121 based on scheduling and repetition information in the control signaling 125. In some embodiments, control signaling 125 includes dynamic indications that can be used with semi-statically configured factors to determine a repetition scheme for the set 127 of TBs, as described in further detail below.

[0052] In some embodiments, remote unit 105 communicates with application server 141 via a network connection to mobile core network 140. For example, application 107 in remote unit 105 (e.g., a web browser, media client, telephone, and / or Voice over Internet Protocol (“VoIP”) application) can trigger remote unit 105 to establish a Protocol Data Unit (“PDU”) session (or other data connection) with mobile core network 140 via RAN 120. Mobile core network 140 then uses the PDU session to relay services between remote unit 105 and application server 151 in packet data network 150. The PDU session represents a logical connection between remote unit 105 and user plane function (“UPF”) 141.

[0053] To establish a PDU session (or PDN connection), remote unit 105 must register with mobile core network 140 (also referred to as "attached to mobile core network" in the context of fourth-generation ("4G") systems). Note that remote unit 105 may establish one or more PDU sessions (or other data connections) with mobile core network 140. Therefore, remote unit 105 may have at least one PDU session for communicating with packet data network 150. Remote unit 105 may establish additional PDU sessions for communicating with other data networks and / or other communication peers.

[0054] In the context of a 5G system (“5GS”), the term “PDU session” refers to a data connection that provides end-to-end (“E2E”) user plane (“UP”) connectivity between remote unit 105 and a specific data network (“DN”) via UPF 141. A PDU session supports one or more Quality of Service (“QoS”) streams. In some embodiments, a one-to-one mapping may exist between QoS streams and QoS profiles, such that all packets belonging to a particular QoS stream have the same 5G QoS identifier (“5QI”).

[0055] In the context of 4G / LTE systems such as Evolved Packet System (“EPS”), a Packet Data Network (“PDN”) connection (also known as an EPS session) provides end-to-end (E2E) connectivity between the remote unit and the PDN. The PDN connectivity process establishes an EPS bearer, i.e., a tunnel between the remote unit 105 and the packet gateway (“PGW”, not shown) in the mobile core network 140. In some embodiments, a one-to-one mapping exists between the EPS bearer and the QoS profile, such that all packets belonging to a particular EPS bearer have the same QoS class identifier (“QCI”).

[0056] Base station unit 121 may be distributed across a geographical area. In some embodiments, base station unit 121 may also be referred to as an access terminal, access point, base station, Node B (“NB”), Evolved Node B (abbreviated as eNodeB or “eNB”, also known as Evolved Universal Terrestrial Radio Access Network (“E-UTRAN”) Node B), 5G / NR Node B (“gNB”), Home Node B, Relay Node, RAN Node, or any other term used in the art. Base station unit 121 is typically part of a RAN such as RAN 120, which may include one or more controllers communicatively coupled to one or more corresponding base station units 121. These and other elements of the radio access network are not illustrated but are generally well known to those skilled in the art. Base station unit 121 is connected to mobile core network 140 via RAN 120.

[0057] Base station unit 121 can serve multiple remote units 105 within its service area, such as a cell or cell sector, via wireless communication link 123. Base station unit 121 can communicate directly with one or more remote units 105 via communication signals. Typically, base station unit 121 transmits DL communication signals to serve remote units 105 in the time, frequency, and / or spatial domains. Furthermore, DL communication signals can be carried on wireless communication link 123. Wireless communication link 123 can be any suitable carrier in licensed or unlicensed radio spectrum. Wireless communication link 123 facilitates communication between one or more remote units 105 and / or one or more base station units 121. Note that during NR-U operation, base station unit 121 and remote units 105 communicate via unlicensed (i.e., shared) radio spectrum.

[0058] In one embodiment, the mobile core network 140 is a 5GC or Evolved Packet Core (“EPC”), which may be coupled to a packet data network 150, such as the Internet and private data networks, as well as other data networks. The remote unit 105 may have a subscription or other account with respect to the mobile core network 140. Each mobile core network 140 belongs to a single mobile network operator, such as a Public Land Mobile Network (“PLMN”). This disclosure is not intended to limit implementation to any particular wireless communication system architecture or protocol.

[0059] Mobile core network 140 includes several network functions (“NFs”). As depicted, mobile core network 140 includes at least one UPF 141. Mobile core network 140 also includes multiple control plane (“CP”) functions, including but not limited to Access and Mobility Management Functions (“AMF”) 143, Session Management Functions (“SMF”) 145, Policy Control Functions (“PCF”) 147, and Unified Data Management Functions (“UDM”) serving RAN 120. In some embodiments, UDM is quasi-co-located with User Data Repository (“UDR”) and is depicted as a combined entity “UDM / UDR” 149. In various embodiments, mobile core network 140 may also include Authentication Server Functions (“AUSF”), Network Repository Functions (“NRF”) (which are used by various NFs to discover and communicate with each other via Application Programming Interfaces (“API”), or other NFs defined for 5GC. In some embodiments, mobile core network 140 may include an Authentication, Authorization, and Accounting (“AAA”) server.

[0060] In various embodiments, the mobile core network 140 supports different types of mobile data connections and different types of network slices, wherein each mobile data connection utilizes a specific network slice. Here, a "network slice" refers to a portion of the mobile core network 140 optimized for a specific service type or communication service. A network slice instance may be identified by a single network slice selection aid information ("S-NSSAI"), while the set of network slices authorized for use by the remote unit 105 is identified by network slice selection aid information ("NSSAI"). Here, "NSSAI" refers to a vector value including one or more S-NSSAI values. In some embodiments, various network slices may include separate instances of network functions, such as SMF 145 and UPF 141. In some embodiments, different network slices may share some common network functions, such as AMF 143. For illustration purposes, in Figure 1 Different network slices are not shown, but their support is assumed.

[0061] Despite Figure 1 A specific number and type of network functions are described, but those skilled in the art will recognize that any number and type of network functions can be included in the mobile core network 140. Furthermore, in the LTE variant of the mobile core network 140 where the EPC is an EPC, the described network functions can be replaced with appropriate EPC entities, such as a Mobility Management Entity (“MME”), Serving Gateway (“SGW”), PGW, Home Subscriber Server (“HSS”), etc. For example, AMF 143 can be mapped to the MME, SMF 145 can be mapped to the control plane portion of the PGW and / or the MME, UPF 141 can be mapped to the SGW and the user plane portion of the PGW, UDM / UDR 149 can be mapped to the HSS, and so on.

[0062] Although Figure 1 The components of the 5G RAN and 5G core network are depicted, but the embodiments described for indicating the repetition scheme of the set of TBs for scheduling are applicable to other types of communication networks and RATs, including IEEE 802.11 variants, Global System for Mobile Communications (“GSM”, i.e., 2G digital cellular networks), General Packet Radio Service (“GPRS”), General Mobile Telecommunications System (“UMTS”), LTE variants, CDMA 2000, Bluetooth, ZigBee, Sigfox, etc.

[0063] In the following description, the term "RAN node" is used for base station, but it can be replaced by any other radio access node such as gNB, eNB, base station ("BS"), access point ("AP"), etc. Furthermore, the operation is primarily described in the context of 5G NR. However, the proposed solution / method is equally applicable to other mobile communication systems that support repetitive schemes indicating a set of TBs for scheduling.

[0064] Figure 2 An NR protocol stack 200 according to an embodiment of this disclosure is depicted. Although Figure 2 The diagram shows UE 205, RAN node 210, and AMF 215 in the 5G core network (“5GC”), but these represent a collection of remote units 105 that interact with base station unit 121 and mobile core network 140. As depicted, protocol stack 200 includes user plane protocol stack 201 and control plane protocol stack 203. User plane protocol stack 201 includes physical (“PHY”) layer 220, medium access control (“MAC”) sublayer 225, radio link control (“RLC”) sublayer 230, packet data convergence protocol (“PDCP”) sublayer 235, and service data adaptation protocol (“SDAP”) layer 240. Control plane protocol stack 203 includes physical layer 220, MAC sublayer 225, RLC sublayer 230, and PDCP sublayer 235. Control plane protocol stack 203 also includes radio resource control (“RRC”) layer 245 and non-access stratum (“NAS”) layer 250.

[0065] The AS layer (also referred to as the "AS protocol stack") for the user plane protocol stack 201 consists of at least SDAP, PDCP, RLC, and MAC sublayers, as well as a physical layer. The AS layer for the control plane protocol stack 203 consists of at least RRC, PDCP, RLC, and MAC sublayers, as well as a physical layer. Layer 2 ("L2") is divided into SDAP, PDCP, RLC, and MAC sublayers. Layer 3 ("L3") includes the RRC sublayer 245 and NAS layer 250 for the control plane and includes, for example, the Internet Protocol ("IP") layer and / or PDU layer (not depicted) for the user plane. L1 and L2 are referred to as "lower layers," while L3 and the layers above (e.g., transport layer, application layer) are referred to as "higher layers" or "upper layers."

[0066] Physical layer 220 provides a transport channel to MAC sublayer 225. During NR-U operation, physical layer 220 may perform clear channel assessment and / or listen-before-talk (“CCA / LBT”) procedures using energy detection thresholds. In some embodiments, physical layer 220 may send a notification of UL listen-before-talk (“LBT”) failure to the MAC entity at MAC sublayer 225. MAC sublayer 225 provides a logical channel to RLC sublayer 230. RLC sublayer 230 provides an RLC channel to PDCP sublayer 235. PDCP sublayer 235 provides radio bearers to SDAP sublayer 240 and / or RRC layer 245. SDAP sublayer 240 provides QoS flows to the core network (e.g., 5GC). RRC layer 245 provides carrier aggregation and / or dual connectivity addition, modification, and release. RRC layer 245 also manages the establishment, configuration, maintenance, and release of signaling radio bearers (“SRB”) and data radio bearers (“DRB”).

[0067] NAS layer 250 is located between UE 205 and 5GC 215. NAS messages are transparently transmitted through the RAN. NAS layer 250 is used to manage the establishment of communication sessions and to maintain continuous communication with UE 205 when UE 205 moves between different cells in the RAN. Conversely, AS layer is located between UE 205 and the RAN (i.e., RAN node 210) and carries information through the radio portion of the network.

[0068] Regarding time-domain resource allocation, this document describes the use of a single instance of control signaling (e.g., DCI and / or CG) to schedule multiple PUSCHs with different transport blocks (“TBs”) and the repetition of one or more scheduled transport blocks when multiple start and length indicator values ​​(“SLIV”) are indicated by rows of a time-domain resource allocation table (“TDRA”) corresponding to different TBs, and additionally to configure / indicate the repetition factor dynamically or semi-statically.

[0069] In some embodiments, multiple PUSCHs are scheduled, for example, one TB / PUSCH and at least some PUSCH overlaps. These embodiments are highly relevant to URLLC operation. In other embodiments, multiple PUSCHs are scheduled with one TB and at least one TB / multiple PUSCH overlaps for multiple PUSCH scheduling. These embodiments are highly relevant to coverage enhancement. While the solutions and embodiments discussed herein primarily address scheduling from a PUSCH perspective, they are applicable to other physical shared channels as well as physical downlink shared channels (“PUSCH”) and physical sidelink shared channels (“PSSCH”).

[0070] In the following description, the term "DCI" is used for a single instance of control signaling, but it can be replaced by any other scheduling license, such as DCI format 0_0, DCI format 0_1, UL license in a random access response ("RAR") message, configured license type 1, configured license type 2, etc.

[0071] According to 3GPP Rel-16 NR URLLC, the following protocols have been established related to PUSCH enhancements and corresponding time-domain resource allocation:

[0072] A single PUSCH transport instance is not permitted to cross at least the slot boundaries used for licensed PUSCHs. One or more actual PUSCHs repeating within a slot, or two or more actual PUSCHs repeating across slot boundaries in consecutive available slots, are supported using a UL license for dynamic PUSCHs and a configurable license configuration for configurable licensed PUSCHs.

[0073] To address the aforementioned issues, dynamic indication of the nominal repetition count in the DCI-scheduled dynamic PUSCH is supported for PUSCH enhancement. Furthermore, the Time Domain Resource Assignment (TDRA) field in the DCI or the TDRA parameter in the Type 1 configured license indicates the resource for the first "nominal" repetition. However, note that PUSCH mapping type A is not supported for the above options.

[0074] Regarding the interpretation of parameters L and K for all PUSCH transmissions, in one embodiment, the time window in which valid symbols are used for transmission is L*K. In another embodiment, the time window in which valid symbols are used for transmission can be longer than L*K symbols, and is extended at least in the case of semi-static DL symbols. For Rel-16 PUSCH with enhanced repetitive transmissions, the time window in which valid symbols are used for transmission is L*K, starting from the first symbol indicated by SLIV in the TDRA field.

[0075] It is agreed that the Rel-16 Enhanced PUSCH scheme (including dynamic indication of repetition count) is supported for DCI format 0_1 ​​and the new UL DCI formats (for DG and Type 2 CG). It is further agreed that the Rel-16 Enhanced PUSCH scheme is not supported for DCI format 0_0 and Type 2 configuration licensing (“CG”) for dynamic licensing (“DG”).

[0076] For the dynamic indication of the number of repetitions used for dynamic licensing, it is agreed that joint encoding with SLIV in the TDRA table can be supported by adding an additional column for the number of repetitions to the TDRA table. The maximum TDRA table size is 64.

[0077] It is agreed to use DCI format 0_1 ​​& the new UL DCI format to support the use of slot aggregation to dynamically indicate the number of repetitions for 3GPP Release 15 (“Rel-15”) PUSCH. The dynamic indication is accomplished by using the same Rel-16 mechanism (e.g., co-encoding the number of repetitions with SLIV in the TDRA table).

[0078] Regarding CG PUSCH transfers, for initial type 2CG PUSCH transfers, the TDRA table follows the activated DCI. Additionally, for initial type 2CG PUSCH transfers with PUSCH repetition type A or type B, if it exists in the corresponding TDRA table, the repetition count is provided by activating the DCI via the parameter numberofrepetitions; otherwise, the repetition count is provided by the parameter repK.

[0079] For an initial type 1CG PUSCH transmission with PUSCH repeat type B, if one and only one of DCI formats 0_1 and 0_2 is configured with PUSCH repeat type B, the TDRA table corresponding to the DCI format (0_1 or 0_2) configured with PUSCH repeat type B is used. If both DCI formats 0_1 and 0_2 are configured with PUSCH repeat type B, the TDRA table corresponding to DCI format 0_1 ​​is used.

[0080] For an initial type 1CG PUSCH transfer with PUSCH repetition type B, an error occurs if neither DCI format 0_1 ​​nor 0_2 is configured with PUSCH repetition type B. For an initial type 1CG PUSCH transfer, if it is configured with PUSCH repetition type A, the TDRA table used in Rel-15 for the user-specific search space (“USS”) is used. For an initial type 1CG PUSCH transfer with PUSCH repetition, the number of repetitions is provided via the parameter numberofrepetitions if it exists in the corresponding TDRA table; otherwise, the number of repetitions is provided by the parameter repK.

[0081] In URLLC in Rel-16, TDRA has been enhanced to indicate the repetition factor (but still has a single SLIV). This disclosure provides new details when this aspect needs to be combined with the enhancements in NR-U in Rel-16 to indicate multiple PUSCH / slots using a TDRA table.

[0082] In various embodiments, the column for the number of repetitions (numberofrepetitions) always exists in the parameters PUSCH-TimeDomainResourceAllocationList-ForDCIformat0_1 and PUSCH-TimeDomainResourceAllocationList-ForDCIformat0_2.

[0083] For dynamic permissions with PUSCH repetition type A, the number of repetitions is given by `numberofrepetitions` if it exists in the corresponding TDRA table. Otherwise, if the UE is configured with a `pusch-AggregationFactor`, the number of repetitions is given by `pusch-AggregationFactor`. Otherwise, the number of repetitions is 1.

[0084] For dynamic licenses with PUSCH repeat type B, the number of repetitions is given by numberofrepetitions. Note that pusch-TimeDomainAllocationList-ForDCIformat0_1 / 2 needs to be configured for PUSCH repeat type B.

[0085] For PUSCH repetition types A and B, the number of bits indicating numberofrepetitions is 3. {1,2,[3],4,[6],7,[8],12,16} is supported. In some embodiments, for PUSCH repetition type B, L<=14.

[0086] In order to indicate S and L in the TDRA table for PUSCH repeat type B, S and L are indicated separately (4 bits for S and 4 bits for L). S ranges from 0 to

[13] , and L ranges from [1] to 14. Note that additional restrictions may still apply for specific waveform and / or demodulation reference signal (“DMRS”) mapping types from Rel-15.

[0087] In some embodiments, {3,8} is additionally supported for numberofrepetitions of PUSCH repetition types A and B. That is, {1,2,3,4,7,8,12,16} is supported for numberofrepetitions.

[0088] In some embodiments, for a PUSCH with repetition type B, it is not intended to use an antenna port configuration that is ineffective for the duration of any actual repetition to indicate the UE. In some embodiments, for a PUSCH with repetition type B, an actual repetition with a single symbol is not transmitted.

[0089] According to Rel 16NR-U, the following protocols have been established regarding multi-PUSCH scheduling and corresponding time-domain resource allocation:

[0090] To signal the number of scheduled PUSCHs and TDRAs in a DCI that schedules multiple PUSCHs, the TDRA table is expanded such that each row indicates multiple PUSCHs (contiguous in the time domain). In some embodiments, each scheduled PUSCH has a separate SLIV and mapping type. The number of scheduled PUSCHs is signaled by the number of valid SLIVs indicated in the rows of the signaled TDRA table in the DCI.

[0091] For scheduling multiple PUSCHs using a single DCI format 0_1, the same DCI format 0_1 ​​can schedule either a single PUSCH or multiple PUSCHs. The maximum number of PUSCHs that can be configured in a single row of the TDRA table is 8. Furthermore, the number of NDI bits and RV bits in DCI format 0_1 ​​is determined based on the configured TDRA table.

[0092] i.1 If multiple PUSCHs are scheduled, each PUSCH is 1RV bits.

[0093] ii.2 If only a single PUSCH is scheduled, then for that PUSCH2RV bit...

[0094] The TDRA table configuration allows indicating a single or multiple consecutive PUSCHs in any time slot across multiple scheduling time slots.

[0095] For a DCI format 0_1 ​​that schedules multiple PUSCHs using signaling, the number of scheduled PUSCHs and TDRAs is determined by expanding the TDRA table so that each row indicates multiple PUSCHs (contiguous in the time domain). Each PUSCH has a separate SLIV and mapping type. The number of PUSCHs scheduled using signaling is determined by the number of valid SLIVs indicated in the rows of the signaled TDRA table in the DCI. Note that for fallback DCI, a Rel-15 TDRA table can be used.

[0096] The key difference between the solution below and the repetition scheme used for URLLC in Rel-16 / 15 is that the solution below uses multiple SLIVs to indicate multiple PUSCHs. Note that the scheduled TB may span more than one slot / TTI.

[0097] According to the first solution, the repetition scheme for multiple PUSCH transmissions is dynamically scheduled by a single instance of control signaling, such as a single DCI. According to the second solution, the selective repetition scheme for multiple PUSCH transmissions is dynamically scheduled by a single instance of control signaling, such as a single DCI. According to the third solution, the prioritization scheme for multiple PUSCH transmissions is dynamically scheduled by a single instance of control signaling, such as a single DCI.

[0098] The first subset of the first solution described herein, referred to as "Solution 1a," is characterized by scheduling a first instance of each TB / PUSCH transmission with a multi-PUSCH license before scheduling a repetition of any TB / PUSCH transmission with a multi-PUSCH license. This solution is also referred to herein as "Multi-PUSCH First, Repetition Second." As mentioned above, the scheduled TBs can span multiple time slots.

[0099] According to Solution 1a, when the UE is indicated to have multiple SLIVs and corresponding mapping types via a single row of the TDRA table in the scheduling permission (e.g., DCI or CG), and additionally indicated by a repetition factor via a row of the TDRA table, the UE first allocates time-domain resources for multiple PUSCHs with different TBs in a sequential manner, followed by repetition of all scheduled PUSCHs. Repetition scheme type A (i.e., slot-based repetition) or type B (i.e., non-slot-based repetition) can be applied to multi-PUSCH scheduling according to this solution.

[0100] In the example, when PUSCH type B repetition is applied, the nominal repetition length for a given PUSCH and the repetition corresponds to the indicated length parameter L, but the start symbol for subsequent repetitions of a given PUSCH can be the same as or different from the indicated start symbol parameter S. Note that the actual length of the repetition for any PUSCH can be shorter than the nominal length, depending on segmentation caused by slot boundaries, invalid symbols, or any unavailable symbols for UL transmission. In some embodiments of Solution 1a, the repetition mechanism for each PUSCH follows the current PUSCH repetition type B as specified in 3GPP Technical Specification (“TS”) 38.214v 16.1.0.

[0101] Figure 3An example of a time-domain resource allocation 300 with repetition type B according to an embodiment of solution 1a is depicted. As depicted, the repetition scheme used in the time-domain resource allocation 300 schedules multiple PUSCH first and repetition second. Note that repetition type B supports repetition within time slots, such as... Figure 3 As depicted in [the text]. In one embodiment, repetition type B is configured in such a way that in-slot transmissions can be aligned with slot boundaries, as [example configuration would be here]. Figure 5 As depicted in [the text]. In other embodiments, repetition type B can cause PUSCH transmissions to cross slot boundaries, such as [the text is incomplete]. Figure 3 As depicted in [the document]. In some embodiments, repetition type B may use microslot-based repetition.

[0102] As described above, the TDRA table may include a mapping type indicating a specific repeat scheme. For example, when a row in the TDRA table indicates the corresponding field and value as shown in index 1 of Table 1 (hereinafter), and the PUSCH repeat type B (without invalid symbols) according to 3GPP TS 38.214v16.1.0 is indicated / configured to the UE, then in Figure 3 The diagram illustrates the allocation of time-domain resources for multiple PUSCH transfers and their corresponding repetitions.

[0103] Table 1: Example of TDRA row index for multi-PUSCH scheduling with repetition factor

[0104]

[0105] In one implementation of solution 1a, the number of repetitions can be dynamically indicated by a TDRA table, such as as disclosed in Table 1 above. When multiple SLIVs and a repetition factor are indicated, the SLIVs are for multiple PUSCHs, and the indicated repetition factor is applied to all PUSCHs. In an alternative implementation, the number of repetitions can be semi-statically indicated by higher-level signaling (e.g., RRC signaling).

[0106] In another embodiment of solution 1a, if mapping type B is indicated by a row in the TDRA table for any of the multiple PUSCH transmissions, then UE 205 is not expected to be configured / indicated with PUSCH repetition type A.

[0107] Figure 4 An example of a time-domain resource allocation 400 for multiple PUSCH first and second repetitions having repetition type A, according to an embodiment of the present disclosure, is depicted. The time-domain resource allocation 400 is based on solution 1a. Note that repetition type B is slot-based repetition. However, the size of the PUSCH transmission can be based on micro-slots.

[0108] In some embodiments of Solution 1a, when PUSCH repetition type A is configured / indicated to the UE using multi-PUSCH scheduling, all PUSCH transmissions with different TBs are then temporally consecutive. For repetition type A, the repetition is slot-based and not necessarily temporally consecutive. In this implementation scenario, the same SLIV applies to the first transmission and corresponding repetition of a given PUSCH. For example, when the rows of the TDRA table indicate the corresponding fields and values ​​as shown in index 1 of Table 2 (hereinafter), and PUSCH repetition type A is configured / indicated to the UE, the time domain resource allocation is as follows: Figure 4 As shown in the diagram.

[0109] Table 2: Example of TDRA row index for multi-PUSCH scheduling with repetition factor

[0110]

[0111] In one implementation, the number of repetitions can be dynamically indicated by a TDRA table, such as those disclosed in Table 2 above. Again, when multiple SLIVs and a repetition factor are indicated, the SLIVs are for multiple PUSCHs, and the indicated repetition factor is applied to all PUSCHs. In an alternative implementation, the number of repetitions can be semi-statically indicated by higher-level signaling (e.g., RRC signaling).

[0112] In another embodiment of solution 1a, if mapping type A is indicated by a row in the TDRA table for any of the multiple PUSCH transmissions, then UE 205 is not expected to be configured / indicated with PUSCH repetition type B.

[0113] This document describes a second subset of the first solution, referred to as "Solution 1b," characterized by scheduling repetition in the first case and multiple PUSCH in the second. As mentioned above, the scheduled TB can span multiple time slots.

[0114] According to Solution 1b, when the UE is indicated by a single row of the TDRA table in the scheduling DCI to have multiple SLIVs and corresponding mapping types, and additionally by a row of the TDRA table indicating a repetition factor, the UE first allocates temporal resources for the first PUSCH and its corresponding repetition. After the repetition of the first PUSCH, temporal resources are allocated for the next PUSCH with a different TB and its corresponding repetition, and so on.

[0115] Compared to Solution 1a, here the repetition of the first PUSCH transmission is followed by a different PUSCH transmission. For example, in one implementation of Solution 1b, when the row of the TDRA table indicates the corresponding field and value as shown in index 1 of Table 3 (hereinafter), and PUSCH repetition type B (without invalid symbols) is indicated / configured to the UE according to 3GPP TS38.214v16.1.0, then the time-domain resource allocation for multiple PUSCH transmissions and corresponding repetitions is... Figure 5 The diagram illustrates the scheme of repeating the first time according to the scheduling.

[0116] Table 3: Example of TDRA row index for multi-PUSCH scheduling with repetition factor

[0117]

[0118] Figure 5 An example of time-domain resource allocation 500 for a repeating first and multiple PUSCH second with repeating type B, according to an embodiment of solution 1b, is depicted. As described above, using repeating type B, repeating can occur within the same time slot. The time-domain resource allocation 500 is according to the first solution, wherein the repeating scheme for all PUSCHs is scheduled by a single DCI.

[0119] Figure 6 An example of a time-domain resource allocation 600 for a first repetition of repetition type A and a second multiple PUSCH, according to an embodiment of this disclosure, is depicted. The time-domain resource allocation 600 is based on solution 1b. Note that for a given PUSCH, its repetitions are not in the same time slot, but the repetitions of another PUSCH can be in the same time slot, provided that the indicated UL symbol is available.

[0120] In one implementation of Solution 1b, when PUSCH repetition type A is configured / instructed to the UE using multi-PUSCH scheduling, time-domain resources are first allocated to the first PUSCH transmission according to the first indicated SLIV via rows of the TDRA table. Then, the repetition of the first PUSCH is allocated resources in the next available time slot with the same SLIV. Then, time-domain resources for the second PUSCH are allocated, these time-domain resources being sequential in time with respect to the last repetition of the first PUSCH. The same process is followed for multiple PUSCHs and repetitions. Examples of TDRA rows and corresponding time-domain resource allocations are shown in Table 4 (below) and... Figure 6 The diagram in the middle is shown.

[0121] Table 4: Example of TDRA row index for multi-PUSCH scheduling with repetition factor

[0122]

[0123] In an alternative implementation, the number of repetitions can also be indicated in a semi-static manner via higher-level signaling (e.g., RRC signaling).

[0124] In another implementation of solution 1b, if mapping type A is indicated by a row in the TDRA table for any of the multiple PUSCH transmissions, then the UE is not expected to be configured / indicated with PUSCH repetition type B.

[0125] The third subset of the first solution described herein, referred to as "Solution 1c," is characterized by multi-PUSCH scheduling within a single TB. Advantageously, Solution 1c supports coverage enhancement and increases the likelihood of successful transmission in operations with shared (i.e., unlicensed) spectrum.

[0126] According to Solution 1c, when a UE has a SLIV and a corresponding mapping type indicated by a single row of the TDRA table in the scheduling DCI, and a repetition factor indicated by a row of the TDRA table, the UE allocates time-domain resources for a single TB and its corresponding repetition. In one embodiment, the scheduled TB can span multiple time slots, for example, to support TBs via multiple time slots (“TBoMS”). TB repetition can be time slot-based (i.e., repetition type A) or can support repetition within a time slot (i.e., repetition type B).

[0127] As described above, according to the second solution, the UE receives an instruction and / or configuration for a selective repetition scheme for multiple PUSCHs. As used herein, "selective repetition" refers to different repetition factors applied to different TB / PUSCH transmissions within multiple PUSCHs. In some embodiments, certain TBs are repeated at a higher frequency, while other TBs are repeated at a lower frequency. In other embodiments, certain TBs are repeated while other TBs are not.

[0128] This document describes a first subset of the second solution, referred to as "Solution 2a," characterized by a selective repetition scheme based on the NDI value of the PUSCH scheduled by a single DCI. As mentioned above, the scheduled TB can span multiple time slots.

[0129] According to Solution 2a, when the UE has multiple SLIVs and corresponding mapping types indicated by a single row of the TDRA table in the scheduling DCI, and the TDRA table also indicates the repetition factor by a row and indicates the NDI bitmap for multiple PUSCHs, then the scheduling repetition is only for the PUSCHs whose corresponding NDI bits are switched, that is, only for the PUSCHs in which a new TB is transmitted (without retransmission).

[0130] Figure 7An example of selectively repeating time-domain resource allocation 700 for a new TB for which an NDI is switched, according to an embodiment of solution 2a, is depicted. As depicted, time-domain resource allocation 700 can be used with repetition type A for an NDI (new TB) used only for a second PUSCH switch. For example, for TDRA Table 4 (above), if the NDI is switched only for the second PUSCH, then in Figure 7 The diagram shows the time-domain resource allocation based on this solution.

[0131] In some embodiments, solution 2a can be referenced above. Figure 5 and Figure 6 The discussion repeats the first, and the second, multiple-push solution combination. In other embodiments, solution 2a can be referenced above. Figure 3 and Figure 4 The first and second solutions are discussed in the multi-push discussion. In other words, solution 2a can be applied in conjunction with any of the solutions and implementations discussed above in solution 1a and / or solution 1b.

[0132] This document describes a second subset of the second solution, referred to as "Solution 2b," characterized by a selective repetition scheme based on the intra-UE priority value of the PUSCH scheduled by a single DCI. As mentioned above, the scheduled TB can span multiple time slots.

[0133] According to Solution 2b, when a UE has multiple SLIVs and corresponding mapping types indicated by a single row of the TDRA table in the scheduling DCI, and the TDRA table indicates a repetition factor, and the UE is configured with intra-UE priority levels associated with different PUSCHs (TBs), then repetition is scheduled only for PUSCHs with higher priority levels.

[0134] In one implementation of solution 2b, the UE is configured / indicated with a priority level threshold. If the priority level associated with the scheduled TB is higher than or equal to the threshold, repetition is performed only for the corresponding PUSCH; otherwise, repetition is not performed for PUSCHs with a priority level lower than the threshold.

[0135] In another implementation of solution 2b, only one of the two priority levels can be associated with the PUSCH; for example, the first priority level can be eMBB, and the second priority level can be URLLC. Duplicates are performed only if a given PUSCH has the URLLC priority level; otherwise, duplicates are not performed for a given PUSCH with the eMBB priority level.

[0136] In an alternative implementation of solution 2b, when each of the scheduled PUSCHs is indicated with a certain priority level (as described below in the third solution), the repetition factor associated with those priority levels can be different. So, for example, the URLLC priority level implies Rmax = 4, and the eMBB priority level implies Rmax = 2. These different maximum repetitions (Rmax) values ​​can be further indicated by entries in the TDRA table. In an alternative implementation, the Rmax value can be indicated semi-statically via higher-level signaling (e.g., RRC signaling).

[0137] It should be noted that solution 2b can be applied in conjunction with any of the solutions and implementations discussed above in solution 1a and / or solution 1b and / or solution 2a.

[0138] This document describes a third subset of the second solution, referred to as "Solution 2c," characterized by a selective repetition scheme based on the mapping type of the PUSCH scheduled by a single DCI. As mentioned above, the scheduled TB can span multiple time slots.

[0139] According to Solution 2c, when a UE has multiple SLIVs and corresponding mapping types indicated by a single row in the TDRA table in the scheduling DCI, and also by a repetition factor indicated by a row in the TDRA table, and the UE is configured / indicated to PUSCH repetition type B, then repetition is applied only to PUSCHs with the corresponding mapping type B. If there are multiple scheduled PUSCHs and they are associated with different mapping types, then the PUSCH associated with mapping type A will not be repeated with PUSCH repetition type B. For such PUSCHs, only the first instance is transmitted.

[0140] Note that solution 2c can be applied in conjunction with any of the solutions and implementations discussed above in solution 1a and / or solution 1b and / or solution 2a and / or solution 2b.

[0141] The third solution described herein is characterized by the use of DCI format for scheduling one or more PUSCHs carrying different transport blocks (“TBs”), including one or more priority indicators, each priority indicator corresponding to a PUSCH for each schedule. As mentioned above, the scheduled TBs can span multiple time slots.

[0142] In one example of the third solution, the size of the priority indicator field in the DCI format, which supports multiple PUSCH scheduling and priority indicators, is determined as follows:

[0143] Priority indicator:

[0144] If the higher-level parameter PriorityIndicator-ForDCIFormat0_x is not configured (e.g., x = 1, 2), then 0 bits are used;

[0145] If the higher-level parameter PriorityIndicator-ForDCIFormat0_xis is configured and the number of scheduled PUSCHs indicated by the time-domain resource assignment field is 1, then 1 bit;

[0146] The number of bits 2, 3, 4, 5, 7, 7, or 8 is determined based on the maximum number of schedulable PUSCHs in all entries of the higher-level parameter pusch-TimeDomainAllocationList-r16, for example, as defined in Clause 7.1.4 of 3GPP TS 38.214.

[0147] Here, in the DCI format, the bits of the priority indicator field are mapped one-to-one with the corresponding transport blocks to the scheduled PUSCHs, with the least significant bit (“LSB”) of the priority indicator field corresponding to the scheduling order of the last scheduled PUSCH. For the bits of the priority indicator field, a bit value “1” indicates a higher priority than a bit value “0”.

[0148] In another embodiment of the third solution, the DCI format for scheduling one or more PUSCHs carrying different transport blocks includes a priority indicator applied to the PUSCH of one schedule. The PUSCHs of the remaining(s) schedules are considered to have a priority index of "0" (i.e., lower priority).

[0149] In one implementation of the third solution, a scheduled PUSCH is the first scheduled PUSCH. In another implementation of the third solution, a scheduled PUSCH is the last scheduled PUSCH. In yet another implementation of the third solution, the UE receives information about the order of scheduled PUSCHs to which a priority indicator is applicable via higher-layer signaling (e.g., RRC and / or MAC control elements (“CE”)). That is, a scheduled PUSCH is determined based on the received information.

[0150] In one example, the size of the priority indicator field in the DCI format, which supports multiple PUSCH scheduling and priority indicators, is determined as follows:

[0151] Priority indicator:

[0152] If the higher-level parameter PriorityIndicator-ForDCIFormat0_x is not configured (e.g., x = 1, 2), then 0 bits are used;

[0153] If the higher-level parameter PriorityIndicator-ForDCIFormat0_x is configured, then 1 bit.

[0154] In the DCI format, the priority indicator field bits indicate the priority index of the first (or last, or higher-level) scheduled PUSCH.

[0155] In another embodiment of the third solution, the DCI format for scheduling one or more PUSCHs carrying different transport blocks includes a priority indicator applied to all PUSCH(s) scheduled by the DCI format.

[0156] In one example, the size of the priority indicator field in a DCI format that supports multiple PUSCH scheduling and priority indicators is determined as follows:

[0157] Priority indicator:

[0158] If the higher-level parameter PriorityIndicator-ForDCIFormat0_x is not configured (e.g., x = 1, 2), then 0 bits are used;

[0159] If the higher-level parameter PriorityIndicator-ForDCIFormat0_x is configured, then 1 bit.

[0160] The priority indicator field in the DCI format indicates the priority index for all scheduled PUSCHs.

[0161] Regarding URLLC, in one embodiment, the URLLC service does not support PUSCH repetition type B with a licensed "CG" configured based on NR-U Rel-16 for shared (i.e., unlicensed) band operation. In another embodiment, the URLLC service supports enhancements to PUSCH repetition type B, such as those described above, when using an NR-U Rel-16-based CG for unlicensed band operation.

[0162] Regarding coverage enhancement, multiple PUSCH transport bearers will be repeated in a single TB, as described above. In some embodiments, consecutive physical time slots for UL transport can be used for TBs (“TBoMS”) across multiple time slots for unpaired spectrum. In one embodiment, non-consecutive physical time slots can be used for UL transport for TBoMS for unpaired spectrum. In some embodiments, consecutive physical time slots for UL transport can be used for TBoMS for paired spectrum and supplementary uplink (“SUL”) bands. In one embodiment, non-consecutive physical time slots for UL transport can also be used for paired spectrum and SUL bands.

[0163] In some embodiments, discontinuous physical time slots used for UL transmissions can be used to transmit TBoMS for at least unpaired spectrum. In some embodiments, discontinuous physical time slots used for UL transmissions can also be used to transmit TBoMS for paired spectrum and supplementary uplink bands.

[0164] Regarding the definition of a single TBoMS, in the first embodiment, a transmission occasion (“TOT”) for the TBoMS is determined. In this embodiment, a single redundant version (“RV”) is used to transmit the TB on the TOT. In one implementation, a single RV is rate-matched using continuous rate matching across the TOT. In another implementation, a single RV is rate-matched for each time slot in the TOT.

[0165] In the second embodiment, only one TOT is determined for TBoMS. In this embodiment, TBs are transmitted on the TOT using different RVs. In one implementation, the RV index is refreshed within the TOT after each slot boundary. In another implementation, the RV index is refreshed within the TOT at each hop between two non-contiguous resources (if any).

[0166] In a third embodiment, multiple TOTs are identified for TBoMS, wherein a TB is transmitted on multiple TOTs using a single RV. In one embodiment, rate matching is performed on a single RV for each of the multiple TOTs. In one embodiment, rate matching is performed on a single RV for all TOTs, for example, using consecutive rate matching across TOTs. In another embodiment, rate matching is performed on a single RV for each time slot of the multiple TOTs.

[0167] In the fourth embodiment, multiple Time-of-Touch (TOTs) are determined for TBoMS, wherein TBs are transmitted on multiple TOTs using different RVs. In one implementation, the RV index is refreshed within one TOT after each slot boundary. In another implementation, the RV index is refreshed within one TOT at each hop between two non-contiguous resources (if any).

[0168] In some embodiments, a single TBoMS can be repeated, as described above in Solution 1c.

[0169] In various embodiments, one or both of the following methods may be considered as the starting point for determining how to calculate the parameter NInfo for TBoMS. In a first method (Method 1), the starting point is based on all REs determined by the symbols or time slots allocated to it across the TBoMS transmission. In a second method (Method 2), the starting point is based on the number of REs determined by the TBoMS transmission in the first L symbols it has allocated, scaled by K ≥ 1. Here, L is the number of symbols determined using SLIV of the PUSCH indicated via TDRA.

[0170] In various embodiments, one or both of the following options will be considered to calculate the parameter NohPRB for TBoMS. In the first option (Option 1), it is assumed that NohPRB is the same for all TBoMS transmissions through all the time slots it is allocated, and can be configured via xOverhead as in Rel-15 / 16. In the second option (Option 2), the calculation of NohPRB depends on both xOverhead and the number of symbols or time slots through which TBoMS transmissions are allocated.

[0171] In some of the embodiments described above, the repetition of TBoMS is supported, as described above in Solution 1c.

[0172] Figure 8 User equipment device 800, according to embodiments of the present disclosure, can be used to indicate a repetition scheme for a set of scheduled TBs. In various embodiments, user equipment device 800 is used to implement one or more of the solutions described above. User equipment device 800 may be an embodiment of the remote unit 105 and / or UE 205 described above. Furthermore, user equipment device 800 may include processor 805, memory 810, input device 815, output device 820, and transceiver 825.

[0173] In some embodiments, input device 815 and output device 820 are combined into a single device, such as a touchscreen. In some embodiments, user equipment device 800 may not include any input device 815 and / or output device 820. In various embodiments, user equipment device 800 may include one or more of the following: processor 805, memory 810, and transceiver 825, and may not include input device 815 and / or output device 820.

[0174] As depicted, transceiver 825 includes at least one transmitter 830 and at least one receiver 835. In some embodiments, transceiver 825 communicates with one or more cells (or radio coverage areas) supported by one or more base station units 121. In various embodiments, transceiver 825 may operate on unlicensed spectrum. Furthermore, transceiver 825 may include multiple UE panels supporting one or more beams. Additionally, transceiver 825 may support at least one network interface 840 and / or application interface 845. The application interface(s) 845 may support one or more APIs. The network interface(s) 840 may support 3GPP reference points such as Uu, N1, PC5, etc. Other network interfaces 840 may be supported, as will be understood by those skilled in the art.

[0175] In one embodiment, processor 805 may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, processor 805 may be a microcontroller, microprocessor, central processing unit (“CPU”), graphics processing unit (“GPU”), auxiliary processing unit, field-programmable gate array (“FPGA”), or similar programmable controller. In some embodiments, processor 805 executes instructions stored in memory 810 to perform the methods and routines described herein. Processor 805 is communicatively coupled to memory 810, input device 815, output device 820, and transceiver 825.

[0176] In various embodiments, processor 805 controls user equipment device 800 to implement the UE behavior described above. In some embodiments, processor 805 may include an application processor (also referred to as a "main processor") that manages application domain and operating system ("OS") functions and a baseband processor (also referred to as a "baseband radio processor") that manages radio functions.

[0177] In various embodiments, via transceiver 825, processor 805 receives control signaling (e.g., DCI, CG, etc.) containing scheduling information (i.e., configuration and / or indication) for transmitting a set of one or more TBs through multiple transmission occasions (e.g., time slots) and receives repetition information (i.e., configuration and / or indication) for time-domain repetition of the set of scheduled TBs.

[0178] Processor 805 determines whether to apply time-domain repetition for each TB in the set of TBs based on the time-domain resources allocated to each TB (e.g., based on the time slot index, start symbol, and duration). Additionally, processor 805 controls transceiver 825 to transmit the set of TBs according to scheduling and repetition information.

[0179] In some embodiments, the set of TBs comprises a single TB scheduled across multiple transport instances. In other embodiments, the set of TBs comprises multiple TBs. In some embodiments, duplication information is configured semi-statically using higher-layer signaling (e.g., RRC signaling and / or MAC CE), wherein the duplication information includes at least one duplication factor.

[0180] In some embodiments, the set of TBs transmitted according to scheduling and repetition information includes a first instance of each TB in the set of TBs transmitted prior to a second instance (i.e., repetition) of any TB in the set of transmitted TBs. In other embodiments, the set of TBs transmitted according to scheduling and repetition information includes all repetitions of the first TB in the set of TBs transmitted prior to the second (i.e., the next) TB in the set of transmitted TBs.

[0181] In some embodiments, control signaling includes a Time Domain Resource Allocation (“TDRA”) table. In such embodiments, scheduling information for a set of TBs may include multiple start and length indicator values ​​(“SLIV”) in rows of the TDRA table, with the multiple SLIVs corresponding to a set of TBs. In some embodiments, repetition information includes at least one repetition factor dynamically indicated within rows of the TDRA table.

[0182] In some embodiments, the rows of the TDRA table contain the mapping type for each SLIV. In one embodiment, when the corresponding mapping type is a first type (i.e., repetition type A), the actual length of the repetition must follow the length value indicated in the SLIV. In another embodiment, when the corresponding mapping type is a second type (i.e., repetition type B), the actual length of the repetition may differ from the length value indicated in the SLIV. As described above, Figure 3 An example of a repetition type B mapping is depicted, where the actual length of the repetition differs from the length indicated in the SLIV. Instead, Figure 5 An example of repetition type B is depicted, where the actual length of the repetition differs from the length indicated in the SLIV.

[0183] In some embodiments, control signaling includes a DCI, wherein the DCI further includes an NDI value for each TB in the set of TBs. In such embodiments, determining whether to apply time-domain repetition is further based on the NDI corresponding to each TB, wherein repetition of a particular TB is not scheduled across multiple time slots when the NDI of a particular TB indicates a retransmission. As used herein, the NDI for each TB can be a 1-bit indicator, wherein a switched NDI for a HARQ process indicates that the transmission is the initial transmission of the corresponding TB, while an unswitched NDI for a HARQ process indicates that transmission occurs if a previously transmitted TB is retransmitted. A “switched” NDI means that the current NDI value (i.e., “0” or “1”) is different from the previous NDI value. An “unswitched” NDI means that the current NDI value is the same as the previous NDI value.

[0184] In some embodiments, determining whether to apply time-domain repetition is further based on a service priority level corresponding to each TB. In some embodiments, when the service priority level of a particular TB is below a threshold level, repetition of that particular TB is not scheduled across multiple time slots. In some embodiments, priority levels can be indicated using priority values, where a lower priority value indicates a higher priority level, and a higher priority value indicates a lower priority level.

[0185] In some embodiments, different repetition factors are associated with different business priority levels corresponding to a set of TBs. In some embodiments, a first TB with a higher priority has a higher repetition factor than a second TB with a lower priority.

[0186] In some embodiments, the control signaling further includes a priority indication for each TB in the set of TBs. In such embodiments, determining whether to apply time-domain repetition can be based on the service priority level corresponding to the indication for each TB.

[0187] In one embodiment, memory 810 is a computer-readable storage medium. In some embodiments, memory 810 includes volatile computer storage media. For example, memory 810 may include RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”). In some embodiments, memory 810 includes non-volatile computer storage media. For example, memory 810 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 810 includes both volatile and non-volatile computer storage media.

[0188] In some embodiments, memory 810 stores data relating to repetition schemes indicating a set of TBs for scheduling. For example, memory 810 may store various parameters, panel / beam configurations, resource assignments, policies, etc., as described above. In some embodiments, memory 810 also stores program code and related data, such as an operating system or other controller algorithms operating on device 800.

[0189] In one embodiment, input device 815 may include any known computer input device, including a touch panel, buttons, keyboard, stylus, microphone, etc. In some embodiments, input device 815 may be integrated with output device 820, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, input device 815 includes a touchscreen, allowing text to be entered using a virtual keyboard displayed on the touchscreen and / or by handwriting on the touchscreen. In some embodiments, input device 815 includes two or more different devices, such as a keyboard and a touch panel.

[0190] In one embodiment, output device 820 is designed to output visual, auditory, and / or tactile signals. In some embodiments, output device 820 includes an electronically controllable display or display device capable of outputting visual data to a user. For example, output device 820 may include, but is not limited to, a liquid crystal display (“LCD”), a light-emitting diode (“LED”) display, an organic LED (“OLED”) display, a projector, or similar display devices capable of outputting images, text, etc., to a user. As another non-limiting example, output device 820 may include a wearable display, such as a smartwatch, smart glasses, a head-up display, etc., separate from but communicatively coupled to the rest of user equipment device 800. Furthermore, output device 820 may be a component of a smartphone, personal digital assistant, television, desktop computer, laptop computer, personal computer, vehicle dashboard, etc.

[0191] In some embodiments, output device 820 includes one or more speakers for generating sound. For example, output device 820 may generate an auditory alarm or notification (e.g., a buzzer or ring). In some embodiments, output device 820 includes one or more haptic devices for generating vibration, motion, or other haptic feedback. In some embodiments, all or part of output device 820 may be integrated with input device 815. For example, input device 815 and output device 820 may form a touchscreen or similar touch-sensitive display. In other embodiments, output device 820 may be located near input device 815.

[0192] Transceiver 825 communicates with one or more network functions of a mobile communication network via one or more access networks. Transceiver 825 operates under the control of processor 805 to transmit and receive messages, data, and other signals. For example, processor 805 may selectively activate transceiver 825 (or a portion thereof) at specific times to send and receive messages.

[0193] Transceiver 825 includes at least a transmitter 830 and at least one receiver 835. One or more transmitters 830 can be used to provide UL communication signals to base station unit 121, such as UL transmissions described herein. Similarly, as described herein, one or more receivers 835 can be used to receive DL communication signals from base station unit 121. Although only one transmitter 830 and one receiver 835 are illustrated, user equipment device 800 can have any suitable number of transmitters 830 and receivers 835. Furthermore, transmitters 830 and receivers 835 can be of any suitable type. In one embodiment, transceiver 825 includes a first transmitter / receiver pair for communicating with a mobile communication network on licensed radio spectrum and a second transmitter / receiver pair for communicating with a mobile communication network on unlicensed radio spectrum.

[0194] In some embodiments, a first transmitter / receiver pair for communicating with a mobile communication network on licensed radio spectrum and a second transmitter / receiver pair for communicating with a mobile communication network on unlicensed radio spectrum may be combined into a single transceiver unit, such as a single chip performing functions for both licensed and unlicensed radio spectrum. In some embodiments, the first transmitter / receiver pair and the second transmitter / receiver pair may share one or more hardware components. For example, certain transceivers 825, transmitters 830, and receivers 835 may be implemented as physically separate components that access shared hardware and / or software resources, such as, for example, a network interface 840.

[0195] In various embodiments, one or more transmitters 830 and / or one or more receivers 835 may be implemented and / or integrated into a single hardware component, such as a multi-transceiver chip, a system-on-a-chip, an application-specific integrated circuit (“ASIC”), or other types of hardware components. In some embodiments, one or more transmitters 830 and / or one or more receivers 835 may be implemented and / or integrated into a multi-chip module. In some embodiments, other components such as network interface 840 or other hardware components / circuitets may be integrated with any number of transmitters 830 and / or receivers 835 into a single chip. In such embodiments, transmitters 830 and receivers 835 may be logically configured as transceivers 825 using a plurality of common control signals or as modular transmitters 830 and receivers 835 implemented in the same hardware chip or multi-chip module.

[0196] Figure 9 A network device 900, according to embodiments of the present disclosure, can be used to indicate a repetition scheme for a set of scheduled TBs. In one embodiment, the network device 900 may be an implementation of a RAN node, such as base station unit 121, RAN node 210, or gNB as described above. Furthermore, the base station network device 900 may include a processor 905, a memory 910, an input device 915, an output device 920, and a transceiver 925.

[0197] In some embodiments, input device 915 and output device 920 are combined into a single device, such as a touchscreen. In some embodiments, network device 900 may not include any input device 915 and / or output device 920. In various embodiments, network device 900 may include one or more of the following: processor 905, memory 910, and transceiver 925, and may not include input device 915 and / or output device 920.

[0198] As depicted, transceiver 925 includes at least one transmitter 930 and at least one receiver 935. Here, transceiver 925 communicates with one or more remote units 95. Additionally, transceiver 925 may support at least one network interface 940 and / or application interface 945. The application interfaces 945 may support one or more APIs. The network interfaces 940 may support 3GPP reference points such as Uu, N1, N2, and N3. Other network interfaces 940 may be supported, as will be understood by those skilled in the art.

[0199] In one embodiment, processor 905 may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, processor 905 may be a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, or similar programmable controller. In some embodiments, processor 905 executes instructions stored in memory 910 to perform the methods and routines described herein. Processor 905 is communicatively coupled to memory 910, input device 915, output device 920, and transceiver 925.

[0200] In various embodiments, network device 900 is a RAN node (e.g., gNB) communicating with one or more UEs, as described herein. In such embodiments, processor 905 controls network device 900 to perform the RAN behaviors described above. When operating as a RAN node, processor 905 may include an application processor (also referred to as a "main processor") that manages application domain and operating system ("OS") functions, and a baseband processor (also referred to as a "baseband radio processor") that manages radio functions.

[0201] In various embodiments, processor 905 controls network device 900 to implement the RAN behavior described above. For example, processor 905 may determine scheduling information for transmitting a set of one or more TBs through multiple transmission occasions (e.g., time slots) and determine repetition information for time-domain repetition of the set of scheduled TBs. Transmitting via transceiver 925, processor 905 transmits control signaling (e.g., DCI, CG, etc.) containing configuration and / or indications of, for example, scheduling information and repetition information, and receives a set of TBs based on the scheduling information and repetition information, wherein time-domain repetition is applied to the set of TBs based on the time-domain resources allocated to each TB (e.g., based on time slot index, start symbol, and duration).

[0202] In some embodiments, the set of TBs comprises a single TB scheduled across multiple transport instances. In other embodiments, the set of TBs comprises multiple TBs. In some embodiments, duplication information is configured semi-statically using higher-layer signaling (e.g., RRC signaling and / or MAC CE), wherein the duplication information includes at least one duplication factor.

[0203] In some embodiments, the set of TBs received according to scheduling information and repetition information includes a first instance of each TB in the set of TBs received before a second instance (i.e., a repetition) of any TB in the set of TBs received. In other embodiments, the set of TBs received according to scheduling information and repetition information includes all repetitions of the first TB in the set of TBs received before a second (i.e., the next) TB in the set of TBs received.

[0204] In some embodiments, control signaling includes a Time Domain Resource Allocation (“TDRA”) table. In such embodiments, scheduling information for a set of TBs may include multiple start and length indicator values ​​(“SLIV”) in rows of the TDRA table, with the multiple SLIVs corresponding to a set of TBs. In some embodiments, repetition information includes at least one repetition factor dynamically indicated within rows of the TDRA table.

[0205] In some embodiments, the rows of the TDRA table contain the mapping type for each SLIV. In one embodiment, when the corresponding mapping type is a first type (i.e., repetition type A), the actual length of the repetition must follow the length value indicated in the SLIV. In another embodiment, when the corresponding mapping type is a second type (i.e., repetition type B), the actual length of the repetition may differ from the length value indicated in the SLIV.

[0206] In some embodiments, control signaling includes downlink control information (“DCI”), wherein the DCI further includes a new data indicator (“NDI”) value for each TB in the set of TBs. In such an embodiment, the UE applies time-domain repetition to the set of TBs based on the NDI corresponding to each TB, wherein repetition of a particular TB is not scheduled across multiple time slots when the NDI of a particular TB indicates a retransmission.

[0207] In some embodiments, the UE applies time-domain repetition to the set of TBs based on the service priority level corresponding to each TB. In some embodiments, when the service priority level of a particular TB is below a threshold level, repetition of that particular TB is not scheduled in multiple time slots.

[0208] In some embodiments, different repetition factors are associated with different business priority levels corresponding to a set of TBs. In some embodiments, a first TB with a higher priority has a higher repetition factor than a second TB with a lower priority.

[0209] In some embodiments, the control signaling further includes a priority indication for each TB in the set of TBs. In some embodiments, the UE applies time-domain repetition to the set of TBs based on the service priority level corresponding to the indication for each TB.

[0210] In one embodiment, memory 910 is a computer-readable storage medium. In some embodiments, memory 910 includes volatile computer storage media. For example, memory 910 may include RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”). In some embodiments, memory 910 includes non-volatile computer storage media. For example, memory 910 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 910 includes both volatile and non-volatile computer storage media.

[0211] In some embodiments, memory 910 stores data relating to a repetition scheme indicating a set of TBs for scheduling. For example, memory 910 may store parameters, configurations, resource assignments, policies, etc., as described above. In some embodiments, memory 910 also stores program code and related data, such as an operating system or other controller algorithms operating on device 900.

[0212] In one embodiment, input device 915 may include any known computer input device, including a touch panel, buttons, keyboard, stylus, microphone, etc. In some embodiments, input device 915 may be integrated with output device 920, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, input device 915 includes a touchscreen, allowing text to be entered using a virtual keyboard displayed on the touchscreen and / or by handwriting on the touchscreen. In some embodiments, input device 915 includes two or more different devices, such as a keyboard and a touch panel.

[0213] In one embodiment, output device 920 is designed to output visual, auditory, and / or tactile signals. In some embodiments, output device 920 includes an electronically controllable display or display device capable of outputting visual data to a user. For example, output device 920 may include, but is not limited to, LCD displays, LED displays, OLED displays, projectors, or similar display devices capable of outputting images, text, etc., to a user. As another non-limiting example, output device 920 may include a wearable display, such as a smartwatch, smart glasses, head-up display, etc., separate from but communicatively coupled to the rest of network device 900. Furthermore, output device 920 may be a component of a smartphone, personal digital assistant, television, desktop computer, laptop computer, personal computer, vehicle dashboard, etc.

[0214] In some embodiments, the output device 920 includes one or more speakers for generating sound. For example, the output device 920 may generate an auditory alarm or notification (e.g., a buzzer or ring). In some embodiments, the output device 920 includes one or more haptic devices for generating vibration, motion, or other haptic feedback. In some embodiments, all or part of the output device 920 may be integrated with the input device 915. For example, the input device 915 and the output device 920 may form a touchscreen or similar touch-sensitive display. In other embodiments, the output device 920 may be located near the input device 915.

[0215] Transceiver 925 includes at least a transmitter 930 and at least one receiver 935. As described herein, one or more transmitters 930 can be used to communicate with a UE. Similarly, as described herein, one or more receivers 935 can be used to communicate with network functions in a PLMN and / or RAN. Although only one transmitter 930 and one receiver 935 are illustrated, network device 900 can have any suitable number of transmitters 930 and receivers 935. Furthermore, the transmitter(s) 930 and receiver(s) 935 can be of any suitable type of transmitter and receiver.

[0216] Figure 10 An embodiment of a method 1000 for indicating a repetition scheme for a set of scheduling TBs is described according to embodiments of the present disclosure. In various embodiments, method 1000 is performed by a user equipment device in a mobile communication network, such as remote unit 105, UE 205, and / or user equipment device 800 described above. In some embodiments, method 1000 is performed by a processor such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0217] Method 1000 begins and receives 1005 control signaling (e.g., DCI, configured permission, etc.) containing scheduling information for transmitting a set of one or more TBs across multiple transmission occasions (e.g., time slots). Method 1000 includes receiving 1010 time-domain repetition information for scheduling the set of TBs. Method 1000 includes determining 1015 whether to apply time-domain repetition based on the time-domain resources allocated to each TB on a per-TB basis (i.e., for each TB in the set of TBs). Method 1000 includes transmitting 1020 sets of TBs according to the scheduling information and the repetition information. Method 1000 ends.

[0218] Figure 11An embodiment of a method 1100 for indicating a repetition scheme for a set of scheduled TBs is described according to embodiments of the present disclosure. In various embodiments, method 1100 is performed by a base station in a radio access network, such as base station unit 121, RAN node 210, and / or network device 900 described above. In some embodiments, method 1100 is performed by a processor, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0219] Method 1100 begins and determines 1105 scheduling information for transmitting a set of one or more TBs across multiple transmission scenarios (e.g., time slots). Method 1100 includes determining 1110 time-domain repetition information for scheduling the set of TBs. Method 1100 includes transmitting 1115 control signaling (e.g., DCI, configured authorization, etc.) to the UE, the control signaling containing the scheduling information and the repetition information. Method 1100 includes receiving 1120 sets of TBs from the UE based on the scheduling information and the repetition information, wherein time-domain repetition is applied to the set of TBs based on time-domain resources allocated to each TB. Method 1100 ends.

[0220] According to embodiments of this disclosure, a first apparatus for indicating a repetition scheme for a set of scheduled TBs is disclosed herein. The first apparatus may be implemented by a user equipment apparatus in a mobile communication network, such as the remote unit 105, UE 205, and / or user equipment apparatus 800 described above. The first apparatus includes a receiver that receives control signaling (e.g., DCI, CG, etc.) containing scheduling information (i.e., configuration and / or indication) for transmitting a set of one or more TBs over multiple transmission occasions (e.g., time slots), and receives repetition information (i.e., configuration and / or indication) for time-domain repetition of the set of scheduled TBs. The first apparatus includes a processor that determines, for each TB in the set of TBs, whether to apply time-domain repetition based on time-domain resources allocated for each TB (e.g., based on time slot index, start symbol, and duration), and controls a transmitter to transmit the set of TBs according to the scheduling information and the repetition information.

[0221] In some embodiments, the set of TBs comprises a single TB scheduled across multiple transport scenarios. In other embodiments, the set of TBs comprises multiple TBs. In some embodiments, duplication information is configured semi-statically using higher-layer signaling (e.g., RRC signaling), wherein the duplication information includes at least one duplication factor.

[0222] In some embodiments, the set of TBs transmitted according to scheduling and repetition information includes a first instance of each TB in the set of TBs transmitted prior to a second instance of any TB (i.e., a repetition) in the set of TBs transmitted. In other embodiments, the set of TBs transmitted according to scheduling and repetition information includes all repetitions of the first TB in the set of TBs transmitted prior to the second (i.e., the next) TB in the set of TBs transmitted.

[0223] In some embodiments, control signaling includes a Time Domain Resource Allocation (“TDRA”) table. In such embodiments, scheduling information for a set of TBs may include multiple start and length indicator values ​​(“SLIV”) in rows of the TDRA table, with the multiple SLIVs corresponding to a set of TBs. In some embodiments, repetition information includes at least one repetition factor dynamically indicated within rows of the TDRA table.

[0224] In some embodiments, the rows of the TDRA table contain the mapping type for each SLIV. In one embodiment, when the corresponding mapping type is a first type (i.e., repetition type A), the actual length of the repetition must follow the length value indicated in the SLIV. In another embodiment, when the corresponding mapping type is a second type (i.e., repetition type B), the actual length of the repetition is allowed to differ from the length value indicated in the SLIV.

[0225] In some embodiments, control signaling includes downlink control information (“DCI”), wherein the DCI further includes a new data indicator (“NDI”) value for each TB in the set of TBs. In such embodiments, determining whether to apply time-domain repetition is further based on the NDI corresponding to each TB, wherein repetition of a particular TB is not scheduled across multiple time slots when the NDI of a particular TB indicates retransmission.

[0226] In some embodiments, determining whether to apply time-domain repetition is further based on the service priority level corresponding to each TB. In some embodiments, when the service priority level of a particular TB is below a threshold level, repetition of that particular TB is not scheduled across multiple time slots.

[0227] In some embodiments, different repetition factors are associated with different business priority levels corresponding to a set of TBs. In some embodiments, a first TB with a higher priority has a higher repetition factor than a second TB with a lower priority.

[0228] In some embodiments, the control signaling further includes a priority indication for each TB in the set of TBs. In such embodiments, determining whether to apply time-domain repetition can be based on the service priority level corresponding to the indication for each TB.

[0229] According to embodiments of this disclosure, a first method for indicating a repetition scheme for a scheduled set of TBs is disclosed herein. The first method can be performed by a user equipment device in a mobile communication network, such as remote unit 105, UE 205, and / or user equipment device 800 described above. The first method includes receiving control signaling (e.g., DCI, CG, etc.) containing scheduling information (e.g., configuration and / or indication) for transmitting a set of one or more TBs over multiple transmission occasions (e.g., time slots). The first method includes receiving repetition information (e.g., configuration and / or indication) for time-domain repetition of the set of TBs, and determining for each TB in the set whether to apply time-domain repetition based on time-domain resources allocated for each TB (e.g., based on time slot index, start symbol, and duration). The first method includes transmitting the set of TBs according to the scheduling information and the repetition information.

[0230] In some embodiments, the set of TBs comprises a single TB scheduled across multiple transport scenarios. In other embodiments, the set of TBs comprises multiple TBs. In some embodiments, duplication information is configured semi-statically using higher-layer signaling (e.g., RRC signaling), wherein the duplication information includes at least one duplication factor.

[0231] In some embodiments, the set of TBs transmitted according to scheduling and repetition information includes a first instance of each TB in the set of TBs transmitted prior to a second instance of any TB (i.e., a repetition) in the set of TBs transmitted. In other embodiments, the set of TBs transmitted according to scheduling and repetition information includes all repetitions of the first TB in the set of TBs transmitted prior to the second (i.e., the next) TB in the set of TBs transmitted.

[0232] In some embodiments, control signaling includes a Time Domain Resource Allocation (“TDRA”) table. In such embodiments, scheduling information for a set of TBs may include multiple start and length indicator values ​​(“SLIV”) in rows of the TDRA table, with the multiple SLIVs corresponding to a set of TBs. In some embodiments, repetition information includes at least one repetition factor dynamically indicated within rows of the TDRA table.

[0233] In some embodiments, the rows of the TDRA table contain the mapping type for each SLIV. In one embodiment, when the corresponding mapping type is a first type (i.e., repetition type A), the actual length of the repetition must follow the length value indicated in the SLIV. In another embodiment, when the corresponding mapping type is a second type (i.e., repetition type B), the actual length of the repetition is allowed to differ from the length value indicated in the SLIV.

[0234] In some embodiments, control signaling includes downlink control information (“DCI”), wherein the DCI further includes a new data indicator (“NDI”) value for each TB in the set of TBs. In such embodiments, determining whether to apply time-domain repetition is further based on the NDI corresponding to each TB, wherein repetition of a particular TB is not scheduled across multiple time slots when the NDI of a particular TB indicates retransmission.

[0235] In some embodiments, determining whether to apply time-domain repetition is further based on the service priority level corresponding to each TB. In some embodiments, when the service priority level of a particular TB is below a threshold level, repetition of that particular TB is not scheduled across multiple time slots.

[0236] In some embodiments, different repetition factors are associated with different business priority levels corresponding to a set of TBs. In some embodiments, a first TB with a higher priority has a higher repetition factor than a second TB with a lower priority.

[0237] In some embodiments, the control signaling further includes a priority indication for each TB in the set of TBs. In some embodiments, determining whether to apply time-domain repetition is further based on the service priority level corresponding to the indication for each TB.

[0238] According to embodiments of this disclosure, a second means for indicating a repetition scheme for a scheduled set of TBs is disclosed herein. The second means may be implemented by a base station in a radio access network, such as base station unit 121, gNB 210, and / or network device 900 described above. The second means includes a processor that determines scheduling information for transmitting a set of one or more TBs through multiple transmission occasions (e.g., time slots) and determines repetition information for time-domain repetition of the set of scheduled TBs. The second means includes a transceiver that transmits control signaling (e.g., DCI, CG, etc.) containing configuration and / or indications such as scheduling information and repetition information, and receives a set of TBs according to the scheduling information and repetition information, wherein time-domain repetition is applied to the set of TBs based on time-domain resources allocated to each TB (e.g., based on time slot index, start symbol, and duration).

[0239] In some embodiments, the set of TBs comprises a single TB scheduled across multiple transport scenarios. In other embodiments, the set of TBs comprises multiple TBs. In some embodiments, duplication information is configured semi-statically using higher-layer signaling (e.g., RRC signaling), wherein the duplication information includes at least one duplication factor.

[0240] In some embodiments, the set of TBs received according to scheduling information and repetition information includes a first instance of each TB in the set of TBs received before a second instance (i.e., a repetition) of any TB in the set of TBs received. In other embodiments, the set of TBs received according to scheduling information and repetition information includes all repetitions of the first TB in the set of TBs received before a second (i.e., the next) TB in the set of TBs received.

[0241] In some embodiments, control signaling includes a Time Domain Resource Allocation (“TDRA”) table. In such embodiments, scheduling information for a set of TBs may include multiple start and length indicator values ​​(“SLIV”) in rows of the TDRA table, with the multiple SLIVs corresponding to a set of TBs. In some embodiments, repetition information includes at least one repetition factor dynamically indicated within rows of the TDRA table.

[0242] In some embodiments, the rows of the TDRA table contain the mapping type for each SLIV. In one embodiment, when the corresponding mapping type is a first type (i.e., repetition type A), the actual length of the repetition must follow the length value indicated in the SLIV. In another embodiment, when the corresponding mapping type is a second type (i.e., repetition type B), the actual length of the repetition is allowed to differ from the length value indicated in the SLIV.

[0243] In some embodiments, control signaling includes downlink control information (“DCI”), wherein the DCI further includes a new data indicator (“NDI”) value for each TB in the set of TBs. In such an embodiment, the UE applies time-domain repetition to the set of TBs based on the NDI corresponding to each TB, wherein repetition of a particular TB is not scheduled across multiple time slots when the NDI of a particular TB indicates a retransmission.

[0244] In some embodiments, the UE applies time-domain repetition to a set of TBs based on the service priority level corresponding to each TB. In some embodiments, when the service priority level of a particular TB is below a threshold level, repetition of that particular TB is not scheduled in multiple time slots.

[0245] In some embodiments, different repetition factors are associated with different business priorities corresponding to a set of TBs. In some embodiments, a first TB with a higher priority has a higher repetition factor than a second TB with a lower priority.

[0246] In some embodiments, the control signaling further includes a priority indication for each TB in the set of TBs. In some embodiments, the UE applies time-domain repetition to the set of TBs based on the service priority level corresponding to the indication for each TB.

[0247] According to embodiments of this disclosure, a second method is disclosed herein for indicating a repetition scheme for a set of scheduled TBs. The second method can be performed by a base station in a radio access network, such as base station unit 121, gNB 210, and / or network device 900 described above. The second method includes determining scheduling information for transmitting a set of one or more TBs through multiple transmission occasions (e.g., time slots). The second method includes determining repetition information for time-domain repetition of the set of scheduled TBs. The second method includes transmitting control signaling (e.g., DCI, CG, etc.) to a UE containing configuration and / or indications such as scheduling information and repetition information, and receiving a set of TBs from the UE based on the scheduling information and repetition information, wherein time-domain repetition is applied to the set of TBs based on time-domain resources allocated for each TB (e.g., based on time slot index, start symbol, and duration).

[0248] In some embodiments, the set of TBs comprises a single TB scheduled across multiple transport scenarios. In other embodiments, the set of TBs comprises multiple TBs. In some embodiments, duplication information is configured semi-statically using higher-layer signaling (e.g., RRC signaling), wherein the duplication information includes at least one duplication factor.

[0249] In some embodiments, the set of TBs received according to scheduling information and repetition information includes a first instance of each TB in the set of TBs received before a second instance (i.e., a repetition) of any TB in the set of TBs received. In other embodiments, the set of TBs received according to scheduling information and repetition information includes all repetitions of the first TB in the set of TBs received before a second (i.e., the next) TB in the set of TBs received.

[0250] In some embodiments, control signaling includes a Time Domain Resource Allocation (“TDRA”) table. In such embodiments, scheduling information for a set of TBs may include multiple start and length indicator values ​​(“SLIV”) in rows of the TDRA table, with the multiple SLIVs corresponding to a set of TBs. In some embodiments, repetition information includes at least one repetition factor dynamically indicated within rows of the TDRA table.

[0251] In some embodiments, the rows of the TDRA table contain a mapping type for each SLIV, wherein when the corresponding mapping type is a first type (i.e., repetition type A), the actual length of the repetition must follow the length value indicated in the SLIV, and wherein when the corresponding mapping type is a second type (i.e., repetition type B), the actual length of the repetition is allowed to differ from the length value indicated in the SLIV.

[0252] In some embodiments, control signaling includes downlink control information (“DCI”), wherein the DCI further includes a new data indicator (“NDI”) value for each TB in the set of TBs. In such an embodiment, the UE applies time-domain repetition to the set of TBs based on the NDI corresponding to each TB, wherein repetition of a particular TB is not scheduled across multiple time slots when the NDI of a particular TB indicates a retransmission.

[0253] In some embodiments, the UE applies time-domain repetition to a set of TBs based on the service priority level corresponding to each TB. In some embodiments, when the service priority level of a particular TB is below a threshold level, repetition of that particular TB is not scheduled in multiple time slots.

[0254] In some embodiments, different repetition factors are associated with different business priorities corresponding to a set of TBs. In some embodiments, a first TB with a higher priority has a higher repetition factor than a second TB with a lower priority.

[0255] In some embodiments, the control signaling further includes a priority indication for each TB in the set of TBs. In some embodiments, the UE applies time-domain repetition to the set of TBs based on the service priority level corresponding to the indication for each TB.

[0256] The embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects as illustrative rather than restrictive. Therefore, the scope of the invention is indicated by the appended claims rather than by the foregoing description. All variations within the equivalent meaning and scope of the claims should be covered within their scope.

Claims

1. A method performed by a user equipment (UE), the method comprising: Receive control signaling containing scheduling information for transmitting a set of transport blocks (TBs) through multiple transport scenarios; Receive the time-domain repetition information of the set of scheduled TBs; For each TB in the set of TBs, it is determined whether to apply the time-domain repetition based on the time-domain resources allocated to each TB; as well as The set of TBs is transmitted according to the scheduling information and the duplication information. The set of TBs that are launched according to the scheduling information and the duplication information includes all duplications of the first TB in the set of TBs launched before the second TB in the set of TBs launched.

2. The method according to claim 1, wherein, The set of TBs includes a single TB scheduled through the multiple transmission scenarios.

3. The method according to claim 1, wherein, The duplication information includes a duplication factor that is semi-statically configured by higher-level signaling.

4. The method according to claim 1, wherein, The control signaling includes a Time Domain Resource Allocation (TDRA) table, wherein the scheduling information for the set of TBs includes multiple start and length indicator values ​​(SLIVs) in rows of the TDRA table, the multiple SLIVs corresponding to the set of TBs.

5. The method according to claim 4, wherein, The repetition information includes a repetition factor dynamically indicated within the rows of the TDRA table.

6. The method according to claim 4, wherein, The rows of the TDRA table include a mapping type for each SLIV, wherein when the corresponding mapping type is a first type, the actual length of the repeat follows the length value indicated in the SLIV, and wherein when the corresponding mapping type is a second type, the actual length of the repeat is different from the length value indicated in the SLIV.

7. The method according to claim 1, wherein, The control signaling includes downlink control information (DCI), wherein the DCI further includes a new data indicator (NDI) value for each TB in the set of TBs, wherein determining whether to apply the time-domain repetition is further based on the NDI corresponding to each TB, wherein when the NDI of a particular TB indicates a retransmission, repetition of the particular TB is not scheduled within the plurality of time slots.

8. The method according to claim 1, wherein, Whether to apply the time-domain repetition is further based on the service priority level corresponding to each TB, wherein when the service priority level of a particular TB is below a threshold level, repetition of the particular TB is not scheduled in the plurality of time slots.

9. The method according to claim 1, wherein, Different repetition factors are associated with different business priority levels corresponding to the set of TBs, wherein a first TB with a higher priority level has a higher repetition factor than a second TB with a lower priority level.

10. The method according to claim 1, wherein, The control signaling further includes a priority indication for each TB in the set of TBs, wherein determining whether to apply the time-domain repetition is further based on the service priority level corresponding to the indication for each TB.

11. A user equipment (UE) apparatus in a mobile communication network, the apparatus comprising: Receiver, the receiver: Receive control signaling containing scheduling information for transmitting a set of transport blocks (TBs) through multiple transport scenarios; Receive the temporal repetition information of the set of scheduled TBs; A processor that determines, for each TB in the set of TBs, whether to apply the time-domain repetition based on the time-domain resources allocated to each TB; as well as A transmitter that transmits the set of TBs according to the scheduling information and the repetition information, wherein the transmitter transmits all repetitions of the first TB in the set of TBs before transmitting the second TB in the set of TBs.

12. A method performed by a radio access network (RAN) node, the method comprising: Determine the scheduling information for a set of transport blocks to be transmitted through multiple transport scenarios; Determine the temporal repetition information of the set of scheduled TBs; A control signaling message is transmitted to the user equipment (UE), the control signaling message including the scheduling information and the duplication information; as well as The set of time-domain repetitions is received from the UE based on the scheduling information and the repetition information, wherein the time-domain repetitions are applied to the set of time-domain repetitions based on the time-domain resources allocated to each time-domain repetition. The set of TBs received according to the scheduling information and the repetition information includes all repetitions of the first TB in the set of TBs received before the second TB in the set of TBs received.

13. The method according to claim 12, wherein, The set of TBs includes a single TB scheduled through the multiple transmission scenarios.

14. The method according to claim 12, wherein, The control signaling includes a Time Domain Resource Allocation (TDRA) table, wherein the scheduling information for the set of TBs includes multiple start and length indicator values ​​(SLIVs) in rows of the TDRA table, the multiple SLIVs corresponding to the set of TBs, wherein the repetition information includes a repetition factor dynamically indicated within rows of the TDRA table.

15. The method according to claim 12, wherein, The control signaling includes downlink control information (DCI), wherein the DCI further includes a new data indicator (NDI) value for each TB in the set of TBs, wherein the UE applies time-domain repetition to the set of TBs based on the NDI corresponding to each TB, wherein when the NDI of a particular TB indicates a retransmission, repetition of the particular TB is not scheduled within the plurality of time slots.

16. A radio access network (RAN) apparatus in a mobile communication network, the apparatus comprising: Processor, the processor: Determine the scheduling information for the set of transport blocks (TBs) to be transmitted through multiple transport scenarios; and Determine the temporal repetition information of the set of scheduled TBs; and Transceiver, the transceiver: The system transmits control signaling to the user equipment (UE), the control signaling including the scheduling information and the duplication information; and The set of TBs is received according to the scheduling information and the repetition information, wherein the time-domain repetition is applied to the set of TBs based on the time-domain resources allocated to each TB. The transceiver receives all repetitions of the first TB in the set of TBs before receiving the second TB in the set of TBs.

Images