Multiple tti pusch transmissions in a wireless communication system

Abstract

This disclosure relates to multiple TTI PUSCH transmissions in a wireless communication system. Apparatuses, systems, and methods are disclosed for a user equipment device (UE) to perform multiple TTI PUSCH transmissions and code block group (CBG) based retransmission operations in a wireless communication system. The UE can perform radio resource control (RRC) signaling with a network entity to configure a data structure that can include one or more sets of physical uplink shared channel (PUSCH) transmission configurations, where each set of PUSCH transmission configurations spans multiple TTIs. The wireless device can be configured to receive a downlink control information (DCI) message from the network entity, the DCI message can include a time domain resource allocation (TDRA) field, the TDRA can indicate a set of PUSCH transmission configurations included in the data structure. The wireless device can perform PUSCH transmissions spanning multiple TTIs in accordance with the indicated set of PUSCH transmission configurations on an unlicensed band.

Description

[0001] Priority Data

[0002] This patent application claims priority benefit of U.S. Provisional Patent Application Serial No. 62 / 886,902, entitled “Multiple TTI PUSCH Transmissions in a Wireless Communication System” and filed on August 14, 2019, which is hereby incorporated by reference in its entirety as if fully set forth herein. TECHNICAL FIELD

[0003] The present application relates to wireless devices, and more specifically, to apparatus, systems, and methods for multiple TTI PUSCH transmissions in a wireless communication system. BACKGROUND

[0004] The use of wireless communication systems is rapidly increasing. In recent years, wireless devices such as smart phones and tablet computers have become increasingly sophisticated. In addition to supporting telephone calls, many mobile devices now also provide access to the Internet, email, text messaging, and navigation using the global positioning system (GPS), and are capable of operating sophisticated, complex applications that utilize these functions.

[0005] Long Term Evolution (LTE) has become the technology of choice for most wireless network operators worldwide, offering mobile broadband data and high-speed Internet access to their user base. LTE defines a number of downlink (DL) physical channels, classified as transport or control channels, to carry information blocks received from the medium access control (MAC) and higher layers. LTE also defines the number of physical layer channels for the uplink (UL).

[0006] For example, LTE defines the physical downlink shared channel (PDSCH) as a DL transport channel. The PDSCH is the main data carrying channel allocated to users on a dynamic and opportunistic basis. The PDSCH carries data in transport blocks (TBs) corresponding to MAC protocol data units (PDUs) that are passed from the MAC layer to the physical (PHY) layer once per transmission time interval (TTI). The PDSCH is also used to transmit broadcast information such as system information blocks (SIBs) and paging messages.

[0007] For example, LTE defines a physical downlink control channel (PDCCH) as a DL control channel that carries resource assignments for UEs contained in a downlink control information (DCI) message. Multiple PDCCHs can be transmitted in the same subframe using control channel elements (CCEs), each of which is nine groups of four resource elements known as resource element groups (REGs). The PDCCH employs quadrature phase shift keying (QPSK) modulation, with four QPSK symbols mapped to each REG. In addition, 1, 2, 4, or 8 CCEs can be used depending on channel conditions to ensure sufficient robustness.

[0008] In addition, LTE defines a physical uplink shared channel (PUSCH) as an UL channel shared by all devices (user equipment, UEs) in a radio cell to transmit user data to the network. Scheduling of all UEs is under the control of the LTE base station (enhanced Node B or eNB). The eNB informs the UE of resource block (RB) allocation, as well as the modulation and coding scheme to use, using an uplink scheduling grant (DCI format 0). PUSCH typically supports QPSK and quadrature amplitude modulation (QAM). In addition to user data, the PUSCH carries any control information necessary for decoding the information, such as a transport format indicator and multiple-input multiple-output (MIMO) parameters. Control data is multiplexed with information data prior to digital Fourier transform (DFT) spreading.

[0009] The next telecommunication standard beyond the current International Mobile Telecommunications Advanced (IMT-Advanced) standard is referred to as the 5th Generation Mobile Networks or 5th Generation Wireless Systems, or simply 5G (also referred to as 5G New Radio, also simply NR, for 5G-NR). In comparison to the current LTE standard, 5G-NR proposes higher capacity for higher density of mobile broadband users, while supporting device-to-device, ultra-reliable, and massive machine communications, as well as lower latency and lower battery consumption. In addition, the 5G-NR standard can allow less restrictive UE scheduling in comparison to the current LTE standard. Therefore, efforts are being made to utilize higher throughput possible at higher frequencies in the ongoing development of 5G-NR. SUMMARY

[0010] Embodiments relate to apparatus, systems, and methods for multiple TTI PUSCH transmissions in a wireless communication system.

[0011] In some embodiments, a wireless device, e.g., such as a user equipment device (UE), can be configured to perform radio resource control (RRC) signaling with a network entity to configure a data structure that can include one or more sets of physical uplink shared channel (PUSCH) transmission configurations, where each set of PUSCH transmission configurations spans a single or multiple transmission time intervals (TTIs). The wireless device can be configured to receive, from the network entity, a downlink control information (DCI) message that can include a time domain resource allocation field (TDRA) that can indicate a set of PUSCH transmission configurations included in the data structure. The wireless device can perform a PUSCH transmission spanning a single or multiple TTIs in accordance with the indicated set of PUSCH transmission configurations on an unlicensed band. In some embodiments, each set of PUSCH transmission configurations can include one or more PUSCH transmission configurations. In some embodiments, each PUSCH transmission configuration within a set of PUSCH transmission configurations can include at least one of a start and length indicator value (SLIV), a PUSCH mapping type to apply, and / or a slot offset K2 value.

[0012] In some embodiments, a wireless device, e.g., such as a user equipment device (UE), can be configured to perform radio resource control (RRC) signaling with a network entity to configure a data structure that can include one or more sets of physical uplink shared channel (PUSCH) transmission configurations, where each set of PUSCH transmission configurations spans a single or multiple transmission time intervals (TTIs). The wireless device can be configured to receive, from the network entity, a downlink control information (DCI) message that can include a time domain resource allocation field (TDRA) that can indicate a set of PUSCH transmission configurations included in the data structure. The wireless device can perform a PUSCH transmission spanning a single or multiple TTIs in accordance with the indicated set of PUSCH transmission configurations on an unlicensed band. In some embodiments, each set of PUSCH transmission configurations can include one or more PUSCH transmission configurations. In some embodiments, each PUSCH transmission configuration within a set of PUSCH transmission configurations can include at least one of a start and length indicator value (SLIV), a PUSCH mapping type to apply, and / or a slot offset K2 value.

[0013] The techniques described herein can be implemented in and / or used with a number of different types of devices, including but not limited to cellular phones, tablet computers, wearable computing devices, portable media players, and any of a variety of other computing devices.

[0014] This summary is intended to provide a brief overview of some of the subject matter described in this document. Accordingly, it will be appreciated that the above-described features are merely examples and should not be construed to narrow the scope or spirit of the subject matter described in this disclosure. Other features, aspects, and advantages of the subject matter described herein will become apparent from the following DETAILED DESCRIPTION, Figures, and Claims. BRIEF DESCRIPTION OF DRAWINGS

[0015] A better understanding of the subject can be obtained when the following detailed description of the various embodiments is considered in conjunction with the following drawings, in which:

[0016] FIG. 1A An exemplary wireless communication system is shown in accordance with some embodiments.

[0017] FIG. 1B An example of a base station (BS) and access point in communication with a user equipment (UE) device is shown in accordance with some embodiments.

[0018] FIG. 2 An exemplary simplified block diagram of a WLAN access point (AP) is shown in accordance with some embodiments.

[0019] FIG. 3 An example block diagram of a UE is shown in accordance with some embodiments.

[0020] FIG. 4 An example block diagram of a BS is shown in accordance with some embodiments.

[0021] FIG. 5 An example block diagram of cellular communication circuitry is shown in accordance with some embodiments.

[0022] FIG. 6A An example of connections between an EPC network, an LTE base station (eNB), and a 5G NR base station (gNB) is shown.

[0023] FIG. 6B An example of protocol stacks for eNBs and gNBs is shown.

[0024] FIG. 7A An example of a 5G network architecture is shown in accordance with some embodiments, which combines 3GPP (e.g., cellular) and non-3GPP (e.g., non-cellular) access in the 5G CN.

[0025] FIG. 7B An example of a 5G network architecture is shown in accordance with some embodiments, which combines dual 3GPP (e.g., LTE and 5G NR) access as well as non-3GPP access in the 5G CN.

[0026] FIG. 8 An example of a baseband processor architecture for a UE is shown in accordance with some embodiments.

[0027] FIG. 9A An example of an RRC configuration table for multi-slot PUSCH time domain resource allocation is shown in accordance with some embodiments.

[0028] FIG. 9B-C An example slot allocation for a table in accordance with some embodiments is shown. FIG. 9A ​

[0029] FIG. 10A-B An ASN.1 syntax for defining data structures is shown in accordance with some embodiments.

[0030] FIG. 11 A block diagram showing an example of a method for scheduling a user equipment device (UE) to transmit on multiple transmission time intervals (TTIs) using an unlicensed band in accordance with some embodiments is shown.

[0031] FIG. 12 An example of CBG-based retransmission for multi-slot / min-slot PUSCH scheduling in accordance with some embodiments is shown.

[0032] FIG. 13A-B An example of a starting PUSCH index S and corresponding transmissions in accordance with some embodiments is shown.

[0033] FIG. 14 A block diagram showing an example of a method for code block group (CBG)-based retransmission operation for multi-slot / min-slot PUSCH scheduling in accordance with some embodiments is shown.

[0034] While features described herein can be susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and are herein described in detail. It should be understood, however, that the drawings and detailed description thereto are not intended to limit the disclosure to the particular form disclosed but on the contrary, the intention is to cover all modifications, equivalents and alternatives falling within the spirit and scope of the subject matter defined by the appended claims. DETAILED DESCRIPTION

[0035] Terminology

[0036] The following is a glossary of terms used in the disclosure:

[0037] Memory medium—any one of various types of memory devices or storage devices. The term "memory medium" is intended to include a single memory device, such as one of the types listed above, or multiple memory devices. Further, the memory medium can include a computer-readable medium, which can be a non-transitory computer-readable medium (for example, having a structure that is fixed prior to time of access). A non-transitory computer-readable medium is a tangible component or article of manufacture that is not a signal. The term "memory medium" can also include two or more memory devices that can reside in different locations, such as on different computer systems that are connected over a network. Each of the two or more memory devices can have a computer program stored thereon. The term "memory medium" shall therefore include one or more of various types of tangible memory devices or storage devices, such as one or more of volatile memory (for example, DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.), non-volatile memory (for example, ROM, EEPROM, flash memory, etc.), or any other type of memory device or storage device. The term "memory medium" shall also include any types of tangible storage that can store programming code or instructions without

[0038] Carrier medium—memory medium as described above, as well as a physical transmission medium such as a bus, network, and / or other physical transmission medium that can carry signals such as electrical, electromagnetic, or digital signals.

[0039] Programmable hardware element—includes various hardware devices comprising multiple programmable function blocks connected via a programmable interconnect. Examples

[0040] Computer system—any of various types of computing or processing systems, including a personal computer system (PC), mainframe computer system, workstation, network appliance, internet appliance, personal digital assistant (PDA), television system, grid computing system, or other device or combinations of devices. In general, the term "computer system" can be broadly defined to encompass any device (or combination of devices) having at least one processor that executes instructions from a memory medium.

[0041] User equipment (UE) (or "UE device")—any of various types of computer systems devices which are mobile or portable and which performs wireless communications. Examples of UE devices include mobile telephones or smart phones (for example, iPhone TM , Android TMTelephones), portable gaming devices (e.g., Nintendo DS) TM PlayStation Portable TM Gameboy Advance TM iPhone TM ), laptops, wearable devices (e.g., smartwatches, smart glasses), personal digital assistants, portable internet devices, music players, data storage devices, or other handheld devices, etc. Generally speaking, the term "UE" or "UE device" can be broadly defined as any electronic device, computing device, and / or telecommunications device (or combination of devices) that is portable to the user and capable of wireless communication.

[0042] Base station—The term “base station” has the full range of its common meaning and includes at least a wireless communication station that is installed in a fixed location and is used for communication as part of a wireless telephone system or radio system.

[0043] A processing element is a component or combination of components capable of performing the functions of a device such as a user equipment or cellular network device. A processing element may include, for example: a processor and associated memory, portions or circuitry of individual processor cores, an entire processor core, a processor array, circuitry such as an ASIC (Application-Specific Integrated Circuit), programmable hardware components such as a Field-Programmable Gate Array (FPGA), and any combination thereof.

[0044] A channel is a medium used to transmit information from a transmitter to a receiver. It should be noted that because the characteristics of the term "channel" can vary depending on different wireless protocols, the term "channel" as used herein can be considered to be used in a standard manner consistent with the type of device to which the term is referenced. In some standards, the channel width can be variable (e.g., depending on device capabilities, band conditions, etc.). For example, LTE can support scalable channel bandwidths from 1.4 MHz to 20 MHz. In contrast, WLAN channels can be 22 MHz wide, while Bluetooth channels can be 1 MHz wide. Other protocols and standards may include different definitions of channels. Furthermore, some standards may define and use multiple types of channels, such as different channels for uplink or downlink and / or different channels for different purposes such as data, control information, etc.

[0045] Frequency band—The term “frequency band” has the full range of its general meaning and includes at least a segment of spectrum (e.g., radio frequency spectrum) in which a channel is used or reserved for the same purpose.

[0046] Automatic—refers to actions or operations performed by a computer system (e.g., software executed by the computer system) or device (e.g., circuits, programmable hardware elements, ASICs, etc.) without requiring direct user input to specify or perform the actions or operations. Therefore, the term "automatic" contrasts with actions performed or specified manually by the user, where the user provides input to directly perform the action. An automatic process can be initiated by user-provided input, but the subsequent actions performed "automatically" are not specified by the user; that is, they are not performed "manually," where the user specifies each action to be performed. For example, a user filling out a form by selecting each field and providing input specifying information (e.g., by typing information, selecting a checkbox, radio selection, etc.) is considered manually filling out the form, even though the computer system must update the form in response to the user's actions. The form can be automatically filled out by a computer system (e.g., software executed on the computer system) which analyzes the fields of the form and fills it out without any user input specifying answers for the fields. As indicated above, the user can invoke the automatic filling of the form but does not participate in the actual filling of the form (e.g., the user does not manually specify answers for the fields, but they are completed automatically). This manual provides various examples of operations that are automatically performed in response to actions taken by the user.

[0047] Approximately—means a value close to the correct or precise value. For example, approximately can refer to a value within 1% to 10% of the precise (or expected) value. However, it should be noted that the actual threshold (or tolerance) can vary depending on the application. For example, in some implementations, “approximately” may mean within 0.1% of some specified or expected value, while in various other implementations, the threshold may be, for example, 2%, 3%, 5%, etc., depending on the expectations or requirements of the specific application.

[0048] Concurrency refers to the parallel execution or implementation of tasks, processes, or programs in a manner that at least partially overlaps. For example, concurrency can be achieved using “strong” or strict parallelism, where tasks are executed in parallel (at least partially) on corresponding computing elements; or using “weak parallelism,” where tasks are executed in an interleaved manner (e.g., by time multiplexing of execution threads).

[0049] Various components can be described as being "configured" to perform one or more tasks. In such contexts, "configured" is a broad expression generally meaning "having" a "structure" that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when it is not currently performing one (e.g., a set of electrical conductors can be configured to electrically connect one module to another, even when the two modules are not connected). In some contexts, "configured" can be a broad description generally meaning a structure that "has a circuit system that performs one or more tasks during operation." Thus, a component can be configured to perform a task even when it is not currently switched on. Typically, the circuit forming the structure corresponding to "configured" can include hardware circuitry.

[0050] For ease of description, various components may be described as performing one or more tasks. Such descriptions should be interpreted as including the phrase "configured to". Statements describing a component as configured to perform one or more tasks are explicitly intended not to invoke the interpretation of 35 U.S.SC §112(f) for that component.

[0051] FIG. 1A and FIG. 1B - communication system

[0052] FIG. 1A A simplified exemplary wireless communication system according to some implementation schemes is shown. It should be noted that the system of Figure 1 is merely an example of a possible system, and the features of this disclosure can be implemented in any of a variety of systems as needed.

[0053] As shown in the figure, the exemplary wireless communication system includes a base station 102A, which communicates with one or more user equipments 106A, 106B to 106N via a transmission medium. Each user equipment may be referred to herein as a "user equipment" (UE). Therefore, user equipment 106 is referred to as a UE or UE device.

[0054] Base station (BS) 102A may be a transceiver base station (BTS) or a cell site (“cellular base station”), and may include hardware that enables wireless communication with UE 106A to UE 106N.

[0055] The communication area (or coverage area) of a base station can be referred to as a "cell". Base station 102A and UE 106 can be configured to communicate via a transmission medium using any of a variety of Radio Access Technologies (RATs), also known as wireless communication technologies or telecommunications standards, such as GSM, UMTS (associated with air interfaces such as WCDMA or TD-SCDMA), LTE, LTE-Advanced (LTE-A), 5G New Radio (5G NR), HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc. Note that if base station 102A is implemented in an LTE environment, its alternative location can be referred to as an "eNodeB" or "eNB". Note that if base station 102A is implemented in a 5G NR environment, its alternative location can be referred to as a "gNodeB" or "gNB".

[0056] As shown in the figure, base station 102A can also be configured to communicate with network 100 (e.g., in various possibilities, the core network of a cellular service provider, telecommunications networks such as the Public Switched Telephone Network (PSTN), and / or the Internet). Therefore, base station 102A can facilitate communication between user equipments and / or between user equipments and network 100. Specifically, cellular base station 102A can provide UE 106 with various communication capabilities such as voice, SMS, and / or data services.

[0057] Base station 102A and other similar base stations (such as base stations 102B...102N) operating according to the same or different cellular communication standards can therefore be provided as a network of cells that can provide continuous or nearly continuous overlapping services to UE 106A-N and similar devices over a geographical area via one or more cellular communication standards.

[0058] Therefore, although base station 102A can act as the "serving cell" for UEs 106A-N as shown in Figure 1, each UE 106 may also be able to receive signals (and possibly within its communication range) from one or more other cells (which may be provided by base stations 102B-N and / or any other base station), which may be referred to as "neighboring cells". Such cells may also facilitate communication between user equipments and / or between user equipments and network 100. Such cells may include "macro" cells, "micro" cells, "pecimen" cells and / or any other cells of various other granularities providing service area size. For example, base stations 102A-B shown in Figure 1 may be macro cells, while base station 102N may be a pico cell. Other configurations are also possible.

[0059] In some implementations, base station 102A may be a next-generation base station, such as a 5G New Radio (5G NR) base station or a “gNB”. In some implementations, the gNB may be connected to a legacy evolved packet core (EPC) network and / or to a new radio communication core (NRC) network. Furthermore, a gNB cell may include one or more transition and receive points (TRPs). Additionally, a UE capable of operating according to 5G NR may connect to one or more TRPs within one or more gNBs.

[0060] It should be noted that UE106 can communicate using multiple wireless communication standards. For example, in addition to at least one cellular communication protocol (e.g., GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-A, 5G NR, HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD, etc.), UE106 can be configured to communicate using wireless networking (e.g., Wi-Fi) and / or peer-to-peer wireless communication protocols (e.g., Bluetooth, Wi-Fi peer-to-peer, etc.). If desired, UE106 can also or alternatively be configured to communicate using one or more Global Navigation Satellite Systems (GNSS, such as GPS or GLONASS), one or more mobile television broadcasting standards (e.g., ATSC-M / H or DVB-H), and / or any other wireless communication protocol. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.

[0061] FIG. 1B User equipment 106 (e.g., one of devices 106A to 106N) communicating with base station 102 and access point 112 according to some embodiments is shown. UE 106 can be a device with cellular and non-cellular communication capabilities (e.g., Bluetooth, Wi-Fi, etc.), such as a mobile phone, handheld device, computer or tablet, or virtually any type of wireless device.

[0062] UE 106 may include a processor configured to execute program instructions stored in memory. UE 106 may execute any of the method embodiments of the present invention by executing such stored instructions. Alternatively or additionally, UE 106 may include programmable hardware elements, such as a field-programmable gate array (FPGA) configured to execute any of the method embodiments of the present invention or any portion thereof.

[0063] UE 106 may include one or more antennas for communicating using one or more wireless communication protocols or technologies. In some embodiments, UE 106 may be configured to communicate using, for example, CDMA2000 (1xRTT / 1xEV-DO / HRPD / eHRPD), LTE / Advanced LTE, or 5G NR and / or GSM, LTE, Advanced LTE, or 5G NR using a single shared radio component. The shared radio may be coupled to a single antenna or to multiple antennas (e.g., for MIMO) for performing wireless communication. Typically, the radio component may include any combination of baseband processor, analog radio frequency (RF) signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc.) or digital processing circuitry (e.g., for digital modulation and other digital processing). Similarly, the radio component may use the aforementioned hardware to implement one or more receive chains and transmit chains. For example, UE 106 may share one or more portions of the receive chain and / or transmit chain among various wireless communication technologies such as those discussed above.

[0064] In some implementations, UE 106 may include separate transmit and / or receive chains (e.g., including separate antennas and other radio components) for each wireless communication protocol configured to communicate therewith. As another possibility, UE 106 may include one or more radio components shared among multiple wireless communication protocols, as well as one or more radio components used uniquely by a single wireless communication protocol. For example, UE 106 may include shared radio components for communication using either LTE or 5G NR (or LTE or 1xRTT, or LTE or GSM), and separate radio components for communication using each of Wi-Fi and Bluetooth. Other configurations are also possible.

[0065] FIG. 2 Access point block diagram

[0066] FIG. 2 An exemplary block diagram of access point (AP) 112 is shown. Note that... FIG. 2 The block diagram of the AP is only one example of a possible system. As shown, AP 112 may include a processor 204 capable of executing program instructions for AP 112. Processor 204 may also be (directly or indirectly) coupled to memory management unit (MMU) 240 or other circuitry or devices, which may be configured to receive addresses from processor 204 and translate these addresses into locations in memory (e.g., memory 260 and read-only memory (ROM) 250).

[0067] AP 112 may include at least one network port 270. Network port 270 may be configured to couple to a wired network and provide access to the Internet to multiple devices such as UE 106. For example, network port 270 (or additional network ports) may be configured to couple to a local network, such as a home network or a corporate network. For example, port 270 may be an Ethernet port. The local network may provide connectivity to additional networks such as the Internet.

[0068] AP 112 may include at least one antenna 234, which may be configured to function as a wireless transceiver and may be further configured to communicate with UE 106 via wireless communication circuitry 230. Antenna 234 communicates with wireless communication circuitry 230 via communication link 232. Communication link 232 may include one or more receive links, one or more transmit links, or both. Wireless communication circuitry 230 may be configured to communicate via Wi-Fi or WLAN (e.g., 802.11). For example, in the case of a small cell where the AP coexists with a base station, or in other situations where it may be desirable for AP 112 to communicate via various different wireless communication technologies, wireless communication circuitry 230 may also or alternatively be configured to communicate via various other wireless communication technologies, including, but not limited to, 5G NR, LTE, LTE-A Advanced, GSM, WCDMA, CDMA2000, etc.

[0069] In some implementations, as further described below, AP 112 can be configured to perform a method for multiple TTI PUSCH transmissions in a wireless communication system as further described herein.

[0070] FIG. 3 - block diagram of a UE

[0071] FIG. 3 An exemplary simplified block diagram of a communication device 106 according to some embodiments is shown. It should be noted that... FIG. 3 The block diagram of the communication device is merely one example of possible communication devices. According to the implementation, among other devices, the communication device 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet computer, and / or a combination of devices. As shown, the communication device 106 may include a set of components 300 configured to perform core functions. For example, this set of components may be implemented as a system-on-a-chip (SOC), which may include portions for various purposes. Alternatively, the set of components 300 may be implemented as individual components or groups of components for various purposes. This set of components 300 may be (e.g., communicatively; directly or indirectly) coupled to various other circuitry of the communication device 106.

[0072] For example, communication device 106 may include various types of memory (e.g., including NAND flash memory 310), input / output interfaces such as connector I / F 320 (e.g., for connection to a computer system; docking station; charging station; input devices such as microphone, camera, keyboard; output devices such as speaker; etc.), a display 360 that may be integrated with or external to communication device 106, and cellular communication circuitry 330 such as for 5G NR, LTE, GSM, etc., and short- to medium-range wireless communication circuitry 329 (e.g., Bluetooth). TM (and WLAN circuitry). In some embodiments, the communication device 106 may include wired communication circuitry (not shown), such as, for example, a network interface card for Ethernet.

[0073] Cellular communication circuitry 330 may be coupled (e.g., communicatively grounded; directly or indirectly) to one or more antennas, such as antennas 335 and 336 shown. Short-to-medium-range wireless communication circuitry 329 may also be coupled (e.g., communicatively grounded; directly or indirectly) to one or more antennas, such as antennas 337 and 338 shown. Alternatively, short-to-medium-range wireless communication circuitry 329 may be coupled (e.g., communicatively grounded; directly or indirectly) to antennas 337 and 338, or as an alternative, to antennas 335 and 336. Short-to-medium-range wireless communication circuitry 329 and / or cellular communication circuitry 330 may include multiple receive chains and / or multiple transmit chains for receiving and / or transmitting multiple spatial streams, such as in a multiple-input multiple-output (MIMO) configuration.

[0074] In some embodiments, as further described below, the cellular communication circuit 330 may include dedicated receive chains for multiple RATs (including and / or coupled to (e.g., communication ground; directly or indirectly) dedicated processors and / or radio components) (e.g., a first receive chain for LTE and a second receive chain for 5G NR). Furthermore, in some embodiments, the cellular communication circuit 330 may include a single transmit chain that can be switched between radio components dedicated to a particular RAT. For example, a first radio component may be dedicated to a first RAT, such as LTE, and can communicate with a dedicated receive chain and a transmit chain shared with additional radio components, such as a second radio component that may be dedicated to a second RAT (e.g., 5G NR) and can communicate with a dedicated receive chain and a shared transmit chain.

[0075] The communication device 106 may also include one or more user interface elements and / or be configured to be used with one or more user interface elements. User interface elements may include any of a variety of components such as a display 360 (which may be a touch screen display), a keyboard (which may be a separate keyboard or may be implemented as part of the touch screen display), a mouse, a microphone and / or a speaker, one or more cameras, one or more buttons, and / or any of a variety of other components capable of providing information to the user and / or receiving or interpreting user input.

[0076] The communication device 106 may also include one or more smart cards 345 with SIM (Subscriber Identity Module) functionality, such as one or more UICC cards (one or more general purpose integrated circuit cards) 345.

[0077] As shown in the figure, the SOC 300 may include a processor 302 and a display circuit 304. The processor executes program instructions for the communication device 106, and the display circuit performs graphics processing and provides display signals to the display 360. One or more processors 302 may also be coupled to a memory management unit (MMU) 340 (which may be configured to receive addresses from one or more processors 302 and translate those addresses into locations in memory (e.g., memory 306, read-only memory (ROM) 350, NAND flash memory 310)) and / or coupled to other circuitry or devices (such as the display circuit 304, short-to-medium range wireless communication circuitry 329, cellular communication circuitry 330, connector I / F 320, and / or display 360). The MMU 340 may be configured to perform memory protection and page table translation or setup. In some embodiments, the MMU 340 may be included as part of the processor 302.

[0078] As described above, communication device 106 can be configured to communicate using wireless and / or wired communication circuitry. Communication device 106 can be configured to perform a method for multiple TTI PUSCH transmissions in a wireless communication system as further described herein.

[0079] As described herein, communication device 106 may include hardware and software components for implementing the features described above to transmit a scheduling profile for power saving to a network. For example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable storage medium), processor 302 of communication device 106 may be configured to implement some or all of the features described herein. Alternatively (or otherwise), processor 302 may be configured as a programmable hardware element such as an FPGA (Field-Programmable Gate Array) or as an ASIC (Application-Specific Integrated Circuit). Alternatively (or otherwise), in conjunction with one or more of other components 300, 304, 306, 310, 320, 329, 330, 340, 345, 350, 360, processor 302 of communication device 106 may be configured to implement some or all of the features described herein.

[0080] Furthermore, as described in this invention, processor 302 may include one or more processing elements. Therefore, processor 302 may include one or more integrated circuits (ICs) configured to perform the functions of processor 302. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of one or more processors 302.

[0081] Further, as described herein, the cellular communication circuit 330 and the short-to-medium-range wireless communication circuit 329 may each include one or more processing elements. In other words, one or more processing elements may be included in the cellular communication circuit 330, and similarly, one or more processing elements may be included in the short-to-medium-range wireless communication circuit 329. Therefore, the cellular communication circuit 330 may include one or more integrated circuits (ICs) configured to perform the functions of the cellular communication circuit 330. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the cellular communication circuit 330. Similarly, the short-to-medium-range wireless communication circuit 329 may include one or more ICs configured to perform the functions of the short-to-medium-range wireless communication circuit 329. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the short-to-medium-range wireless communication circuit 329.

[0082] FIG. 4 - block diagram of a base station

[0083] FIG. 4 An exemplary block diagram of a base station 102 according to some embodiments is shown. It should be noted that... FIG. 4The base station shown is merely one example of a possible base station. As illustrated, base station 102 may include a processor 404 capable of executing program instructions specific to base station 102. Processor 404 may also be coupled to a memory management unit (MMU) 440 or other circuitry or device, which may be configured to receive addresses from processor 404 and translate those addresses into locations in memory (e.g., memory 460 and read-only memory (ROM) 450).

[0084] Base station 102 may include at least one network port 470. Network port 470 may be configured to be coupled to a telephone network and provide access rights as described above in Figure 1 and... FIG. 2 The telephone network described herein includes multiple devices such as UE device 106.

[0085] Network port 470 (or an additional network port) may also be configured, or alternatively configured, to be coupled to a cellular network, such as the core network of a cellular service provider. The core network may provide mobility-related services and / or other services to multiple devices, such as UE device 106. In some cases, network port 470 may be coupled to a telephone network via the core network, and / or the core network may provide the telephone network (e.g., in other UE devices served by the cellular service provider).

[0086] In some implementations, base station 102 may be a next-generation base station, such as a 5G New Radio (5G NR) base station, or “gNB”. In such implementations, base station 102 may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network. Furthermore, base station 102 may be considered a 5G NR cell and may include one or more transition and receive points (TRPs). Additionally, UEs capable of operating according to 5G NR may connect to one or more TRPs within one or more gNBs.

[0087] Base station 102 may include at least one antenna 434 and possibly multiple antennas. The at least one antenna 434 may be configured to function as a wireless transceiver and may be further configured to communicate with UE device 106 via radio component 430. Antenna 434 communicates with radio component 430 via communication link 432. Communication link 432 may be a receive link, a transmit link, or both. Radio component 430 may be configured to communicate via various wireless communication standards, including but not limited to 5G NR, LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, etc.

[0088] Base station 102 can be configured to perform wireless communication using multiple wireless communication standards. In some cases, base station 102 may include multiple radios that enable base station 102 to communicate according to multiple wireless communication technologies. For example, as one possibility, base station 102 may include an LTE radio component for performing communication according to LTE and a 5G NR radio component for performing communication according to 5G NR. In this case, base station 102 may be able to operate as both an LTE base station and a 5G NR base station. As another possibility, base station 102 may include a multimode radio component capable of performing communication according to any of multiple wireless communication technologies (e.g., 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.).

[0089] As further described below, base station 102 may include hardware and software components for implementing or supporting embodiments of the features described herein. Processor 404 of base station 102 may be configured to implement or support some or all of the methods described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, processor 404 may be configured as a programmable hardware element such as an FPGA (Field-Programmable Gate Array), or as an ASIC (Application-Specific Integrated Circuit), or a combination thereof. Alternatively (or in addition), in conjunction with one or more of other components 430, 432, 434, 440, 450, 460, and 470, processor 404 of base station 102 may be configured to implement or support some or all of the features described herein.

[0090] Furthermore, as described herein, processor 404 may comprise one or more processing elements. In other words, one or more processing elements may be included in processor 404. Therefore, processor 404 may include one or more integrated circuits (ICs) configured to perform the functions of processor 404. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of one or more processors 404.

[0091] Additionally, as described herein, the radio component 430 may comprise one or more processing elements. In other words, one or more processing elements may be included in the radio component 430. Therefore, the radio component 430 may include one or more integrated circuits (ICs) configured to perform the functions of the radio component 430. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the radio component 430.

[0092] FIG. 5 : block diagram of cellular communication circuit

[0093] FIG. 5 An exemplary simplified block diagram of a cellular communication circuit according to some embodiments is shown. It should be noted that... FIG. 5 The block diagram of the cellular communication circuit is merely one example of a possible cellular communication circuit. According to the implementation, the cellular communication circuit 330 may be included in a communication device such as the communication device 106 described above. As mentioned above, among other devices, the communication device 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet computer, and / or a combination of these devices.

[0094] Cellular communication circuit 330 may (e.g., communicatively; directly or indirectly) be coupled to one or more antennas, such as ( FIG. 3 Antennas 335a-335b and 336 are shown in the diagram. In some embodiments, the cellular communication circuit 330 may include dedicated receive chains for multiple RATs (including and / or coupled to (e.g., communication ground; directly or indirectly) dedicated processors and / or radio components) (e.g., a first receive chain for LTE and a second receive chain for 5G NR). For example, as shown... FIG. 5 As shown, the cellular communication circuit 330 may include a modem 510 and a modem 520. The modem 510 may be configured for communication according to a first RAT, such as LTE or LTE-A, and the modem 520 may be configured for communication according to a second RAT, such as 5G NR.

[0095] As shown, modem 510 may include one or more processors 512 and memory 516 communicating with processors 512. Modem 510 may communicate with radio frequency (RF) front end 530. RF front end 530 may include circuitry for transmitting and receiving radio signals. For example, RF front end 530 may include receiver circuitry (RX) 532 and transmitter circuitry (TX) 534. In some embodiments, receiver circuitry 532 may communicate with downlink (DL) front end 550, which may include circuitry for receiving radio signals via antenna 335a.

[0096] Similarly, modem 520 may include one or more processors 522 and memory 526 communicating with processor 522. Modem 520 may communicate with RF front end 540. RF front end 540 may include circuitry for transmitting and receiving radio signals. For example, RF front end 540 may include receiving circuitry 542 and transmitting circuitry 544. In some embodiments, receiving circuitry 542 may communicate with DL front end 560, which may include circuitry for receiving radio signals via antenna 335b.

[0097] In some implementations, switch 570 may couple transmitting circuitry 534 to uplink (UL) front-end 572. Additionally, switch 570 may couple transmitting circuitry 544 to UL front-end 572. UL front-end 572 may include circuitry for transmitting radio signals via antenna 336. Therefore, when cellular communication circuitry 330 receives an instruction to transmit according to a first RAT (e.g., supported by modem 510), switch 570 may be switched to a first state allowing modem 510 to transmit signals according to the first RAT (e.g., via a transmission chain including transmitting circuitry 534 and UL front-end 572). Similarly, when cellular communication circuitry 330 receives an instruction to transmit according to a second RAT (e.g., supported by modem 520), switch 570 may be switched to a second state allowing modem 520 to transmit signals according to the second RAT (e.g., via a transmission chain including transmitting circuitry 544 and UL front-end 572).

[0098] In some implementations, the cellular communication circuit 330 may be configured to perform a method for multiple TTI PUSCH transmissions in a wireless communication system as further described herein.

[0099] As described herein, modem 510 may include hardware and software components for implementing the features described above or for UL data used in time-division multiplexing NSA NR operation, as well as various other technologies described herein. For example, processor 512 may be configured to implement some or all of the features described herein by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable storage medium). Alternatively (or otherwise), processor 512 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array) or as an ASIC (Application-Specific Integrated Circuit). Alternatively (or otherwise), processor 512 may be configured to implement some or all of the features described herein by combining with one or more of other components 530, 532, 534, 550, 570, 572, 335, and 336.

[0100] Furthermore, as described herein, processor 512 may include one or more processing elements. Therefore, processor 512 may include one or more integrated circuits (ICs) configured to perform the functions of processor 512. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 512.

[0101] As described herein, modem 520 may include hardware and software components designed to implement the aforementioned features for transmitting power-saving scheduling profiles to the network, as well as various other technologies described herein. For example, processor 522 may be configured to implement some or all of the features described herein by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable storage medium). Alternatively (or otherwise), processor 522 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array) or as an ASIC (Application-Specific Integrated Circuit). Alternatively (or additionally), processor 522 may be configured to implement some or all of the features described herein by combining one or more of other components 540, 542, 544, 550, 570, 572, 335, and 336.

[0102] Furthermore, as described herein, processor 522 may include one or more processing elements. Therefore, processor 522 may include one or more integrated circuits (ICs) configured to perform the functions of processor 522. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 522.

[0103] 5G NR architecture with LTE

[0104] In some specific implementations, fifth-generation (5G) wireless communication will initially be deployed concurrently with current wireless communication standards (e.g., LTE). For example, dual connectivity between LTE and the new 5G radio (5G NR or NR) has been designated as part of the initial deployment of NR. Therefore, as... FIG. 6A-B As shown, the Evolved Packet Core (EPC) network 600 can continue to communicate with the current LTE base station (e.g., eNB 602). Furthermore, eNB 602 can communicate with the 5G NR base station (e.g., gNB 604) and can transfer data between the EPC network 600 and gNB 604. Therefore, the EPC network 600 can be used (or reused), and gNB 604 can serve as additional capacity for user equipment, for example, to provide increased downlink throughput for the UE. In other words, LTE can be used for control plane signaling, and NR can be used for user plane signaling. Therefore, LTE can be used to establish connections to the network, and NR can be used for data services.

[0105] FIG. 6B The proposed protocol stack for eNB 602 and gNB 604 is shown. As illustrated, eNB 602 may include a Media Access Control (MAC) layer 632 that interfaces with Radio Link Control (RLC) layers 622a-622b. RLC layer 622a may also interface with Packet Data Convergence Protocol (PDCP) layer 612a, and RLC layer 622b may interface with PDCP layer 612b. Similar to the dual connectivity specified in Advanced LTE Release 12, PDCP layer 612a may interface with EPC network 600 via Primary Cell Group (MCG) bearer, while PDCP layer 612b may interface with EPC network 600 via decoupling bearer.

[0106] Additionally, as shown in the figure, gNB 604 may include a MAC layer 634 that interfacing with RLC layers 624a-624b. RLC layer 624a may interfacing with the PDCP layer 612b of eNB 602 via the X2 interface for information exchange and / or coordination (e.g., UE scheduling) between eNB 602 and gNB 604. Furthermore, RLC layer 624b may interfacing with PDCP layer 614. Similar to the dual connectivity specified in Advanced LTE Release 12, PDCP layer 614 may interfacing with EPC network 600 via a secondary cell group (SCG) bearer. Therefore, eNB 602 can be considered the primary node (MeNB), and gNB 604 can be considered the secondary node (SgNB). In some cases, it may be required that the UE maintain connectivity with both the MeNB and the SgNB. In such cases, the MeNB can be used to maintain the Radio Resource Control (RRC) connection with the EPC, while the SgNB can be used for capacity (e.g., additional downlink and / or uplink throughput).

[0107] 5G core network architecture - Interworking with Wi-Fi

[0108] In some implementations, access to the 5G core network (CN) can be made via (or through) cellular connections / interfaces (e.g., via 3GPP communication architectures / protocols) and non-cellular connections / interfaces (e.g., non-3GPP access architectures / protocols such as Wi-Fi connections). FIG. 7AAn example of a 5G network architecture according to some implementation schemes is shown, which combines 3GPP (e.g., cellular) and non-3GPP (e.g., non-cellular) access in a 5G CN. As shown, a user equipment device (e.g., UE 106) can access the 5G CN via both a radio access network (RAN, e.g., gNB or base station 604) and an access point such as AP 112. AP 112 may include a connection to the Internet 700 and a connection to a non-3GPP Interoperability Function (N3IWF) 702 network entity. N3IWF may include a connection to the core access and mobility management function (AMF) 704 of the 5G CN. AMF 704 may include an instance of 5G mobility management (5G MM) functions associated with UE 106. Additionally, the RAN (e.g., gNB 604) may also have a connection to AMF 704. Therefore, the 5G CN can support unified authentication on both connections and allow UE 106 to register access simultaneously via gNB 604 and AP 112. As shown, AMF 704 may include one or more functional entities associated with the 5G CN (e.g., Network Slice Selection Function (NSSF) 720, Short Message Service Function (SMSF) 722, Application Function (AF) 724, Unified Data Management (UDM) 726, Policy Control Function (PCF) 728, and / or Authentication Server Function (AUSF) 730). It should be noted that these functional entities can also be supported by the 5G CN's Session Management Functions (SMF) 706a and SMF 706b. AMF 706 can connect to (or communicate with) SMF 706a. Furthermore, gNB 604 can communicate with (or connect to) the User Plane Function (UPF) 708a, which can also communicate with SMF 706a. Similarly, N3IWF 702 can communicate with UPF 708b, which can also communicate with SMF 706b. Both UPFs can communicate with data networks (e.g., DN 710a and 710b) and / or the Internet 700 and IMS core network 710.

[0109] FIG. 7BAn example of a 5G network architecture according to some implementation schemes is shown, which combines dual 3GPP (e.g., LTE and 5G NR) access and non-3GPP access in a 5G CN. As shown, a user equipment device (e.g., UE 106) can access the 5G CN through both a radio access network (RAN, such as gNB or base station 604 or eNB or base station 602) and an access point such as AP 112. AP 112 may include a connection to the Internet 700 and a connection to the N3IWF 702 network entity. The N3IWF may include a connection to the AMF 704 of the 5G CN. AMF 704 may include an instance of 5G MM functionality associated with UE 106. Additionally, the RAN (e.g., gNB 604) may also have a connection to AMF 704. Therefore, the 5G CN can support unified authentication on both connections and allow UE 106 to register access simultaneously via gNB 604 and AP 112. Additionally, the 5G CN can support dual registration of the UE on both a legacy network (e.g., LTE via base station 602) and a 5G network (e.g., via base station 604). As shown, base station 602 may have connections to both Mobility Management Entity (MME) 742 and Service Gateway (SGW) 744. MME 742 may have connections to both SGW 744 and AMF 704. Furthermore, SGW 744 may have connections to both SMF 706a and UPF 708a. As shown, AMF 704 may include one or more functional entities associated with the 5G CN (e.g., NSSF 720, SMSF 722, AF 724, UDM 726, PCF 728, and / or AUSF 730). Note that UDM 726 may also include Home Subscriber Server (HSS) functionality, and PCF may also include Policy and Charging Rules (PCRF) functionality. It should also be noted that these functional entities can also be supported by the 5G CN's SMF 706a and SMF 706b. The AMF 706 can connect to (or communicate with) the SMF 706a. Furthermore, the gNB 604 can communicate with (or connect to) the UPF 708a, which in turn can communicate with the SMF 706a. Similarly, the N3IWF702 can communicate with the UPF 708b, which in turn can communicate with the SMF 706b. Both UPFs can communicate with data networks (e.g., DN710a and 710b) and / or the Internet 700 and IMS core network 710.

[0110] It should be noted that, in various implementations, one or more of the network entities described above may be configured to perform methods for improving security checks in 5G NR networks, including, for example, mechanisms for multiple TTI PUSCH transmissions in wireless communication systems as further described herein.

[0111] FIG. 8 An example of a baseband processor architecture for a UE (e.g., UE 106) according to some implementation schemes is shown. As described above, FIG. 8 The baseband processor architecture 800 described herein can be implemented on one or more radio components (e.g., radio components 329 and / or 330) or modems (e.g., modems 510 and / or 520) as described above. As shown, the non-access stratum 810 may include a 5G NAS 820 and a traditional NAS 850. The traditional NAS 850 may include a communication connection with a traditional access stratum (AS) 870. The 5G NAS 820 may include communication connections with a 5G AS 840 and a non-3GPP AS 830, as well as a Wi-Fi AS 832. The 5G NAS 820 may include functional entities associated with both access strata. Therefore, the 5G NAS 820 may include multiple 5G MM entities 826 and 828 and 5G session management (SM) entities 822 and 824. The traditional AS 850 may include functional entities such as Short Message Service (SMS) entity 852, Evolved Packet System (EPS) Session Management (ESM) entity 854, Session Management (SM) entity 856, EPS Mobility Management (EMM) entity 858, and Mobility Management (MM) / GPRS Mobility Management (GMM) entity 860. Furthermore, the traditional AS 870 may include functional entities such as LTE AS 872, UMTS AS 874, and / or GSM / GPRS 876.

[0112] Therefore, the baseband processor architecture 800 allows for a common 5G-NAS for both 5G cellular and non-cellular (e.g., non-3GPP access) networks. It's important to note that, as shown in the figure, the 5G MM can maintain separate connection management and registration management state machines for each connection. Furthermore, a device (e.g., UE 106) can register to a single PLMN (e.g., a 5G CN) using both 5G cellular and non-cellular access. Additionally, a device can be in a connected state in one access and an idle state in another, or vice versa. Finally, there may be common 5G-MM procedures (e.g., registration, deregistration, identification, authentication, etc.) for both accesses.

[0113] It should be noted that, in various implementations, one or more of the aforementioned functional entities of the 5G NAS and / or 5G AS may be configured to perform methods, such as those described further herein, for multiple TTI PUSCH transmissions in a wireless communication system.

[0114] Multiple TTI PUSCH transmission

[0115] In current communication systems, certain unlicensed frequency bands, such as the 5GHz and / or 6GHz bands, are already used by communication systems, such as Wi-Fi in the 5GHz band. Therefore, 5G NR unlicensed (NR-U) band access systems need to be able to coexist fairly with systems already deployed in unlicensed bands. For example, an NR-U access system deployed in the 5GHz band should be able to coexist fairly with Wi-Fi access systems deployed in the 5GHz band. Therefore, a Listen-Before-Tell (LBT) mechanism (e.g., an energy-sensing (ED)-based channel access mechanism) can be implemented before transmission to ensure fair coexistence with existing systems.

[0116] However, in current implementations of 5G NR (e.g., such as 3GPP Release 15), the downlink control information (DCI) format can only schedule a single physical uplink shared channel (PUSCH) transmission. Therefore, scheduling multiple PUSCH transmissions over a single or multiple transmission time intervals (TTIs) may require, for example, multiple DCI message transmissions as is required for licensed band transmissions. However, while this approach may be a good design for licensed band access, for example, to provide flexibility in PUSCH scheduling, it is unsuitable for NR-U operation on unlicensed bands because multiple DCI scheduling requests require multiple LBT processes (e.g., each DCI scheduling request may require an LBT process) to schedule PUSCHs via network (base station) access to channels in unlicensed bands.

[0117] This issue has been addressed by allowing the use of a single DCI format in NR-U to support multiple TTI PUSCH transport scheduling. For example, NR-U will support multiple TTI scheduling for each PUSCH transport using a separate uplink (UL) license during the same physical downlink control channel (PDCCH) monitoring time. Additionally, NR-U will support multiple TTI scheduling for PUSCH transports using a single UL license.

[0118] The embodiments described herein provide systems, methods, and mechanisms for implementing multiple TTI scheduling using a single DCI format in NR-U. For example, the embodiments described herein provide a mechanism for allocating time-domain resources for scheduling multiple TTI PUSCH transports in NR-U. Additionally, the embodiments described herein provide a mechanism for enabling Hybrid Automatic Repeat Request (HARQ) operation based on Block Code Groups (CBGs) for PUSCHs with multiple TTI scheduling in NR-U.

[0119] In some implementations, the UE can be scheduled to transmit transport blocks (TBs) over multiple PUSCH transport opportunities via DCI messages using unlicensed frequency bands across multiple time slots and / or micro-time slots. In some implementations, the Time Domain Resource Allocation (TDRA) field value m of the DCI message (or format) can provide a row index, e.g., m+1, to a table configured by higher-level signaling (e.g., Radio Resource Control (RRC) signaling). In some implementations, each row of the RRC configuration table can include one or more PUSCH transport configurations (e.g., a set of PUSCH transport configurations) and can be associated with a dedicated row index. In some implementations, for each PUSCH transport configuration (and / or within a set of PUSCH transport configurations) in the one or more PUSCH transport configurations, the index row can define a start and length indication value (SLIV), the PUSCH mapping type to be applied, and / or a time slot offset K2 value. In some implementations, the maximum number (or value) of PUSCH transport configurations can be predefined by the UE and / or indicated as part of the UE capability signaling. In some implementations, for example, the maximum number of PUSCH transport configurations can be determined by a balance (or trade-off) between the DCI message (or format) overhead and the DCI message (or format) payload size, due to transport-specific parameters in the DCI message (or format).

[0120] For example, FIG. 9A An example of an RRC configuration table for multi-slot PUSCH time-domain resource allocation is shown according to some implementation schemes. As shown, index row 0 defines (or specifies) the first PUSCH transmission configuration for four time-domain resource allocations by defining (or specifying) the slot offset K2 value, PUSCH mapping type, and SLIV for each time-domain resource allocation. Similarly, index row 1 defines (or specifies) the first PUSCH transmission configuration for four time-domain allocations by defining (or specifying) the slot offset K2 value, PUSCH mapping type, and SLIV for each time-domain allocation. In some implementation schemes, multi-slot PUSCH time-domain resource allocation can aggregate more than one single-slot PUSCH time-domain resource allocation that can be used for radio transmissions (such as for NR unlicensed band (NR-U) systems). Specifically, as FIG. 9B and FIG. 9C As shown, there are gaps between the time-domain resource allocations of multi-slot PUSCH (e.g., as...). FIG. 9B (as shown) or without gaps (e.g., as shown) FIG. 9CIn the case shown, multi-slot PUSCH time-domain resource allocation can be achieved by aggregating PUSCH transmissions of hybrid type A (e.g., slot-based scheduling) and type B (e.g., micro-slot-based scheduling and / or sub-slot-based scheduling). In some implementations, this unified framework can provide the network with scheduling flexibility to dynamically meet various application requirements.

[0121] In some implementations, the abstract syntax symbol 1 (ASN.1) can be used to define the data structure for signaling the configuration table of multi-slot PUSCH transports, for example, as... FIG. 10A As shown in the figure, a multi-slot PUSCH transport configuration table, such as PUSCH-TimeDomainAllocationlist, can include the maximum number of allocations that can be specified (maxNrOfAllocations), as well as the K2 value, PUSCH mapping type, and SLIV.

[0122] In some implementations, multiple micro-slot (e.g., sub-slot) type UL licenses may be transmitted to the UE to provide the UE with sufficient Listen-Before-Beat (LBT) opportunities, thereby reserving channels in unlicensed bands for transmission. In some implementations, full-slot UL transmission can be assumed, except for the start and end slots within the UL transmission burst, such as index 2 of Table 11.1.1-1 in 3GPP TS38.213 v15.6.0. Furthermore, in some implementations, it can be assumed that only gapless, continuous time-domain resource allocations are supported. Based on such assumptions, higher-layer signaling can be further simplified because the start symbol of the UL transmission does not need to be signaled except for the first time-domain resource allocation. For example, as... FIG. 10B As shown, ASN.1 can be used to define a data structure for signaling UL licenses for multiple micro-slot types. As illustrated, the data structure can be simplified to include only the PUSCH mapping type and length.

[0123] FIG. 11 A block diagram illustrating an example of a method for scheduling a User Equipment (UE) to transmit over multiple Transmission Time Intervals (TTIs) using an unlicensed frequency band, according to some implementation schemes. Among other things, FIG. 11 The method shown can also be used with any of the systems, methods, or devices shown in the figures. In various embodiments, some of the method elements shown may be executed concurrently in a different order than that shown, or may be omitted. Additional method elements may also be executed as needed. As shown, the method operates as follows.

[0124] At 1102, the UE (such as UE 106) can execute Radio Resource Control (RRC) signaling with a network entity (such as gNB 604) to configure a data structure that may include one or more sets of Physical Uplink Shared Channel (PUSCH) transport configurations. In some embodiments, each set of PUSCH transport configurations may span multiple TTIs. In some embodiments, each set of PUSCH transport configurations may include one or more PUSCH transport configurations. In some embodiments, each PUSCH transport configuration within a set of PUSCH transport configurations may include at least one of a Start and Length Indication Value (SLIV), a PUSCH mapping type to be applied, and / or a slot offset K2 value (or one or more of them and / or any combination thereof). In some embodiments, the PUSCH mapping type may indicate one of slot-based scheduling or micro-slot-based scheduling. In some embodiments, the UE may indicate a maximum number of PUSCH transport configurations. In some embodiments, the maximum number of PUSCH transport configurations may be predefined. In some implementations, the maximum number of PUSCH transport configurations may be determined at least in part based on a balance between DCI message (or format) overhead and DCI message (or format) payload size (e.g., via communication between the UE and the network). In some implementations, the data structure may be defined using Abstract Syntax Notation 1 (ASN.1) and may include a PUSCH-TimeDomainAllocationlist parameter. In some implementations, the PUSCH-TimeDomainAllocationlist parameter specifies at least one (or one or more and / or any combination thereof) of the following: the maximum number of PUSCH transport allocations, the slot offset K2 value, the PUSCH mapping type, and / or the start and length indication value (SLIV). In some implementations, the data structure may be simplified to include only the PUSCH mapping type and length. In some implementations, the network (and / or network entity / base station) may operate according to 3GPP 5G New Radio (5G NR) Radio Access Technology (RAT).

[0125] At 1104, the UE can receive a Downlink Control Information (DCI) message (from the network). This DCI message may include a Time Domain Resource Allocation (TDRA) field, which may (e.g., based on the value of the TDRA) indicate a set of PUSCH transport configurations included in a data structure. In some embodiments, the indicated set of PUSCH transport configurations may include a transport gap between each PUSCH transport indicated by that set of PUSCH transport configurations. In some embodiments, the indicated set of PUSCH transport configurations may not include the transport gap between each PUSCH transport indicated by that set of PUSCH transport configurations.

[0126] At 1106, the UE can perform PUSCH transmissions across multiple TTIs on an unlicensed frequency band according to an indicated set of PUSCH transmission configurations.

[0127] In some implementations, code block group (CBG)-based retransmission operations for multi-slot / micro-slot PUSCH scheduling can be supported. Such implementations can improve spectral efficiency (e.g., utilization of unlicensed frequency bands). In some implementations, for transport block (TB)-based PUSCHs scheduled by multi-slot / micro-slot and / or multiple TTI PUSCH scheduling DCI formats (e.g., as described above), the UE may not expect CBG-based retransmissions. In other words, TB-based transmissions or retransmissions can be scheduled by multi-slot / micro-slot and / or multiple TTI PUSCH scheduling DCI messages. However, this approach may increase signaling overhead and / or the probability of channel unavailability. Therefore, in some implementations, to improve resource utilization, reduce signaling overhead, and / or reduce the probability of channel unavailability, multiple (e.g., a set) CBG transport information (CBGTI) information elements (IEs) can be transmitted via DCI messages that can schedule multi-slot / sub-slot / micro-slot PUSCH transmissions. In some implementations, the number of bits per CBGTI IE (e.g., the number of CBGs per TB for UL transmission) can be configured by a higher layer (e.g., via RRC signaling) on ​​a per-UE basis. In some implementations, the number of CBGs per TB can be based at least in part on UE capabilities and a balance (or trade-off) between control signaling overhead and Hybrid Automatic Repeat Request (HARQ) operational efficiency. In some implementations, the DCI format size can increase linearly with the number of PUSCH transmissions scheduled by UL license.

[0128] For example, FIG. 12 An example of CBG-based retransmission for multi-slot / micro-slot PUSCH scheduling is shown according to some implementation schemes. As shown, multiple CBG transmission information (CBGTI) IEs 1210 to 1240 can be transmitted to a UE (such as UE 106) via DCI format 1200 (which may also include other IEs 1250 and CRC 1260) to schedule multiple PUSCH transmissions 1212-1242. In some implementations, the number of bits for each CBGTI IE 1210 to 1240 can be represented as N. CBG (For example, the number of CBGs per TB used for UL transmission), which can be configured by higher layers on a per-UE basis, for example, based on UE geometry and a trade-off between control signaling overhead and HARQ operational efficiency.

[0129] In some implementations, to reduce signaling overhead from multiple TTI UL licenses, the CBGTI field may be limited to PUSCH retransmissions and may not exist for the initial PUSCH transmission. For example, the maximum number of HARQ processes with CBG-based retransmissions that can be scheduled by a single TTI UL license (e.g., Higher-layer signaling (e.g., RRC signaling) is configured on a per-UE basis, for example, to avoid blind detection of the assumed DCI format size on the UE side. In some implementations, the HARQ process ID associated with PUSCH retransmission can be implicitly determined by the UE (e.g., based on a HARQ process-specific New Data Indication (NDI) field) or signaled as part of the DCI format in multiple TTI UL licenses. For example, the CBG-based HARQ process ID (CBG-HPI) IE can use a bitmap to indicate which HARQ process IDs are retransmitted using CBG-based HARQ retransmission. In some implementations, CBG-HPI may include a maximum number of bits, max{[log2(maxHPICindex)+1],1}maxHPICindex can be the maximum value of the HARQ process ID composite index (HPIC) within a PUSCH transmission scheduled by a single multiple TTI UL license. In some implementations, HPIC combinations using CBG-based retransmissions can be identified by an HPIC index corresponding to an HPIC combination table. In some implementations, this table can be configured by a higher layer (e.g., via RRC signaling) or can be predefined (e.g., by specification). In some implementations, when With reduced signaling overhead, the HARQ process ID can be directly indicated in the DCI format.

[0130] In some implementations, to further reduce the signaling overhead associated with CBG-based HARQ operations, the UE can be provided with the start slot (or index) and length of CBG-based PUSCH retransmissions within multiple TTI schedules. In some implementations, the starting PUSCH index S with CBG-based operations may be associated with the first PUSCH transmission across multiple TTI transmissions. Additionally, the number L of consecutive PUSCHs with CBG-based transmissions, counted from PUSCH index S, can be indicated. In some implementations, the indication of the starting PUSCH index S and the number of consecutive CBG-based PUSCHs can be indicated individually by a dedicated IE or jointly signaled by a single IE in multiple TTI DCI formats.

[0131] For example, FIG. 13A-B Examples of the starting PUSCH index S and corresponding transfers according to some implementation schemes are shown. FIG. 13B The table shown assumes Four PUSCH transfers are scheduled by a single multiple TTI scheduling DCI format. For this example, a total of 3 bits is sufficient to indicate all combinations of two CBG-based PUSCH transfers, such as PUSCH transfers 1312-1314, which can be preceded by TB-based PUSCH transfer 1310 and followed by TB-based PUSCH transfer 1316.

[0132] In some implementations, multiple TTI scheduling DCI formats may include information elements (IEs), such as the priority level (PC) and / or LBT type of a PUSCH transmission. In some implementations, a single PC IE in the DCI format may be applied to all PUSCH transmissions to minimize downlink control overhead. In some implementations, to ensure scheduling flexibility for UL shared channel transmissions with potentially different priority levels, a separate PC IE may be included in the DCI format, associated one-to-one with each PUSCH transmission within a PUSCH transmission burst (e.g., at the cost of increased downlink signaling overhead). In some implementations, a 1-bit may be used to signal the LBT type, where a value of 0 indicates a Category 2 (Cat-2) LBT type and a value of 1 indicates a Category 4 (Cat-4) LBT type. In some implementations, joint encoding of these IEs (e.g., for priority level and LBT type) may be used to further reduce the DCI format size.

[0133] In some implementations, aperiodic sounding reference signal (SRS) transmissions can be triggered by multiple TTIs scheduling DCI formats. In some implementations, the UE can... The non-periodic SRS transmissions triggered by the SRS resource set during the defined time slot down rounding operation, where u srs and u PDCCH These are the subcarrier spacing configurations for SRS and PDCCH, respectively.

[0134] FIG. 14 A block diagram illustrating an example of a method for retransmission operations based on code block groups (CBGs) for multi-slot / micro-slot PUSCH scheduling, according to some implementation schemes, is shown. Among other things, FIG. 14 The method shown can also be used with any of the systems, methods, or devices shown in the figures. In various embodiments, some of the method elements shown may be executed concurrently in a different order than that shown, or may be omitted. Additional method elements may also be executed as needed. As shown, the method operates as follows.

[0135] At 1402, the UE (such as UE 106) can execute Radio Resource Control (RRC) signaling with a network entity (such as gNB 604) to configure the maximum number of Hybrid Automatic Repeat Request (HARQ) processes with CBG-based retransmissions to be scheduled by a single Multiple Transmission Time Interval (TTI) uplink (UL) license. In some implementations, CBG-based retransmissions can be indicated by one or more CBG Transmission Information (TI) Information Elements (IEs).

[0136] At 1404, the UE can receive a DCI message that schedules multiple PUSCH transmissions across multiple TTIs and includes a HARQ process with CBG-based retransmissions. In some implementations, the HARQ process identifier associated with a PUSCH retransmission can be implicitly determined by the UE. In some implementations, the HARQ process identifier associated with a PUSCH retransmission is indicated via the DCI message. In some implementations, a bitmap included in the DCI message can indicate the HARQ process identifier to be retransmitted using GCB-based retransmissions. In some implementations, the start transmission slot and length of the CBG-based retransmission can be indicated by the DCI message. In some implementations, the start transmission slot may be related to the first PUSCH transmission scheduled as indicated by the DCI message. In some implementations, the start transmission slot and length can be indicated by a single information element included in the DCI message. In some implementations, the DCI message can indicate a priority level and a Listen-Before-Speak (LBT) type. In some implementations, the priority level and LBT type can be indicated by a single information element included in the DCI message. In some implementations, the transmission of the non-periodic sounding reference signal (SRS) can be triggered by a DCI message.

[0137] At 1406, the UE can perform PUSCH transmissions across multiple TTIs and CBG-based HARQ retransmissions according to the scheduling indicated by the DCI message.

[0138] Other embodiments

[0139] In some implementations, methods for scheduling a user equipment (UE) to transmit over multiple transmission time intervals (TTIs) using unlicensed frequency bands may include the UE (e.g., such as UE 106):

[0140] Execute Radio Resource Control (RRC) signaling with network entities to configure a data structure comprising one or more sets of Physical Uplink Shared Channel (PUSCH) transport configurations, wherein each set of PUSCH transport configurations spans one or more TTIs;

[0141] Receive downlink control information (DCI) messages from the network entity, wherein the DCI messages include a time-domain resource allocation field (TDRA), and wherein the value of the TDRA indicates a set of PUSCH transport configurations included in the data structure; and

[0142] Perform PUSCH transmissions across one or more TTIs on unlicensed frequency bands according to the indicated set of PUSCH transmission configurations.

[0143] In some implementations, each group of PUSCH transport configurations may include one or more PUSCH transport configurations.

[0144] In some implementations, each PUSCH transport configuration within a set of PUSCH transport configurations may include at least one of the following:

[0145] Start and Length Indicator Values ​​(SLIV);

[0146] The type of PUSCH mapping to apply; and / or

[0147] Time slot offset K2 value.

[0148] In some implementations, the PUSCH mapping type may indicate either slot-based scheduling or micro-slot-based scheduling.

[0149] In some implementations, the method may include the UE indicating a maximum number of PUSCH transmission configurations.

[0150] In some implementations, the maximum number of PUSCH transport configurations can be predefined.

[0151] In some implementations, the maximum number of PUSCH transport configurations may be determined at least in part based on a balance between DCI message overhead and DCI message payload size.

[0152] In some implementations, the data structure may be defined using Abstract Syntax Notation 1 (ASN.1) and includes the PUSCH-TimeDomainAllocationlist parameter. In some implementations, the PUSCH-TimeDomainAllocationlist parameter may specify at least one of the following:

[0153] Maximum number of PUSCH transfer allocations;

[0154] K2 value;

[0155] PUSCH mapping type; and / or

[0156] Start and Length Indicator Values ​​(SLIV).

[0157] In some implementations, the data structure may be defined using abstract syntax notation 1 (ASN.1) and may include the PUSCH mapping type and length.

[0158] In some implementations, the indicated set of PUSCH transport configurations may include transport gaps between each PUSCH transport indicated by the set of PUSCH transport configurations.

[0159] In some implementations, the indicated set of PUSCH transport configurations may not include the transport gaps between each PUSCH transport indicated by the set of PUSCH transport configurations.

[0160] In some implementations, the network entity may operate according to 3GPP 5th Generation New Radio (5GNR) Radio Access Technology (RAT).

[0161] In some implementations, the UE may include:

[0162] One or more antennas;

[0163] One or more radio components, wherein each of the one or more radio components is configured to perform cellular communication using at least one radio access technology (RAT); and

[0164] One or more processors coupled to one or more radio components, wherein the one or more processors and the one or more radio components are configured to perform voice and / or data communication, and wherein the one or more processors are configured to cause the UE to perform the method.

[0165] In some implementations, a non-transitory computer-readable storage medium may store program instructions executable by processing circuitry to cause the UE to perform the method.

[0166] In some implementations, methods for scheduling user equipment (UE) to transmit over multiple transmission time intervals (TTIs) using unlicensed frequency bands may include network entities (e.g., such as base station 102):

[0167] The radio resource control (RRC) signaling configuration with the UE includes a data structure comprising one or more sets of physical uplink shared channel (PUSCH) transmission configurations, wherein each set of PUSCH transmission configurations spans multiple TTIs;

[0168] Sending a downlink control information (DCI) message to the UE, wherein the DCI message includes a time domain resource allocation field (TDRA), and wherein the value of the TDRA indicates a set of PUSCH transport configurations included in the data structure; and

[0169] On an unlicensed frequency band, the UE receives PUSCH transmissions spanning multiple TTIs according to an indicated set of PUSCH transmission configurations.

[0170] In some implementations, each group of PUSCH transport configurations may include one or more PUSCH transport configurations.

[0171] In some implementations, each PUSCH transport configuration within a set of PUSCH transport configurations may include at least one of the following:

[0172] Start and Length Indicator Values ​​(SLIV);

[0173] The type of PUSCH mapping to apply; and / or

[0174] Time slot offset K2 value.

[0175] In some implementations, the PUSCH mapping type may indicate either slot-based scheduling or micro-slot-based scheduling.

[0176] In some implementations, the method may include the network entity receiving an indication from the UE of the maximum number of PUSCH transmission configurations.

[0177] In some implementations, the maximum number of PUSCH transport configurations can be predefined.

[0178] In some implementations, the maximum number of PUSCH transport configurations may be determined at least in part based on a balance between DCI message overhead and DCI message payload size.

[0179] In some implementations, the data structure may be defined using abstract syntax notation 1 (ASN.1) and may include the PUSCH-TimeDomainAllocationlist parameter.

[0180] In some implementations, the PUSCH-TimeDomainAllocationlist parameter may specify at least one of the following:

[0181] Maximum number of PUSCH transfer allocations;

[0182] K2 value;

[0183] PUSCH mapping type; and / or

[0184] Start and Length Indicator Values ​​(SLIV).

[0185] In some implementations, the data structure may be defined using abstract syntax notation 1 (ASN.1) and may include the PUSCH mapping type and length.

[0186] In some implementations, the indicated set of PUSCH transport configurations may include transport gaps between each PUSCH transport indicated by the set of PUSCH transport configurations.

[0187] In some implementations, the indicated set of PUSCH transport configurations may not include the transport gaps between each PUSCH transport indicated by the set of PUSCH transport configurations.

[0188] In some implementations, the network entity may operate according to 3GPP 5th Generation New Radio (5GNR) Radio Access Technology (RAT).

[0189] In some implementations, the network entity may include:

[0190] At least one antenna;

[0191] At least one radio component, wherein the at least one radio component is configured to perform cellular communication using at least one radio access technology (RAT); and

[0192] One or more processors coupled to the at least one radio component, wherein the one or more processors and the at least one radio component are configured to perform voice and / or data communication, and wherein the one or more processors are configured to cause the network entity to perform the method.

[0193] In some implementations, a non-transitory computer-readable storage medium may store program instructions executable by processing circuitry to cause the network entity to perform the method.

[0194] In some implementations, the method for code block group (CBG) based retransmission operations for multi-slot / micro-slot physical uplink control channel (PUSCH) scheduling may include user equipment (UE) (such as UE 106):

[0195] Execute Radio Resource Control (RRC) signaling with network entities to configure the maximum number of Hybrid Automatic Repeat Request (HARQ) processes with CBG-based retransmissions to be scheduled by a single Multiple Transmission Time Interval (TTI) uplink (UL) license.

[0196] Receive downlink control information (DCI) messages from the network entity, wherein the DCI messages schedule multiple PUSCH transmissions across multiple TTIs and include a HARQ process with CBG-based retransmissions; and

[0197] The scheduler, as indicated by the DCI message, performs PUSCH transmissions across multiple TTIs.

[0198] In some implementations, CBG-based retransmissions can be indicated by one or more CBG Transport Information (TI) Info Elements (IE).

[0199] In some implementations, the HARQ process identifier associated with PUSCH retransmission can be implicitly determined by the UE.

[0200] In some implementations, the HARQ process identifier associated with PUSCH retransmission can be indicated by the DCI message.

[0201] In some implementations, the bitmap may indicate the HARQ process identifier for which GCB-based retransmission should be used.

[0202] In some implementations, the start transmission slot and length of a CBG-based retransmission can be indicated by a DCI message.

[0203] In some implementations, the start of the transmission slot may be associated with the first PUSCH transmission scheduled as indicated by the DCI message.

[0204] In some implementations, the start time slot and length of transmission can be indicated by a single information element included in the DCI message.

[0205] In some implementations, the DCI message may indicate a priority level and a Listen-Before-Speak (LBT) type.

[0206] In some implementations, the priority level and LTB type can be indicated by a single information element included in the DCI message.

[0207] In some implementations, the transmission of the non-periodic sounding reference signal (SRS) can be triggered by a DCI message.

[0208] In some implementations, the UE may include:

[0209] One or more antennas;

[0210] One or more radio components, wherein each of the one or more radio components is configured to perform cellular communication using at least one radio access technology (RAT); and

[0211] One or more processors coupled to one or more radio components, wherein the one or more processors and the one or more radio components are configured to perform voice and / or data communication, and wherein the one or more processors are configured to cause the UE to perform the method.

[0212] In some implementations, a non-transitory computer-readable storage medium may store program instructions executable by processing circuitry to cause the UE to perform the method.

[0213] In some implementations, the method for code block group (CBG) based retransmission operations for multi-slot / micro-slot physical uplink control channel (PUSCH) scheduling may include network entities (e.g., such as base station 102):

[0214] Perform Radio Resource Control (RRC) signaling with User Equipment (UE) to configure the maximum number of Hybrid Automatic Repeat Request (HARQ) processes with CBG-based repeats to be scheduled by a single Multiple Transmission Time Interval (TTI) uplink (UL) license.

[0215] The UE is transmitted downlink control information (DCI) messages, wherein the DCI messages span multiple TTIs, schedule multiple PUSCH transmissions, and include a HARQ process with CBG-based retransmissions; and

[0216] The scheduling indicated by the DCI message receives PUSCH transmissions across multiple TTIs from the UE.

[0217] In some implementations, CBG-based retransmissions can be indicated by one or more CBG Transport Information (TI) Info Elements (IE).

[0218] In some implementations, the HARQ process identifier associated with PUSCH retransmission can be implicitly determined by the UE.

[0219] In some implementations, the HARQ process identifier associated with PUSCH retransmission can be indicated by the DCI message.

[0220] In some implementations, the bitmap may indicate the HARQ process identifier for which GCB-based retransmission should be used.

[0221] In some implementations, the start transmission slot and length of a CBG-based retransmission can be indicated by a DCI message.

[0222] In some implementations, the start of the transmission slot may be associated with the first PUSCH transmission scheduled as indicated by the DCI message.

[0223] In some implementations, the start time slot and length of transmission can be indicated by a single information element included in the DCI message.

[0224] In some implementations, the DCI message may indicate a priority level and a Listen-Before-Speak (LBT) type.

[0225] In some implementations, the priority level and LTB type can be indicated by a single information element included in the DCI message.

[0226] In some implementations, the transmission of the non-periodic sounding reference signal (SRS) can be triggered by a DCI message.

[0227] In some implementations, the network entity may include:

[0228] At least one antenna;

[0229] At least one radio component, wherein the at least one radio component is configured to perform cellular communication using at least one radio access technology (RAT); and

[0230] One or more processors coupled to the at least one radio component, wherein the one or more processors and the at least one radio component are configured to perform voice and / or data communication, and wherein the one or more processors are configured to cause the network entity to perform the method.

[0231] In some implementations, a non-transitory computer-readable storage medium may store program instructions executable by processing circuitry to cause the network entity to perform the method.

[0232] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0233] Embodiments of this disclosure may be implemented in any of a variety of forms. For example, some embodiments may be implemented as computer-implemented methods, computer-readable storage media, or computer systems. Other embodiments may be implemented using one or more custom-designed hardware devices such as ASICs. Other embodiments may be implemented using one or more programmable hardware elements such as FPGAs.

[0234] In some embodiments, a non-transitory computer-readable storage medium may be configured to store program instructions and / or data, wherein if the program instructions are executed by a computer system, the computer system performs a method, such as any method embodiment of the method embodiments described herein, or any combination of the method embodiments described herein, or any subset or combination of any such subset of any method embodiments described herein.

[0235] In some embodiments, the device (e.g., UE 106) may be configured to include a processor (or a set of processors) and a memory medium storing program instructions, wherein the processor is configured to read from and execute the program instructions from the memory medium, wherein the program instructions are executable to implement any of the various method embodiments described herein (or any combination of method embodiments described herein, or any subset of any of the method embodiments described herein, or any combination of such subsets). The device may be implemented in any of a variety of forms.

[0236] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the disclosure is fully understood. This disclosure is intended to render the following claims as encompassing all such variations and modifications.

Claims

1. A user equipment (UE) device, the user equipment device comprising: One or more antennas; One or more radio components, each of which is configured to perform cellular communication using at least one radio access technology (RAT); One or more processors, said one or more processors being coupled to said one or more radio components, wherein said one or more processors and said one or more radio components are configured to perform voice and / or data communication; The one or more processors are configured such that the UE: Execute Radio Resource Control (RRC) signaling with network entities to configure a data structure, wherein each line of the data structure includes a set of Physical Uplink Shared Channel (PUSCH) transport configurations, wherein the data structure is defined using the abstract syntax notation ASN.1 and includes a PUSCH time-domain allocation list parameter, wherein the PUSCH time-domain allocation list parameter specifies the maximum number of PUSCH transport allocations and specifies a K2 value, a PUSCH mapping type, and a start and length indication value SLIV for each time-domain allocation, and wherein each set of PUSCH transport configurations spans multiple TTIs; Receive downlink control information (DCI) messages from the network entity, wherein the DCI messages include a time-domain resource allocation (TDRA) field and a corresponding priority level associated one-to-one with each PUSCH transmission within a PUSCH transmission burst, wherein the value of the TDRA indicates a row index of the data structure, and wherein the row index is associated with a set of PUSCH transmission configurations included in the data structure; and Perform PUSCH transmissions across multiple TTIs on unlicensed frequency bands according to a set of indicated PUSCH transmission configurations.

2. The UE according to claim 1, Each PUSCH transport configuration group includes one or more PUSCH transport configurations.

3. The UE according to claim 1, The PUSCH mapping type indicates either slot-based scheduling or micro-slot-based scheduling.

4. The UE according to claim 1, The one or more processors are configured such that the UE: Indicates the maximum number of PUSCH transport configurations, wherein the maximum number of PUSCH transport configurations is determined at least in part based on a balance between DCI message overhead and DCI message payload size.

5. The UE according to claim 1, The maximum number of PUSCH transport configurations is predefined, and the maximum number of PUSCH transport configurations is determined at least in part based on a balance between DCI message overhead and DCI message payload size.

6. An apparatus comprising: Memory; as well as At least one processor, which communicates with the memory, wherein the at least one processor is configured to: Execute Radio Resource Control (RRC) signaling with network entities to configure a data structure, wherein each line of the data structure includes a set of Physical Uplink Shared Channel (PUSCH) transport configurations, wherein the data structure is defined using the abstract syntax notation ASN.1 and includes a PUSCH time-domain allocation list parameter, wherein the PUSCH time-domain allocation list parameter specifies the maximum number of PUSCH transport allocations and specifies a K2 value, a PUSCH mapping type, and a start and length indication value SLIV for each time-domain allocation, and wherein each set of PUSCH transport configurations spans multiple TTIs; Receive downlink control information (DCI) messages from the network entity, wherein the DCI messages include a time-domain resource allocation (TDRA) field and a corresponding priority level associated one-to-one with each PUSCH transmission within a PUSCH transmission burst, wherein the value of the TDRA indicates a row index of the data structure, and wherein the row index is associated with a set of PUSCH transmission configurations included in the data structure; and Perform PUSCH transmissions across multiple TTIs on unlicensed frequency bands according to a set of indicated PUSCH transmission configurations.

7. The apparatus according to claim 6, The indicated set of PUSCH transport configurations includes the transport gaps between each PUSCH transport indicated by the set of PUSCH transport configurations.

8. The apparatus according to claim 6, The set of PUSCH transport configurations indicated does not include the transport gaps between each PUSCH transport indicated by the set of PUSCH transport configurations.

9. The apparatus according to claim 6, The network entity described therein operates according to the 3GPP 5G NR Radio Access Technology (RAT).

10. The apparatus according to claim 6, Each PUSCH transport configuration group includes one or more PUSCH transport configurations.

11. A method performed by a user equipment (UE), comprising: Execute Radio Resource Control (RRC) signaling with network entities to configure a data structure, wherein each line of the data structure includes a set of Physical Uplink Shared Channel (PUSCH) transport configurations, wherein the data structure is defined using the abstract syntax notation ASN.1 and includes a PUSCH time-domain allocation list parameter, wherein the PUSCH time-domain allocation list parameter specifies the maximum number of PUSCH transport allocations and specifies a K2 value, a PUSCH mapping type, and a start and length indication value SLIV for each time-domain allocation, and wherein each set of PUSCH transport configurations spans multiple TTIs; Receive downlink control information (DCI) messages from the network entity, wherein the DCI messages include a time-domain resource allocation (TDRA) field and a corresponding priority level associated one-to-one with each PUSCH transmission within a PUSCH transmission burst, wherein the value of the TDRA indicates a row index of the data structure, and wherein the row index is associated with a set of PUSCH transmission configurations included in the data structure; and Perform PUSCH transmissions across multiple TTIs on unlicensed frequency bands according to a set of indicated PUSCH transmission configurations.

12. The method according to claim 11, Each PUSCH transport configuration group includes one or more PUSCH transport configurations.

13. The method according to claim 11, The PUSCH mapping type indicates either slot-based scheduling or micro-slot-based scheduling.

14. The method of claim 11, further comprising: Indicates the maximum number of PUSCH transport configurations, wherein the maximum number of PUSCH transport configurations is determined at least in part based on a balance between DCI message overhead and DCI message payload size.

15. The method according to claim 11, The maximum number of PUSCH transport configurations is predefined, and the maximum number of PUSCH transport configurations is determined at least in part based on a balance between DCI message overhead and DCI message payload size.

16. The method according to claim 11, The indicated set of PUSCH transport configurations includes the transport gaps between each PUSCH transport indicated by the set of PUSCH transport configurations.

17. The method according to claim 11, The set of PUSCH transport configurations indicated does not include the transport gaps between each PUSCH transport indicated by the set of PUSCH transport configurations.

18. The method according to claim 11, The network entity described therein operates according to the 3GPP 5G NR Radio Access Technology (RAT).

19. A non-transitory computer-readable storage medium storing program instructions that can be executed by processing circuitry to cause a user equipment device (UE) to perform the method as described in any one of claims 11-18.

20. A computer program product comprising program instructions executable by processing circuitry to cause a user equipment device (UE) to perform the method as described in any one of claims 11-18.

Images