Scheduling of transmission time intervals

Abstract

This application relates to scheduling of transmission time intervals. Disclosed are devices, methods, and systems for scheduling transmission time intervals. A device (300) includes a processor (302) that determines (1002) a first semi-persistent scheduling resource allocation indicating a resource group comprising a plurality of time domain resources. Each time domain resource of the plurality of time domain resources has a first transmission time interval length. Further, the processor (302) determines (1004) a second semi-persistent scheduling resource allocation indicating a resource group comprising a plurality of time domain resources. Each time domain resource of the plurality of time domain resources has a second transmission time interval length, and the first transmission time interval length is different from the second transmission time interval length. The device (300) includes a transmitter (310) that transmits (1006) the first semi-persistent scheduling resource allocation using a first semi-persistent scheduling identifier, and transmits (1008) the second semi-persistent scheduling resource allocation using a second semi-persistent scheduling identifier.

Description

[0001] This application is a divisional application of Chinese invention patent application "Scheduling of Transmission Time Intervals", which entered the Chinese national phase on October 10, 2018, with PCT application number PCT / US2017 / 022360, international filing date of March 14, 2017, and Chinese application number 201780022762.3.

[0002] Cross-reference of related applications

[0003] This application is a non-provisional application filed on April 12, 2016, by Hossein Bagheri et al., entitled “SCHEDULING OFTRANSMISSION TIME INTERVALS”, with the entire contents of which are incorporated herein by reference. Technical Field

[0004] The topics disclosed in this article generally relate to wireless communication, and in particular to the scheduling of transmission time intervals (TTI) in wireless communication systems. Background Technology

[0005] In wireless communication networks, a LTE (Long Term Evolution) Frequency Division Duplex (FDD) frame structure can be used. Alternatively, a Time Division Duplex (FDD) frame structure can be used. A 10-millisecond (ms) radio frame can comprise 10 subframes, each 1ms long. Each subframe can also include two time slots, each 0.5ms long. Within each time slot, multiple Orthogonal Frequency Division Multiplexing (OFDM) symbols can be transmitted. The signal transmitted in each time slot at the antenna port can be transmitted via... Subcarriers and The resource grid is described by OFDM symbols, where These are multiple resource blocks (RBs) in the downlink (DL) (depending on the cell's transmission bandwidth); It represents the number of subcarriers in each RB; each subcarrier occupies a certain frequency Δf. Δf, and The value can depend on the cyclic prefix shown in Table 1.

[0006] Table 1

[0007]

[0008] In some configurations, an antenna port may refer to a logical antenna port (i.e., it does not necessarily represent a physical antenna or antenna element). The mapping between an antenna port and one or more physical antenna elements (or elements) can vary depending on the implementation. In other words, different devices may have different mappings of physical antenna elements (or elements) to the same antenna port. A receiving device may assume that signals transmitted on the same antenna port travel through the same channel. Conversely, a receiving device cannot assume that signals transmitted on different antenna ports travel through the same channel.

[0009] In some wireless communication networks, the Transmission Time Interval (TTI) can be 1 ms. In other wireless communication networks, such as those using a shortened TTI (s-TTI), the s-TTI can be less than 1 ms. Semi-persistent scheduling (SPS) can be used in such networks. Scheduling conflicts may occur in some wireless communication networks. Summary of the Invention

[0010] A device for scheduling transmission time intervals is disclosed. Furthermore, methods and systems perform the functions of the device. In one embodiment, the device includes a processor that determines a first semi-persistent scheduling resource allocation indicating a first set of resources, the first set of resources including a first plurality of time-domain resources. In this embodiment, each of the first plurality of time-domain resources has a first transmission time interval length. Furthermore, the processor determines a second semi-persistent scheduling resource allocation indicating a second set of resources, the second set of resources including a second plurality of time-domain resources. In this embodiment, each of the second plurality of time-domain resources has a second transmission time interval length, and the first transmission time interval length is different from the second transmission time interval length. In some embodiments, the device includes a transmitter that transmits the first semi-persistent scheduling resource allocation using a first semi-persistent scheduling radio network identifier, and transmits the second semi-persistent scheduling resource allocation using a second semi-persistent scheduling radio network identifier.

[0011] In some embodiments, the method includes determining a first semi-persistent scheduling resource allocation indicating a first set of resources, the first set of resources including a first plurality of time-domain resources. In this embodiment, each of the first plurality of time-domain resources has a first transmission time interval length. Furthermore, the method includes determining a second semi-persistent scheduling resource allocation indicating a second set of resources, the second set of resources including a second plurality of time-domain resources. In this embodiment, each of the second plurality of time-domain resources has a second transmission time interval length, and the first transmission time interval length is different from the second transmission time interval length. The method includes transmitting the first semi-persistent scheduling resource allocation using a first semi-persistent scheduling radio network identifier. Furthermore, the method includes transmitting the second semi-persistent scheduling resource allocation using a second semi-persistent scheduling radio network identifier.

[0012] In some embodiments, the first semi-persistent scheduling radio network identifier and the second semi-persistent scheduling radio network identifier are the same. In some embodiments, the first semi-persistent scheduling radio network identifier and the second semi-persistent scheduling radio network identifier are different. In various embodiments, the first and second semi-persistent scheduling resource allocations are used for uplink transmission. In one embodiment, the first and second semi-persistent scheduling resource allocations are used for downlink transmission. In some embodiments, the method includes determining the location of the first semi-persistent scheduling resource allocation based on a first number of symbols, and determining the location of the second semi-persistent scheduling resource allocation based on a second number of symbols. In some embodiments, the method includes transmitting information indicating the location in a subframe for one or more of a semi-persistent scheduling activation and deactivation command. In various embodiments, the method includes transmitting information indicating one or more of a semi-persistent scheduling activation and deactivation command at a predetermined location in the subframe.

[0013] Another device includes a receiver that receives an indication of a first semi-persistent scheduling resource allocation for a first set of resources, the first set of resources comprising a first plurality of time-domain resources. In this embodiment, each of the first plurality of time-domain resources has a first transmission time interval length. Furthermore, the receiver receives an indication of a second semi-persistent scheduling resource allocation for a second set of resources, the second set of resources comprising a second plurality of time-domain resources. In this embodiment, each of the second plurality of time-domain resources has a second transmission time interval length, and the first transmission time interval length is different from the second transmission time interval length. The device includes a processor that determines the first semi-persistent scheduling resource allocation using a first semi-persistent scheduling radio network identifier and determines the second semi-persistent scheduling resource allocation using a second semi-persistent scheduling radio network identifier.

[0014] Another method includes receiving an indication of a first semi-persistent scheduling resource allocation for a first group of resources, the first group of resources comprising a first plurality of time-domain resources. In this embodiment, each of the first plurality of time-domain resources has a first transmission time interval length. The method includes receiving an indication of a second semi-persistent scheduling resource allocation for a second group of resources, the second group of resources comprising a second plurality of time-domain resources. In this embodiment, each of the second plurality of time-domain resources has a second transmission time interval length, and the first transmission time interval length is different from the second transmission time interval length. Furthermore, the method includes determining the first semi-persistent scheduling resource allocation using a first semi-persistent scheduling radio network identifier. The method includes determining the second semi-persistent scheduling resource allocation using a second semi-persistent scheduling radio network identifier.

[0015] In one embodiment, a first semi-persistent scheduling resource allocation is used for uplink transmission, and the method further includes receiving a deactivation command, determining at least one time-domain resource of a first plurality of time-domain resources, and in response to receiving the deactivation command, deactivating semi-persistent scheduling-related data transmission on at least one time-domain resource of the first plurality of time-domain resources.

[0016] In some embodiments, the deactivation command is a first deactivation command, and the method further includes receiving a second deactivation command, and in response to receiving the second deactivation command, deactivating semi-persistent scheduling related data transmission until a semi-persistent scheduling activation command or a semi-persistent scheduling reactivation command is received. In various embodiments, the first transmission time interval length corresponds to a first number of symbols, and the second transmission time interval length corresponds to a second number of symbols.

[0017] Another method includes receiving a first semi-persistent scheduling resource allocation indicating a first set of periodic time-domain resources. In this embodiment, each resource in the first set of periodic time-domain resources has a first transmission time interval length. Furthermore, the method includes determining a first resource of the first set of periodic time-domain resources that overlaps with resources used for transmissions based on a second transmission time interval length. The method also includes determining a second resource of the first transmission time interval length that does not overlap with resources used for transmissions based on the second transmission time interval length. Additionally, the method includes using the second resource for semi-persistent scheduling-related data transmissions and not using the first resource for such data transmissions. In this embodiment, the first transmission time interval length and the second transmission time interval length are different.

[0018] In one embodiment, the method includes receiving a message indicating resources for transmission based on a second transmission time interval length. In some embodiments, the first transmission time interval length corresponds to a shortened transmission time interval length, and the second transmission time interval length corresponds to a conventional transmission time interval length, wherein the shortened transmission time interval length is less than the conventional transmission time interval length. In various embodiments, the method includes determining a second resource based on a first set of periodic time-domain resources.

[0019] In some embodiments, the method includes determining a second resource based on a third set of time-domain resources that do not overlap with a first set of periodic time-domain resources. In one embodiment, the method includes determining the second resource based on time-domain information of the first resource and time-domain information of resources used for transmission based on a second transmission time interval length. In some embodiments, the first semi-persistent scheduling resource allocation includes a bitmap pattern. In various embodiments, the periodicity of the first set of time-domain resources is defined based on multiple transmission time intervals. In some embodiments, the method includes receiving an indication of a third transmission time interval length for the allocation of the first semi-persistent scheduling resource, and determining the periodicity of the first time-domain resource based on the third transmission time interval length. In this embodiment, the first transmission time interval length and the third transmission time interval length are different. Attached Figure Description

[0020] A more detailed description of the embodiments briefly described above is given with reference to specific embodiments illustrated in the accompanying drawings. It should be understood that these drawings illustrate only some embodiments and should not be considered as limiting the scope. The embodiments are described and explained with additional features and details using the drawings, wherein:

[0021] Figure 1 This is a schematic block diagram illustrating one embodiment of a wireless communication system for scheduling transmission time intervals (TTI).

[0022] Figure 2 This is a schematic block diagram illustrating one embodiment of a device that can be used to schedule TTI.

[0023] Figure 3 This is a schematic block diagram illustrating one embodiment of a device that can be used to schedule TTI.

[0024] Figure 4 An embodiment of s-TTI is shown;

[0025] Figure 5 Another embodiment of s-TTI is shown;

[0026] Figure 6 This illustrates an example of TTI scheduling;

[0027] Figure 7 This illustrates another embodiment of TTI scheduling;

[0028] Figure 8 This illustrates yet another embodiment of TTI scheduling;

[0029] Figure 9 This illustrates yet another embodiment of TTI scheduling;

[0030] Figure 10This is a schematic flowchart illustrating one embodiment of a method for scheduling TTI; and

[0031] Figure 11 This is a schematic flowchart illustrating another embodiment of a method for scheduling TTI. Detailed Implementation

[0032] As those skilled in the art will understand, the embodiments can be embodied as systems, devices, methods, or program products. Therefore, embodiments can take the form of entirely hardware embodiments, entirely software embodiments (including firmware, resident software, microcode, etc.), or embodiments combining software and hardware solutions, which are generally referred to herein as “circuit,” “module,” or “system.” Furthermore, embodiments can take the form of program products embodied in one or more computer-readable storage devices storing machine-readable code, computer-readable code, and / or program code (hereinafter referred to as “code”). The storage device can be tangible, non-transitory, and / or non-transferable. The storage device may not contain signals. In one embodiment, the storage device uses only signals for accessing the code.

[0033] Some of the functional units described in this specification may be labeled as modules to more specifically emphasize their implementation independence. For example, modules may be implemented as hardware circuits that include custom-designed very large-scale integrated (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. Furthermore, modules may be implemented in programmable hardware devices such as field-programmable gate arrays, programmable array logic, programmable logic devices, etc.

[0034] Furthermore, modules can be implemented in code and / or software for execution by various types of processors. Identified code modules may, for example, comprise one or more physical or logical blocks of executable code, which may be organized as objects, procedures, or functions. However, the executable files of the identified modules do not need to be physically co-located; instead, they may comprise different instructions stored in different locations that, when logically combined, comprise the module and achieve its stated purpose.

[0035] In practice, a code module can be a single instruction or multiple instructions, and can even be distributed across several different code segments, across different programs, and across several memory devices. Similarly, operational data can be identified and represented within a module, and can be implemented in any suitable form and organized within any suitable data structure. Operational data can be collected as a single dataset or distributed across different locations, including across different computer-readable storage devices. When a module or parts thereof are implemented in software, the software portion is stored on one or more computer-readable storage devices.

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

[0037] More specific examples of storage devices (a non-exhaustive list) include the following: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium can be any tangible medium that can contain or store programs used by or in connection with an instruction execution system, device, or apparatus.

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

[0039] References to "an embodiment," "an embodiment," or similar language throughout this specification, in conjunction with the specific features, structures, or characteristics described in that embodiment, include at least one embodiment. Therefore, unless explicitly stated otherwise, the phrases "in an embodiment," "in one embodiment," and similar language appearing throughout this specification may, but do not necessarily, refer to the same embodiment, but rather to "one or more, but not all, embodiments." Unless explicitly stated otherwise, the terms "including," "comprising," "having," and variations thereof mean "including, but not limited to,". Unless explicitly stated otherwise, the list of items does not indicate that any or all items are mutually exclusive. Unless explicitly stated otherwise, the terms "a," "an," and "the" also mean "one or more".

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

[0041] The embodiments are described below with reference to schematic flowcharts and / or schematic block diagrams of methods, apparatus, systems, and program products according to the embodiments. It should be understood that each block of the schematic flowcharts and / or schematic block diagrams, and combinations of blocks of the schematic flowcharts and / or schematic block diagrams, can be implemented by code. This code can be provided to a processor of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to produce a machine, such that instructions executable via the processor of the computer or other programmable data processing apparatus create means for implementing the functions / actions specified in the blocks or blocks of the schematic flowcharts and / or schematic block diagrams.

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

[0043] In addition, code may be loaded into a computer, other programmable data processing device, or other apparatus to cause a series of operational steps to be performed on the computer, other programmable device, or other apparatus to produce a computer-implemented process, such that the code executing on the computer or other programmable apparatus provides processing for implementing the functions / actions specified in the blocks or blocks of the flowchart and / or block diagram.

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

[0045] Furthermore, it should be noted that in some alternative embodiments, the functions mentioned in the boxes may not occur in the order shown in the figures. For example, two boxes shown consecutively may actually be executed substantially simultaneously, or these boxes may sometimes be executed in reverse order, depending on the functions involved. Other steps and methods can be conceived that are functionally, logically, or effectively equivalent to one or more of the boxes or a portion thereof in the figures shown.

[0046] While various arrow types and line styles may be used in flowcharts and / or block diagrams, it should be understood that they do not limit the scope of the respective embodiments. In fact, some arrows or other connectors may be used only to indicate the logical flow of the illustrated embodiment. For example, an arrow may indicate a waiting or monitoring period between enumerated steps in the illustrated embodiment where no duration is specified. Furthermore, it should be noted that each block in the block diagram and / or flowchart, and combinations of blocks in the block diagram and / or flowchart, may be implemented by a system based on dedicated hardware or a combination of dedicated hardware and code that performs a specific function or action.

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

[0048] Figure 1 An embodiment of a wireless communication system 100 for scheduling transmission time intervals (TTIs) is shown. In one embodiment, the wireless communication system 100 includes a remote unit 102 and a basic unit 104. Although in Figure 1 A specific number of remote units 102 and basic units 104 are shown, but those skilled in the art will recognize that any number of remote units 102 and basic units 104 may be included in the wireless communication system 100.

[0049] In one embodiment, remote unit 102 may include computing devices such as desktop computers, laptop computers, personal digital assistants (PDAs), tablet computers, smartphones, smart TVs (e.g., internet-connected TVs), set-top boxes, game consoles, security systems (including security cameras), in-vehicle computers, network devices (e.g., routers, switches, modems), low-throughput devices, low-latency sensitivity devices, ultra-low-cost devices, low-power devices, or IoT devices. In some embodiments, remote unit 102 includes wearable devices such as smartwatches, fitness bands, optical head-mounted displays, etc. Furthermore, remote unit 102 may be referred to as a subscriber unit, mobile device, mobile station, user, terminal, mobile terminal, fixed terminal, subscriber station, user equipment (UE), user terminal, device, or other terms used in the art. Remote unit 102 may communicate directly with one or more basic units 104 via UL communication signals.

[0050] Basic unit 104 may be distributed across a geographical area. In some embodiments, basic unit 104 may also be referred to as an access point, access terminal, base station, Node B, evolved Node B (eNB), home Node B, relay node, apparatus, or any other term used in the art. Basic unit 104 is typically part of a radio access network, which may include one or more controllers communicatively connected to one or more corresponding basic units 104. The radio access network is typically communicatively connected to one or more core networks, which may be connected to other networks, such as the Internet and the public switched telephone network, among others. These and other elements of the radio access network and core network are not shown but are generally well known to those skilled in the art. For example, one or more basic units 104 may be communicatively connected to a Mobility Management Entity (MME), Serving Gateway (SGW), and / or Packet Data Network (PDN) Gateway (PGW).

[0051] In one embodiment, the wireless communication system 100 conforms to the 3GPP LTE protocol, wherein the basic unit 104 transmits using an OFDM modulation scheme on the uplink (DL), while the remote unit 102 transmits using a single-carrier frequency division multiple access (SC-FDMA) scheme on the uplink (UL). In another embodiment, the wireless communication system 100 conforms to Narrowband Internet of Things (NB-IoT). However, more generally, the wireless communication system 100 may implement other open or proprietary communication protocols, such as WiMAX among others. This disclosure is not intended to limit to any particular wireless communication system architecture or protocol implementation.

[0052] The basic unit 104 can serve multiple remote units 102 within a service area—such as a cell or cell sector—via a wireless communication link. The basic unit 104 transmits DL communication signals in the time domain, frequency domain, and / or spatial domain to serve the remote units 102.

[0053] In one embodiment, a device (e.g., basic unit 104) may determine a first semi-persistent scheduling (SPS) radio network identifier (RNI) for a first resource allocation associated with a first transmission time interval (TTI), the first TTI including a first number of symbols. The RNI may include a network temporary identifier (RNTI). The device may also determine a second SPS RNI for a second resource allocation associated with a second TTI, the second TTI including a second number of symbols different from the first number of symbols. The device may transmit information indicating the first resource allocation using the first SPS RNI and information indicating the second resource allocation using the second SPS RNI. Therefore, SPSs of different sizes can be allocated for multiple TTIs.

[0054] In another embodiment, the device (e.g., remote unit 102) may receive information indicating a first resource allocation associated with a first TTI, the first TTI including a first number of symbols. The device may also receive information indicating a second resource allocation associated with a second TTI, the second TTI including a second number of symbols different from the first number. The device may use a first SPS RNI to determine the first resource allocation. The device may also use a second SPS RNI to determine the second resource allocation. In another embodiment, the device may determine the association of a resource allocation with a TTI length based on the location of the resource allocation. For example, a resource allocation received at a first location or region in a subframe may be associated with the first TTI, while a resource allocation received at a second location or region in a subframe may be associated with the second TTI. The first and second locations or regions may be non-overlapping, and the first and second resource allocations may use the same SPS RNI.

[0055] Figure 2An embodiment of a device 200 for scheduling TTI is shown. Device 200 includes one embodiment of a remote unit 102. Furthermore, the remote unit 102 may include a processor 202, a memory 204, an input device 206, a display 208, a transmitter 210, and a receiver 212. In some embodiments, the input device 206 and the display 208 are combined into a single device, such as a touchscreen. In some embodiments, the remote unit 102 may not include any input device 206 and / or display 208. In various embodiments, the remote unit 102 may include one or more of the processor 202, memory 204, transmitter 210, and receiver 212, and may not include the input device 206 and / or display 208.

[0056] In one embodiment, processor 202 may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, processor 202 may be a microcontroller, microprocessor, central processing unit (CPU), graphics processing unit (GPU), auxiliary processing unit, field-programmable gate array (FPGA), or similar programmable controller. In some embodiments, processor 202 executes instructions stored in memory 204 to perform the methods and routines described herein. Processor 202 may be communicatively connected to memory 204, input device 206, display 208, transmitter 210, and receiver 212. In some embodiments, processor 202 may use a first SPS RNI to determine a first resource allocation and a second SPS RNI to determine a second resource allocation.

[0057] In one embodiment, memory 204 is a computer-readable storage medium. In some embodiments, memory 204 includes volatile computer storage media. For example, memory 204 may include random access memory (RAM), including dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), and / or static RAM (SRAM). In some embodiments, memory 204 includes non-volatile computer storage media. For example, memory 204 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 204 includes both volatile and non-volatile computer storage media. In some embodiments, memory 204 stores data relating to instructions to be provided to another device. In some embodiments, memory 204 also stores program code and related data, such as an operating system or other controller algorithms operating on remote unit 102.

[0058] In one embodiment, input device 206 may include any known computer input device, including a touchpad, button, keyboard, stylus, microphone, etc. In some embodiments, input device 206 may be integrated with display 208, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, input device 206 includes a touchscreen, enabling text input using a virtual keyboard displayed on the touchscreen and / or by handwriting on the touchscreen. In some embodiments, input device 206 includes two or more different devices, such as a keyboard and a touchpad.

[0059] In one embodiment, display 208 may include any known electronically controllable display or display device. Display 208 may be designed to output visual, auditory, and / or tactile signals. In some embodiments, display 208 includes an electronic display capable of outputting visual data to a user. For example, display 208 may include, but is not limited to, a liquid crystal display (LCD), a light-emitting diode (LED) display, an organic light-emitting diode (OLED) display, a projector, or similar display devices capable of outputting images, text, etc., to a user. As another non-limiting example, display 208 may include wearable displays, such as smartwatches, smart glasses, heads-up displays, etc. Furthermore, display 208 may be a component of a smartphone, personal digital assistant, television, desktop computer, laptop computer, personal computer, vehicle dashboard, etc.

[0060] In some embodiments, display 208 includes one or more speakers for generating sound. For example, display 208 may generate audible alarms or notifications (e.g., buzzers or musical sounds). In some embodiments, display 208 includes one or more haptic devices for generating vibration, motion, or other haptic feedback. In some embodiments, all or part of display 208 may be integrated with input device 206. For example, input device 206 and display 208 may form a touchscreen or similar touch-sensitive display. In other embodiments, display 208 may be located near input device 206.

[0061] Transmitter 210 provides UL communication signals to base unit 104, while receiver 212 receives information indicating a first resource allocation associated with a first TTI, the first TTI including a first number of symbols. In some embodiments, receiver 212 receives information indicating a second resource allocation associated with a second TTI, the second TTI including a second number of symbols different from the first number of symbols. In one embodiment, transmitter 210 transmits feedback information and / or indications to base unit 104. Although only one transmitter 210 and one receiver 212 are shown, remote unit 102 may include any suitable number of transmitters 210 and receivers 212. Transmitters 210 and receivers 212 can be of any suitable type. In one embodiment, transmitters 210 and receivers 212 may be part of a transceiver.

[0062] Figure 3 An embodiment of a device 300 that can be used to schedule TTIs is shown. Device 300 includes one embodiment of a basic unit 104. Furthermore, the basic unit 104 may include a processor 302, a memory 304, an input device 306, a display 308, a transmitter 310, and a receiver 312. It should be noted that the processor 302, memory 304, input device 306, and display 308 may be substantially similar to the processor 202, memory 204, input device 206, and display 208 of the remote unit 102, respectively. In some embodiments, the processor 302 may be used to determine a first SPS RNI associated with a first resource allocation for a first TTI, the first TTI including a first number of symbols. In some embodiments, the processor 302 may be used to determine a second SPS RNI associated with a second resource allocation for a second TTI, the second TTI including a second number of symbols different from the first number of symbols.

[0063] Transmitter 310 is used to provide DL communication signals to remote unit 102, and receiver 312 is used to receive UL communication signals from remote unit 102. In some embodiments, transmitter 310 is used to transmit information indicating a first resource allocation using a first SPS RNI, and to transmit information indicating a second resource allocation using a second SPS RNI. It should be noted that in some embodiments, MME, SGW, and / or PGW may include one or more components found in base unit 104. Furthermore, in some embodiments, base unit 104 may represent an embodiment of MME, SGW, or PGW.

[0064] Figure 4An embodiment of the s-TTI 400 using a normal cyclic prefix is ​​shown as an example. In the illustrated embodiment, each s-TTI is half the length of a standard 1 ms TTI. Therefore, each s-TTI is 0.5 ms. As shown, each s-TTI includes seven OFDM symbols 402. Figure 5 Another embodiment of s-TTI 500 is shown, using a normal cyclic prefix as an example. In this embodiment, some s-TTIs include four OFDM symbols 402, and some s-TTIs include three OFDM symbols 402. It should be noted that s-TTIs can include any number of OFDM symbols 402 smaller than the standard size TTI. In this disclosure, a UE configured to use s-TTI may be referred to as an s-UE (e.g., remote unit 102), while a UE not configured to use s-TTI may be referred to as a conventional UE. In some embodiments, the subcarrier spacing and cyclic prefix length may be common to both conventional and s-UEs.

[0065] In some configurations, dynamic scheduling may be advantageous for bursty, infrequent, and bandwidth-intensive data transmissions (e.g., web surfing, video streaming, email). However, dynamic scheduling may be less suitable for real-time streaming. Semi-persistent scheduling (SPS) is a transmission method that limits the transmission mode rather than scheduling individual uplink or downlink transmissions. In some embodiments, SPS can reduce scheduling allocation overhead and enable data communication with lower latency because it does not require obtaining / generating scheduling allocation information for individual transmissions. SPS operation combined with s-TTI can further reduce scheduling allocation overhead. It should be noted that the transmissions from remote unit 102 can be received by one or more base stations or other remote units 102 in the communication network.

[0066] In some LTE systems, base unit 104 can be configured and / or reconfigured by radio resource control (RRC) at any time using SPS configuration (SPS-Config) to SPS configure and / or reconfigure remote unit 102. SPS-Config may include configurations for the SPS cell radio network temporary identifier (C-RNTI) (SPS-C-RNTI), SPS downlink configuration (SPS-ConfigDL), and / or SPS uplink configuration (SPS-ConfigUL). When SPS is configured in either the UL or DL ​​direction, the SPS C-RNTI can be provided by base unit 104. After the remote unit 102 is configured with the SPS C-RNTI, it can be configured at higher layers to decode the physical downlink control channel (PDCCH) using a cyclic redundancy code (CRC) scrambled with the SPS C-RNTI. In each subframe, remote unit 102 can monitor PDCCH using CRC scrambled by SPS C-RNTI, because basic unit 104 can activate, reactivate and / or release SPS at any time using downlink control information (DCI).

[0067] When s-TTI is enabled in the system, remote unit 102 can be configured to use different TTI lengths for different packet types (e.g., 1ms TTI for voice packets, 0.5ms TTI for packets with low latency requirements, and 2-symbol TTI for packets with ultra-low latency requirements). Therefore, remote unit 102 can be configured with more than one SPS configuration, and each SPS configuration can have a different TTI length (e.g., an SPS configuration using 1ms TTI for voice, another SPS configuration for s-TTI = 2 symbols, and yet another SPS configuration for s-TTI = 0.5ms).

[0068] In some embodiments, various methods can be used for UL and DL to achieve multiple SPS configurations with different TTI lengths.

[0069] For example, in one embodiment, each SPS configuration of remote unit 102 corresponds to a different TTI length and has its own corresponding SPS-C-RNTI. For each TTI length that remote unit 102 is configured to use, remote unit 102 can receive the SPS configuration via dedicated RRC signaling. Each SPS configuration RRC signal contains its own SPS-C-RNTI. For example, in each s-TTI of monitoring control information, base unit 104 can scramble the PDCCH (e.g., enhanced PDCCH (EPDCCH)) corresponding to that TTI length using a CRC scrambled with the SPS-C-RNTI associated with the SPS configuration of the TTI length. In each s-TTI of monitoring control information, remote unit 102 can monitor the PDCCH using a CRC scrambled with the SPS-C-RNTI.

[0070] As another example, in some embodiments, all SPS configurations of remote unit 102 can use the same SPS-C-RNTI. For each TTI length configured to be used, remote unit 102 can receive the SPS configuration via dedicated RRC signaling. Each SPS configuration RRC signal contains the same SPS-C-RNTI. In each s-TTI of monitoring control information, base unit 104 can scramble the PDCCH corresponding to the TTI length using a CRC scrambled with the same SPS-C-RNTI. In some embodiments, for s-TTIs, control information about s-TTI operation can be transmitted in two parts for SPS. In such embodiments, one or both parts can be scrambled using SPS-C-RNTI. For example, the two-part transmission may include transmissions for activation, release, verification, etc. In each s-TTI of monitoring control information, remote unit 102 can monitor the PDCCH using a CRC scrambled with SPS-C-RNTI.

[0071] In some embodiments, such as when all SPS configurations use the same SPS-C-RNTI, remote unit 102 may need to distinguish which control commands are used for which SPS configuration. Certain control commands may be sent to activate and / or deactivate the SPS, or to change the frequency resource allocation of the SPS. For example, if remote unit 102 is configured for two SPS operations: one with a TTI length of 1 ms and the other with a TTI length of 2 symbols, then upon receiving a PDCCH scrambled with SPS-C-RNTI, remote unit 102 may need to determine whether the PDCCH command is for the SPS with a TTI length of 1 ms or for the SPS with a TTI length of 2 symbols.

[0072] In one embodiment, remote unit 102 can infer which SPS configuration the control command points to based on the location of the received control command. For example, if the TTI in which the PDCCH command is received is OFDM symbol 4, then the command may not be for a 1ms TTI, but for an s-TTI starting with symbol 4. In some embodiments, the time-frequency location of the PDCCH command can be used to indicate which SPS configuration the control command points to. In this embodiment, remote unit 102 can receive an indication of such a usable time-frequency location. In some embodiments, the remote unit can determine the association between the SPS configuration and the TTI length based on the location of the PDCCH control message. For example, a control message received in a first location or region in a subframe may be associated with the SPS configuration of a first TTI, while a control message received in a second location or region in a subframe may be associated with the SPS configuration of a second TTI. The first location or region and the second location or region may not overlap.

[0073] In another embodiment, the control command may have a new field indicating the length of the TTI corresponding to the SPS configuration. In some embodiments, the field may use a predetermined combination of other fields in the control command to indicate the length of the TTI corresponding to the SPS configuration.

[0074] In certain configurations, such as when multiple SPS configurations use a single SPS-C-RNTI, SPS reconfiguration can be avoided and / or reduced if the s-TTI length changes. In one embodiment, RRC reconfiguration can be avoided and / or reduced if the s-TTI length changes (e.g., from a 2-symbol TTI to a 0.5ms TTI). For example, if remote unit 102 is configured with an SPS corresponding to a 2-symbol TTI and the s-TTI length changes to 0.5ms, then if the SPS configuration is a function of the TTI length, and only the TTI length changes in the SPS scheme, RRC reconfiguration can be avoided and / or reduced. For example, if the s-TTI length becomes 0.5ms, and SPS-Interval = 10 TTI is used for remote unit 102 configured with s-TTI = 2 symbols (i.e., SPS-Interval = 2 symbols), then SPS-Interval = 10 TTI, but now equals 5ms.

[0075] In some embodiments, control commands and / or higher-level commands (e.g., Media Access Control (MAC) Control Element (CE) (MAC-CE) or RRC commands) indicate to remote unit 102 that the TTI length has been changed. For example, SPS activation and / or SPS reactivation commands may be sent. In various embodiments, an SPS release control command may be sent, and then an SPS activation command may be sent again once remote unit 102 has been informed that the TTI length has been changed.

[0076] In one embodiment, when different SPS configurations correspond to different TTI lengths, the network and / or base unit 104 can notify the remote unit 102 which control commands are for which SPS configuration.

[0077] In some embodiments, the network and / or basic unit 104 may indicate a first SPS radio network identifier (RNI) for a first resource allocation via a first set of higher-layer configured SPS parameters associated with a first TTI length of a first SPS transport set. In this embodiment, the higher layer may be above the physical layer, the first transport set spans the first TTI length, and the first TTI length includes a first number of symbols.

[0078] In some embodiments, network and / or base unit 104 may indicate a second SPS RNI for the second resource allocation via a second set of higher-layer configuration SPS parameters associated with a second TTI length of the second SPS transport set. In this embodiment, the higher layer is above the physical layer, the second transport set spans a second TTI length, the second TTI length includes a second number of symbols, and the second number is different from the first number. In various embodiments, network and / or base unit 104 may use a first SPS RNI to transmit a first resource allocation and use a second SPS RNI to transmit a second resource allocation.

[0079] In one embodiment, the CRC bits of each resource allocation are scrambled using a sequence initialized with the corresponding RNI. In some embodiments, the first SPS RNI and the second SPS RNI are the same. In other embodiments, the first SPS RNI and the second SPS RNI are different. In various embodiments, the first and second resource allocations are used for UL transmission. In some embodiments, the first and second resource allocations are used for DL ​​transmission. In one embodiment, the network and / or base unit 104 determines the location of the SPS resource allocation based on the TTI length. In some embodiments, the network and / or base unit 104 signals a set of possible time and / or frequency locations to the means of signaling for SPS resource allocations of the first and second TTI lengths. For example, the frequency locations of PDCCH commands may be different, and such frequency locations may be signaled to the remote unit 102.

[0080] In some embodiments, activation and / or release commands for SPS resources can be instructed to remote unit 102 using resource allocation commands. Remote unit 102 can verify the activation and / or release commands.

[0081] In some embodiments, the configuration of SPS does not necessarily enable remote unit 102 to begin using SPS licensing and / or allocation. For example, base unit 104 may explicitly activate SPS to enable remote unit 102 to use SPS licensing and / or allocation.

[0082] In the event of incorrect SPS activation, remote unit 102 may use the reproduction resource for an extended period, potentially interfering with normal data transmission. Therefore, various methods can be used to activate SPS to prevent incorrect activation. In some embodiments, base unit 104 can explicitly release SPS without releasing the SPS RRC configuration.

[0083] In one example, remote unit 102 can be configured with two SPS configurations: one with a 1ms TTI and one with a 2-symbol TTI. In this example, no SPS configuration is activated for remote unit 102. If network and / or base unit 104 wants to activate the second SPS (i.e., the SPS with TTI = 2 symbols) for remote unit 102, then network and / or base unit 104 sends a control command to remote unit 102. In embodiments using the same SPS-C-RNTI configuration for remote unit 102 with different TTI lengths, to avoid erroneously activating the wrong SPS (i.e., the SPS with a 1ms TTI length), the following can be used: Figure 6 The SPS allocation verification process described above.

[0084] Figure 6An embodiment of TTI scheduling 600 is shown. A subframe 601 has a length of 1 ms 602. Subframe 601 includes 14 symbols, each symbol having a length of 1 / 14 ms 604. The SPS allocation verification process for the SPS configuration corresponding to the s-TTI length may include, whereby the SPS activation and / or release command may appear only during a certain s-TTI index (here referred to as s_indx) within the 1 ms subframe. For example, s_indx can be selected such that SPS commands for 1 ms and 2-symbol TTI lengths do not appear in the same symbol: in other words, when the s-TTI within the subframe starts with 1, s_indx is selected to be greater than 1. Other variations are possible (e.g., selecting s_indx such that it avoids all configurations of SPS with a TTI length different from the TTI length of the SPS of s_indx). In the illustrated embodiment, the first s-indx 606 may correspond to a possible location for SPS activation and / or deactivation for a 1ms TTI (e.g., any combination of the three symbols of the first s-indx 606 can be used for SPS activation and / or deactivation for a 1ms TTI), the second s-indx 608 may correspond to a possible location for SPS activation and / or deactivation for a 2-symbol TTI (e.g., any combination of the nine symbols of the second s-indx 608 can be used for SPS activation and / or deactivation for a 2-symbol TTI), and the third s-indx 610 may correspond to a possible location for SPS activation and / or deactivation for a 0.5ms TTI (e.g., any combination of the two symbols of the third s-indx 610 can be used for SPS activation and / or deactivation for a 0.5ms TTI). In some embodiments, s_indx may be fixed in the specification for each TTI length, or may be indicated to the remote unit 102 via higher-layer signaling.

[0085] Figure 7 Another embodiment of the TTI scheduling 700 is shown. Specifically, Figure 7 An embodiment of an SPS scenario is shown, where s-TTI occurs in a subframe where s-TTI operation is not permitted. A subframe 701 has a length of 1 ms 702. Two other subframes 703, each 1 ms long, comprise seven partitions, each partition having a length of 1 / 7 ms 704.

[0086] Some embodiments can achieve lower latency operation and can reserve some subframes (e.g., subframe 701) for conventional TTI operations (e.g., conventional subframes only). In this embodiment, s-TTI operations may not be performed in these subframes. Because SPS resources can appear periodically, the SPS used for s-TTI operations can be consistent with conventional subframes only.

[0087] In one embodiment, base unit 104 can send a PDCCH control command to temporarily release the SPS, and when such consistency is no longer present, base unit 104 can send a control command to reactivate the SPS.

[0088] In another embodiment, basic unit 104 can perform "opportunistic muting" of pre-configured SPS resources. For example, basic unit 104 can send two different types of deactivation commands: a first deactivation command and a second deactivation command. The first deactivation command is a temporary command 710 applied to only one subframe (i.e., deactivating SPS in a single 1ms subframe), and the second deactivation command is a periodic command and / or reactivation command that deactivates until the next activation. Figure 7 As shown, subframe 703 may include an SPS for the TTI, which is deactivated via temporary command 710 to skip subframe 701 and then resume after subframe 701. The system may operate only for a single TTI length, such as conventional TTI operation or s-TTI operation, or both conventional TTI and s-TTI operation.

[0089] In some embodiments, two types of deactivation commands can be distinguished based on at least one field in the command that is set to different values ​​for the two commands. In some embodiments, the two types of deactivation commands can be distinguished based on the location where they are sent. For example, if the command is sent in one time-frequency region, it means that the command is a first type of deactivation command, and if the command is sent in another time-frequency region, it means that the command is a second type of deactivation command.

[0090] In some embodiments, a temporary command 710 may be sent before subframe 701, where SPS transmission is not permitted. The timing of such a command (relative to subframes where s-TTI operation is not permitted) may be specified in the specification. For example, a command may not be sent if less than four s-TTIs have elapsed before the start of only conventional subframe 701.

[0091] Figure 8 This illustrates yet another embodiment of the TTI scheduling 800. Specifically, Figure 8 Another embodiment of an SPS scenario is shown, where s-TTI occurs in subframes where s-TTI operation is not permitted. Each subframe has a length of 1 ms 802. Subframes including effectively scheduled SPS events may include 7 partitions, each partition having a length of 1 / 7 ms 804. Specifically, subframe 806 includes effectively scheduled SPS events 808. SPS events 810 are scheduled during subframe 812, which is a conventional-only subframe where SPS events 810 are not permitted. Subframe 814 in the illustrated embodiment allows SPS events but does not include any scheduled SPS events.

[0092] Some embodiments can facilitate "rule-based SPS scenarios." In a rule-based SPS scenario, remote unit 102 can skip SPS event 810 in only conventional subframe 812. The next SPS scenario can be determined by a bitmap in the SPS scheme and / or specification. For example, as shown, the next SPS scenario could be a normal scheduled SPS event 808 following the skipped SPS event 810.

[0093] Figure 9 This illustrates yet another embodiment of the TTI scheduling 900. Specifically, Figure 9 Another embodiment of SPS is shown, where s-TTI occurs in subframes where s-TTI operation is not permitted. Each subframe has a length of 1 ms (902). Subframes including validly scheduled SPS events may comprise 7 partitions, each with a length of 1 / 7 ms (904). Specifically, subframe 906 includes validly scheduled SPS events (908). SPS events (910) are scheduled during subframe 912, which is a conventional-only subframe where SPS events (910) are not permitted. Subframe 914 in the illustrated embodiment allows SPS events but does not include any scheduled SPS events.

[0094] In various embodiments, occasions not belonging to the SPS occasion set (i.e., SPS schemes and / or bitmaps) can be used as alternative SPS occasions to SPS occasions that are interfered with by only conventional subframes. Such alternative SPS occasions can be deterministic functions of SPS configuration and skipped SPS occasions. For example, an alternative SPS occasion could be the first s-TTI location outside of conventional subframes. As another example, an alternative SPS occasion could use the same s-TTI index as the s-TTI that is skipped in the next subframe that allows both conventional and s-TTI operations (e.g., alternative SPS event 916 used because SPS event 910 is skipped).

[0095] In some embodiments, in order to reduce control overhead and remote unit 102 processing for PDCCH, SPS-C-RNTI for lower latency operation may be processed only in certain s-TTI (e.g., in the first case in a subframe that coincides with the 1ms TTIPDCCH control region in the time domain).

[0096] In one embodiment, when the device’s s-TTI SPS resource (occasion) appears in a subframe where s-TTI operation is not permitted (SPS resources are periodic, and therefore such events are possible), the network and / or base unit 104 may notify the device not to use the SPS resource and / or the occasion.

[0097] In some embodiments, the method may include indicating to the device a first indication corresponding to determining an SPS resource allocation for a first set of resources to be used for a first set of transmissions using a first TTI. In various embodiments, the method may include indicating to the device a second indication corresponding to a second set of resources to be used for a second set of transmissions using a second TTI. In this embodiment, a subset of the first set of transmissions may overlap with the second transmissions in time. In one embodiment, the method may include indicating to the device an indication not to use (e.g., ignore, discard) a subset of the first set of transmissions.

[0098] In one embodiment, the first group of transmissions is used for s-TTI and / or lower latency, and the second transmission using the second TTI is a periodic 1ms subframe transmission. In some embodiments, a subset of the first group of transmissions corresponds to transmissions belonging to a single subframe. In one embodiment, the third indication is a physical layer indication. In various embodiments, the first group of transmissions and the second transmission are UL transmissions, and the third indication is a higher layer indication. In various embodiments, the first group of transmissions and the second transmission are UL transmissions, and the third indication is an implicit indication to discard a subset of the first group of transmissions. In one embodiment, the first TTI length is 1ms.

[0099] In some embodiments, there may be conventional SPS conflicts with s-TTI. In some LTE systems, dynamic scheduling of maximum effort data may occur on top of SPS, but SPS allocation may take precedence over scheduling conflicts.

[0100] However, if remote unit 102 is configured with an SPS corresponding to a 1ms TTI in the UL, and remote unit 102 receives dynamic grants for s-TTIs with conflicting times and / or time-frequency resources with SPS resources, then remote unit 102 may prioritize low-latency data transmission if low-latency data transmission is configured to drop 1ms SPS transmissions via higher-level configuration; otherwise, it may prioritize 1ms SPS transmissions. In one embodiment, in the case of resource conflicts, priority rules may be fixed in the specification, for example, SPS takes precedence over dynamic scheduling; for a given scheduling type (dynamic or SPS), s-TTI operations take precedence over conventional TTI operations; SPS using conventional TTI takes precedence over dynamic scheduling using s-TTI; and / or SPS using s-TTI takes precedence over dynamic scheduling using conventional TTI.

[0101] In one embodiment, for example, a device in UL may take precedence over a transmission on a second transmission (one of which is a transmission corresponding to SPS operation).

[0102] In some embodiments, a method on the device may include transmitting a first transmission in the UL using a first TTI in a first resource, and discarding (e.g., not transmitting) a second UL transmission using a second TTI corresponding to a second SPS for a third time period. In this embodiment, the first and second resources may overlap in time during the third time period. In various embodiments, the device may be configured via a higher layer to discard the second UL transmission.

[0103] In some embodiments, the SPS may have an aperiodic pattern. For example, an SPS occasion may follow an aperiodic pattern (e.g., a bitmap pattern) indicated to the device, such as via higher-layer signaling (e.g., RRC signaling). In one embodiment, the SPS pattern may be a bitmap pattern indicated via higher-layer signaling. In some embodiments, the SPS occasion is indicated to the device via a bitmap through higher-layer signaling. In another embodiment, the indication may include a first period lasting a first time period, and a second period lasting a second time period, for example, after the end of the first time period. The first period may be shorter than the second period.

[0104] Figure 10 This is a schematic flowchart illustrating one embodiment of a method 1000 for scheduling TTI. In some embodiments, method 1000 is performed, for example, by a device such as basic unit 104. In some embodiments, method 1000 can be performed by a processor that executes program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0105] Method 1000 may include determining 1002 a first SPS RNI for a first resource allocation associated with a first TTI including a first number of symbols. Furthermore, method 1000 may include determining 1004 a second SPS RNI for a second resource allocation associated with a second TTI, the second TTI including a second number of symbols different from the first number of symbols. Method 1000 may include transmitting 1006 information using the first SPS RNI to indicate the first resource allocation. Method 1000 may include transmitting 1008 information using the second SPS RNI to indicate the second resource allocation.

[0106] Figure 11 This is a schematic flowchart illustrating one embodiment of a method 1100 for scheduling TTI. In some embodiments, method 1100 is performed, for example, by a device such as remote unit 102. In some embodiments, method 1100 can be performed by a processor that executes program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0107] Method 1100 may include receiving 1102 information indicating a first resource allocation associated with a first TTI including a first number of symbols. Furthermore, method 1100 may include receiving 1104 information indicating a second resource allocation associated with a second TTI, the second TTI including a second number of symbols different from the first number of symbols. Method 1100 may include determining 1106 the first resource allocation using a first SPSRNI. Furthermore, method 1100 may include determining 1108 the second resource allocation using a second SPSRNI.

[0108] Embodiments may be practiced in other specific forms. These embodiments should be considered illustrative rather than restrictive in all embodiments. Therefore, the scope of the invention is defined by the appended claims rather than the foregoing description. All variations falling within the meaning and equivalents of the claims are covered within their scope.

Claims

1. A method executed by a user equipment, comprising: At the user equipment, a physical layer drop indication is received in the physical layer control channel for a cell, wherein the physical layer drop indication indicates the dropping of uplink transmissions in the resource set; Determine whether to define at least a time to receive the physical layer control channel before a potential uplink transmission that overlaps with the resource set, wherein the resources corresponding to the potential uplink transmission include semi-persistent scheduling resources for shortened transmission time interval operations, and the resource set does not allow shortened transmission time interval operations within the resource set; and In response to determining that the physical layer control channel is received at least a defined time prior to the potential uplink transmission, the potential uplink transmission is discarded based on the physical layer discard indication.

2. The method according to claim 1, wherein, The potential uplink transmission is discarded from the resource set, and the resource set is indicated to the user equipment via the network.

3. The method according to claim 2, wherein, The resource set includes time-frequency resources.

4. The method according to claim 2, wherein, The resource set includes resources associated with semi-persistent licenses.

5. The method according to claim 2, wherein, The resource set has a fixed duration.

6. The method according to claim 2, wherein, A resource is determined for a future uplink transmission to replace the potential uplink transmission, and the resource does not belong to the resource set.

7. The method according to claim 1, wherein, The potential uplink transmission is discarded based on whether the user equipment is configured to discard the potential uplink transmission.

8. The method according to claim 1, wherein, The potential uplink transmission can be transmitted after the time of the potential uplink transmission in the resource indicated by the bitmap.

9. The method of claim 1, further comprising receiving a semi-persistent scheduling activation command indicating frequency resources for semi-persistent scheduling data communication, wherein, The potential uplink transmission is part of the semi-persistent scheduling data communication.

10. The method according to claim 1, wherein, The physical layer control channel is processed at defined time intervals.

11. An apparatus including a user equipment, the apparatus comprising: A receiver that receives a physical layer drop indication in a physical layer control channel for a cell, wherein the physical layer drop indication indicates the dropping of uplink transmissions in a resource set; Processor, the processor: Determine whether to define at least a time to receive the physical layer control channel before a potential uplink transmission that overlaps with the resource set, wherein the resources corresponding to the potential uplink transmission include semi-persistent scheduling resources for shortened transmission time interval operations, and the resource set does not allow shortened transmission time interval operations within the resource set; and In response to determining that the physical layer control channel is received at least a defined time prior to the potential uplink transmission, the potential uplink transmission is discarded based on the physical layer discard indication.

12. The apparatus according to claim 11, wherein, The potential uplink transmission is discarded from the resource set, and the resource set is indicated to the user equipment via the network.

13. The apparatus according to claim 12, wherein, The resource set includes time-frequency resources.

14. The apparatus according to claim 12, wherein, The resource set includes resources associated with semi-persistent licenses.

15. The apparatus according to claim 12, wherein, The resource set has a fixed duration.

16. The apparatus according to claim 12, wherein, A resource is determined for a future uplink transmission to replace the potential uplink transmission, and the resource does not belong to the resource set.

17. The apparatus according to claim 11, wherein, The potential uplink transmission is discarded based on whether the user equipment is configured to discard the potential uplink transmission.

18. The apparatus according to claim 11, wherein, The potential uplink transmission can be transmitted in the resource indicated by the bitmap after the time of one such potential uplink transmission.

19. The apparatus according to claim 11, wherein, The receiver receives a semi-persistent scheduling activation command indicating frequency resources for semi-persistent scheduling data communication, and the potential uplink transmission is part of the semi-persistent scheduling data communication.

20. The apparatus according to claim 11, wherein, The physical layer control channel is processed at defined time intervals.

Images