Uplink data transmission via random access or dedicated uplink resources

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may determine that uplink data is to be sent in an inactive state. The UE may determine whether a timing advance of the UE is valid. If the timing advance is invalid, the UE may determine whether the uplink data meets a transport block size (TBS) threshold. The UE may selectively send uplink data via an uplink random access channel (RACH) message or configured uplink resources, or establish a radio resource control (RRC) connection for the uplink data, based at least in part on whether the uplink data meets the TBS threshold. The present disclosure provides many other aspects.

Description

Technical Field

[0001] Aspects of the present disclosure relate generally to wireless communications and techniques and apparatus for uplink data transmission on random access or dedicated uplink resources. Background Art

[0002] Wireless communication systems are widely deployed to provide various telecommunication services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0003] A wireless network may include multiple base stations (BS) that can support communications for multiple user equipment (UE). A user equipment (UE) may communicate with a base station (BS) via a downlink and an uplink. A downlink (or forward link) refers to a communication link from a BS to a UE, and an uplink (or reverse link) refers to a communication link from a UE to a BS. As will be described in more detail herein, a BS may be referred to as a Node B, gNB, access point (AP), radio head, transmit receive point (TRP), new air interface (NR) BS, 5G Node B, etc.

[0004] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different user devices to communicate at a city, country, region, and even global level. New Radio (NR), also known as 5G, is a collection of enhancements to the LTE mobile standard promulgated by the Third Generation Partnership Project (3GPP). NR aims to better support mobile broadband Internet access by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and better integrating with other open standards, which use orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink (DL), CP-OFDM and / or SC-FDM (e.g., also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink (UL), and support beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to grow, further improvements in LTE, NR, and other radio access technologies remain very useful. Summary of the invention

[0005] In some aspects, a method of wireless communication performed by a user equipment (UE) includes: in an inactive state, determining that uplink data is to be sent; determining whether a timing advance of the UE is valid; if the timing advance is invalid, determining whether the uplink data meets a transport block size (TBS) threshold; and based at least in part on whether the uplink data meets the TBS threshold, selectively: sending the uplink data via an uplink random access channel (RACH) message or a configured uplink resource, or establishing a radio resource control (RRC) connection for the uplink data.

[0006] In some aspects, the UE includes one or more memories; and one or more processors communicatively coupled to the one or more memories, configured to: in an inactive state, determine that uplink data is to be sent; determine whether a timing advance of the UE is valid; if the timing advance is invalid, determine whether the uplink data meets a TBS threshold; and based at least in part on whether the uplink data meets the TBS threshold, selectively: send the uplink data via an uplink RACH message or a configured uplink resource, or establish an RRC connection for the uplink data.

[0007] In some aspects, a non-transitory computer-readable medium storing instructions includes: one or more instructions that, when executed by one or more processors, cause the one or more processors to: in an inactive state, determine that uplink data is to be sent; determine whether a timing advance of the UE is valid; if the timing advance is invalid, determine whether the uplink data meets a TBS threshold; and based at least in part on whether the uplink data meets the TBS threshold, selectively: send the uplink data via an uplink RACH message or a configured uplink resource, or establish an RRC connection for the uplink data.

[0008] In some aspects, an apparatus includes: a device for determining that uplink data is to be sent in an inactive state; a device for determining whether a timing advance of the apparatus is valid; a device for determining whether the uplink data meets a TBS threshold if the timing advance is invalid; and a device for selectively: sending the uplink data via an uplink RACH message or a configured uplink resource, or establishing an RRC connection for the uplink data, based at least in part on whether the uplink data meets the TBS threshold.

[0009] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices, and / or processing systems as substantially described herein with reference to and illustrated by the drawings and description.

[0010] The features and technical advantages of 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

[0011] In order to be able to understand the above-mentioned features of the present disclosure in detail, a more specific description of the above brief summary may be made with reference to some aspects, some of which are shown in the accompanying drawings. However, it should be noted that the accompanying drawings only show certain typical aspects of the present disclosure and should not be considered as limiting the scope thereof, as the description may admit of other equally effective aspects. The same reference numerals in different drawings may represent the same or similar elements.

[0012] Figure 1 is a diagram illustrating an example of a wireless network in accordance with various aspects of the present disclosure.

[0013] Figure 2 is a diagram illustrating an example of a base station communicating with a UE in a wireless network according to various aspects of the present disclosure.

[0014] Figure 3 is a diagram illustrating an example of a four-step random access procedure according to various aspects of the present disclosure.

[0015] Figure 4 is a diagram illustrating an example of a two-step random access procedure according to various aspects of the present disclosure.

[0016] Figure 5 is a diagram illustrating examples associated with uplink data transmission through random access or configured uplink resources according to various aspects of the present disclosure.

[0017] Figure 6-Figure 9 is a diagram illustrating an example associated with uplink data transmission through configured uplink resources related to a random access procedure according to various aspects of the present disclosure.

[0018] Fig.10 is a diagram illustrating example procedures associated with uplink data transmission through random access and / or dedicated uplink resources in accordance with various aspects of the present disclosure. DETAILED DESCRIPTION

[0019] The various aspects of the present disclosure will be described more fully below with reference to the accompanying drawings. However, the present disclosure can be implemented in many different forms and should not be interpreted as being limited to any specific structure or function presented throughout the present disclosure. In contrast, these aspects are provided to make the present disclosure thorough and complete, and to fully convey the scope of the present disclosure to those skilled in the art. Based on the teachings herein, it should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect disclosed herein, whether it is implemented independently of any other aspect of the present disclosure or implemented in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein can be used to implement equipment or practice methods. In addition, the scope of the present disclosure is intended to cover such equipment or methods, which are practiced using other structures, functions, or structures and functions in addition to or different from the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein can be embodied by one or more elements of the claims.

[0020] Several aspects of telecommunication systems will now be described with reference to various equipment and techniques. These equipment and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and design constraints on the overall system.

[0021] It should be noted that although terms generally associated with 5G or NR radio access technologies (RATs) may be used herein to describe various aspects, various aspects of the present disclosure may be applied to other RATs, such as 3G RATs, 4G RATs, and / or RATs beyond 5G (e.g., 6G).

[0022] Figure 1 is a diagram showing an example of a wireless network 100 according to various aspects of the present disclosure. The wireless network 100 may be or may include elements of a 5G (NR) network, an LTE network, etc. The wireless network 100 may include a plurality of base stations 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and other network entities. A base station (BS) is an entity that communicates with a user equipment (UE) and may also be referred to as an NR BS, Node B, gNB, 5G Node B (NB), access point, transmit receive point (TRP), etc. Each BS may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to a coverage area of ​​a BS and / or a BS subsystem serving the coverage area, depending on the context in which the term is used.

[0023] A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access to UEs with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access to UEs with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access to UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG)). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In Figure 1 In the example shown, BS 110a may be a macro BS of macro cell 102a, BS 110b may be a pico BS of pico cell 102b, and BS 110c may be a femto BS of femto cell 102c. A BS may support one or more (e.g., three) cells. The terms "eNB", "base station", "NR BS", "gNB", "TRP", "AP", "Node B", "5G NB", and "cell" may be used interchangeably herein.

[0024] In some aspects, the cells are not necessarily stationary, and the geographic area of ​​the cells may move depending on the location of the mobile BS. In some aspects, the BSs may be interconnected with each other and / or with one or more other BSs or network nodes (not shown) in the wireless network 100 using any suitable transport network, through various types of backhaul interfaces, such as direct physical connections, virtual networks, etc.

[0025] The wireless network 100 may also include a relay station. A relay station is an entity that can receive transmissions of data from an upstream station (e.g., a BS or a UE) and send transmissions of data to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that is capable of relaying transmissions for other UEs. Figure 1 In the example shown, relay BS 110d may communicate with macro BS 110a and UE 120d to facilitate communication between BS 110a and UE 120d. A relay BS may also be referred to as a relay station, relay base station, repeater, etc.

[0026] The wireless network 100 may be a heterogeneous network including different types of BSs, such as a macro BS, a pico BS, a femto BS, a relay BS, etc. These different types of BSs may have different transmit power levels, different coverage areas, and different effects on interference in the wireless network 100. For example, a macro BS may have a high transmit power level (e.g., 5 to 40 watts), while a pico BS, a femto BS, and a relay BS may have a lower transmit power level (e.g., 0.1 to 2 watts).

[0027] A network controller 130 may be coupled to a set of BSs and may provide coordination and control for these BSs. The network controller 130 may communicate with the BSs via a backhaul. The BSs may also communicate with each other, for example, directly or indirectly via a wireless or wired backhaul.

[0028] UE 120 (e.g., 120a, 120b, 120c) can be dispersed in the wireless network 100, and each UE can be fixed or mobile. UE can also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, etc. UE can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, a biosensor / device, a wearable device (smart watch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., a music or video device, or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing device, a global positioning system device, or any other suitable device configured to communicate via a wireless or wired medium.

[0029] Some UEs may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., which can communicate with a base station, another device (e.g., a remote device), or some other entity. For example, a wireless node may provide a connection to a network (e.g., a wide area network such as the Internet or a cellular network) via a wired or wireless communication link. Some UEs may be considered as Internet of Things (IoT) devices, and / or may be implemented as NB-IoT (narrowband Internet of Things) devices. Some UEs may be considered as customer premises equipment (CPE). UE 120 may be included in a housing that houses components of UE 120 (such as processor components, memory components, etc.). In some aspects, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operably coupled, communicatively coupled, electronically coupled, electrically coupled, etc.

[0030] Generally, any number of wireless networks can be deployed in a given geographic area. Each wireless network can support a specific RAT and can operate on one or more frequencies. RAT can also be referred to as radio technology, air interface, etc. Frequency can also be referred to as carrier, channel, etc. Each frequency can support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0031] In some aspects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using base station 110 as an intermediary for communicating with each other) using one or more bypass channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, etc.), mesh networks, etc. In this case, UE 120 may perform scheduling operations, resource selection operations, and / or other operations performed by base station 110 as described elsewhere herein.

[0032] The devices of the wireless network 100 can communicate using an electromagnetic spectrum, which can be subdivided into various categories, frequency bands, channels, etc. based on frequency or wavelength. For example, the devices of the wireless network 100 can communicate using an operating frequency band having a first frequency range (FR1) from 410 MHz to 7.125 GHz, and / or can communicate using an operating frequency band having a second frequency range (FR2) from 24.25 GHz to 52.6 GHz. The frequencies between FR1 and FR2 are sometimes referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to as a "sub-6 GHz" band. Similarly, FR2 is also often referred to as a "millimeter wave" band, although it is different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) determined by the International Telecommunication Union (ITU) as a "millimeter wave" band. Therefore, unless otherwise stated, it should be understood that the term "below 6 GHz" and the like, if used herein, can broadly represent frequencies less than 6 GHz, frequencies within FR1, and / or mid-band frequencies (e.g., greater than 7.125 GHz). Similarly, unless otherwise stated, it should be understood that the term "millimeter wave", etc., if used herein, can broadly refer to frequencies within the EHF band, frequencies within FR2, and / or mid-band frequencies (e.g., less than 24.25 GHz). It is expected that the frequencies included in FR1 and FR2 can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0033] As mentioned above, Figure 1are provided as examples. Other examples may differ from those described in Figure 1 As described.

[0034] Figure 2 is a diagram illustrating an example 200 of a base station 110 communicating with a UE 120 in a wireless network 100 in accordance with various aspects of the present disclosure. The base station 110 may be equipped with T antennas 234a through 234t and the UE 120 may be equipped with R antennas 252a through 252r, where in general T≥1 and R≥1.

[0035] At the base station 110, the transmit processor 220 may receive data for one or more UEs from the data source 212, select one or more modulation and coding schemes (MCS) for each UE based at least in part on a channel quality indicator (CQI) received from the UE, process (e.g., encode and modulate) the data for each UE based at least in part on the (multiple) MCS selected for each UE, and provide data symbols for all UEs. The transmit processor 220 may also process system information (e.g., for semi-static resource partitioning information (SRPI) and the like) and control information (e.g., CQI requests, grants, upper layer signaling, etc.), and provide overhead symbols and control symbols. The transmit processor 220 may also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS), demodulation reference signals (DMRS), etc.) and synchronization signals (e.g., primary synchronization signals (PSS) and secondary synchronization signals (SSS)). A transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols (if applicable), and may provide T output symbol streams to T modulators (MOD) 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 (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 232a to 232t may be transmitted via T antennas 234a to 234t, respectively.

[0036] At the UE 120, antennas 252a to 252r may receive downlink signals from the base station 110 and / or other base stations, and may provide received signals to demodulators (DEMODs) 254a to 254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) the received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. The MIMO detector 256 may obtain received symbols from all R demodulators 254a to 254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data of the UE 120 to the data sink 260, and provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine reference signal received power (RSRP), received signal strength indicator (RSSI), reference signal received quality (RSRQ), channel quality indicator (CQI), etc. In some aspects, one or more components of the UE 120 may be included in the housing 284.

[0037] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the base station 110 via the communication unit 294.

[0038] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, CQI, etc.). The transmit processor 264 may also generate reference symbols for one or more reference signals. If applicable, the symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266, further processed by modulators 254a through 254r (e.g., for DFT-s-OFDM, CP-OFDM, etc.), and transmitted to the base station 110. In some aspects, the UE 120 includes a transceiver. The transceiver may include any combination of antenna(s) 252, modulators and / or demodulators 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. A processor (eg, controller / processor 280) and memory 282 may use a transceiver to perform aspects of any of the methods described herein, for example, as described with reference to Figure 3-Figure 9 As described.

[0039] At the base station 110, uplink signals from the UE 120 and other UEs may be received by the antenna 234, processed by the demodulator 232, detected by the MIMO detector 236 (if applicable), and further processed by the receive processor 238 to obtain decoded data and control information sent by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and communicate with the network controller 130 via the communication unit 244. The base station 110 may include a scheduler 246 for scheduling the UE 120 for downlink and / or uplink communications. In some aspects, the base station 110 includes a transceiver. The transceiver may include any combination of the antenna 234, the modulator and / or demodulator 232, the MIMO detector 236, the receive processor 238, the transmit processor 220, and / or the TX MIMO processor 230. A processor (eg, controller / processor 240) and memory 242 may use a transceiver to perform aspects of any of the methods described herein, for example, as described with reference to Figure 3-Figure 9 As described.

[0040] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other components of the base station 110 may perform one or more techniques associated with uplink data transmission on random access or dedicated uplink resources, as described in more detail elsewhere herein. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the can perform or direct e.g. Fig.10 The operations of process 1000 and / or other processes described herein may be performed. Memories 242 and 282 may store data and program codes for base station 110 and UE 120, respectively. In some aspects, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code, program code, etc.) for wireless communication. For example, when one or more instructions are executed (e.g., directly, or after compilation, conversion, interpretation, etc.) by one or more processors of base station 110 and / or UE 120, it may cause one or more processors, UE 120, and / or base station 110 to perform or direct, for example Fig.10 The operations of process 1000 and / or other processes described herein. In some aspects, executing instructions may include running instructions, converting instructions, compiling instructions, interpreting instructions, etc.

[0041] In some aspects, the UE 120 may include means for determining that uplink data is to be sent in an inactive state; means for determining whether a timing advance of the UE is valid; means for determining whether the uplink data meets a transport block size (TBS) threshold; means for sending the uplink data via an uplink random access channel (RACH) message or a configured uplink resource; means for establishing a radio resource control (RRC) connection for the uplink data; means for sending the uplink data via an uplink RACH message if the uplink data fails to meet the threshold, wherein the failure to meet the threshold indicates that the uplink data can be accommodated in the uplink RACH message; means for sending the uplink data via the configured uplink resource if the uplink data meets the threshold; means for sending a request for the configured uplink resource before sending the uplink data via the configured uplink resource; means for receiving information configuring the configured uplink resource based at least in part on the request; and means for determining whether the uplink data meets the threshold. Means for sending a request based at least in part on determining that a periodic transmission is to be performed by the UE; means for receiving an indication of whether to use a threshold or a TBS threshold; means for receiving system information indicating a TBS threshold; means for receiving information indicating a TBS threshold via dedicated RRC signaling; means for determining whether a configured uplink resource is configured and whether uplink data can be accommodated in the configured uplink resource; means for sending uplink data on the configured uplink resource; means for sending a request for other configured uplink resources; means for sending uplink data on other configured uplink resources; means for initiating a RACH procedure; means for determining whether the uplink data meets the TBS threshold; means for sending uplink data in connection with the RACH procedure; means for sending a request for the configured uplink resource; means for establishing an RRC connection for uplink data; means for receiving configuration information indicating the configured uplink resource; etc. In some aspects, such means may include in combination Figure 2 One or more components of UE 120 are depicted, such as controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, and the like.

[0042] Although Figure 2The blocks in the 200 are shown as distinct components, but the functionality described above with respect to the blocks may be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functionality described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0043] As mentioned above, Figure 2 are provided as examples. Other examples may differ from those described in Figure 2 As described.

[0044] The UE may enter an inactive state, such as a radio resource control (RRC) inactive state, to save battery power and network resources when data traffic is infrequent. Entering the active state from the inactive state may involve a random access channel (RACH) procedure or another form of establishment procedure. In many applications, the UE may generate only a small amount of data in a burst of a data session. Examples of such applications include enhanced mobile broadband (eMBB) communications, Internet of Things (IoT) communications, instant messaging applications, social media applications, wearable device applications, etc. Re-establishing an RRC connection just to send a small burst of data may waste UE resources and network resources.

[0045] Some radio access technologies can provide services for sending small data transmissions in inactive mode, such as via uplink RACH messages or the uplink resources of configuration (for example, dedicated pre-configured uplink resources, pre-configured uplink resources, dedicated uplink resources, etc.). However, not all small data transmissions are suitable for uplink RACH messages or the uplink resources of configuration. In addition, in some cases, it is possible not to configure uplink resources for UE. Therefore, providing small data transmissions indiscriminately via uplink RACH messages or the uplink resources of configuration (for example, without considering the size of the uplink resources of data transmission or configuration) may cause uplink transmissions, retransmissions, etc. of failure.

[0046] Some techniques and equipment described herein enable to selectively use uplink RACH message or at least partially based on one or more size thresholds (e.g., transport block size (TBS) threshold, etc.) configured uplink resources to transmit uplink data (e.g., small data transmission). For example, if uplink data cannot meet the size threshold (e.g., less than or equal to, or less than the size threshold), UE can send uplink data (e.g., at least partially based on one or more other thresholds or other values ​​associated with the size threshold) on uplink RACH message or configured uplink resources. If uplink data meets the size threshold (e.g., greater than, or greater than or equal to the size threshold), UE can establish RRC connection to send uplink data. In this way, UE can selectively provide uplink data via uplink RACH resource or configured uplink resource at least partially based on the size of uplink data. By establishing an RRC connection when the uplink data meets a size threshold, the UE can reduce the likelihood of uplink data transmission failure and reduce the latency or delay associated with transmitting larger uplink data transmissions via configured uplink resources (e.g., via multiple occasions of configured uplink resources).

[0047] Figure 3 is a diagram illustrating an example 300 of a four-step random access procedure according to various aspects of the present disclosure. Figure 3 As shown, base station 110 and UE 120 may communicate with each other to perform a four-step random access procedure.

[0048] As indicated by reference numeral 305, the base station 110 may send and the UE 120 may receive one or more synchronization signal blocks (SSBs) and random access configuration information. In some aspects, the random access configuration information may be sent and / or indicated by system information (e.g., in one or more system information blocks (SIBs), etc.) and / or SSBs, such as for contention-based random access. Additionally or alternatively, the random access configuration information may be sent in a radio resource control (RRC) message and / or a physical downlink control channel (PDCCH) command message that triggers a RACH procedure, such as for contention-free random access. The random access configuration information may include one or more parameters to be used in the random access procedure, such as one or more parameters for sending a random access message, one or more parameters for receiving a RAR, etc.

[0049] As shown by reference numeral 310, UE 120 may send a RACH message, which may include a preamble (sometimes referred to as a random access preamble, a physical random access (PRACH) preamble, a RACH message preamble, etc.). In the four-step random access procedure, the message including the preamble may be referred to as message 1, msg1, MSG1, a first message, an initial message, etc. The random access message may include a random access preamble identifier.

[0050] As shown in reference numeral 315, the base station 110 may send a RAR in reply to the preamble. In the four-step random access procedure, the message including the RAR may be referred to as message 2, msg2, MSG2, or a second message. In some aspects, the RAR may indicate a detected random access preamble identifier (e.g., received from the UE 120 in msg1). Additionally or alternatively, the RAR may indicate a resource allocation that the UE 120 is to use to send message 3 (msg3).

[0051] In some aspects, as part of the second step of the four-step random access procedure, the base station 110 may send a PDCCH communication for the RAR. The PDCCH communication may schedule a PDSCH communication including the RAR. For example, the PDCCH communication may indicate a resource allocation for the PDSCH communication. In addition, as part of the second step of the four-step random access procedure, the base station 110 may send a PDSCH communication for the RAR as scheduled by the PDCCH communication. The RAR may be included in a MAC protocol data unit (PDU) of the PDSCH communication.

[0052] As indicated by reference numeral 320, UE 120 may send an RRC connection request message. The RRC connection request message may be referred to as message 3, msg3, MSG3, or a third message of the four-step random access procedure. In some aspects, the RRC connection request may include a UE identifier, a UCI, a physical uplink shared channel (PUSCH) communication (e.g., an RRC connection request), etc.

[0053] As indicated by reference numeral 325, the base station 110 may send an RRC connection setup message. The RRC connection setup message may be referred to as message 4, msg4, MSG4, or a fourth message of the four-step random access procedure. In some aspects, the RRC connection setup message may include a detected UE identifier, a timing advance value, contention resolution information, etc. As indicated by reference numeral 330, if the UE 120 successfully receives the RRC connection setup message, the UE 120 may send a hybrid automatic repeat request (HARQ) acknowledgement (ACK).

[0054] As mentioned above, Figure 3 are provided as examples. Other examples may differ from those described in Figure 3 As described.

[0055] Figure 4 4 is a diagram illustrating an example 400 of a two-step random access procedure according to various aspects of the present disclosure. Figure 4 As shown, base station 110 and UE 120 may communicate with each other to perform a two-step random access procedure.

[0056] As indicated by reference numeral 405, the base station 110 may send and the UE 120 may receive one or more SSBs and random access configuration information. In some aspects, the random access configuration information may be sent and / or indicated by system information (e.g., in one or more SIBs, etc.) and / or SSBs, such as for contention-based random access. Additionally or alternatively, the random access configuration information may be sent in an RRC message and / or a PDCCH command message that triggers a RACH procedure, such as for contention-free random access. The random access configuration information may include one or more parameters to be used in a two-step random access procedure, such as one or more parameters for sending a random access message (referred to herein as a RACH message), a RAR for receiving a RACH message, and the like.

[0057] As indicated by reference numeral 410, UE 120 may send a RACH message preamble, and base station 110 may receive the RACH message preamble. As indicated by reference numeral 415, UE 120 may send a RACH message payload, and base station 110 may receive the RACH message payload. As shown, as part of the initial (or first) step of the two-step random access procedure, UE 120 may send a RACH message preamble and a RACH message payload to base station 110. In some aspects, in the two-step random access procedure, the RACH message may be referred to as message A, msgA, first message, initial message, etc. In addition, in some aspects, the RACH message preamble may be referred to as message A preamble, msgA preamble, preamble, PRACH preamble, etc., and the RACH message payload may be referred to as message A payload, msgA payload, payload, etc. In some aspects, the RACH message may include some or all of the contents of message 1 (msg1) and message 3 (msg3) of the four-step random access procedure, which will be described in more detail below. For example, the RACH message preamble may include some or all of the contents of message 1 (e.g., PRACH preamble), while the RACH message payload may include some or all of the contents of message 3 (e.g., UE identifier, uplink control information (UCI), PUSCH transmission, etc.).

[0058] As indicated by reference numeral 420, the base station 110 may receive the RACH message preamble transmitted by the UE 120. If the base station 110 successfully receives and decodes the RACH message preamble, the base station 110 may receive and decode the RACH message payload.

[0059] As shown in the reference numeral 425, the base station 110 may send a RAR (sometimes referred to as a RAR message). As shown, the base station 110 may send a RAR message as part of the second step of the two-step random access procedure. In some aspects, the RAR message may be referred to as message B, msgB, or a second message in the two-step random access procedure. The RAR message may include some or all of the contents of message 2 (msg2) and message 4 (msg4) of the four-step random access procedure. For example, the RAR message may include a detected PRACH preamble identifier, a detected UE identifier, a timing advance value, contention resolution information, etc.

[0060] As shown by reference numeral 430, as part of the second step of the two-step random access procedure, the base station 110 may send a physical downlink control channel (PDCCH) communication for the RAR. The PDCCH communication may schedule a physical downlink shared channel (PDSCH) communication including the RAR. For example, the PDCCH communication may indicate a resource allocation for the PDSCH communication (e.g., in downlink control information).

[0061] As shown at 435, as part of the second step of the two-step random access procedure, the base station 110 may send a PDSCH communication for the RAR as scheduled by the PDCCH communication. The RAR may be included in the MAC PDU of the PDSCH communication. As shown at 440, if the UE 120 successfully receives the RAR, the UE 120 may send a HARQ ACK.

[0062] use Figure 3 and Figure 4The RACH process shown in the figure sets up an RRC connection, which consumes a large amount of resources of the UE and the network. Therefore, in some cases, it may be inefficient to set up an RRC connection for uplink data transmission. The technology and equipment described herein enable uplink data transmission to be provided without setting up an RRC connection, for example, if the uplink data transmission is small enough to fit the uplink resources of the RACH message or the configuration of the UE. If the uplink data transmission is too large to be provided via the RACH message or the uplink resources of the configuration, the UE can set up an RRC connection. Therefore, the communication resources associated with the unnecessary establishment of an RRC connection are saved. In addition, the UE can selectively send uplink data on the RACH message and / or the uplink resources of the configuration based on the size of the uplink data, at least in part, which improves the utilization rate of the communication resources of the UE.

[0063] As mentioned above, Figure 4 are provided as examples. Other examples may differ from those described in Figure 4 As described.

[0064] Figure 5 is a diagram illustrating an example 500 associated with uplink data transmission through random access or configured uplink resources in accordance with various aspects of the present disclosure. Figure 5 The operations shown in may be performed by a UE, such as UE 120. In example 500, UE 120 starts in an inactive state, such as an RRC inactive state.

[0065] As indicated by reference numeral 505, UE 120 may determine to send data on the uplink (referred to as a data transfer (DT)). A DT may be associated with any application or source. In some aspects, a DT may be associated with an IoT application, a wearable device application, etc. In some aspects, a DT may be referred to as a small data transfer.

[0066] As indicated by reference numeral 510, UE 120 may determine whether a timing advance (TA) of UE 120 is valid. The TA value may identify a timing adjustment for uplink transmissions of UE 120. UE 120 may determine the TA value based at least in part on a RACH procedure or a MAC message following a RACH procedure. For example, UE 120 may receive the TA value in a RAR or in a TA MAC CE following a RACH procedure. UE 120 may determine whether the TA is valid based at least in part on a timer, location information associated with UE 120, and the like.

[0067] As indicated by reference numeral 515, if UE 120 determines that the TA value is invalid (block 510 No), UE 120 may perform a RACH procedure. UE 120 may perform a RACH procedure to update the TA value associated with UE 120 so that UE 120 may successfully transmit a DT.

[0068] As shown in reference numeral 520, UE 120 may determine whether DT satisfies a TBS threshold (also referred to herein as a size threshold). The TBS threshold may indicate whether DT is small enough to be sent on a RACH message such as msg3 or msgA. CUR will be described in more detail below. As shown in reference numeral 525, if DT is greater than the TBS threshold (block 520 No), UE 120 may establish an RRC connection and send DT via the RRC connection. For example, if DT is greater than the TBS threshold, UE 120 may exit the RRC inactive state and may enter an RRC connected state for transmitting DT. Example values ​​of the TBS threshold include 328 bits, 504 bits, 680 bits, 936 bits, 1000 bits, 2000 bits, etc.

[0069] BS 110 may configure TBS thresholds for UE 120. In some aspects, the TBS threshold may include a single threshold. In this case, if the DT satisfies the single threshold (e.g., is greater than the single threshold), the UE 120 is not allowed to send the DT in the RACH message or CUR. If the DT fails to meet the single threshold (e.g., is less than or equal to the single threshold), the UE 120 may be allowed to send the DT in the RACH message or CUR. In some aspects, the TBS threshold may include multiple thresholds. For example, BS 110 may configure UE 120 with multiple thresholds. In this case, when the size of the DT is less than the TBS threshold, BS 110 may send an RRC parameter to enable or disable whether an alternative TBS may be selected for UE 120 (e.g., enable or disable whether UE 120 may send the DT on the RACH message). The TBS threshold may include a set of TBS values ​​indicating a set of thresholds for sending the DT on the RACH message. BS 110 may activate one or more thresholds in the set of thresholds for UE 120. Therefore, UE 120 may be configured to use different thresholds in different scenarios. The "TBS threshold" mentioned in this article should be understood to include "a set of TBS thresholds" or "multiple TBS thresholds"

[0070] In some aspects, the TBS threshold may be signaled in the SIB. For example, the TBS threshold may be broadcast to all UEs covered by BS 110. Therefore, all UEs covered by BS 110 may be configured with the same TBS threshold. In this case, BS 110 may provide the TBS threshold in a RACH-ConfigCommon parameter, a RACH-ConfigCommonTwoStepRA-r16 parameter, etc. In some aspects, BS 110 may signal the TBS threshold in dedicated RRC signaling. For example, BS 110 may send an RRC release message including a TBS threshold configuration (e.g., with a suspendConfig parameter to move UE 120 to an RRC inactive state). In some aspects, the TBS threshold may be provided in a RACH-ConfigDedicated parameter.

[0071] As shown in reference numeral 530, if DT is less than or equal to the TBS threshold (block 520 is), the UE 120 may determine whether the DT may be sent in the RACH message. For example, the UE 120 may determine whether the DT satisfies an uplink grant threshold, which indicates whether the UE 120 is allowed to send the DT in the RACH message. The uplink grant threshold may include a TBS threshold for an uplink grant for the payload of the RACH message (e.g., may be configured as part of the TBS threshold). As shown in reference numeral 535, if DT may be sent in the RACH message (block 530 is), the UE 120 may send the DT in the RACH message (e.g., msgA or msg3). For example, the UE 120 may send the DT without entering the RRC connected mode or the RRC active mode, thereby saving UE and network resources associated with entering the RRC connected mode or the RRC active mode.

[0072] As shown in reference numeral 540, if DT cannot be sent in the RACH message (block 530 No), indicating that UE120 is not allowed to send DT in the RACH message, UE 120 can send a CUR request. In this example, the CUR request is sent in the RACH message, although in other examples described herein, the CUR request can be sent in another type of message. CUR can refer to configured uplink resources, pre-configured uplink resources, dedicated uplink resources, dedicated pre-configured uplink resources (D-PUR), etc. CUR can be a resource on which UE 120 can perform uplink transmission without entering RRC connected mode or RRC active mode. In some aspects, CUR can have a TBS sufficient to send DT in a single transport block, which is called a single CUR. In some aspects, CUR can include multiple resources distributed in the time domain so that UE 120 can send data after sending DT, or DT can be sent on multiple resources.

[0073] In some aspects, the UE 120 may send the CUR request based at least in part on the DT being less than or equal to a TBS threshold (indicating that the UE 120 may send the DT without establishing an RRC connection) and the DT being too large to be sent on an RRC message. In some aspects, the UE 120 may send the CUR request based at least in part on a determination that the UE 120 is to perform a subsequent transmission. For example, the UE 120 may send the CUR request based at least in part on a determination that the UE 120 is associated with potential periodic data for a subsequent transmission.

[0074] In some aspects, the UE 120 may send a CUR request in a MAC CE. For example, the MAC CE may include a BSR MAC CE, such as a short BSR with a byte indicating that the short BSR is a CUR request. As another example, the MAC CE may be specific to the CUR request. For example, the MAC CE may include a BSR (e.g., information indicating a logical channel identifier and an amount of data associated with the logical channel identifier), information indicating a traffic mode associated with the DT (e.g., a single transmission traffic mode, a periodic transmission traffic mode), a predicted traffic volume associated with the DT, etc. In some aspects, the UE 120 may send a CUR request in an RRC message, such as an RRC recovery request message. In this case, an RRC parameter of the RRC message (e.g., an RRCResumeRequest parameter, etc.) may indicate the amount of data of the DT and / or the traffic mode associated with the DT. In some aspects, the UE 120 may send a CUR request in a RACH message (such as msgA or msg3). In this case, the CUR request may include a resume identifier, an authentication token (eg, shortResumeMac-I or resumeMAC-I), and the like.

[0075] As shown in reference numeral 545, UE 120 may send DT in CUR. For example, BS 110 may configure UE 120 with CUR based at least in part on CUR request. In some aspects, BS 110 may provide configuration information for configuring CUR via RACH message (such as msgB or msg4). In some aspects, BS 110 may provide configuration information via RRC message (such as RRC release message or RRC message associated with response CUR request). CUR may be a single CUR or multiple (e.g., configured permission, periodicity, semi-persistent, etc.) CUR. In some aspects, multiple CURs may recur until multiple CURs are deactivated or reconfigured. In other words, multiple CURs may have unlimited configurations in the time domain. In some aspects, CUR may be based at least in part on CUR request. In some aspects, the CUR may be based at least in part on subscription information associated with the UE 120 (e.g., indicating a set of services applicable to the UE 120), network traffic information (e.g., network traffic statistics) associated with the UE 120 (e.g., associated with the UE context of the UE 120 or the traffic history of the UE 120), etc.

[0076] As indicated by reference numeral 550, if the TA value of UE 120 is valid (block 510 is), UE 120 may determine whether a CUR is configured for the UE (as indicated by (1)), and whether the CUR is associated with a size (e.g., TBS) sufficient to transmit a DT (as indicated by (2)). For example, in some aspects, the CUR may be configured independently of the RACH procedure. For example, the configuration of the CUR may not involve the RACH procedure. In this case, BS 110 may configure the CUR via RRC dedicated signaling, such as when UE 120 is in an RRC connected state or when UE 120 is in an RRC inactive state.

[0077] As indicated by reference numeral 555, if UE 120 determines that CUR is configured and is associated with a size sufficient to transmit DT (block 550-(1) Yes and (2) Yes), UE 120 may transmit DT on CUR without performing a RACH procedure. For example, since UE 120 has a valid TA, UE 120 may transmit DT without updating the TA via a RACH procedure. Therefore, UE 120 may save communication resources that would otherwise have been used to perform a RACH procedure.

[0078] As indicated by reference numeral 560, if UE 120 determines that CUR is not configured (block 550—(1) No and (2) No), UE 120 may return to block 515. UE 120 may then perform operations described with respect to blocks 520, 525, 530, 535, 540, and 545. Thus, if CUR is not configured, then depending on the size of the DT, UE 120 may selectively send the DT in a RACH message, a CUR (based at least in part on the request CUR), or via an RRC connection.

[0079] As shown in reference numeral 565, if the UE 120 determines that the CUR is configured and is not of sufficient size to carry the DT (block 550-(1) yes and (2) no), the UE 120 may use the CUR to send a CUR request. For example, the CUR request may request a CUR of sufficient size to carry the DT (e.g., as a single CUR or multiple CURs). As shown in reference numeral 570, the UE 120 may receive configuration information to configure the CUR. The configuration information may include at least a portion of the configuration information described in reference numeral 545, and the CUR request is described in more detail in conjunction with reference numeral 540. As shown, the UE 120 may proceed to block 545 after receiving the configuration information. For example, the UE 120 may send the DT on the CUR configured by the configuration information shown in reference numeral 570.

[0080] As mentioned above, Figure 5 are provided as examples. Other examples may differ from those described in Figure 5 As described.

[0081] Figure 6-Figure 9 1 is a diagram illustrating examples 600, 700, 800, and 900 associated with uplink data transmission over configured uplink resources associated with a random access procedure in accordance with various aspects of the present disclosure. Examples 600 and 700 illustrate two-step and four-step RACH procedures in which the UE 120 transmits uplink data over a single CUR, while examples 800 and 900 illustrate two-step and four-step RACH procedures in which the UE 120 transmits uplink data over multiple CURs. For purposes of examples 600, 700, 800, and 900, the UE 120 has determined that uplink data is to be transmitted.

[0082] like Figure 6 As shown by reference numeral 610, UE 120 may send an RRC resume request in RACH msgA. As further shown, the RRC resume request may include a CUR request, such as a MAC CE indicating the CUR request. As shown by reference numeral 620, UE 120 may receive a CUR configuration (e.g., configuration information configuring the CUR) via a RACH message (such as an RRC release message carried by RACH msgB). As shown by reference numeral 630, UE 120 may send uplink data on the CUR configured by the CUR configuration. Figure 6 The example 600 may show Figure 5 The operations shown in blocks 540 and 545 of and illustrate a process for requesting a CUR and performing a single transmission of uplink data associated with a two-step RACH procedure.

[0083] like Figure 7 As shown by reference numeral 710, UE 120 may send RACH msg1 to BS 110. As shown by reference numeral 720, BS 110 may send RACH msg2 to UE 120. As shown by reference numeral 730, UE 120 may send an RRC recovery request in RACHmsg3. As further shown, the RRC recovery request may include a CUR request, such as a MAC CE indicating a CUR request. As shown by reference numeral 740, UE 120 may receive a CUR configuration (e.g., configuration information configuring the CUR) via a RACH message (such as an RRC release message carried by RACH msg4). As shown by reference numeral 750, UE 120 may send uplink data on the CUR configured by the CUR configuration. Figure 7 The example 700 may also correspond to Figure 5Blocks 540 and 545 of , and illustrate a process for requesting a CUR and performing a single transmission of uplink data associated with a four-step RACH procedure. For the entire examples 600 and 700, the UE 120 may be maintained in an RRC inactive state.

[0084] like Figure 8 As shown, by reference numeral 810, UE 120 may send an RRC recovery request in RACH msgA. As further shown, the RRC recovery request may include a CUR request, such as a MAC CE indicating a CUR request. In this case, the CUR request may request multiple CURs, as described in more detail elsewhere herein. As shown by reference numeral 820, UE 120 may receive a CUR configuration (e.g., configuration information for configuring the CUR) via a RACH message (such as an RRC release message carried by RACH msgB). As shown by reference numeral 830, UE 120 may monitor a UE-specific search space (USS) associated with the CUR. For example, the USS may carry control information associated with a specific UE (here, UE 120). Therefore, UE 120 may monitor the USS for scheduling information associated with sending uplink data and subsequent uplink data. For example, as indicated by reference numeral 840, the UE 120 may send uplink data on the CUR configured by the CUR configuration (e.g., based at least in part on receiving scheduling information in a USS indicating that uplink data is to be sent on the CUR). In addition, as indicated by reference numeral 850, the UE 120 may send subsequent uplink data on the CUR (e.g., based at least in part on receiving scheduling information in a USS indicating that subsequent uplink data is to be sent on the CUR). Figure 8 Example 800 may show Figure 5 The operations shown in blocks 540 and 545 of , and illustrate the process of requesting a CUR and performing multiple transmissions of uplink data associated with a two-step RACH procedure.

[0085] like Fig. 9As shown by reference numeral 910, UE 120 may send RACH msg1 to BS 110. As shown by reference numeral 920, BS 110 may send RACH msg2 to UE 120. As shown by reference numeral 930, UE 120 may send an RRC recovery request in RACHmsg3. As further shown, the RRC recovery request may include a CUR request, such as a MAC CE indicating a CUR request. In this case, the CUR request may request multiple CURs, as described in more detail elsewhere herein. As shown by reference numeral 940, UE 120 may receive a CUR configuration (e.g., configuration information configuring the CUR) via a RACH message (such as an RRC release message carried by RACH msg4). As shown by reference numeral 950, UE 120 may monitor a USS associated with the CUR. As indicated by reference numeral 960, UE 120 may send uplink data on the CUR configured by the CUR configuration (e.g., based at least in part on receiving scheduling information in a USS indicating that uplink data is to be sent on the CUR). Additionally, as indicated by reference numeral 970, UE 120 may send subsequent uplink data on the CUR (e.g., based at least in part on receiving scheduling information in a USS indicating that subsequent uplink data is to be sent on the CUR). Fig. 9 Example 900 may show Figure 5 The operations shown in blocks 540 and 545 of , and illustrate the process of requesting a CUR and performing multiple transmissions of uplink data associated with a four-step RACH process.

[0086] As mentioned above, Figure 6-Figure 9 are provided as examples. Other examples may differ from those described in Figure 6 -- Fig. 9 As described.

[0087] Fig.10 1 is a diagram illustrating an example process 1000 performed, for example, by a user equipment (UE) in accordance with various aspects of the present disclosure. Example process 1000 is an example of operations in which a UE (eg, UE 120, etc.) performs operations associated with uplink data transmission via random access or dedicated uplink resources.

[0088] like Fig.10 As shown, in some aspects, process 1000 may include determining that uplink data is to be transmitted in an inactive state (block 1010). For example, as described above, the UE (e.g., using controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, etc.) may determine that uplink data is to be transmitted in an inactive state (e.g., RRC inactive state).

[0089] like Fig.10 As further shown in FIG. 1 , in some aspects, process 1000 may include determining whether the timing advance of the UE is valid (block 1020). For example, as described above, the UE (e.g., using antenna 252, demodulator 254, MIMO detector 256, receive processor 258, controller / processor 280, etc.) may determine whether the timing advance of the UE is valid.

[0090] like Fig.10 As further shown in FIG. 1 , in some aspects, process 1000 may include, if the timing advance is invalid, determining whether the uplink data satisfies the TBS threshold (block 1030). For example, if the timing advance is invalid, the UE (e.g., using receive processor 258, transmit processor 264, controller / processor 280, memory 282, etc.) may determine whether the uplink data satisfies the TBS threshold, as described above.

[0091] like Fig.10 As further shown in , in some aspects, process 1000 may include selectively sending uplink data via an uplink RACH message or a configured uplink resource (block 1040). Additionally or alternatively, process 1000 may include establishing an RRC connection for the uplink data (block 1050). For example, as described above, the UE (e.g., using the receiving processor 258, the transmitting processor 264, the controller / processor 280, the memory 282, etc.) may selectively send uplink data via an uplink RACH message or a configured uplink resource, or establish an RRC connection for the uplink data. In some aspects, the UE may selectively send uplink data via an uplink RACH message or a configured uplink resource, or establish an RRC connection for the uplink data based at least in part on whether the uplink data meets a TBS threshold. In some aspects, as described above, the UE (e.g., using the receive processor 258, the transmit processor 264, the controller / processor 280, the memory 282, etc.) can selectively send uplink data via an uplink RACH message and / or configured uplink resources, or establish an RRC connection for uplink data.

[0092] Process 1000 may include additional aspects, such as any single aspect or any combination of aspects described below, and / or in conjunction with one or more other processes described elsewhere herein.

[0093] In a first aspect, sending uplink data via an uplink RACH message or configured uplink resources is based at least in part on the uplink data being less than or equal to a TBS threshold.

[0094] In a second aspect, alone or in combination with the first aspect, establishing the RRC connection is based at least in part on uplink data greater than a TBS threshold.

[0095] In a third aspect, alone or in combination with one or more of the first and second aspects, sending uplink data via an uplink RACH message or configured uplink resources also includes sending the uplink data via an uplink RACH message if the uplink data fails to meet an uplink permission threshold, wherein the failure to meet the uplink permission threshold indicates that the uplink data can be accommodated in the uplink RACH message, and if the uplink data meets the uplink permission threshold, the uplink data is transmitted via the configured uplink resources.

[0096] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, process 1000 includes sending a request for configured uplink resources prior to sending uplink data via the configured uplink resources, and receiving information configuring the configured uplink resources based at least in part on the request.

[0097] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the request is sent on a RACH message.

[0098] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the request indicates that the configured uplink resources will include a single transport block of sufficient size to carry the uplink data.

[0099] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the request indicates that the configured uplink resources will include multiple transport blocks distributed in time.

[0100] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the request indicates that the configured uplink resources include cyclic transmission blocks until the configured uplink resources are deactivated

[0101] In a ninth aspect, either alone or in combination with one or more of the first to eighth aspects, process 1000 includes sending a request based at least in part on determining that periodic transmission is to be performed by the UE.

[0102] In a tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the request comprises at least one of a media access control control element, an RRC parameter of an RRC recovery request message, or an RRC message.

[0103] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the request comprises a buffer status report message including an indication of the uplink resources requested to be configured.

[0104] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the request comprises a buffer status report and a traffic mode indication associated with the uplink data.

[0105] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the request further comprises a recovery identifier associated with the UE and an authentication token associated with the UE.

[0106] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the request includes an RRC parameter indicating an amount of data associated with the uplink data and a traffic mode indication associated with the uplink data.

[0107] In a fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the information configuring the configured uplink resources is received via a downlink RACH message.

[0108] In a sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, the information configuring the configured uplink resources is received via an RRC release message or an RRC response associated with the request.

[0109] In a seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, the uplink grant threshold and the TBS threshold are configured by the same configuration message.

[0110] In an eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, process 1000 includes receiving an indication of whether to use an alternate TBS size for a TBS threshold.

[0111] In a nineteenth aspect, either alone or in combination with one or more of the first to eighteenth aspects, the TBS threshold is configured with a plurality of values, and wherein the indication indicates a subset of the plurality of values ​​to be used as the TBS threshold.

[0112] In a twentieth aspect, either alone or in combination with one or more of the first to nineteenth aspects, the TBS threshold is associated with a first value associated with a two-step RACH procedure and a second value associated with a four-step RACH procedure, and wherein selectively sending uplink data via the uplink RACH message is based at least in part on the first value if the uplink RACH message is associated with the two-step RACH procedure, and at least in part on the second value if the uplink RACH message is associated with the four-step RACH procedure.

[0113] In a twenty-first aspect, alone or in combination with one or more of the first to twentieth aspects, process 1000 includes receiving system information indicating a TBS threshold.

[0114] In a twenty-second aspect, alone or in combination with one or more of the first to twenty-first aspects, process 1000 includes receiving information indicating a TBS threshold via dedicated RRC signaling.

[0115] In a twenty-third aspect, alone or in combination with one or more of the first to twenty-second aspects, a TBS threshold is associated with a data radio bearer.

[0116] In a twenty-fourth aspect, alone or in combination with one or more of the first to twenty-third aspects, the TBS threshold is UE-specific.

[0117] In a twenty-fifth aspect, alone or in combination with one or more of the first to twenty-fourth aspects, sending uplink data via a RACH message or a configured uplink resource further comprises performing a single transmission on the configured uplink resource.

[0118] In a twenty-sixth aspect, alone or in combination with one or more of the first to twenty-fifth aspects, sending uplink data via a RACH message or a configured uplink resource further comprises performing multiple transmissions at corresponding timings of the configured uplink resources.

[0119] In aspect twenty-seven, alone or in combination with one or more of aspects one to twenty-six, if the timing advance is determined to be valid, process 1000 includes determining whether the configured uplink resources are configured and whether the uplink data can be accommodated in the configured uplink resources, and if the configured uplink resources are configured and the uplink data can be accommodated in the configured uplink resources, sending uplink data on the configured uplink resources.

[0120] In a twenty-eighth aspect, either alone or in combination with one or more of the first to twenty-seventh aspects, process 1000 includes sending a request for other configured uplink resources and sending uplink data on the other configured uplink resources.

[0121] In a twenty-ninth aspect, either alone or in combination with one or more of the first to twenty-eighth aspects, the other configured uplink resources have a larger transport block size than the configured uplink resources.

[0122] In a thirtieth aspect, alone or in combination with one or more of the first to twenty-ninth aspects, a request for other configured uplink resources is sent in the configured uplink resources.

[0123] In the thirty-first aspect, alone or in combination with one or more of the first to thirtieth aspects, process 1000 includes: initiating a RACH process, determining whether the uplink data meets the TBS threshold, and selectively, based at least in part on whether the uplink data meets the TBS threshold, sending uplink data in connection with the RACH process, sending a request for configured uplink resources, or establishing an RRC connection for the uplink data.

[0124] In a thirty-first aspect, alone or in combination with one or more of the first to thirtieth aspects, process 1000 includes receiving configuration information indicating configured uplink resources.

[0125] In a thirty-second aspect, either alone or in combination with one or more of the first to thirty-first aspects, the configuration information is based at least in part on subscription information associated with the UE.

[0126] In a thirty-third aspect, either alone or in combination with one or more of the first to thirty-second aspects, the configuration information is based at least in part on network service information associated with the UE.

[0127] In a thirty-fourth aspect, alone or in combination with one or more of the first to twenty-third aspects, the configured uplink resources are configured independent of whether the UE determines that uplink data is to be sent.

[0128] In a thirty-fifth aspect, alone or in combination with one or more of the first to twenty-fourth aspects, the UE is maintained in an inactive state when sending uplink data via an uplink RACH message or a configured uplink resource.

[0129] although Fig.10 Example blocks of process 1000 are shown, but in some aspects, process 1000 may include more Fig.10The blocks depicted in the process 1000 may be more blocks, fewer blocks, different blocks, or blocks in a different arrangement. Additionally or alternatively, two or more blocks of the process 1000 may be executed in parallel.

[0130] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit these aspects to the precise forms disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of these aspects.

[0131] As used herein, the term "component" is intended to be broadly interpreted as hardware, firmware, and / or a combination of hardware and software. As used herein, a processor is implemented in hardware, firmware, and / or a combination of hardware and software. It is apparent that the systems and / or methods described herein may be implemented in different forms of hardware, firmware, and / or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit these aspects. Therefore, the operation and behavior of the systems and / or methods are described herein without reference to specific software code, and it should be understood that software and hardware may be designed to implement the systems and / or methods based at least in part on the description herein.

[0132] As used herein, satisfying a threshold may refer to a value greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0133] Even if specific combinations of features are stated in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of the various aspects. In fact, many of these features can be combined in ways that are not specifically stated in the claims and / or disclosed in the specification. Although each dependent claim listed below may be directly dependent on only one claim, the disclosure of the various aspects includes the combination of each dependent claim with each other claim in the claim set. A phrase referring to "at least one" of a series of items refers to any combination of these items, including single members. For example, "at least one of a, b or c" is intended to cover a, b, c, ab, ac, bc and abc, as well as any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbb, bbc, cc and cccc or any other order of a, b and c).

[0134] Unless explicitly described, any element, action or instruction used in this article should not be interpreted as critical or necessary. In addition, as used herein, the articles "one" and "an" are intended to include one or more items and can be used interchangeably with "one or more". In addition, as used herein, the article "the" is intended to include one or more items related to the article "the", and can be used interchangeably with "the one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items (e.g., related items, unrelated items, combinations of related and unrelated items, etc.), and can be used interchangeably with "one or more". If only one item is referred to, the phrase "only one" or similar language is used. In addition, as used herein, the terms "have", "have", "have" and other terms are intended to be open terms. In addition, the phrase "based on" is intended to mean "based at least in part on", unless otherwise clearly stated. In addition, as used herein, the term "or" is inclusive when used in a series, and can be used interchangeably with "and / or", unless otherwise clearly stated (e.g., if used in combination with "either" or "only one").

Claims

1. A method of wireless communication performed by a user equipment (UE), comprising: In an inactive state, determining that uplink small data is to be sent; Determine whether the timing advance of the UE is valid; If the timing advance is invalid, determining whether the uplink small data meets a transport block size (TBS) threshold; and Based at least in part on whether the uplink small data satisfies a TBS threshold, selectively: If the uplink small data is less than or equal to the TBS threshold, the uplink small data is sent via an uplink random access channel (RACH) message or a configured uplink resource, or If the uplink small data is greater than the TBS threshold, a radio resource control (RRC) connection is established for the uplink small data. Wherein, sending uplink small data via an uplink RACH message or a configured uplink resource also includes: If the uplink small data fails to meet the uplink grant threshold, sending the uplink small data via an uplink RACH message, wherein the failure to meet the uplink grant threshold indicates that the uplink small data can be accommodated in the uplink RACH message; and If the uplink small data satisfies the uplink grant threshold, the uplink small data is sent via the configured uplink resources.

2. The method according to claim 1, wherein: When uplink small data is transmitted via an uplink RACH message or configured uplink resources, the UE is maintained in an inactive state.

3. The method according to claim 1, further comprising: Before sending uplink small data via the configured uplink resources, sending a request for the configured uplink resources; and Based at least in part on the request, information configuring uplink resources is received.

4. The method according to claim 3, wherein: The request is sent on a RACH message.

5. The method according to claim 3, wherein: The request indicates that the configured uplink resources will include a single transport block of sufficient size to carry the uplink small data.

6. The method according to claim 3, wherein: The request indicates that the configured uplink resources will include multiple transport blocks distributed in time.

7. The method according to claim 3, wherein: The request indicates that the configured uplink resources include cyclic transport blocks until the configured uplink resources are deactivated.

8. The method according to claim 3, further comprising: The request is sent based at least in part on determining that periodic transmissions are to be performed by the UE.

9. The method according to claim 3, wherein: The request includes at least one of the following: Media Access Control Element, RRC parameters of the RRC Recovery Request message, or RRC message.

10. The method according to claim 9, wherein: The request comprises a buffer status report message including an indication of the uplink resources requested to be configured.

11. The method according to claim 9, wherein: The request includes a buffer status report and a traffic mode indication associated with uplink small data.

12. The method according to claim 9, wherein: The request includes an RRC parameter indicating an amount of data associated with the uplink small data and a traffic mode indication associated with the uplink small data.

13. The method according to claim 3, wherein: Information configuring the configured uplink resources is received via a downlink RACH message.

14. The method according to claim 3, wherein: The information configuring the configured uplink resources is received via an RRC release message or an RRC response associated with the request.

15. The method according to claim 1, wherein: The uplink grant threshold and the TBS threshold are configured by the same configuration message.

16. The method according to claim 15, further comprising: An indication is received whether to use an alternate TBS size for the TBS threshold.

17. The method according to claim 1, further comprising: System information indicating a TBS threshold is received.

18. The method of claim 1, further comprising: Information indicating the TBS threshold is received via dedicated RRC signaling.

19. The method according to claim 1, wherein: The TBS threshold is associated with a data radio bearer.

20. The method according to claim 1, wherein: The TBS threshold is specific to the UE.

21. The method according to claim 1, wherein: Sending uplink small data via the RACH message or the configured uplink resources also includes performing a single transmission on the configured uplink resources.

22. The method according to claim 1, wherein: Sending uplink small data via the RACH message or the configured uplink resources also includes performing multiple transmissions at corresponding opportunities of the configured uplink resources.

23. The method according to claim 1, wherein: If the timing advance is determined to be valid, the method further comprises: determining whether the configured uplink resources are configured and whether the uplink small data can be accommodated in the configured uplink resources; and If the configured uplink resources are configured and the uplink small data can be accommodated in the configured uplink resources, the uplink small data is transmitted on the configured uplink resources.

24. The method according to claim 23, wherein: If the uplink small data cannot be accommodated in the configured uplink resources, the method further includes: sending a request for additional configured uplink resources; and The uplink small data is sent on other configured uplink resources.

25. The method according to claim 24, wherein: The other configured uplink resources have a larger transport block size than the configured uplink resources.

26. The method according to claim 24, wherein: Requests for other configured uplink resources are sent within the configured uplink resources.

27. The method according to claim 26, wherein: If the configured uplink resource is not configured, the method further comprises: Initiate RACH process; Determining whether the uplink small data meets the TBS threshold; and Based at least in part on whether the uplink small data satisfies a TBS threshold, selectively: Sending uplink small data in connection with the RACH procedure, Send a request for configured uplink resources, or Establish an RRC connection for uplink small data.

28. The method of claim 1, further comprising: Configuration information indicating configured uplink resources is received.

29. The method according to claim 28, wherein: The configuration information is based at least in part on subscription information associated with the UE.

30. A user equipment (UE), comprising: one or more memories; and One or more processors, communicatively coupled to the one or more memories, configured to: In an inactive state, determining that uplink small data is to be sent; Determine whether the timing advance of the UE is valid; If the timing advance is invalid, determining whether the uplink small data meets a transport block size (TBS) threshold; and Based at least in part on whether the uplink small data satisfies a TBS threshold, selectively: If the uplink small data is less than or equal to the TBS threshold, the uplink small data is sent via an uplink random access channel (RACH) message or a configured uplink resource, or If the uplink small data is greater than the TBS threshold, a radio resource control (RRC) connection is established for the uplink small data. Wherein, sending uplink small data via an uplink RACH message or a configured uplink resource also includes: If the uplink small data fails to meet the uplink grant threshold, sending the uplink small data via an uplink RACH message, wherein the failure to meet the uplink grant threshold indicates that the uplink small data can be accommodated in the uplink RACH message; and If the uplink small data satisfies the uplink grant threshold, the uplink small data is sent via the configured uplink resources.

31. A non-transitory computer-readable medium storing instructions, the instructions comprising: One or more instructions, when executed by one or more processors of a user equipment (UE), cause the one or more processors to: In an inactive state, determining that uplink small data is to be sent; Determine whether the timing advance of the UE is valid; If the timing advance is invalid, determining whether the uplink small data meets a transport block size (TBS) threshold; and Based at least in part on whether the uplink small data satisfies a TBS threshold, selectively: If the uplink small data is less than or equal to the TBS threshold, the uplink small data is sent via an uplink random access channel (RACH) message or a configured uplink resource, or If the uplink small data is greater than the TBS threshold, a radio resource control (RRC) connection is established for the uplink small data. Wherein, sending uplink small data via an uplink RACH message or a configured uplink resource also includes: If the uplink small data fails to meet the uplink grant threshold, sending the uplink small data via an uplink RACH message, wherein the failure to meet the uplink grant threshold indicates that the uplink small data can be accommodated in the uplink RACH message; and If the uplink small data satisfies the uplink grant threshold, the uplink small data is sent via the configured uplink resources.

32. An apparatus comprising: means for determining that uplink small data is to be sent in an inactive state; means for determining whether the timing advance of the equipment is valid; means for determining whether the uplink small data meets a transport block size (TBS) threshold if the timing advance is invalid; and for selectively: based at least in part on whether the uplink small data satisfies a TBS threshold; If the uplink small data is less than or equal to the TBS threshold, the uplink small data is sent via an uplink random access channel (RACH) message or a configured uplink resource, or means for establishing a radio resource control (RRC) connection for the uplink small data if the uplink small data is greater than the TBS threshold, Wherein, sending uplink small data via an uplink RACH message or a configured uplink resource also includes: If the uplink small data fails to meet the uplink grant threshold, sending the uplink small data via an uplink RACH message, wherein the failure to meet the uplink grant threshold indicates that the uplink small data can be accommodated in the uplink RACH message; and If the uplink small data satisfies the uplink grant threshold, the uplink small data is sent via the configured uplink resources.

Images