Methods and apparatus for validation of preconfigured uplink resources

Abstract

Aspects relate to verifying preconfigured uplink resource (PUR) occasions. For example, a user equipment (UE) can perform a verification procedure for a PUR occasion before using the PUR occasion for an uplink transmission. The verification procedure for the PUR occasion can involve ensuring that the UE will be able to reliably transmit during the PUR occasion. A base station can transmit a PUR configuration to the UE that the UE can use for the verification procedure. The PUR configuration can include timing advance (TA) verification information and PUR verification information that depend at least on a capability of the UE.

Description

[0001] Cross-reference to related applications

[0002] This patent application claims priority and benefit to pending U.S. Provisional Application No. 63 / 079,412, filed on September 16, 2020, entitled “VALIDATION FOR PRE-CONFIGURED UPLINK RESOURCE,” which has been assigned to the assignee of this application and is expressly incorporated herein by reference as if its entire contents were fully set forth below and for all applicable purposes. Technical Field

[0003] In summary, the technologies discussed below relate to wireless communication, and more specifically, the technologies discussed below relate to techniques for verifying the timing of pre-configured uplink resources (PUR). Background Technology

[0004] Next-generation wireless communication systems (e.g., 5GS) may include a 5G core network and a 5G radio access network (RAN) (such as a new radio (NR)-RAN). The NR-RAN supports communication via one or more cells. For example, a wireless communication device such as a user equipment (UE) may access a first cell of a first base station (BS) such as a gNB and / or a second cell of a second base station. The base station may schedule access to cells to support access by multiple UEs. For example, the base station may allocate different resources (e.g., time-domain and frequency-domain resources) for different UEs operating within the base station's cells.

[0005] In recent years, technologies related to the Internet of Things (IoT) have become more widely used. The 3rd Generation Partnership Project (3GPP) has specified cellular solutions for operation in licensed spectrum, including Machine Type Communications (MTC), Narrowband IoT (NB-IoT) communications, and extended coverage for IoT. Unlike short-range and low-power wide-area (LPWA) technologies that operate in unlicensed spectrum, these 3GPP solutions operate in licensed spectrum and can provide guaranteed Quality of Service (QoS). Corresponding applications include, for example, sensors, surveillance cameras, wearable devices, smart meters, and smart meter sensors. Summary of the Invention

[0006] To provide a basic understanding of one or more aspects of this disclosure, an overview of such aspects is given below. This overview is not a general summary of all anticipated features of this disclosure, nor is it intended to identify key or essential elements of all aspects of this disclosure, nor to depict the scope of any or all aspects of this disclosure. Its sole purpose is to present some concepts of one or more aspects of this disclosure in one form as a prelude to the more detailed description given later.

[0007] In some examples, a method for wireless communication at a user equipment is disclosed. The method may include: receiving a pre-configured uplink resource (PUR) configuration, the PUR configuration including PUR authentication information and timing advance (TA) authentication information for a plurality of PUR times. In some aspects, the PUR authentication information and the TA authentication information may depend on at least one capability of the user equipment. The method may further include: performing an authentication process for a first PUR time among the plurality of PUR times based on the PUR authentication information and the TA authentication information; and selectively transmitting uplink transmissions during the first PUR time based on the authentication process.

[0008] In some examples, a user equipment may include: a transceiver; a memory; and a processor coupled to the transceiver and the memory. The processor may be configured to receive, via the transceiver, a pre-configured uplink resource (PUR) configuration, the PUR configuration including PUR authentication information and timing advance (TA) authentication information for multiple PUR times. In some aspects, the PUR authentication information and the TA authentication information may depend on at least one capability of the user equipment. The processor may also be configured to: perform an authentication process for a first PUR time among the multiple PUR times based on the PUR authentication information and the TA authentication information; and, based on the authentication process, selectively transmit uplink transmissions via the transceiver during the first PUR time.

[0009] In some examples, a user equipment may include: a unit for receiving a pre-configured uplink resource (PUR) configuration, the PUR configuration including PUR authentication information and timing advance (TA) authentication information for multiple PUR times. In some aspects, the PUR authentication information and the TA authentication information may depend on at least one capability of the user equipment. The user equipment may further include: a unit for performing an authentication process for a first PUR time among the multiple PUR times based on the PUR authentication information and the TA authentication information; and a unit for selectively transmitting uplink transmissions during the first PUR time according to the authentication process.

[0010] In some examples, an article of art for use by a user equipment includes a non-transitory computer-readable medium having instructions stored therein, executable by one or more processors of the user equipment, to: receive a pre-configured uplink resource (PUR) configuration, the PUR configuration including PUR verification information and timing advance (TA) verification information for a plurality of PUR times. In some aspects, the PUR verification information and the TA verification information may depend on at least one capability of the user equipment. The computer-readable medium may also have instructions stored therein, executable by one or more processors of the user equipment, to: perform a verification process for a first PUR time among the plurality of PUR times based on the PUR verification information and the TA verification information; and selectively transmit uplink transmissions during the first PUR time based on the verification process.

[0011] In some examples, a computer program is described. The computer program may include instructions executable by one or more processors of a user equipment. The computer program may be stored on a computer-readable medium. When executed, the computer program causes one or more processors of the user equipment to: receive a pre-configured uplink resource (PUR) configuration, the PUR configuration including PUR authentication information and timing advance (TA) authentication information for multiple PUR times. In some aspects, the PUR authentication information and the TA authentication information may depend on at least one capability of the user equipment. The computer program may also cause the one or more processors of the user equipment to: perform an authentication process for a first PUR time among the multiple PUR times based on the PUR authentication information and the TA authentication information; and selectively transmit uplink transmissions during the first PUR time based on the authentication process.

[0012] In some examples, a method for wireless communication at a base station is disclosed. The method may include: receiving an indication of at least one capability of a user equipment (UE); and generating a pre-configured uplink resource (PUR) configuration, the PUR configuration including PUR authentication information and timing advance (TA) authentication information for multiple PUR times. In some aspects, the PUR authentication message and the TA authentication information may depend on the at least one capability of the UE. The method may further include: sending the PUR configuration to the UE; and receiving uplink transmissions from the UE during at least one of the multiple PUR times.

[0013] In some examples, a base station may include: a transceiver; a memory; and a processor coupled to the transceiver and the memory. The processor may be configured to: receive, via the transceiver, an indication of at least one capability of a user equipment; and generate a pre-configured uplink resource (PUR) configuration, the PUR configuration including PUR authentication information and timing advance (TA) authentication information for multiple PUR times. In some aspects, the PUR authentication message and the TA authentication information may depend on the at least one capability of the user equipment. The processor may also be configured to: send the PUR configuration to the user equipment via the transceiver; and receive uplink transmissions from the user equipment via the transceiver during at least one of the multiple PUR times.

[0014] In some examples, a base station may include: a unit for receiving an indication of at least one capability of a user equipment; and a unit for generating a pre-configured uplink resource (PUR) configuration, the PUR configuration including PUR verification information and timing advance (TA) verification information for multiple PUR times. In some aspects, the PUR verification message and the TA verification information may depend on the at least one capability of the user equipment. The base station may further include: a unit for sending the PUR configuration to the user equipment; and a unit for receiving uplink transmissions from the user equipment during at least one of the multiple PUR times.

[0015] In some examples, an article of art for use by a base station includes a non-transitory computer-readable medium having instructions stored therein, executable by one or more processors of the base station, to: receive an indication of at least one capability of a user equipment; and generate a pre-configured uplink resource (PUR) configuration, the PUR configuration including PUR authentication information and timing advance (TA) authentication information for multiple PUR times. In some aspects, the PUR authentication message and the TA authentication information may depend on the at least one capability of the user equipment. The computer-readable medium may also have instructions stored therein, executable by one or more processors of the base station, to: send the PUR configuration to the user equipment; and receive uplink transmissions from the user equipment during at least one of the multiple PUR times.

[0016] In some examples, a computer program is described. The computer program may include instructions executable by one or more processors of a base station. The computer program may be stored on a computer-readable medium. When executed, the computer program causes one or more processors of the base station to: receive an indication of at least one capability of a user equipment; and generate a pre-configured uplink resource (PUR) configuration, the PUR configuration including PUR authentication information and timing advance (TA) authentication information for multiple PUR times. In some aspects, the PUR authentication message and the TA authentication information may depend on the at least one capability of the user equipment. The computer program may also cause the one or more processors of the base station to: send the PUR configuration to the user equipment; and receive uplink transmissions from the user equipment during at least one of the multiple PUR times.

[0017] These and other aspects of this disclosure will become more fully understood after reviewing the following detailed description. Other aspects, features, and examples of this disclosure will become apparent to those skilled in the art after reviewing the following description of specific exemplary aspects of this disclosure in conjunction with the accompanying drawings. While features of this disclosure may be discussed below with respect to certain examples and drawings, all examples of this disclosure may include one or more of the advantageous features discussed herein. In other words, while one or more examples may be discussed as having certain advantageous features, one or more such features may also be used according to the various examples of this disclosure discussed herein. Similarly, while exemplary aspects may be discussed below as examples of devices, systems, or methods, it should be understood that such exemplary aspects can be implemented in a variety of devices, systems, and methods. Attached Figure Description

[0018] Figure 1 It is a schematic diagram of a wireless communication system based on some aspects.

[0019] Figure 2 It is a conceptual diagram based on some aspects of radio access networks.

[0020] Figure 3 This is a schematic diagram illustrating an example of utilizing radio resources in an air interface of orthogonal frequency division multiplexing (OFDM) based on certain aspects.

[0021] Figure 4 This is a signaling diagram illustrating an example of an permission-based process between a user equipment (UE) and a base station (BS) according to some aspects.

[0022] Figure 5It is a conceptual diagram based on examples of UE use cases from some aspects.

[0023] Figure 6 This is a signaling diagram illustrating an example of small data transmission during a two-step random access procedure between the UE and the BS, based on some aspects.

[0024] Figure 7 This is a signaling diagram illustrating an example of small data transmission during a four-step random access procedure between the UE and the BS, based on some aspects.

[0025] Figure 8 This is a signaling diagram illustrating an example of an unpermitted process between the UE and BS, based on some aspects.

[0026] Figure 9 This is a signaling diagram illustrating an example of small data transmission via pre-configured uplink resources (PURs) based on some aspects.

[0027] Figure 10 This is a signaling diagram illustrating an example of the PUR verification process based on some aspects.

[0028] Figure 11 This is a schematic diagram illustrating an example of PUR verification timing based on some aspects.

[0029] Figure 12 This is a schematic diagram illustrating another example of PUR verification timing based on some aspects.

[0030] Figure 13 This is a schematic diagram illustrating another example of PUR verification timing based on some aspects.

[0031] Figure 14 This is a flowchart of an example method for PUR verification based on some aspects.

[0032] Figure 15 This is a flowchart of another example method for PUR verification based on some aspects.

[0033] Figure 16 This is a flowchart of another example method for PUR verification based on some aspects.

[0034] Figure 17 This is a block diagram illustrating an example of a hardware implementation for a user device employing a processing system, based on some aspects.

[0035] Figure 18 This is a flowchart of an example method for PUR verification based on some aspects.

[0036] Figure 19 This is a flowchart of another example method for PUR verification based on some aspects.

[0037] Figure 20 This is a block diagram illustrating an example of a hardware implementation of a base station for employing a processing system, based on some aspects.

[0038] Figure 21 This is a flowchart illustrating an example method for configuring PUR verification based on several aspects.

[0039] Figure 22 This is a flowchart of another example method for configuring PUR verification based on some aspects. Detailed Implementation

[0040] The detailed description below, taken in conjunction with the accompanying drawings, is intended as a description of various configurations and not as representing the only configuration in which the concepts described herein can be implemented. To provide a full understanding of the various concepts, the detailed description includes specific details. However, it will be apparent to those skilled in the art that these concepts can be implemented without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0041] While aspects and embodiments are described herein by way of example, those skilled in the art will understand that additional implementations and use cases can arise in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, aspects and / or uses can arise via integrated chip examples and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial devices, retail / purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specific to a particular use case or application, a wide variety of applicability to the described innovations can exist. Implementations can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more aspects of the described innovations. In some practical settings, devices incorporating the described aspects and features may also necessary include additional components and features for the implementation and execution of the claimed and described examples. For example, the transmission and reception of wireless signals necessarily involve multiple components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders / converters, etc.). The innovations described herein are intended to be implemented in a variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc., with different sizes, shapes, and constructions.

[0042] The base station can pre-configure uplink resources that can be used by user equipment (UEs) to transmit small data transmissions (SDTs), etc. For example, the base station can send a configuration to a UE that is currently or will be operating in inactive or idle mode, where the configuration identifies specific pre-configured uplink resources (PURs) that the UE can use for uplink transmission. In some examples, the base station sends this configuration in response to a request from a UE (e.g., a UE with data to send to the base station can request the base station to pre-configure uplink resources for uplink transmission).

[0043] The UE can transmit uplink data on the PUR without establishing a connection to the base station (e.g., without switching to connected mode). Therefore, the UE can use less signaling and / or processing overhead for this uplink transmission compared to uplink transmissions during connected mode. Furthermore, transmitting without establishing a connection to the base station can result in reduced power consumption at the UE, which can be important for IoT wireless devices or other types of UEs, especially those with regular small data transmissions.

[0044] In some examples, a PUR can correspond to a set of PUR opportunities that occur at time intervals. For example, a base station can schedule several periodic PUR opportunities or multiple aperiodic PUR opportunities for a UE.

[0045] In some aspects, this disclosure relates to a verification process for verifying PUR timing. For example, before using a PUR timing for uplink transmission, the UE may perform a timing advance (TA) verification process and a PUR verification process for the PUR timing.

[0046] In some examples, the verification rule can specify that the verification process will be performed within a defined time window. For example, the start of the time window can be defined to ensure that the UE has sufficient time to switch from uplink transmission (e.g., for a previous PUR timing) to downlink reception (e.g., for the verification process) before starting the verification process. As another example, the length of the time window can be defined to ensure that the UE has sufficient time to perform the verification process. As yet another example, the end of the time window can be defined to ensure that the UE has sufficient time to switch from downlink reception (e.g., for the verification process) to uplink transmission for the PUR timing.

[0047] In some examples, the verification process for the PUR timing may involve ensuring that the UE will be able to transmit during the PUR timing. For example, if the UE does not have sufficient time to switch from receiving downlink reception to transmitting uplink transmissions within the PUR timing, the PUR timing may be considered invalid. As another example, if the uplink symbol used for the PUR timing is not aligned with the slot format used for Time Division Duplex (TDD) operation mode, or is not aligned with the uplink-downlink resource configuration used for Half-Duplex-Frequency Division Duplex (HD-FDD) operation mode, the PUR timing may be considered invalid. As a further example, if the uplink symbol used for the PUR timing falls within the slot of another uplink transmission performed by the UE, the PUR timing may be considered invalid. As yet another example, if the UE does not have sufficient time to switch from transmitting a first type of uplink transmission to transmitting a second type of uplink transmission within the PUR timing, the PUR timing may be considered invalid. In some examples, the first type of uplink transmission may involve transmission using a first subcarrier spacing and / or a first bandwidth portion configuration, while the second type of uplink transmission may involve transmission using a second subcarrier spacing and / or a second bandwidth portion configuration.

[0048] The various concepts presented throughout this disclosure can be implemented across a wide range of telecommunications systems, network architectures, and communication standards. See now for reference. Figure 1 As an example and not a limitation, various aspects of this disclosure are illustrated with reference to a wireless communication system 100. The wireless communication system 100 includes three interaction domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106. With the aid of the wireless communication system 100, the UE 106 is capable of performing data communication with an external data network 110 (such as, but not limited to, the Internet).

[0049] RAN 104 can implement any one or more suitable wireless communication technologies to provide radio access to UE 106. As an example, RAN 104 can operate according to the 3GPP New Radio (NR) specification (often referred to as 5G). As another example, RAN 104 can operate according to a hybrid of 5G NR and the Evolved Universal Terrestrial Radio Access Network (eUTRAN) standard (often referred to as Long Term Evolution (LTE)). 3GPP refers to this hybrid RAN as Next Generation RAN or NG-RAN. Of course, many other examples can be utilized within the scope of this disclosure.

[0050] As shown in the figure, RAN 104 includes multiple base stations 108. Broadly speaking, a base station is a network element in a radio access network responsible for radio transmission and reception to or from a UE in one or more cells. In different technologies, standards, or contexts, those skilled in the art may refer to a base station as a base transceiver station (BTS), radio base station, radio transceiver, transceiver functional unit, basic service set (BSS), extended service set (ESS), access point (AP), node B (NB), evolved node B (eNB), gNodeB (gNB), transmit / receive point (TRP), or some other suitable term. In some examples, a base station may include two or more TRPs that may be co-located or non-co-located. Each TRP may communicate on the same or different carrier frequencies within the same or different frequency bands. In an example where RAN 104 operates according to both LTE and 5G NR standards, one base station may be an LTE base station, while the other may be a 5G NR base station.

[0051] RAN 104 is also shown to support wireless communication for multiple mobile devices. In 3GPP standards, a mobile device may be referred to as a User Equipment (UE), but those skilled in the art may also refer to it as a Mobile Station (MS), Subscriber Station, Mobile Unit, Subscriber Unit, Radio Unit, Remote Unit, Mobile Device, Radio Device, Wireless Communication Device, Remote Device, Mobile Subscriber Station, Access Terminal (AT), Mobile Terminal, Radio Terminal, Remote Terminal, Handset, Terminal, User Agent, Mobile Client, Client, or any other suitable term. A UE may be a device (e.g., a mobile device) that provides users with access to network services.

[0052] Within the scope of this disclosure, a “mobile” device does not necessarily need to be capable of movement, and it may be stationary. The term mobile device or mobile equipment broadly refers to a wide variety of devices and technologies. A UE may include multiple hardware structural components that are sized, shaped, and arranged to facilitate communication; such components may include electrically coupled antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc. For example, some non-limiting examples of mobile devices include mobile stations, cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptop computers, personal computers (PCs), notebooks, netbooks, smartbooks, tablet devices, personal digital assistants (PDAs), and a wide variety of embedded systems, for example, corresponding to the “Internet of Things” (IoT).

[0053] Additionally, mobile devices can be automobiles or other vehicles, remote sensors or actuators, robots or robotic devices, satellite radio units, Global Positioning System (GPS) devices, object tracking devices, drones, multi-rotor helicopters, quadcopter helicopters, remote control devices, consumer devices and / or wearable devices such as glasses, wearable cameras, virtual reality devices, smartwatches, health or fitness trackers, digital audio players (e.g., MP3 players), cameras, game consoles, etc. Furthermore, mobile devices can be digital home or smart home devices, such as home audio, video and / or multimedia equipment, appliances, vending machines, smart lighting, home security systems, smart meters, etc. Additionally, mobile devices can be smart energy devices, security devices, solar panels or solar arrays, municipal infrastructure equipment controlling electricity (e.g., smart grids), lighting, water, etc., industrial automation and enterprise equipment, logistics controllers and / or agricultural equipment, etc. Finally, mobile devices can provide connected medical or telemedicine support (e.g., telehealth). Telemedicine devices may include telemedicine monitoring devices and telemedicine management devices, whose communications may be given priority processing or access compared to other types of information, for example, priority access for the transmission of critical service data, and / or QoS related to the transmission of critical service data.

[0054] Wireless communication between RAN 104 and UE 106 can be described as utilizing an air interface. Transmissions over the air interface from a base station (e.g., base station 108) to one or more UEs (e.g., similar to UE 106) can be referred to as downlink (DL) transmissions. According to certain aspects of this disclosure, the term downlink can refer to point-to-multipoint transmissions originating from a base station (e.g., base station 108). Another way to describe this scheme is by using the term broadcast channel multiplexing. Transmissions from a UE (e.g., UE 106) to a base station (e.g., base station 108) can be referred to as uplink (UL) transmissions. According to a further aspect of this disclosure, the term uplink can refer to point-to-point transmissions originating from a UE (e.g., UE 106).

[0055] In some examples, access to the air interface can be scheduled, where a scheduling entity (e.g., base station 108) allocates resources for communication among some or all devices and apparatuses within its service area or cell. As further discussed below in this disclosure, the scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities (e.g., UE 106). That is, for scheduled communication, multiple UEs 106 (which may be scheduled entities) can utilize the resources allocated by the scheduling entity 108.

[0056] Base station 108 is not the only entity that can act as a scheduling entity. That is, in some examples, a UE can act as a scheduling entity, which schedules resources for one or more scheduled entities (e.g., one or more other UEs). For example, a UE can communicate directly with other UEs in a peer-to-peer or device-to-device manner and / or communicate with other UEs in a relay configuration.

[0057] like Figure 1 As shown, scheduling entity 108 can broadcast downlink service 112 to one or more scheduled entities (e.g., one or more UEs 106). Broadly speaking, scheduling entity 108 is a node or device responsible for scheduling services (including downlink service 112, and in some examples, uplink service 116 from one or more scheduled entities (e.g., one or more UEs 106) to scheduling entity 108) in a wireless communication network. On the other hand, a scheduled entity (e.g., UE 106) is a node or device that receives downlink control information 114 (including but not limited to scheduling information (e.g., permission), synchronization or timing information, or other control information) from another entity in the wireless communication network (such as scheduling entity 108). Scheduled entity 106 can also send uplink control information 118 (including but not limited to scheduling requests or feedback information or other control information) to scheduling entity 108.

[0058] Additionally, uplink control information 118 and / or downlink control information 114 and / or downlink traffic information 112 and / or uplink traffic information 116 can be transmitted on a waveform, which can be time-divided into frames, subframes, time slots, and / or symbols. As used herein, a symbol can refer to a time unit carrying one resource element (RE) per subcarrier in an Orthogonal Frequency Division Multiplexing (OFDM) waveform. A time slot can carry 7 or 14 OFDM symbols. A subframe can refer to a duration of 1 millisecond (ms). Multiple subframes or time slots can be grouped together to form a single frame or radio frame. Within this disclosure, a frame can refer to a predetermined duration (e.g., 10 milliseconds) for radio transmission, where each frame consists of, for example, 10 subframes, each each having 1 millisecond (ms). Of course, these definitions are not mandatory, and any suitable scheme for organizing the waveform can be utilized, and various time divisions of the waveform can have any suitable duration.

[0059] Typically, base station 108 may include a backhaul interface for communication with the backhaul portion 120 of wireless communication system 100. Backhaul portion 120 provides a link between base station 108 and core network 102. Furthermore, in some examples, the backhaul network may provide interconnection between corresponding base stations 108. Various types of backhaul interfaces can be employed, such as direct physical connections, virtual networks, or backhaul interfaces using any suitable transport network.

[0060] Core network 102 may be part of wireless communication system 100 and may be independent of the radio access technology used in RAN 104. In some examples, core network 102 may be configured according to 5G standards (e.g., 5GC). In other examples, core network 102 may be configured according to 4G Evolved Packet Core (EPC) or any other suitable standard or configuration.

[0061] Now refer to Figure 2 The schematic diagram of a radio access network (RAN) 200 according to some aspects of this disclosure is provided as an illustrative example and not as a limitation. In some examples, the RAN 200 may be integrated with the network described above and in... Figure 1 The same as RAN 104 shown in the figure.

[0062] The geographical area covered by RAN 200 can be divided into multiple cellular areas (cells), and user equipment (UE) can uniquely identify these cellular areas (cells) based on an identifier broadcast from an access point or base station within the geographical area. Figure 2 Cells 202, 204, 206, and 208 are shown, each of which may include one or more sectors (not shown). A sector is a sub-area of ​​a cell. All sectors within a cell are served by the same base station. Radio links within a sector can be identified by a single logical identifier belonging to that sector. In a cell divided into sectors, multiple sectors within the cell can be formed using multiple sets of antennas, each responsible for communicating with UEs within a portion of the cell.

[0063] Various base stations can be used for deployment. For example, in Figure 2 In this example, two base stations (base station 210 and base station 212) are shown in cells 202 and 204. A third base station (base station 214) is shown as a remote radio head (RRH) 216 controlling cell 206. That is, the base station can have an integrated antenna, or it can be connected to an antenna or RRH 216 via a feeder cable. In the example shown, cells 202, 204, and 206 can be referred to as macro cells because base stations 210, 212, and 214 support cells with large sizes. Furthermore, base station 218 is shown in cell 208, which can overlap with one or more macro cells. In this example, cell 208 can be referred to as a small cell (e.g., small cell, microcell, picocell, femtocell, home base station, home node B, home eNodeB, etc.) because base station 218 supports cells with relatively small sizes. Cell size can be set according to system design and component constraints.

[0064] It is important to understand that RAN 200 can include any number of radio base stations and cells. Furthermore, relay nodes can be deployed to extend the size or coverage area of ​​a given cell. Base stations 210, 212, 214, and 218 provide radio access points to the core network for any number of mobile devices. In some examples, base stations 210, 212, 214, and / or 218 can be used in conjunction with those described above and in... Figure 1 The scheduling entity 108 shown is the same as or similar to that shown.

[0065] Figure 2 This also includes unmanned aerial vehicles (UAVs) 220, which can be drones or quadcopter helicopters. UAV 220 can be configured to act as a base station, or more specifically, as a mobile base station. That is, in some examples, the cell may not be stationary, and the geographical area of ​​the cell can move depending on the location of the mobile base station (such as UAV 220).

[0066] In RAN 200, a cell may include UEs capable of communicating with one or more sectors of each cell. Furthermore, each base station 210, 212, 214, 218 and UAV 220 can be configured to provide access to the core network 102 (see [link to core network]) to all UEs in the corresponding cell. Figure 1 Access points for various mobile base stations. For example, UEs 222 and 224 can communicate with base station 210; UEs 226 and 228 can communicate with base station 212; UEs 230 and 232 can communicate with base station 214 via RRH 216; UE 234 can communicate with base station 218; and UE 236 can communicate with mobile base stations (such as UAV 220). In some examples, UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and / or 242 can communicate with the access points described above and in... Figure 1 The UE / scheduled entity 106 shown is the same as or similar to that shown. In some examples, the UAV 220 (e.g., a quadcopter) can be a mobile network node and can be configured to act as a UE. For example, the UAV 220 can operate in cell 202 by communicating with base station 210.

[0067] In a further aspect of RAN 200, sidelink signaling can be used between UEs without relying on scheduling or control information from the base station. Sidelink communication can be utilized in device-to-device (D2D) networks, peer-to-peer (P2P) networks, vehicle-to-vehicle (V2V) networks, vehicle-to-everything (V2X) networks, and / or other suitable sidelink networks. For example, two or more UEs (e.g., UEs 238, 240, and 242) can communicate with each other using sidelink signal 237 without relaying the communication through a base station. In some examples, UEs 238, 240, and 242 can each act as a scheduling entity or transmitting sidelink device and / or a scheduled entity or receiving sidelink device to schedule resources and transmit sidelink signal 237 between them, without relying on scheduling or control information from the base station. In other examples, two or more UEs (e.g., UEs 226 and 228) within the coverage area of ​​a base station (e.g., base station 212) may also transmit sidelink signals 227 via a direct link (sidelink) without transmitting the communication through base station 212. In this example, base station 212 may allocate resources for sidelink communication to UEs 226 and 228.

[0068] In RAN 200, the ability of a UE to communicate while moving (independent of its location) is referred to as mobility. Various physical channels between the UE and RAN 200 are typically established, maintained, and released under the control of the Access and Mobility Management Function (AMF). In some scenarios, the AMF may include a Security Context Management Function (SCMF) and a Security Anchor Function (SEAF) that performs authentication. The SCMF can manage the security context for both control plane functions and user plane functions, either wholly or partially.

[0069] In various aspects of this disclosure, RAN 200 can utilize DL-based mobility or UL-based mobility to enable movement and handover (i.e., the UE's connection is transferred from one radio channel to another). In a network configured for DL-based mobility, during a call with a scheduling entity, or at any other time, the UE can monitor various parameters of the signal from its serving cell and various parameters of neighboring cells. Based on the quality of these parameters, the UE can maintain communication with one or more of its neighboring cells. During this time, if the UE moves from one cell to another, or if the signal quality from a neighboring cell exceeds the signal quality from the serving cell for a given amount of time, the UE can perform a handoff or handover from the serving cell to a neighboring (target) cell. For example, UE 224 can move from a geographic area corresponding to its serving cell 202 to a geographic area corresponding to a neighboring cell 206. When the signal strength or quality from the neighboring cell 206 exceeds the signal strength or quality from its serving cell 202 for a given amount of time, UE 224 can send a report message to its serving base station 210 indicating this condition. In response, UE 224 can receive a handover command and can perform a handover to cell 206.

[0070] In a network configured for UL-based mobility, the network can utilize UL reference signals from each UE to select a serving cell for each UE. In some examples, base stations 210, 212, and 214 / 216 can broadcast uniform synchronization signals (e.g., a uniform primary synchronization signal (PSS), a uniform secondary synchronization signal (SSS), and a uniform physical broadcast channel (PBCH)). UEs 222, 224, 226, 228, 230, and 232 can receive the uniform synchronization signals, derive carrier frequencies and time slot timings from the synchronization signals, and transmit uplink pilots or reference signals in response to the derived timings. The uplink pilot signal transmitted by a UE (e.g., UE 224) can be concurrently received by two or more cells within RAN 200 (e.g., base stations 210 and 214 / 216). Each cell can measure the strength of the pilot signal, and the radio access network (e.g., one or more of the central nodes within base stations 210 and 214 / 216 and / or the core network) can determine the serving cell for UE 224. As UE 224 moves through RAN 200, RAN 200 can continue to monitor the uplink pilot signal transmitted by UE 224. When the signal strength or quality of the pilot signal measured by a neighboring cell exceeds that measured by the serving cell, RAN 200 can, with or without notifying UE 224, hand over UE 224 from the serving cell to the neighboring cell.

[0071] While the synchronization signals transmitted by base stations 210, 212, and 214 / 216 can be uniform, these signals may not identify a specific cell, but rather an area of ​​multiple cells operating on the same frequency and / or using the same timing. Using areas in 5G networks or other next-generation communication networks enables an uplink-based mobility framework and improves efficiency for both the UE and the network because it reduces the number of mobility messages that need to be exchanged between the UE and the network.

[0072] In various implementations, the air interface in the radio access network 200 can utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum typically provides exclusive use of a portion of the spectrum by means of a license purchased by a mobile network operator from a government regulatory agency. Unlicensed spectrum provides shared use of a portion of the spectrum without requiring a government-authorized license. While some technical rules are usually still required to access unlicensed spectrum, access is generally available to any operator or device. Shared spectrum can fall between licensed and unlicensed spectrum, where some technical rules or restrictions may be required to access the spectrum, but the spectrum can still be shared by multiple operators and / or multiple RATs. For example, a licensee of a portion of licensed spectrum can provide Licensed Shared Access (LSA) to share the spectrum with other parties (e.g., those with appropriate licensee-defined conditions for access).

[0073] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, the two initial operating bands have been designated as frequency range names FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, in various documents and articles, FR1 is generally (interchangeably) referred to as the "below 6 GHz" band. Similar naming issues sometimes arise regarding FR2, although it differs from the Extremely High Frequency (EHF) band (30 GHz - 300 GHz) which is designated as the "millimeter wave" band by the International Telecommunication Union (ITU), it is generally (interchangeably) referred to as the "millimeter wave" band in documents and articles.

[0074] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR studies have designated the operating bands used for these mid-band frequencies as the frequency range name FR3 (7.125 GHz - 24.25 GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, and thus can effectively extend the features of FR1 and / or FR2 to mid-band frequencies. Additionally, higher bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been designated as the frequency range names FR4-a or FR4-1 (52.6 GHz - 71 GHz), FR4 (52.6 GHz - 114.25 GHz), and FR5 (114.25 GHz - 300 GHz). Each of these higher bands falls within the EHF band.

[0075] In light of the foregoing, unless otherwise specifically stated, it should be understood that when the term "below 6 GHz" is used herein, it can broadly refer to frequencies that are less than 6 GHz, within FR1, or may include intermediate frequency band frequencies. Furthermore, unless otherwise specifically stated, it should be understood that when the term "millimeter wave" is used herein, it can broadly refer to frequencies that may include intermediate frequency band frequencies, within FR2, FR4, FR4-a or FR4-1 and / or FR5, or within the EHF band.

[0076] Devices communicating in the radio access network 200 can utilize one or more multiplexing techniques and multiple access algorithms to achieve simultaneous communication between various devices. For example, the 5G NR specification utilizes Orthogonal Frequency Division Multiplexing (OFDM) with a cyclic prefix (CP) to provide multiplexing for UL transmissions from UEs 222 and 224 to base station 210, and for DL ​​transmissions from base station 210 to one or more UEs 222 and 224. Additionally, for UL transmissions, the 5G NR specification provides support for Discrete Fourier Transform Extended OFDM (DFT-s-OFDM) with CP (also known as Single-Carrier FDMA (SC-FDMA)). However, within the scope of this disclosure, multiplexing and multiple access are not limited to the above schemes and can be provided using Time Division Multiple Access (TDMA), Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Sparse Code Multiple Access (SCMA), Resource Extended Multiple Access (RSMA), or other suitable multiple access schemes. In addition, time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM) or other appropriate multiplexing schemes can be used to provide multiplexing for DL ​​transmission from base station 210 to UEs 222 and 224.

[0077] Devices in the radio access network 200 can also utilize one or more duplex algorithms. Duplex refers to a point-to-point communication link where two endpoints can communicate with each other in both directions. Full-duplex means that two endpoints can communicate with each other simultaneously. Half-duplex means that at any given time, only one endpoint can send information to the other. Half-duplex simulations often utilize Time Division Duplex (TDD) for wireless links. In TDD, transmissions in different directions on a given channel are separated from each other using time-division multiplexing. That is, in some scenarios, the channel is dedicated to transmission in one direction, while at other times, the channel is dedicated to transmission in the other direction, where the direction can change very rapidly (e.g., several times per time slot). In wireless links, full-duplex channels typically rely on physical isolation between the transmitter and receiver, as well as appropriate interference cancellation techniques. Full-duplex simulations are often implemented for wireless links using Frequency Division Duplex (FDD) or Space Division Duplex (SDD). In FDD, transmissions in different directions can operate at different carrier frequencies (e.g., within paired spectrum). In SDD, spatial division multiplexing (SDM) separates transmissions in different directions on a given channel from each other. In other examples, full-duplex communication can be implemented in unpaired spectrum (e.g., within a single carrier bandwidth), where transmissions occur in different directions within different subbands of the carrier bandwidth. This type of full-duplex communication may be referred to herein as subband full-duplex (SBFD), also known as flexible duplex.

[0078] Reference Figure 3 The OFDM waveforms illustrated herein are used to describe various aspects of this disclosure. Those skilled in the art will understand that various aspects of this disclosure can be applied to SC-FDMA waveforms in essentially the same manner as described below. That is, while some examples of this disclosure may focus on OFDM links for clarity, it should be understood that the same principles can also be applied to SC-FDMA waveforms.

[0079] Now for reference Figure 3 An expanded view of exemplary subframe 302 is shown, illustrating the OFDM resource grid. However, as those skilled in the art will readily recognize, the physical (PHY) layer transport architecture for any particular application can differ from the example described herein, depending on any number of factors. Here, time is in the horizontal direction, in OFDM symbols; while frequency is in the vertical direction, in subcarriers of a carrier.

[0080] Resource grid 304 can be used to schematically represent time-frequency resources for a given antenna port. That is, in a multiple-input multiple-output (MIMO) implementation with multiple available antenna ports, a corresponding number of resource grids 304 can be available for communication. Resource grid 304 is divided into multiple resource elements (REs) 306. An RE (which is 1 carrier × 1 symbol) is the smallest discrete part of the time-frequency grid and contains a single complex value representing data from a physical channel or signal. Depending on the modulation used in a particular implementation, each RF can represent one or more bits of information. In some examples, a block of REs may be referred to as a physical resource block (PRB) or more simply as a resource block (RB) 308, which contains any appropriate number of consecutive subcarriers in the frequency domain. In one example, an RB may include 12 subcarriers, the number of which is independent of the digital scheme used. In some examples, depending on the digital scheme, an RB may include any appropriate number of consecutive OFDM symbols in the time domain. Within this disclosure, it is assumed that a single RB (such as RB 308) corresponds exactly to a single direction of communication (for a given device, the transmit or receive direction).

[0081] A set of contiguous or non-contiguous resource blocks may be referred to herein as a resource block group (RBG), subband, or bandwidth portion (BWP). A subband or BWP set can span the entire bandwidth. Scheduling a scheduled entity (e.g., a UE) for downlink, uplink, or sidelink transmission typically involves scheduling one or more resource elements 306 within one or more subbands or bandwidth portions (BWPs). Therefore, a UE typically utilizes only a subset of the resource grid 304. In some examples, an RB can be the smallest unit of resources that can be allocated to a UE. Therefore, the more RBs scheduled for a UE and the higher the modulation scheme selected for the air interface, the higher the data rate for the UE. RBs can be scheduled by base stations (e.g., gNB, eNB, etc.) or can be self-scheduled by the UE implementing D2D sidelink communication.

[0082] In this illustration, RB 308 is shown occupying less than the entire bandwidth of subframe 302, with some subcarriers shown above and below RB 308. In a given implementation, subframe 302 can have a bandwidth corresponding to any number of one or more RB 308s. Furthermore, although RB 308 is shown occupying less than the entire duration of subframe 302 in this illustration, this is only one possible example.

[0083] Each 1 ms subframe 302 can consist of one or more adjacent time slots. Figure 3In the example shown, a subframe 302 includes four time slots 310 as an illustrative example. In some examples, time slots may be defined based on a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a time slot may include 7 or 14 OFDM symbols with a nominal CP. Other examples may include micro-time slots (sometimes referred to as shortened transmission time intervals (TTIs)) with shorter durations (e.g., one to three OFDM symbols). In some cases, these micro-time slots or shortened transmission time intervals (TTIs) may be transmitted by consuming resources scheduled for ongoing time slot transmissions for the same or different UEs. Any number of resource blocks can be utilized within a subframe or time slot.

[0084] An expanded view of time slot 310 shows that time slot 310 includes a control region 312 and a data region 314. Typically, control region 312 can carry a control channel, and data region 314 can carry a data channel. Of course, a time slot can contain all DL, all UL, or at least one DL portion and at least one UL portion. Figure 3 The structure shown is merely exemplary in nature, and different time slot structures can be utilized, and different time slot structures can include one or more regions of each of the control region and the data region.

[0085] Despite Figure 3 Although not shown, each RE 306 within RB 308 can be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, etc. Other REs 306 within RB 308 can also carry pilot or reference signals. These pilot or reference signals can provide the receiving device with channel estimation for the corresponding channel, which enables coherent demodulation / detection of the control and / or data channels within RB 308.

[0086] In some examples, time slot 310 can be used for broadcast, multicast, unicast, or unicast communications. For example, broadcast, multicast, or unicast communications can refer to point-to-multipoint transmissions from one device (e.g., a base station, UE, or other similar device) to other devices. Here, broadcast communications are delivered to all devices, while multicast or unicast communications are delivered to multiple intended recipient devices. Unicast communications can refer to point-to-point transmissions from one device to a single other device.

[0087] In an example of cellular communication over a cellular carrier via the Uu interface, for DL ​​transmission, a scheduling entity (e.g., a base station) may assign one or more REs 306 (e.g., within control area 312) to one or more scheduled entities (e.g., UEs) to carry DL control information including one or more DL control channels (such as the Physical Downlink Control Channel (PDCCH)). The terms Uu interface, Uu signaling, etc., generally refer to the wireless communication interface or wireless communication signaling between the RAN (e.g., eNB, gNB, etc.) and wireless communication devices (e.g., UE, IoT devices, etc.). The PDCCH carries downlink control information (DCI), including but not limited to power control commands (e.g., one or more open-loop power control parameters and / or one or more closed-loop power control parameters), scheduling information, and permission and / or assignment of REs for DL ​​and UL transmissions. The PDCCH may also carry hybrid Automatic Repeat Request (HARQ) feedback transmissions, such as acknowledgment (ACK) or negative acknowledgment (NACK). HARQ is a technique well-known to those skilled in the art, in which the integrity of packet transmissions can be verified for accuracy at the receiving end, for example, using any appropriate integrity verification mechanism, such as checksum or cyclic redundancy check (CRC). If the integrity of the transmission is verified, an ACK can be sent; if the integrity of the transmission is not verified, a NACK can be sent. In response to a NACK, the transmitting device can send a HARQ retransmission, which can implement append merging, incremental redundancy, etc.

[0088] The base station can also allocate one or more REs 306 (e.g., in control area 312 or data area 314) to carry other DL signals, such as demodulation reference signals (DMRS); phase tracking reference signals (PT-RS); channel state information (CSI) reference signals (CSI-RS); and synchronization signal blocks (SSBs). SSBs can be broadcast at regular intervals based on a period (e.g., 5, 10, 20, 40, 80, or 160 ms). SSBs include the primary synchronization signal (PSS), secondary synchronization signal (SSS), and physical broadcast control channel (PBCH). The UE can utilize the PSS and SSS to achieve radio frame, subframe, time slot, and symbol synchronization in the time domain, identify the center of the channel (system) bandwidth in the frequency domain, and identify the cell's physical cell identifier (PCI).

[0089] The PBCH in the SSB may also include a Master Information Block (MIB) containing various system information and parameters for decoding the System Information Block (SIB). For example, the SIB may be System Information Type 1 (SIB1), which may include various additional system information. Together, the MIB and SIB1 provide the minimum system information (SI) for initial access. Examples of system information transmitted in the MIB may include, but are not limited to, subcarrier spacing (e.g., default downlink digital scheme), system frame number, PDCCH control resource set (CORESET) configuration (e.g., PDCCH CORESET0), cell prohibition indicator, cell reselection indicator, grid offset, and search space for SIB1. Examples of residual minimum system information (RMSI) transmitted in SIB1 may include, but are not limited to, random access search space, paging search space, downlink configuration information, and uplink configuration information. The base station may also transmit other system information (OSI).

[0090] In UL transmissions, the scheduled entity (e.g., the UE) may utilize one or more RE 306s to carry UL control information (UCI) to the scheduling entity, including one or more UL control channels such as the Physical Uplink Control Channel (PUCCH). UCIs can include a wide variety of packet types and categories, including pilots, reference signals, and information configured to enable or assist in decoding uplink data transmissions. Examples of uplink reference signals may include Sounding Reference Signals (SRS) and Uplink DMRS. In some examples, the UCI may include a scheduling request (SR), i.e., a request to the scheduling entity to schedule uplink transmissions. Here, in response to an SR transmitted on the UCI, the scheduling entity may send downlink control information (DCI), which can schedule resources for uplink packet transmissions. UCIs may also include HARQ feedback, Channel State Feedback (CSF) (such as CSI reports), or any other suitable UCI.

[0091] In addition to control information, one or more REs 306 (e.g., within data area 314) can also be allocated for data services. Such data services can be carried on one or more service channels (e.g., a Physical Downlink Shared Channel (PDSCH) for DL ​​transmissions; or a Physical Uplink Shared Channel (PUSCH) for UL transmissions). In some examples, one or more REs 306 within data area 314 can be configured to carry other signals (such as one or more SIBs and DMRS). In some examples, the PDSCH can carry multiple SIBs, not limited to SIB1 discussed above. For example, OSI can be provided in these SIBs (e.g., SIB2 and above).

[0092] In an example of sidelink communication on a sidelink carrier via the Proximity Service (ProSe) PC5 interface, the control area 312 of time slot 310 may include a Physical Sidelink Control Channel (PSCCH), which includes sidelink control information (SCI) transmitted by an initiating (transmitting) sidelink device (e.g., a Tx V2X device or other Tx UE) toward a set of one or more other receiving sidelink devices (e.g., a receiving (Rx) V2X device or other Rx UE). The data area 314 of time slot 310 may include a Physical Sidelink Shared Channel (PSSCH), which includes sidelink data traffic transmitted by the initiating (transmitting) sidelink device within resources reserved on the sidelink carrier via the transmitting sidelink device through the SCI. Other information may also be transmitted on each RE 306 within time slot 310. For example, HARQ feedback information may be transmitted from the receiving sidelink device to the transmitting sidelink device in the Physical Sidelink Feedback Channel (PSFCH) within time slot 310. Additionally, one or more reference signals (such as lateral link SSB, lateral link CSI-RS, lateral link SRS and / or lateral link positioning reference signal (PRS)) can be transmitted within time slot 310.

[0093] Within the RAN's coverage area, a UE can operate in one of several defined operating states (also known as modes). In some examples, these states include idle, inactive, and connected states. In 5G NR, these operating states are defined as Radio Resource Control (RRC) states: RRC_IDLE, RRC_INACTIVE, and RRC_CONNECTED.

[0094] The UE will be in an idle state (e.g., RRC_IDLE) upon its first power-on. The UE can transition to a connected state with the RAN by performing a random access procedure with the RAN (e.g., RRC_CONNECTED). In the connected state, the UE can communicate with the RAN via dedicated signaling (e.g., dedicated channels). In certain situations, the UE can switch to an idle or inactive state (e.g., RRC_INACTIVE). For example, a UE that does not have data to send to the RAN and is not receiving data from the RAN can choose to switch to an idle or inactive state to conserve battery power. In these states, because the UE is not actively communicating with the RAN, it can power down some of its components (e.g., radio components). That is, the UE enters a lower power state.

[0095] The UE will periodically wake up from a low-power state to monitor signaling from the RAN (e.g., to determine if the RAN has data to send to the UE). This period is based on a Discontinuous Receive (DRX) cycle specified by the RAN. A DRX cycle can include paging time windows that are temporally separated according to the DRX cycle period. Each paging time window corresponds to the period during which the UE wakes up from a low-power state to receive a paging message from the RAN. If the RAN has data to send to the UE, or if the RAN needs to communicate with the UE for other reasons, the RAN will page the UE according to the DRX cycle (i.e., during the paging time window during which the UE periodically wakes up from a low-power state). The RAN transmits the paging message via a paging channel (e.g., via a paging frame). Furthermore, the RAN can define different paging opportunities that can be used by different UEs to receive paging messages. That is, the UE remains in a low-power state until its own paging opportunity occurs. Using different paging opportunities for different UEs allows the RAN to direct paging to a specific UE or a small subset of UEs. This reduces the likelihood that a UE will need to consume battery power to process a paging directed to another UE. Upon receiving a paging message instructing the network to send data (or other information) that the UE needs to receive, the UE can resume all operations (e.g., turn on all radio components) and, if necessary, re-establish the connection with the RAN.

[0096] The physical channels described above are typically multiplexed and mapped to transport channels for processing at the Media Access Control (MAC) layer. The transport channels carry blocks of information called transport blocks (TBs). The transport block size (TBS), which can correspond to the number of bits of information, can be a controlled parameter based on the modulation and coding scheme (MCS) and the number of redundancies (RBs) in a given transmission.

[0097] exist Figure 3 The channels or carriers shown may not be all the channels or carriers that can be used between devices, and those skilled in the art will recognize that other channels or carriers, such as other service, control and feedback channels, may be used in addition to the channels or carriers shown.

[0098] As described above, considering user QoS requirements, wireless networks can employ a scheduler (e.g., executing scheduling algorithms) to dynamically allocate radio resources to users. The scheduler can also consider CSI and target block error rate (BLER) to allocate channel resources for transmitting buffered data. Link adaptation based on adaptive modulation and coding can be employed to improve the spectral efficiency associated with these transmissions. The scheduler can multiplex transmissions allocated per user to utilize available time-frequency resources. The scheduling algorithm executed by the scheduler can ensure efficient channel utilization and fairness for serving multiple users while meeting any QoS requirements. For 5G NR, scheduling prioritization for services can be allocated within short transmission time intervals (TTIs) to satisfy service requirements.

[0099] In the downlink, resource allocation and dynamic link adaptation can be rapidly provided by transmitting DCI within the same transmission time interval (TTI) as the data. Therefore, the UE can quickly process control information using the indicated parameters and then decode the data accordingly.

[0100] However, in the uplink, permission-based processes are typically used for resource allocation. Figure 4 This is a signaling diagram 400 illustrating a permission-based process between a user equipment (UE) 402 and a base station (BS) 404, according to some aspects. In some examples, UE 402 may correspond to... Figure 1 , 2 The UE or any of the scheduled entities shown in any of the figures in 6-10 and 17. In some examples, BS 404 may correspond to... Figure 1 , 2 Any of the base stations or scheduling entities shown in any of the figures in 6-10 and 20.

[0101] When data 406 becomes available for transmission at UE 402 (e.g., data 406 arrives in UE 402's transmission buffer), UE 402 processes the data and waits for a specific opportunity to send a scheduling request (SR) 410 to BS 404. BS 404 processes SR 410 and sends a scheduling grant 412 to UE 402 via DCI, where the DCI contains allocation and transmission parameters. UE 402 processes scheduling grant 412 and uses the granted resources to send data 414 to BS 404, which processes and receives data 406. (As in...) Figure 4 As can be seen, the delay 416 used for this process is shown as the time period from the time when data 406 is received in the buffer of UE 402 to the time period when data 406 is received by BS 404.

[0102] refer to Figure 5LTE includes support for advanced services 502, such as low-power wide-area (LPWA) communications and massive machine-type communications (mMTC). Furthermore, previous 3GPP releases for NR (e.g., Rel-15 and Rel-16) included support for high-performance features (advanced 5G), such as ultra-reliable low-latency communications (URLLC) 504, enhanced mobile broadband (eMBB) 506, and vehicle-to-everything (V2X) communications (not shown).

[0103] NR also supports more efficient and cost-effective scalability and deployment. Therefore, a new UE type with reduced capabilities (RedCap UE 508) has been defined. RedCap UEs can have one or more of the following: lower peak throughput requirements, less stringent latency requirements, or less stringent reliability requirements. Examples of RedCap UEs include, but are not limited to, sensors, cameras, IoT devices with less stringent requirements, and smart wearables. In some examples, RedCap UEs can be battery-powered. For RedCap UEs, resource allocation can be scalable, coverage enhancements can be provided for DL ​​and UL, additional power savings can be provided in all Radio Resource Control (RRC) states, and coexistence with NR Advanced UEs can be supported.

[0104] Therefore, in an operating environment supporting RedCap UEs (also known as “NR Lightweight”), RedCap UEs can be configured to have lower device complexity and reduced power consumption (compared to what can be provided by conventional NR devices, such as conventional NR UEs). For example, conventional NR devices may have higher requirements in terms of data rate and latency compared to what is provided by, for example, LTE Machine Type Communication (MTC) and Narrowband Internet of Things (NB-IoT) communication. Regarding reduced device complexity, RedCap UEs can be configured to support a reduced number of transmit and / or receive (TX / RX) antennas on the device side, a reduced minimum required device bandwidth, and / or support devices that can only operate in half-duplex mode on paired spectrum (e.g., devices that do not support simultaneous TX / RX). Regarding reduced device power consumption, RedCap UEs can be configured to have reduced complexity in PDCCH monitoring by reducing the number of blind decodings required, and can be configured to have extended discontinuous reception (DRX) functionality. Those skilled in the art will understand that while the examples in this disclosure are suitable for applications utilizing RedCap UEs, they can also be applied to conventional NR configurations.

[0105] In some examples, RedCap UEs may have relatively low uplink transmission requirements. For instance, a sensor might only occasionally send small amounts of data when the sensed condition occurs. In a given... Figure 4Given the relatively complex signaling and relatively long latency involved in permitted uplink transmissions, it is desirable to avoid such signaling overhead and latency for RedCap UEs (e.g., to increase battery life and improve RedCap UE performance).

[0106] Therefore, the UE (e.g., a RedCap UE) can be configured to transmit small data transmissions during a two-step or four-step Random Access Channel (RACH) procedure in the initial bandwidth portion (BWP) or active BWP. For example, the UE can select a preamble configured for uplink small data transmission during the RACH. Advantageously, the UE can transmit data while in RRC_INACTIVE mode. Therefore, the UE does not need to switch to RRC_CONNECTED mode to transmit data.

[0107] Figure 6 Signaling diagram 600 illustrates a two-step RACH procedure between UE 602 and BS 604, according to some aspects. In some examples, UE 602 may correspond to... Figure 1 , 2 Any UE or scheduled entity shown in any of the figures in 7-10 and 17. In some examples, BS 604 may correspond to... Figure 1 , 2 Any of the base stations or scheduling entities shown in any of the figures 7-10 and 20. In this example, at point 1, UE 602 can send a small amount of data (Mobile-Initiated (MO) UL data) to BS 604 in Msg-A of the two-step RACH procedure. Furthermore, at point 2, BS 604 can send a small amount of data (DL data) to UE 602 in Msg-B of the two-step RACH procedure. As in Figure 6 As indicated in the document, the UE can remain in RRC_INACTIVE mode to send UL data and receive DL data.

[0108] Figure 7 Signaling diagram 700 illustrates a four-step RACH procedure between UE 702 and BS 704, according to some aspects. In some examples, UE 702 may correspond to... Figure 1 , 2 Any of the UEs or scheduled entities shown in any of the figures in 6, 8-10, and 17. In some examples, BS 704 may correspond to... Figure 1 , 2Any of the base stations or scheduling entities shown in any of the figures in 6, 8-10, and 20. To initiate the four-step RACH procedure, at point 1, UE 702 sends a first message to BS 704 including a Physical Random Access Channel (PRACH) preamble. The transmission of the PRACH preamble can be referred to as Msg-1 of the four-step RACH procedure. At point 2, BS 704 responds with a second message including a Random Access Response (RAR) (also referred to as a RACH response). The second message can be referred to as Msg-2 of the four-step RACH procedure and can include both a PDCCH (which can be referred to as Msg-2 (PDCCH)) and a PDSCH carrying the RAR (which can be referred to as Msg-2 (PDSCH)). In this example, at point 3, UE 702 can send a small amount of data (Mobile-Initiated (MO) UL data) to BS 704 in Msg-3 of the four-step RACH procedure. Furthermore, at point 4, BS 604 can send a small amount of data (DL data) to UE 602 in Msg-4 of the four-step RACH procedure. For example, in Figure 7 As indicated in the document, the UE can remain in RRC_INACTIVE mode to send UL data and receive DL data.

[0109] As Figure 6 and 7 As an alternative to the RACH-based procedure, the UE can be pre-configured to have uplink resources. This type of resource allocation procedure can be called a permissionless procedure. By providing pre-configured uplink resources, the use of Msg-1 and Msg-2, as well as the need for performing traditional connection establishment procedures, can be avoided. Furthermore, compared to the RACH-based procedure, the UE can use less signaling to send more data to the base station. In some examples, the UE can be configured to have uplink resources (e.g., obtaining UE-specific radio resources for uplink transmissions, Radio Network Temporary Identifier (RNTI) for uplink transmissions, etc.) while in a connected state via dedicated RRC signaling.

[0110] Figure 8 Signaling diagram 800 illustrates an example of an unpermitted procedure between UE 802 and BS 804 according to some aspects. In some examples, UE 802 may correspond to... Figure 1 , 2 Any of the UEs or scheduled entities shown in any of the figures in 6, 7, 9, 10, and 17. In some examples, BS 804 may correspond to... Figure 1 , 2 Any of the base stations or scheduling entities shown in any of the figures in 6, 7, 9, 10, and 20.

[0111] BS 804 pre-configures UE 802 with uplink resource allocation and uplink transmission parameters via resource configuration 806. When data 808 (e.g., packets) becomes available for transmission at UE 802, the UE processes the data and aligns it with the configured resources 810, and transmits data 812 using the pre-allocated resources, thereby BS 804 receives and processes data 808. It should be noted that in this case, UE 802 does not need to... Figure 4 The scheduling request is sent to BS804 in the permission-based process. Therefore, with Figure 4 Compared to the permission-based process, Figure 8 The process can have lower control channel overhead and reduced reliance on control signaling (which can be error-prone and cause delays). Furthermore, as in... Figure 8 As indicated in the document, and Figure 4 The delay of this process is shorter than that of the permitted process delay 416.

[0112] Figure 9 Signaling diagram 900 illustrates an example of a Mobile-Initiated (MO) Small Data Transfer (SDT) between UE 902 and BS 904 on a dedicated, pre-configured uplink resource (PUR), according to some aspects. In some examples, UE 902 may correspond to... Figure 1 , 2 Any of the UEs or scheduled entities shown in any of the figures in 6-8, 10, and 17. In some examples, BS 904 may correspond to... Figure 1 , 2 Any of the base stations or scheduling entities shown in any of the figures in 6-8, 10, and 20.

[0113] In some examples, when UE 902 is in RRC_CONNECTED mode, pre-configured uplink resources can be configured. For example, BS 904 can be configured in conjunction with the above. Figure 8 (exist Figure 9 (Not shown in the text) A similar approach is used to pre-configure uplink resources for UE 902. These pre-configured uplink resources can then be used for subsequent uplink small data transfers (SDTs) when UE 902 is in RRC_INACTIVE mode. For example, in Figure 9In this process, UE 902 can enter RRC_INACTIVE mode after receiving an RRC release message from BS 904 at point 1. At point 2, UE 902 can send an SDT to BS 904 in an RRC recovery request message. BS 904 can then forward this uplink data 908 to (e.g., the user plane function (UPF) 906 of the core network node). Furthermore, in response to the RRC recovery request message, BS 904 can send an RRC release message to UE 902 at point 3, thereby keeping UE 902 in RRC-INACTIVE mode. Figure 9 As shown, UE 902 can also monitor DL ​​data 912 forwarded by BS 904. In other examples, UE 902 can send UL data and receive DL data in other messages. Figure 9 As shown, the UE can remain in RRC_INACTIVE mode to send UL data and receive DL data.

[0114] As can be seen from the above, using PUR-based small data transmission can save UE power and reduce signaling overhead in the wireless communication network. PUR timing can be configured for both regular UEs and RedCap UEs. The use of PURs can be particularly useful for RedCap UEs, which may require coverage enhancements for DL ​​signaling and may need higher power efficiency.

[0115] In the PUR configuration, intra-slot and / or inter-slot repetitions for PUSCH can be used for RedCap UEs. For example, such repetitions can be used to compensate for coverage loss caused by RedCap UEs due to reduced capabilities. In some examples, these reduced capabilities may include reduced bandwidth, a reduced number of TX / RX antennas, reduced antenna efficiency (e.g., due to device size limitations), or a combination thereof.

[0116] In some examples, if the UE is configured to have PUR resources, the UE verifies timing advance (TA) before transmitting on the PUR timing to avoid interfering with UL transmissions (e.g., PUSCH, PUCCH, SRS, PRACH) performed by other UEs. Not every PUR timing is valid for the UE due to factors such as: potential UL / DL handover gaps required for TDD and HD-FDD communication, potential digital scheme changes in the UL waveform, and potential BWP handover.

[0117] In some respects, this disclosure relates to the PUR verification process for a UE. The PUR verification process can be applied to both regular UEs and RedCap UEs.

[0118] PUR timing verification can be performed jointly with TA verification or separately. In some examples, if TA verification is performed before PUR verification and fails, the UE can skip PUR timing verification and transmissions during the PUR timing. In some examples, if TA verification is performed before PUR verification and succeeds, the UE can perform PUR timing verification based on the rules discussed below. In some examples, if PUR timing verification is performed before TA verification and fails, the UE can skip TA verification and transmissions during the PUR timing. In some examples, if PUR timing verification is performed before TA verification and succeeds, the UE can perform TA verification based on the rules for TA verification.

[0119] A timer can be configured for the UE to verify TA and PUR. In some examples, the start time and length of this timer can be configured via RRC signaling. If the UE transmits at the PUR time, in some examples, the UE may need to complete both TA and PUR verifications before the timer expires. The timer configuration can be cell-specific (e.g., independent of UE capabilities) or cell- and UE-specific (e.g., dependent on at least one or more of the UE's capabilities).

[0120] Below are some examples of rules used for PUR timing verification. Other rules may be used in other examples.

[0121] In the first example, if the UE is configured to have PUR resources and operates in TDD or HD-FDD mode, a valid PUR timing must meet the following rule: the PUR timing must be at least [distance] from the last DL symbol. N A symbol, N >0, where, N Subcarrier spacing (SCS) depends on the PUR timing. Parameter N These parameters can be hard-coded in the UE (e.g., specified by a standard) or determined by the base station. N It can be configured as a function of UE capabilities (e.g., UE processing capabilities, UE UL / DL switching time, UE PUR capabilities, or some other UE capability).

[0122] In the second example, one or more of the following rules may be applied: (1) The UL symbol used by the PUR timing must be aligned with the TDD time slot format. (2) The UL symbol used by the PUR timing must be aligned with the DL-UL resource configuration allocated for HD-FDD across different carriers. (3) The UL symbol used by the PUR timing cannot share the same time slot with previous transmissions of other UL signals / channels by the UE.

[0123] In the third example, the PUR timing must be at least [distance] from the preceding UL signal / channel. K A symbol. K >0. Parameters K SCS can depend on the timing of PUR. Parameters K These parameters can be hard-coded in the UE (e.g., specified by a standard) or determined by the base station. K Functions that can be configured as UE capabilities (e.g., processing capabilities).

[0124] Figure 10 Signaling diagram 1000 illustrates an example of the PUR authentication process in a communication system including BS 1002 and UE 1004, according to some aspects. In some examples, BS 1002 may correspond to... Figure 1 , 2 Any of the base stations or scheduling entities shown in any of the figures in 6-9 and 20. In some examples, UE 1004 may correspond to... Figure 1 , 2 The UE or any of the scheduled entities shown in any of the figures in 6-9 and 17.

[0125] At 1006, UE 1004 sends a capability message and / or a PUR configuration request message to BS 1002. The capability message may include indications of one or more capabilities of UE 1004, such as PUR capabilities. In some examples, this UE capability information may include information indicating power headroom (PH) for UE 1004, buffer status reports (BSR), and channel state information (CSI) reports. The PUR configuration request message may include, for example, indications of the service mode for the upcoming UL transmission for the UE, the period of the UL transmission, and the amount of data to be transmitted. In some examples, the PUR configuration request may include UE capability information.

[0126] At locations 1008 and 1010, BS 1002 generates a PUR configuration for UE 1004 and sends an RRC configuration including the PUR configuration to UE 1004. In some examples, the PUR configuration may be based on at least one capability of the UE. In some examples, the PUR configuration may include one or more of the following: a PUR timer configuration for UE verification of TA and PUR timing, PUR resource allocation, an MCS or TBS configuration for PUR, power control parameters for PUR, a PUR response (PDCCH) monitoring window and search space configuration, a Transmission Configuration Indicator (TCI) status for PUR response, or the UE's PUR RNTI. In some examples, the PUR configuration may include information and / or parameters for pause and / or recovery procedures associated with PUR and TA verification failures. For example, the PUR resource allocation may be a single PUSCH slot, aggregated PUSCH slots, regular slots, micro-slots, or some other suitable allocation. In some examples, BS 1002 can allocate periodic and / or non-periodic PUR resources to UE 1004.

[0127] At 1012, for each PUR timing, UE 1004 verifies the TA used for the PUR timing and verifies the PUR timing. For example, to verify the TA, UE 1004 may measure the timing DL reference signal (e.g., synchronization signal block (SSB) signal) from BS 1002 and determine whether UE 1004's timing is sufficiently close (e.g., substantially synchronized with) BS 1002's timing (e.g., subframe timing). In some examples, UE 1004 may measure the received reference signal power (RSRP) to determine whether UE 1004 has moved relative to BS 1002 compared to previous measurements when UE 1004 is synchronized with BS 1002 (e.g., when UE 1004 receives a TA command from BS 1002, for example, during a RACH procedure).

[0128] If the TA verification process for the PUR time slot and / or the PUR verification process for the PUR time slot fails, UE1004 may suspend the PUR time slot. For example, UE1004 may avoid sending data during the PUR time slot.

[0129] In some cases (e.g., due to limited UE capabilities), the UE may be unable to successfully perform the measurements required for TA verification. For example, when SSB and UL transmissions overlap and the UE capability is only half-duplex, the UE cannot perform SSB-based DL measurements for TA verification. Since the UE has no DL measurements available for TA verification in this situation, TA verification can be considered to have failed, resulting in a pause in the PUR timing.

[0130] At 1014, for each verified PUR timing, UE 1004 transmits user plane data and / or control plane data to BS 1002 via the corresponding PUR timing. As discussed herein, UE 1004 may transmit on PUR timings when it is in IDLE mode or INACTIVE mode (or some other mode).

[0131] Figure 11 An example of a PUR verification timing 1100 is shown, which includes a PUR verification period that can be used to verify the PUR timing (e.g., PUR timing k+1). In this example, the PUR timer configuration for the UE to verify the TA and PUR timing includes a time period T. PUR and time period S PUR or E PUR At least one of the following. The PUR timing verification process is conducted within the time period T. PUR Executed during the period. Time period S PUR Defined in time period T PUR The time period preceding the start of [the event / event]. Time period E PUR Defined in time period T PUR The time period following the end of the current period. The timer configuration can be cell-specific or UE-specific (depending on at least one UE capability).

[0132] exist Figure 11 In the example, the PUR verification period (T) used for PUR timing k+1 PUR The defined time period (S) following the end of the previous PUR timing k. PUR It begins at ) . In addition, the PUR verification period (T PUR The time period (E) defined before the start of PUR timing k+1. PUR End at ) . For example, at Figure 11 As shown in the example, S PUR It begins at time 11:02 and ends at time 11:04 (verification period T). PUR It ends at the beginning (of the sentence). Furthermore, E... PUR At the third time 11:06 (verification period T) PUR It begins at the end of the period and ends at the fourth time 1108 (the beginning of the PUR time K+1).

[0133] Figure 12 An example of a PUR verification timing 1200 is shown, including the PUR verification requirement for PUR timing k+1. For example, in (as discussed above) Figure 11 Time period T PUR The PUR verification process performed during this period can determine whether the PUR timing k+1 is satisfied. Figure 12 The PUR verification requirements. Here, in order for PUR timing k+1 to be valid, the time period T from time 1202 of the last downlink (DL) symbol (not shown) to PUR timing k+1 is... D It must be greater than or equal to N ∙ Tµ (T D ≥ In some examples, time 1202 is the time of the last DL symbol before the PUR timing. DL symbols can belong to a TDD slot or can be on a DL carrier operating in HD-FDD. Parameters N [symbol] is the minimum gap between the last DL symbol (before PUR) and the effective PUR timing. The duration of the PUSCH symbol representing the PUR timing, where SCS is determined by... kHz and Provided.

[0134] Figure 13 Another example of a PUR verification timing 1300, including the PUR verification requirement for PUR timing k+1, is shown. For example, in (as discussed above) Figure 11 Time period T PUR The PUR verification process performed during this period can determine whether the PUR timing k+1 is satisfied. Figure 13 The PUR verification requirements. Here, for PUR timing k+1 to be valid, the time period T is from time 1302 of the last uplink (UL) symbol (not shown) before PUR timing k+1 to the time of PUR timing k+1. U It must be greater than or equal to K ∙ Tµ (T U ≥ ).parameter K [symbol] is the minimum gap between the last UL symbol (before the PUR) and the effective PUR timing. The duration of the PUSCH symbol representing the PUR timing, where SCS is determined by... kHz and That's what they gave.

[0135] In cases where a specific PUR timing is deemed invalid (e.g., PUR timing is paused), the UE can take different actions for subsequent PUR timings in different examples. In some examples, if the UE pauses the first PUR timing, the UE can resume PUR authentication and TA authentication at the next PUR timing. In some examples, if the UE pauses the first PUR timing, the UE can pause subsequent PUR timings based on a pre-configured counter or timer (which can be controlled by a threshold). In this case, the UE can resume PUR authentication and TA authentication after the counter or timer expires. In some examples, if the UE pauses the first PUR timing, the UE can pause all subsequent PUR timings in the configured set of PUR timings. As mentioned above, information and / or parameters can be specified in the PUR configuration for the UE to use for the pause and / or resume procedures associated with PUR and TA authentication failures. Figure 14-16 An example of a user device procedure that can be used when the PR timing is paused is shown.

[0136] Figure 14 This is a flowchart illustrating an example method 1400 for wireless communication according to some aspects of this disclosure. Method 1400 illustrates an example scenario where, after pausing a first PUR timing, the UE resumes PUR authentication and TA authentication at the next PUR timing. As described below, in certain implementations within the scope of this disclosure, some or all of the shown features may be omitted, and some shown features may not be necessary for all example implementations. In some examples, method 1400 may be performed by... Figure 17 The method is performed by UE 1700 shown below. In some examples, method 1400 may be performed by any suitable means or unit for performing the functions or algorithms described below.

[0137] At box 1402, the user equipment can determine that the first PUR timing is not valid. For example, (e.g., in...) Figure 10 The TA verification and / or PUR verification performed at position 1012 may have failed for a specific PUR opportunity in the assigned set of PUR opportunities.

[0138] At box 1404, the user equipment can pause the first PUR timing. For example, the user equipment can avoid using the first PUR timing to send data.

[0139] At box 1406, the user equipment can perform verification for the second PUR timing. For example, even if the first PUR timing fails verification, the user equipment can still perform verification (e.g., instead of simply pausing all PUR timings) for the second PUR timing in the set of PUR timings (e.g., the next PUR timing following the first PUR timing). If the verification for the second PUR timing passes, the user equipment can use the second PUR timing to send data. Conversely, if the verification for the second PUR timing fails, the user equipment will not use the second PUR timing to send data. In some examples, verification can be performed for the second PUR timing even if it is not valid. Figure 14 For example, if the second PUR timing is not valid, the UE can still perform verification for the third PUR timing, and so on.

[0140] Figure 15 This is a flowchart illustrating an example method 1500 for wireless communication according to some aspects of this disclosure. Method 1500 illustrates an example scenario where, after pausing a first PUR timing, the UE can pause subsequent PUR timings for a period of time. As described below, in certain implementations within the scope of this disclosure, some or all of the shown features may be omitted, and some shown features may not be necessary for all example implementations. In some examples, method 1500 may be performed by... Figure 17 The method is performed by UE 1700 shown below. In some examples, method 1500 may be performed by any suitable means or unit for performing the functions or algorithms described below.

[0141] At box 1502, the user equipment can determine that the first PUR timing is not valid. For example, (e.g., in...) Figure 10 The TA verification and / or PUR verification performed at position 1012 may have failed for a specific PUR opportunity in the assigned set of PUR opportunities.

[0142] At box 1504, the user equipment pauses the first PUR timing. For example, the user equipment can avoid using the first PUR timing to send data.

[0143] At box 1506, the user equipment can pause subsequent PUR opportunities for a defined period of time. For example, when pausing the first PUR opportunity, the user equipment can start a timer, and while the timer is running, the user equipment pauses (does not send) any PUR opportunities that occur within that time period in the PUR opportunity set. Once the timer expires (or the timer reaches a threshold), the user equipment can perform verification on any subsequent PUR opportunity in the PUR opportunity set.

[0144] Figure 16This is a flowchart illustrating an example method 1600 for wireless communication according to some aspects of this disclosure. Method 1600 illustrates an example scenario where, after pausing a first PUR timing, the UE can pause one or more subsequent PUR timings. As described below, in certain implementations within the scope of this disclosure, some or all of the shown features may be omitted, and some shown features may not be necessary for all implementations of the examples. In some examples, method 1600 may be performed by... Figure 17 The method is performed by UE 1700 shown below. In some examples, method 1600 may be performed by any suitable means or unit for performing the functions or algorithms described below.

[0145] At box 1602, the user equipment can determine that the first PUR timing is not valid. For example, (e.g., in...) Figure 10 The TA verification and / or PUR verification performed at position 1012 may have failed for a specific PUR opportunity in the assigned set of PUR opportunities.

[0146] At box 1604, the user equipment pauses the first PUR timing. For example, the user equipment may avoid using the first PUR timing to send data.

[0147] At box 1606, the user equipment can pause a specified number of PUR opportunities after the first PUR opportunity. For example, when pausing the first PUR opportunity, the user equipment can start a counter, and before the counter reaches a specified threshold count, the user equipment can pause any PUR opportunity in the PUR opportunity set (without transmitting on it). Once the counter reaches the threshold count, the user equipment can perform verification on any subsequent PUR opportunity in the PUR opportunity set.

[0148] Figure 17 This is a block diagram illustrating an example hardware implementation of a UE 1700 employing a processing system 1714. For example, the UE 1700 could be a device configured to communicate wirelessly with a base station, as in... Figure 1-16 The discussion is in any one or more of the diagrams. In some implementations, UE 1700 may correspond to... Figure 1 , 2 And any of the UEs or scheduled entities shown in any of the figures in 6-10.

[0149] According to various aspects of this disclosure, any element, any part of an element, or any combination of elements may be implemented using processing system 1714. Processing system 1714 may include one or more processors 1704. Examples of processors 1704 include microprocessors, microcontrollers, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuitry, and other suitable hardware configured to perform the various functions described throughout this disclosure. In various examples, UE 1700 may be configured to perform any one or more of the functions described herein. That is, processor 1704, as utilized in UE 1700, may be used to implement any one or more of the processes and procedures described herein.

[0150] In some implementations, the processor 1704 may be implemented via a baseband or modem chip, while in other implementations, the processor 1704 itself may include multiple devices that are distinct from and different from the baseband or modem chip (e.g., in scenarios where they can work together to implement the embodiments discussed herein). Furthermore, as mentioned above, various hardware arrangements and components other than the baseband modem processor can be used in the implementations, including RF chains, power amplifiers, modulators, buffers, interleavers, adders / converters, etc.

[0151] In this example, processing system 1714 can be implemented using a bus architecture, typically represented by bus 1702. Depending on the specific application and overall design constraints of processing system 1714, bus 1702 can include any number of interconnect buses and bridges. Bus 1702 communicatively couples together various circuits including one or more processors (typically represented by processor 1704), memory 1705, and computer-readable media (typically represented by computer-readable media 1706). Bus 1702 can also link various other circuits such as timing sources, peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further. Bus interface 1708 provides an interface between bus 1702 and transceiver 1710, and between bus 1702 and interface 1730. Transceiver 1710 provides a communication interface or unit for communicating with various other devices over a wireless transmission medium. In some examples, the UE may include two or more transceivers 1710, each configured to communicate with a corresponding network type (e.g., terrestrial or non-terrestrial). Interface 1730 provides a communication interface or unit for communicating with various other devices and equipment (e.g., other devices housed within the same device or other external devices) over an internal bus or external transmission medium (such as an Ethernet cable). Depending on the nature of the device, interface 1730 may include a user interface (e.g., a keypad, display, speaker, microphone, joystick). Of course, such a user interface is optional and may be omitted in some examples (such as IoT devices).

[0152] Processor 1704 is responsible for managing bus 1702 and general processing, including executing software stored on computer-readable medium 1706. When executed by processor 1704, the software causes processing system 1714 to perform the various functions described below for any particular device. Computer-readable medium 1706 and memory 1705 may also be used to store data manipulated by processor 1704 when executing the software. For example, memory 1705 may include PUR information 1715 (e.g., PUR configuration) that can be used by processor 1704 for PUR-related operations as discussed herein.

[0153] One or more processors 1704 in the processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc. Software may reside on computer-readable media 1706.

[0154] Computer-readable medium 1706 may be a non-transitory computer-readable medium. For example, non-transitory computer-readable media include magnetic storage devices (e.g., hard disks, floppy disks, magnetic tapes), optical disks (e.g., compressed optical disks (CDs) or digital versatile optical disks (DVDs)), smart cards, flash memory devices (e.g., card, stick, or key drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. Computer-readable medium 1706 may be located within processing system 1714, outside of processing system 1714, or distributed across multiple entities including processing system 1714. Computer-readable medium 1706 may be embodied in a computer program product. For example, a computer program product may include a computer-readable medium having encapsulation material. Those skilled in the art will recognize how the functions described throughout this disclosure are best implemented, depending on the specific application and the overall design constraints imposed on the system as a whole.

[0155] UE 1700 can be configured to perform any one or more of the operations described herein (e.g., as combined above). Figure 1-16 As described, and in combination with the following text Figure 18 and 19 (As described). In some aspects of this disclosure, such as the processor 1704 utilized in UE 1700, circuitry may be configured for various functions.

[0156] Processor 1704 may include communication and processing circuitry 1741. Communication and processing circuitry 1741 may be configured to communicate with a base station, such as a gNB. Communication and processing circuitry 1741 may include one or more hardware components providing a physical structure that performs various processes as described herein related to wireless communication (e.g., signal reception and / or signal transmission). Communication and processing circuitry 1741 may also include one or more hardware components providing a physical structure that performs various processes as described herein related to signal processing (e.g., processing received signals and / or processing signals for transmission). In some examples, communication and processing circuitry 1741 may include two or more transmit / receive chains, each configured to process signals of different RAT (or RAN) types. Communication and processing circuitry 1741 may also be configured to execute communication and processing software 1751 included on computer-readable medium 1706 to implement one or more of the functions described herein. Communication and processing circuitry 1741 may also be configured to control antenna array 1720 and transceiver 1710.

[0157] The communication and processing circuitry 1741 can also be configured to generate a request and send the request to the base station. For example, the request may include: a MAC-CE carried in the PUSCH, a UCI in the PUCCH or PUSCH, a random access message, or an RRC message. The communication and processing circuitry 1741 can also be configured to generate a scheduling request and send the scheduling request to the base station (e.g., via a UCI in the PUCCH) to receive uplink permission for a PUSCH carrying a MAC-CE including a request for uplink beam refinement.

[0158] The communication and processing circuitry 1741 can also be configured to generate and transmit uplink signals. Uplink signals may include, for example, PUCCH, PUSCH, SRS, DMRS, or PRACH.

[0159] In some implementations where communication involves receiving information, communication and processing circuitry 1741 may obtain information from components of UE 1700 (e.g., transceiver 1710 that receives information via radio frequency signaling or some other type of signaling suitable for an applicable communication medium), process (e.g., decode) the information, and output the processed information. For example, communication and processing circuitry 1741 may output information to another component of processor 1704, memory 1705, or bus interface 1708. In some examples, communication and processing circuitry 1741 may receive one or more of signals, messages, other information, or any combination thereof. In some examples, communication and processing circuitry 1741 may receive information via one or more channels. In some examples, communication and processing circuitry 1741 may include the functionality of a receiving unit. In some examples, communication and processing circuitry 1741 may include the functionality of a decoding unit.

[0160] In some implementations where communication involves sending (e.g., transmitting) information, communication and processing circuitry 1741 may obtain information (e.g., from another component of processor 1704, memory 1705, or bus interface 1708), process (e.g., encode) the information, and output the processed information. For example, communication and processing circuitry 1741 may output information to transceiver 1710 (e.g., which transmits information via radio frequency signaling or some other type of signaling suitable for an applicable communication medium). In some examples, communication and processing circuitry 1741 may send one or more of signals, messages, other information, or any combination thereof. In some examples, communication and processing circuitry 1741 may transmit information via one or more channels. In some examples, communication and processing circuitry 1741 may include the functionality of units for sending (e.g., units for transmitting). In some examples, communication and processing circuitry 1741 may include the functionality of units for encoding.

[0161] According to some examples, processor 1704 may include PUR configuration circuitry 1742, which is configured to perform PUR configuration-related operations as discussed herein (e.g., in conjunction with...). Figure 5-13 (One or more of the operations described herein). Furthermore, in some examples, the PUR configuration circuit 1742 may be configured to execute the PUR configuration software 1752 included on the computer-readable medium 1706 to implement one or more of the functions described herein.

[0162] The PUR configuration circuit 1742 may include the function of a unit for transmitting capability information. For example, the PUR configuration circuit 1742 may be configured to perform... Figure 10 One or more of the operations described at 1006 include obtaining capability information of the UE 1700 to be sent to the gNB and cooperating with the communication and processing circuitry 1741 (e.g., instructing the communication and processing circuitry 1741) to send a message including the capability information to the gNB.

[0163] The PUR configuration circuit 1742 may include the functionality of a unit for sending a PUR configuration request. For example, the PUR configuration circuit 1742 may be configured to perform... Figure 10 At position 1006 and / or at Figure 19 One or more of the operations described in box 1902. In some examples, PUR configuration circuitry 1742 may generate a request for a PUR and cooperate with communication and processing circuitry 1741 (e.g., instructing communication and processing circuitry 1741) to send the request to the gNB via specified signaling.

[0164] The PUR configuration circuit 1742 may include the function of a unit for receiving PUR configurations. For example, the PUR configuration circuit 1742 may be configured to perform... Figure 10 At position 1010 and / or at Figure 18 At box 1802 and / or at Figure 19 One or more of the receive-related operations described in block 1904. In some examples, the PUR configuration circuit 1742 may cooperate with (e.g., instruct) the communication and processing circuit 1741 to monitor a designated channel for a transmission made by the gNB. Furthermore, the PUR configuration circuit 1742 may process information received by the communication and processing circuit 1741 during such a transmission (e.g., to determine one or more configuration parameters).

[0165] According to some examples, processor 1704 may include verification circuitry 1743, which is configured to perform verification-related operations as discussed herein (e.g., in conjunction with...). Figure 5-16 (One or more of the operations described herein). Furthermore, in some examples, the verification circuit 1743 may be configured to execute the verification software 1753 included on the computer-readable medium 1706 to implement one or more of the functions described herein.

[0166] Verification circuit 1743 may include the functionality of units for performing verification processes. For example, verification circuit 1743 may be configured to perform... Figure 10 At position 1012 and / or at Figure 18 At box 1804 and / or at Figure 19 One or more of the operations described in box 1906. In some examples, the PUR configuration circuit 1742 can determine whether TA is valid and whether the timing of the first PUR timing indicates that the first PUR is valid.

[0167] The verification circuit 1743 may include the functionality of a unit for selectively transmitting uplink transmissions. For example, the verification circuit 1743 may be configured to perform... Figure 10 At position 1014 and / or at Figure 18 At frame 1806 and / or at Figure 19 One or more of the transmission-related operations described in box 1908. In some examples, verification circuitry 1743 may generate a small data transfer (SDT) and cooperate with communication and processing circuitry 1741 (e.g., instructing communication and processing circuitry 1741) to send the SDT to the gNB on resources allocated for the first PUR timing.

[0168] Figure 18This is a flowchart illustrating an example method 1800 for wireless communication according to some aspects of this disclosure. As described below, in certain implementations within the scope of this disclosure, some or all of the shown features may be omitted, and some shown features may not be necessary for all example implementations. In some examples, method 1800 may be performed by... Figure 17 The method is performed by UE 1700 shown below. In some examples, method 1800 may be performed by any suitable means or unit for performing the functions or algorithms described below.

[0169] At block 1802, the user equipment can receive a pre-configured uplink resource (PUR) configuration, which includes PUR authentication information and timing advance (TA) authentication information for multiple PUR events, wherein the PUR authentication message and TA authentication information depend on at least one capability of the user equipment. For example, PUR configuration circuitry 1742, together with communication and processing circuitry 1741 and transceiver 1710, can provide elements for receiving a pre-configured uplink resource (PUR) configuration, which includes PUR authentication information and timing advance (TA) authentication information for multiple PUR events.

[0170] At block 1804, the UE can perform a verification process for the first PUR timing among multiple PUR timings based on PUR verification information and TA verification information. For example, verification circuit 1743 can provide a unit for performing a verification process for the first PUR timing among multiple PUR timings based on PUR verification information and TA verification information.

[0171] At box 1806, the UE can selectively transmit uplink transmissions during the first PUR timing based on the authentication process. For example, in conjunction with the above... Figure 17 The verification circuit 1743 shown and described, together with the communication and processing circuit 1741 and the transceiver 1710, can provide a unit for selectively transmitting uplink transmissions during the first PUR timing according to the verification process.

[0172] In some examples, the user equipment may send a PUR configuration request to the base station, wherein the PUR configuration is received from the base station after the PUR configuration request is sent (e.g., at box 1802). In some examples, the PUR configuration request indicates at least one capability of the user equipment, the PUR configuration including an uplink bandwidth portion configuration associated with at least one of PUR authentication for multiple PUR times, TA authentication for multiple PUR times, transmissions on multiple PUR times, or a combination thereof, and the PUR configuration including a downlink bandwidth portion configuration associated with at least one of PUR authentication for multiple PUR times, TA authentication for multiple PUR times, transmissions on multiple PUR times, or a combination thereof.

[0173] In some examples, multiple PUR timings are configured on the uplink bandwidth portion indicated by the PUR configuration, and selectively sending uplink transmissions during a first PUR timing according to the verification process may include selectively sending uplink transmissions based on at least one transmission parameter associated with at least one valid PUR timing among the multiple PUR timings.

[0174] In some examples, PUR authentication information may include at least one of the following: resource allocation associated with multiple PUR times, transmission parameters associated with multiple PUR times, uplink bandwidth portions configured for PUR authentication for multiple PUR times, downlink bandwidth portions configured for PUR authentication for multiple PUR times, or a combination thereof.

[0175] In some examples, receiving a PUR configuration may include receiving the PUR configuration via a Radio Resource Control (RRC) message or a Media Access Control-Control Element (MAC-CE).

[0176] In some examples, selectively transmitting uplink transmissions during a first PUR timing according to the verification process may include: determining that the first PUR timing is valid according to a PUR timing verification process of the verification process; determining that the TA is valid based on whether an uplink carrier configured to have multiple PUR timings is synchronized with the serving cell of the user equipment according to a TA verification process of the verification process; and transmitting uplink transmissions during the first PUR timing after determining that the first PUR timing is valid and the TA is valid. In some examples, the PUR configuration indicates an uplink bandwidth portion for multiple PUR timings, wherein the first PUR timing is in the uplink bandwidth portion, the PUR configuration indicates a downlink bandwidth portion for measurements associated with TA verification of multiple PUR timings, and determining that the TA is valid is further based on whether the user equipment performed measurements for the TA verification process on the downlink bandwidth portion prior to the first PUR timing in the uplink bandwidth portion.

[0177] In some examples, selectively transmitting uplink transmissions during a first PUR timing according to the authentication process may include: determining, according to the authentication process, that the first PUR timing is invalid; and, after determining that the first PUR timing is invalid, abandoning the transmission of uplink transmissions during the first PUR timing. In some examples, the user equipment may, after determining that the first PUR timing is invalid, determine whether a second PUR timing among a plurality of PUR timings is valid. In some examples, the user equipment may, after determining that the first PUR timing is invalid, abandon transmitting uplink transmissions during at least one subsequent PUR timing among a plurality of PUR timings. In some examples, abandoning the transmission of uplink transmissions during at least one second PUR timing may include suspending transmissions on the plurality of PUR timings for a period of time. In some examples, PUR authentication information may include an indication of that period of time. In some examples, abandoning the transmission of uplink transmissions during at least one second PUR timing may include suspending transmissions for a specified number of PUR timings among a plurality of PUR timings. In some examples, PUR authentication information may include an indication of that specified number. In some examples, the user equipment may, after determining that the first PUR timing is invalid, abandon transmitting uplink transmissions during any of the plurality of PUR timings.

[0178] In some examples, the verification process may include: determining that TA verification for a first PUR timing has failed; and abandoning verification of the first PUR timing after determining that TA verification for the first PUR timing has failed. In some examples, the user equipment may, after determining that TA verification for the first PUR timing has failed, determine whether a second PUR timing among a plurality of PUR timings is valid. In some examples, the user equipment may, after determining that TA verification for the first PUR timing has failed, abandon transmitting uplink transmissions during at least one second PUR timing among a plurality of PUR timings. In some examples, abandoning transmitting uplink transmissions during at least one second PUR timing may include pausing transmissions on the plurality of PUR timings for a period of time. In some examples, abandoning transmitting uplink transmissions during at least one second PUR timing may include pausing transmissions for a specified number of PUR timings among the plurality of PUR timings. In some examples, the user equipment may, after determining that TA verification for the first PUR timing has failed, abandon transmitting uplink transmissions during any PUR timing among a plurality of PUR timings.

[0179] In some examples, the verification process may include: determining that the TA verification for the first PUR timing has passed; and verifying the first PUR timing after determining that the TA verification for the first PUR timing has passed. In some examples, the verification process may include: determining that the PUR verification for the first PUR timing has failed; and abandoning the execution of the TA verification for the first PUR timing after determining that the PUR verification for the first PUR timing has failed. In some examples, the verification process may include: determining that the PUR verification for the first PUR timing has passed; and performing the TA verification for the first PUR timing after determining that the PUR verification for the first PUR timing has passed.

[0180] In some examples, PUR verification information and TA verification information may include the start time of at least one of the following: the timing of the first PUR verification, the TA for the first PUR timing, or a combination thereof (e.g., Figure 11 The second time (1104) and the timer duration (e.g., Figure 11 Time period T PUR In some examples, PUR verification information and TA verification information may include the end time of at least one of the following: the verification of the first PUR timing, the TA for the first PUR timing, or a combination thereof (e.g., Figure 11 The third time (1106) and the timer duration (e.g., Figure 11 Time period T PUR In some examples, PUR verification information may include the start time of at least one of the following: the timing of the first PUR verification, the TA for the first PUR timing, or a combination thereof (e.g., Figure 11 The second time (1104) and the end time (e.g., Figure 11 (First time 1106). In some examples, the PUR authentication information is defined for all user equipment under the cell of the base station.

[0181] In some examples, the user equipment's (UE) verification process may include: determining that a handover gap between a first uplink transmission and a first downlink transmission is defined for the UE (e.g., the UL / DL handover gap discussed above); and after determining that a handover gap between the first uplink transmission and the first downlink transmission is defined for the UE, determining whether the time gap between the first PUR timing and the last downlink symbol prior to the first PUR timing is greater than or equal to a threshold; and determining whether the UE has performed measurements for TA verification prior to the last downlink symbol. In some examples, this threshold depends on at least one of the duplex mode, the subcarrier spacing for the first PUR timing, the UE's capabilities, or a combination thereof. In some examples, the threshold is a normalized value, or the UE receives the threshold from the base station. In some examples, determining whether a handover gap between the first uplink transmission and the first downlink transmission is defined for the UE may include: determining whether the UE is operating in time division duplex (TDD) mode, full-duplex-frequency division duplex (FD-FDD) mode, or half-duplex-frequency division duplex (HD-FDD) mode.

[0182] In some examples, the user equipment performing the verification process may include determining whether the uplink symbol used for the first PUR timing is aligned with the time slot format used for Time Division Duplex (TDD) operating mode. In some examples, performing the verification process may include determining whether the uplink symbol used for the first PUR timing is aligned with the uplink resource configuration used for Half-Duplex-Frequency Division Duplex (HD-FDD) operating mode. In some examples, performing the verification process may include verifying that the uplink symbol used for the first PUR timing does not share a time slot with the first uplink transmission performed by the user equipment.

[0183] In some examples, the user equipment's verification process may include: determining whether a transmission gap (e.g., a minimum gap defined between uplink transmissions) is defined for the user equipment between the first uplink transmission and the PUR transmission; and if a transmission gap is defined, determining whether the time gap between the first PUR timing and the last uplink symbol preceding the first PUR timing is greater than or equal to a threshold. In some examples, this threshold depends on at least one of the following: duplex mode, subcarrier spacing for the first PUR timing, user equipment capabilities, or combinations thereof. In some examples, the threshold is a normalized value, or the user equipment receives the threshold from the base station.

[0184] In some examples, determining whether a transmission gap between a first uplink transmission and a PUR transmission is defined for the user equipment may include determining whether the user equipment is operating in time division duplex (TDD) mode, full-duplex-frequency division duplex (FD-FDD) mode, or half-duplex-frequency division duplex (HD-FDD) mode.

[0185] Figure 19 This is a flowchart illustrating an example method 1900 for wireless communication according to some aspects of this disclosure. As described below, in certain implementations within the scope of this disclosure, some or all of the shown features may be omitted, and some shown features may not be necessary for all example implementations. In some examples, method 1900 may be performed by... Figure 17 The method is performed by UE 1700 shown below. In some examples, method 1900 may be performed by any suitable means or unit for performing the functions or algorithms described below.

[0186] At box 1902, the user equipment can send a pre-configured uplink resource (PUR) configuration request. For example, in conjunction with the above... Figure 17 The PUR configuration circuit 1742 shown and described, together with the communication and processing circuit 1741 and the transceiver 1710, can provide a unit for sending a pre-configured uplink resource (PUR) configuration request.

[0187] At block 1904, the user equipment can receive a PUR configuration after sending a PUR configuration request. This PUR configuration includes at least one of the following: PUR verification information for multiple PUR times, timing advance (TA) verification information for multiple PUR times, at least one parameter for multiple PUR times, or a combination thereof. For example, PUR configuration circuitry 1742, together with communication and processing circuitry 1741 and transceiver 1710, can provide a unit for receiving PUR configuration after sending a PUR configuration request.

[0188] In some examples, PUR authentication information and TA authentication information may include a start time and timer duration for verifying at least one of the following: a first PUR timing, a timing advance for the first PUR timing, or a combination thereof. In some examples, PUR authentication information and TA authentication information may include an end time and timer duration for verifying at least one of the following: a first PUR timing, a TA for the first PUR timing, or a combination thereof. In some examples, PUR authentication information may include a start time and end time for verifying at least one of the following: a first PUR timing, a TA for the first PUR timing, or a combination thereof. In some examples, at least one parameter may include at least one of the following: resource allocation associated with multiple PUR timings, transmission parameters associated with multiple PUR timings, or a combination thereof. In some examples, receiving PUR configuration may include receiving PUR configuration via Radio Resource Control (RRC) messages or Media Access Control-Control Element (MAC-CE).

[0189] In some examples, the PUR authentication information is defined for all user equipment (UEs) within the cell of the base station. In some examples, the PUR configuration request may indicate at least one capability of the UE, and the PUR authentication information and TA authentication information depend on at least one capability of the UE.

[0190] At block 1906, the UE can perform a verification process for the first PUR timing among multiple PUR timings based on the PUR verification information. For example, verification circuit 1743 can provide a unit for performing a verification process for the first PUR timing among multiple PUR timings based on the PUR verification information.

[0191] In some examples, the verification process may include: determining that TA verification for the first PUR timing failed; and abandoning the verification of the first PUR timing after determining that TA verification for the first PUR timing failed. In some examples, the verification process may include: determining that TA verification for the first PUR timing passed; and verifying the first PUR timing after determining that TA verification for the first PUR timing passed. In some examples, the verification process may include: determining that PUR verification for the first PUR timing failed; and abandoning the execution of TA verification for the first PUR timing after determining that PUR verification for the first PUR timing failed. In some examples, the verification process may include: determining that PUR verification for the first PUR timing passed; and performing TA verification for the first PUR timing after determining that PUR verification for the first PUR timing passed.

[0192] In some examples, performing the verification process may include: determining whether a handover gap between a first uplink transmission and a first downlink transmission is defined for the user equipment; and if a handover gap is defined, determining whether the time interval between the first PUR timing and the last downlink symbol prior to the first PUR timing is greater than or equal to a threshold. In some examples, this threshold depends on at least one of the following: duplex mode, subcarrier spacing for the first PUR timing, the capabilities of the user equipment, or a combination thereof. In some examples, the threshold is a normalized value, or the user equipment receives the threshold from the base station. In some examples, determining whether a handover gap between a first uplink transmission and a first downlink transmission is defined for the user equipment may include: determining whether the user equipment is operating in time division duplex (TDD) mode or half-duplex-frequency division duplex (HD-FDD) mode.

[0193] In some examples, performing the verification process may include determining whether the uplink symbol used for the first PUR timing is aligned with the time slot format used for Time Division Duplex (TDD) operating mode. In some examples, performing the verification process may include determining whether the uplink symbol used for the first PUR timing is aligned with the uplink resource configuration used for Half-Duplex-Frequency Division Duplex (HD-FDD) operating mode. In some examples, performing the verification process may include verifying that the uplink symbol used for the first PUR timing does not share a time slot with the first uplink transmission performed by the user equipment.

[0194] In some examples, performing the verification process may include: determining whether a transmission gap between the first uplink transmission and the PUR transmission is defined for the user equipment; and if a transmission gap is defined, determining whether the time gap between the first PUR timing and the last uplink symbol preceding the first PUR timing is greater than or equal to a threshold. In some examples, this threshold depends on at least one of the following: duplex mode, subcarrier spacing for the first PUR timing, the capabilities of the user equipment, or a combination thereof. In some examples, the threshold is a normalized value, or the user equipment receives the threshold from the base station. In some examples, determining whether a transmission gap between the first uplink transmission and the PUR transmission is defined for the user equipment may include determining whether the user equipment is operating in time division duplex (TDD) mode or half-duplex-frequency division duplex (HD-FDD) mode.

[0195] At box 1908, the UE can selectively transmit uplink transmissions during the first PUR timing based on the result of the authentication process. For example, in conjunction with the above... Figure 17 The verification circuit 1743 shown and described, together with the communication and processing circuit 1741 and the transceiver 1710, can provide a unit for selectively transmitting uplink transmissions during the first PUR timing based on the result of the verification process.

[0196] In some examples, selectively transmitting uplink transmissions during a first PUR timing according to the verification process may include selectively transmitting downlink transmissions based on at least one transmission parameter associated with at least one valid PUR timing among a plurality of PUR timings. In some examples, selectively transmitting uplink transmissions during a first PUR timing according to the verification process may include: determining that the first PUR timing is valid according to a PUR timing verification process; determining that the TA is valid based on whether an uplink carrier configured to have multiple PUR timings is synchronized with the serving cell of the user equipment according to a TA verification process; and transmitting uplink transmissions during the first PUR timing after determining that the first PUR timing is valid and the TA is valid. In some examples, selectively transmitting uplink transmissions during a first PUR timing according to the verification process may include: determining that the first PUR timing is not valid according to the verification process; and abandoning the transmission of uplink transmissions during the first PUR timing after determining that the first PUR timing is not valid.

[0197] In some examples, a method for wireless communication at a user equipment may include: sending a pre-configured uplink resource (PUR) configuration request; and receiving PUR configuration after sending the PUR configuration request. The PUR configuration may include at least one of the following: PUR verification information for multiple PUR times, timing advance (TA) verification information for multiple PUR times, at least one parameter for multiple PUR times, or a combination thereof. The method may further include: performing a verification process for a first PUR time among multiple PUR times based on the PUR verification information; and selectively transmitting uplink transmissions during the first PUR time based on the result of the verification process.

[0198] In some examples, a user equipment may include a transceiver, a memory, and a processor communicatively coupled to the transceiver and the memory. The processor may be configured to: transmit a pre-configured uplink resource (PUR) configuration request via the transceiver; and receive PUR configuration via the transceiver after transmitting the PUR configuration request. The PUR configuration may include at least one of the following: PUR authentication information for multiple PUR times, timing advance (TA) authentication information for multiple PUR times, at least one parameter for multiple PUR times, or a combination thereof. The processor may also be configured to: perform an authentication process for a first PUR time among multiple PUR times based on the PUR authentication information; and selectively transmit uplink transmissions during the first PUR time based on the result of the authentication process.

[0199] In some examples, a user equipment may include: a unit for sending a pre-configured uplink resource (PUR) configuration request; and a unit for receiving PUR configuration after sending the PUR configuration request. The PUR configuration may include at least one of the following: PUR verification information for multiple PUR times, timing advance (TA) verification information for multiple PUR times, at least one parameter for multiple PUR times, or a combination thereof. The user equipment may also include: a unit for performing a verification process for a first PUR time among multiple PUR times based on the PUR verification information; and a unit for selectively sending uplink transmissions during the first PUR time based on the result of the verification process.

[0200] In some examples, an article of art for use by a user equipment includes a computer-readable medium having instructions stored therein, executable by one or more processors of the user equipment, to: send a pre-configured uplink resource (PUR) configuration request; and receive PUR configuration after sending the PUR configuration request. The PUR configuration may include at least one of the following: PUR verification information for multiple PUR times, timing advance (TA) verification information for multiple PUR times, at least one parameter for multiple PUR times, or a combination thereof. The computer-readable medium may also have instructions stored therein, executable by one or more processors of the user equipment, to: perform a verification process for a first PUR time among multiple PUR times based on the PUR verification information; and selectively send uplink transmissions during the first PUR time based on the result of the verification process.

[0201] In one configuration, user equipment 1700 includes: a unit for receiving a pre-configured uplink resource (PUR) configuration, the PUR configuration including PUR authentication information and timing advance (TA) authentication information for multiple PUR times, wherein the PUR authentication information and TA authentication information depend on at least one capability of the user equipment; a unit for performing an authentication process for a first PUR time among the multiple PUR times based on the PUR authentication information and TA authentication information; and a unit for selectively transmitting uplink transmissions during the first PUR time according to the authentication process. In one aspect, the aforementioned unit may be in... Figure 17 The processor 1704 shown is configured to perform the functions described by the aforementioned unit (e.g., as discussed above). In another aspect, the aforementioned unit may be a circuit or any device configured to perform the functions described by the aforementioned unit.

[0202] Of course, in the above example, the circuitry included in processor 1704 is provided merely as an example, and other units for performing the described functions may be included within various aspects of this disclosure, including but not limited to instructions stored in computer-readable medium 1706, or in Figure 1 , 2 The figures described in any one or more of the figures 4, 6-10 and 17, and utilizing, for example, the text concerning... Figure 18 and 19 Any other suitable apparatus or unit for the described method and / or algorithm.

[0203] Figure 20 This is a conceptual diagram illustrating an example hardware implementation of a base station (BS) 2000 employing a processing system 2014. In some implementations, the BS 2000 may correspond to... Figure 1 , 2 And any of the BS (e.g., gNB) or scheduling entities shown in any of the diagrams in 6-10.

[0204] According to various aspects of this disclosure, an element, any part of an element, or any combination of elements can be implemented using the processing system 2014. The processing system may include one or more processors 2004. The processing system 2014 can be used with... Figure 17 The processing system 1714 shown is substantially the same, including a bus interface 2008, a bus 2002, a memory 2005, a processor 2004, and a computer-readable medium 2006. The memory 2005 may include PUR information 2015 (e.g., PUR configuration) that can be used by the processor 2004 for PUR-related operations as discussed herein. Furthermore, the BS 2000 may include an interface 2030 (e.g., a network interface) that provides a unit for communicating with at least one other device within the core network and with at least one radio access network.

[0205] BS 2000 can be configured to perform any one or more of the operations described herein (e.g., as combined above). Figure 1-16 As described, and in combination with the following text Figure 21 and 22 (As described). In some aspects of this disclosure, such as the processor 2004 utilized in BS 2000, circuitry may be configured for various functions.

[0206] Processor 2004 can be configured to generate, schedule, and modify resource assignments or permissions for time-frequency resources (e.g., a set of one or more resource elements). For example, processor 2004 can schedule time-frequency resources within multiple time-division duplex (TDD) and / or frequency-division duplex (FDD) subframes, time slots, and / or micro-time slots to carry user data services and / or control information to and / or from multiple UEs.

[0207] In some aspects of this disclosure, processor 2004 may include communication and processing circuitry 2041. Communication and processing circuitry 2041 may be configured to communicate with a UE. Communication and processing circuitry 2041 may include one or more hardware components providing a physical structure that performs various processes related to communication (e.g., signal reception and / or signal transmission) as described herein. Communication and processing circuitry 2041 may also include one or more hardware components providing a physical structure that performs various processes related to signal processing (e.g., processing received signals and / or processing signals for transmission) as described herein. Communication and processing circuitry 2041 may also be configured to execute communication and processing software 2051 included on computer-readable medium 2006 to implement one or more of the functions described herein.

[0208] The communication and processing circuitry 2041 can also be configured to receive messages from the UE. For example, the message may include: a MAC-CE carried in the PUSCH, a UCI in the PUCCH or PUSCH, a random access message, or an RRC message. The communication and processing circuitry 2041 can also be configured to receive from the UE a scheduling request for uplink permission for the PUSCH (e.g., via a UCI in the PUCCH).

[0209] In some implementations where communication involves receiving information, communication and processing circuitry 2041 may obtain information from components of BS 2000 (e.g., transceiver 2010 that receives information via radio frequency signaling or some other type of signaling suitable for an applicable communication medium), process (e.g., decode) the information, and output the processed information. For example, communication and processing circuitry 2041 may output information to another component of processor 2004, memory 2005, or bus interface 2008. In some examples, communication and processing circuitry 2041 may receive one or more of signals, messages, other information, or any combination thereof. In some examples, communication and processing circuitry 2041 may receive information via one or more channels. In some examples, communication and processing circuitry 2041 may include the functionality of a unit for receiving. In some examples, communication and processing circuitry 2041 may include the functionality of a unit for decoding.

[0210] In some implementations where communication involves sending (e.g., transmitting) information, communication and processing circuitry 2041 may obtain information (e.g., from another component of processor 2004, memory 2005, or bus interface 2008), process (e.g., encode) the information, and output the processed information. For example, communication and processing circuitry 2041 may output information to transceiver 2010 (e.g., which transmits information via radio frequency signaling or some other type of signaling suitable for an applicable communication medium). In some examples, communication and processing circuitry 2041 may send one or more of signals, messages, other information, or any combination thereof. In some examples, communication and processing circuitry 2041 may transmit information via one or more channels. In some examples, communication and processing circuitry 2041 may include the functionality of units for sending (e.g., units for transmitting). In some examples, communication and processing circuitry 2041 may include the functionality of units for encoding.

[0211] According to some examples, processor 2004 may include PUR configuration circuitry 2042, which is configured to perform PUR configuration-related operations as discussed herein (e.g., in conjunction with...). Figure 5-16 (One or more of the operations described herein). Furthermore, in some examples, the PUR configuration circuit 2042 may be configured to execute the PUR configuration software 2052 included on the computer-readable medium 2006 to implement one or more of the functions described herein.

[0212] The PUR configuration circuit 2042 may include the function of a unit for receiving an indication of at least one capability of the UE. For example, the PUR configuration circuit 2042 may be configured to perform... Figure 10 At position 1006 and / or at Figure 22 One or more of the receiving-related operations described at box 2202 include cooperating with communication and processing circuitry 2041 (e.g., instructing communication and processing circuitry 2041) to monitor capability message transmissions performed by the UE. Furthermore, PUR configuration circuitry 2042 can process information received by communication and processing circuitry 2041 during such transmissions (e.g., to determine one or more UE capability parameters).

[0213] The PUR configuration circuit 2042 may include the function of a unit for receiving a PUR configuration request. For example, the PUR configuration circuit 2042 may be configured to perform... Figure 10 At position 1006 and / or at Figure 22One or more of the operations described in box 2202. In some examples, the PUR configuration circuit 2042 may cooperate with the communication and processing circuit 2041 (e.g., instruct the communication and processing circuit 2041) to monitor transmissions made by idle and / or inactive UEs to receive requests for PUR. Furthermore, the PUR configuration circuit 2042 may process information received by the communication and processing circuit 2041 during such transmissions (e.g., to determine one or more request parameters).

[0214] The PUR configuration circuit 2042 may include the functionality of a unit for generating a PUR configuration. For example, the PUR configuration circuit 2042 may be configured to perform... Figure 10 At position 1008 and / or at Figure 22 One or more of the operations described in box 2204. In some examples, the PUR configuration circuit 2042 may allocate resources for the PUR to the UE and specify one or more parameters for the PUR.

[0215] The PUR configuration circuit 2042 may include the function of a unit for transmitting PUR configuration. For example, the PUR configuration circuit 2042 may be configured to perform... Figure 10 At position 1010 and / or at Figure 22 One or more of the operations described in box 2206. In some examples, PUR configuration circuit 2042 may encode PUR configuration and cooperate with communication and processing circuit 2041 (e.g., instructing communication and processing circuit 2041) to send PUR configuration to UE (e.g., a UE requesting PUR configuration).

[0216] According to some examples, processor 2004 may include PUR processing circuitry 2043, which is configured to perform PUR processing-related operations as discussed herein (e.g., in conjunction with...). Figure 5-16 (One or more of the operations described herein). Furthermore, in some examples, the PUR processing circuit 2043 may be configured to execute PUR processing software 2053 included on the computer-readable medium 2006 to implement one or more of the functions described herein.

[0217] The PUR processing circuit 2043 may include the function of a unit for receiving uplink transmissions during at least one PUR event. For example, the PUR processing circuit 2043 may be configured to perform... Figure 10 At step 1014 and / or in Figure 22One or more of the operations described in box 2208. In some examples, PUR processing circuitry 2043 may cooperate with communication and processing circuitry 2041 (e.g., instructing communication and processing circuitry 2041) to monitor resources allocated for the first PUR timing to receive small data transmission (SDT) from the UE. Furthermore, PUR processing circuitry 2043 may process information received by communication and processing circuitry 2041 during such transmission (e.g., to provide SDT to a target application).

[0218] Figure 21 This is a flowchart illustrating an example method 2100 for wireless communication according to some aspects of this disclosure. As described below, in certain implementations within the scope of this disclosure, some or all of the shown features may be omitted, and some shown features may not be necessary for all example implementations. In some examples, method 2100 may be provided by... Figure 20 The method is executed by the BS 2000 shown below. In some examples, method 2100 may be executed by any suitable means or unit for performing the functions or algorithms described below.

[0219] At box 2102, the base station can receive an indication of at least one capability of the user equipment. For example, in conjunction with the above... Figure 20 The PUR configuration circuit 2042 shown and described, together with the communication and processing circuit 2041 and the transceiver 2010, can provide a unit for receiving an indication of at least one capability of a user equipment.

[0220] At box 2104, the base station can generate a pre-configured uplink resource (PUR) configuration, which includes PUR verification information and timing advance (TA) verification information for multiple PUR timings, wherein the PUR verification message and TA verification information depend on at least one capability of the user equipment. For example, in conjunction with the above... Figure 20 The PUR configuration circuit 2042 shown and described can provide a unit for generating a pre-configured uplink resource (PUR) configuration, which includes PUR verification information and timing advance (TA) verification information for multiple PUR timings.

[0221] At box 2106, the BS can send PUR configuration to the user equipment. For example, in conjunction with the above... Figure 20 The PUR configuration circuitry 2042 shown and described, together with the communication and processing circuitry 2041 and the transceiver 2010, can provide a unit for transmitting PUR configuration to a user equipment. In some examples, transmitting PUR configuration may include transmitting the PUR via a Radio Resource Control (RRC) message or a Media Access Control-Control Element (MAC-CE).

[0222] At box 2108, the BS can receive uplink transmissions from the user equipment during at least one of a plurality of PUR times. For example, in conjunction with the above... Figure 20 The PUR processing circuit 2043 shown and described, together with the communication and processing circuit 2041 and the transceiver 2010, can provide a unit for receiving uplink transmissions from a user equipment during at least one of a plurality of PUR times.

[0223] In some examples, PUR verification information may include at least one of the following: resource allocations associated with multiple PUR times, transmission parameters associated with multiple PUR times, or a combination thereof.

[0224] In some examples, sending the PUR configuration may include sending the PUR configuration via Radio Resource Control (RRC) messages or Media Access Control-Control Element (MAC-CE).

[0225] In some examples, PUR verification information may include a start time and timer duration for verifying at least one of the following: multiple PUR events, TAs for multiple PUR events, or a combination thereof. In some examples, at least one user equipment capability indicates the user equipment uplink-to-downlink handover time, and generating the PUR configuration may include defining the start time based on the user equipment uplink-to-downlink handover time. In some examples, at least one user equipment capability indicates user equipment processing capacity, and generating the PUR configuration may include defining the timer duration based on the user equipment processing capacity.

[0226] In some examples, PUR verification information may include an end time and timer duration for verifying at least one of the following: multiple PUR events, TAs for multiple PUR events, or a combination thereof. In some examples, at least one UE capability indicates the UE downlink-to-uplink handover time, and generating the PUR configuration may include defining an end time based on the UE downlink-to-uplink handover time.

[0227] In some examples, PUR verification information may include start and end times for verifying at least one of the following: multiple PUR timings, TAs for multiple PUR timings, or combinations thereof. In some examples, PUR verification information is defined for all user equipment under the cell of the base station.

[0228] In some examples, generating a PUR configuration may include defining PUR authentication information and TA authentication information based on at least one capability of the user equipment. In some examples, generating a PUR configuration may include defining a threshold for the time interval between a first PUR timing and the last downlink symbol preceding the first PUR timing. In some examples, defining the threshold may include defining the threshold based on at least one of the following: duplex mode, subcarrier spacing for the first PUR timing, at least one capability of the user equipment, or a combination thereof. In some examples, the PUR configuration may include an indication of the threshold.

[0229] In some examples, generating a PUR configuration may include defining a threshold for the time gap between the first PUR timing and the last uplink symbol preceding the first PUR timing. In some examples, defining the threshold may include defining the threshold based on at least one of the following: duplex mode, subcarrier spacing for the first PUR timing, user equipment capabilities, or a combination thereof. In some examples, the PUR configuration may include an indication of the threshold.

[0230] In some examples, the base station may receive a PUR configuration request from the user equipment, wherein the PUR configuration is sent to the user equipment in response to the PUR configuration request. In some examples, the PUR configuration request and an indication of at least one capability of the user equipment may be received in the same message. In some examples, the PUR configuration request and an indication of at least one capability of the user equipment may be received in different messages.

[0231] In some examples, the PUR verification information may include an indication of the time period for suspending transmissions on multiple PUR times in response to a PUR verification failure or a TA verification failure. In some examples, the PUR verification information may include an indication of a specified number of PUR times that will be suspended in response to a PUR verification failure or a TA verification failure.

[0232] Figure 22 This is a flowchart illustrating an example method 2200 for wireless communication according to some aspects of this disclosure. As described below, in certain implementations within the scope of this disclosure, some or all of the shown features may be omitted, and some shown features may not be necessary for all example implementations. In some examples, method 2200 may be provided by... Figure 20 The method is executed by the BS 2000 shown below. In some examples, method 2200 may be executed by any suitable means or unit for performing the functions or algorithms described below.

[0233] At box 2202, the base station can receive a pre-configured uplink resource (PUR) configuration request. For example, in conjunction with the above... Figure 20 The PUR configuration circuit 2042 shown and described, together with the communication and processing circuit 2041 and the transceiver 2010, can provide a unit for receiving pre-configured uplink resource (PUR) configuration requests.

[0234] At block 2204, the base station may generate a PUR configuration after receiving a PUR configuration request. This PUR configuration includes at least one of the following: PUR verification information for multiple PUR times, timing advance (TA) verification information for multiple PUR times, at least one parameter for multiple PUR times, or a combination thereof. For example, PUR configuration circuitry 2042 may provide a unit for generating a PUR configuration after receiving a PUR configuration request.

[0235] In some examples, PUR verification information may include a start time and timer duration for verifying at least one of the following: multiple PUR times, TAs for multiple PUR times, or a combination thereof. In some examples, a PUR configuration request may include user equipment capability information indicating the uplink-to-downlink handover time of the user equipment. In some examples, generating a PUR configuration may include defining a start time based on the uplink-to-downlink handover time of the user equipment. In some examples, a PUR configuration request may indicate user equipment processing capacity. In some examples, generating a PUR configuration may include defining a timer duration based on user equipment processing capacity. In some examples, at least one parameter may include at least one of the following: resource allocation associated with multiple PUR times, transport parameters associated with multiple PUR times, or a combination thereof.

[0236] In some examples, PUR verification information may include an end time and timer duration for verifying at least one of the following: multiple PUR events, TAs for multiple PUR events, or a combination thereof. In some examples, a PUR configuration request may include UE capability information indicating the UE's downlink-to-uplink handover time. In some examples, generating a PUR configuration may include defining an end time based on the UE's downlink-to-uplink handover time.

[0237] In some examples, PUR verification information may include start and end times for verifying at least one of the following: multiple PUR timings, TAs for multiple PUR timings, or a combination thereof.

[0238] In some examples, the PUR authentication information is defined for all user equipment (UEs) within the cell of the base station. In some examples, the PUR configuration request may indicate at least one capability of the UE; and generating PUR configuration and TA authentication information may include defining the PUR authentication information based on at least one capability of the UE.

[0239] In some examples, generating a PUR configuration may include defining a threshold for the time interval between the first PUR timing and the last downlink symbol preceding the first PUR timing. In some examples, defining the threshold may include defining the threshold based on at least one of the following: duplex mode, subcarrier spacing for the first PUR timing, user equipment capabilities, or a combination thereof. In some examples, the PUR configuration may include an indication of the threshold.

[0240] In some examples, generating a PUR configuration may include defining a threshold for the time gap between the first PUR timing and the last uplink symbol preceding the first PUR timing. In some examples, defining the threshold may include defining the threshold based on at least one of the following: duplex mode, subcarrier spacing for the first PUR timing, user equipment capabilities, or a combination thereof. In some examples, the PUR configuration may include an indication of the threshold.

[0241] At box 2206, the BS can transmit PUR configuration (e.g., via an RRC message). In some examples, transmitting PUR configuration may include transmitting PUR configuration via a Radio Resource Control (RRC) message or a Media Access Control-Control Element (MAC-CE). For example, PUR configuration circuitry 2042, together with communication and processing circuitry 2041 and transceiver 2010, can provide a unit for transmitting PUR configuration.

[0242] At box 2208, the BS can receive uplink transmissions (e.g., including small data transmissions) during at least one of a plurality of PUR times. For example, in conjunction with the above... Figure 20 The PUR processing circuit 2043 shown and described, together with the communication and processing circuit 2041 and the transceiver 2010, can provide a unit for receiving uplink transmissions during at least one of a plurality of PUR times.

[0243] In some examples, a method for wireless communication at a base station may include: receiving a pre-configured uplink resource (PUR) configuration request; and generating a PUR configuration after receiving the PUR configuration request. The PUR configuration may include at least one of the following: PUR verification information for multiple PUR times, timing advance (TA) verification information for multiple PUR times, at least one parameter for multiple PUR times, or a combination thereof. The method may also include: transmitting the PUR configuration; and receiving uplink transmissions during at least one of the multiple PUR times.

[0244] In some examples, a base station may include a transceiver, a memory, and a processor communicatively coupled to the transceiver and the memory. The processor may be configured to: receive a pre-configured uplink resource (PUR) configuration request via the transceiver; and generate a PUR configuration upon receiving the PUR configuration request. The PUR configuration may include at least one of the following: PUR authentication information for multiple PUR times, timing advance (TA) authentication information for multiple PUR times, at least one parameter for multiple PUR times, or a combination thereof. The processor may also be configured to: transmit the PUR configuration via the transceiver; and receive uplink transmissions via the transceiver during at least one of the multiple PUR times.

[0245] In some examples, a base station may include: a unit for receiving a pre-configured uplink resource (PUR) configuration request; and a unit for generating a PUR configuration after receiving the PUR configuration request. The PUR configuration may include at least one of the following: PUR verification information for multiple PUR times, timing advance (TA) verification information for multiple PUR times, at least one parameter for multiple PUR times, or a combination thereof. The base station may also include: a unit for transmitting the PUR configuration; and a unit for receiving uplink transmissions during at least one of the multiple PUR times.

[0246] In some examples, an article of art for use by a base station includes a computer-readable medium having instructions stored therein, executable by one or more processors of the base station, to: receive a pre-configured uplink resource (PUR) configuration request; and generate a PUR configuration after receiving the PUR configuration request. The PUR configuration may include at least one of the following: PUR verification information for multiple PUR times, timing advance (TA) verification information for multiple PUR times, at least one parameter for multiple PUR times, or a combination thereof. The computer-readable medium may also have instructions stored therein, executable by one or more processors of the base station, to: transmit the PUR configuration; and receive uplink transmissions during at least one of the multiple PUR times.

[0247] In one configuration, base station 2000 includes: a unit for receiving an indication of at least one capability of a user equipment; a unit for generating a pre-configured uplink resource (PUR) configuration, the PUR configuration including PUR verification information and timing advance (TA) verification information for multiple PUR times, wherein the PUR verification information and TA verification information depend on at least one capability of the user equipment; a unit for sending the PUR configuration to the user equipment; and a unit for receiving uplink transmissions from the user equipment during at least one of the multiple PUR times. In one aspect, the aforementioned unit may be in Figure 20 The processor 2004 shown is configured to perform the functions described by the aforementioned unit (e.g., as discussed above). In another aspect, the aforementioned unit may be a circuit or any device configured to perform the functions described by the aforementioned unit.

[0248] Of course, in the above example, the circuitry included in processor 2004 is provided merely as an example, and other units for performing the described functions may be included within various aspects of this disclosure, including but not limited to instructions stored in computer-readable medium 1206, or in Figure 1 , 2 The figures described in any one or more of 4, 6-10 and 20, and utilizing, for example, the text concerning... Figure 21 and 22 Any other suitable apparatus or unit for the described method and / or algorithm.

[0249] exist Figure 18-19 The methods shown in 21-22 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere in this document. An overview of several aspects of this disclosure is provided below.

[0250] Aspect 1: A user equipment, comprising: a transceiver; a memory; and a processor coupled to the transceiver and the memory, wherein the processor is configured to: receive, via the transceiver, a pre-configured uplink resource (PUR) configuration, the PUR configuration including PUR authentication information and timing advance (TA) authentication information for a plurality of PUR times, wherein the PUR authentication information and the TA authentication information depend on at least one capability of the user equipment; perform an authentication process for a first PUR time among the plurality of PUR times based on the PUR authentication information and the TA authentication information; and selectively transmit uplink transmissions via the transceiver during the first PUR time based on the authentication process.

[0251] Aspect 2: The user equipment according to aspect 1, wherein the processor is further configured to: send a PUR configuration request to a base station; and receive the PUR configuration from the base station after sending the PUR configuration request.

[0252] Aspect 3: The user equipment according to Aspect 2, wherein: the PUR configuration request indicates the at least one capability of the user equipment; the PUR configuration includes an uplink bandwidth portion configuration associated with at least one of the following: a first PUR authentication for the plurality of PUR times, a first TA authentication for the plurality of PUR times, a first transmission on the plurality of PUR times, or a combination thereof; and the PUR configuration includes a downlink bandwidth portion configuration associated with at least one of the following: a second PUR authentication for the plurality of PUR times, a second TA authentication for the plurality of PUR times, a second transmission on the plurality of PUR times, or a combination thereof.

[0253] Aspect 4: The user equipment according to any one of aspects 1 to 3, wherein: the plurality of PUR timings are configured on an uplink bandwidth portion indicated by the PUR configuration; and the processor is further configured to: selectively transmit the uplink transmission according to at least one transmission parameter associated with at least one valid PUR timing among the plurality of PUR timings.

[0254] Aspect 5: The user equipment according to any one of aspects 1 to 4, wherein the PUR authentication information includes at least one of the following: resource allocation associated with the plurality of PUR times, transmission parameters associated with the plurality of PUR times, an uplink bandwidth portion configured for PUR authentication for the plurality of PUR times, a downlink bandwidth portion configured for PUR authentication for the plurality of PUR times, or a combination thereof.

[0255] Aspect 6: The user equipment according to any one of aspects 1 to 5, wherein the processor is further configured to receive the PUR configuration via a Radio Resource Control (RRC) message or a Media Access Control-Control Element (MAC-CE).

[0256] Aspect 7: The user equipment according to any one of aspects 1 to 6, wherein the processor is further configured to: determine that the first PUR timing is valid according to the PUR timing verification process of the verification process; determine that the TA is valid based on whether the uplink carrier configured to have the plurality of PUR timings is synchronized with the serving cell of the user equipment according to the TA verification process of the verification process; and after determining that the first PUR timing is valid and the TA is valid, transmit the uplink transmission during the first PUR timing.

[0257] Aspect 8: The user equipment according to Aspect 7, wherein: the PUR configuration indicates an uplink bandwidth portion for the plurality of PUR timings, wherein the first PUR timing is in the uplink bandwidth portion; the PUR configuration indicates a downlink bandwidth portion for measurements associated with TA verification of the plurality of PUR timings; and the processor is further configured to determine that the TA is valid based on whether the user equipment performed measurements for the TA verification process on the downlink bandwidth portion prior to the first PUR timing in the uplink bandwidth portion.

[0258] Aspect 9: The user equipment according to any one of aspects 1 to 6, wherein the processor is further configured to: determine, according to the verification process, that the first PUR timing is not valid; and, after determining that the first PUR timing is not valid, abandon sending the uplink transmission during the first PUR timing.

[0259] Aspect 10: The user equipment according to aspect 9, wherein the processor is further configured to: after determining that the first PUR timing is not valid, determine whether a second PUR timing among the plurality of PUR timings is valid.

[0260] Aspect 11: The user equipment according to aspect 9, wherein the processor is further configured to: abandon transmitting the uplink transmission during at least one subsequent PUR opportunity among the plurality of PUR opportunities after determining that the first PUR opportunity is not valid.

[0261] Aspect 12: The user equipment according to aspect 11, wherein the processor is further configured to: pause transmissions on the plurality of PUR times for a period of time.

[0262] Aspect 13: The user equipment according to aspect 12, wherein the PUR verification information includes an indication of the time period.

[0263] Aspect 14: The user equipment according to aspect 11, wherein the processor is further configured to: suspend transmission for a specified number of PUR times among the plurality of PUR times.

[0264] Aspect 15: The user equipment according to aspect 14, wherein the PUR verification information includes an indication of the specified number.

[0265] Aspect 16: The user equipment according to aspect 9, wherein the processor is further configured to: abandon transmitting the uplink transmission during any of the plurality of PUR opportunities after determining that the first PUR opportunity is not valid.

[0266] Aspect 17: The user equipment according to any one of aspects 1 to 16, wherein the processor is further configured to: determine that the TA verification for the first PUR timing has failed; and after determining that the TA verification for the first PUR timing has failed, abandon the verification of the first PUR timing.

[0267] Aspect 18: The user equipment according to aspect 17, wherein the processor is further configured to: determine whether a second PUR timing among the plurality of PUR timings is valid after determining that the TA verification for the first PUR timing has failed.

[0268] Aspect 19: The user equipment according to aspect 17, wherein the processor is further configured to: abandon sending the uplink transmission during at least one second PUR time period among the plurality of PUR time periods after determining that the TA verification for the first PUR time period has failed.

[0269] Aspect 20: The user equipment according to aspect 19, wherein the processor is further configured to: pause transmission on the plurality of PUR times for a period of time.

[0270] Aspect 21: The user equipment according to aspect 19, wherein the processor is further configured to: suspend transmission for a specified number of PUR times among the plurality of PUR times.

[0271] Aspect 22: The user equipment according to aspect 17, wherein the processor is further configured to: abandon sending the uplink transmission during any of the plurality of PUR times after determining that the TA verification for the first PUR time has failed.

[0272] Aspect 23: The user equipment according to any one of aspects 1 to 22, wherein the processor is further configured to: determine that the TA verification for the first PUR timing has passed; and after determining that the TA verification for the first PUR timing has passed, verify the first PUR timing.

[0273] Aspect 24: The user equipment according to any one of aspects 1 to 23, wherein the processor is further configured to: determine that the PUR verification for the first PUR timing has failed; and after determining that the PUR verification for the first PUR timing has failed, abandon the execution of TA verification for the first PUR timing.

[0274] Aspect 25: The user equipment according to any one of aspects 1 to 23, wherein the processor is further configured to: determine that the PUR verification for the first PUR timing has passed; and after determining that the PUR verification for the first PUR timing has passed, perform TA verification for the first PUR timing.

[0275] Aspect 26: The user equipment according to any one of aspects 1 to 25, wherein the PUR verification information and the TA verification information include a start time and a timer duration for verifying at least one of the following: the first PUR timing, the TA for the first PUR timing, or a combination thereof.

[0276] Aspect 27: The user equipment according to any one of aspects 1 to 25, wherein the PUR verification information and the TA verification information include an end time and a timer duration for verifying at least one of the following: the first PUR timing, the TA for the first PUR timing, or a combination thereof.

[0277] Aspect 28: The user equipment according to any one of aspects 1 to 25, wherein the PUR verification information includes a start time and an end time for verifying at least one of the following: the first PUR timing, the TA for the first PUR timing, or a combination thereof.

[0278] Aspect 29: User equipment according to any one of aspects 1 to 28, wherein the PUR authentication information is defined for all user equipment under the cell of the base station.

[0279] Aspect 30: A user equipment according to any one of aspects 1 to 29, wherein the processor is further configured to: determine that a handover gap between a first uplink transmission and a first downlink transmission is defined for the user equipment; and after determining that the handover gap between the first uplink transmission and the first downlink transmission is defined for the user equipment, determine whether the time gap between the first PUR timing and the last downlink symbol before the first PUR timing is greater than or equal to a threshold, and determine whether the user equipment has performed a measurement for TA verification before the last downlink symbol.

[0280] Aspect 31: The user equipment according to aspect 30, wherein the threshold depends on at least one of the following: duplex mode, subcarrier spacing for the first PUR timing, the capability of the user equipment, or a combination thereof.

[0281] Aspect 32: The user equipment according to aspect 30, wherein the threshold is a standardized value, or the user equipment receives the threshold from a base station.

[0282] Aspect 33: The user equipment according to any one of aspects 30 to 32, wherein the processor is further configured to: determine whether the user equipment is operating in time division duplex (TDD) mode, full duplex-frequency division duplex (FD-FDD) mode or half duplex-frequency division duplex (HD-FDD) mode.

[0283] Aspect 34: The user equipment according to any one of aspects 1 to 33, wherein the processor is further configured to: determine whether the uplink symbol for the first PUR timing is aligned with the slot format for the time division duplex (TDD) operation mode.

[0284] Aspect 35: The user equipment according to any one of aspects 1 to 33, wherein the processor is further configured to: determine whether the uplink symbol for the first PUR timing is aligned with the uplink resource configuration for the half-duplex-frequency division duplex (HD-FDD) operation mode.

[0285] Aspect 36: The user equipment according to any one of aspects 1 to 33, wherein the processor is further configured to: verify that the uplink symbol for the first PUR timing does not share a time slot with the first uplink transmission performed by the user equipment.

[0286] Aspect 37: The user equipment according to any one of aspects 1 to 36, wherein the processor is further configured to: determine whether a transmission gap between a first uplink transmission and a PUR transmission is defined for the user equipment; and if the transmission gap is defined, determine whether the time gap between the first PUR timing and the last uplink symbol prior to the first PUR timing is greater than or equal to a threshold.

[0287] Aspect 38: The user equipment according to aspect 37, wherein the threshold depends on at least one of the following: duplex mode, subcarrier spacing for the first PUR timing, the at least one capability of the user equipment, or a combination thereof.

[0288] Aspect 39: The user equipment according to aspect 37, wherein the threshold is a standardized value, or the user equipment receives the threshold from a base station.

[0289] Aspect 40: The user equipment according to aspect 37, wherein the processor is further configured to: determine whether the user equipment is operating in time division duplex (TDD) mode, full duplex-frequency division duplex (FD-FDD) mode or half duplex-frequency division duplex (HD-FDD) mode.

[0290] Aspect 41: A method for wireless communication at a user equipment, the method comprising: receiving a pre-configured uplink resource (PUR) configuration, the PUR configuration including PUR verification information and timing advance (TA) verification information for a plurality of PUR times, wherein the PUR verification information and the TA verification information depend on at least one capability of the user equipment; performing a verification process for a first PUR time among the plurality of PUR times based on the PUR verification information and the TA verification information; and selectively transmitting uplink transmissions during the first PUR time based on the verification process.

[0291] Aspect 42: The method according to aspect 41 further includes: sending a PUR configuration request to a base station, wherein the PUR configuration is received from the base station after the PUR configuration request is sent.

[0292] Aspect 43: The method according to aspect 42, wherein: the PUR configuration request indicates the at least one capability of the user equipment; the PUR configuration includes an uplink bandwidth portion configuration associated with at least one of the following: a first PUR authentication for the plurality of PUR times, a first TA authentication for the plurality of PUR times, a first transmission on the plurality of PUR times, or a combination thereof; and the PUR configuration includes a downlink bandwidth portion configuration associated with at least one of the following: a second PUR authentication for the plurality of PUR times, a second TA authentication for the plurality of PUR times, a second transmission on the plurality of PUR times, or a combination thereof.

[0293] Aspect 44: The method according to any one of aspects 41 to 43, wherein: the plurality of PUR timings are configured on an uplink bandwidth portion indicated by the PUR configuration; and the selective transmission of the uplink transmission during the first PUR timing according to the verification process comprises: selectively transmitting the uplink transmission according to at least one transmission parameter associated with at least one valid PUR timing among the plurality of PUR timings.

[0294] Aspect 45: The method according to any one of aspects 41 to 44, wherein the PUR verification information includes at least one of the following: resource allocation associated with the plurality of PUR times, transmission parameters associated with the plurality of PUR times, an uplink bandwidth portion configured for PUR verification for the plurality of PUR times, a downlink bandwidth portion configured for PUR verification for the plurality of PUR times, or a combination thereof.

[0295] Aspect 46: The method according to any one of aspects 41 to 45, wherein receiving the PUR configuration includes receiving the PUR configuration via a Radio Resource Control (RRC) message or a Media Access Control-Control Element (MAC-CE).

[0296] Aspect 47: The method according to any one of aspects 41 to 46, wherein selectively transmitting the uplink transmission during the first PUR timing according to the verification process comprises: determining that the first PUR timing is valid according to a PUR timing verification process of the verification process; determining that a TA is valid based on whether an uplink carrier configured to have the plurality of PUR timings is synchronized with the serving cell of the user equipment according to a TA verification process of the verification process; and transmitting the uplink transmission during the first PUR timing after determining that the first PUR timing is valid and the TA is valid.

[0297] Aspect 48: The method according to aspect 47, wherein: the PUR configuration indicates an uplink bandwidth portion for the plurality of PUR timings, wherein the first PUR timing is in the uplink bandwidth portion; the PUR configuration indicates a downlink bandwidth portion for measurements associated with TA verification of the plurality of PUR timings; and the determination that the TA is valid is further based on whether the user equipment performed measurements for the TA verification process on the downlink bandwidth portion prior to the first PUR timing in the uplink bandwidth portion.

[0298] Aspect 49: The method according to any one of aspects 41 to 46, wherein selectively transmitting the uplink transmission during the first PUR timing according to the verification process comprises: determining, according to the verification process, that the first PUR timing is not valid; and, after determining that the first PUR timing is not valid, abandoning the transmission of the uplink transmission during the first PUR timing.

[0299] Aspect 50: The method according to aspect 49 further includes: after determining that the first PUR timing is not valid, determining whether a second PUR timing among the plurality of PUR timings is valid.

[0300] Aspect 51: The method according to aspect 49 further includes: after determining that the first PUR timing is not valid, abandoning the transmission of the uplink transmission during at least one subsequent PUR timing among the plurality of PUR timings.

[0301] Aspect 52: According to the method of aspect 51, wherein abandoning the transmission of the uplink transmission during the at least one second PUR timing includes: suspending the transmission on the plurality of PUR timings for a period of time.

[0302] Aspect 53: The method according to aspect 52, wherein the PUR verification information includes an indication of the time period.

[0303] Aspect 54: According to the method of aspect 51, wherein abandoning the transmission of the uplink transmission during the at least one second PUR timing comprises: suspending transmission for a specified number of PUR timings among the plurality of PUR timings.

[0304] Aspect 55: The method according to aspect 54, wherein the PUR verification information includes an indication of the specified quantity.

[0305] Aspect 56: The method according to aspect 49 further includes: after determining that the first PUR timing is not valid, abandoning the transmission of the uplink transmission during any of the plurality of PUR timings.

[0306] Aspect 57: The method according to any one of aspects 41 to 56, wherein the verification procedure includes: determining that the TA verification for the first PUR timing has failed; and abandoning the verification of the first PUR timing after determining that the TA verification for the first PUR timing has failed.

[0307] Aspect 58: The method according to aspect 57 further includes: after determining that the TA verification for the first PUR timing has failed, determining whether a second PUR timing among the plurality of PUR timings is valid.

[0308] Aspect 59: The method according to aspect 57 further includes: after determining that the TA verification for the first PUR timing has failed, abandoning the transmission of the uplink transmission during at least one second PUR timing among the plurality of PUR timings.

[0309] Aspect 60: According to the method of aspect 59, wherein abandoning the transmission of the uplink transmission during the at least one second PUR timing includes: pausing the transmissions on the plurality of PUR timings for a period of time.

[0310] Aspect 61: The method according to aspect 59, wherein abandoning the transmission of the uplink transmission during the at least one second PUR timing comprises: suspending transmission for a specified number of PUR timings among the plurality of PUR timings.

[0311] Aspect 62: The method according to aspect 57 further includes: after determining that the TA verification for the first PUR timing has failed, abandoning the transmission of the uplink transmission during any of the plurality of PUR timings.

[0312] Aspect 63: The method according to any one of aspects 41 to 62, wherein the verification procedure includes: determining that the TA verification for the first PUR timing has passed; and verifying the first PUR timing after determining that the TA verification for the first PUR timing has passed.

[0313] Aspect 64: The method according to any one of aspects 41 to 63, wherein the verification process includes: determining that the PUR verification for the first PUR timing has failed; and after determining that the PUR verification for the first PUR timing has failed, abandoning the execution of TA verification for the first PUR timing.

[0314] Aspect 65: The method according to any one of aspects 41 to 63, wherein the verification process includes: determining that the PUR verification for the first PUR timing is passed; and after determining that the PUR verification for the first PUR timing is passed, performing TA verification for the first PUR timing.

[0315] Aspect 66: The method according to any one of aspects 41 to 65, wherein the PUR verification information and the TA verification information include a start time and a timer duration for verifying at least one of the following: the first PUR timing, the TA for the first PUR timing, or a combination thereof.

[0316] Aspect 67: The method according to any one of aspects 41 to 65, wherein the PUR verification information and the TA verification information include an end time and a timer duration for verifying at least one of the following: the first PUR timing, the TA for the first PUR timing, or a combination thereof.

[0317] Aspect 68: The method according to any one of aspects 41 to 65, wherein the PUR verification information includes a start time and an end time for verifying at least one of the following: the first PUR timing, the TA for the first PUR timing, or a combination thereof.

[0318] Aspect 69: The method according to any one of aspects 41 to 68, wherein the PUR verification information is defined for all user equipment under the cell of the base station.

[0319] Aspect 70: The method according to any one of aspects 41 to 69, wherein performing the verification process includes: determining that a handover gap between a first uplink transmission and a first downlink transmission is defined for the user equipment; and after determining that the handover gap between the first uplink transmission and the first downlink transmission is defined for the user equipment, determining whether the time gap between the first PUR timing and the last downlink symbol before the first PUR timing is greater than or equal to a threshold, and determining whether the user equipment has performed a measurement for TA verification before the last downlink symbol.

[0320] Aspect 71: The method according to aspect 70, wherein the threshold depends on at least one of the following: duplex mode, subcarrier spacing for the first PUR timing, the at least one capability of the user equipment, or a combination thereof.

[0321] Aspect 72: The method according to aspect 70, wherein the threshold is a standardized value, or the user equipment receives the threshold from the base station.

[0322] Aspect 73: The method according to any one of aspects 70 to 72, wherein determining whether the switching gap between the first uplink transmission and the first downlink transmission is defined for the user equipment includes: determining whether the user equipment is operating in time division duplex (TDD) mode, full duplex-frequency division duplex (FD-FDD) mode or half duplex-frequency division duplex (HD-FDD) mode.

[0323] Aspect 74: The method according to any one of aspects 41 to 73, wherein performing the verification process includes: determining whether the uplink symbol for the first PUR timing is aligned with the slot format for the time division duplex (TDD) operation mode.

[0324] Aspect 75: The method according to any one of aspects 41 to 73, wherein performing the verification process includes: determining whether the uplink symbol for the first PUR timing is aligned with the uplink resource configuration for the half-duplex-frequency division duplex (HD-FDD) operating mode.

[0325] Aspect 76: The method according to any one of aspects 41 to 73, wherein performing the verification process includes: verifying that the uplink symbol for the first PUR timing does not share a time slot with the first uplink transmission performed by the user equipment.

[0326] Aspect 77: The method according to any one of aspects 41 to 76, wherein performing the verification process includes: determining whether a transmission gap between a first uplink transmission and a PUR transmission is defined for the user equipment; and if the transmission gap is defined, determining whether the time gap between the first PUR timing and the last uplink symbol prior to the first PUR timing is greater than or equal to a threshold.

[0327] Aspect 78: The method according to aspect 77, wherein the threshold depends on at least one of the following: duplex mode, subcarrier spacing for the first PUR timing, the at least one capability of the user equipment, or a combination thereof.

[0328] Aspect 79: The method according to aspect 77, wherein the threshold is a standardized value, or the user equipment receives the threshold from the base station.

[0329] Aspect 80: According to the method of aspect 77, wherein determining whether the transmission gap between the first uplink transmission and the PUR transmission is defined for the user equipment includes: determining whether the user equipment is operating in time division duplex (TDD) mode, full duplex-frequency division duplex (FD-FDD) mode or half duplex-frequency division duplex (HD-FDD) mode.

[0330] Aspect 81: A base station comprising: a transceiver; a memory; and a processor coupled to the transceiver and the memory, wherein the processor is configured to: receive, via the transceiver, an indication of at least one capability of a user equipment; generate a pre-configured uplink resource (PUR) configuration, the PUR configuration including PUR authentication information and timing advance (TA) authentication information for a plurality of PUR times, wherein the PUR authentication message and the TA authentication information depend on the at least one capability of the user equipment; transmit the PUR configuration to the user equipment via the transceiver; and receive uplink transmissions from the user equipment via the transceiver during at least one of the plurality of PUR times.

[0331] Aspect 82: The base station according to aspect 81, wherein the PUR verification information includes at least one of the following: resource allocation associated with the plurality of PUR times, transmission parameters associated with the plurality of PUR times, or a combination thereof.

[0332] Aspect 83: A base station according to any one of aspects 81 to 82, wherein the processor is further configured to transmit the PUR configuration via a Radio Resource Control (RRC) message or a Media Access Control-Control Element (MAC-CE).

[0333] Aspect 84: A base station according to any one of aspects 81 to 83, wherein the PUR verification information includes a start time and a timer duration for verifying at least one of the following: the plurality of PUR timings, a TA for the plurality of PUR timings, or a combination thereof.

[0334] Aspect 85: The base station according to aspect 84, wherein: the at least one capability of the user equipment indicates the uplink-to-downlink handover time of the user equipment; and the processor is further configured to: define the start time based on the uplink-to-downlink handover time of the user equipment.

[0335] Aspect 86: The base station according to aspect 84, wherein: the at least one capability of the user equipment indicates the user equipment processing capability; and the processor is further configured to: define the timer duration based on the user equipment processing capability.

[0336] Aspect 87: A base station according to any one of aspects 81 to 83, wherein the PUR verification information includes an end time and a timer duration for verifying at least one of the following: the plurality of PUR timings, a TA for the plurality of PUR timings, or a combination thereof.

[0337] Aspect 88: The base station according to aspect 87, wherein: the at least one capability of the user equipment indicates the user equipment downlink to uplink handover time; and the processor is further configured to: define the end time based on the user equipment downlink to uplink handover time.

[0338] Aspect 89: A base station according to any one of aspects 81 to 83, wherein the PUR verification information includes a start time and an end time for verifying at least one of the following: the plurality of PUR timings, a TA for the plurality of PUR timings, or a combination thereof.

[0339] Aspect 90: A base station according to any one of aspects 81 to 89, wherein the PUR authentication information is defined for all user equipment under the cell of the base station.

[0340] Aspect 91: A base station according to any one of aspects 81 to 90, wherein the processor is further configured to: define the PUR authentication information and the TA authentication information based on the at least one capability of the user equipment.

[0341] Aspect 92: A base station according to any one of aspects 81 to 91, wherein the processor is further configured to: define a threshold for a time gap between a first PUR timing and the last downlink symbol preceding the first PUR timing among the plurality of PUR timings.

[0342] Aspect 93: The base station according to aspect 92, wherein the processor is further configured to define the threshold based on at least one of the following: duplex mode, subcarrier spacing for the first PUR timing, the at least one capability of the user equipment, or a combination thereof.

[0343] Aspect 94: The base station according to any one of aspects 92 to 93, wherein the PUR configuration includes an indication of the threshold.

[0344] Aspect 95: A base station according to any one of aspects 81 to 94, wherein the processor is further configured to: define a threshold for the time interval between a first PUR timing and the last uplink symbol preceding the first PUR timing among the plurality of PUR timings.

[0345] Aspect 96: The base station according to aspect 95, wherein the processor is further configured to define the threshold based on at least one of the following: duplex mode, subcarrier spacing for the first PUR timing, the at least one capability of the user equipment, or a combination thereof.

[0346] Aspect 97: The base station according to aspect 95, wherein the PUR configuration includes an indication of the threshold.

[0347] Aspect 98: A base station according to any one of aspects 81 to 97, wherein the processor is further configured to: receive a PUR configuration request from the user equipment; and, in response to the PUR configuration request, send the PUR configuration to the user equipment.

[0348] Aspect 99: A base station according to any one of aspects 81 to 98, wherein the PUR authentication information includes an indication of a time period for suspending transmission at the plurality of PUR times in response to a PUR authentication failure or a TA authentication failure.

[0349] Aspect 100: A base station according to any one of aspects 81 to 98, wherein the PUR verification information includes an indication of a specified number of PUR timings that will be suspended in response to a PUR verification failure or a TA verification failure.

[0350] Aspect 101: A method for wireless communication at a base station, the method comprising: receiving an indication of at least one capability of a user equipment; generating a pre-configured uplink resource (PUR) configuration, the PUR configuration including PUR authentication information and timing advance (TA) authentication information for a plurality of PUR times, wherein the PUR authentication information and the TA authentication information depend on the at least one capability of the user equipment; sending the PUR configuration to the user equipment; and receiving uplink transmissions from the user equipment during at least one of the plurality of PUR times.

[0351] Aspect 102: According to the method of aspect 101, wherein the PUR verification information includes at least one of the following: resource allocation associated with the plurality of PUR times, transmission parameters associated with the plurality of PUR times, or a combination thereof.

[0352] Aspect 103: The method according to any one of aspects 101 to 102, wherein sending the PUR configuration includes sending the PUR configuration via a Radio Resource Control (RRC) message or a Media Access Control-Control Element (MAC-CE).

[0353] Aspect 104: The method according to any one of aspects 101 to 103, wherein the PUR verification information includes a start time and a timer duration for verifying at least one of the following: the plurality of PUR timings, a TA for the plurality of PUR timings, or a combination thereof.

[0354] Aspect 105: The method according to aspect 104, wherein: the at least one capability of the user equipment indicates the uplink-to-downlink handover time of the user equipment; and generating the PUR configuration includes defining the start time based on the uplink-to-downlink handover time of the user equipment.

[0355] Aspect 106: The method according to aspect 105, wherein: the at least one capability of the user equipment indicates the user equipment processing capability; and generating the PUR configuration includes defining the timer duration based on the user equipment processing capability.

[0356] Aspect 107: The method according to any one of aspects 101 to 106, wherein the PUR verification information includes an end time and a timer duration for verifying at least one of the following: the plurality of PUR timings, a TA for the plurality of PUR timings, or a combination thereof.

[0357] Aspect 108: The method according to aspect 107, wherein: the at least one user equipment capability indicates the user equipment downlink to uplink handover time; and generating the PUR configuration includes: defining the end time based on the user equipment downlink to uplink handover time.

[0358] Aspect 109: The method according to any one of aspects 101 to 108, wherein the PUR verification information includes a start time and an end time for verifying at least one of the following: the plurality of PUR timings, a TA for the plurality of PUR timings, or a combination thereof.

[0359] Aspect 110: The method according to any one of aspects 101 to 109, wherein the PUR verification information is defined for all user equipment under the cell of the base station.

[0360] Aspect 111: The method according to any one of aspects 101 to 110, wherein generating the PUR configuration includes: defining the PUR authentication information and the TA authentication information based on the at least one capability of the user equipment.

[0361] Aspect 112: The method according to any one of aspects 101 to 111, wherein generating the PUR configuration includes: defining a threshold for the time interval between a first PUR timing and the last downlink symbol preceding the first PUR timing.

[0362] Aspect 113: The method according to aspect 112, wherein defining the threshold includes defining the threshold based on at least one of the following: duplex mode, subcarrier spacing for the first PUR timing, the at least one capability of the user equipment, or a combination thereof.

[0363] Aspect 114: The method according to aspect 112, wherein the PUR configuration includes an indication of the threshold.

[0364] Aspect 115: The method according to any one of aspects 101 to 114, wherein generating the PUR configuration includes: defining a threshold for the time interval between a first PUR timing and the last uplink symbol preceding the first PUR timing.

[0365] Aspect 116: The method according to aspect 115, wherein defining the threshold includes defining the threshold based on at least one of the following: duplex mode, subcarrier spacing for the first PUR timing, the at least one capability of the user equipment, or a combination thereof.

[0366] Aspect 117: The method according to aspect 115, wherein the PUR configuration includes an indication of the threshold.

[0367] Aspect 118: The method according to any one of aspects 101 to 117 further includes: receiving a PUR configuration request from the user equipment; and sending the PUR configuration to the user equipment in response to the PUR configuration request.

[0368] Aspect 119: The method according to any one of aspects 101 to 118, wherein the PUR verification information includes an indication of a time period for suspending transmission at the plurality of PUR times in response to a PUR verification failure or a TA verification failure.

[0369] Aspect 120: The method according to any one of aspects 101 to 119, wherein the PUR verification information includes an indication of a specified number of PUR timings that will be paused in response to a PUR verification failure or a TA verification failure.

[0370] Aspect 121: A user equipment includes: a unit for receiving a pre-configured uplink resource (PUR) configuration, the PUR configuration including PUR verification information and timing advance (TA) verification information for a plurality of PUR times, wherein the PUR verification information and the TA verification information depend on at least one capability of the user equipment; a unit for performing a verification process for a first PUR time among the plurality of PUR times based on the PUR verification information and the TA verification information; and a unit for selectively transmitting uplink transmissions during the first PUR time based on the verification process.

[0371] Aspect 122: A base station comprising: a unit for receiving an indication of at least one capability of a user equipment; a unit for generating a pre-configured uplink resource (PUR) configuration, the PUR configuration including PUR verification information and timing advance (TA) verification information for a plurality of PUR times, wherein the PUR verification information and the TA verification information depend on the at least one capability of the user equipment; a unit for sending the PUR configuration to the user equipment; and a unit for receiving uplink transmissions from the user equipment during at least one of the plurality of PUR times.

[0372] Aspect 123: A computer program including instructions that, when executed by a computer of a user equipment (UE), cause the computer to perform the steps of the method according to aspects 41 to 80.

[0373] Aspect 124: A computer program including instructions that, when executed by a computer at a base station, cause the computer to perform the steps of the method according to aspects 101 to 120.

[0374] Aspect 125: An apparatus configured for wireless communication, comprising at least one unit for performing any one of aspects 41 to 80.

[0375] Aspect 126: A non-transitory computer-readable medium storing computer-executable code, including for causing a device to execute the code according to any one of aspects 41 to 80.

[0376] Aspect 127: An apparatus configured for wireless communication, comprising at least one unit for performing the functions described in any one of aspects 101 to 120.

[0377] Aspect 128: A non-transitory computer-readable medium storing computer-executable code, including means for causing a device to execute the code according to any one of aspects 101 to 120.

[0378] Several aspects of wireless communication networks have been described with reference to example implementations. As will be readily recognized by those skilled in the art, the various aspects described throughout this disclosure can be extended to other telecommunications systems, network architectures, and communication standards.

[0379] For example, the various aspects can be implemented within other systems defined by 3GPP, such as Long Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile Communications (GSM). The aspects can also be extended to systems defined by 3GPP2, such as CDMA2000 and / or Evolved Data Optimization (EV-DO). Other examples can be implemented within systems employing IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra Wideband (UWB), Bluetooth, and / or other suitable systems. The specific telecommunications standards, network architecture, and / or communication standards employed depend on the specific application and the overall design constraints imposed on the system.

[0380] In this disclosure, the term "exemplary" as used means "serving as an example, instance, or illustration." Any implementation or aspect described herein as "exemplary" should not be construed as superior or advantageous to other aspects of this disclosure. Similarly, the term "aspect" does not require that all aspects of this disclosure include the features, advantages, or modes of operation discussed. The term "coupling" is used herein to refer to direct or indirect coupling between two objects. For example, if object A physically contacts object B, and object B contacts object C, objects A and C can still be considered coupled to each other, even if they are not in direct physical contact. For example, a first object can be coupled to a second object, even if the first object never physically contacts the second object. The terms "circuit" and "circuitry" are used broadly, and they are intended to include both hardware implementations of electronic devices and conductors (where these electronic devices and conductors, when connected and configured, perform the functions described in this disclosure, without limitation on the type of electronic circuit) and software implementations of information and instructions (where these information and instructions, when executed by a processor, perform the functions described in this disclosure).

[0381] Can be Figure 1-22 The components, steps, features, and / or functions shown herein may be rearranged and / or combined into a single component, step, feature, or function, or embodied in several components, steps, or functions. Furthermore, additional elements, components, steps, and / or functions may be added without departing from the novel features disclosed herein. Figure 1 , 2 The apparatuses, devices, and / or components shown in 4, 6-10, 17, and 20 may be configured to perform one or more of the methods, features, or steps described herein. The novel algorithms described herein can also be efficiently implemented in software and / or embedded in hardware.

[0382] It is to be understood that the specific order or hierarchy of steps in the methods disclosed herein is an illustration of an exemplary process. It is to be understood that the specific order or hierarchy of steps in these methods may be rearranged based on design preferences. The appended method claims give the elements of each step in an exemplary order, but are not intended to limit one to the given specific order or hierarchy unless expressly stated herein.

[0383] The preceding description is provided to enable any person skilled in the art to implement the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but are to be given the full scope consistent with the text of the claims, wherein references to elements in the singular form are not intended to mean “one and only one”, but rather “one or more”, unless expressly stated otherwise. Unless expressly stated otherwise, the term “some” means one or more. The phrase “at least one” referring to a list of items means any combination of those items, including a single member. For example, “at least one of a, b, or c” is intended to cover: a; b; c; a and b; a and c; b and c; and a, b, and c. All structural and functional equivalents of elements throughout the various aspects described in this disclosure that are known or to be known to those skilled in the art are expressly incorporated herein by reference, and are intended to be included in the claims. Furthermore, nothing herein is intended to be offered to the public, whether or not such disclosure is expressly recited in the claims.

Claims

1. A user equipment, comprising: One or more memories that store processor-executable code; as well as One or more processors coupled to the one or more memories and configured to execute processor-executable code and cause the user equipment to perform the following operations: Receive a pre-configured uplink resource (PUR) configuration, the PUR configuration including PUR verification information and timing advance (TA) verification information for multiple PUR timings, wherein the PUR verification information and the TA verification information depend on at least one capability of the user equipment; Based on the PUR verification information and the TA verification information, a verification process is performed for the first PUR opportunity among the plurality of PUR opportunities, wherein the verification process includes: A switching gap between the first uplink transmission and the first downlink transmission is defined for the user equipment. Determine whether the time gap between the first PUR timing and the last downlink symbol prior to the first PUR timing is greater than or equal to a first threshold, and Determine whether the user equipment has performed measurements for TA verification prior to the last downlink symbol; and According to the verification process, uplink transmissions are selectively sent during the first PUR timing.

2. The user equipment according to claim 1, wherein, The one or more processors are also configured to execute processor executable code and to cause the user equipment to perform the following operations: Send a PUR configuration request to the network entity; and The PUR configuration is received from the network entity after the PUR configuration request is sent.

3. The user equipment according to claim 2, wherein: The PUR configuration request indicates at least one of the capabilities of the user equipment; The PUR configuration includes an uplink bandwidth portion configuration, which is associated with at least one of the following: a first PUR verification for the plurality of PUR times, a first TA verification for the plurality of PUR times, a first transmission on the plurality of PUR times, or a combination thereof; and The PUR configuration includes a downlink bandwidth portion configuration, which is associated with at least one of the following: a second PUR verification for the plurality of PUR times, a second TA verification for the plurality of PUR times, a second transmission on the plurality of PUR times, or a combination thereof.

4. The user equipment according to claim 1, wherein: The plurality of PUR timings are configured on the uplink bandwidth portion indicated by the PUR configuration; and The one or more processors are also configured to execute processor-executable code and cause the user equipment to selectively transmit the uplink transmission based on at least one transmission parameter associated with at least one valid PUR timing among the plurality of PUR timings.

5. The user equipment according to claim 1, wherein, The PUR verification information includes at least one of the following: resource allocation associated with the plurality of PUR times, transmission parameters associated with the plurality of PUR times, an uplink bandwidth portion configured for PUR verification for the plurality of PUR times, a downlink bandwidth portion configured for PUR verification for the plurality of PUR times, or a combination thereof.

6. The user equipment according to claim 1, wherein, The one or more processors are also configured to execute processor executable code and to cause the user equipment to perform the following operations: The PUR configuration is received via Radio Resource Control (RRC) messages or Media Access Control-Control Element (MAC-CE).

7. The user equipment according to claim 1, wherein: The PUR configuration indicates the uplink bandwidth portion for the plurality of PUR timings, wherein the first PUR timing is in the uplink bandwidth portion; The PUR configuration indicates the downlink bandwidth portion of the measurement associated with TA verification of the plurality of PUR timings; and The one or more processors are also configured to execute processor executable code and cause the user equipment to determine that the TA is valid based on whether the user equipment performed measurements for the TA verification process on the downlink bandwidth portion prior to the first PUR timing in the uplink bandwidth portion.

8. The user equipment according to claim 1, wherein, The one or more processors are also configured to execute processor executable code and to cause the user equipment to perform the following operations: Based on the verification process, it is determined that the first PUR timing is not valid; and After determining that the first PUR timing is not valid, the uplink transmission during the first PUR timing is abandoned.

9. The user equipment according to claim 8, wherein, The one or more processors are also configured to execute processor executable code and to cause the user equipment to perform the following operations: After determining that the first PUR timing is not valid, it is then determined whether the second PUR timing among the plurality of PUR timings is valid.

10. The user equipment according to claim 8, wherein, The one or more processors are also configured to execute processor executable code and to cause the user equipment to perform the following operations: After determining that the first PUR timing is not valid, the uplink transmission is abandoned during at least one subsequent PUR timing among the plurality of PUR timings.

11. The user equipment according to claim 10, wherein, The one or more processors are also configured to execute processor executable code and to cause the user equipment to perform the following operations: Transmissions at the multiple PUR times will be paused for a period of time.

12. The user equipment according to claim 11, wherein, The PUR verification information includes an indication of the time period.

13. The user equipment according to claim 10, wherein, The one or more processors are also configured to execute processor executable code and to cause the user equipment to perform the following operations: Suspend transmission for a specified number of PUR times out of the plurality of PUR times.

14. The user equipment according to claim 13, wherein, The PUR verification information includes an indication of the specified quantity.

15. The user equipment according to claim 8, wherein, The one or more processors are also configured to execute processor executable code and to cause the user equipment to perform the following operations: After determining that the first PUR timing is not valid, the uplink transmission is abandoned during any of the plurality of PUR timings.

16. The user equipment according to claim 1, wherein, The one or more processors are also configured to execute processor executable code and to cause the user equipment to perform the following operations: The TA verification for the first PUR timing was determined to have failed. as well as After determining that the TA verification for the first PUR timing has failed, the verification of the first PUR timing is abandoned.

17. The user equipment according to claim 16, wherein, The one or more processors are also configured to execute processor executable code and to cause the user equipment to perform the following operations: After determining that the TA verification for the first PUR timing has failed, it is determined whether the second PUR timing among the plurality of PUR timings is valid.

18. The user equipment according to claim 16, wherein, The one or more processors are also configured to execute processor executable code and to cause the user equipment to perform the following operations: After determining that the TA verification for the first PUR timing has failed, the uplink transmission is abandoned during at least one of the multiple PUR timings, which is a second PUR timing.

19. The user equipment according to claim 16, wherein, The one or more processors are also configured to execute processor executable code and to cause the user equipment to perform the following operations: Transmissions at the multiple PUR times will be paused for a period of time.

20. The user equipment according to claim 18, wherein, The one or more processors are also configured to execute processor executable code and to cause the user equipment to perform the following operations: Suspend transmission for a specified number of PUR times out of the plurality of PUR times.

21. The user equipment according to claim 16, wherein, The one or more processors are also configured to execute processor executable code and to cause the user equipment to perform the following operations: After determining that the TA verification for the first PUR timing has failed, the uplink transmission is abandoned during any of the plurality of PUR timings.

22. The user equipment according to claim 1, wherein, The one or more processors are also configured to execute processor executable code and to cause the user equipment to perform the following operations: The TA verification for the first PUR timing was confirmed to be successful; and After the TA verification for the first PUR timing is determined to be successful, the first PUR timing is verified.

23. The user equipment according to claim 1, wherein, The one or more processors are also configured to execute processor executable code and to cause the user equipment to perform the following operations: The PUR verification for the first PUR timing was determined to have failed; as well as After determining that the PUR verification for the first PUR timing has failed, the TA verification for the first PUR timing is abandoned.

24. The user equipment according to claim 1, wherein, The one or more processors are also configured to execute processor executable code and to cause the user equipment to perform the following operations: The PUR verification for the first PUR timing was confirmed to be successful; and After the PUR verification for the first PUR timing is determined to be successful, TA verification for the first PUR timing is performed.

25. The user equipment according to claim 1, wherein, The PUR verification information and the TA verification information include a start time and a timer duration for verifying at least one of the following: the first PUR timing, the TA for the first PUR timing, or a combination thereof.

26. The user equipment according to claim 1, wherein, The PUR verification information and the TA verification information include an end time and a timer duration for verifying at least one of the following: the first PUR timing, the TA for the first PUR timing, or a combination thereof.

27. The user equipment according to claim 1, wherein, The PUR verification information includes the start and end times for verifying at least one of the following: the first PUR timing, the TA for the first PUR timing, or a combination thereof.

28. The user equipment according to claim 1, wherein, The PUR authentication information is defined for all user equipment within a cell of a network entity.

29. The user equipment according to claim 1, wherein, The first threshold depends on at least one of the following: duplex mode, subcarrier spacing for the first PUR timing, the capability of the user equipment, or a combination thereof.

30. The user equipment according to claim 1, wherein, The first threshold is a standardized value, or the user equipment receives the first threshold from a network entity.

31. The user equipment according to claim 1, wherein, The one or more processors are also configured to execute processor executable code and to cause the user equipment to perform the following operations: Determine whether the user equipment is operating in Time Division Duplex (TDD), Full Duplex-Frequency Division Duplex (FD-FDD), or Half Duplex-Frequency Division Duplex (HD-FDD) mode.

32. The user equipment according to claim 1, wherein, The one or more processors are also configured to execute processor executable code and to cause the user equipment to perform the following operations: Determine whether the uplink symbol used for the first PUR timing is aligned with the slot format used for the time division duplex (TDD) operation mode.

33. The user equipment according to claim 1, wherein, The one or more processors are also configured to execute processor executable code and to cause the user equipment to perform the following operations: Determine whether the uplink symbol used for the first PUR timing is aligned with the uplink resource configuration used for the half-duplex-frequency division duplex (HD-FDD) operation mode.

34. The user equipment according to claim 1, wherein, The one or more processors are also configured to execute processor executable code and to cause the user equipment to perform the following operations: Determine whether a transmission gap between the second uplink transmission and the PUR transmission has been defined for the user equipment; as well as If the transmission gap is defined, it is determined whether the second time gap between the first PUR timing and the last uplink symbol before the first PUR timing is greater than or equal to the second threshold.

35. The user equipment according to claim 34, wherein, The second threshold depends on at least one of the following: duplex mode, subcarrier spacing for the first PUR timing, at least one capability of the user equipment, or a combination thereof.

36. The user equipment according to claim 34, wherein, The second threshold is a standardized value, or the user equipment receives the second threshold from the network entity.

37. The user equipment according to claim 34, wherein, The one or more processors are also configured to execute processor executable code and to cause the user equipment to perform the following operations: Determine whether the user equipment is operating in Time Division Duplex (TDD), Full Duplex-Frequency Division Duplex (FD-FDD), or Half Duplex-Frequency Division Duplex (HD-FDD) mode.

38. A method for conducting wireless communication at a user equipment, the method comprising: Receive a pre-configured uplink resource (PUR) configuration, the PUR configuration including PUR verification information and timing advance (TA) verification information for multiple PUR timings, wherein the PUR verification information and the TA verification information depend on at least one capability of the user equipment; Based on the PUR verification information and the TA verification information, a verification process is performed for the first PUR opportunity among the plurality of PUR opportunities, wherein the verification process includes: A switching gap between the first uplink transmission and the first downlink transmission is defined for the user equipment. Determine whether the time gap between the first PUR timing and the last downlink symbol prior to the first PUR timing is greater than or equal to a first threshold, and Determine whether the user equipment has performed measurements for TA verification prior to the last downlink symbol; and According to the verification process, uplink transmissions are selectively sent during the first PUR timing.

39. The method of claim 38, further comprising: Send a PUR configuration request to the network entity. The PUR configuration is received from the network entity after the PUR configuration request is sent.

40. The method of claim 39, wherein: The PUR configuration request indicates at least one of the capabilities of the user equipment; The PUR configuration includes an uplink bandwidth portion configuration, which is associated with at least one of the following: a first PUR verification for the plurality of PUR times, a first TA verification for the plurality of PUR times, a first transmission on the plurality of PUR times, or a combination thereof; and The PUR configuration includes a downlink bandwidth portion configuration, which is associated with at least one of the following: a second PUR verification for the plurality of PUR times, a second TA verification for the plurality of PUR times, a second transmission on the plurality of PUR times, or a combination thereof.

41. The method according to claim 38, wherein: The plurality of PUR timings are configured on the uplink bandwidth portion indicated by the PUR configuration; and Selectively sending the uplink transmission during the first PUR timing according to the verification process includes: selectively sending the uplink transmission based on at least one transmission parameter associated with at least one valid PUR timing among the plurality of PUR timings.

42. The method according to claim 38, wherein, The PUR verification information includes at least one of the following: resource allocation associated with the plurality of PUR times, transmission parameters associated with the plurality of PUR times, an uplink bandwidth portion configured for PUR verification for the plurality of PUR times, a downlink bandwidth portion configured for PUR verification for the plurality of PUR times, or a combination thereof.

43. The method according to claim 38, wherein, The receipt of the PUR configuration includes: The PUR configuration is received via Radio Resource Control (RRC) messages or Media Access Control-Control Element (MAC-CE).

44. The method of claim 38, wherein: The PUR configuration indicates the uplink bandwidth portion for the plurality of PUR timings, wherein the first PUR timing is in the uplink bandwidth portion; The PUR configuration indicates the downlink bandwidth portion of the measurement associated with TA verification of the plurality of PUR timings; and The determination of whether the TA is valid is based on whether the user equipment performed measurements for the TA verification process on the downlink bandwidth portion before the first PUR timing in the uplink bandwidth portion.

45. The method according to claim 38, wherein, The step of selectively sending the uplink transmission during the first PUR timing according to the verification process includes: Based on the verification process, it is determined that the first PUR timing is not valid; and After determining that the first PUR timing is not valid, the uplink transmission during the first PUR timing is abandoned.

46. ​​The method according to claim 38, wherein, The verification process includes: It was determined that the TA verification for the first PUR timing failed; and After determining that the TA verification for the first PUR timing has failed, the verification of the first PUR timing is abandoned.

47. A network entity, comprising: One or more memories that store processor-executable code; as well as One or more processors, coupled to the one or more memories and configured to execute processor-executable code and cause the network entity to perform the following operations: Receive instructions on at least one capability of the user equipment; Generate a pre-configured uplink resource (PUR) configuration, the PUR configuration including PUR verification information and timing advance (TA) verification information for multiple PUR times, wherein the PUR verification information and the TA verification information depend on the user equipment's at least one capability; Define a threshold for the time gap between a first PUR timing and the last downlink symbol preceding the first PUR timing, wherein the threshold is defined based on at least one of the following: duplex mode, subcarrier spacing for the first PUR timing, at least one capability of the user equipment, or a combination thereof. Send the PUR configuration to the user equipment; and During at least one of the plurality of PUR times, an uplink transmission is received from the user equipment.

48. The network entity according to claim 47, wherein, The PUR verification information includes at least one of the following: resource allocation associated with the plurality of PUR times, transmission parameters associated with the plurality of PUR times, or a combination thereof.

49. The network entity according to claim 47, wherein, The one or more processors are also configured to execute processor executable code and cause the network entity to perform the following operations: The PUR configuration is sent via Radio Resource Control (RRC) messages or Media Access Control-Control Element (MAC-CE).

50. The network entity according to claim 47, wherein, The PUR verification information includes the start time and timer duration for verifying at least one of the following: the plurality of PUR timings, the TA for the plurality of PUR timings, or a combination thereof.

51. The network entity according to claim 50, wherein: The at least one capability of the user equipment indicates the uplink-to-downlink handover time of the user equipment; and The one or more processors are also configured to execute processor executable code and cause the network entity to define the start time based on the uplink-to-downlink switching time of the user equipment.

52. The network entity according to claim 50, wherein: The at least one capability of the user equipment indicates the user equipment's processing capability; and The one or more processors are also configured to execute processor-executable code and cause the network entity to define the timer duration based on the user equipment processing capabilities.

53. The network entity according to claim 47, wherein, The PUR verification information includes the end time and timer duration for verifying at least one of the following: the plurality of PUR timings, the TA for the plurality of PUR timings, or a combination thereof.

54. The network entity according to claim 53, wherein: The at least one capability of the user equipment indicates the downlink-to-uplink handover time of the user equipment; and The one or more processors are also configured to execute processor executable code and cause the network entity to define the end time based on the user equipment downlink-to-uplink switching time.

55. The network entity according to claim 47, wherein, The PUR verification information includes start and end times for verifying at least one of the following: the plurality of PUR timings, the TA for the plurality of PUR timings, or a combination thereof.

56. The network entity according to claim 47, wherein, The PUR authentication information is defined for all user equipment within the cell of the network entity.

57. The network entity according to claim 47, wherein, The one or more processors are also configured to execute processor executable code and cause the network entity to perform the following operations: The PUR verification information and the TA verification information are defined based on at least one capability of the user equipment.

58. The network entity according to claim 47, wherein, The PUR configuration includes an indication of the threshold.

59. The network entity according to claim 47, wherein, The one or more processors are also configured to execute processor executable code and cause the network entity to perform the following operations: Receive a PUR configuration request from the user equipment; and In response to the PUR configuration request, the PUR configuration is sent to the user equipment.

60. The network entity according to claim 47, wherein, The PUR verification information includes an indication of the time period for suspending transmission at the plurality of PUR times in response to a PUR verification failure or a TA verification failure.

61. The network entity according to claim 47, wherein, The PUR verification information includes an indication of a specified number of PUR opportunities that will be suspended in response to a PUR verification failure or a TA verification failure.

62. A method for wireless communication at a network entity, the method comprising: Receive instructions on at least one capability of the user equipment; Generate a pre-configured uplink resource (PUR) configuration, the PUR configuration including PUR verification information and timing advance (TA) verification information for multiple PUR times, wherein the PUR verification information and the TA verification information depend on the user equipment's at least one capability; Define a threshold for the time gap between a first PUR timing and the last downlink symbol preceding the first PUR timing, wherein the threshold is defined based on at least one of the following: duplex mode, subcarrier spacing for the first PUR timing, at least one capability of the user equipment, or a combination thereof. Send the PUR configuration to the user equipment; and Uplink transmissions are received from the user equipment during at least one of the plurality of PUR times.

63. The method according to claim 62, wherein, The PUR verification information includes at least one of the following: resource allocation associated with the plurality of PUR times, transmission parameters associated with the plurality of PUR times, or a combination thereof.

64. The method according to claim 62, wherein, Sending the PUR configuration includes: The PUR configuration is sent via Radio Resource Control (RRC) messages or Media Access Control-Control Element (MAC-CE).

65. The method according to claim 62, wherein, The PUR verification information includes the start time and timer duration for verifying at least one of the following: the plurality of PUR timings, the TA for the plurality of PUR timings, or a combination thereof.

66. The method of claim 65, wherein: The at least one capability of the user equipment indicates the uplink-to-downlink handover time of the user equipment; and The generation of the PUR configuration includes defining the start time based on the uplink-to-downlink switching time of the user equipment.

67. The method of claim 65, wherein: The at least one capability of the user equipment indicates the user equipment's processing capability; and The generation of the PUR configuration includes defining the timer duration based on the user equipment's processing capabilities.

68. The method according to claim 62, wherein, The PUR verification information includes the end time and timer duration for verifying at least one of the following: the plurality of PUR timings, the TA for the plurality of PUR timings, or a combination thereof.

69. The method according to claim 68, wherein: The at least one capability of the user equipment indicates the downlink-to-uplink handover time of the user equipment; and The generation of the PUR configuration includes defining the end time based on the user equipment downlink to uplink switching time.

70. The method according to claim 62, wherein, The PUR verification information includes start and end times for verifying at least one of the following: the plurality of PUR timings, the TA for the plurality of PUR timings, or a combination thereof.

71. The method according to claim 62, wherein, The PUR authentication information is defined for all user equipment within the cell of the network entity.

Images