Method and apparatus for wireless communication

Abstract

In one aspect, a method of wireless communication includes receiving a preconfigured uplink resource (PUR) configuration message by a user equipment (UE), the message indicating a PUR configuration for small data transmission. The method also includes determining a PUR configuration release trigger for the PUR configuration by the UE. The method also includes receiving a PUR configuration release message configured to release the PUR configuration by the UE. In another aspect, a method of wireless communication includes sending a preconfigured uplink resource (PUR) configuration message by a network entity, the message indicating a PUR configuration for small data transmission. The method also includes determining a PUR configuration release trigger for the PUR configuration by the network entity. The method also includes sending a PUR configuration release message configured to release the PUR configuration by the network entity. Other aspects are described and claimed.

Description

Technical Field

[0001] Aspects of the present disclosure relate generally to wireless communication systems, and more particularly, to preconfigured uplink resource (PUR) configuration and release operations. Certain embodiments of the techniques discussed below may enable and provide enhanced PUR configuration and release operations. Background Art

[0002] Wireless communication networks are widely deployed to provide various communication services, such as voice, video, packet data, messaging, broadcasting, etc. These wireless networks can be multiple access networks that can support multiple users by sharing available network resources. Such networks are usually multiple access networks that support communication of multiple users by sharing available network resources. An example of such a network is the Universal Terrestrial Radio Access Network (UTRAN). UTRAN is a radio access network (RAN) defined as a part of the Universal Mobile Telecommunications System (UMTS), which is a third generation (3G) mobile phone technology supported by the Third Generation Partnership Project (3GPP). Examples of multiple access network formats include code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, and single carrier FDMA (SC-FDMA) networks.

[0003] A wireless communication network may include multiple base stations or Node Bs that can support communication for multiple user equipments (UEs). A UE may communicate with a base station via a downlink and an uplink. A downlink (or forward link) refers to a communication link from a base station to a UE, and an uplink (or reverse link) refers to a communication link from a UE to a base station.

[0004] The base station may send data and control information to the UE on the downlink, and / or may receive data and control information from the UE on the uplink. On the downlink, the transmission from the base station may encounter interference due to transmissions from neighboring base stations or other wireless radio frequency (RF) transmitters. On the uplink, the transmission from the UE may encounter interference from uplink transmissions of other UEs communicating with neighboring base stations or from other wireless RF transmitters. Such interference may reduce the performance of the downlink and uplink.

[0005] As the demand for mobile broadband access continues to increase, the potential for interference and congested networks increases as more UEs access long-range wireless communication networks and more short-range wireless systems are deployed in communities. Research and development continue to drive the development of wireless technologies, not only to meet the growing demand for mobile broadband access, but also to improve and enhance the user's mobile communication experience. Summary of the invention

[0006] In one aspect of the present disclosure, a method of wireless communication includes: receiving, by a user equipment (UE), a preconfigured uplink resource (PUR) configuration message indicating a PUR configuration for small data transmission; determining, by the UE, a PUR configuration release trigger for the PUR configuration; and receiving, by the UE, a PUR configuration release message configured to release the PUR configuration.

[0007] In an additional aspect of the present disclosure, an apparatus configured for wireless communication is disclosed. The apparatus includes a component for receiving, by a user equipment (UE), a preconfigured uplink resource (PUR) configuration message indicating a PUR configuration for small data transmission; a component for determining, by the UE, a PUR configuration release trigger for the PUR configuration; and a component for receiving, by the UE, a PUR configuration release message configured to release the PUR configuration.

[0008] In an additional aspect of the present disclosure, a non-transitory computer-readable medium having program code recorded thereon is disclosed. The program code further includes code for: receiving, by a user equipment (UE), a preconfigured uplink resource (PUR) configuration message indicating a PUR configuration for small data transmission; determining, by the UE, a PUR configuration release trigger for the PUR configuration; and receiving, by the UE, a PUR configuration release message configured to release the PUR configuration.

[0009] In an additional aspect of the present disclosure, a device configured for wireless communication is disclosed. The device includes at least one processor and a memory coupled to the processor. The processor is configured to receive a preconfigured uplink resource (PUR) configuration message by a user equipment (UE), the message indicating a PUR configuration for small data transmission; determine a PUR configuration release trigger for the PUR configuration by the UE; and receive a PUR configuration release message configured to release the PUR configuration by the UE.

[0010] In another aspect of the present disclosure, a method of wireless communication includes: sending, by a network entity, a preconfigured uplink resource (PUR) configuration message indicating a PUR configuration for small data transmission; determining, by the network entity, a PUR configuration release trigger for the PUR configuration; and sending, by the network entity, a PUR configuration release message configured to release the PUR configuration.

[0011] In an additional aspect of the present disclosure, an apparatus configured for wireless communication is disclosed. The apparatus includes a component for sending a preconfigured uplink resource (PUR) configuration message by a network entity, the message indicating a PUR configuration for small data transmission; a component for determining a PUR configuration release trigger for the PUR configuration by the network entity; and a component for sending a PUR configuration release message configured to release the PUR configuration by the network entity.

[0012] In an additional aspect of the present disclosure, a non-transitory computer-readable medium having program code recorded thereon is disclosed. The program code further includes code for: sending, by a network entity, a preconfigured uplink resource (PUR) configuration message indicating a PUR configuration for small data transmission; determining, by the network entity, a PUR configuration release trigger for the PUR configuration; and sending, by the network entity, a PUR configuration release message configured to release the PUR configuration.

[0013] In an additional aspect of the present disclosure, a device configured for wireless communication is disclosed. The device includes at least one processor and a memory coupled to the processor. The processor is configured to send a preconfigured uplink resource (PUR) configuration message by a network entity, the message indicating a PUR configuration for small data transmission; determine a PUR configuration release trigger for the PUR configuration by the network entity; and send a PUR configuration release message configured to release the PUR configuration by the network entity.

[0014] The features and technical advantages of the examples according to the present disclosure have been outlined quite broadly above so that the following detailed description may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The features of the concepts disclosed herein, their organization and methods of operation, and related advantages will be better understood from the following description when considered in conjunction with the accompanying drawings. Each of the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] A further understanding of the nature and advantages of the present disclosure may be achieved by reference to the following drawings. In the drawings, similar components or features may have the same reference numerals. In addition, various components of the same type may be distinguished by adding a dash and a second reference numeral after the reference numeral, the second reference numeral being used to distinguish similar components. If only the first reference numeral is used in the specification, the description applies to any similar component having the same first reference numeral, regardless of the second reference numeral.

[0016] Figure 1 is a block diagram showing details of a wireless communication system.

[0017] Figure 2 is a block diagram showing a design of a base station and a UE configured according to one aspect of the present disclosure.

[0018] Figure 3A is a diagram of the first example of PUR operation.

[0019] Figure 3B is a diagram of the second example of the PUR operation.

[0020] Figure 3C is a diagram showing the resources and settings for a specific PUR configuration.

[0021] Figure 4 is a block diagram illustrating an example of a wireless communication system (having a UE and a base station) with PUR configuration and release operations.

[0022] Figure 5 is a step diagram of an example of PUR configuration and release operations according to some embodiments of the present disclosure.

[0023] Figure 6 is a step diagram of another example of PUR deployment and release operations according to some embodiments of the present disclosure.

[0024] Figure 7 is a flow diagram illustrating example blocks executed by a UE configured according to one aspect of the present disclosure.

[0025] Figure 8 is a flow diagram illustrating example blocks executed by a base station configured according to one aspect of the present disclosure.

[0026] Fig. 9 is a block diagram conceptually illustrating a design of a UE configured to perform a precoding information update operation according to some embodiments of the present disclosure.

[0027] Fig.10 is a block diagram conceptually illustrating a design of a base station configured to perform precoding information update operations according to some embodiments of the present disclosure. DETAILED DESCRIPTION

[0028] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to limit the scope of the present disclosure. Instead, the detailed description includes specific details in order to provide a thorough understanding of the subject matter of the present invention. It is clear to those skilled in the art that these specific details are not required in every case, and in some cases, for clarity of presentation, well-known structures and components are shown in block diagram form.

[0029] The present disclosure generally relates to providing or participating in authorized shared access between two or more wireless communication systems (also referred to as wireless communication networks). In various embodiments, these techniques and devices can be used in wireless communication networks, such as code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, single carrier FDMA (SC-FDMA) networks, LTE networks, GSM networks, fifth generation (5G) or new radio (NR) networks, and other communication networks. As described herein, the terms "network" and "system" can be used interchangeably.

[0030] OFDMA networks can implement radio technologies such as Evolved UTRA (E-UTRA), IEEE 802.11, IEEE802.16, IEEE 802.20, flash-OFDM, etc. UTRA, E-UTRA, and Global System for Mobile Communications (GSM) are part of Universal Mobile Telecommunications System (UMTS). In particular, Long Term Evolution (LTE) is a version of UMTS that uses E-UTRA. UTRA, E-UTRA, GSM, UMTS, and LTE are described in documents provided by an organization named "3rd Generation Partnership Project" (3GPP), and cdma2000 is described in documents provided by an organization named "3rd Generation Partnership Project 2" (3GPP 2). These different radio technologies and standards are known or under development. For example, the 3rd Generation Partnership Project (3GPP) is a collaboration between telecommunications association groups to define globally applicable third generation (3G) mobile phone specifications. 3GPP Long Term Evolution (LTE) is a 3GPP project that aims to improve the Universal Mobile Telecommunications System (UMTS) mobile phone standard. 3GPP may define specifications for next generation mobile networks, mobile systems, and mobile devices. The present disclosure relates to the evolution of wireless technology from LTE, 4G, 5G, NR, and sharing access to wireless spectrum between networks using a set of new and different radio access technologies or radio air interfaces.

[0031] Specifically, 5G networks consider different deployments, different spectrums, and different services and devices that can be implemented using a unified air interface based on OFDM. To achieve these goals, in addition to developing new radio technologies for 5GNR networks, further enhancements to LTE and LTE-A are also considered. 5G NR will be able to scale to provide coverage (1) Ultra-high density (e.g., about 1M nodes / km 2(1) Massive Internet of Things (IoT) with ultra-low complexity (e.g., about tens of bits / second), ultra-low energy (e.g., about 10+ years of battery life), and deep coverage to reach challenging locations; (2) Mission-critical controls including strong security to protect sensitive personal, financial, or classified information, ultra-high reliability (e.g., ~99.9999% reliability), ultra-low latency (e.g., ~1 ms), and users with wide-range mobility or lack of mobility; and (3) Enhanced mobile broadband, including extremely high capacity (e.g., about 10 Tbps / km 2 ), extremely high data rates (e.g., multi-Gbps rates, 100+Mbps user experience rates), and deep awareness for advanced discovery and optimization.

[0032] 5G NR can be implemented using an optimized OFDM-based waveform with scalable parameter sets and transmission time intervals (TTI); a general, flexible framework to efficiently multiplex services and features using dynamic, low-latency time division duplex (TDD) / frequency division duplex (FDD) designs; advanced wireless technologies such as massive multiple-input multiple-output (MIMO), robust millimeter wave (mmWave) transmission, advanced channel coding, and device-centric mobility. The scalability of parameter sets in 5G NR, as well as the scaling of subcarrier spacing, can efficiently address the problem of operating different services on different spectrums and different deployments. For example, in various outdoor and macro coverage deployments of less than 3GHz FDD / TDD implementations, subcarrier spacing may appear at 15kHz, such as on bandwidths of 1, 5, 10, 20MHz, etc. For other various outdoor and small cell coverage deployments of TDD greater than 3GHz, the subcarrier spacing on 80 / 100MHz bandwidth may be 30kHz. For various other indoor broadband implementations, using TDD on the unlicensed portion of the 5GHz band, the subcarrier spacing may occur at 60kHz over a 160MHz bandwidth. Finally, for various deployments that send the mmWave component with 28GHz TDD, the subcarrier spacing may be 120kHz over a 500MHz bandwidth.

[0033] 5G NR's scalable parameter sets facilitate scalable TTIs for different latency and quality of service (QoS) requirements. For example, shorter TTIs can be used for low latency and high reliability, while longer TTIs can be used for higher spectral efficiency. Efficient multiplexing of long and short TTIs allows transmissions to start on symbol boundaries. 5G NR also considers a self-contained integrated subframe design with uplink / downlink scheduling information, data, and acknowledgment in the same subframe. The self-contained integrated subframe supports communications in unlicensed or contention-based shared spectrum, adaptive uplink / downlink, which can be flexibly configured on a per-cell basis to dynamically switch between uplink and downlink to meet current business needs.

[0034] Various other aspects and features of the present disclosure are further described below. It should be clear that the teachings herein can be implemented in various forms, and any specific structure, function, or both disclosed herein are merely representative and non-restrictive. Based on the teachings herein, it should be understood by those of ordinary skill in the art that an aspect disclosed herein can be implemented independently of any other aspect, and two or more of these aspects can be combined in various ways. For example, any number of aspects set forth herein can be used to implement a device or practice a method. In addition, in addition to one or more aspects set forth herein, or in addition to one or more aspects set forth herein, other structures, functions, or structures and functions can be used to implement such a device or practice such a method. For example, a method can be implemented as a part of a system, device, device, and / or implemented as an instruction stored on a computer-readable medium for execution on a processor or computer. In addition, an aspect can include at least one element of a claim.

[0035] Figure 1 is a block diagram illustrating a 5G network 100 including various base stations and UEs configured according to aspects of the present disclosure. The 5G network 100 includes multiple base stations 105 and other network entities. A base station may be a station that communicates with a UE and may also be referred to as an evolved Node B (eNB), a next generation eNB (gNB), an access point, etc. Each base station 105 may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to a specific geographic coverage area of ​​a base station and / or a base station subsystem serving that coverage area, depending on the context in which the term is used.

[0036] A base station may provide communication coverage for a macro cell or a small cell (such as a pico cell or a femto cell) and / or other types of cells. A macro cell typically covers a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UEs that have subscribed to services from a network provider. A small cell, such as a pico cell, typically covers a relatively small geographic area and may allow unrestricted access by UEs that have subscribed to services from a network provider. A small cell, such as a femto cell, also typically covers a relatively small geographic area (e.g., a home) and, in addition to unrestricted access, may also provide restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs of users in a home, etc.). A base station for a macro cell may be referred to as a macro base station. A base station for a small cell may be referred to as a small cell base station, a pico base station, a femto base station, or a home base station. In Figure 1 In the example shown, base stations 105d and 105e are conventional macro base stations, while base stations 105a-105c are macro base stations that support one of three-dimensional (3D), full-dimensional (FD), or massive MIMO. Base stations 105a-105c utilize their higher-dimensional MIMO capabilities to increase coverage and capacity by utilizing 3D beamforming in elevation and azimuth beamforming. Base station 105f is a small cell base station, which can be a home node or a portable access point. The base station can support one or more (e.g., two, three, four, etc.) cells.

[0037] The 5G network 100 may support synchronous or asynchronous operation. For synchronous operation, the base stations may have similar frame timing, and transmissions from different base stations may be approximately aligned in time. For asynchronous operation, the base stations may have different frame timing, and transmissions from different base stations may not be aligned in time.

[0038] UE 115 is scattered throughout the wireless network 100, and each UE can be fixed or mobile. UE can also be referred to as a terminal, a mobile station, a subscriber unit, a station, etc. UE can be a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop computer, a cordless phone, a wireless local loop (WLL) station, etc. In one aspect, the UE can be a device including a universal integrated circuit card (UICC). In another aspect, the UE can be a device that does not include a UICC. In some aspects, a UE that does not include a UICC can also be referred to as an Internet of Everything (IoE) or Internet of Things (IoT) device. UE 115a-115d is an example of a mobile smart phone type device that accesses the 5G network 100. UE can also be a machine specially configured for connecting communications, including machine type communications (MTC), enhanced MTC (eMTC), narrowband Internet of Things (NB-IoT), etc. UE 115e-115k is an example of various machines configured for communication of accessing the 5G network 100. The UE can communicate with any type of base station, whether it is a macro base station, a small cell or similar base station. Figure 1 , a lightning icon (eg, a communication link) indicates wireless transmission between a UE and a serving base station that is a base station designated to serve the UE on a downlink and / or uplink, or desired transmission between base stations, and backhaul transmission between base stations.

[0039] In operation of the 5G network 100, base stations 105a-105c use 3D beamforming and collaborative spatial techniques (e.g., coordinated multipoint (CoMP) or multi-connectivity) to serve UEs 115a and 115b. Macro base station 105d performs backhaul communications with base stations 105a-105c and small cell base station 105f. Macro base station 105d also transmits multicast services subscribed to and received by UEs 115c and 115d. Such multicast services may include mobile TV or streaming video, or may include other services for providing community information, such as weather emergencies or alerts, such as missing child alerts or violent patient alerts.

[0040] The 5G network 100 also supports mission-critical communications with ultra-reliable and redundant links for mission-critical devices, such as UE 115e as a drone. The redundant communication links with UE 115e include links from macro base stations 105d and 105e and small cell base station 105f. Other machine-type devices, such as UE 115f (thermometer), UE 115g (smart meter), and UE 115h (wearable device), can communicate directly with base stations such as small cell base station 105f and macro base station 105e through the 5G network 100, or communicate in a multi-hop configuration by communicating with another user device that relays its information to the network, such as UE 115f transmitting temperature measurement information to smart meter UE 115g, which then reports the information to the network through small cell base station 105f. The 5G network 100 may also provide additional network efficiencies through dynamic, low-latency TDD / FDD communications, such as in a vehicle-to-vehicle (V2V) mesh network between UEs 1151 - 115k communicating with a macro base station 105e.

[0041] Figure 2 It shows that it can be Figure 1 1 is a block diagram of a design of a base station 105 of one of the base stations in the present invention and a UE 115 of one of the UEs. At the base station 105, a transmit processor 220 may receive data from a data source 212 and control information from a controller / processor 240. The control information may be for a PBCH, a PCFICH, a PHICH, a PDCCH, an EPDCCH, an MPDCCH, etc. The data may be for a PDSCH, etc. The transmit processor 220 may process (e.g., encode and symbol map) the data and the control information to obtain data symbols and control symbols, respectively. The transmit processor 220 may also generate reference symbols, such as for PSS, SSS, and a cell-specific reference signal. A transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, and / or reference symbols (if applicable), and may provide an output symbol stream to modulators (MODs) 232a to 232t. Each modulator 232 may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator 232 may further process (eg, convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The downlink signals from modulators 232a through 232t may be transmitted via antennas 234a through 234t, respectively.

[0042] At the UE 115, antennas 252a to 252r may receive downlink signals from the base station 105 and may provide received signals to demodulators (DEMODs) 254a to 254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) a corresponding received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 256 may obtain received symbols from all demodulators 254a to 254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 258 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 115 to a data sink 260, and provide decoded control information to a controller / processor 280.

[0043] On the uplink, at the UE 115, a transmit processor 264 may receive and process data from a data source 262 (e.g., for PUSCH) and control information from a controller / processor 280 (e.g., for PUCCH). The transmit processor 264 may also generate reference symbols for reference signals. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266, if applicable, further processed by modulators 254a through 254r (e.g., for SC-FDM, etc.), and transmitted to the base station 105. At the base station 105, the uplink signals from the UE 115 may be received by the antennas 234, processed by the demodulators 232, detected by the MIMO detector 236 (if applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 115. The processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240.

[0044] The controller / processors 240 and 280 may direct the operation at the base station 105 and the UE 115, respectively. The controller / processor 240 and / or other processors and modules at the base station 105 may perform or direct the execution of various processes for the techniques described herein. The controller / processor 280 and / or other processors and modules at the UE 115 may also perform or direct the execution of various processes for the techniques described herein. Figure 7 and Figure 8 , and / or other processes of the techniques described herein. Memories 242 and 282 may store data and program codes for base station 105 and UE 115, respectively. Scheduler 244 may schedule UEs for data transmission on downlink and / or uplink.

[0045] Wireless communication systems operated by different network operating entities (e.g., network operators) may share spectrum. In some cases, a network operating entity may be configured to use the entire designated shared spectrum for at least a period of time before another network operating entity uses the entire designated shared spectrum at a different time period. Therefore, in order to allow the network operating entity to use the entire designated shared spectrum, and to mitigate interfering communications between different network operating entities, certain resources (e.g., time) may be divided and allocated to different network operating entities for certain types of communications.

[0046] For example, a network operating entity may be allocated certain time resources that are reserved for dedicated communications by the network operating entity using the entire shared spectrum. A network operating entity may also be allocated other time resources where the entity is given a higher priority than other network operating entities to use the shared spectrum for communications. If the prioritized network operating entity does not utilize these resources, the time resources prioritized for use by the network operating entity may be utilized by other network operating entities on an opportunistic basis. Additional time resources may be allocated to any network operator for use on an opportunistic basis.

[0047] Access to the shared spectrum and arbitration of time resources between different network operating entities may be centrally controlled by a separate entity, autonomously determined by a predefined arbitration scheme, or dynamically determined based on interactions between wireless nodes of the network operator.

[0048] In some cases, 5G network 100 ( Figure 1A UE 115 and a base station 105 (in a shared radio spectrum band) may operate in a shared radio spectrum band, which may include licensed or unlicensed (e.g., contention-based) spectrum. In the unlicensed frequency portion of the shared radio spectrum band, the UE 115 or base station 105 may conventionally perform a medium sensing process to compete for access to the spectrum. For example, the UE 115 or base station 105 may perform a listen-before-talk (LBT) process, such as a clear channel assessment (CCA), before communicating to determine whether the shared channel is available. CCA may include an energy detection process to determine whether there are any other active transmissions. For example, a device may infer that a change in a received signal strength indicator (RSSI) of a power meter indicates that the channel is occupied. Specifically, a signal power concentrated in a certain bandwidth and exceeding a predetermined noise floor may indicate another wireless transmitter. CCA may also include detection of a specific sequence indicating channel usage. For example, another device may send a specific preamble before sending a data sequence. In some cases, the LBT process may include the wireless node adjusting its own backoff window based on the amount of energy detected on the channel and / or acknowledgement / negative acknowledgement (ACK / NACK) feedback for its own transmitted packets as a proxy for collisions.

[0049] Generally speaking, four categories of LBT procedures have been proposed to sense a shared channel for signals that may indicate that the channel is already occupied. In the first category (CAT 1LBT), no LBT or CCA is applied to detect occupancy of a shared channel. The second category (CAT 2LBT), which may also be referred to as simplified LBT, single-shot LBT, or 25-μs LBT, specifies that a node performs CCA to detect energy above a predetermined threshold or to detect a message or preamble occupying a shared channel. CAT 2LBT performs CCA without using a random backoff operation, which results in its length being shortened relative to the next category.

[0050] The third category (CAT 3LBT) performs CCA to detect energy or messages on a shared channel, but also uses random backoffs and fixed contention windows. Therefore, when a node starts CAT 3LBT, it performs a first CCA to detect occupancy of the shared channel. If the shared channel is idle for the duration of the first CCA, the node can continue to send. However, if the first CCA detects that the signal occupies the shared channel, the node selects a random backoff based on a fixed contention window size and performs an extended CCA. If the shared channel is detected to be idle during the extended CCA and the random number has been decremented to 0, the node can start transmitting on the shared channel. Otherwise, the node decrements the random number and performs another extended CCA. The node will continue to perform extended CCAs until the random number reaches 0. If the random number reaches 0 without any extended CCAs detecting channel occupancy, the node can send on the shared channel. If in any extended CCA, the node detects channel occupancy, the node can reselect a new random backoff based on a fixed contention window size to start the countdown again.

[0051] The fourth category (CAT 4LBT), which may also be referred to as a full LBT process, uses random backoff and a variable contention window size to perform CCA with energy or message detection. The order of CCA detection is similar to that of the CAT 3LBT process, except that the contention window size is variable for the CAT 4LBT process.

[0052] Using a medium sensing process to compete for access to an unlicensed shared spectrum may result in inefficient communications. This may be particularly evident when multiple network operating entities (e.g., network operators) attempt to access shared resources. In a 5G network 100, base stations 105 and UEs 115 may be operated by the same or different network operating entities. In some examples, a single base station 105 or UE 115 may be operated by more than one network operating entity. In other examples, each base station 105 and UE 115 may be operated by a single network operating entity. Requiring each base station 105 and UE 115 of different network operating entities to compete for shared resources may result in increased signaling overhead and communication delays.

[0053] Figure 3A , Figure 3B and Figure 3C An example of PUR (preconfigured uplink resource) or preconfigured PUSCH resource configuration and usage operation is shown. Figure 3A and Figure 3B The PUR configuration and operation are shown in Figure 3C , an example diagram illustrating a PUR configuration setup is shown.

[0054] The UE usually generates only a small amount of data on a burst in a data session. This type of data traffic may occur in all verticals including mobile broadband (MBB) and IoT. Examples of such small data bursts include data bursts for instant messaging software, social media software, wearable IoT devices, etc. It is beneficial for the network to allow the UE to send mobile originating (MO) uplink small data in the RRC_INACTIVE state without the UE having to transition to the RRC_CONNECTED state.

[0055] For example, the network may enable transmission of uplink data on preconfigured PUSCH resources in the RRC_INACTIVE state under certain conditions, such as when the timing advance (TA) value is valid. For illustration, a TA timer may be used to track the validity of the TA value, which may indicate that the uplink timing setting is valid.

[0056] The network (e.g., eNB or gNB) configures dedicated pre-configured uplink resources for the UE (or its data radio bearer (DRB)) via RRC dedicated signaling. Figure 3A in RRC_INACTIVE mode (e.g. Figure 3B ), such signaling can occur.

[0057] In the RRC_INACTIVE state, if the UE has small data to send and it has valid settings (such as valid uplink timing settings), it can request one or more small data transmissions without transitioning to the RRC connected state.

[0058] The UE may then send small data (ie, small data transmission) via the PUR configuration. After the UE transmits over the configured PUR, it monitors the PUR search space for a response from the network.

[0059] For NRUL small data transmission, when the first uplink small data is transmitted via a 2-step / 4-step random access channel (RACH) procedure, preconfigured uplink resources can be configured to the UE for subsequent uplink data transmission. The UE receives the preconfigured uplink resource configuration and sends subsequent UL packets in the preconfigured resources without entering RRC_CONNECTED mode. This has the benefit of saving power by keeping the UE in RRC_INACTIVE state for subsequent data transmission without entering RRC_CONNECTED.

[0060] refer to Figure 3A, showing a ladder diagram of a UE, a base station, and a user plane function (UPF). Prior to step 1, the UE is in an RRC connected state. In step 1, a base station (e.g., a gNB) sends an RRC release message. The RRC release message includes or corresponds to an RRC message, and may optionally include release clause information (e.g., releaseClause), next hop parameter (NH) link counter (NCC) information, and PUR configuration information (e.g., pre-configured PUSCH resource information). The RRC release message may be generated in response to the base station determining to transition the UE to an RRC inactive state.

[0061] In response to receiving the RRC release message, the UE transitions from the RRC connected state to the RRC inactive state, as shown before step 2. In step 2, the UE sends an RRC resume request message. The RRC resume request message includes or corresponds to an RRC message and may optionally be sent together with uplink data (such as a small data transmission sent according to the PUR configuration of the RRC release message).

[0062] In step 3, the base station (e.g., gNB) sends a second RRC release message. The second RRC release message includes or corresponds to an RRC message, and may optionally include release clause information (e.g., releaseClause), resumption information (e.g., resumeID), next hop parameter (NH) link counter (NCC) information. Compared with the RRC release message of step 1 (e.g., the first RRC release message), the second RRC release message may include resumption information and may not include PUR configuration information because such PUR configuration information was previously sent in step 1.

[0063] Between steps 2 and 3, the base station may send uplink data received from the UE to the UPF. After step 3, the UPF may send downlink data to the base station (e.g., gNB); the base station may send downlink data to the UE. Figure 3A As shown, after using a specific PUR resource (eg, sending uplink data in step 2), the UE monitors the search space (eg, USS) configured by the PUR.

[0064] refer to Figure 3B , shows a ladder diagram of a UE, a base station, and a user plane function (UPF). Before step 1, the UE is in an RRC inactive state. In step 1, the UE sends a random access preamble message, i.e., a RACH preamble message (e.g., message 1). The RACH preamble message may include or correspond to an RRC message.

[0065] In step 2, the base station (e.g., gNB) sends a random access response message, i.e., a RACH response message (e.g., message 2). The RACH response message may include or correspond to an RRC message.

[0066] In step 3, the UE sends an RRC recovery request message (eg, message 3). The RRC recovery request message includes or corresponds to an RRC message, and may be optionally sent together with uplink data (such as small data transmission).

[0067] In step 4, the base station (e.g., gNB) sends an RRC release message (e.g., message 4). The RRC release message includes or corresponds to an RRC message, and may optionally include release clause information (releaseClause), resume information (e.g., resumeID), next hop parameter (NH) link counter (NCC) information, and PUR configuration information (e.g., pre-configured PUSCH resources).

[0068] In step 5, the UE may optionally use the PUR configuration and its resources to send subsequent uplink data, small data transmission. Between steps 3 and 4, the base station may send uplink data from the UE to the UPF. Between steps 4 and 5, the UPF may send downlink data to the base station (e.g., gNB); the base station may send downlink to the UE. After step 5, the base station may send subsequent uplink data from the UE to the UPF.

[0069] like Figure 3B As shown, after receiving a specific PUR configuration (eg, receiving an RRC release message with PUR configuration information in step 4), the UE monitors the search space (eg, USS) of the PUR configuration.

[0070] refer to Figure 3C , a diagram showing the transmission opportunities for a particular PUR configuration. Figure 3C In FIG. 1 , three PUR transmission opportunities (also referred to as PUR opportunities) are shown. A PUR opportunity may include one or more PUR transmission opportunities. Figure 3C In the example of , each PUR opportunity includes three PUR transmission opportunities (also referred to as PUR opportunities). In addition, each opportunity and opportunity may occur at a specific timing or have a specific timing, such as a cycle. Figure 3C The PUR period between the second PUR opportunity and the third PUR opportunity is shown. Figure 3C The PUR period in is the PUR opportunity period, and indicates the duration from the start of one PUR opportunity (i.e., the start of the first PUR opportunity or the only PUR opportunity of a PUR opportunity) to the start of another subsequent PUR opportunity (i.e., the start of the first PUR opportunity or the only PUR opportunity of a PUR opportunity).

[0071] In some implementations where the opportunity includes multiple opportunities, the UE or the network may decide which opportunity to use. Figure 3C In the example of , the UE determines to use the first transmission opportunity of each opportunity based on the synchronization signal block (SSB) condition. For illustration, each transmission opportunity can be associated with a specific SSB, so the UE can determine which opportunity to use based on determining which SSB to use. The UE can maintain such an opportunity for each opportunity, or can change the opportunity, such as when the UE decides to switch / use another SSB.

[0072] As an illustrative example, UE 115 may measure the reference signal received power (RSRP) of the candidate SSBs. UE 115 determines and selects an SSB among the candidate SSBs whose RSRP is above a threshold (such as Trsrp). UE 115 may then send data on the first available PUR opportunity associated with the selected SSB.

[0073] Then, the UE 115 monitors the response of the network after sending data through the PUR opportunity. For example, the UE monitors the search space configured by the PDCCH on the monitoring opportunity of the quasi co-location (QCL) with its selected SSB. Then, when the monitoring starts, the UE can start the retransmission timer.

[0074] If the UE does not receive any message (such as DCI) from the network when the retransmission timer expires, the UE switches to RACH-based small data transmission. Otherwise, the UE follows the normal dynamic grant / allocation process according to the scheduling of the NW.

[0075] Figure 4 An example of a wireless communication system 400 supporting PUR configuration and release operations according to aspects of the present disclosure is shown. In some examples, the wireless communication system 400 can implement aspects of the wireless communication system 100. For example, the wireless communication system 400 may include a UE 115 and a network entity 405. The PUR configuration and release operations can reduce power consumption and network switching by enabling the UE to send data in an RRC inactive state. Therefore, network and device performance can be improved.

[0076] The network entity 405 and the UE 115 may be configured to communicate via a frequency band, such as FR1 having a frequency of 410 to 7125 MHz, FR2 having a frequency of 24250 to 52600 MHz for millimeter wave, and / or one or more other frequency bands. Note that for some data channels, the SCS may be equal to 15, 30, 60, or 120 kHz. The network entity 405 and the UE 115 may be configured to communicate via one or more component carriers (CCs), such as a representative first CC 481, a second CC 482, a third CC 483, and a fourth CC 484. Although four CCs are shown, this is for illustration only, and more or less than four CCs may be used. One or more CCs may be used to communicate control channel transmissions, data channel transmissions, and / or sidelink channel transmissions.

[0077] Such transmissions may include a physical downlink control channel (PDCCH), a physical downlink shared channel (PDSCH), a physical uplink control channel (PUCCH), a physical uplink shared channel (PUSCH), a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), or a physical sidelink feedback channel (PSFCH). Such transmissions may be scheduled by aperiodic grants and / or periodic grants.

[0078] Each periodic grant may have a corresponding configuration, such as configuration parameters / settings. The periodic grant configuration may include a configuration grant (CG) configuration and settings. Additionally or alternatively, one or more periodic grants (e.g., their CGs) may have or be assigned a CC ID, such as an expected CC ID.

[0079] Each CC may have a corresponding configuration, such as a configuration parameter / setting. The configuration may include bandwidth, bandwidth portion, HARQ process, TCI state, RS, control channel resources, data channel resources, or a combination thereof. Additionally or alternatively, one or more CCs may have or be assigned a cell ID, a bandwidth portion (BWP) ID, or both. The cell ID may include a unique cell ID of the CC, a virtual cell ID, or a specific cell ID of a specific CC in multiple CCs. Additionally or alternatively, one or more CCs may have or be assigned a HARQ ID. Each CC may also have corresponding management functions, such as beam management, BWP switching functions, or both. In some implementations, two or more CCs are quasi-co-located so that the CCs have the same beam and / or the same symbol.

[0080] In some implementations, the control information may be communicated via the network entity 405 and the UE 115. For example, the control information may be communicated using a MAC-CE transmission, an RRC transmission, a DCI transmission, another transmission, or a combination thereof.

[0081] The UE 115 may include various components (e.g., structures, hardware components) for performing one or more functions described herein. For example, these components may include a processor 402, a memory 404, a transmitter 410, a receiver 412, an encoder 413, a decoder 414, a PUR manager 415, a small data transmission manager 416, and antennas 252a-r. The processor 402 may be configured to execute instructions stored at the memory 404 to perform the operations described herein. In some implementations, the processor 402 includes or corresponds to the controller / processor 280, and the memory 404 includes or corresponds to the memory 282. The memory 404 may also be configured to store trigger condition data 406, PUR configuration data 408, small transmission data 442, setting data 444, or a combination thereof, as further described herein.

[0082] The trigger condition data 406 includes or corresponds to data associated with or corresponding to the PUR configuration release trigger condition information. For example, the trigger condition data 406 may indicate one or more possible trigger conditions and / or one or more active trigger conditions. The trigger condition data 406 may also include a threshold value or data for evaluating the trigger condition, such as a condition for evaluating an inactive timer. In addition, the trigger condition data 406 may also include a threshold value or data for evaluating a trigger transmission condition, such as a DCI indication value 1 corresponding to releasing the PUR configuration.

[0083] The PUR configuration data 408 includes or corresponds to data indicating or corresponding to a PUR configuration for small data transmission. For example, the PUR configuration data 408 may include possible PUR configurations, active (e.g., currently used) PUR configurations, default PUR configurations, requested PUR configurations, received PUR configurations, or combinations thereof. The PUR configuration data 408 may indicate the number of transmission opportunities, the number of transmission opportunities per opportunity, the period of opportunities, the period of opportunities, or the period of both. The indicated PUR configuration may be for each UE or each data radio bearer (DRB). In some implementations, the PUR configuration data 408 may further indicate a PUSCH configuration or setting.

[0084] Small transmission data 442 includes or corresponds to data associated with small data transmissions. Small transmission data 442 may include short and / or small data bursts for MBB and IoT applications, such as data for instant messaging applications, social media applications, wearable devices (e.g., fitness trackers and monitors), etc. Small transmission data 442 may include data less than a threshold number of bytes, such as less than 10 bytes or less than 1000 bytes.

[0085] The setting data 444 includes or corresponds to data associated with PUR configuration and release operations. The setting data 444 may include one or more types of PUR configuration and release operation modes and / or thresholds or conditions for switching between PUR configuration and release modes and / or configurations. For example, the setting data 444 may have data indicating different thresholds for different PUR release modes, such as a UE-initiated PUR configuration release mode and a network-initiated PUR configuration release.

[0086] The transmitter 410 is configured to send data to one or more other devices, and the receiver 412 is configured to receive data from one or more other devices. For example, the transmitter 410 can send data and the receiver 412 can receive data via a network (such as a wired network, a wireless network, or a combination thereof). For example, the UE 115 can be configured to send and / or receive data via a direct device-to-device connection, a local area network (LAN), a wide area network (WAN), a modem-to-modem connection, the Internet, an intranet, an extranet, a cable transmission system, a cellular communication network, any combination of the above, or any other communication network now known or later developed that allows two or more electronic devices to communicate therein. In some implementations, the transmitter 410 and the receiver 412 can be replaced with a transceiver. Additionally or alternatively, the transmitter 410, the receiver 412, or both may include or correspond to reference Figure 2 One or more components of UE 115 are described.

[0087] Encoder 413 and decoder 414 can be configured to encode and decode data for transmission. PUR manager 415 can be configured to determine and perform PUR management operations, such as configuration and release operations. For example, PUR manager 415 is configured to determine and implement received PUR configuration. As another example, PUR manager 415 is configured to determine a specific PUR configuration release trigger, and releases a specific PUR configuration in response to a specific PUR configuration release trigger. Optionally, in such an implementation, PUR manager 415 can send a PUR configuration release request message to the network. In addition, in some implementations, PUR manager 415 can also be configured to request a specific PUR configuration before receiving the PUR configuration from the network.

[0088] The small data transfer manager 416 can be configured to determine and perform small data transfer management operations. For example, the small data transfer manager 416 can be configured to determine data for a small data transfer and generate a small data transfer.

[0089] The network entity 405 includes a processor 430, a memory 432, a transmitter 434, a receiver 436, an encoder 437, a decoder 438, a PUR manager 439, a small data transmission manager 440, and antennas 234a-t. The processor 430 may be configured to execute instructions stored at the memory 432 to perform the operations described herein. In some implementations, the processor 430 includes or corresponds to the controller / processor 240, and the memory 432 includes or corresponds to the memory 242. The memory 432 may be configured to store the trigger condition data 406, the PUR configuration data 408, the small transmission data 442, the setting data 444, or a combination thereof, similar to the UE 115 and as further described herein.

[0090] The transmitter 434 is configured to send data to one or more other devices, and the receiver 436 is configured to receive data from one or more other devices. For example, the transmitter 434 can send data and the receiver 436 can receive data via a network (such as a wired network, a wireless network, or a combination thereof). For example, the network entity 405 can be configured to send and / or receive data via a direct device-to-device connection, a local area network (LAN), a wide area network (WAN), a modem-to-modem connection, the Internet, an intranet, an extranet, a cable transmission system, a cellular communication network, any combination of the above, or any other communication network now known or later developed that allows two or more electronic devices to communicate therein. In some implementations, the transmitter 434 and the receiver 436 can be replaced with a transceiver. Additionally or alternatively, the transmitter 434, the receiver 436, or both may include or correspond to reference Figure 2 One or more components of network entity 405 are described.

[0091] Encoder 437 and decoder 438 may include the same functionality described with reference to encoder 413 and decoder 414, respectively. PUR manager 439 may include similar functionality described with reference to PUR manager 415. Small data transfer manager 440 may include similar functionality described with reference to small data transfer manager 416.

[0092] During operation of the wireless communication system 400, the network entity 405 may determine that the UE 115 has PUR configuration and release capabilities. For example, the UE 115 may send a message 448 including a PUR configuration and / or release indicator 490 (e.g., a PUR configuration and release indicator). The indicator 490 may indicate the PUR configuration and release operation capability or a specific type or mode of PUR configuration and release operation. In some implementations, the network entity 405 sends control information to indicate to the UE 115 that the PUR configuration and release operation and / or a specific type of PUR configuration and release operation will be used. For example, in some implementations, the message 448 (or another message, such as a configuration transmission 450) is sent by the network entity 405. The configuration transmission 450 may include or indicate the use of the PUR configuration and release operation, or adjust or implement settings for a specific type of PUR configuration and release operation.

[0093] During operation, the devices of the wireless communication system 400 perform PUR configuration and release operations. For example, the network entity 405 and the UE 115 exchange transmissions to set a specific PUR configuration. Such transmissions may include or correspond to Figure 3A and Figure 3B The RRC transmission shown in Figure 4 In the example of FIG. 4 , the network entity 405 sends a PUR configuration message 452 to the UE 115. The PUR configuration message 452 may include or indicate a specific PUR configuration or multiple PUR configurations (e.g., PUR configuration data 408). For illustration, the network entity 405 may send an RRC message indicating a PUR configuration, such as an RRC release message. As another illustration, the network entity 405 may send an RRC message including multiple PUR configurations, such as multiple PUR configurations per DRB for a single UE.

[0094] The indicated PUR configuration may include the number of transmission opportunities, the number of transmission opportunities per transmission opportunity, the period of transmission opportunities and / or opportunities, or a combination thereof. The PUR configuration may also indicate one or more release conditions (e.g., trigger release data 406), which may be active or applicable. Satisfying one or more such release conditions will cause the UE and / or network to initiate the release of the PUR configuration. The PUR configuration may also indicate whether the PUR configuration is for the UE 115, or for a DRB of the UE 115 or a DRB associated with the UE 115. By using a per-DRB PUR configuration, the UE 115 may be configured with multiple PUR configurations with different settings.

[0095] The network entity 405 and / or the UE 115 may optionally perform one or more small data transmissions 454 using the PUR configuration included in or indicated by the PUR configuration message 452. For example, the UE 115 may send multiple small data transmissions.

[0096] The network entity 405 and / or the UE 115 may determine to release the PUR configuration to more efficiently use the network spectrum (eg, not waste unused spectrum dedicated solely to the UE 115).

[0097] For example, UE 115 may determine that PUR configuration release conditions are met and may send a release request message 456 to network entity 405 to instruct network entity 405 to release the PUR configuration. To illustrate, UE 115 may send an RRC or MAC CE transmission to indicate and / or request a PUR configuration release.

[0098] As another example, both the network entity 405 and the UE 115 may determine that a PUR configuration release condition is met. In such a case, signaling may not be required (e.g., a release request message 456 is not required or sent) because both the network entity 405 and the UE 115 monitor the condition and release the PUR configuration when the specific PUR configuration release condition is met.

[0099] Alternatively, the network entity 405 may determine that the PUR configuration release condition is satisfied, and may send a release message 458 to the UE 115 to instruct the UE to release the PUR configuration. In addition, the network entity 405 may send a release message 458 to the UE 115 in response to receiving the release request message 456 to confirm to the UE 115 that the PUR configuration is released. Examples of such PUR configuration release conditions include UE-based triggers, network-based triggers, or both. Some examples of UE-based triggers include a TA timer, a number of PUR transmission opportunity conditions, a UE-based trigger signal, a RACH process condition, or an LBT failure condition. Some examples of UE network triggers include a network-configured timer, a network-configured counter, or a network-sent trigger signal.

[0100] During the above operations, UE 115 may remain in RRC inactive mode. In other implementations, UE 115 may determine to switch RRC connected mode to perform data transmission, such as when no PUR configuration is received, no PUR configuration is active, or UE 115 has a larger amount of data to send.

[0101] In some such implementations, the UE 115 may perform a RACH operation to send data. For example, if the UE 115 does not receive a dynamic grant (to establish a PUR configuration), the UE 115 may perform a RACH operation and send data during one or more RACH messages. For illustration, in a two-step RACH process, the UE 115 may send data (e.g., small data) during or with message A, or for a four-step RACH process, may send data (e.g., small data) during or with message 3.

[0102] Therefore, UE 115 and network entity 405 can configure and release PUR configuration more efficiently. Figure 4 Enhanced PUR configuration and release operations are described. Using the enhanced PUR configuration and release operations can achieve improvements, such as power savings, when operating with less advanced hardware. Performing the enhanced PUR configuration and release operations can reduce bandwidth / spectrum waste when performing small data transmissions, thereby enhancing UE and network performance by increasing throughput and reducing latency.

[0103] Figure 5 and Figure 6 An example of a ladder diagram showing the PUR configuration and release operation. Figure 5 , Figure 5 is a step diagram 500 of PUR configuration and release operations based on a UE or UE-initiated PUR configuration release. Figure 5 In the example of , the ladder diagram shows a UE and a network entity, such as a base station 105.

[0104] At 510, the UE 115 generates and sends a PUR request message to the base station 105 (e.g., gNB). For example, the UE 115 sends an RRC, PUCCH, or PUSCH transmission to the base station 105 requesting establishment of a PUR configuration. In some implementations, the UE 115 may also include or indicate the requested PUR configuration. For example, the UE 115 may include or indicate a particular PUR configuration or one or more settings of the PUR configuration, such as the number of transmit opportunities and / or opportunities, the periodicity, the type of configuration (e.g., per UE or per DRB), or a combination thereof. Additionally, the UE 115 may request to enter an RRC inactive state in the PUR request message. Alternatively, the UE 115 may already be in an RRC inactive state, such as Figure 3A As shown, or may be in the RRC connected state and later transition to the RRC inactive state.

[0105] At 515, the base station 105 (e.g., gNB) generates and sends a PUR request configuration message including or indicating a PUR configuration. For example, the base station 105 sends an RRC message, such as an RRC release message, to the UE 115 with the PUR configuration. For example, the UE 115 may include or indicate a particular PUR configuration or one or more settings of the PUR configuration, such as the number, period, or combination thereof of transmission opportunities and / or occasions. In addition, the PUR configuration may indicate whether it is a per-UE PUR configuration or a per-DRB PUR configuration. The PUR configuration message (e.g., an RRC release message) may also be configured to transition the UE 115 from the RRC connected state to the RRC inactive state.

[0106] From 520 to 525, the UE 115 may optionally generate one or more small data transmissions and send the one or more small data transmissions to the base station 105 using the PUR configuration received in the PUR configuration message. For example, the UE 115 may send one or more PUSCH transmissions to the base station 105. Figure 5 As shown in the example of , UE 115 sends a first small data transmission and a second small data transmission to base station 105. The first small data transmission and the second small data transmission may occur in consecutive or non-consecutive transmission opportunities and / or chances.

[0107] In addition, after sending and setting the PUR configuration at 515, the UE 115 and optionally the base station 105 can track one or more metrics for determining whether the PUR configuration should be released. For example, the UE 115 and the base station 105 can track the number of consecutive missed opportunities and / or chances, such as by using a counter. As another example, the UE 115 and the base station 105 can set one or more timers, such as a TA timer or a PUR timer. In addition, the UE 115 can monitor whether it has completed its known or allocated small data transmission, such as by reaching the number of configured transmission opportunities and / or opportunities, or whether the previously identified small data amount to be transmitted has been communicated.

[0108] At 530, UE 115 determines a release trigger for a specific PUR configuration. For example, UE 115 may determine to release the PUR configuration based on one or more conditions. These conditions include reaching the number of configured transmission opportunities or opportunities, satisfying a timer condition (e.g., a TA timer condition), satisfying a counter condition, satisfying a small data transmission condition, etc.

[0109] In some implementations, the PUR configuration release trigger condition is based on a TA timer, such as a new TA timer. For example, the UE 115 may set a TA timer based on the PUR configuration and start a new TA timer in response to switching to the RRC inactive state. The UE 115 may determine whether the new TA timer has expired and determine to release the PUR configuration based on determining that the new TA timer has expired. In some such implementations, the expiration of the TA timer indicates that the uplink transmission is out of sync.

[0110] In some other implementations, the PUR configuration release trigger condition is based on reaching the number of PUR configurations (e.g., the number of allocated opportunities). For example, the UE 115 determines the number of allocated PUR transmission opportunities based on the PUR configuration and monitors the number of PUR transmission opportunities that have passed. The UE 115 can then compare the number of allocated PUR transmission opportunities with the number of PUR transmission opportunities that have passed to determine whether the number of allocated PUR transmission opportunities has been reached.

[0111] In some other implementations, the PUR configuration release trigger condition is based on the state of one or more small data transmissions. For example, UE 115 can determine whether the small data transmission is completed, and in response to determining that the small data transmission is completed, a PUR release request message is generated. In such an implementation, UE 115 sends a PUR release request message to a network entity, and the PUR release request message is configured to indicate the release of the PUR configuration. In some aspects, the PUR release request message includes or corresponds to a MAC CE. The MAC CE can be a fixed size. In one implementation, the MAC CE has a certain size of zero bits (asize of zero bits). In addition, the MAC CE can have a new logical channel ID (LCID). The MAC CE can include or correspond to a data request MAC CE for requesting uplink resource allocation for small data transmission. Alternatively, the MAC CE can be a re-planned or reused MAC CE, such as a small data request MAC CE. In a specific implementation, the small data request MAC CE can include a special value indicating release, such as a traffic pattern indication element set to zero. In other aspects, the PUR release request message includes or corresponds to an RRC message.

[0112] In some other implementations, the PUR configuration release trigger condition is based on a retransmission timer. UE 115 may be configured to switch to a RACH process for small data transmission based on a retransmission timer and / or based on one or more other conditions. For example, UE 115 may start a retransmission timer and, in response to the expiration of the retransmission timer, switch to a RACH process for small data transmission. UE 115 may then send the small data transmission in message A or message 3. When switching to a two-step RACH process, UE 115 may use message A (MSA), and when switching to a four-step RACH process, UE 115 may use message 3 (msg3).

[0113] In some other implementations, the PUR configuration release trigger condition is based on the LBT counter. For example, UE 115 can start the LBT failure counter based on the PUR configuration message. UE 115 can increment the LBT failure counter based on each LBT failure, and reset the LBT failure counter based on LBT success. Then, UE 115 determines to release the PUR configuration release based on the LBT failure counter meeting the continuous LBT failure number condition. UE 115 can optionally generate a PUR configuration release request message based on the LBT failure counter meeting the continuous LBT failure number condition. For example, base station 105 may not be able to track (or accurately track) the LBT success and / or failure of UE 115, so UE 115 can notify the network of such a situation.

[0114] At 535, the base station 105 may optionally determine a specific PUR configuration release trigger. For example, the base station 105 may determine to release the PUR configuration based on one or more conditions. Such conditions may include similar conditions evaluated by the UE 115, and optionally, conditions of interest to other base stations 105.

[0115] At 540, the UE 115 optionally generates and sends a PUR release request message to indicate or signal the release of the specific PUR configuration. For example, when the triggering condition is based on the UE or UE initiated condition, or when the base station 105 does not monitor the specific PUR configuration release condition, the UE 115 sends an RRC message or a MAC CE to indicate the release of the specific PUR configuration.

[0116] At 545, the base station 105 may optionally determine to release a particular PUR configuration in response to receiving the PUR release request message. For example, the base station 105 may determine to release the PUR configuration based on an indication or request in the PUR release request message to release the PUR configuration.

[0117] At 550, the base station 105 generates and sends a PUR release message. For example, the base station 105 sends an RRC release message to the UE 115, which is configured to initiate or confirm the actual release of the PUR configuration. In response to communicating the PUR release message, the UE 115 and the base station 105 may release the PUR configuration settings and stop operating according to the PUR configuration settings. The base station 105 and the UE 115 may then attempt to establish another PUR configuration in a similar or other manner. Additionally or alternatively, the UE 115 and the base station 105 may operate according to another PUR configuration, such as a default PUR configuration or another PUR configuration that was previously established and is still active (e.g., not released by the above-mentioned release message). Although not in Figure 5 , but UE 115 may send an optional confirmation message for the PUR release message.

[0118] Therefore, in Figure 5 In the example of , the device performs UE-based PUR configuration and release operations. That is, the UE can make a determination without signaling and optionally notify the network to release the PUR configuration, which achieves enhanced release operations and reduced spectrum waste.

[0119] refer to Figure 6 , Figure 6 is a step-by-step diagram of the PUR configuration and release operations. Figure 6 In the example of FIG. 1 , the ladder diagram shows a UE and a network entity, such as a base station 105. Figure 5 Compared with the UE-based or UE-initiated PUR configuration release in the step diagram, Figure 6 The ladder diagram illustrates the PUR configuration and release operations of a network-based or network-initiated PUR configuration release.

[0120] At 610, the UE 115 generates and sends a PUR request message to the base station 105 (e.g., gNB). For example, the UE 115 sends an RRC, PUCCH, or PUSCH transmission to the base station 105 requesting establishment of a PUR configuration. In some implementations, the UE 115 may also include or indicate the requested PUR configuration. For example, the UE 115 may include or indicate a particular PUR configuration or one or more settings of the PUR configuration, such as the number of transmit opportunities and / or opportunities, the periodicity, the type of configuration (e.g., per UE or per DRB), or a combination thereof. Additionally, the UE 115 may request to enter an RRC inactive state in the PUR request message. Alternatively, the UE 115 may already be in an RRC inactive state, such as Figure 3A As shown, or may be in the RRC connected state and later transition to the RRC inactive state.

[0121] At 615, the base station 105 (e.g., gNB) generates and sends a PUR request configuration message including or indicating a PUR configuration. For example, the base station 105 sends an RRC message, such as an RRC release message, to the UE 115 with the PUR configuration. For example, the UE 115 may include or indicate a particular PUR configuration or one or more settings of the PUR configuration, such as the number of transmit opportunities and / or opportunities, a periodicity, or a combination thereof. In addition, the PUR configuration may indicate that it is a per-UE PUR configuration or a per-DRB PUR configuration. The PUR configuration message (e.g., an RRC release message) may also be configured to transition the UE 115 from an RRC connected state to an RRC inactive state.

[0122] From 620 to 625, the UE 115 may optionally generate one or more small data transmissions and send the one or more small data transmissions to the base station 105 using the PUR configuration received in the PUR configuration message. For example, the UE 115 may send one or more PUSCH transmissions to the base station 105. Figure 5 As shown in the example of , UE 115 sends a first small data transmission and a second small data transmission to base station 105. The first small data transmission and the second small data transmission may occur in consecutive or non-consecutive transmission opportunities and / or chances.

[0123] In addition, after sending and setting the PUR configuration at 515, the base station 105 and optionally, the UE 115 can track one or more metrics for determining whether the PUR configuration should be released. For example, the base station 105 and the UE 115 can track the number of consecutive missed opportunities and / or opportunities, such as using a counter. As another example, the base station 105 and the UE 115 can set one or more timers, such as a TA timer or a PUR timer. In addition, the base station 105 can monitor whether the UE 115 has completed its assigned small data transmission, such as by reaching the number of configured transmission opportunities and / or opportunities, or whether the previously identified small data amount to be transmitted has been communicated.

[0124] At 630, the base station 105 determines a release trigger for a specific PUR configuration. For example, the base station 105 may determine to release the PUR configuration based on one or more conditions. These conditions include reaching the number of configured transmission opportunities or opportunities, satisfying a timer condition (e.g., a TA timer condition), satisfying a counter condition, satisfying a small data transmission condition, etc.

[0125] In some other implementations, the PUR configuration release trigger condition is based on a configuration timer. For example, the base station 105 starts the PUR configuration timer based on the first small data transmission, and resets the PUR configuration timer based on the subsequent small data transmission. As another example, the base station 105 starts the PUR configuration timer based on receiving a PUR configuration message, setting a PUR configuration, or converting an RRC state. The base station 105 generates a PUR configuration release message based on the expiration of the PUR configuration timer.

[0126] In some other implementations, the PUR configuration release trigger condition is based on a counter. For example, the base station 105 starts the PUR configuration counter based on the first small data transmission. The base station 105 increments the PUR configuration counter based on each unused PUR transmission opportunity and resets the PUR configuration counter based on the small data transmission. The base station 105 generates a PUR configuration release message based on the PUR configuration counter satisfying the number of consecutive unused transmission opportunities.

[0127] In some other implementations, the PUR configuration release trigger condition is based on the decision to revoke the PUR configuration. For example, the base station 105 may determine that a spectrum should be allocated to data or equipment of higher priority rather than the UE 115 and its data, and / or determine that the configuration or parameters of the UE and / or network have changed. In such an implementation, the base station 105 may send a PUR release message to the UE, and the PUR release message may be configured to indicate the release of the PUR configuration. For illustration, the base station 105 may determine to revoke the PUR configuration, and generate a PUR release message in response to determining to revoke the PUR configuration. The PUR release message may include or correspond to an RRC message.

[0128] At 635, UE 115 may optionally determine a specific PUR configuration release trigger. For example, UE 115 may determine to release the PUR configuration based on one or more conditions. Such conditions may include similar conditions evaluated by base station 105, and optionally, other conditions based on UE 115 or UE 115 concerns.

[0129] At 640, the base station 105 generates and sends a PUR release message. For example, the base station 105 sends an RRC release message to the UE 115, which is configured to initiate or confirm the actual release of the PUR configuration. In response to determining a specific PUR configuration release trigger at 630, the PUR release message is generated. In response to communicating the PUR release message, the UE 115 and the base station 105 can release the PUR configuration settings and stop operating according to the PUR configuration settings.

[0130] Instead of the UE 115 determining a specific PUR configuration release trigger at 635, the UE 115 may determine to release the specific PUR configuration based on and in response to receiving the PUR release message at 645. For example, the UE 115 may determine to release the PUR configuration based on an indication or request in the PUR release message to release the PUR configuration.

[0131] UE 115 optionally generates and sends a confirmation message for the PUR release message at 650. For example, UE 115 sends an RRC message, UCI, or MAC CE to base station 105, which is configured to confirm the receipt of the PUR release message and the actual release of the PUR configuration.

[0132] The base station 105 and the UE 115 may then attempt to establish another PUR configuration in a similar or other manner. Additionally or alternatively, the UE 115 and the base station 105 may operate according to another PUR configuration, such as a default PUR configuration or another PUR configuration that was previously established and is still active (e.g., not released by the above release message). In other implementations, the PUR release message may configure another PUR configuration, such as a PUR configuration with less bandwidth and / or spectrum allocated to the UE 115, or a PUR configuration with different time constraints.

[0133] Therefore, in Figure 6 In the example of , the device performs network-based PUR configuration and release operations. That is, the base station can make a determination without signaling and optionally notify the UE to release the PUR configuration, which achieves enhanced release operations and reduced spectrum waste.

[0134] Additionally or alternatively, in other implementations, you can add, delete, replace Figure 3A-Figure 6 For example, in some implementations, Figure 3A and Figure 3B For illustration, you can execute Figure 3B steps, and then at a later time, you can perform Figure 3A As another example, Figure 5 Some steps of UE-initiated release in Figure 6 Some steps of network-initiated release in Figure 3A or Figure 3B Used together with or added to the Figure 3A or Figure 3B in the steps.

[0135] Figure 7 is a flow chart illustrating example blocks executed by a UE configured according to one aspect of the present disclosure. Fig. 9 UE 115 is shown to describe the example blocks. Fig. 9 1 is a block diagram illustrating a UE 115 configured according to one aspect of the present disclosure. The UE 115 includes Figure 2 1. The structure, hardware, and components of the UE 115 shown in FIG. 1. For example, the UE 115 includes a controller / processor 280 that operates to execute logic or computer instructions stored in a memory 282 and controls the components of the UE 115 that provide the features and functions of the UE 115. Under the control of the controller / processor 280, the UE 115 sends and receives signals via wireless radios 900a-r and antennas 252a-r. The wireless radios 900a-r include various components and hardware, such as Figure 2 As shown for UE 115, it includes modulators / demodulators 254a-r, MIMO detector 256, receive processor 258, transmit processor 264 and TX MIMO processor 266. Fig. 9 As shown in the example, the memory 282 stores PUR configuration logic 902, PUR release logic 903, small data transmission logic 904, PUR release trigger data 905, small data 906, timer 907, counter 908 and setting data 909.

[0136] At block 700, a wireless communication device such as a UE receives a preconfigured uplink resource (PUR) configuration message indicating a PUR configuration for small data transmission. Figure 3A-Figure 6 As described, the UE 115 receives an RRC message including PUR configuration data indicating a PUR configuration for small data transmission. The PUR configuration data may indicate a PUR configuration indicator or index number, or may include data for settings of the PUR configuration, such as the number of transmission opportunities, the transmission opportunity of each opportunity, the period, the type of each configuration, etc., or a combination thereof. After the PUR configuration is set, the UE 115 may send small data transmission in the PUSCH resources configured and allocated by the PUR configuration.

[0137] At block 701, the UE 115 determines a PUR configuration release trigger for a PUR configuration. Figure 3A-Figure 6As described, UE 115 determines to release an active PUR configuration indicated by the network based on one or more UE-monitored release conditions. For illustration, UE 115 may set and monitor one or more counters and / or timers. As another illustration, UE 115 may monitor whether a PUR configuration has expired or whether a small data transfer has been completed. In some such implementations, UE 115 may send a message to the network to indicate that one or more release conditions have been met. For illustration, UE 115 may send a PUR configuration release request message, such as an RRC message. Alternatively, UE 115 may receive a release message from the network indicating that the PUR configuration is released based on some network-monitored conditions, such as reference Figure 8 described.

[0138] At block 702, the UE 115 receives a PUR configuration release message configured to release a PUR configuration. Figure 3A-Figure 6 As described, UE 115 receives an RRC message from the network indicating or confirming the release of the PUR configuration.

[0139] In other implementations, the UE 115 may perform additional blocks (or the UE 115 may be configured to further perform additional operations). For example, the UE 115 may perform one or more of the operations described above. As another example, the UE 115 may perform one or more operations as described below.

[0140] In a first aspect, before determining a PUR configuration release trigger: UE 115 receives one or more SSB transmissions; the UE selects a specific SSB from the one or more SSB transmissions; a specific PUR transmission opportunity is determined based on the selected SSB; and the UE sends a first small data based on the PUR configuration and using the specific transmission opportunity of the first PUR transmission opportunity.

[0141] In a second aspect, alone or in combination with one or more of the above aspects, the UE 115 transmits the second small data based on the PUR configuration and using a specific PUR transmission opportunity of the second PUR transmission opportunity.

[0142] In a third aspect, alone or in combination with one or more of the above aspects, the first PUR sending opportunity and the second PUR sending opportunity include PUSCH transmission opportunities, and wherein the UE is in an RRC inactive state when sending the first small data and the second small data.

[0143] In a fourth aspect, either alone or in combination with one or more of the above aspects, before receiving the PUR configuration message: UE 115 receives dedicated RRC signaling (e.g., an RRC release message) indicating a change in the RRC state; and the UE transitions from the RRC connected state to the RRC inactive state based on the dedicated signaling (e.g., the RRC release message).

[0144] In a fifth aspect, alone or in combination with one or more of the above aspects, prior to receiving the PUR configuration message: the UE 115 sends a RACH preamble message; and receives a RACH response message in response to the RACH preamble message.

[0145] In a sixth aspect, alone or in combination with one or more of the above aspects, prior to receiving a radio resource control (RRC) message including a PUR configuration message, the UE 115 sends a PUR configuration request message based on determining that the UE has small data to send.

[0146] In a seventh aspect, alone or in combination with one or more of the above aspects, the PUR configuration release message is an RRC message or a MAC CE, and wherein the PUR configuration request message is an RRC message or a MAC CE.

[0147] In an eighth aspect, alone or in combination with one or more of the above aspects, the PUR configuration release trigger is a UE-based trigger.

[0148] In a ninth aspect, alone or in combination with one or more of the above aspects, the UE-based trigger includes a TA timer condition, a PUR transmission opportunity quantity condition, a UE-based trigger signal, a RACH process condition, or an LBT failure condition.

[0149] In a tenth aspect, alone or in combination with one or more of the above aspects, the PUR configuration release trigger is a network-based trigger.

[0150] In an eleventh aspect, alone or in combination with one or more of the above aspects, the network-based trigger includes a network-configured timer condition, a network-configured counter condition, or a trigger signal sent by the network.

[0151] In a twelfth aspect, alone or in combination with one or more of the above aspects, the PUR configuration indicates the number of transmission opportunities configured by the PUR and the period of the transmission opportunities configured by the PUR.

[0152] In a thirteenth aspect, alone or in combination with one or more of the above aspects, the PUR configuration further indicates a number of transmission opportunities for each transmission opportunity.

[0153] In a fourteenth aspect, either alone or in combination with one or more of the above aspects, the transmission occasions of each PUR configuration include multiple transmission opportunities.

[0154] In a fifteenth aspect, alone or in combination with one or more of the above aspects, a PUR configuration includes one PUR transmission opportunity (eg, one shot uplink grant resource).

[0155] In a sixteenth aspect, alone or in combination with one or more of the above aspects, a PUR configuration comprises multiple PUR transmission opportunities (eg, multiple shots of uplink grant resources).

[0156] In a seventeenth aspect, alone or in combination with one or more of the above aspects, the plurality of PUR transmission opportunities includes a finite number of transmission opportunities.

[0157] In an eighteenth aspect, alone or in combination with one or more of the above aspects, the plurality of PUR transmission opportunities includes an infinite number of PUR transmission opportunities (eg, infinite opportunities).

[0158] In a nineteenth aspect, alone or in combination with one or more of the above aspects, an infinite number of PUR transmission opportunities (eg, infinite opportunities) is indicated by a first value indicating an infinite number of transmission opportunities.

[0159] In a twentieth aspect, alone or in combination with one or more of the above aspects, an infinite number of PUR opportunities (eg, infinite opportunities) is indicated by a lack of indication of an amount of transmission opportunities.

[0160] In a twenty-first aspect, either alone or in combination with one or more of the above aspects, UE 115 sets a TA timer based on a PUR configuration; starts a TA timer in response to the UE entering an RRC inactive state; determines whether a new TA timer has expired; and determines to release the PUR configuration based on determining that the new TA timer has expired.

[0161] In a twenty-second aspect, alone or in combination with one or more of the above aspects, expiration of a new TA timer indicates that uplink transmission is out of sync.

[0162] In a twenty-third aspect, alone or in combination with one or more of the above aspects, the UE 115 determines the number of allocated PUR sending opportunities based on the PUR configuration; monitors the number of PUR sending opportunities that have passed; and compares the number of allocated PUR sending opportunities with the number of PUR sending opportunities that have passed to determine whether the number of allocated PUR sending opportunities has been reached; wherein determining a PUR configuration release trigger for the PUR configuration includes determining that the number of allocated PUR sending opportunities has been reached.

[0163] In a twenty-third aspect, alone or in combination with one or more of the above aspects, the UE 115 sends a PUR release request message to a network entity, the PUR release request message being configured to indicate a release of a PUR configuration.

[0164] In a twenty-fourth aspect, alone or in combination with one or more of the above aspects, the UE 115 determines that the small data transmission is complete; and in response to determining that the small data transmission is complete, generates a PUR release request message.

[0165] In a twenty-fifth aspect, alone or in combination with one or more of the above aspects, the PUR release request message includes or corresponds to a MAC CE.

[0166] In a twenty-sixth aspect, alone or in combination with one or more of the above aspects, the MAC CE has a fixed size of zero bits, and wherein the MAC CE has a new LCID.

[0167] In a twenty-seventh aspect, alone or in combination with one or more of the above aspects, the PUR release request message includes or corresponds to a data request MAC CE, which requests uplink resource allocation for small data transmission.

[0168] In a twenty-eighth aspect, alone or in combination with one or more of the above aspects, the PUR release request message includes or corresponds to an RRC message.

[0169] In a twenty-ninth aspect, alone or in combination with one or more of the above aspects, the UE 115 is configured to switch to a RACH procedure for small data transmission based on one or more conditions.

[0170] In a thirtieth aspect, either alone or in combination with one or more of the above aspects, UE 115 starts a retransmission timer when monitoring a search space associated with a PUR configuration; sends a first small data transmission using the PUR configuration; in response to expiration of the retransmission timer, switches to a RACH process for small data transmission; and sends a second small data transmission using RACH resources in message A (MSGA) or message 3 (msg3).

[0171] In aspect thirty-second, either alone or in combination with one or more of the above aspects, UE 115 starts a retransmission timer upon monitoring a search space associated with a PUR configuration; sends a small data transmission using the PUR configuration; receives a DCI in response to the small data transmission and indicating that the small data transmission has been received; and resets the retransmission timer.

[0172] In the thirty-third aspect, alone or in combination with one or more of the above aspects, the PUR configuration includes an LBT failure counter, and also includes: UE 115 starts the LBT failure counter based on the PUR configuration message; increments the LBT failure counter based on each LBT failure; resets the LBT failure counter based on LBT success; and generates a PUR configuration release request message based on the LBT failure counter satisfying a continuous LBT failure number condition.

[0173] In a thirty-fourth aspect, alone or in combination with one or more of the above aspects, a small data transfer comprises 1000 bytes or less, 10 bytes or less, or another byte threshold.

[0174] In a thirty-fifth aspect, alone or in combination with one or more of the above aspects, the PUR configuration is per UE or per data radio bearer (DRB).

[0175] Therefore, the UE and the base station may perform PUR configuration and release operations.By performing PUR configuration and release operations, throughput and reliability may be increased, and such operations may be compatible with reduced capability (eg, less advanced) devices.

[0176] Figure 8 is a flow chart illustrating example blocks executed by a wireless communication device configured according to another aspect of the present disclosure. Fig.10 A base station 105 (e.g., gNB) is shown to describe the example block. Fig.10 1 is a block diagram illustrating a base station 105 configured according to one aspect of the present disclosure. The base station 105 includes Figure 2 1. The structure, hardware, and components of the base station 105 shown in FIG. 1. For example, the base station 105 includes a controller / processor 240 that operates to execute logic or computer instructions stored in a memory 242 and to control components of the base station 105 that provide the features and functions of the base station 105. Under the control of the controller / processor 240, the base station 105 transmits and receives signals via the wireless radios 1001a-t and antennas 234a-t. The wireless radios 1001a-t include various components and hardware, such as Figure 2 As shown for base station 105, it includes modulator / demodulators 232a-t, MIMO detector 236, receive processor 238, transmit processor 220 and TX MIMO processor 230. Fig.10As shown in the example, the memory 242 stores PUR configuration logic 1002, PUR release logic 1003, small data transmission logic 1004, PUR release trigger data 1005, small data 1006, timer 1007, counter 1008 and setting data 1009. One or more of 1002-1009 may include or correspond to one of 902-902.

[0177] At block 800, a wireless communication device such as a base station sends a preconfigured uplink resource (PUR) configuration message indicating a PUR configuration for small data transmission. For example, the base station 105 sends an RRC message including PUR configuration data indicating a PUR configuration for small data transmission, as described in reference to FIG. Figure 3A-Figure 6 The PUR configuration data may indicate a PUR configuration indicator or index number, or may include data for settings of the PUR configuration, such as the number of transmission opportunities, the transmission opportunity per opportunity, the periodicity, the type per configuration, etc., or a combination thereof. After the PUR configuration is set, the UE 115 may send small data transmissions in the PUSCH resources configured and allocated by the PUR configuration.

[0178] At block 801, the base station 105 determines a PUR configuration release trigger for a PUR configuration. Figure 3A-Figure 6 As described, the base station 105 determines to release the active PUR configuration of the UE based on one or more network monitored release conditions. For illustration, the base station 105 can set and monitor one or more counters and / or timers. As another example, the base station 105 can monitor whether the PUR configuration has expired or whether the small data transmission has been completed. In some such implementations, the base station 105 can receive a message from the UE 115 indicating that one or more UE release conditions have been met. For illustration, the UE 115 can send a PUR configuration release request message, such as an RRC message, to the base station 105.

[0179] At block 802, the base station 105 sends a PUR configuration release message configured to release the PUR configuration. Figure 3A-Figure 6 As described above, the base station 105 sends an RRC message to the UE to indicate or confirm the release of the PUR configuration.

[0180] In other implementations, the base station 105 may perform additional blocks (or the base station 105 may be configured to further perform additional operations). For example, the base station 105 may perform one or more operations described above, including: Figure 7 As another example, the base station 105 may perform the following and / or reference actions: Figure 7 One or more aspects of a description.

[0181] In a first aspect, the PUR configuration includes a PUR configuration timer, and the base station 105 starts the PUR configuration timer based on a first small data transmission; resets the PUR configuration timer based on a subsequent small data transmission; and generates a PUR configuration release message based on expiration of the PUR configuration timer.

[0182] In a second aspect, alone or in combination with one or more of the above aspects, the PUR configuration of the UE 115 includes a PUR configuration counter, and the base station 105 starts the PUR configuration counter based on the first small data transmission; increments the PUR configuration counter based on each unused PUR sending opportunity; resets the PUR configuration counter based on the small data transmission; and generates a PUR configuration release message based on the PUR configuration counter satisfying a condition of the number of consecutive unused sending opportunities.

[0183] In a third aspect, alone or in combination with one or more of the above aspects, the UE 115 sends a PUR release request message to the UE, the PUR release request message being configured to indicate a release of the PUR configuration.

[0184] In a fourth aspect, alone or in combination with one or more of the above aspects, the PUR release request message includes or corresponds to an RRC message.

[0185] In a fifth aspect, alone or in combination with one or more of the above aspects, the UE 115 determines to revoke a PUR configuration; and generates a PUR release request message in response to determining to revoke the PUR configuration.

[0186] Therefore, the UE and the base station may perform PUR configuration and release operations.By performing PUR configuration and release operations, throughput and reliability may be increased, and such operations may be compatible with reduced capability (eg, less advanced) devices.

[0187] Those skilled in the art will appreciate that any of a variety of different techniques and methods may be used to represent information and signals. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0188] Figure 7 and 8 The functional blocks and modules in may include processors, electronic devices, hardware devices, electronic components, logical circuits, memories, software codes, firmware codes, etc., or any combination thereof.

[0189] Those skilled in the art will further appreciate that the various illustrative logic blocks, modules, circuits and algorithm steps described in conjunction with the disclosure herein can be implemented as electronic hardware, computer software or a combination of the two. In order to clearly illustrate this interchangeability of hardware and software, they have been generally described above according to the functions of various illustrative components, frames, modules, circuits and steps. Whether such functions are implemented as hardware or software depends on specific applications and design constraints to the entire system. Those skilled in the art can implement the described functions in different ways for each specific application, but such implementation decisions should not be interpreted as causing departure from the scope of the present disclosure. Those skilled in the art will also readily recognize that the order or combination of components, methods or interactions described herein are only examples, and the components, methods or interactions of various aspects of the present disclosure can be combined or performed in a manner different from that shown and described herein.

[0190] The various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure herein may be implemented or executed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors with a DSP core, or any other such configuration.

[0191] The steps of the method or algorithm described in conjunction with the disclosure herein may be directly embodied in hardware, a software module executed by a processor, or a combination of the two. The software module may reside in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. Alternatively, the storage medium may be integrated into the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. Alternatively, the processor and the storage medium may reside in a user terminal as discrete components.

[0192] In one or more exemplary designs, the functions described can be implemented with hardware, software, firmware or any combination thereof. If implemented with software, these functions can be stored or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, including any medium that is convenient for transferring a computer program from one place to another. Computer-readable storage media can be any available medium that can be accessed by a general or special-purpose computer. As an example and not limitation, such a computer-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code components in the form of instructions or data structures and can be accessed by a general or special-purpose computer or a general or special-purpose processor. In addition, a connection can be appropriately referred to as a computer-readable medium. For example, if a coaxial cable, fiber optic cable, twisted pair or digital subscriber line (DSL) is used to transmit software from a website, server or other remote source, the coaxial cable, fiber optic cable, twisted pair or DSL are all included in the definition of the medium. Disk and disc as used herein include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, wherein disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0193] As used herein, including in the claims, the term "and / or," when used in a list of two or more items, means that any one of the listed items may be used alone, or any combination of two or more of the listed items may be used. For example, if a composition is described as comprising components A, B, and / or C, the composition may comprise only A; only B; only C; a combination of A and B; a combination of A and C; a combination of B and C; or a combination of A, B, and C. Furthermore, as used herein, including in the claims, "or" used in a list of items ending with "at least one of" means a disjunctive list, such that, for example, a list of "at least one of A, B, or C" means any one of A or B or C or AB or AC or BC or ABC (i.e., A and B and C), or any combination thereof.

[0194] The foregoing description of the present disclosure is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to the present disclosure will be clear to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure is not intended to be limited to the examples and designs described herein, but to conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method of wireless communication, comprising: Receiving, by a user equipment UE, a configuration message indicating a preconfigured uplink resource PUR configuration for small data transmission; Receiving one or more synchronization signal blocks (SSB) transmissions by the UE; Selecting, by the UE, an SSB from among the one or more SSB transmissions; The UE determines a first PUR transmission opportunity based on the selected SSB; as well as The UE sends first small data based on the PUR configuration and using the first PUR sending opportunity.

2. The method according to claim 1, further comprising: The UE transmits the second small data based on the PUR configuration and using a second PUR transmission opportunity based on the selected SSB.

3. The method according to claim 2, wherein: The first PUR transmission opportunity and the second PUR transmission opportunity are included in a PUSCH transmission opportunity, and wherein, when the first small data and the second small data are transmitted, the UE is in a radio resource control RRC inactive state.

4. The method according to claim 1, further comprising, before receiving the configuration message: receiving, by the UE, dedicated RRC signaling indicating a radio resource control, RRC, state change; and The UE switches from the RRC connected state to the RRC inactive state based on the dedicated RRC signaling.

5. The method according to claim 1, further comprising, before receiving the configuration message: The UE sends a random access channel RACH preamble message; and A RACH response message is received by the UE in response to the RACH preamble message. 6 . The method of claim 5 , further comprising, before receiving a radio resource control (RRC) message including the configuration message, sending, by the UE, a configuration request message based on determining that the UE has small data to send.

7. The method according to claim 1, further comprising: Determining, by the UE, a PUR configuration release trigger for the PUR configuration; as well as A PUR configuration release message configured to release the PUR configuration is received by the UE.

8. The method according to claim 7, wherein: The PUR configuration release message is an RRC message or a MAC CE, and wherein the PUR configuration request message is an RRC message or a MAC CE.

9. The method according to claim 7, wherein: The PUR configuration release trigger is based on the UE trigger.

10. The method according to claim 9, wherein: The UE-based trigger includes a TA timer condition, a PUR sending opportunity quantity condition, a UE-based trigger signal, a random access channel RACH process condition or a listen-before-talk LBT failure condition.

11. The method according to claim 7, wherein: The PUR configuration release trigger is a network-based trigger.

12. The method according to claim 11, wherein: The network-based trigger includes a timer condition configured by the network, a counter condition configured by the network, or a trigger signal sent by the network.

13. The method according to claim 1, wherein: The PUR configuration indicates the number of transmission opportunities of the PUR configuration and the period of the transmission opportunities of the PUR configuration.

14. The method according to claim 1, wherein: The PUR configuration includes a PUR sending opportunity.

15. The method according to claim 1, wherein: The PUR configuration includes multiple PUR sending opportunities.

16. The method according to claim 1, further comprising: The UE sets a new TA timer based on the PUR configuration; Starting, by the UE in response to the UE entering a radio resource control (RRC) inactive state, the new TA timer; Determining, by the UE, whether the new TA timer expires; as well as The UE determines to release the PUR configuration based on determining that the new TA timer expires.

17. The method according to claim 1, further comprising sending, by the UE, a PUR release request message to a network entity, wherein the PUR release request message is configured to indicate the release of the PUR configuration.

18. The method of claim 1, further comprising: The UE determines that the small data transmission is completed; as well as The UE generates a PUR release request message in response to determining that the small data transmission is completed.

19. The method according to claim 1, wherein: The PUR release request message includes or corresponds to the MAC CE.

20. The method according to claim 19, wherein: The MAC CE has a fixed size of zero bits, and wherein the MAC CE has a new logical channel ID LCID.

21. The method according to claim 1, wherein: The PUR release request message includes or corresponds to a data request MAC CE requesting uplink resource allocation for small data transmission.

22. The method according to claim 1, wherein: The PUR release request message includes or corresponds to a radio resource control RRC message.

23. The method according to claim 1, wherein: The UE is configured to switch to a random access channel (RACH) procedure for small data transmission based on one or more conditions.

24. The method of claim 1, further comprising: Starting a retransmission timer by the UE when monitoring a search space associated with the PUR configuration; sending, by the UE, a first small data transmission using the PUR configuration; In response to expiration of the retransmission timer, switching by the UE to a random access channel RACH procedure for small data transmission; as well as The second small data transmission is sent by the UE using RACH resources in message A MSG A or message 3 msg3.

25. The method of claim 1, wherein: The small data transfer comprises 1000 bytes or less.

26. The method of claim 1, wherein: The PUR configuration is for each data radio bearer DRB.

27. An apparatus configured for wireless communication, comprising: at least one processor; as well as a memory coupled to the at least one processor, Wherein, the at least one processor is configured to: Receiving, by a user equipment UE, a configuration message indicating a preconfigured uplink resource PUR configuration for small data transmission; Receiving one or more synchronization signal blocks (SSB) transmissions by the UE; Selecting, by the UE, an SSB from among the one or more SSB transmissions; determining, by the UE, a first PUR transmission opportunity based on the selected SSB; and The UE sends first small data based on the PUR configuration and using the first PUR sending opportunity.

28. An apparatus configured for wireless communication, comprising: means for receiving, by a user equipment UE, a configuration message indicating a preconfigured uplink resource PUR configuration for small data transmission; means for receiving, by a UE, one or more synchronization signal blocks, SSB, transmissions; means for selecting, by the UE, an SSB of the one or more SSB transmissions; means for determining, by the UE, a first PUR transmission opportunity based on the selected SSB; as well as A means for transmitting, by the UE, first small data based on the PUR configuration and using the first PUR transmission opportunity.

29. A non-transitory computer readable medium storing instructions which, when executed by a processor, cause the processor to perform operations comprising: Receiving, by a user equipment UE, a configuration message indicating a preconfigured uplink resource PUR configuration for small data transmission; Receiving one or more synchronization signal blocks (SSB) transmissions by the UE; Selecting, by the UE, an SSB from among the one or more SSB transmissions; The UE determines a first PUR transmission opportunity based on the selected SSB; as well as The UE sends first small data based on the PUR configuration and using the first PUR sending opportunity.

Images