Application of Uplink Preemption for Random Access Transmission

Abstract

According to some examples, a base station may allocate uplink and / or downlink resources (e.g., in the time domain, frequency domain, spatial domain) to a user equipment (UE) or a group of UEs, and the resources may subsequently be reallocated. For example, the base station may determine a reallocation of uplink resources and may issue a preemption indication (e.g., cancellation indication) that may correspond to at least a portion of the random access resources. The UE may be configured to monitor the preemption indication, and based on the received preemption indication, the UE may determine whether to continue transmitting a random access message using random access resources that at least partially overlap with the resources indicated by the preemption indication. For example, the UE may transmit a random access message or preempt the transmission of a random access message based on the preemption configuration of the UE (e.g., configuration rules for the UE to preempt random access resources).

Description

[0001] Cross-reference

[0002] This patent application claims the benefit of U.S. Provisional Patent Application No. 62 / 888,304, filed Aug. 16, 2019, entitled “Applying Uplink Preemption to Random Access Transmission,” by Yang et al.; and U.S. Patent Application No. 16 / 991,984, filed Aug. 12, 2020, entitled “Applying Uplink Preemption to Random Access Transmission,” by Yang et al.; each of these patents is assigned to the assignee of this patent application. Field of the Disclosure

[0003] The present disclosure generally relates to wireless communications and, more particularly, to applying uplink preemption to random access transmissions. Background of the Disclosure

[0004] Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcasting, and the like. These systems may be capable of supporting communication with multiple users by sharing available system resources, such as time, frequency, and power. Examples of such multi-access systems include fourth generation (4G) systems such as Long Term Evolution (LTE) systems, Advanced LTE (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems that may be referred to as New Radio (NR) systems. These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiple access (DFT-S-OFDM). A wireless multi-access communication system may include multiple base stations or network access nodes, each of which simultaneously supports communication of multiple communication devices, which may alternatively be referred to as user equipment (UE).

[0005] Some wireless communication systems, such as NR systems, may support heterogeneous conditions for one or more service deployments. For example, a communication device such as a base station or UE may support flexibility in allocating multiple supported services or traffic types over channel resources. As part of channel resource allocation, the base station and UE may support prioritizing some communications over others, which may include prioritizing traffic or services with different reliability thresholds, different latency thresholds, and the like. In some cases, efficient system utilization may be based on how resources are shared or allocated among different traffic types, or how the UE is configured according to different traffic types. Summary of the Invention

[0006] The described technology relates to methods, systems, devices, and apparatuses that support improvements to uplink preemption for random access transmissions. In some examples, a base station or other network entity may allocate uplink and / or downlink resources to one or more user equipment (UEs), and the resources may subsequently be reallocated (e.g., based on reprioritization of communications) to other UEs or groups of other UEs. For example, a base station may determine a reallocation of uplink resources and issue a preemption indication (e.g., an uplink preemption indication (ULPI) or a downlink preemption indication (DLPI)) that may correspond to at least a portion of the previously allocated resources (e.g., resources allocated to a specific UE). A UE may be configured to monitor the preemption indication, and based on the received preemption indication, the UE may determine whether to continue an uplink transmission using its previously allocated resources.

[0007] For example, a preemption indication (e.g., ULPI) may be used to prevent a UE from using at least a portion of preconfigured or previously allocated uplink resources for an uplink transmission. Thus, a base station may support dynamically allocating uplink resources from a communication associated with one latency threshold to a communication associated with another latency threshold. For example, resources initially allocated for enhanced mobile broadband (eMBB) communications may be reallocated to ultra-reliable low latency communications (URLLC) (e.g., reallocating resources to a communication that is more performance-sensitive, higher priority traffic, etc.). In one example, an eMBB UE that decodes a ULPI may cancel or otherwise preempt an uplink transmission corresponding to the resources (e.g., time and frequency resources) associated with the ULPI.

[0008] According to one or more aspects of the technology described herein, a base station may determine to reclaim or reallocate uplink resources and may issue a preemption indication (e.g., ULPI) that may correspond to at least a portion of a UE random access resource. A UE may be configured to monitor the preemption indication, and upon receiving the preemption indication, the UE may determine whether to continue transmission of a random access message using the random access resource (e.g., in the case where the random access resource at least partially overlaps with the resources indicated by the preemption indication). For example, when a ULPI indicates that at least a portion of a random access resource is being preempted, the UE may transmit an associated random access message based on the UE's preemption configuration (e.g., based on rules or instructions configured for preemption of random access resources for the UE) or the UE may preempt transmission of the associated random access message.

[0009] The described preemption configuration and preemption application techniques can provide efficient UE handling of preemption indications (e.g., ULPI) corresponding to random access message transmissions. For example, the preemption configuration can configure the UE application of uplink preemption (e.g., comply with ULPI or disregard ULPI) based on whether the random access message (associated with a random access resource that is at least partially preempted) is to be sent as part of a contention-free random access (CFRA) procedure or a contention-based random access (CBRA) procedure. Additionally, the preemption configuration can configure the UE application of uplink preemption based on a random access trigger condition (e.g., based on what event or situation triggers the random access procedure associated with the resource that is at least partially preempted).

[0010] A method of wireless communication by a UE is described. The method can include: identifying a preemption configuration that indicates in which operating state of a set of operating states the UE is to monitor an uplink preemption indication; and transmitting a random access message or a preempted random access message via a random access resource based on the preemption configuration.

[0011] An apparatus for wireless communication by a UE is described. The apparatus can include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions can be executed by the processor to cause the apparatus to: identify a preemption configuration that indicates in which operating state of a set of operating states the UE is to monitor an uplink preemption indication; and transmit a random access message or a preempted random access message via a random access resource based on the preemption configuration.

[0012] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, identifying the preemption configuration can include: operations, features, components, or instructions for identifying that the preemption configuration indicates monitoring an uplink preemption indication when the UE can operate in a connected operating state of the set of operating states. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein can further include: operations, features, components, or instructions for monitoring an uplink preemption indication based on the UE operating in the connected operating state of the set of operating states.

[0013] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include: operations, features, components, or instructions for receiving an uplink preemption indication from a base station, the uplink preemption indication indicating that at least a portion of a random access resource may be preempted, wherein the random access message may be transmitted or preempted from transmission via the random access resource based on the uplink preemption indication. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include: operations, features, components, or instructions for skipping monitoring of the uplink preemption indication based on the UE operating in an idle operating state, an inactive operating state, or both of a set of operating states, wherein the random access message may be transmitted via the random access resource based on the UE operating in an idle operating state, an inactive operating state, or both of a set of operating states.

[0014] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, identifying a preemption configuration may include: operations, features, components, or instructions for identifying that the preemption configuration indicates that uplink preemption does not apply to contention-based random access procedures. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the transmission of a random access message or preemption of a random access message may include: operations, features, components, or instructions for transmitting a random access message according to a contention-based random access procedure.

[0015] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, identifying a preemption configuration may include: operations, features, components, or instructions for identifying that the preemption configuration indicates that uplink preemption applies to contention-free random access procedures. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the transmission of a random access message or preemption of a random access message may include: operations, features, components, or instructions for pre-empting the transmission of a random access message according to a contention-free random access procedure.

[0016] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the transmission of a preempted random message may include: operations, features, components, or instructions for pre-empting the transmission of a random access preamble message. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the transmission of a preempted random access message may include: operations, features, components, or instructions for pre-empting the transmission of a random access preamble message and a random access payload message.

[0017] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, identifying a preemption configuration may include operations, features, components, or instructions for identifying that the preemption configuration indicates that uplink preemption applies to a random access procedure triggered by at least one of: a downlink control channel command, beam failure recovery, a system information request, an uplink resource request, a scheduling request failure, or any combination thereof.

[0018] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, identifying a preemption configuration may include operations, features, components, or instructions for identifying that the preemption configuration indicates that uplink preemption does not apply to a random access procedure triggered by at least one of: initial access, handover, establishing a timing advance for a secondary cell addition, re-establishing uplink timing advance, radio resource control connection re-establishment, or any combination thereof.

[0019] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, identifying a preemption configuration may include operations, features, components, or instructions for identifying that the preemption configuration indicates that uplink preemption applies to a random access procedure in a secondary cell. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, identifying a preemption configuration may include operations, features, components, or instructions for identifying that the preemption configuration indicates that uplink preemption does not apply to a random access procedure in a primary cell.

[0020] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, transmitting a random access message or a preemptive random message may include operations, features, components, or instructions for preempting the transmission of the random access message. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for preempting the transmission of the entire random access message.

[0021] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, preempting the transmission of a random access message may include operations, features, components, or instructions for preempting the transmission of the random access message based on discarding the random access message on a per transmission time interval basis over more than one transmission time interval, where the random access message spans more than one transmission time interval.

[0022] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, based on preemption of the transmission of the random access message, the UE does not increase the transmission power level, does not increase the power ramp counter, does not increase the transmission counter, or any combination thereof. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for transmitting the random access message in the next available random access resource after preemption of the transmission of the random access message via the random access resource.

[0023] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for receiving a first downlink control channel command scheduling the transmission of the random access message and monitoring a second downlink control channel command after preemption of the transmission of the random access message. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the transmission of the random access message or preemption of the random message may include operations, features, components, or instructions for transmitting the random access message.

[0024] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, for a random access resource, a first subcarrier spacing of a bandwidth part of a serving cell on which an uplink preemption indication can be sent is different from a second subcarrier spacing of the bandwidth part of the serving cell. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the transmission of the random access message or preemption of the random access message may include operations, features, components, or instructions for preempting the transmission of the random access message during a first transmission time interval of the random access resource, the first transmission time interval overlapping a second transmission time interval indicated by the uplink preemption indication as being preemptable, the first transmission time interval having a longer duration than the second transmission time interval.

[0025] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, transmitting the random access message may include operations, features, components, or instructions for preempting the transmission of the random access message during a first transmission time interval of the random access resource, the first transmission time interval not overlapping a second transmission time interval indicated by the uplink preemption indication as being preemptable, the first transmission time interval having a longer duration than the second transmission time interval.

[0026] A method for wireless communication by a base station is described. The method may include establishing a connection with a UE in a connected state; sending an uplink preemption indication to the UE based on the connected state indicating that at least a part of a random access resource is being preempted; and scheduling the random access resource based on the uplink preemption indication.

[0027] Describes an apparatus for wireless communication by a base station. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: establish a connection with a UE in a connected state; send an uplink preemption indication indicating that at least a portion of the random access resources is being preempted to the UE based on the connection state; and schedule the random access resources based on the uplink preemption indication.

[0028] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include: operations, features, components, or instructions for receiving a random access message from a UE in a next available random access resource after a preemption of a random access message via a transmission of the random access resources. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include: operations, features, components, or instructions for sending a first control channel command for scheduling a transmission of a random access message, and for sending a second control channel command after a transmission of the preemption of the random access message. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, for a random access resource, a first subcarrier spacing of a bandwidth portion of a serving cell on which an uplink preemption indication may be sent is different from a second subcarrier spacing of the bandwidth portion of the serving cell. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Figure 1 Shows an example of a wireless communication system supporting uplink preemption for random access transmissions in accordance with aspects of the present disclosure.

[0030] Figure 2 Shows an example of a wireless communication system supporting uplink preemption for random access transmissions in accordance with aspects of the present disclosure.

[0031] Figure 3A and 3B Shows an example processing flow supporting uplink preemption for random access transmissions in accordance with aspects of the present disclosure.

[0032] Figure 4 Shows an example of a processing flow supporting uplink preemption for random access transmissions in accordance with aspects of the present disclosure.

[0033] Figure 5A and 5B Shows an example uplink preemption indication (ULPI) diagram supporting uplink preemption for random access transmissions in accordance with aspects of the present disclosure.

[0034] Figure 6 Shows an example of a ULPI diagram supporting uplink preemption for random access transmissions in accordance with aspects of the present disclosure.

[0035] Figure 7A and 7B illustrates an example processing flow that supports applying uplink preemption to a random access transmission according to an aspect of the present disclosure.

[0036] Figure 8 and Figure 9 illustrates a block diagram of a device that supports applying uplink preemption to a random access transmission according to an aspect of the present disclosure.

[0037] Figure 10 illustrates a block diagram of a communication manager that supports applying uplink preemption to a random access transmission according to an aspect of the present disclosure.

[0038] Figure 11 illustrates a schematic diagram of a system that includes a device that supports applying uplink preemption to a random access transmission according to an aspect of the present disclosure.

[0039] Figure 12 and Figure 13 illustrates a block diagram of a device that supports applying uplink preemption to a random access transmission according to an aspect of the present disclosure.

[0040] Figure 14 illustrates a block diagram of a communication manager that supports applying uplink preemption to a random access transmission according to an aspect of the present disclosure.

[0041] Figure 15 illustrates a schematic diagram of a system that includes a device that supports applying uplink preemption to a random access transmission according to an aspect of the present disclosure.

[0042] Figures 16 to 19 illustrates a flowchart that depicts a method that supports applying uplink preemption to a random access transmission according to an aspect of the present disclosure. Detailed Description

[0043] Some communication systems can support different service types (e.g., service classes), which can include or refer to communication services with different reliability thresholds, different latency thresholds, different services, or various combinations thereof. For example, a wireless communication system can support a first service type (e.g., a first type of communication) associated with a relatively high reliability threshold and a relatively low latency threshold, such as ultra-reliable low-latency communication (URLLC) service. The wireless communication system can also support other service types associated with relatively lower reliability thresholds and relatively longer or looser latency thresholds, such as enhanced mobile broadband (eMBB) service. In some cases, to support various system operations (e.g., efficient utilization of wireless communication resources, proper allocation or balancing of wireless communication resources, proper support for services based on different priorities or latency thresholds), the wireless communication system can support dynamic resource sharing between service types. For example, the wireless communication system can support dynamic resource allocation between URLLC communication and eMBB communication or other communications according to different service types, classes, or other priorities.

[0044] The described techniques include various examples of dynamic resource allocation by way of pre-empting (e.g., or canceling) previously allocated uplink resources of a network entity such as a base station or other controller or resource allocation grantor communicating with the base station. For example, a base station or other network entity can allocate uplink resources (e.g., an initial uplink resource allocation) to a user equipment (UE) or a group of UEs, and the base station can subsequently issue a pre-emption indication (e.g., an uplink pre-emption indication (ULPI) or a downlink pre-emption indication (DLPI)), which can correspond to at least a portion of the previously allocated uplink or downlink resources (e.g., allocated to a specific UE). The UE can detect such a pre-emption indication and use its previously allocated uplink resources to determine whether to continue with an uplink transmission (e.g., based on whether the pre-emption indication is directed at the UE, application rules for the ULPI, etc.).

[0045] In some examples, the pre-emption indication can be used to prevent the UE from using at least a portion of the previously allocated uplink resources for uplink transmission (e.g., such that the wireless communication system can support dynamic allocation of uplink resources from communication associated with one latency threshold to communication associated with another latency threshold, or some other reallocation based on communication priorities). For example, resources initially allocated for eMBB communication can be reallocated to URLLC communication (e.g., a reallocation to a communication that is more sensitive to performance).

[0046] However, in some scenarios, terminating or pre-empting some transmissions (e.g., some random access transmissions) may or may not be effective, even if such pre-emption is indicated by the ULPI. For example, pre-emption of random access message transmissions in some random access scenarios (e.g., such as for random access message transmissions associated with contention-based random access (CBRA) procedures) may, in some cases, have an adverse impact on the effective prioritization of communications within a wireless communication system. Thus, a trade-off between reallocation of previously allocated resources for high-priority communications and the consideration and management of resulting random access message pre-emption may be desirable.

[0047] For example, in some cases, the UE may have previously established a radio resource control (RRC) connection with the base station, and the UE may receive a ULPI that indicates that at least a portion of the contention-free random access (CFRA) resources are being pre-empted. In such a case, when prompted by the received ULPI (e.g., since the base station may have prior knowledge of the UE priority, the priority associated with the communications supported or used by the UE, etc. based on the previously established RRC connection), the transmission of the UE pre-empting the CFRA transmission may be effective. Alternatively, the UE may not have previously established an RRC connection with the base station (e.g., because the UE may be attempting initial access), and the UE may receive a ULPI that indicates that at least a portion of the CBRA resources are being pre-empted. In such a case, pre-empting the transmission of the random access message may be inefficient for the UE (e.g., because the base station may have relatively little (or no) prior knowledge of the UE priority, because the base station may have relatively little (or no) prior knowledge of the priority associated with the communications supported or used by the UE, because the UE may not be monitoring the ULPI, etc.). That is, in cases where the ULPI indicates that at least a portion of the CBRA resources are pre-empted, it may be effective for the UE to continue with the CBRA transmission regardless (e.g., in such scenarios, the base station may not know whether the UE will support the ULPI since the services or communications supported by the UE may change the effective dynamic resource allocation and ULPI usage, etc.).

[0048] Accordingly, the described techniques can provide an effective preemption configuration for a UE. The preemption configuration can provide more effective resource utilization and resource reallocation within a wireless communication system that supports various service deployments. Specifically, aspects of the described preemption configuration can provide effective UE handling of the ULPI associated with random access message transmission based on whether the random access message is sent as part of a CFRA procedure or as part of a CBRA procedure. Additionally, aspects of the described preemption configuration can provide effective handling of the ULPI associated with random access message transmission based on the random access trigger condition (e.g., based on what event or situation triggers the UE to send a random access message).

[0049] A wireless communication system can thus adopt a preemption configuration (e.g., uplink preemption applicability rules, rules for ULPI application, etc.) to balance the trade-off between the reallocation of previously allocated resources for high-priority communications and the consequences of preempting certain random access messages. Accordingly, a UE can be configured with a preemption configuration and can handle the ULPI according to this preemption configuration (e.g., can send an associated random access message or preempt the transmission of an associated random access message). Thus, the described techniques can provide dynamic reallocation of uplink resources in a wireless communication system to more effectively balance the performance of communications and resource utilization according to different priorities. Additionally, the described techniques can provide effective compliance with preemption indications (e.g., in the case where the resources indicated by a preemption indication correspond to resources used for a random access procedure). For example, the described preemption configuration (e.g., rules for applying the ULPI to the random access message transmission of a UE) can provide effective communication preemption such that certain random access processes are not preempted by the UE unnecessarily or ineffectively.

[0050] Aspects of the present disclosure are initially described in the context of a wireless communication system. Aspects of the present disclosure are also illustrated and described by reference to examples of signaling, operations, and diagrams that can support one or more aspects of the techniques for applying uplink preemption to random access transmission. Further aspects of the present disclosure are illustrated and described with reference to apparatus diagrams, system diagrams, and flowcharts related to applying uplink preemption to random access transmission.

[0051] Figure 1FIG. 0 shows an example of a wireless communication system 100 that supports an uplink preemption application technique in accordance with aspects of the present disclosure. The wireless communication system 100 includes a base station 105, a UE 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network. In some cases, the wireless communication system 100 may support enhanced broadband communications, ultra-reliable (e.g., mission-critical) communications, low-latency communications, or communications with low-cost and low-complexity devices.

[0052] The base station 105 may communicate wirelessly with the UE 115 via one or more base station antennas. The base station 105 described herein may include or may be referred to by those skilled in the art as a base transceiver station, a radio base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB), a next-generation NodeB, or a giga NodeB (any of which may be referred to as a gNB), a home NodeB, a home eNodeB, or some other suitable term. The wireless communication system 100 may include different types of base stations 105 (e.g., macro cell base stations or small cell base stations). The UE 115 described herein may be capable of communicating with various types of base stations 105 and network devices, including macro eNBs, small cell eNBs, gNBs, relay base stations, and the like.

[0053] Each base station 105 may be associated with a particular geographic coverage area 110 in which communication with various UEs 115 is supported. Each base station 105 may provide communication coverage for the corresponding geographic coverage area 110 via a communication link 125, and the communication link 125 between the base station 105 and the UE 115 may utilize one or more carriers. The communication link 125 shown in the wireless communication system 100 may include an uplink transmission from the UE 115 to the base station 105, or a downlink transmission from the base station 105 to the UE 115. Downlink transmissions may also be referred to as forward link transmissions, and uplink transmissions may also be referred to as reverse link transmissions.

[0054] The geographical coverage area 110 of the base station 105 can be divided into sectors that form part of the geographical coverage area 110, and each sector can be associated with a cell. For example, each base station 105 can provide communication coverage for macro cells, small cells, hotspots, or other types of cells, or various combinations thereof. In some examples, the base station 105 can be movable and thus provide communication coverage for a movable geographical coverage area 110. In some examples, different geographical coverage areas 110 associated with different technologies can overlap, and the overlapping geographical coverage areas 110 associated with different technologies can be supported by the same base station 105 or different base stations 105. The wireless communication system 100 can include, for example, a heterogeneous LTE / LTE-A / LTE-A Pro or NR network in which different types of base stations 105 provide coverage for various geographical coverage areas 110.

[0055] The term "cell" refers to a logical communication entity for communicating with the base station 105 (e.g., via a carrier), and it can be associated with an identifier (e.g., physical cell identifier (PCID), virtual cell identifier (VCID)) for differentiating adjacent cells operating via the same or different carriers. In some examples, a carrier can support multiple cells, and different cells can be configured according to different protocol types (e.g., machine type communication (MTC), narrowband Internet of Things (NB-IoT), eMBB, or others) that can provide access for different types of devices. In some cases, the term "cell" can refer to a part (e.g., a sector) of the geographical coverage area 110 on which the logical entity operates.

[0056] UEs 115 can be dispersed throughout the wireless communication system 100, and each UE 115 can be fixed or movable. The UE 115 can also be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or some other suitable term, where "device" can also be referred to as a unit, station, terminal, or client. The UE 115 can also be a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, the UE 115 can also refer to a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or MTC device, etc., which can be implemented in various items such as appliances, vehicles, meters, etc.

[0057] Some UEs 115, such as MTC or IoT devices, can be low-cost or low-complexity devices and can provide automatic communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with each other or with the base station 105 without human intervention. In some examples, M2M communication or MTC can include communication from devices integrated with sensors or meters to measure or capture information and relay the information to a central server or application, which can utilize the information or present the information to a person interacting with the program or application. Some UEs 115 can be designed to collect information or enable automated behavior of machines. Examples of applications of MTC devices include smart metering, inventory monitoring, water level monitoring, device monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.

[0058] Some UEs 115 can be configured to operate in power-saving modes, such as half-duplex communication (e.g., a mode that supports one-way communication via transmission or reception but not simultaneous transmission and reception). In some examples, half-duplex communication can be performed at a reduced peak rate. Other power-saving techniques for UEs 115 include entering an energy-saving "deep sleep" mode when not participating in active communication, or operating on a limited bandwidth (e.g., according to narrowband communication). In certain cases, UEs 115 can be designed to support critical functions (e.g., mission-critical functions), and the wireless communication system 100 can be configured to provide ultra-reliable communication for these functions.

[0059] In certain cases, UEs 115 are also capable of communicating directly with other UEs 115 (e.g., using peer-to-peer (P2P) or device-to-device (D2D) protocols). One or more UEs in a group of UEs 115 that utilize D2D communication can be within the geographical coverage area 110 of the base station 105. Other UEs 115 in the group can be outside the geographical coverage area 110 of the base station 105 or cannot receive transmissions from the base station 105. In certain cases, a group of UEs 115 that communicate via D2D communication can utilize a one-to-many (1:M) system in which each UE 115 transmits to every other UE 115 in the group. In certain cases, the base station 105 facilitates resource scheduling for D2D communication. In other cases, D2D communication is performed between UEs 115 without the participation of the base station 105.

[0060] Base station 105 can communicate with core network 130 and with each other. For example, base station 105 can interface with core network 130 via a backhaul link 132 (e.g., via S1, N2, N3, or other interfaces). Base station 105 can communicate with each other directly (e.g., directly between base stations 105) or indirectly (e.g., via core network 130) via a backhaul link 134 (e.g., via X2, Xn, or other interfaces).

[0061] Core network 130 can provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 can be an evolved packet core (EPC), which can include at least one mobility management entity (MME), at least one serving gateway (S-GW), and at least one packet data network (PDN) gateway (P-GW). The MME can manage non-access stratum (e.g., control plane) functions of UEs 115 served by base stations 105 associated with the EPC, such as mobility, authentication, and bearer management. User IP packets can be transported through the S-GW, which itself can be connected to the P-GW. The P-GW can provide IP address allocation and other functions. The P-GW can be connected to the network operator's IP services. The operator's IP services can include access to the Internet, an intranet(s), IP multimedia subsystem (IMS), or packet switched (PS) streaming services.

[0062] At least some network devices such as base station 105 can include subcomponents such as access network entities, which can be examples of access node controllers (ANCs). Each access network entity can communicate with UE 115 via a plurality of other access network transport entities, which can be referred to as radio heads, intelligent radio heads, or transmit / receive points (TRPs). In some configurations, the various functions of each access network entity or base station 105 can be distributed across various network devices (e.g., radio heads and access network controllers) or consolidated into a single network device (e.g., base station 105).

[0063] The wireless communication system 100 can operate using one or more frequency bands typically in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or the decimeter band because the wavelength range is approximately from 1 decimeter to 1 meter. UHF waves can be blocked or redirected by buildings and environmental features. However, the waves can penetrate structures sufficiently to enable a macro cell to serve a UE 115 located indoors. Compared with transmissions at smaller frequencies and longer wavelengths using the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, UHF wave transmissions can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

[0064] The wireless communication system 100 can also operate in the super-high frequency (SHF) region using frequency bands from 3 GHz to 30 GHz (also known as the centimeter band). The SHF region includes frequency bands such as the 5 GHz industrial, scientific, and medical (ISM) band, which can be used opportunistically by devices that can tolerate interference from other users.

[0065] The wireless communication system 100 can also operate in the extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz), which is also known as the millimeter band. In some examples, the wireless communication system 100 can support millimeter wave (mmW) communication between the UE 115 and the base station 105, and the EHF antennas of the respective devices can be even smaller and closer spaced than UHF antennas. In certain cases, this can facilitate the use of antenna arrays within the UE 115. However, EHF transmissions may experience even greater atmospheric attenuation and shorter ranges than SHF or UHF transmissions. The techniques disclosed herein can be employed across transmissions using one or more different frequency regions, and the designated use of frequency bands across these frequency regions may vary by country or regulatory authority.

[0066] In some cases, the wireless communication system 100 can utilize both licensed radio frequency bands and unlicensed radio frequency bands. For example, the wireless communication system 100 can employ Licensed-Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band such as the 5 GHz ISM band. When operating in an unlicensed radio frequency band, wireless devices such as the base station 105 and the UE 115 can employ a Listen-Before-Talk (LBT) procedure to ensure that the frequency channel is idle before transmitting data. In some cases, operation in the unlicensed band can be based on a carrier aggregation configuration in combination with a component carrier operating in a licensed band (e.g., LAA). Operation in the unlicensed spectrum can include downlink transmissions, uplink transmissions, peer-to-peer transmissions, or a combination of these transmissions. Duplexing in the unlicensed spectrum can be based on Frequency Division Duplexing (FDD), Time Division Duplexing (TDD), or a combination of both.

[0067] In some examples, the base station 105 or the UE 115 can be equipped with multiple antennas, which can be used to employ techniques such as transmit diversity, receive diversity, Multiple-Input Multiple-Output (MIMO) communication, or beamforming. For example, the wireless communication system 100 can use a transmission scheme between a transmitting device (e.g., the base station 105) and a receiving device (e.g., the UE 115), where the transmitting device is equipped with multiple antennas and the receiving device is equipped with one or more antennas. MIMO communication can utilize multipath signal propagation to improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers, which can be referred to as spatial multiplexing. The multiple signals can be transmitted, for example, by the transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals can be received by the receiving device via different antennas or different combinations of antennas. Each of the multiple signals can be referred to as a separate spatial stream and can carry bits associated with the same data stream (e.g., the same codeword) or different data streams. Different spatial layers can be associated with different antenna ports for channel measurement and reporting. MIMO techniques include Single-User MIMO (SU-MIMO) (where multiple spatial layers are transmitted to the same receiving device), and Multi-User MIMO (MU-MIMO) (where multiple spatial layers are transmitted to multiple devices).

[0068] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting device or a receiving device (e.g., base station 105 or UE 115) to shape or manipulate an antenna beam (e.g., a transmit beam or a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming can be achieved by combining signals communicated via the antenna elements of an antenna array such that signals propagating in a particular azimuth relative to the antenna array experience constructive interference while other signals experience destructive interference. The adjustment of the signals communicated via the antenna elements can include the transmitting device or the receiving device applying a certain amplitude and phase offset to the signals carried via each antenna element associated with the device. The adjustment associated with each antenna element can be defined by a set of beamforming weights associated with a particular azimuth (e.g., relative to the antenna array of the transmitting device or the receiving device, or relative to some other azimuth).

[0069] In one example, base station 105 can use multiple antennas or an antenna array to perform beamforming operations for directional communication with UE 115. For example, base station 105 can transmit some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) multiple times in different directions, and these signals can include signals transmitted according to different sets of beamforming weights associated with different transmission directions. Transmissions in different beam directions can be used to identify beam directions (e.g., by base station 105 or a receiving device such as UE 115) for subsequent transmission and / or reception by base station 105.

[0070] Base station 105 can transmit some signals, such as data signals associated with a particular receiving device, in a single beam direction (e.g., a direction associated with a receiving device such as UE 115). In some examples, the beam direction associated with a transmission along a single beam direction can be determined at least in part based on signals transmitted in different beam directions. For example, UE 115 can receive one or more of the signals transmitted by base station 105 in different directions, and UE 115 can report an indication of the signal it received with the highest signal quality or other acceptable signal quality to base station 105. Although these techniques are described with reference to signals transmitted by base station 105 in one or more directions, UE 115 can employ similar techniques to transmit signals multiple times in different directions (e.g., for identifying beam directions for subsequent transmission or reception by UE 115) or to transmit signals in a single direction (e.g., for transmitting data to a receiving device).

[0071] When receiving various signals such as synchronization signals, reference signals, beam selection signals, or other control signals from base station 105, a receiving device (e.g., UE 115, which can be an example of a millimeter-wave receiving device) may attempt multiple receive beams. For example, the receiving device may attempt multiple receive directions by receiving via different antenna subarrays, processing received signals according to different antenna subarrays, receiving according to different receive beamforming weight sets applied to signals received at multiple antenna elements of the antenna array, or processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of the antenna array. Any of the above ways may be referred to as "listening" according to different receive beams or receive directions. In some examples, the receiving device may use a single receive beam to receive along a single beam direction (e.g., when receiving a data signal). The single receive beam may be aligned in a beam direction determined at least in part based on listening according to different receive beam directions (e.g., a beam direction having the highest signal strength, highest signal-to-noise ratio, or other acceptable signal quality determined at least in part based on listening according to multiple beam directions).

[0072] In some cases, the antennas of base station 105 or UE 115 may be located within one or more antenna arrays, which may support MIMO operation, or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be collocated at an antenna fixture such as an antenna tower. In some cases, the antennas or antenna arrays associated with base station 105 may be located at different geographical locations. Base station 105 may have an antenna array with multiple rows and columns of antenna ports, and base station 105 may use this antenna array to support beamforming for communication with UE 115. Similarly, UE 115 may have one or more antenna arrays that can support various MIMO or beamforming operations.

[0073] In some cases, wireless communication system 100 may be a packet-based network operating according to a hierarchical protocol stack. In the user plane, communication at the bearer or packet data convergence protocol (PDCP) layer may be IP-based. The radio link control (RLC) layer may perform packet segmentation and reassembly for communication over logical channels. The medium access control (MAC) layer may perform priority handling and multiplexing of logical channels to transport channels. The MAC layer may also use hybrid automatic repeat request (HARQ) to provide retransmission at the MAC layer to improve link efficiency. In the control plane, the RRC protocol layer may provide the establishment, configuration, and maintenance of an RRC connection (which supports radio bearers for user plane data) between UE 115 and base station 105 or core network 130. At the physical layer, transport channels may be mapped to physical channels.

[0074] In some cases, the UE 115 and the base station 105 may support retransmission of data to increase the likelihood of successful data reception. HARQ feedback is a technique that increases the likelihood of correctly receiving data over the communication link 125. HARQ may include a combination of error detection (e.g., using cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., signal-to-noise ratio conditions). In some cases, a wireless device may support simultaneous slot HARQ feedback, where the device can provide HARQ feedback in a particular slot for data received in previous symbols in that slot. In other cases, the device may provide HARQ feedback in a subsequent slot or according to some other time interval.

[0075] Time intervals in LTE or NR can be expressed as multiples of a basic time unit. For example, the time interval can refer to a sampling period of Ts = 1 / 30,720,000 seconds. The time intervals of communication resources can be organized according to radio frames (each radio frame having a duration of 10 milliseconds (ms)), where the frame period can be expressed as Tf = 307,200 Ts. Radio frames can be identified by a system frame number (SFN) ranging from 0 to 1023. Each frame can include 10 subframes numbered from 0 to 9, and each subframe can have a duration of 1 ms. A subframe can be further divided into 2 slots, each slot having a duration of 0.5 ms, and each slot can contain 6 or 7 modulation symbol periods (e.g., depending on the length of the cyclic prefix before each symbol period). Excluding the cyclic prefix, each symbol period can contain 2048 sampling periods. In some cases, a subframe can be the smallest scheduling unit of the wireless communication system 100 and can be referred to as a transmission time interval (TTI). In other cases, the smallest scheduling unit of the wireless communication system 100 can be shorter than a subframe or can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs) or in a selected component carrier using sTTI).

[0076] In some wireless communication systems, a slot can also be divided into multiple mini-slots containing one or more symbols. In some instances, a mini-slot or a symbol of a mini-slot can be the smallest unit of scheduling. The duration of each symbol can vary depending on, for example, the subcarrier spacing or the operating frequency band. Additionally, some wireless communication systems can implement slot aggregation, where multiple slots or mini-slots are aggregated together and used for communication between the UE 115 and the base station 105.

[0077] The term "carrier" refers to a collection of radio spectrum resources that has a defined physical layer structure for supporting communication on communication link 125. For example, the carrier of communication link 125 can include a portion of the radio frequency spectrum band operating according to the physical layer channels for a given radio access technology. Each physical layer channel can carry user data, control information, or other signaling. The carrier can be associated with a predefined frequency channel (e.g., the evolved universal terrestrial radio access (E-UTRA) absolute radio frequency channel number (EARFCN)) and can be located according to a channel raster for discovery by UE 115. The carrier can be downlink or uplink (e.g., in FDD mode), or be configured to carry both downlink and uplink communications (e.g., in TDD mode). In some examples, the signal waveform transmitted on the carrier can be composed of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)).

[0078] For different radio access technologies (e.g., LTE, LTE-A, LTE-A Pro, NR), the organizational structure of the carrier can be different. For example, the communication on the carrier can be organized according to TTI or time slots, where each TTI or time slot can include user data as well as control information or signaling to support decoding of the user data. The carrier can also include dedicated acquisition signaling (e.g., synchronization signals or system information, etc.) and control signaling to coordinate the operation of the carrier. In some examples (e.g., in a carrier aggregation configuration), the carrier can also have acquisition signaling or control signaling to coordinate the operation of other carriers.

[0079] Physical channels can be multiplexed on the carrier according to various techniques. For example, time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques can be used to multiplex physical control channels and physical data channels on a downlink carrier. In some examples, the control information transmitted in the physical control channel can be distributed in a cascaded manner between different control regions (e.g., between a common control region or common search space and one or more UE-specific control regions or UE-specific search spaces).

[0080] A carrier can be associated with a specific bandwidth of the radio frequency spectrum, and in some examples, the carrier bandwidth can be referred to as the "system bandwidth" of the carrier or the wireless communication system 100. For example, the carrier bandwidth can be one of multiple predetermined bandwidths of a carrier for a specific radio access technology (e.g., 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). In some examples, each served UE 115 can be configured to operate on part or all of the carrier bandwidth. In other examples, some UEs 115 can be configured to operate using a narrowband protocol type associated with a predefined part or range within the carrier (e.g., a set of subcarriers or RBs) (e.g., "in-band" deployment of the narrowband protocol type).

[0081] In a system employing MCM technology, a resource element can consist of a symbol period (e.g., the duration of a modulation symbol) and a subcarrier, where the symbol period and the subcarrier spacing are inversely related. The number of bits carried by each resource element can depend on the modulation scheme (e.g., the order of the modulation scheme). Thus, the more resource elements received by the UE 115 and the higher the order of the modulation scheme, the higher the data rate of the UE 115 may be. In an MIMO system, the wireless communication resources can refer to a combination of radio spectrum resources, time resources, and spatial resources (e.g., spatial layers), and using multiple spatial layers can also increase the data rate for communicating with the UE 115.

[0082] Devices of the wireless communication system 100 (e.g., the base station 105 or the UE 115) can have a hardware configuration that supports communication on a specific carrier bandwidth, or can be configured to support communication on one of a set of carrier bandwidths. In some examples, the wireless communication system 100 can include the base station 105 and / or the UE 115 that support simultaneous communication via carriers associated with more than one different carrier bandwidth.

[0083] The wireless communication system 100 can support communication with the UE 115 on multiple cells or carriers, and this feature can be referred to as carrier aggregation or multi-carrier operation. According to the carrier aggregation configuration, the UE 115 can be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used with both FDD and TDD component carriers.

[0084] In some cases, the wireless communication system 100 may utilize an enhanced component carrier (eCC). The eCC may be characterized by one or more features including a wider carrier or frequency channel bandwidth, a shorter symbol duration, a shorter TTI duration, or a modified control channel configuration. In some cases, the eCC may be associated with a carrier aggregation configuration or a dual connectivity configuration (e.g., when multiple serving cells have suboptimal or non-ideal backhaul links). The eCC may also be configured to operate in unlicensed or shared spectrum (e.g., in cases where more than one operator is allowed to use the spectrum). An eCC characterized by a wide carrier bandwidth may include one or more segments that may be used by a UE 115 that cannot monitor the entire carrier bandwidth or is otherwise configured to use a limited carrier bandwidth (e.g., to conserve power).

[0085] In some cases, the eCC may utilize a symbol duration different from that of other component carriers, which may include using a reduced symbol duration compared to the symbol duration of other component carriers. The shorter symbol duration may be associated with an increased spacing between adjacent subcarriers. Devices such as UE 115 or base station 105 that utilize the eCC may transmit broadband signals (e.g., according to a frequency channel or carrier bandwidth of 20Mhz, 40Mhz, 60Mhz, 80MHz, etc.) with a reduced symbol duration (e.g., 16.67 microseconds). The TTI in the eCC may consist of one or more symbol periods. In some cases, the TTI duration (i.e., the number of symbol periods in the TTI) may be variable.

[0086] The wireless communication system 100 may be an NR system, which may utilize any combination of licensed, shared, and unlicensed spectrum bands, etc. The flexibility of the eCC symbol duration and subcarrier spacing may allow the eCC to be used across multiple spectrums. In some examples, NR shared spectrum may increase spectrum utilization and spectral efficiency, specifically through dynamic vertical (e.g., across the frequency domain) and horizontal (e.g., across the time domain) resource sharing.

[0087] The wireless communication system 100 can be configured to support different service types (e.g., service classes, service priorities, serving priorities), which can include or refer to communication services having different reliability thresholds, different latency thresholds, different services, or various combinations thereof. For example, the wireless communication system 100 can support a first service type associated with a relatively high reliability goal or threshold and a relatively low latency goal or threshold, such as the URLLC service type. The wireless communication system 100 can also support a second service type associated with a relatively low reliability goal or threshold and a relatively long or relaxed latency threshold, such as the eMBB service type. In some cases, to support various system operations (e.g., efficient utilization of wireless communication resources, proper allocation or balancing of wireless communication resources, proper support of services according to different priorities or latency thresholds), the wireless communication system 100 can support dynamic resource sharing between service types, such as dynamic allocation of resources between URLLC communication and eMBB communication or other communications according to different service types, classes, or other priorities.

[0088] To support various resource allocation techniques, the base station 105 or other network entities (e.g., entities of the core network 130, entities of the distributed base station 105) can allocate uplink and / or downlink resources (e.g., initial uplink resource allocation or initial downlink resource allocation) to the UE 115 or a group of UEs 115 for uplink transmission and / or downlink transmission. In some examples, the base station 105 or other network entities can subsequently determine to perform a reallocation of the previously allocated resources, which can be triggered by, for example, a determined or detected need, requirement, or request to support higher priority communication. Thus, the base station 105 or other network entities can generate and send a cancellation indication (e.g., ULPI and / or DLPI) that can correspond to at least a portion of the previously allocated resources (e.g., resources allocated to a specific UE 115). The UE 115 can be configured to monitor the ULPI and DLPI, and thus can determine whether to continue uplink transmission and / or downlink reception using the uplink resources it was previously allocated, at least in part based on the received, detected, or decoded ULPI or DLPI.

[0089] For example, base station 105 may transmit a Physical Downlink Control Channel (PDCCH) to schedule an eMBB Physical Uplink Shared Channel (PUSCH) (e.g., schedule UE 115 with time and frequency resources for eMBB uplink). In some cases, the uplinks for both eMBB (e.g., low-priority traffic) and URLLC (e.g., high-priority traffic) may be grant-based (e.g., scheduled by DCI). Given that URLLC may require a faster timeline than eMBB (e.g., faster N2 for UL scheduling), some resources initially allocated for the eMBB uplink may be reclaimed for URLLC. To reduce the interference imposed by eMBB users on URLLC users, eMBB users may be required to preempt their uplink transmissions (e.g., via ULPI monitored by the eMBB user).

[0090] For example, base station 105 may transmit a PDCCH to schedule an eMBB PUSCH. Later, base station 105 may identify that the traffic of another UE has a first priority higher than the second priority of the uplink message for this UE (e.g., the base station may identify that another URLLC UE will communicate traffic with a higher priority than the previously scheduled UE). Then, base station 105 may identify the resources in the time domain, frequency domain, and / or spatial domain in which the transmission by the UE is preempted (e.g., one or more spatial directions and at least a portion of the scheduled time and frequency resources) based on the identification that the traffic of another UE has a first priority higher than the second priority of the uplink message to be transmitted on the initially scheduled resources. In such a case, the base station may send a preemption indication (e.g., ULPI) during the UE ULPI monitoring occasion, which may preempt the transmission of the scheduled uplink message (e.g., ULPI may preempt the scheduled uplink message on a portion of the scheduled multiple time and frequency resources). Thus, in some cases, another UE 115 may transmit a URLLC PUSCH on the preempted resources.

[0091] According to one or more aspects of the techniques described herein, UE 115 may ignore a preemption indication (e.g., ULPI), such as when the preemption indication means stopping the transmission of a random access message associated with a specific type of random access procedure or when the preemption indication means stopping a random access procedure associated with a specific trigger event. For example, the preemption configuration may indicate rules or instructions for applying the preemption indication for random access transmission. Thus, according to these and other examples, certain types of uplink resource allocations may be canceled, preempted, or reallocated, thereby supporting the dynamic reallocation of uplink resources in a wireless communication system, while some preemption indications may be disregarded or ignored to more effectively balance the performance of communication and resource utilization according to different priorities.

[0092] Figure 2 FIG. 2 illustrates an example of a wireless communication system 200 that supports applying uplink preemption to random access transmissions in accordance with aspects of the present disclosure. In some examples, the wireless communication system 200 may implement aspects of the wireless communication system 100. The wireless communication system 200 may include a base station 105-a, a UE 115-a, and a UE 115-b, which may be examples of corresponding devices as described with reference to Figure 1 In Figure 2 this example, the base station 105-a may support communication with a plurality of UEs (e.g., UE 115-a and UE 115-b) within the supported geographic coverage area 110-a. In some examples, the wireless communication system 200 may support mission-critical applications that include strict communication performance (e.g., reliability thresholds, latency thresholds) as well as other types of communication.

[0093] In the wireless communication system 200, the UE 115-a and / or the UE 115-b may support various service deployments (e.g., such as URLLC services and eMBB services). For example, the UE 115-b may support URLLC transmissions (e.g., via communication link 205) to reduce the end-to-end latency of data transmission and reception associated with the base station 105-a. In some examples, the UE 115-b may correspond to a URLLC UE that supports or is otherwise configured for the transmission of relatively small data packets (such as periodic transmissions). For example, the UE 115-b may include a URLLC UE that supports operations and data communication associated with factory automation (e.g., automated manufacturing, supply chain management), transportation (e.g., vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication), or power distribution (e.g., grid networking) within the supported area or site, as well as other possible implementations.

[0094] In addition, the base station 105-a may support communication with other UEs (e.g., such as UE 115-a) that support eMBB transmissions associated with high data rates across a wide coverage area (such as geographic coverage area 110-a). In some examples, compared to URLLC communication, eMBB communication may be associated with relatively loose (e.g., longer) latency targets or thresholds, lower reliability targets or thresholds, or both. In addition, one or more of the UEs 115-a and 115-b may support data communication associated with multiple service deployments (such as URLLC and eMBB) as part of intra-UE or inter-UE operations.

[0095] Thus, according to the described techniques, base station 105-a or other network entities can allocate uplink and / or downlink resources (e.g., in time domain, frequency domain, spatial domain) to UE 115 or a group of UEs, and these resources can then be reallocated. For example, base station 105-a can determine the reallocation of uplink resources and / or downlink resources, and can issue a preemption indication (e.g., ULPI, DLPI, cancellation indication, etc.) corresponding to at least a portion of the previously allocated resources. UE 115 (e.g., UE 115-a and UE 115-b) can be configured to monitor such preemption indications, and based on the received preemption indications, UE 115 can determine whether to continue uplink transmission or downlink reception using its previously allocated resources. In some cases, the preemption configuration (e.g., rules for applying preemption indications) can be identified by UE 115 and / or base station 105 based on traffic prioritization, preemption indication prioritization, the type of scheduling signal to be sent by UE 115, the type of unscheduled signal to be sent by UE 115, etc.

[0096] That is, to support the conditions associated with some service deployments (e.g., URLLC and eMBB service deployments, or other types of resource allocations based on communication prioritization), base station 105-a and UE 115-a and 115-b can support various techniques for dynamic uplink resource allocation and uplink preemption applied to random access transmissions as described herein. For example, base station 105-a can be configured to send ULPI 210 at least partially based on determining the reallocation of uplink resources (e.g., associated with the uplink resources allocated to UE 115-b for communication link 205), and UE 115 (e.g., UE 115-a) can monitor such ULPI 210 to determine how they should continue uplink communication. In other words, UE 115 can be notified about uplink resources preempted (e.g., or cancelled) in the time domain, frequency domain, and / or spatial domain. According to various examples, UE 115 (e.g., such as UE 115-a) that receives ULPI 210 can perform uplink communication determination, such as determining whether to perform or continue uplink transmission, or determining whether to avoid or preempt uplink transmission (e.g., based on the resources indicated by ULPI 210, based on the preemption configuration corresponding to the received ULPI 210, etc.).

[0097] According to various techniques, the ULPI 210 can be signaled by the base station 105-a to the UE 115 (e.g., to the UE 115-a, to a group of UEs 115). For example, the UE 115 can be configured to monitor the ULPI 210 based on various signaling from the base station 105-a (such as various types of downlink control signaling, physical channel signaling, cell-specific signaling, etc.). In some examples, the ULPI 210 can be conveyed in the downlink control information (DCI) via the PDCCH, and the PDCCH can support UE-specific ULPI. In some examples, the UE 115 can be configured (e.g., by the base station 105-a) with a radio network temporary identifier (RNTI) for monitoring the PDCCH that may carry the ULPI 210. In certain cases, the UE 115 can be configured with an RNTI that is common between uplink and downlink preemption indications, or different RNTIs between uplink and downlink preemption indications.

[0098] According to various aspects of the techniques described herein, in different scenarios, if the UE 115-a receives the ULPI 210, terminating some transmissions (e.g., the random access message 215) may or may not be effective. That is, generally, the allowance or preemption of the random access message 215 transmission in different random access scenarios (e.g., the random access message 215 transmission for the CFRA process versus the random access message 215 transmission for the CBRA process) may, in some cases, affect the effective prioritization of communications within the wireless communication system 200 (e.g., such that a trade-off between the reallocation of previously allocated resources for high-priority communications and the resulting preemption of the random access message 215 can be considered).

[0099] For example, in some cases, UE 115-a may have previously established an RRC connection with base station 105-a, and UE 115-a may receive ULPI 210 indicating that at least a portion of the CFRA resources are being pre-empted. In such a case, it may be valid for UE 115-a to pre-empt the transmission of random access message 215 (e.g., because base station 105-a may have prior knowledge of the priority of UE 115-a based on the previously established RRC connection, the priority associated with the communication supported or used by UE 115-a, etc.). Alternatively, UE 115-a may not have previously established an RRC connection with base station 105-a (e.g., UE 115-a may be attempting initial access to wireless communication system 200), and UE 115-a may receive ULPI 210 indicating that at least a portion of the CBRA resources are being pre-empted. In such a case, it may be valid for UE 115-a to send random access message 215 (e.g., ignoring, disregarding, or overriding ULPI 210), because base station 105-a may have relatively little (or no) prior knowledge of the priority of UE 115-a, the priority associated with the communication supported or used by UE 115-a, etc. That is, in the case where ULPI 210 indicates that at least a portion of the CBRA resources are pre-empted, regardless (e.g., in such a scenario, base station 105-a may not know whether UE 115-a will support ULPI 210 because the services or communications supported by UE 115-a may change the effective dynamic resource allocation of base station 105-a and the use of ULPI 210, etc.), it is valid for UE 115-a to proceed with CBRA message 215.

[0100] Accordingly, the described techniques provide an effective pre-emption configuration for UE 115. The pre-emption configuration can provide more efficient resource utilization and resource allocation within a wireless communication system that supports various service deployments. Specifically, aspects of the described pre-emption configuration can provide effective handling of ULPI 210 for random access message transmission based on whether the random access message 215 is being sent as part of a CFRA procedure or as part of a CBRA procedure. Additionally, aspects of the described pre-emption configuration can provide effective handling of ULPI 210 based on the random access trigger condition (e.g., based on what event or situation triggers the transmission of random access message 215 by UE 115).

[0101] A wireless communication system (e.g., wireless communication system 200) may employ a preemption configuration (e.g., uplink preemption applicability rules, rules for ULPI 210 applications, etc.) to balance the trade-off between the reallocation of previously allocated resources for high-priority communications and the preemption consequences of certain random access messages 215. Thus, the UE 115 may be configured with a preemption configuration and may handle the ULPI 210 according to this preemption configuration (e.g., may send a random access message 215 or preempt the transmission of a random access message 215). Generally, the preemption configuration may refer to a configuration of whether to send a random access message 215 or preempt a random access message 215 based on the type of procedure with which the random access message 215 is associated (e.g., a CFRA procedure or a CBRA procedure), based on the condition that triggers the transmission of the random access message 215 (e.g., an initial access trigger, a beam failure recovery trigger, etc.), and so on.

[0102] In some cases, the UE 115 may be preconfigured with a preemption configuration. In some cases, aspects of the preemption configuration (e.g., one or more rules for whether the ULPI 210 received by the UE 115 applies to a certain random access message 215) may be dynamically configurable. For example, in some cases, the base station 105-a may configure in the ULPI 210 itself the rules for applying the ULPI 210 in RRC signaling (e.g., the ULPI 210 may be associated with a priority based on which the UE 115 may determine whether to apply the ULPI for a random access message 215), and so on.

[0103] As discussed herein, the preemption configuration may selectively preempt a random access channel (RACH) transmission (e.g., a random access message 215 transmission) based on whether the RACH transmission (e.g., a random access message 215 having at least a portion of its corresponding random access resources preempted by the ULPI 210) is part of a CBRA procedure or a CFRA procedure. For example, the ULPI 210 may only apply to (e.g., preempt) a CFRA and may not apply to a CBRA. Specifically, in a 4-step RACH, the ULPI 210 may apply to a CFRA (e.g., a CFRA random access preamble) and may not apply to a CBRA (e.g., a CBRA random access preamble and a CBRA message 3). In a 2-step RACH, the ULPI 210 may apply to a contention-free 2-step RACH (e.g., both the preamble and the data), but may not apply to a contention-based 2-step RACH. The ULPI 210 may not apply to the transmission or retransmission of message 3 scheduled by a PDCCH scrambled with a temporary cell radio network temporary identifier (TC-RNTI) (e.g., because the base station 105-a may not know whether the UE that sent the preamble can support the ULPI).

[0104] In addition, the preemption configuration may selectively preempt a RACH transmission (e.g., a random access message 215 transmission) based on a triggering event (e.g., conditional triggering) that triggers the RACH transmission (e.g., a random access message 215 transmission, at least a portion of the corresponding random access resources of which are preempted by the ULPI 210). For example, RACH events for or triggered by the UE 115 may include: initial access from the RRC_IDLE state, RRC connection reestablishment procedure, downlink or uplink data arrival during RRC_CONNECTED when the uplink synchronization state is "asynchronous", uplink data arrival during RRC_CONNECTED when there are no physical uplink control channel (PUCCH) resources available for a scheduling request (SR), SR failure, RRC request during synchronous reconfiguration (e.g., handover), transition from RRC_INACTIVE, timing alignment establishment when adding a secondary cell (SCell), request for other system information (SI), beam failure recovery, etc.

[0105] According to aspects of the techniques described herein, a preemption configuration may be employed such that the ULPI 210 may be applied to a RACH triggered by: a PDCCH command, beam failure recovery, a request for other SI, a request for uplink resources (e.g., when there is no SR available), SR failure, or some combination thereof. The ULPI 210 may not be applied to a RACH triggered by: initial access, transition from the RRC_INACTIVE state (e.g., to the RRC_CONNECTED state), mobility (e.g., handover), timing advance (TA) establishment for SCell addition, uplink TA reestablishment, RRC connection reestablishment, or some combination thereof.

[0106] For example, ULPI 210 may not be applied to a RACH triggered by initial access or a transition from the RRC_INACTIVE state, because in such cases, it is less likely that the UE monitors ULPI 210 (e.g., UE 115 may only monitor ULPI when in the RRC_CONNECTED state). ULPI 210 may not be applied to a RACH triggered by mobility (e.g., handover), because ULPI 210 may be applied to the current cell, and the UE receiving ULPI 210 may not monitor the ULPI in the target cell (e.g., ULPI 210 may not be applied to the target cell to which the UE is being handed over). ULPI 210 may not be applied to a RACH triggered by TA establishment for SCell addition, because in such cases, the UE may not monitor ULPI for the new SCell. Additionally, ULPI 210 may not be applied to a RACH triggered by uplink TA re-establishment, because without the correct TA, the ULPI may be inaccurate (e.g., without the correct TA, the UE may not be able to accurately apply ULPI).

[0107] In some examples, the preemption configuration may selectively preempt RACH transmissions (e.g., random access message 215 transmissions) based on the cell associated with the random access procedure. For example, the preemption configuration may specify that UE 115-a applies ULPI 210 to RACH transmissions in a secondary serving cell (e.g., SCell), but UE 115-a may not apply ULPI 210 to RACH transmissions in the primary cell (PCell). Generally, the preemption configuration may indicate whether ULPI 210 is applied to random access procedures in different cells (e.g., such as ULPI being applied to random access message 215 in one or more secondary serving cells, but ULPI not being applied to random access message 215 in the primary cell).

[0108] If the ULPI 210 indicates that a portion of the RACH preamble transmission is to be pre-empted (e.g., if the ULPI 210 indicates that at least a portion of the random access resources are being pre-empted), and the pre-emption configuration indicates that the RACH preamble transmission is to be pre-empted (e.g., if the random access message 215 is part of a CFRA procedure, if the random access message 215 is triggered by beam failure recovery or SR failure, etc.), then the UE 115 may abort the entire RACH transmission. For example, pre-emption (e.g., RACH discard) may be indicated on a slot basis, and in cases where the RACH preamble spans more than one slot (e.g., including one or more slots indicated by the ULPI), the UE may discard the entire RACH transmission over the more than one slot spanned by the RACH preamble. That is, in some cases (e.g., for some pre-emption configurations), if any symbol of the random access message 215 is pre-empted (e.g., according to pre-emption configuration rules), then the entire random access message 215 is cancelled (e.g., on all symbols of the random access resources associated with the random access message 215).

[0109] If the RACH preamble is pre-empted by the ULPI 210 (e.g., based on the pre-emption configuration and the CFRA / CBRA type and / or the triggering event of the random access message 215), then the UE may not increase its power, the UE may not increase its preamble_power_ramping_counter, and the UE may not increase its preamble_transmission_counter (e.g., because the RACH preamble is pre-empted and the RACH preamble is thus not associated with a failed transmission to the base station 105-a). In cases where the RACH is initiated by the UE, the UE may use the next immediately available RACH resource to transmit the RACH preamble without performing a time backoff. In cases where the RACH is scheduled by a PDCCH command, the UE may wait for the next PDCCH command.

[0110] Using the techniques described, various other implementations can be considered and can be readily implemented by analogy without departing from the scope of the present disclosure. For example, aspects of the pre-emption configurations described herein can generally be applied to other types of uplink transmissions, other pre-emption indications (e.g., other cancellation indications such as DLPI), pre-emption indications that may include bit sequences of different lengths (e.g., to convey more or less granular pre-emption information), etc.

[0111] Figure 3A and 3B illustrates an example processing flow that supports applying uplink pre-emption to random access transmissions in accordance with aspects of the present disclosure. For example, Figure 3A illustrates an example processing flow 300 for a CBRA procedure, andFigure 3B An example of a processing flow 301 for a CFRA process is shown. In some examples, the processing flow 300 and the processing flow 301 may show aspects of the technologies supported by the wireless communication system 100 and / or the wireless communication system 200. For example, the processing flow 300 and the processing flow 301 may show the processing of ULPI from the base station 105 by the UE 115 according to a preemption configuration, where the base station 105 and the UE 115 may be examples of the corresponding devices described with reference to Figure 1 and Figure 2 the corresponding devices.

[0112] Figure 3A An example processing flow 300 for a CBRA process is shown. As discussed herein, a preemption configuration corresponding to ULPI may not be applied (e.g., not preempt) a random access message associated with a CBRA process. That is, in a case where the ULPI indicates that at least a portion of the CBRA resource is being preempted, the UE 115-c may not apply the ULPI and may send a random access message associated with the CBRA resource according to the CBRA process.

[0113] For example, at 305, base station 105-b may send a ULPI to UE 115-c, where the ULPI may indicate that at least a portion of the random access resources (e.g., associated with a random access preamble at 310 and / or associated with message 3 / scheduled transmission at 320) is being pre-empted. UE 115-c may identify the pre-emption configuration corresponding to the ULPI and may not apply the ULPI according to the pre-emption configuration. Thus, UE 115-c may send a random access preamble at 310, receive a random access response at 315, send message 3 / scheduled transmission at 320, and receive a contention resolution message at 325. In some cases, as discussed herein, the CBRA process shown by processing flow 300 may be triggered by the initial access of UE 115-c or the transition of UE 115-c from the RRC_INACTIVE state. Since the base station 105-b may have little or no knowledge of UE 115-c before or during the initial access (e.g., regarding UE 115-c configuration, or services supported by UE 115-c, whether UE 115-c is monitoring the ULPI, etc.), a pre-emption configuration specifying that the ULPI is not to be applied to such CBRA transmissions may be associated with increased system efficiency, as described in more detail herein. For example, since the base station 105-b may know little or nothing about UE 115-c, it may be unreasonable for the base station 105-b to schedule URLLC transmissions on contention-based PRACH resources because there is no guarantee that UE 115-c (e.g., which is configured to send CBRA on these PRACH resources) will be able to monitor the ULPI and thus pre-empt the transmission. Thus, a pre-emption configuration specifying that UE 115-c may not pre-empt CBRA RACH transmissions may imply that the base station 105-b may not schedule URLLC uplink transmissions on CBRA PRACH resources and may thus improve the reliability of URLLC.

[0114] Figure 3B An example processing flow 301 for the CFRA process is shown. As discussed herein, the pre-emption configuration corresponding to the ULPI may be applied (e.g., pre-empt) a random access message associated with the CFRA process. That is, in the case where the ULPI indicates that at least a portion of the CFRA resources is being pre-empted, UE 115-d may apply the ULPI and may pre-empt the transmission of a random access message associated with the CFRA.

[0115] For example, at 330, base station 105-c may send a ULPI to UE 115-d, where the ULPI may indicate that at least a portion of the random access resources (e.g., associated with a random access preamble at 335) is being pre-empted. UE 115-d may identify the pre-emption configuration corresponding to the ULPI and may apply the ULPI according to the pre-emption configuration. Thus, in the case where UE 115-d receives the ULPI at 330, UE 115-c may pre-empt (e.g., cancel) the transmission of the random access preamble at 335 (e.g., in this case, the random access response may not be sent by base station 105-c as a result). In some cases, as discussed herein, the CFRA process shown in processing flow 301 may be triggered by: UE 115-d mobility (e.g., handover of UE115-d), UE 115-d beam failure recovery, UE 115-d SI request, etc. which may be a PDCCH command. Since base station 105-c may have prior knowledge of UE 115-d (e.g., regarding UE 115-d configuration, or services supported by UE 115-d, whether UE 115-d is monitoring the ULPI, etc.), because UE 115-d may already be connected to base station 105-c, the pre-emption configuration in which the specified ULPI is applied to such CFRA transmissions may be associated with increased system efficiency, as described in more detail herein. In such a case, if base station 105-c sends a ULPI to UE 115-d, base station 105-c may know that UE115-d will be able to monitor the ULPI and apply the ULPI. Thus, it is safe for base station 105-c to schedule URLLC transmissions on contention-free RACH resources (e.g., in terms of guaranteeing URLLC reliability).

[0116] Figure 4 FIG. 400 illustrates an example of a processing flow 400 that supports applying uplink pre-emption to random access transmissions, in accordance with aspects of the present disclosure. In some examples, processing flow 400 may implement aspects of wireless communication system 100 and / or wireless communication system 200. Processing flow 400 may include base station 105-d and UE 115-e, which may be examples of corresponding devices as referenced Figure 1 and Figure 2 described. Processing flow 400 may illustrate a two-step physical random access channel (PRACH) or two-step RACH.

[0117] A two-step RACH can be employed to reduce the waiting time of the RACH procedure. The two-step RACH can be contention-based (e.g., the CBRA procedure). However, some wireless communication systems can support contention-free two-step RACH. In the two-step RACH, the UE 115-e can send a msgA preamble (e.g., which can be similar to or analogous to Message 1 in the four-step RACH) and a msgA payload (e.g., which can be similar to or analogous to Message 3 in the four-step RACH) without waiting for the signaling between the msgA preamble and the msgA payload (e.g., without waiting for the signaling similar to or analogous to Message 2 in the four-step RACH). In some cases, the two-step RACH can be triggered in the same or a similar manner as the four-step RACH (e.g., the two-step CBRA procedure can be associated with the same or similar triggering events as the four-step CBRA procedure, and the two-step CFRA procedure can be associated with the same or similar triggering events as the four-step CFRA procedure).

[0118] At 405, the base station 105-d can send a ULPI to the UE 115-e, where the ULPI can indicate that at least a part of the random access resources (e.g., associated with the transmission of the msgA preamble at 410 and / or associated with the transmission of the msgA payload at 415) is being pre-empted. The UE 115-e can identify the pre-emption configuration corresponding to the ULPI, and can transmit the random access message or the pre-empted random access message (e.g., the msgA preamble at 410 and / or the msgA payload at 415) at least partially based on the pre-emption configuration (e.g., according to the pre-emption configuration). For example, in the case where the two-step RACH of the processing flow 400 is a two-step CBRA procedure, the UE 115-e can not apply the ULPI, and can transmit the msgA preamble at 410 and / or the msgA payload at 415 associated with the CBRA resources according to the two-step CBRA procedure. In the case where the two-step RACH of the processing flow 400 is a two-step CFRA procedure, the UE 115-e can apply the ULPI, and can pre-empt (e.g., cancel) the transmission of the msgA preamble at 410 and / or the msgA payload at 415 associated with the CFRA resources. In the case where the UE 115-e applies the ULPI and pre-empts the transmission of the msgA preamble at 410 and / or the msgA payload at 415, the base station 105-d can thus not perform the msgA preamble / msgA processing and the msgB PDCCH / msg physical downlink shared channel (PDSCH) transmission.

[0119] Additionally or alternatively, as discussed herein, UE 115-e may apply ULPI based on a preemption configuration and a triggering event of a two-step RACH procedure (e.g., based on a triggered condition). For example, as discussed herein, a preemption configuration may be employed such that ULPI may be applied to a two-step RACH procedure triggered by: a PDCCH command, beam failure recovery, a request for other SI, a request for uplink resources (e.g., when no SR is available), SR failure, or some combination thereof. Additionally, ULPI may not be applied to a RACH procedure triggered by: initial access, a transition from the RRC_INACTIVE state (e.g., to the RRC_CONNECTED state), mobility (e.g., handover), timing advance (TA) establishment for SCell addition, uplink TA re-establishment, RRC connection re-establishment, or some combination thereof.

[0120] Figure 5A and 5B FIG. shows an example ULPI diagram supporting the application of uplink preemption to random access transmissions in accordance with aspects of the present disclosure. Figure 5A FIG. shows an example ULPI diagram 500, and Figure 5B FIG. shows an example ULPI diagram 501. In some examples, wireless communication system 100 and / or wireless communication system 200 may implement aspects of ULPI diagram 500 and / or ULPI diagram 501.

[0121] As discussed herein, to pre-empt certain resources (e.g., previously allocated resources such as previously allocated eMBB resources) from being unused (e.g., reclaim the previously allocated resources for other communications such as for URLLC), ULPI can be used. In some cases, ULPI can refer to a bit sequence in DCI. For example, the bits of ULPI can be used to indicate the pre-emption of time and frequency resources. For example, ULPI can include (e.g., or refer to, be configured as, etc.) a 14-bit sequence in DCI. A UE receiving ULPI can know which resources ULPI is indicating for pre-emption based on the configuration of ULPI. For example, the bit sequence or bitmap of ULPI can include bits corresponding to a set of communication resources in the time domain and / or a set of communication resources in the frequency domain. For example, ULPI figure 500 can show ULPI configuration, ULPI correspondence, ULPI mapping, etc., where the bits of the bit sequence indicate the pre-emption of a set of communication resources in the time domain. ULPI figure 501 can show ULPI configuration, ULPI correspondence, ULPI mapping, etc., where the bits of the bit sequence indicate the pre-emption of a set of communication resources in the time and frequency domains. For example, a value '1' in the ULPI bit sequence can indicate that the corresponding resource (e.g., in time and / or frequency) is pre-empted, and a value '0' in the ULPI bit sequence can indicate that the corresponding resource (e.g., in time and / or frequency) is not pre-empted (e.g., unaffected, the same as previously allocated, etc.).

[0122] A UE receiving ULPI can identify the pre-empted resources based on the pre-emption information (e.g., the '1' value in the ULPI bit sequence) and the resources corresponding to that pre-emption information (e.g., where the ULPI resource correspondence can be pre-configured, configured via RRC, implicitly configured based on ULPI signaling, etc.). That is, the ULPI bit sequence can include or indicate a bit sequence or bitmap associated with a set of communication resources in the time domain and / or the frequency domain (e.g., and the receiving UE can determine whether at least a portion of the random access resources corresponds to one or more communication resources in the subset of communication resources indicated for pre-emption by the bitmap). Thus, the UE can identify or determine when the ULPI indicates that at least a portion of the random access resources is being pre-empted based on when the resources pre-empted by ULPI are aligned or overlapped with the random access resources. According to the techniques described herein, once the UE receives a ULPI indicating that at least a portion of the random access resources is being pre-empted, the UE can apply or not apply the ULPI according to the pre-emption configuration.

[0123] As discussed herein, ULPI can be supported by a communication system as a mechanism to achieve dynamic multiplexing between different service types (e.g., between eMBB transmissions and URLLC transmissions). In some cases, ULPI can be referred to as an uplink cancellation indication. In some cases, a base station can indicate ULPI to one or more eMBB users via group common DCI. ULPI can indicate a set of uplink resources on which resources for eMBB transmissions are not available (e.g., the resources indicated by the ULPI can be resources on which the base station can schedule URLLC uplink transmissions). A UE can receive the DCI and can determine the set of resources for preemption indicated by the ULPI. The UE can compare the indicated resources for preemption with the resources scheduled for its own transmissions (e.g., the UE can compare the resources for preemption indicated by the ULPI with its own random access resources). If the resources scheduled by the UE overlap with the set of resources indicated in the group common DCI, the UE can preempt eMBB PUSCH transmissions. As discussed herein, the described techniques can enable a UE to apply ULPI to any resources indicated in the group common DCI that overlap with the UE's random access resources according to a preemption configuration.

[0124] Figure 6 FIG. 600 is an example of a ULPI diagram that supports applying uplink preemption to random access transmissions in accordance with aspects of the present disclosure. In some examples, wireless communication system 100 and wireless communication system 200 can implement aspects of ULPI diagram 600. For example, ULPI diagram 600 can illustrate subcarrier spacing (SCS) considerations for identifying when ULPI indicates preempted resources that are aligned (or overlap) with resources previously allocated to or scheduled for a UE. Specifically, ULPI diagram 600 can illustrate an example where the SCS of the resources indicated by the ULPI is different from the SCS of the random access resources.

[0125] In some cases, the ULPI can be configured to be associated with specific communication resources in the time domain (e.g., in some cases, it can be pre-configured, configured by the base station through RRC configuration, configured by preemption configuration or other configurations). In some examples, resources in the time domain to which preemption (e.g., corresponding to the ULPI) can be applied can be indicated in symbol-level intervals (e.g., symbol duration, OFDM symbol duration, etc.). For example, the ULPI can indicate resources to which preemption can be applied in a set of 7 symbol durations, a set of 14 symbol durations, resources to which preemption can be indicated in sub-slots (e.g., 7 sub-slots each having a length of 2 symbol durations or 4 symbol durations), etc. This partitioning or segmentation can be referred to as the resource granularity in the time domain for preemption. For example, in some cases, a 14-bit ULPI can indicate resources to which preemption can be applied over a set of 14 symbols (e.g., a time slot), where each bit corresponds to a respective symbol over 14 symbol time slot durations. In other examples, a 14-bit ULPI can indicate resources to which preemption can be aligned and applied over the sum of 28 symbols (e.g., two time slots), where each bit corresponds to a respective pair of symbols over 28 symbol durations. Without departing from the scope of the present disclosure, various other preemption indication (e.g., ULPI) configurations can be considered, and these configurations can be easily implemented by analogy. That is, generally, the ULPI can include bit sequences of various lengths, and each bit can correspond to resources of different sizes (e.g., such as one symbol, two symbols, half a symbol, etc.) to convey more or less granular preemption information for various applications.

[0126] In some examples, the SCS for RACH preamble transmission in the active bandwidth part (BWP) of the serving cell can be different from the SCS of the same BWP of the serving cell for uplink data transmission. For example, the symbol duration 605 of the time slot for data transmission can be different from the symbol duration 610 of the time slot for random access transmission (e.g., RACH preamble transmission). In Figure 6 the example of, a full time slot of data transmission resources (e.g., one time slot having an SCS of 30 KHz and a symbol duration 605) is shown over a half RACH time slot of random access resources (e.g., a half time slot having an SCS of 15 KHz and a symbol duration 610).

[0127] For example, the time slot in which the RACH preamble is sent can be referred to as the RACH time slot. In the case where the SCS used for RACH preamble transmission is different from the SCS of the service used for transmitting uplink data (e.g., of the same BWP), the UE can use the SCS of the data channel of the same BWP / service cell to interpret the ULPI (e.g., the UE can use the SCS associated with the data transmission time slot parameter set to interpret the resources preempted by the ULPI). In the case where the RACH SCS is lower than the data SCS, one symbol (e.g., one OFDM symbol) in the RACH time slot can be equal to (e.g., or overlap with) more than one symbol (e.g., more than one OFDM symbol) in a non-RACH time slot (e.g., in a time slot associated with data transmission and thus associated with the ULPI). In this case, the UE can preempt RACH symbols as long as it is indicated that any corresponding non-RACH symbols are to be preempted. For example, in Figure 6 In the example of, if the symbol duration 605-a is indicated to be preempted by the ULPI, the UE can interpret the ULPI as preempting the symbol duration 610-a corresponding to the symbol duration 605-a. The symbol duration 610-a (e.g., the RACH symbol) can correspond to two symbol durations 605 in the SCS of the data channel (e.g., including the symbol duration 605-a). In such an example, the UE can identify that the ULPI indicates that at least a part of the random access resource (e.g., half of the symbol duration 610-a) is preempted, and the UE can apply (e.g., or not apply) the ULPI to the random access resource (e.g., to the symbol duration 610-a) according to the preemption configuration.

[0128] Figure 7A and 7B shows an example processing flow that supports applying uplink preemption to random access transmission according to an aspect of the present disclosure.

[0129] Figure 7A An example processing flow 700 for a scenario where the UE 115 does not preempt the transmission of a random access message (e.g., the UE 115 does not apply or comply with the ULPI) according to the preemption configuration is shown. For example, the processing flow 700 can show a scenario where the ULPI indicates that at least a part of the random access resource associated with the CBRA process is preempted, a scenario where the ULPI indicates that at least a part of the random access resource associated with the random access process triggered by initial access is preempted, etc.

[0130] In some examples, the processing flow 700 can implement aspects of the wireless communication system 100 and / or the wireless communication system 200. In addition, the processing flow 700 can be implemented by the UE 115-f and the base station 105-e, which can be reference Figures 1 - 6Examples of the described UE 115 and base station 105. In the following description of process flow 700, the operations between UE 115-f and base station 105-e may be sent in an order different from the shown order, or the operations performed by base station 105-e and UE 115-f may be performed in a different order or at different times. Certain operations may also be omitted from process flow 700, or other operations may be added to process flow 700. It should be understood that although base station 105-e and UE 115-f are shown performing several operations of process flow 700, any wireless device may perform the shown operations.

[0131] At 705, UE 115-f may identify a preemption configuration. In some examples, the preemption configuration may indicate in which of multiple operating states the UE is to monitor the ULPI. For example, UE 115-f may identify that when UE 115-f is operating in a connected operating state (e.g., RRC_CONNECTED state), the preemption configuration indicates that UE 115-f is to monitor the ULPI. For example, in certain cases, when UE 115-f is in the RRC_CONNECTED state (e.g., and UE 115-f may not monitor the ULPI in the RRC_IDLE state or RRC_INACTIVE state), UE 115-f may monitor the ULPI. That is, in certain cases, the ULPI configuration may be conveyed via RRC configuration (e.g., but not via system information block (SIB) configuration). Thus, an RRC connection may be established between UE 115-f and base station 105-e so that UE 115-f monitors the ULPI.

[0132] As discussed herein, the preemption configuration may also include or indicate instructions or rules for ULPI application for various random access scenarios. For example, the preemption configuration may configure UE 115-f to disregard or ignore the ULPI for certain random access messages (e.g., random access messages for the CBRA procedure), the preemption configuration may configure UE 115-f to disregard or ignore the ULPI for certain random access messages triggered by an event (e.g., random access messages triggered by an initial access attempt, etc.). Additionally, the preemption configuration may configure UE 115-f to apply or comply with the ULPI and preempt certain random access messages (e.g., random access messages for the CFRA procedure), the preemption configuration may configure UE 115-f to apply or comply with the ULPI and preempt random access messages triggered by certain events (e.g., random access messages triggered by beam failure recovery), etc.

[0133] At 710, UE 115-f may monitor the ULPI based on the UE operating in a connected operating state (e.g., according to a preemption configuration), and UE 115-f may receive the ULPI from base station 105-e (e.g., based on the monitoring). In some cases, the ULPI may indicate that at least a portion of the random access resources (e.g., the random access resources for the random access message that UE 115-f intends to send at 720) is being preempted.

[0134] At 715, UE 115-f may identify the rules for ULPI application based on the preemption configuration. In other words, UE 115-f may identify the preemption configuration and may, according to the preemption configuration, identify whether to send a random access message via the random access resources or preempt the transmission of the random access message via the random access resources. In the example of processing flow 700, at 720, UE 115-f may send a random access message according to the preemption configuration.

[0135] For example, UE 115-f may identify that the preemption configuration indicates that uplink preemption does not apply to the CBRA procedure, and UE 115-f may send the random access message at 720 based on the random access message being part of the CBRA procedure.

[0136] In some examples, UE 115-f may identify that the preemption configuration indicates that uplink preemption does not apply to RACH transmissions in the PCell, and UE 115-f may send the random access message at 720 based on the random access message being part of the random access procedure for the PCell.

[0137] Additionally or alternatively, UE 115-f may identify that the preemption configuration indicates that uplink preemption does not apply to random access procedures triggered by at least one of the following: initial access, handover, establishment of timing advance for secondary cell addition, uplink timing advance reestablishment, radio resource control connection reestablishment, or any combination thereof. At 715, UE 115-f may identify that the random access message is part of a random access procedure triggered by initial access, handover, establishment of timing advance for secondary cell addition, uplink timing advance reestablishment, and / or radio resource control connection reestablishment, and UE 115-f may accordingly send the random access message at 720.

[0138] In some examples, for a random access resource, a first SCS of a BWP of a serving cell on which a ULPI is sent may be different from a second SCS of the BWP of the serving cell. In some cases, the transmission of a random access message at 720 may include sending the random access message during a first transmission time interval of a random access resource that does not overlap with a second transmission time interval in which the ULPI indicates preemption, where the first transmission time interval has a longer duration than the second transmission time interval.

[0139] Figure 7B An example processing flow 701 of a scenario for a UE 115 to preempt the transmission of a random access message (e.g., the UE 115 applies or complies with a ULPI) is shown according to a preemption configuration. For example, the processing flow 701 may show a scenario where the ULPI indicates that at least a portion of a random access resource associated with a CFRA procedure is preempted, a scenario where the ULPI indicates that at least a portion of a random access resource associated with a random access procedure triggered by beam failure recovery is preempted, etc.

[0140] In some examples, the processing flow 701 may implement aspects of the wireless communication system 100 and / or the wireless communication system 200. Additionally, the processing flow 701 may be implemented by a UE 115-g and a base station 105-f, which may be examples of the UE 115 and the base station 105 described with reference to Figures 1 - 6 In the following description of the processing flow 701, operations between the UE 115-g and the base station 105-f may be sent in an order different from the order shown, or operations performed by the base station 105-f and the UE 115-g may be performed in a different order or at different times. Certain operations may also be omitted from the processing flow 701, or other operations may be added to the processing flow 701. It should be understood that although the base station 105-f and the UE 115-g are shown performing several operations of the processing flow 701, any wireless device may perform the shown operations.

[0141] At 725, UE 115-g may identify a preemption configuration. In some examples, the preemption configuration may indicate in which of multiple operating states the UE is to monitor the ULPI. For example, UE 115-g may identify that when UE 115-g is operating in a connected operating state (e.g., the RRC_CONNECTED state), the preemption configuration indicates that UE 115-g is to monitor the ULPI. As discussed herein, the preemption configuration may also include or indicate instructions or rules for ULPI application for various random access scenarios. For example, the preemption configuration may configure UE 115-g to disregard or ignore the ULPI for certain random access messages (e.g., random access messages for a CBRA procedure), and the preemption configuration may configure UE 115-g to disregard or ignore the ULPI for certain random access messages triggered by an event (e.g., random access messages triggered by an initial access attempt, etc.). Additionally, the preemption configuration may configure UE 115-g to apply or comply with the ULPI and preempt certain random access messages (e.g., random access messages for a CFRA procedure), and the preemption configuration may configure UE 115-g to apply or comply with the ULPI and preempt random access messages triggered by certain events (e.g., random access messages triggered by beam failure recovery), etc.

[0142] At 730, UE 115-g may monitor the ULPI based on the UE operating in a connected operating state (e.g., according to the preemption configuration), and UE 115-g may receive the ULPI from base station 105-f (e.g., based on the monitoring). In some cases, the ULPI may indicate that at least a portion of the random access resources (e.g., the random access resources for the random access message that UE 115-g intends to send at 740) is being preempted.

[0143] At 735, UE 115-g may identify rules for ULPI application based on the preemption configuration. In other words, UE 115-g may identify the preemption configuration and may, according to the preemption configuration, identify whether to transmit a random access message via the random access resources or to preempt the transmission of the random access message via the random access resources. In the example of process flow 700, at 740, UE 115-g may preempt the transmission of the random access message according to the preemption configuration. In some cases, as discussed herein, at 740, the entire random access message may be preempted (e.g., since the ULPI indicates that at least a portion of the random access resources is being preempted, and according to the preemption configuration, the entire random access message may be preempted).

[0144] For example, UE 115-g may recognize that the preemption configuration indicates that uplink preemption applies to the CFRA process, and UE 115-g may preempt the transmission of the random access message at 720 based on the random access message being part of the CFRA process. For example, at 740, according to the preemption configuration, UE 115-g may preempt the transmission of the random access preamble message and / or the random access payload message associated with the CFRA process.

[0145] In some examples, UE 115-g may recognize that the preemption configuration indicates that uplink preemption applies to RACH transmissions in SCell, and UE 115-f may preempt the transmission of the random access message at 740 based on the random access message being part of the random access process for SCell.

[0146] Additionally or alternatively, UE 115-g may recognize that the preemption configuration indicates that uplink preemption applies to random access processes triggered by at least one of: a downlink control channel command, beam failure recovery, system information request, uplink resource request, scheduling request failure, or any combination thereof. At 735, UE 115-g may recognize that the random access message is part of a random access process triggered by a downlink control channel command, beam failure recovery, system information request, uplink resource request, and / or scheduling request failure, and UE 115-g may accordingly preempt the random access message at 740.

[0147] In some cases, preemption of the random access message at 740 may include preempting the transmission of the random access message based on discarding the random access message on a transmission time interval by transmission time interval basis, where the random access message spans more than one transmission time interval.

[0148] In some cases, when UE 115-g preempts the transmission of the random access message at 740, UE 115-g may not increase the transmit power level, may not increase the preamble power ramping counter, may not increase the preamble transmission counter, or any combination thereof. In some cases, after preempting the transmission of the random access message at 740, UE 115-g may transmit the random access message in the next available random access resource after preempting the random access message transmission via the random access resource.

[0149] In some examples, for a random access resource, a first SCS of a BWP of a serving cell on which a ULPI is sent may be different from a second SCS of the BWP of the serving cell. In certain cases, preemption of an access message at 740 may include preempting transmission of the random access message during a first transmission time interval of the random access resource that overlaps a second transmission time interval in which the ULPI indicates preemption, the first transmission time interval having a longer duration than the second transmission time interval (e.g., as discussed in more detail herein with reference to Figure 6 discussed in more detail).

[0150] Figure 8 FIG. 800 is a block diagram showing a device 805 that supports applying uplink preemption to random access transmissions, in accordance with aspects of the present disclosure. Device 805 may be an example of an aspect of UE 115 as described herein. Device 805 may include a receiver 810, a communication manager 815, and a transmitter 820. Device 805 may also include one or more processors, a memory coupled to the one or more processors, and instructions stored in the memory that are executable by the one or more processors to enable the one or more processors to perform the features discussed herein. Each of these components may communicate with one another (e.g., via one or more buses). The wireless device 805 may also include one or more processors, a memory coupled to the one or more processors, and instructions stored in the memory that are executable by the one or more processors to enable the one or more processors to perform the roaming features discussed herein. Each component of these components may communicate with one another.

[0151] The receiver 810 may receive information associated with various information channels (e.g., control channels, data channels, and information related to applying uplink preemption to random access transmissions, etc.), such as packets, user data, or control information. The information may be passed to other components of device 805. The receiver 810 may be an example of aspects of transceiver 1120 as described in reference to Figure 11 described. The receiver 810 may utilize a single antenna or an antenna array.

[0152] The communication manager 815 may identify a preemption configuration that indicates in which operating state of a set of operating states the UE is to monitor an uplink preemption indication. The communication manager 815 may, based on the preemption configuration, transmit a random access message via a random access resource or preempt transmission of the random access message. The communication manager 815 may be an example of an aspect of communication manager 1110 as described herein.

[0153] The communication manager 815 or its sub-components can be implemented with hardware, code executed by a processor (e.g., software or firmware), or any combination thereof. If implemented with code executed by a processor, the functions of the communication manager 815 or its sub-components can be performed by a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is designed to perform the functions described in this disclosure.

[0154] In some cases, the communication configuration manager 815 can be a processor. The processor can be coupled to a memory and execute instructions stored in the memory that enable the processor to perform or facilitate the communication mode detection and mitigation features discussed herein.

[0155] The communication manager 815 or its sub-components can be physically located in various positions, including being distributed such that portions of the functionality are implemented by one or more physical components in different physical locations. In some examples, according to aspects of the present disclosure, the communication manager 815 or its sub-components can be separate and distinct components. In some examples, according to aspects of the present disclosure, the communication manager 815 or its sub-components can be combined with one or more other hardware components, including but not limited to input / output (I / O) components, transceivers, network servers, another computing device, one or more other components described in this disclosure, or combinations thereof.

[0156] The actions performed by the communication manager 815 described herein can be implemented to achieve one or more potential advantages. One implementation can allow for more efficient resource utilization and resource reallocation within a wireless communication system that supports various service deployments based on different preemption configurations. Another implementation can provide improved quality of service and reliability at the UE 115 because the amount of resources individually allocated to the UE 115 can be reduced.

[0157] The transmitter 820 can transmit signals generated by other components of the device 805. In some examples, the transmitter 820 can be collocated with the receiver 810 in a transceiver module. For example, the transmitter 820 can be an example of aspects of the transceiver 1120 described in Figure 11 The transmitter 820 can utilize a single antenna or an antenna array.

[0158] Figure 9Block diagram 900 of a device 905 that supports applying uplink preemption to a random access transmission in accordance with aspects of the present disclosure is shown. The device 905 may be an example of an aspect of a device 805 or UE 115 as described herein. The device 905 may include a receiver 910, a communication manager 915, and a transmitter 930. The device 905 may also include a processor. Each of these components may communicate with one another (e.g., via one or more buses).

[0159] The receiver 910 may receive information associated with various information channels (e.g., control channels, data channels, information related to applying uplink preemption to a random access transmission, etc.), such as packets, user data, or control information. The information may be passed to other components of the device 905. The receiver 910 may be an example of aspects of the transceiver 1120 described in reference Figure 11 The receiver 910 may utilize a single antenna or an antenna array.

[0160] The communication manager 915 may be an example of aspects of the communication manager 815 described herein. The communication manager 915 may include a preemption configuration manager 920 and a random access preemption manager 925. The communication manager 915 may be an example of an aspect of the communication manager 1110 described herein.

[0161] The preemption configuration manager 920 may identify a preemption configuration that indicates in which operating state of a set of operating states the UE is to monitor an uplink preemption indication. The random access preemption manager 925 may, based on the preemption configuration, transmit a random access message via a random access resource or preempt the transmission of the random access message.

[0162] The transmitter 930 may transmit signals generated by other components of the device 905. In some examples, the transmitter 930 may be collocated with the receiver 910 in a transceiver module. For example, the transmitter 930 may be an example of aspects of the transceiver 1120 described in reference Figure 11 The transmitter 930 may utilize a single antenna or an antenna array.

[0163] In some cases, the preemption configuration manager and the random access preemption manager can each be part of a processing or at least a processor (e.g., a transceiver processor, or a radio processor, or a transmitter processor, or a receiver processor). The processor can be coupled to a memory and execute instructions stored in the memory that enable the processor to perform or facilitate the features of the preemption configuration manager and the random access preemption manager discussed herein. The transceiver processor can be collocated with and / or communicate with (e.g., direct the operation of) the transceiver of the device. The radio processor can be collocated with and / or communicate with (e.g., direct the operation of) the radio of the device (e.g., an NR radio, an LTE radio, a Wi-Fi radio). The transmitter processor can be collocated with and / or communicate with (e.g., direct the operation of) the transmitter of the device. The receiver processor can be collocated with and / or communicate with (e.g., direct the operation of) the receiver of the device.

[0164] Figure 10 FIG. 1000 is a block diagram of a communication manager 1005 that supports uplink preemption for a random access transmission in accordance with aspects of the present disclosure. The communication manager 1005 can be an example of aspects of the communication manager 815, the communication manager 915, or the communication manager 1110 described herein. The communication manager 1005 can include a preemption configuration manager 1010, a random access preemption manager 1015, a ULPI monitoring manager 1020, a ULPI manager 1025, and a random access manager 1030. Each of these modules can communicate directly or indirectly with each other (e.g., via one or more buses).

[0165] The preemption configuration manager 1010 can identify a preemption configuration that indicates in which operating state in a set of operating states the UE is to monitor an uplink preemption indication. In some examples, the preemption configuration manager 1010 can identify a preemption configuration that indicates that the UE is to monitor an uplink preemption indication when operating in a connected operating state in the set of operating states. In some examples, the preemption configuration manager 1010 can identify a preemption configuration that indicates that uplink preemption does not apply to contention-based random access procedures. In some examples, the preemption configuration manager 1010 can identify a preemption configuration that indicates that uplink preemption applies to contention-free random access procedures.

[0166] In some examples, the preemption configuration manager 1010 may identify a preemption configuration indicating that uplink preemption applies to a random access procedure triggered by at least one of the following: a downlink control channel command, beam failure recovery, a system information request, an uplink resource request, a scheduling request failure, or any combination thereof. In some examples, the preemption configuration manager 1010 may identify a preemption configuration indicating that uplink preemption does not apply to a random access procedure triggered by at least one of the following: initial access, handover, establishing a timing advance for adding a secondary cell, re-establishing an uplink timing advance, re-establishing a radio resource control connection, or any combination thereof.

[0167] In some examples, the preemption configuration manager 1010 may identify a preemption configuration indicating that uplink preemption applies to a random access procedure in a secondary cell. In some examples, the preemption configuration manager 1010 may identify a preemption configuration indicating that uplink preemption does not apply to a random access procedure in a primary cell.

[0168] In some cases, the preemption configuration manager 1010 may be a processor (e.g., a transceiver processor, a radio processor, or a receiver processor). The processor may be coupled to a memory and execute instructions stored in the memory that enable the processor to perform or facilitate the communication mode identification features discussed herein. The transceiver processor may be collocated with and / or communicate with (e.g., direct the operation of) the transceiver of the device. The radio processor may be collocated with and / or communicate with (e.g., direct the operation of) the radio of the device (e.g., an NR radio, or an LTE radio, or a Wi-Fi radio). The receiver processor may be collocated with and / or communicate with (e.g., direct the operation of) the receiver of the device.

[0169] The random access preemption manager 1015 may send a random access message or preempt the transmission of the random access message via a random access resource based on the preemption configuration. In some examples, the random access preemption manager 1015 may send a random access message according to a contention-based random access procedure. In some examples, the random access preemption manager 1015 may preempt the transmission of a random access message according to a contention-free random access procedure. In some examples, the random access preemption manager 1015 may preempt the transmission of a random access preamble message. In some examples, the random access preemption manager 1015 may preempt the transmission of a random access preamble message and a random access payload message.

[0170] In some cases, the random access preemption manager 1015 can be a processor (e.g., a transceiver processor, a radio processor, or a receiver processor). The processor can be coupled to a memory and execute instructions stored in the memory that enable the processor to perform or facilitate the communication mode identification features discussed herein. The transceiver processor can be collocated with and / or communicate with (e.g., direct the operation of) the device's transceiver. The radio processor can be collocated with and / or communicate with (e.g., direct the operation of) the device's radio (e.g., an NR radio, or an LTE radio, or a Wi-Fi radio). The receiver processor can be collocated with and / or communicate with (e.g., direct the operation of) the device's receiver.

[0171] In some examples, the random access preemption manager 1015 can preempt the transmission of a random access message. In some examples, the random access preemption manager 1015 can preempt the transmission of an entire random access message. In some examples, the random access preemption manager 1015 can preempt the transmission of the random access message based on discarding the random access message on a transmission time interval-by-transmission time interval basis, where the random access message spans more than one transmission time interval. In some examples, the random access preemption manager 1015 can monitor a second downlink control channel command after preempting the transmission of the random access message. In some examples, the random access preemption manager 1015 can send a random access message.

[0172] In some examples, the random access preemption manager 1015 can preempt the sending of the random access message during a first transmission time interval of a random access resource that overlaps with a second transmission time interval of the preemption indicated by the uplink preemption indication, where the first transmission time interval has a longer duration than the second transmission time interval. In some examples, the random access preemption manager 1015 can send the random access message during a first transmission time interval of a random access resource that does not overlap with a second transmission time interval of the preemption indicated by the uplink preemption indication, where the first transmission time interval has a longer duration than the second transmission time interval. In some cases, for the random access resource, a first subcarrier spacing of a bandwidth part of the serving cell on which the uplink preemption indication is sent is different from a second subcarrier spacing of the bandwidth part of the serving cell.

[0173] The ULPI monitoring manager 1020 may monitor an uplink preemption indication based on the UE operating in a connected operating state within a set of operating states. In some examples, the ULPI monitoring manager 1020 may skip monitoring the uplink preemption indication based on the UE operating in an idle operating state, an inactive operating state, or both within the set of operating states, wherein a random access message is transmitted via a random access resource based on the UE operating in an idle operating state, an inactive operating state, or both within the set of operating states.

[0174] In some cases, the ULPI monitoring manager 1020 may be a processor (e.g., a transceiver processor, a radio processor, or a receiver processor). The processor may be coupled to a memory and execute instructions stored in the memory that enable the processor to perform or facilitate the communication mode identification features discussed herein. The transceiver processor may be collocated with and / or communicate with (e.g., direct the operation of) the transceiver of the device. The radio processor may be collocated with and / or communicate with (e.g., direct the operation of) the radio of the device (e.g., an NR radio, or an LTE radio, or a Wi-Fi radio). The receiver processor may be collocated with and / or communicate with (e.g., direct the operation of) the receiver of the device.

[0175] The ULPI monitoring manager 1020 may receive an uplink preemption indication from a base station indicating that at least a portion of a random access resource has been preempted, wherein based on the uplink preemption indication, a random access message is transmitted or preempted from being transmitted via the random access resource.

[0176] In some cases, the ULPI manager 1025 may be a processor (e.g., a transceiver processor, a radio processor, or a receiver processor). The processor may be coupled to a memory and execute instructions stored in the memory that enable the processor to perform or facilitate the communication mode identification features discussed herein. The transceiver processor may be collocated with and / or communicate with (e.g., direct the operation of) the transceiver of the device. The radio processor may be collocated with and / or communicate with (e.g., direct the operation of) the radio of the device (e.g., an NR radio, or an LTE radio, or a Wi-Fi radio). The receiver processor may be collocated with and / or communicate with (e.g., direct the operation of) the receiver of the device.

[0177] The random access manager 1030 may send a random access message in the next available random access resource after pre-empting the transmission of the random access message via the random access resource. In some examples, the random access manager 1030 may receive a first downlink control channel command scheduling the transmission of the random access message. In certain cases, based on pre-empting the transmission of the random access message, the UE does not increase the transmit power level, does not increment the power ramp counter, does not increment the transmit counter, or any combination thereof.

[0178] In certain cases, the random access manager 1030 may be a processor (e.g., a transceiver processor, a radio processor, or a receiver processor). The processor may be coupled to a memory and execute instructions stored in the memory that enable the processor to perform or facilitate the communication mode identification features discussed herein. The transceiver processor may be collocated with and / or communicate with (e.g., direct the operation of) the device's transceiver. The radio processor may be collocated with and / or communicate with (e.g., direct the operation of) the device's radio (e.g., an NR radio, or an LTE radio, or a Wi-Fi radio). The receiver processor may be collocated with and / or communicate with (e.g., direct the operation of) the device's receiver.

[0179] In certain cases, each of the pre-emption configuration manager 1010, the random access pre-emption manager 1015, the ULPI monitoring manager 1020, the ULPI manager 1025, and the random access manager 1030 may be part of a processing or at least a processor (e.g., a transceiver processor, or a radio processor, or a transmitter processor, or a receiver processor). The processor may be coupled to a memory and execute instructions stored in the memory that enable the processor to perform or facilitate the features of the pre-emption configuration manager 1010, the random access pre-emption manager 1015, the ULPI monitoring manager 1020, the ULPI manager 1025, and the random access manager 1030 discussed herein.

[0180] Figure 11 FIG. 1100 is a schematic diagram of a system 1100 including a device 1105 that supports applying uplink pre-emption to random access transmissions in accordance with aspects of the present disclosure. The device 1105 may be an example of a device 805, a device 905, or a UE 115 as described herein or include components of a device 805, a device 905, or a UE 115. The device 1105 may include components for two-way voice and data communication, which include components for sending and receiving communications, the components for sending and receiving communications including a communication manager 1110, an I / O controller 1115, a transceiver 1120, an antenna 1125, a memory 1130, and a processor 1140. These components may communicate electronically via one or more buses (e.g., bus 1145).

[0181] The communication manager 1110 may identify a preemption configuration that indicates in which operating state in the set of operating states the UE is to monitor the uplink preemption indication. The communication manager 1110 may, based on the preemption configuration, send a random access message via a random access resource or preempt the transmission of the random access message.

[0182] The I / O controller 1115 may manage the input and output signals of the device 1105. The I / O controller 1115 may also manage peripheral devices not integrated into the device 1105. In some cases, the I / O controller 1115 may represent a physical connection or port to an external peripheral device. In some cases, the I / O controller 1115 may utilize an operating system such as MS- MS- OS / or another well-known operating system. In other cases, the I / O controller 1115 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, the I / O controller 1115 may be implemented as part of a processor. In some cases, a user may interact with the device 1105 via the I / O controller 1115 or via a hardware component controlled by the I / O controller 1115.

[0183] As described above, the transceiver 1120 may perform two-way communication via one or more antennas, wired or wireless links. For example, the transceiver 1120 may represent a wireless transceiver and may perform two-way communication with another wireless transceiver. The transceiver 1120 may also include a modem to modulate packets and provide the modulated packets to the antenna for transmission, and to demodulate packets received from the antenna.

[0184] In some cases, the wireless device may include a single antenna 1125. However, in some cases, the device may have more than one antenna 1125, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.

[0185] The memory 1130 may include RAM and ROM. The memory 1130 may store computer-readable, computer-executable code or software 1135 including instructions that, when executed, cause the processor to perform the various functions described herein. In some cases, in addition, the memory 1130 may contain a BIOS that may control basic hardware or software operations, such as interactions with peripheral device components or devices.

[0186] Processor 1140 may include intelligent hardware devices (e.g., a general-purpose processor, DSP, CPU, microcontroller, ASIC, FPGA, programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 1140 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into processor 1140. Processor 1140 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1130) to cause device 1105 to perform various functions (e.g., functions or tasks supporting uplink preemption for a random access transmission application).

[0187] Based on the utilization of different preemption configurations, processor 1140 of UE 115 may save power through more efficient resource utilization because processor 1140 may be ready to respond more efficiently by reducing the rise in processing power.

[0188] Software 1135 may include instructions for implementing aspects of the present disclosure, including instructions for supporting wireless communication. Software 1135 may be stored in a non-transitory computer-readable medium such as system memory or other types of memory. In some cases, software 1135 may not be directly executable by processor 1140 but may cause a computer (e.g., when compiled and executed) to perform the functions described herein.

[0189] Figure 12 Block diagram 1200 of a device 1205 that supports uplink preemption for a random access transmission application in accordance with aspects of the present disclosure is shown. Device 1205 may be an example of aspects of base station 105 as described herein. Device 1205 may include a receiver 1210, a communication manager 1215, and a transmitter 1220. Device 1205 may also include one or more processors, a memory coupled to the one or more processors, and instructions stored in the memory that are executable by the one or more processors to enable the one or more processors to perform the [broad title features] features discussed herein. Each of these components may communicate with one another (e.g., via one or more buses).

[0190] Receiver 1210 may receive information associated with various information channels (e.g., control channels, data channels, and information related to uplink preemption for a random access transmission application, etc.), such as packets, user data, or control information. The information may be passed to other components of device 1205. Receiver 1210 may be an example of aspects of transceiver 1520 described in Figure 15 Receiver 1210 may utilize a single antenna or an antenna array.

[0191] The communication manager 1215 may: establish a connection with a UE in a connected state; send an uplink preemption indication to the UE indicating that at least a portion of the random access resources is being preempted, based on the connected state; and schedule the random access resources based on the uplink preemption indication. The communication manager 1215 may be an example of an aspect of the communication manager 1510 described herein.

[0192] The communication manager 1215 or its sub-components may be implemented in hardware, code executed by a processor (e.g., software or firmware), or any combination thereof. If implemented in code executed by a processor, the functions of the communication manager 1215 or its sub-components may be executed by a general-purpose processor, a DSP, an ASIC, an FPGA, or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in this disclosure.

[0193] The communication manager 1215 or its sub-components may be physically located in various positions, including being distributed such that portions of the functionality are implemented by one or more physical components in different physical locations. In some examples, in accordance with various aspects of the present disclosure, the communication manager 1215 or its sub-components may be separate and distinct components. In some examples, in accordance with various aspects of the present disclosure, the communication manager 1215 or its sub-components may be combined with one or more other hardware components, including but not limited to input / output (I / O) components, transceivers, network servers, another computing device, one or more other components described in this disclosure, or combinations thereof.

[0194] The actions performed by the communication manager 1215 described herein may be implemented to achieve one or more potential advantages. One implementation may allow for more efficient resource utilization and resource reallocation within a wireless communication system that supports various service deployments based on different preemption configurations. Another implementation may provide improved quality of service and reliability at the base station 105, as the number of resources that need to be separately allocated may be reduced.

[0195] The transmitter 1220 may send signals generated by other components of the device 1205. In some examples, the transmitter 1220 may be collocated with the receiver 1210 in a transceiver module. For example, the transmitter 1220 may be an example of aspects of the transceiver 1520 described in Figure 15 reference. The transmitter 1220 may utilize a single antenna or an antenna array.

[0196] Figure 13FIG. 1300 is a block diagram of a device 1305 that supports applying uplink preemption to random access transmissions in accordance with aspects of the present disclosure. The device 1305 may be an example of aspects of the device 1205 or the base station 105 as described herein. The device 1305 may include a receiver 1310, a communication manager 1315, and a transmitter 1335. The device 1305 may also include a processor. Each of these components may communicate with one another (e.g., via one or more buses). The wireless device 1305 may also include one or more processors, a memory coupled to the one or more processors, and instructions stored in the memory that are executable by the one or more processors to enable the one or more processors to perform the roaming features discussed herein. Each of these components may communicate with one another.

[0197] The receiver 1310 may receive information associated with various information channels (e.g., control channels, data channels, information related to applying uplink preemption to random access transmissions, etc.), such as packets, user data, or control information. The information may be passed to other components of the device 1305. The receiver 1310 may be an example of aspects of the transceiver 1520 described in reference Figure 15 The receiver 1310 may utilize a single antenna or an antenna array.

[0198] The communication manager 1315 may be an example of aspects of the communication manager 1215 described herein. The communication manager 1315 may include a UE connectivity manager 1320, a ULPI manager 1325, and a random access manager 1330. The communication manager 1315 may be an example of aspects of the communication manager 1510 described herein.

[0199] The UE connection manager 1320 may establish a connection with a UE in a connected state. The ULPI manager 1325 may send an uplink preemption indication to the UE that indicates that at least a portion of the random access resources are being preempted based on the connection state. The random access manager 1330 may schedule the random access resources based on the uplink preemption indication.

[0200] The transmitter 1335 may send signals generated by other components of the device 1305. In some examples, the transmitter 1335 may be collocated with the receiver 1310 in a transceiver module. For example, the transmitter 1335 may be an example of aspects of the transceiver 1520 described in reference Figure 15 The transmitter 1335 may utilize a single antenna or an antenna array.

[0201] In some cases, each of the UE connectivity manager 1320, ULPI manager 1325, and random access manager 1330 can be part of a processing or at least a processor (e.g., transceiver processor, or radio processor, or transmitter processor, or receiver processor). The processor can be coupled to a memory and execute instructions stored in the memory that enable the processor to perform or facilitate the features of the UE connectivity manager 1320, ULPI manager 1325, and random access manager 1330 discussed herein. The transceiver processor can be collocated with and / or communicate with (e.g., direct the operation of) the transceiver of the device. The radio processor can be collocated with and / or communicate with (e.g., direct the operation of) the radio of the device (e.g., NR radio, LTE radio, Wi-Fi radio). The transmitter processor can be collocated with and / or communicate with (e.g., direct the operation of) the transmitter of the device. The receiver processor can be collocated with and / or communicate with (e.g., direct the operation of) the receiver of the device.

[0202] Figure 14 Block diagram 1400 illustrates a communication manager 1405 in accordance with aspects of the present disclosure that supports uplink preemption for random access transmissions. The communication manager 1405 can be an example of aspects of the communication manager 1215, communication manager 1315, or communication manager 1510 described herein. The communication manager 1405 can include a UE connectivity manager 1410, ULPI manager 1415, and random access manager 1420. Each of these modules can communicate directly or indirectly with each other (e.g., via one or more buses).

[0203] The UE connection manager 1410 can establish a connection with a UE in a connected state. The ULPI manager 1415 can send an uplink preemption indication to the UE, the uplink preemption indication indicating that at least a portion of the random access resources is being preempted based on the connection state.

[0204] In some cases, the UE connectivity manager 1410 can be a processor (e.g., transceiver processor, radio processor, or receiver processor). The processor can be coupled to a memory and execute instructions stored in the memory that enable the processor to perform or facilitate the communication mode identification features discussed herein. The transceiver processor can be collocated with and / or communicate with (e.g., direct the operation of) the transceiver of the device. The radio processor can be collocated with and / or communicate with (e.g., direct the operation of) the radio of the device (e.g., NR radio, or LTE radio, or Wi-Fi radio). The receiver processor can be collocated with and / or communicate with (e.g., direct the operation of) the receiver of the device.

[0205] The random access manager 1420 may schedule random access resources based on the uplink preemption indication. In some examples, the random access manager 1420 may receive a random access message from the UE in the next available random access resource after the transmission of the preempted random access message via the random access resources. In some examples, the random access manager 1420 may send a first control channel command scheduling the transmission of the random access message. In some examples, the random access manager 1420 may send a second control channel command after the transmission of the preempted random access message. In some cases, for the random access resources, the first subcarrier spacing of the bandwidth part of the serving cell on which the uplink preemption indication is sent is different from the second subcarrier spacing of the bandwidth part of the serving cell.

[0206] In some cases, the random access manager 1420 may be a processor (e.g., a transceiver processor, a radio processor, or a receiver processor). The processor may be coupled to a memory and execute instructions stored in the memory that enable the processor to perform or facilitate the communication mode identification features discussed herein. The transceiver processor may be collocated with and / or communicate with (e.g., direct the operation of) the transceiver of the device. The radio processor may be collocated with and / or communicate with (e.g., direct the operation of) the radio of the device (e.g., an NR radio, or an LTE radio, or a Wi-Fi radio). The receiver processor may be collocated with and / or communicate with (e.g., direct the operation of) the receiver of the device.

[0207] In some cases, each of the UE connectivity manager 1410, the ULPI manager 1415, and the random access manager 1420 may be part of a process or at least a processor (e.g., a transceiver processor, or a radio processor, or a transmitter processor, or a receiver processor). The processor may be coupled to a memory and execute instructions stored in the memory that enable the processor to perform or facilitate the features of the UE connectivity manager 1410, the ULPI manager 1415, and the random access manager 1420 discussed herein.

[0208] Figure 15FIG. 1500 is a schematic diagram of a system 1500 including a device 1505 that supports uplink preemption for random access transmissions in accordance with aspects of the present disclosure. The device 1505 may be an example of or include components of the device 1205, the device 1305, or the base station 105 as described herein. The device 1505 may include components for two-way voice and data communication, which may include components for sending and receiving communications, the components for sending and receiving communications including a communication manager 1510, a network communication manager 1515, a transceiver 1520, an antenna 1525, a memory 1530, a processor 1540, and an inter-station communication manager 1545. These components may communicate electronically via one or more buses (e.g., bus 1550).

[0209] The communication manager 1510 may: establish a connection with a UE in a connected state; send an uplink preemption indication to the UE indicating that at least a portion of the random access resources are being preempted based on the connection state; and schedule the random access resources based on the uplink preemption indication.

[0210] The network communication manager 1515 may manage communication with the core network (e.g., via one or more wired backhaul links). For example, the network communication manager 1515 may manage the conveyance of data communication of client devices such as one or more UEs 115.

[0211] As described above, the transceiver 1520 may communicate bidirectionally via one or more antennas, wired or wireless links. For example, the transceiver 1520 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1520 may also include a modem to modulate packets and provide the modulated packets to the antenna for transmission, and to demodulate packets received from the antenna.

[0212] In some cases, a wireless device may include a single antenna 1525. However, in some cases, the device may have more than one antenna 1525, which may be capable of concurrently sending or receiving multiple wireless transmissions.

[0213] The memory 1530 may include RAM, ROM, or a combination thereof. The memory 1530 may store computer-readable code or software 1535 including instructions that, when executed by a processor (e.g., processor 1540), cause the device to perform the various functions described herein. In some cases, in addition, the memory 1530 may contain a BIOS that may control basic hardware or software operations, such as interactions with peripheral device components or devices.

[0214] The processor 1540 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, the processor 1540 may be configured to operate a memory array using a memory controller. In some cases, the memory controller may be integrated into the processor 1540. The processor 1540 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1530) to cause the device 1505 to perform various functions (e.g., support functions or tasks for random access transmission application uplink preemption).

[0215] Based on the utilization of different preemption configurations, the processor 1540 of the base station 105 may save power through more efficient resource utilization because the processor 1540 can be ready to respond more efficiently by reducing the rise in processing power.

[0216] The inter-station communication manager 1545 may manage communication with other base stations 105 and may include a controller or scheduler for cooperating with other base stations 105 to control communication with the UE 115. For example, the inter-station communication manager 1545 may coordinate the scheduling of transmissions to the UE 115 for various interference mitigation techniques such as beamforming or joint transmission. In some examples, the inter-station communication manager 1545 may provide an X2 interface within the LTE / LTE-A wireless communication network technology to provide communication between base stations 105.

[0217] The software 1535 may include instructions for implementing aspects of the present disclosure, including instructions for supporting wireless communication. The software 1535 may be stored in a non-transitory computer-readable medium such as system memory or other types of memory. In some cases, the software 1535 may not be directly executable by the processor 1540 but may cause a computer (e.g., when compiled and executed) to perform the functions described herein.

[0218] Figure 16 A flowchart illustrating a method 1600 for supporting random access transmission application uplink preemption in accordance with aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by the UE 115 or its components as described herein. In some examples, the operations of the method 1600 may be performed by a communication manager as described in reference to Figures 8 - 11 described. In some examples, the UE may execute an instruction set to control functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the functions described below.

[0219] At 1605, the UE can identify a preemption configuration that indicates in which operating state within a set of operating states the UE is to monitor an uplink preemption indication. The operation at 1605 can be performed according to the methods described herein. In some examples, aspects of the operation at 1605 can be performed by a preemption configuration manager as referenced Figures 8 - 11 as described.

[0220] At 1610, the UE can send a random access message via a random access resource or preempt the transmission of the random access message based on the preemption configuration. The operation at 1610 can be performed according to the methods described herein. In some examples, aspects of the operation at 1610 can be performed by a random access preemption manager as referenced Figures 8 - 11 as described.

[0221] Figure 17 FIG. 1700 is a flow diagram illustrating a method 1700 for supporting uplink preemption for a random access transmission in accordance with aspects of the present disclosure. The operations of method 1700 can be implemented by a UE 115 or components thereof as described herein. In some examples, the operations of method 1700 can be performed by a communication manager as referenced Figures 8 - 11 as described. In some examples, the UE can execute an instruction set to control functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE can use dedicated hardware to perform aspects of the functions described below.

[0222] At 1705, the UE can monitor an uplink preemption indication based on the UE operating in a connected operating state within a set of operating states. The operation at 1705 can be performed according to the methods described herein. In some examples, aspects of the operation at 1705 can be performed by a ULPI monitoring manager as referenced Figures 8 - 11 as described.

[0223] At 1710, the UE can receive an uplink preemption indication from a base station, where at least a portion of the random access resources indicated by the uplink preemption indication is being preempted. The operation at 1710 can be performed according to the methods described herein. In some examples, aspects of the operation at 1710 can be performed by a ULPI manager as referenced Figures 8 - 11 as described.

[0224] At 1715, the UE can identify a preemption configuration. The operation at 1715 can be performed according to the methods described herein. In some examples, aspects of the operation at 1715 can be performed by a preemption configuration manager as referenced Figures 8 - 11 as described.

[0225] At 1720, the UE may send a random access message or pre-empt the transmission of the random access message via the random access resources based on the pre-emption configuration. The operation at 1720 may be performed according to the methods described herein. In some examples, aspects of the operation at 1720 may be performed by a random access manager as described with reference to Figures 8 - 11 described.

[0226] Figure 18 FIG. shows a flow diagram of a method 1800 that supports applying uplink pre-emption to random access transmissions in accordance with aspects of the present disclosure. The operations of method 1800 may be implemented by a base station 105 or components thereof as described herein. In some examples, the operations of method 1800 may be performed by a communication manager as described with reference to Figures 12 - 15 described. In some examples, the base station may execute an instruction set to control functional elements of the base station to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform aspects of the functions described below.

[0227] At 1805, the base station may establish a connection with a UE in a connected state. The operation at 1805 may be performed according to the methods described herein. In some examples, aspects of the operation at 1805 may be performed by a UE connectivity manager as described with reference to Figures 12 - 15 described.

[0228] At 1810, the base station may send an uplink pre-emption indication to the UE, the uplink pre-emption indication indicating that at least a portion of the random access resources is being pre-empted based on the connection state. The operation at 1810 may be performed according to the methods described herein. In some examples, aspects of the operation at 1810 may be performed by a ULPI manager as described with reference to Figures 12 - 15 described.

[0229] At 1815, the base station may schedule the random access resources based on the uplink pre-emption indication. The operation at 1815 may be performed according to the methods described herein. In some examples, aspects of the operation at 1815 may be performed by a random access manager as described with reference to Figures 12 - 15 described.

[0230] Figure 19 FIG. shows a flow diagram of a method 1900 that supports applying uplink pre-emption to random access transmissions in accordance with aspects of the present disclosure. The operations of method 1900 may be implemented by a base station 105 or components thereof as described herein. In some examples, the operations of method 1900 may be performed by a communication manager as described with reference to Figures 12 - 15The described communication manager executes. In some examples, the base station may execute an instruction set to control functional elements of the base station to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform aspects of the functions described below.

[0231] At 1905, the base station may establish a connection with a UE in a connected state. The operation at 1905 may be performed according to the methods described herein. In some examples, aspects of the operation at 1905 may be performed by a UE connectivity manager as described in reference to Figures 12 - 15 the UE connectivity manager described.

[0232] At 1910, the base station may send an uplink preemption indication to the UE, where the uplink preemption indication is based on the connection state indicating that at least a portion of the random access resources are being preempted. The operation at 1910 may be performed according to the methods described herein. In some examples, aspects of the operation at 1910 may be performed by a ULPI manager as described in reference to Figures 12 - 15 the ULPI manager described.

[0233] At 1915, the base station may schedule the random access resources based on the uplink preemption indication. The operation at 1915 may be performed according to the methods described herein. In some examples, aspects of the operation at 1915 may be performed by a random access manager as described in reference to Figures 12 - 15 the random access manager described.

[0234] At 1920, the base station may receive a random access message from the UE in the next available random access resource after the transmission of the preempted random access message via the random access resources. The operation at 1920 may be performed according to the methods described herein. In some examples, aspects of the operation at 1920 may be performed by a random access manager as described in reference to Figures 12 - 15 the random access manager described.

[0235] It should be noted that the methods described herein describe possible implementations, and the operations and steps may be rearranged or otherwise modified, and other implementations are possible. Additionally, aspects from two or more methods may be combined.

[0236] The techniques described herein can be used in various wireless communication systems such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), and other systems. CDMA systems can implement radio technologies such as CDMA2000, Universal Terrestrial Radio Access (UTRA), etc. CDMA2000 covers standards such as IS-2000, IS-95, and IS-856. The Release of IS-2000 is commonly referred to as CDMA2000 1X, 1X, etc. IS-856 (TIA-856) is commonly referred to as CDMA2000 1xEV-DO, High Rate Packet Data (HRPD), etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. TDMA systems can implement radio technologies such as Global System for Mobile Communications (GSM).

[0237] OFDMA systems can implement radio technologies such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, etc. UTRA and E-UTRA are part of Universal Mobile Telecommunications System (UMTS). LTE, LTE-A, and LTE-A Pro are UMTS versions that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, LTE-A Pro, NR, and GSM are described in documents from an organization called the "3rd Generation Partnership Project" (3GPP). CDMA2000 and UMB are described in documents from an organization called the "3rd Generation Partnership Project 2" (3GPP2). The techniques described herein can be used in the systems and radio technologies mentioned herein and other systems and radio technologies. Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes and the LTE, LTE-A, LTE-A Pro, or NR terms may be used in most of the description, the techniques described herein can be applicable beyond LTE, LTE-A, LTE-A Pro, or NR applications.

[0238] Macro cells typically cover a relatively large geographical area (e.g., several kilometers in radius) and can allow UEs with a service subscription to the network provider to access without restriction. Compared with macro cells, small cells can be associated with low-power base stations, and small cells can operate in the same or different (e.g., licensed, unlicensed, etc.) frequency bands as macro cells. According to various examples, small cells can include picocells, femtocells, and microcells. For example, a picocell can cover a small geographical area and can allow UEs with a service subscription to the network provider to access without restriction. A femtocell can also cover a small geographical area (e.g., a home) and can provide restricted access to UEs associated with the femtocell (e.g., UEs in a Closed Subscriber Group (CSG), UEs of users in the home, etc.). The eNB for a macro cell can be referred to as a macro eNB. The eNB for a small cell can be referred to as a small cell eNB, a pico eNB, a femto eNB, or a home eNB. An eNB can support one or more (e.g., two, three, four, etc.) cells and can also support communication using one or more component carriers.

[0239] The wireless communication systems described herein can support synchronous or asynchronous operation. For synchronous operation, base stations can have similar frame timings, and transmissions from different base stations can be approximately aligned in time. For asynchronous operation, base stations can have different frame timings, and transmissions from different base stations can not be aligned in time. The techniques described herein can be used for synchronous or asynchronous operation.

[0240] The information and signals described herein can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the specification can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0241] The various illustrative blocks and modules described in connection with the disclosure herein can be implemented or performed with a general-purpose processor, a DSP, an ASIC, an FPGA, or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, microcontroller, or state machine. The processor can also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0242] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions can be stored on or transmitted via a computer-readable medium as one or more instructions or code. Other examples and embodiments are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. The features implementing the functions can also be physically located in various positions, including being distributed such that portions of the functions are implemented at different physical locations.

[0243] Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium can be any available medium that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, non-transitory computer-readable media can include random access memory (RAM), read only memory (ROM), electrically erasable programmable ROM (EEPROM), flash memory, compact disc ROM (CD-ROM) or other optical disc storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store the desired program code in the form of instructions or data structures and that can be accessed by a general purpose or special purpose computer or a general purpose or special purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. As used herein, disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0244] As used herein, including in the claims, the "or" used in a list of items (e.g., a list of items ending with a phrase such as "at least one of..." or "one or more of...") indicates an inclusive list, such that a list of at least one of A, B, or C, for example, means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Further, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an exemplary step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0245] In the drawings, like components or features may have the same reference numeral. Further, various components of the same type may be distinguished by following the reference numeral with a dash and a second label that differentiates among the like components. If only the first reference numeral is used in the specification, the specification applies to any one of the like components having the same first reference numeral, regardless of the second reference numeral or any other subsequent reference numerals.

[0246] The description provided herein in conjunction with the drawings describes exemplary configurations and does not represent all examples that can be implemented or that are within the scope of the claims. The term "exemplary" as used herein means "serving as an example, instance, or illustration" and not "preferred" or "better than other examples". To provide an understanding of the described technology, the detailed description includes specific details. However, the technology may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0247] The present description is provided to enable a person skilled in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication at a user equipment (UE), comprising: identifying a preemption configuration that indicates in which of a plurality of operation states the UE is to monitor an uplink preemption indication, wherein identifying the preemption configuration includes identifying that the preemption configuration indicates that uplink preemption applies to a contention-free random access procedure; and transmitting a random access message via a random access resource or pre-empting transmission of the random access message, at least in part based on the preemption configuration.

2. The method according to claim 1, wherein Identifying the preemption configuration includes: identifying that the preemption configuration indicates to monitor the uplink preemption indication when the UE is operating in a connected operation state among the plurality of operation states.

3. The method according to claim 1, further comprising: monitoring the uplink preemption indication, at least in part based on the UE operating in a connected operation state among the plurality of operation states. [[ID=\\(7\\)]]4. The method according to claim 3, further comprising: receiving, from a network entity, the uplink preemption indication indicating that at least a portion of the random access resource is being pre-empted, wherein, at least in part based on the uplink preemption indication, the random access message is transmitted or pre-empted for transmission via the random access resource.

5. The method according to claim 1, further comprising: skipping monitoring of the uplink preemption indication, at least in part based on the UE operating in an idle operation state, an inactive operation state, or both among the plurality of operation states, wherein, at least in part based on the UE operating in the idle operation state, the inactive operation state, or both, the random access message is transmitted via the random access resource.

6. The method according to claim 1, wherein, Identifying the preemption configuration includes: identifying that the preemption configuration indicates that uplink preemption does not apply to a contention-based random access procedure.

7. The method according to claim 6, wherein Transmitting the random access message or pre-empting transmission of the random access message includes: transmitting the random access message according to the contention-based random access procedure.

8. The method according to claim 1, wherein Transmitting the random access message or pre-empting transmission of the random access message includes: pre-empting transmission of the random access message according to the contention-free random access procedure.

9. The method according to claim 8, wherein Pre-empting transmission of the random access message includes: pre-empting transmission of a random access preamble message.

10. The method according to claim 8, wherein, Pre-empting transmission of the random access message includes: pre-empting transmission of a random access preamble message and a random access payload message.

11. The method according to claim 1, wherein, Identifying the preemption configuration includes: identifying that the preemption configuration indicates that uplink preemption applies to a random access procedure triggered by at least one of: a downlink control channel command, beam failure recovery, system information request, uplink resource request, scheduling request failure, or any combination thereof.

12. The method according to claim 1, wherein Identifying the preemption configuration includes: identifying that the preemption configuration indicates that uplink preemption does not apply to a random access procedure triggered by at least one of: initial access, handover, establishing timing advance for adding a secondary cell, re-establishing uplink timing advance, radio resource control connection re-establishment, or any combination thereof.

13. The method according to claim 1, wherein, Transmitting the random access message or pre-empting transmission of the random access message includes: Preempt the transmission of the random access message.

14. The method according to claim 13, wherein: Preempt the transmission of the entire random access message.

15. The method according to claim 13, wherein, Preempting the transmission of the random access message includes: Preempting the transmission of the random access message based at least in part on discarding the random access message on a transmission time interval by transmission time interval basis, where the random access message spans more than one transmission time interval.

16. The method according to claim 13, wherein, Based at least in part on preempting the transmission of the random access message, the UE does not increase the transmit power level, does not increase the power ramp counter, does not increase the transmit counter, or any combination thereof.

17. The method according to claim 13, further comprising: Transmitting the random access message in the next available random access resource after preempting the transmission of the random access message via the random access resource.

18. The method according to claim 13, further comprising: Receiving a first downlink control channel command scheduling the transmission of the random access message; And monitoring a second downlink control channel command after preempting the transmission of the random access message.

19. The method according to claim 1, wherein Transmitting the random access message or preempting the transmission of the random access message includes: Transmitting the random access message.

20. The method according to claim 1, wherein For the random access resource, the first subcarrier spacing of the bandwidth part of the serving cell on which the uplink preemption indication is transmitted is different from the second subcarrier spacing of the bandwidth part of the serving cell.

21. The method according to claim 20, wherein, Transmitting the random access message or preempting the transmission of the random access message includes: Preempting the transmission of the random access message during a first transmission time interval of the random access resource that overlaps with a second transmission time interval indicated by the uplink preemption indication as being preempted, where the first transmission time interval has a longer duration than the second transmission time interval.

22. The method according to claim 20, wherein, Transmitting the random access message or preempting the transmission of the random access message includes: Transmitting the random access message during a first transmission time interval of the random access resource that does not overlap with a second transmission time interval indicated by the uplink preemption indication as being preempted, where the first transmission time interval has a longer duration than the second transmission time interval.

23. The method according to claim 1, wherein Identifying the preemption configuration includes: Identifying that the preemption configuration indicates that uplink preemption applies to the random access procedure in the secondary cell.

24. The method according to claim 1, wherein Identifying the preemption configuration includes: Identifying that the preemption configuration indicates that uplink preemption does not apply to the random access procedure in the primary cell.

25. A method for wireless communication at a network entity, comprising: Establishing a connection with a user equipment (UE) in a connected state; Sending an uplink preemption indication to the UE indicating that at least a part of the random access resource is being preempted, based at least in part on the connected state; And Scheduling the random access resource based at least in part on the uplink preemption indication.

26. The method according to claim 25, further comprising: Receiving the random access message from the UE in the next available random access resource after preempting the transmission of the random access message via the random access resource.

27. The method according to claim 25, further comprising: sending a first control channel command for scheduling the transmission of a random access message; and sending a second control channel command after pre-empting the transmission of the random access message.

28. An apparatus for wireless communication at a user equipment (UE), comprising: means for identifying a pre-emption configuration indicating in which of a plurality of operating states the UE is to monitor an uplink pre-emption indication, wherein identifying the pre-emption configuration includes identifying that the pre-emption configuration indicates that uplink pre-emption applies to a contention-free random access procedure; and means for sending a random access message via a random access resource or means for pre-empting the transmission of the random access message, at least in part based on the pre-emption configuration.

29. An apparatus for wireless communication at a network entity, comprising: means for establishing a connection with a user equipment (UE) in a connected state; means for sending, at least in part based on the connection state, an uplink pre-emption indication to the UE indicating that at least a part of the random access resource is being pre-empted; and means for scheduling the random access resource, at least in part based on the uplink pre-emption indication.

30. A computer-readable medium having instructions stored thereon, which when executed by a processor cause the processor to perform the method according to any one of claims 1 - 27.

31. A computer program product comprising computer instructions which, when executed by a processor, cause the processor to perform the method according to any one of claims 1 - 27.

Images