TW202333527A - Techniques for uplink control information transmission with small data transmission - Google Patents

Abstract

Methods, systems, and devices for wireless communications are described. A user equipment (UE) may be configured to receive, from a base station, control signaling identifying a first set of resources for data transmissions and a second set of resources for uplink control information (UCI) transmission by the UE when the UE is in an inactive state or an idle state. The UE may generate, when the UE is in one of the inactive state or the idle state, a UCI message based on the second set of resources. The UE may then transmit, to the base station when the UE in the one of the inactive state or the idle state, a data message on at least a portion of the first set of resources and the UCI message on the second set of resources.

Description

Technology used for uplink control information transmission together with small data transmission

cross reference This patent application claims the priority of provisional patent application No. PCT/CN2021/122764 filed by LEI et al. on October 9, 2021, titled "TECHNIQUES FOR UPLINK CONTROL INFORMATION TRANSMISSION WITH SMALL DATA TRANSMISSION". The application has been assigned to the assignee hereof and its entire contents are expressly incorporated herein by reference.

This case is about wireless communications, including technologies for the transmission of uplink control information (UCI) along with small data transmission.

Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, etc. These systems can support communications with multiple users by sharing available system resources (eg, time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (eg, Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems system (which may be called a New Radio (NR) system). These systems may employ technologies such as code division multiplexing (CDMA), time division multiplexing (TDMA), frequency division multiplexing (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier Leaf transform spread spectrum orthogonal division multiplexing (DFT-S-OFDM). The wireless multiple access communication system may include one or more base stations or one or more network access nodes, each base station or network access node supporting multiple communication devices at the same time (which may be otherwise referred to as User Equipment (UE)) communication.

Some wireless communication systems can configure the UE to send Small Data Transmissions (SDT) when in an inactive or idle state. The use of SDT can enable the UE to transmit a small amount of data to the network without establishing a complete wireless connection to the network (for example, by entering the active state), which can reduce the control signal transfer management burden. However, the utility of some conventional SDT techniques is limited.

The techniques described relate to improved methods, systems, apparatus and devices for techniques that support the transmission of uplink control information (UCI) along with small data transmissions. In general, aspects of this document provide techniques that enable user equipment (UE) to operate in an inactive state (e.g., radio resource control (RRC) inactive state) or in an idle state (e.g., RRC idle state). status), the Uplink Control Information (UCI) message associated with the Small Data Transfer (SDT) is sent. Specifically, aspects of this proposal support various SDT configurations that define different sets of rules or conditions that UEs can use to determine whether they can operate in conjunction with SDT while in an inactive or idle state. Send UCI message. In some cases, the UE may receive control signaling indicating the set of resources used to transmit SDT and UCI messages when the UE is in an inactive or idle state. In some cases, the control signaling may configure the UE with separate sets of resources for transmitting SDT and UCI messages, where in other cases the UE may be configured to use the same set of resources to transmit UCI messages and SDT messages. Multitasking. In the context of Random Access SDT (RA-SDT) configuration, control signaling may include information on a random access procedure that configures the UE with A collection of resources for random access messages. In contrast, in the context of a configured Granted SDT (CG-SDT) configuration, the UE may receive messages (e.g., Radio Resource Control (RRC) Release messages) that release the UE from the active state to the inactive or idle state. , where the message configures the UE with a resource set for SDT and UCI messages (for example, physical uplink control channel (PUCCH) resources, physical uplink shared channel (PUSCH) resources).

A method is described. The method may include receiving a control signaling from a base station identifying a first set of resources used by the UE for data transmission and a second resource used for UCI transmission when the UE is in an inactive or idle state. set; when the UE is in one of the inactive state or the idle state, generate a UCI message based on the second resource set; and when the UE is in the one of the inactive state or the idle state , sending the data message to the base station on at least part of the first resource set, and sending the UCI message to the base station on the second resource set.

A device is described. The apparatus may include a processor, memory coupled to the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the device to: receive a control signal transfer from a base station, the control signal transfer identifying a third channel used by the UE for data transmission when the UE is in an inactive or idle state. a resource set and a second resource set for UCI transmission; when the UE is in one of the inactive state or the idle state, generating a UCI message based on the second resource set; and when the UE is in the inactive state In one of the active state or the idle state, a data message is sent to the base station on at least a part of the first resource set, and the UCI message is sent to the base station on the second resource set.

Another device is described. The apparatus may include means for receiving a control signal transfer from a base station identifying a first set of resources used by the UE for data transmission when the UE is in an inactive or idle state and for UCI transmission. a second resource set; a component for generating a UCI message based on the second resource set when the UE is in one of the inactive state or the idle state; and a component for generating a UCI message when the UE is in the inactive state Or the component of the idle state, sending a data message to the base station on at least a part of the first resource set, and sending the UCI message to the base station on the second resource set.

Describes a non-transitory computer-readable medium on which code is stored. The code may include instructions executable by the processor to receive a control signal transfer from a base station, the control signal transfer identifying a first step for data transmission by the UE when the UE is in an inactive or idle state. a resource set and a second resource set for UCI transmission; when the UE is in one of the inactive state or the idle state, generating a UCI message based on the second resource set; and when the UE is in the inactive state In one of the state or the idle state, a data message is sent to the base station on at least a part of the first resource set, and the UCI message is sent to the base station on the second resource set.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the control signal transmission may include: operations, characteristics, and operations for receiving a random access message for a random access procedure from the base station. , component or instruction, the random access message identifies the first resource set and the second resource set.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the control signal transfer may include: receiving and transferring the UE from the base station while the UE is in an active state. Operations, features, components, or instructions associated with the release of the active state to the inactive state or the idle state, wherein the message identifies the first set of resources and the second set of resources.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the UCI message may include: for, together with a random access message of a random access procedure, on the second resource set The operation, characteristic, component, or instruction that sends this UCI message.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the methods, apparatus, and non-transitory computer-readable media may further include: for identifying timing for the UE based on An advance (TA) may be available to send operations, features, components or instructions of the UCI message along with the random access message.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the methods, apparatus, and non-transitory computer-readable media may further include: for identifying the TA for the UE. The operations, features, components, or instructions of the UCI message may be sent with the random access message after they have been invalidated.

Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving delivery of the control signal when the UE may be in an active state. Delivery indicates a set of multiple transmission opportunities for the data transmission, the set of multiple transmission opportunities including the first resource set, wherein the data message and the UCI message may be transmitted in the set of multiple transmission opportunities Sent within the opportunity.

In some examples of the methods, devices, and non-transitory computer-readable media described herein, sending the data message and the UCI message may include: multiplexing the data message and the UCI message within the transmission opportunity. operations, features, components, or instructions.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the data message and the UCI message may include operations, features, components, or instructions for: The UCI message is sent in the first transmission opportunity in a set of transmission opportunities to avoid sending the data message in the first transmission opportunity; based on avoiding sending the data message, the UCI is sent in the first transmission opportunity message; and based on sending the UCI message in the first transmission opportunity, sending the data message in a second transmission opportunity in the set of multiple transmission opportunities.

Some examples of the methods, devices and non-transitory computer-readable media described herein may also include: receiving, through the control signal transmission, the UE multiplexing the UCI and the data message in the second resource. The second resource set may be included in the first resource set according to the indicated operations, features, components or instructions in the set, and the sending of the data message and the UCI message may be based on the indication.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second set of resources includes a set of common uplink control resources, a set of dedicated uplink control resources, or any combination thereof, and The first resource set includes an uplink shared resource set.

Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, and components for sending the UCI message based on identifying that the TA for the UE may be valid. or instructions.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, identifying that the TA may be valid for the UE may include operations, features, components, or Instructions: Identify: the first TA for the UCI message may be valid, the second TA for the data message may be valid, and the third TA for both the UCI message and the data message may be valid, or any combination thereof.

Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means for receiving, via the control signal transmission, an indication of suspension of TA authentication at the UE. or instructions, wherein sending the UCI message may be at least partially in response to the suspension of TA verification.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the UCI message includes a hybrid automatic repeat request (HARQ) feedback in response to: contention resolution message, downlink Control plane message, downlink user plane message, RRC release message, or any combination thereof.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the UCI message includes: a first CSI report that is smaller than a second channel status information (CSI) report for the active state, a beam A fault report, a Bandwidth Part (BWP) index, a coverage enhancement request, a request to terminate the set of data messages that includes this data message, or any combination thereof.

Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for receiving a control message from the base station indicating that the UCI message is associated with One or more parameters of the link, the one or more parameters include resource index, transmit beam index, number of repetitions, frequency hopping scheme, orthogonal cover code (OCC), or any combination thereof, wherein the control message includes downlink channel control information message, media access control-control element message, RRC message, system information message, or any combination thereof.

A method for wireless communications at a base station is described. The method may include sending a control signaling to the UE identifying a first set of resources used by the UE for data transmission and a second set of resources used for UCI transmission when the UE is in an inactive or idle state. ; and receiving data messages from the UE on at least a portion of the first resource set and receiving UCI from the UE on the second resource set when the UE is in one of the inactive state or the idle state. message.

An apparatus for wireless communications at a base station is described. The apparatus may include a processor, memory coupled to the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the device to: send a control signal transfer to a UE, the control signal transfer identifies a first step used by the UE for data transmission when the UE is in an inactive state or an idle state. a resource set and a second resource set for UCI transmission; and receiving data messages from the UE on at least a portion of the first resource set when the UE is in one of the inactive state or the idle state, and Receive UCI messages from the UE on the second resource set.

Another apparatus for wireless communications at a base station is described. The apparatus may include means for sending a control signal transfer to the UE identifying a first set of resources used by the UE for data transmission when the UE is in an inactive or idle state and a first set of resources used for UCI transmission. a second set of resources; and for receiving a data message from the UE on at least a portion of the first set of resources when the UE is in one of the inactive state or the idle state, and on the second set of resources Component to receive UCI messages from this UE.

A non-transitory computer-readable medium storing code for wireless communications at a base station is described. The code may include instructions executable by the processor to send a control signal transfer to the UE identifying a first resource used by the UE for data transmission when the UE is in an inactive or idle state. set and a second set of resources for UCI transmission; and when the UE is in one of the inactive state or the idle state, receiving a data message from the UE on at least a portion of the first set of resources, and Receive UCI messages from the UE on the second resource set.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the control signaling may include operations, features, components, or instructions for sending random access messages of the random access procedure. , the random access message identifies the first resource set and the second resource set.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the control signaling may include: for sending and transferring the control signal to the UE when the UE may be in an active state. Operations, features, components, or instructions associated with the release of the active state to the inactive state or the idle state, wherein the message identifies the first set of resources and the second set of resources.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the UCI message may include: for, together with a random access message of a random access procedure, on the second resource set The operation, feature, component, or instruction that receives the UCI message.

Some examples of the methods, devices, and non-transitory computer-readable media described herein may also include: transmitting, through the control signal transmission, for the UE to multiplex the UCI and the data message on the second resource. The second resource set may be included in the first resource set to indicate the operations, features, components, or instructions within the set, wherein receipt of the data message and the UCI message may be at least in part responsive to sending the indication.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second set of resources includes a set of common uplink control resources, a set of dedicated uplink control resources, or any combination thereof, and The first resource set includes an uplink shared resource set.

Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means for sending, via the control signaling, an indication of the suspension of TA authentication at the UE. or instructions, wherein receipt of the UCI message may be in response, at least in part, to the suspension of TA verification.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the UCI message includes HARQ feedback in response to: contention resolution message, downlink control plane message, downlink User plane message, RRC release message, or any combination thereof.

In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the UCI message includes: a first CSI report that may be smaller than a second CSI report for an active state, a beam failure report, a BWP An index, a coverage enhancement request, a request to terminate the set of data messages that includes the data message, or any combination thereof.

Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for sending a control message to the UE indicating that the UCI message is associated with One or more parameters, the one or more parameters include resource index, transmit beam index, number of repetitions, frequency hopping scheme, OCC, or any combination thereof, wherein the control message includes downlink control information message, media storage Get control-control element messages, RRC messages, system information messages, or any combination thereof.

Some wireless communication systems can configure user equipment (UE) to send small data transmissions (SDT) when in an inactive or idle state. The use of SDT enables the UE to transmit a small amount of data to the network without establishing a full wireless connection to the network (for example, by entering the active state), which can reduce the control signal transfer management burden. Some systems may support one or both of two different types of SDT configurations: (1) Random Access SDT (RA-SDT), and (2) Configured Authorization SDT (CG-SDT). In RA-SDT, when the UE is in inactive or idle state, the UE can send SDT together with the random access message transmitted during the random access procedure with the network. In contrast, in CG-SDT, the network can configure the UE with a set of transmission opportunities that can be used to transmit SDT when the UE is in an inactive or idle state.

In some cases, the UE may have control information that needs to be sent to the network (eg, data for uplink control information (UCI) messages). However, conventional wireless communication systems only enable UCI messages to be transmitted when the UE is in an active state. Therefore, according to some conventional technologies, before the UE can transmit UCI messages, the UE may be required to establish a complete wireless connection with the network, which may lead to an increase in signal transmission management burden, power consumption, and UCI delay.

Therefore, various aspects of the content of this application are directed to technologies that enable the UE to send UCI messages associated with SDT when in an inactive or idle state. Specifically, various aspects of this proposal implement different SDT configurations that define different sets of rules or conditions that UEs can use to determine whether they can send UCI messages in the inactive or idle state. Along with SDT. For purposes of this context, the term "SDT" may represent data messages with a size less than a certain threshold size. In some cases, the threshold size for SDT may be preconfigured, configured/signaled by the network, or both.

In some cases, the UE may receive control signaling indicating the set of resources used to transmit SDT and UCI messages when the UE is in an inactive or idle state. In some cases, the control signaling may configure the UE with separate sets of resources for transmitting SDT and UCI messages, where in other cases the UE may be configured to use the same set of resources to transmit UCI messages and SDT messages. Multitasking.

In the context of RA-SDT, control signaling may include random access procedure messages that configure the UE with a set of resources for random access messages that may be used to send SDT and/or UCI messages. In contrast, in the context of CG-SDT, the UE may receive a message (e.g., a radio resource control (RRC) release message) for releasing the UE from an active state to an inactive or idle state, where the message configures the UE There are resource sets for SDT and UCI messages (e.g., Physical Uplink Control Channel (PUCCH) resources, Physical Uplink Shared Channel (PUSCH) resources). The UCI message sent by the UE in the inactive or idle state may include hybrid automatic repeat request (HARQ) feedback information, UE auxiliary information (for example, channel status information (CSI) report, preferred bandwidth part (BWP)), etc. In some cases, the UE may be required to perform timing advance (TA) verification for SDT and/or UCI messages.

As used herein, the active state may represent an RRC active state or an RRC connected state (eg, RRC CONNECTED or NR-RRC CONNECTED), such as where the UE operates according to a connected mode. An active state may also represent other states that have the characteristics described herein for an active state or perform operations for an active state. Examples of characteristics or operations performed by a UE operating in the active state (e.g., connected state) include: in the 5G core (5GC) and the base station (e.g., radio access network for 5G (NG-RAN) ); the UE access layer context stored in the base station (e.g., NG-RAN) and the UE; the base station that knows the cell to which the UE belongs ( For example, NG-RAN); transmission/transmission of unicast data to or from the UE; and network controlled mobility (which includes measurements).

As used herein, the inactive state may represent an RRC inactive state (eg, RRC INACTIVE or NR-RRC INACTIVE), for example, where the UE operates according to connected mode. The inactive state may also represent other states that have the characteristics described herein for the inactive state or perform operations for the inactive state. Examples of characteristics or operations performed by a UE operating in an inactive state include: broadcast of system information by the base station; cell reselection mobility; paging initiated by the base station (e.g., NG-RAN) (RAN paging); RAN-based notification area (RNA) managed by NG-RAN; DRX configured by NG-RAN for RAN paging; establishing a 5GC to NG-RAN connection for UE (one or both of the control plane and user plane) ; Store the UE AS context in NG-RAN and UE; and NG-RAN knows the RNA to which the UE belongs.

As used herein, the idle state may represent an RRC idle state (eg, RRC idle or NR-RRC idle), eg, the UE is operating according to an idle mode. The idle state may also represent other states having the characteristics described herein for the idle state or performing operations for the idle state. Examples of characteristics or operations performed by a UE operating in idle state include: Public Land Mobile Network (PLMN; selection; system information broadcast; cell reselection mobility; paging for mobile station termination data initiated by 5GC; Paging for the mobile station termination data area is managed by 5GC; and discontinuous reception of core network paging configured by the non-access layer.

Upon power-up, the UE may enter an idle (eg, disconnected) state, and in some cases the UE may not have registered with the network. The UE may then perform an attach procedure to enter an active (eg, and connected) state. In the event that the UE enters an inactive (eg, connected) state, the connected state may be suspended. In active and inactive states, the UE can still register with and connect to the network. The UE can recover and return from the inactive state to the active state. However, if the connection to the network (eg, to a base station) fails, the UE may return to the inactive state to the idle state. Similarly, while the UE is in the active state, the UE may return to the idle state if the UE detaches, or if the connection to the network (eg, to a base station) fails.

The UE can also operate in idle mode DRX or connected mode DRX. In idle mode DRX, when in the idle state, the UE wakes up periodically according to the DRX cycle to monitor paging messages, and returns to sleep mode if the paging message is not intended for the UE. In connected mode DRX, when in the connected state, the UE can transition between the DRX active state and the DRX sleep state according to the DRX cycle (for example, long cycle type or short cycle type), and monitor the entity downlink during the DRX active state. channel control channel (PDCCH).

Aspects of the content of this case are initially described in the context of wireless communication systems. Various aspects of this case content are further described in the context of sample resource configurations and sample program flows. Aspects of the content of the present application are further illustrated and described by and with reference to device diagrams, system diagrams, and flow diagrams related to technologies for UCI transmission with small data transmission.

FIG. 1 illustrates an example of a wireless communication system 100 that supports technology for UCI transmission together with small data transmission, according to various aspects of the subject matter. The wireless communication system 100 may include one or more base stations 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, LTE-Advanced (LTE-A) network, LTE-A Pro network, or New Radio (NR) network. In some examples, the wireless communication system 100 may support enhanced broadband communications, ultra-reliable communications, low-latency communications, or communications with low-cost and low-complexity devices, or any combination thereof.

Base stations 105 may be dispersed throughout a geographic area to form wireless communication system 100, and may be devices of different forms or with different capabilities. Base station 105 and UE 115 may communicate wirelessly via one or more communication links 125 . Each base station 105 may provide a coverage area 110 over which the UE 115 and the base station 105 may establish one or more communication links 125 . Coverage area 110 may be an example of a geographic area over which base station 105 and UE 115 may support transmitting signals in accordance with one or more radio access technologies.

UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary, mobile, or both at different times. UE 115 may be a device of different forms or with different capabilities. Some example UEs 115 are illustrated in Figure 1 . The UEs 115 described herein are capable of communicating with various types of devices, such as other UEs 115, base stations 105, or network devices (e.g., core network nodes, relay devices, Integrated Access and Backhaul (IAB) nodes, or other network equipment), as shown in Figure 1.

The base station 105 can communicate with the core network 130, communicate with each other, or perform both of the above operations. For example, the base station 105 may interface with the core network 130 via one or more backhaul links 120 (eg, via S1, N2, N3, or other interfaces). Base stations 105 may communicate with each other directly (eg, directly between base stations 105 ) on backhaul links 120 (eg, via X2, Xn, or other interfaces), or indirectly (eg, via core network 130 ) communicate with each other, or perform both of the above operations. In some examples, backhaul link 120 may be or include one or more wireless links.

One or more of the base stations 105 described herein may include or may be referred to by those skilled in the art as a base station transceiver, wireless base station, access point, wireless transceiver, Node B, evolved node B (eNB), Next Generation Node B or Gigabit Node B (either may be referred to as gNB), Home Node B, Home Evolved Node B, or some other appropriate terminology.

UE 115 may include or may be referred to as a mobile device, wireless device, remote device, handheld device, or user equipment, or some other appropriate terminology, where "device" may also be referred to as a unit, station, terminal, or client. end and other examples. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet, laptop, or personal computer. In some examples, UE 115 may include or be referred to as a wireless area loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine Type Communications (MTC) device, among other examples, It may be implemented in various items such as appliances, or vehicles, or instruments, among other examples.

The UEs 115 described herein are capable of communicating with various types of devices, such as other UEs 115 that may sometimes act as relays, as well as base stations 105 and network equipment, including, among other examples, macro eNBs or gNBs, small cell eNBs Or gNB, or relay base station, as shown in Figure 1.

UE 115 and base station 105 may communicate wirelessly with each other via one or more communication links 125 over one or more carriers. The term “carrier” may represent a collection of radio frequency spectrum resources with a defined physical layer structure used to support communication link 125 . For example, a carrier used for communication link 125 may include a portion of a radio frequency spectrum band (e.g., a bandwidth portion (BWP)) that is configured as specified for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro , NR) to operate on one or more physical layer channels. Each physical layer channel may carry acquisition signaling (eg, synchronization signals, system information), control signaling to coordinate the operation of the carrier, user data, or other signaling. The wireless communication system 100 may support communications with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers.

In some examples (eg, in a carrier aggregation configuration), a carrier may also have acquisition signaling or control signaling for coordinating operations for other carriers. A carrier may be associated with a frequency channel (eg, an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute Radio Frequency Channel Number (EARFCN)) and may be placed according to a channel grid for discovery by UE 115 . The carrier may operate in a standalone mode, where the UE 115 may initially acquire and connect via the carrier, or the carrier may operate in a non-standalone mode, where a different carrier (eg, of the same or different radio access technology) is used to anchor the carrier. Definite connection.

The communication link 125 shown in the wireless communication system 100 may include uplink transmissions from the UE 115 to the base station 105 or downlink transmissions from the base station 105 to the UE 115 . A carrier may carry downlink or uplink communications (eg, in FDD mode) or may be configured to carry both downlink and uplink communications (eg, in TDD mode).

A carrier may be associated with a specific bandwidth of the radio frequency spectrum, and in some examples, the carrier bandwidth may be referred to as the carrier or "system bandwidth" of the wireless communications system 100 . For example, the carrier bandwidth may be one of several determined bandwidths for a carrier of a particular radio access technology (eg, 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)). Devices of wireless communication system 100 (e.g., base station 105, UE 115, or both) may have hardware settings to support communications over a specific carrier bandwidth, or may be configurable to support a carrier in a set of carrier bandwidths. communication over bandwidth. In some examples, wireless communications system 100 may include base stations 105 or UEs 115 that support simultaneous communications via carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate on a portion (eg, subband, BWP) or all of the carrier bandwidth.

The signal waveform transmitted on the carrier can be composed of multiple subcarriers (e.g., using multi-carrier modulation such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread spectrum OFDM (DFT-S-OFDM). (MCM) technology). In a system using MCM technology, a resource element may consist of a symbol period (eg, the duration of a modulation symbol) and a subcarrier, where the symbol period and subcarrier spacing are inversely related. The number of bits carried by each resource element may depend on the modulation scheme (eg, the order of the modulation scheme, the coding rate of the modulation scheme, or both). Therefore, the more resource elements the UE 115 receives and the higher the order of the modulation scheme, the higher the data rate for the UE 115 can be. Wireless communication resources may represent a combination of radio frequency spectrum resources, time resources, and spatial resources (eg, spatial layers or beams), and the use of multiple spatial layers may further increase the data rate or data integrity for communication with UE 115 .

One or more digitization schemes for the carrier may be supported, where the digitization scheme may include subcarrier spacing (Δf) and cyclic prefixes. A carrier may be divided into one or more BWPs with the same or different bit schemes. In some examples, UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier is active at a given time, and communications for UE 115 may be limited to one or more active BWPs.

can be expressed in basic time units (which may for example be referred to as second sampling period, where May represent the maximum supported subcarrier spacing, and The time interval for the base station 105 or UE 115 may be expressed as a multiple of the maximum supported discrete Fourier transform (DFT) size). The time intervals of communication resources can be organized according to wireless frames each having a specified duration (eg, 10 milliseconds (ms)). Each radio frame can be identified by a system frame number (SFN) (eg, ranging from 0 to 1023).

Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided (eg, in the time domain) into multiple subframes, and each subframe may be further divided into multiple time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot can consist of multiple symbol periods (e.g., depending on the length of the cyclic prefix appended before each symbol period). In some wireless communication systems 100, a time slot may be further divided into multiple micro-slots containing one or more symbols. Excluding cyclic prefixes, each symbol period may contain one or more (e.g., ) sampling period. The duration of the symbol period may depend on the subcarrier spacing or operating frequency band.

A subframe, time slot, micro-slot, or symbol may be the smallest scheduling unit (eg, in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (eg, the number of symbol periods in the TTI) may be variable. Additionally or alternatively, the minimum scheduling unit of wireless communication system 100 may be selected dynamically (eg, in short bursts of shortened TTI (sTTI)).

Physical channels can be multiplexed on the carrier according to various techniques. For example, one or more of time division multiplexing (TDM) technology, frequency division multiplexing (FDM) technology, or hybrid TDM-FDM technology may be used to pair the physical control channel and the physical data channel on the downlink carrier. Multitasking. A control region (eg, control resource set (CORESET)) for a physical control channel may be defined by multiple symbol periods and may extend over the system bandwidth of the carrier or a subset of the system bandwidth. One or more control regions (eg, CORESET) may be configured for a set of UEs 115. For example, one or more of the UEs 115 may monitor or search for control regions for control information based on one or more search space sets, and each search space set may include one or more aggregates arranged in a cascade. One or more control channel candidates in the level. The aggregation level for a control channel candidate may represent the number of control channel resources (eg, control channel elements (CCEs)) associated with encoding information for a control information format with a given payload size. The search space set may include a common search space set configured for sending control information to multiple UEs 115 and a UE-specific search space set for sending control information to a particular UE 115 .

In some examples, base station 105 may be mobile and, therefore, provide communications coverage for a mobile geographic coverage area 110 . In some examples, different geographic coverage areas 110 associated with different technologies may overlap, but may be supported by the same base station 105 . In other examples, overlapping geographic coverage areas 110 associated with different technologies may be supported by different base stations 105 . The wireless communication system 100 may include, for example, a heterogeneous network in which different types of base stations 105 use the same or different radio access technologies to provide coverage for various geographic coverage areas 110 .

Some UEs 115 may be configured to employ modes of operation that reduce power consumption, such as half-duplex communication (eg, a mode that supports one-way communication via transmission or reception rather than simultaneous transmission and reception). In some examples, half-duplex communications may be performed at a reduced peak rate. Other power saving techniques for the UE 115 include entering a power saving deep sleep mode when not participating in active communications, when operating on a limited bandwidth (e.g., based on narrowband communications), or a combination of these techniques. . For example, some UEs 115 may be configured to operate using a narrowband protocol type associated with a defined portion or range within a carrier, within a guard band of the carrier, or external to the carrier (e.g., subcarriers or resource blocks). (set of RB)) associated. In some aspects, the terms "inactive state," "idle state," and similar terms may additionally or alternatively be used to describe "low power mode," and vice versa.

The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low latency (URLLC). UE 115 can be designed to support ultra-reliable, low-latency or critical functions. Ultra-reliable communications may include private communications or group communications, and may be supported by one or more services such as push-to-talk, video, or data. Support for ultra-reliable low-latency capabilities can include prioritization of services, and such services can be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.

In some examples, UEs 115 are also able to communicate directly with other UEs 115 over device-to-device (D2D) communication links 135 (eg, using peer-to-peer (P2P) or D2D protocols). One or more UEs 115 utilizing D2D communications may be within the geographic coverage area 110 of the base station 105 . Other UEs 115 in such a group may be outside the geographic coverage area 110 of the base station 105 or otherwise unable to receive transmissions from the base station 105 . In some examples, multiple groups of UEs 115 communicating via D2D communication may utilize a one-to-many (1:M) system, where each UE 115 transmits to each other UE 115 in the group. In some examples, base station 105 facilitates scheduling of resources for D2D communications. In other cases, D2D communication is performed between UEs 115 without involving base station 105.

Core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing or mobility functions. The core network 130 may be an Evolved Packet Core (EPC) or a 5G Core (5GC), which may include at least one control plane entity (eg, Mobility Management Entity (MME), Access and Mobility) for managing access and mobility. Ability Management Function (AMF)) and at least one user plane entity for routing or interconnecting packets to external networks (e.g., Service Gateway (S-GW), Packet Data Network (PDN) gateway ( P-GW), or User Plane Functional Unit (UPF)). The control plane entities may manage non-access layer (NAS) functions such as mobility, authentication and bearer management for UEs 115 served by base stations 105 associated with core network 130. User IP packets may be transmitted via a user plane entity, which may provide IP address allocation and other functions. User plane entities may connect to IP services 150 for one or more network service providers. IP services 150 may include access to the Internet, intranet, IP Multimedia Subsystem (IMS), or packet switched streaming services.

Some of the network devices (eg, base station 105) may include sub-elements such as access network entity 140, which may be an example of an access node controller (ANC). Each access network entity 140 may communicate with the UE 115 via one or more other access network transport entities 145 (which may be referred to as radio heads, smart radio heads, or transmit/receive points (TRPs)). Communication. Each access network transport entity 145 may include one or more antenna panels. In some configurations, the various functions of each access network entity 140 or base station 105 may be distributed across various network devices (eg, radio heads and ANCs) or consolidated into a single network device (eg, base station 105) in.

Wireless communication system 100 may operate using one or more frequency bands, typically in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Broadly speaking, the region from 300 MHz to 3 GHz is called the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features, but the waves may penetrate structures sufficiently for macrocells to provide services to UEs 115 located indoors. Compared to transmission of smaller frequencies and longer waves using the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz, the transmission of UHF waves can be operated with smaller antennas and shorter distance (for example, less than 100 kilometers).

Wireless communication system 100 may utilize both licensed and unlicensed radio frequency spectrum bands. For example, the wireless communication system 100 may employ Licensed Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology in unlicensed frequency bands such as the 5 GHz Industrial, Scientific, and Medical (ISM) band. . When operating in unlicensed radio frequency spectrum bands, devices such as base station 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation in unlicensed bands may be based on a carrier aggregation configuration incorporating component carriers operating in licensed bands (eg, LAA). Operations in unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.

Base station 105 or UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of base station 105 or UE 115 may be located within one or more antenna arrays or antenna panels (which may support MIMO operation or transmit or receive beamforming). For example, one or more base station antennas or antenna arrays may be co-located at an antenna element, such as an antenna tower. In some examples, antennas or antenna arrays associated with base station 105 may be located at different geographic locations. The base station 105 may have an antenna array with rows and columns of antenna ports that the base station 105 may use to support beamforming for communications with the UE 115 . Likewise, UE 115 may have one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support radio frequency beamforming for signals sent via the antenna ports.

Base station 105 or UE 115 can use MIMO communications to take advantage of multipath signal propagation and improve spectral efficiency by sending or receiving multiple signals through different spatial layers. This type of technology can be called spatial multiplexing. For example, a transmitting device may transmit multiple signals via different antennas or different combinations of antennas. Likewise, a receiving device may receive multiple signals via different antennas or different combinations of antennas. Each of the plurality of signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same coded characters) or a different data stream (e.g., different coded characters). ) associated bits. Different spatial layers can be associated with different antenna ports for channel measurement and reporting. MIMO technologies include single-user MIMO (SU-MIMO) (in which multiple spatial layers are sent to the same receiving device) and multi-user MIMO (MU-MIMO) (in which multiple spatial layers are sent to multiple devices).

Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting device or a receiving device (eg, base station 105 or UE 115) to transmit signals along a Forming or directing an antenna beam (e.g., transmit beam, receive beam) along a spatial path between a transmitting device and a receiving device. Beamforming can be achieved by combining signals transmitted through the antenna elements of an antenna array such that some signals experience constructive interference and other signals experience destructive interference when propagating in a particular direction with respect to the antenna array. Adjustment of signals transmitted via antenna elements may include the transmitting device or receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. The adjustments associated with each of the antenna elements may be defined by a set of beamforming weights associated with a particular orientation (eg, relative to an antenna array of a transmitting device or a receiving device, or relative to some other orientation).

As part of the beamforming operation, the base station 105 or the UE 115 may use beam scanning techniques. For example, base station 105 may use multiple antennas or antenna arrays (eg, antenna panels) to perform beamforming operations for directional communications with UE 115 . The base station 105 may transmit some signals (eg, synchronization signals, reference signals, beam selection signals, or other control signals) multiple times in different directions. For example, base station 105 may transmit signals according to different sets of beamforming weights associated with different transmission directions. Transmissions in different beam directions may be used (eg, by a transmitting device (such as base station 105 ) or by a receiving device (such as UE 115 )) to identify the beam direction for subsequent transmission or reception by base station 105 .

Base station 105 may transmit some signals (eg, data signals associated with a particular receiving device (eg, UE 115)) in a single beam direction (eg, a direction associated with the receiving device). In some examples, the beam direction associated with transmission along a single beam direction may be determined based on signals sent in one or more beam directions. For example, UE 115 may receive one or more of the signals transmitted by base station 105 in different directions and may report to base station 105 the signal quality received by UE 115 that has the highest or otherwise acceptable signal quality. signal indication.

In some examples, transmissions by a device (e.g., by base station 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or radio frequency beamforming to generate a signal for (e.g., , the combined beam of transmissions from the base station 105 to the UE 115. UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured number of beams across the system bandwidth or one or more sub-bands. The base station 105 may transmit reference signals (eg, cell-specific reference signals (CRS), channel status information (CSI) reference signals (CSI-RS)) that may or may not be precoded. The UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or a codebook based feedback (e.g., multi-panel type codebook, linear combination type codebook, port selection type codebook ). Although these techniques are described with reference to base station 105 transmitting signals in one or more directions, UE 115 may employ similar techniques to transmit signals multiple times in different directions (e.g., for identification purposes for UE 115 beam direction for subsequent transmission or reception) or to send a signal in a single direction (for example, to send data to a receiving device).

When receiving various signals from base station 105 (such as synchronization signals, reference signals, beam selection signals, or other control signals), a receiving device (eg, UE 115) may attempt multiple reception configurations (eg, directional listening). For example, a receiving device may receive via different antenna sub-arrays, by processing received signals according to the different antenna sub-arrays, by applying a signal based on signals received at multiple antenna elements of the antenna array. Reception is performed with different sets of receive beamforming weights (e.g., different sets of directional listening weights) or by processing reception according to different sets of receive beamforming weights applied to signals received at multiple antenna elements of the antenna array signal (any of the above operations can be called "listening" based on different receive configurations or receive directions), thereby trying multiple receive directions. In some examples, a receiving device may use a single receive configuration to receive along a single beam direction (eg, when receiving a data signal). A single receive configuration can be aligned in a beam direction determined based on listening in different receive configuration directions (e.g., determined to have the highest signal strength, highest signal-to-noise ratio (SNR), based on listening in multiple beam directions) or otherwise acceptable signal quality) in the beam direction.

Wireless communication system 100 may be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or Packet Data Convergence Protocol (PDCP) layer can be IP-based. The Radio Link Control (RLC) layer can perform packet segmentation and reassembly for transmission on logical channels. The Media Access Control (MAC) layer can perform prioritization and multiplexing of logical channels into transport channels. The MAC layer can also use error detection technology, error correction technology, or both to support retransmissions at the MAC layer to improve link efficiency. In the control plane, the Radio Resource Control (RRC) protocol layer may provide for the establishment, configuration and maintenance of RRC connections between the UE 115 and the base station 105 or core network 130 (which supports radio bearers for user plane data). At the physical layer, transport channels can be mapped to physical channels.

The UE 115 and the base station 105 may support retransmission of data to increase the likelihood that the data is successfully received. Hybrid automatic repeat request (HARQ) feedback is a technique used to increase the likelihood that data will be received correctly on the communication link 125 . HARQ may include a combination of error detection (eg, using cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (eg, automatic repeat request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (eg, low signal-to-noise ratio conditions). In some examples, a device may support same-slot HARQ feedback, where the device may provide HARQ feedback in a specific time slot for data received in a previous symbol in that time slot. In some other cases, the device may provide HARQ feedback in subsequent time slots or according to some other time interval.

In some aspects, the UE 115 and the base station 105 of the wireless communication system 100 may support technology that enables the UE 115 to send UCI messages associated with SDT during an inactive or idle state. Specifically, wireless communication system 100 may support various SDT configurations that define different sets of rules or conditions that UEs 115 may use to determine whether they can send UCI messages along with SDT in an inactive or idle state. In some cases, the UE 115 of the wireless communication system 100 may receive control signaling from the network (e.g., the base station 105) that indicates the transmission of SDT and UCI messages when the UE 115 is in an inactive or idle state. resource set. In some cases, control signaling may configure the UE 115 with separate sets of resources for transmitting SDT and UCI messages, where in other cases the UE 115 may be configured to use the same set of resources to transmit UCI messages with SDT multitasks.

In the context of RA-SDT, the control signal transfer received from the network of the wireless communication system 100 may include a random access procedure message that configures the UE to be used to send SDT and/or UCI messages. A collection of resources for random access messages. In comparison, in the context of CG-SDT, the UE 115 may receive a message (eg, an RRC release message) for releasing the UE 115 from an active state to an inactive or idle state, where the message configures the UE 115 to be useful Resource set for SDT and UCI messages (for example, PUCCH resources, PUSCH resources). The UCI messages sent by the UE 115 in the inactive or idle state may include HARQ feedback information, UE assistance information (eg, CSI report, preferred BWP, beam failure report), etc. In some cases, the UE may be required to perform TA verification for SDT and/or UCI messages.

The techniques described herein may facilitate more efficient use of resources by enabling UE 115 to send UCI messages along with SDT during inactive and/or idle states. In particular, by enabling the UE 115 to send UCI messages along with SDT while in an inactive or idle state, the techniques described herein may prevent the need for the UE 115 to establish a full wireless connection with the network to send small amounts of control data. Accordingly, the techniques described herein can reduce the signaling management burden associated with establishing a wireless connection between the UE 115 and the network, and can reduce the latency associated with UCI messages.

FIG. 2 illustrates an example of a wireless communication system 200 that supports technology for UCI transmission together with small data transmission, according to various aspects of the subject matter. In some examples, the wireless communication system 200 can implement various aspects of the wireless communication system 100 or be implemented by various aspects of the wireless communication system 100 . The wireless communication system 200 may support techniques for sending UCI messages along with SDT when the UE 115 is in an inactive state and/or an idle state, as described in FIG. 1 .

For example, wireless communication system 200 may include UE 115-a and base station 105-a, which may be examples of UE 115, base station 105, and other wireless devices as described with reference to FIG. 1 . In some aspects, UE 115-a may communicate with base station 105-a using communication link 205, which may be an NR or LTE link between base station 105-a and UE 115-a. Road example. In some aspects, communication link 205 between base station 105-a and UE 115-a may include an example of an access link (eg, a Uu link), which may include enabling uplink communications and downlink Link communicates a two-way link between the two.

In some aspects, wireless communication system 200 may enable UE 115 (eg, UE 115-a) to send SDT during an inactive or idle state. The use of SDT can enable the UE 115 to transmit small amounts of data to the network without establishing a full wireless connection to the network (eg, by entering the active state), which can reduce the control signal transfer management burden. Specifically, the wireless communication system 200 may support one or both of two different types of SDT configurations: (1) RA-SDT configuration and (2) CG-SDT configuration.

In RA-SDT, when the UE is in inactive or idle state, the UE can send SDT together with the random access message transmitted during the random access procedure with the network. In particular, the RA-SDT configuration enables sending a small amount of uplink data transmission (eg, SDT) for Random Access Channel (RACH) based schemes (which include two-step RACH procedures and four-step RACH procedures). In general, the RA-SDT procedure enables the UE 115 to operate in an inactive state (e.g., RRC is not available) by multiplexing messages from the SDT and RACH procedures (e.g., via MsgA and/or Msg3 in the RACH procedure). Uplink data transmission for small data packets is sent when active). In the context of RA-SDT configuration, different wireless communication systems can support flexible SDT payload sizes. In addition, the RA-SDT configuration can implement context acquisition and data forwarding (with and without anchor relocation) for the inactive UE 115 for RACH-based solutions.

In contrast, in a CG-SDT configuration, the network (eg, base station 105-a) may configure UE 115-a with a set of transmission opportunities that may be used when UE 115-a is inactive. SDT is sent when the RRC is active and/or idle (e.g., RRC inactive or idle). The CG-SDT configuration can enable transmission of a small amount of uplink data on pre-configured PUSCH and/or PUCCH resources (for example, reuse configured grant type 1) when the TA at UE 115-a is valid. In general, the CG-SDT configuration enables small data transmission via configured authorization type 1 resources when UE 115-a is in an inactive state.

In some cases, UE 115-a may have control information that must be sent to the network, such as via UCI messages. Specifically, when UE 115-a is in an inactive or idle state, UE 115-a may have control information to send to the network via UCI messages. For example, UCI messages sent in the inactive or idle state may include HARQ ACK/NACK information in response to downlink control/user plane messages (e.g., RRCRelease messages) for resource optimization and interference management. and power-saving UE auxiliary information (for example, CSI report), turbo HARQ for CG-SDT, etc. However, conventional wireless communication systems only transmit UCI messages when the UE 115-a is in an active state. Therefore, according to some conventional SDT technologies, the UE 115-a may be required to establish a complete wireless connection with the network (e.g., enter the active state) before the UE 115-a can transmit the UCI message, which may result in signaling management burden, functionality consumption and UCI delay increase.

Accordingly, wireless communication system 200 may support techniques that enable UE 115-a to send UCI messages 220 associated with SDT 215 during an inactive or idle state. In particular, the wireless communication system 200 may support multiple SDT configurations 225, each of which defines a different set of rules or conditions that the UE 115-a may use to determine whether the UE 115-a is inactive or inactive. Whether the UCI message 220 together with the SDT 215 can be sent in the idle state includes whether the UCI message 220 and the SDT 215 are to be multiplexed, transmitted separately, or both. This technique may facilitate more efficient use of resources within the wireless communication system 200 by enabling the UE 115-a to send the UCI message 220 along with the SDT 215 during inactive and/or idle states, which may reduce The signaling management burden associated with establishing a wireless connection between UE 115-a and the network can reduce the latency associated with UCI message 220.

For example, as shown in Figure 2, UE 115-a may receive control signaling 210 from base station 105-a, where control signaling 210 identifies when UE 115-a is in an inactive state (eg, RRC inactive state) and One or more resource sets used for data transmission (eg, SDT 215) and UCI messages 220 when/or in an idle state (eg, RRC idle state). For example, control signaling 210 may indicate a first set of resources and a second set of resources that may be used to transmit SDT 215 and UCI, respectively, when UE 115-a is in an inactive or idle state. Message 220. In this example, the first set of resources for SDT 215 may include uplink shared resources (eg, PUSCH resources), wherein the second set of resources for UCI transmission may include uplink shared resources (eg, PUSCH resources) ) and/or uplink control resources (for example, PUCCH resources).

In some implementations, and in the context of RA-SDT, control signaling 210 may include random access messages for random access procedures (eg, two-step RACH procedure, four-step RACH procedure). In this case, control signaling 210 may include system information, RRC reconfiguration messages, or both. For example, control signaling 210 may include system information configured for RA-SDT for transmitting SDT 215 in the context of a RACH procedure. In contrast, in the context of CG-SDT, control signaling 210 may include an RRC release message that releases UE 115-a from an active state to an inactive or idle state.

In some aspects, control signaling 210 may indicate an SDT configuration 225 (eg, RA-SDT, CG-SDT) that defines a set of rules or conditions that may be used to determine when the UE 115- Whether (and when) UCI message 220 together with SDT 215 can be sent when a is inactive or idle. For example, control signaling 210 may indicate whether the network supports transmission of UCI messages 220 when UE 115-a is in an inactive or idle state, a resource set for sending SDT 215 and/or UCI messages 220, etc. By another example, control signaling 210 may indicate SDT configuration 225 that indicates whether UCI message 220 is to be sent separately from SDT 215 (eg, first SDT configuration 255-a), whether UCI message 200 is to be sent separately from SDT 215 SDK 215 performs multiplexing (eg, second SDT configuration 225-b), whether UCI message 220 must satisfy TA verification, etc.

The set of resources configured via control signaling 210 and allocated for UCI message 220 may include PUCCH resources, PUSCH resources, or both. For example, in some cases (e.g., some SDT configurations 225), control signaling 210 may indicate a set of shared PUCCH resources, a set of dedicated PUCCH resources, or both, that is used when UE 115-a is in an inactive or idle state. Can be used for UCI message 220. For example, control signaling 210 may indicate a common PUCCH resource set corresponding to pucch-ResourceCommon. In the context of shared PUCCH resources, control signaling 210 may indicate PUCCH formats dedicated to RA-SDT and/or CG-SDT procedures. Additionally or alternatively, control signaling 210 may include one or more bit field values that UE 115-a may interpret as representing the indicated set of PUCCH resources.

By another example, control signaling 210 may indicate a dedicated set of PUCCH resources corresponding to PUCCH-Config. For example, where UE 115-a is in an RRC inactive state, UE 115-a may have previously connected to the network such that base station 105-a already knows the identity of UE 115-a. Therefore, base station 105-a may configure UE 115-a with a dedicated set of PUCCH resources (eg, via control signaling 210).

In addition or alternatively, control signaling 210 may indicate a set of PUSCH resources to use for UCI transmissions when UE 115-a is in an inactive or idle state. For example, in the context of RA-SDT, control signaling 210 may instruct UCI message 220 to be consistent with the random access procedure performed between UE 115-a and base station 105-a (e.g., two-step RACH procedure, four-step RACH procedure, RACH procedure) associated random access messages are multiplexed. In other cases, control signaling 210 may indicate a set of transmission opportunities (eg, CG-SDT PUSCH transmission opportunities) for sending SDT 215, UCI message 220, or both.

In some aspects, base station 105-a may indicate parameters associated with transmitting UCI via control messages, which may be the same as control signaling 210 and/or be separate control messages. Parameters associated with the UCI message may include resource index (eg, PUCCH resource index), number of repetitions for PUCCH transmission (eg, number of repetitions of UCI), frequency hopping scheme of PUCCH (eg, UCI frequency hopping scheme) , transmit beam index (e.g., Tx beam index of PUCCH), orthogonal code coverage (OCC) of PUCCH, or any combination thereof. Parameters associated with UCI transmission may be transmitted via any control signaling or control message, including DCI messages, MAC CE messages, RRC messages, system information messages, or any combination thereof.

In some aspects, UE 115-a, base station 105-a, or both may perform TA verification. In other words, UE 115-a and/or base station 105-a may determine whether the TA for UE 115-a is valid or invalid. The TA associated with UE 115-b may include a timing offset used by UE 115-a to communicate messages (or message types) with base station 105-a (or other device), and may be associated with UE 115-a and Propagation delays between base stations 105-a are associated. Therefore, the TA for UE 115-a may be a function of how far UE 115-a is from base station 105-a (e.g., if UE 115-a is farther from base station 105-a, TA is larger if If UE 115-a is closer to base point 105-a, TA is smaller). The TA of UE 115-a can be determined/controlled by the base station 105-b through TA commands. Furthermore, the TA for UE 115-a may only be valid for a defined period of time, where the validity of the TA is controlled by a TA timer. In some aspects, control signaling 210 may include a TA command, an indication of a TA timer, or both. In other cases, the TA command and/or TA timer may be transmitted via other signaling from base station 105-a.

In some aspects, UE 115-a and/or base station 105-a may perform TA authentication based on transmit/receive control signaling 210. For example, in some aspects, UE 115-a may perform TA verification based on a TA command and/or a TA timer received via control signaling 210, a random access message of a RACH procedure, or both. In some aspects, the TA verification procedure may vary based on the type of SDT configuration 225. For example, different rules or conditions may be used to perform TA verification in the context of RA-SDT for a two-step RACH procedure, RA-SDT for a four-step RACH procedure, and RA-SDT for a CG-SDT procedure. The various rules/conditions for performing TA verification will be discussed in further detail with respect to Figures 4-6.

In some aspects, UE 115-a may generate UCI message 220. Specifically, UE 115-a may generate UCI when UE 115-a is in an inactive or idle state and upon deciding that UE 115-a has material (eg, control material) to send to base station 105-a Information 220. UE 115-a may generate UCI message 220 based on receiving control signaling 210, perform TA authentication, or both. For example, UE 115-a may generate UCI message 220 based on determining that the TA for UE 115-a is valid.

UE 115-a may send a data message (eg, SDT 215) to base station 105-a. UE 115-a may send SDT 215 in an inactive or idle state. UE 115-a may send SDT 215 based on receiving control signaling 210, performing TA verification, generating UCI message 220, or any combination thereof. Specifically, UE 115-a may send SDT 215 on at least a portion of a first set of resources allocated via control signaling 210 for data transmission. Additionally, in the event that the control signaling 110 indicates that the data message is to be included with the random access message (e.g., multiplexed with the random access message), the UE 115-a may send the SDT 215 along with the data message performed by the base station 105-a. Random access messages for random access procedures (for example, MsgA, Msg3). For example, in some implementations, UE 115-a may multiplex SDT 215 with random access messages (eg, MsgA, Msg3) for two-step and/or four-step RACH procedures.

In some aspects, UE 115-a may send UCI message 220 to base station 105-a. UE 115-a may send UCI message 220 in an inactive or idle state. Additionally, UE 115-a may send a UCI message 220 within an uplink BWP configured for RA-SDT and/or CG-SDT (e.g., indicated via control signaling 210 for RA-SDT and/or CG-SDT). BWP). UE 115-a may send UCI message 220 based on receiving control signaling 210, performing TA verification, generating UCI message 220, sending SDT 215, or any combination thereof. Specifically, UE 115-a may send UCI message 220 on at least a portion of a second set of resources allocated via control signaling 210 for UCI transmission.

Additionally, where control signaling 210 indicates that the UCI message 220 is to be included with the random access message (e.g., multiplexed with the random access message), the UE 115-a may combine the UCI message 220 with the random access procedure. Random access messages are sent together. For example, in some implementations, UE 115-a may multiplex UCI message 220 and MsgA and/or Msg3 with the RACH procedure performed by base station 105-a.

In some aspects, UE 115-a may send UCI message 220 separately from SDT 215. For example, as shown in first SDT configuration 225-a, UE 115-a may send UCI information 220-a before SDT 215-a. In this case, SDT 215-a may be sent via PUSCH resources, where UCI message 220-a may be sent via PUCCH resources and/or PUSCH resources. Additionally or alternatively, UCI message 220 may be multiplexed with SDT 215 . For example, as shown in second SDT configuration 225-b, UE 115-b may multiplex UCI message 220-b with SDT 215-b such that both UCI message 220-b and SDT 215-b are routed via PUSCH resources are sent.

UE 115-a may send UCI message 220 and/or SDT 215 based on the TA verification procedure. The various rules/conditions used to perform TA verification will be described in further detail with reference to Figures 4-6.

The UCI message 220 may include any uplink information, including HARQ feedback information, UE assistance information, etc. For example, UCI message 220 may include HARQ feedback information in response to contention resolution messages (eg, contention-based SDT 215 contention resolution messages), in response to downlink control plane messages, and/or downlink user plane messages. HARQ feedback information of the message, HARQ feedback information in response to the RRC release message (for example, the RRCRelease message used to reconfigure or release SDT 215 resources for RA-SDT or CG-SDT), or any combination thereof. By another example, UCI message 220 may include a CSI report, a BWP index (eg, an index of a preferred BWP), a beam failure report, a coverage enhancement request (eg, a coverage enhancement request for SDT 215), a set of termination data messages for request (e.g., early termination request for SDT 215), UE assistance information multiplexed with HARQ feedback (e.g., CSI report multiplexed with HARK feedback and mapped to UCI), or any combination thereof. For example, the UCI message 220 may include a compact CSI report, which may help the network improve and optimize the spectral efficiency of SDT 215 communications. In this case, the compact CSI report may be aperiodic, semi-static, or both, and may be smaller than the CSI report sent by UE 115-b when in the active state.

The techniques described herein may facilitate more efficient use of resources by enabling UE 115-a to send UCI messages 220 along with SDT 215 during inactive and/or idle states. In particular, by enabling UE 115-a to send UCI message 220 along with SDT 215 in an inactive or idle state, the techniques described herein may enable UE 115-a to establish a full wireless connection with base station 105-a ( or without establishing a full wireless connection with base station 105-a), which can reduce the signaling management burden associated with establishing a wireless connection between UE 115-a and the network, and can Reduce the latency associated with UCI message 220.

FIG. 3 illustrates an example of a resource configuration 300 for a technology that supports UCI transmission together with small data transmission, according to various aspects of the content of this case. In some examples, resource configuration 300 may implement aspects of wireless communication system 100, wireless communication system 200, or both, or be implemented by them.

Resource configuration 300 illustrates different SDT configurations 305 for sending UCI messages along with SDT. Specifically, the first SDT configuration 305 illustrates the UE 115 sending the UCI message 315 before and/or after the SDT 320 , while the second SDT configuration 305 - b illustrates the UCI message 315 multiplexed with the SDT 320 .

As shown in the first SDT configuration 305-a, the UE 115 may receive a downlink message 310-a from the base station 105. The downlink message 310-a may include a PDCCH message, a physical downlink shared channel (PDSCH) message, or both. For example, downlink message 310-a may include downlink messages (eg, RRC reconfiguration messages, downlink user plane messages, downlink control plane messages, or any combination thereof) in which the UE 115 will provide HARQ feedback . In some cases, UE 115 may receive downlink message 310-a while in an inactive or idle state, and thus may have uplink data to be sent via UCI message 315 in response to downlink information 310-a. (For example, HARQ feedback information).

Continuing with reference to the first SDT configuration 305-a, when the UE 115 is in an inactive or idle state, the UE 115 may receive control signaling for allocating a set of resources for the SDT 320 and UCI message 315. Accordingly, UE 115 may be configured to send UCI message 315 including HARQ feedback (and/or UE assistance information) in response to downlink message 310-a when UE 115 is in an inactive or idle state. As previously described herein, UE 115 may be configured with PUSCH resources for SDT transmission, and may be configured with PUCCH and/or PUSCH for UCI messages. For example, as shown in Figure 2, UE 115 may send first UCI message 315-a and second UCI message 315-b via PUCCH resources, and may send SDT 320-a via PUSCH resources. In this example, the UE 115 may send the first UCI message 315-a in the time domain before sending the SDT 320-a, and may send the second UCI message 315-a in the time domain after sending the SDT 320-a. b.

In additional or alternative implementations, UE 115 may be configured to multiplex UCI messages 315 with SDT 320 in an inactive or idle state. For example, referring now to the second SDT configuration 305-b, the UE may receive the downlink message 310-b from the base station 105. Downlink message 310-b may include PDCCH message, PDSCH message, or both. For example, downlink message 310-b may include downlink messages (eg, RRC reconfiguration messages, downlink user plane messages, downlink control plane messages, or any combination thereof) in which the UE 115 will provide HARQ feedback. In some cases, UE 115 may receive downlink message 310-b in an inactive or idle state, and thus may have uplink data to be sent via UCI message 315 in response to downlink information 310b (e.g., HARQ feedback information).

In this example, UE 115 may multiplex UCI message 315-c (eg, UCI message 315-c including HARQ feedback and/or UE assistance information) with SDT 320-b while in an inactive or idle state. handle. In this aspect, UE 115 may be configured to multiplex UCI messages 315-c via a set of PUSCH resources 325 configured for SDT transmission. For example, as shown in Figure 3, UE 115 may receive control signaling indicating a set of PUSCH resources spanning a set of time resources ( _TSDT ) in the time domain and a set of frequency resources ( _FSDT ) in the frequency domain 325. In this case, the control signaling may additionally indicate a subset of the PUSCH resource set 325 that will be used for the multiplexed UCI message 315. In this aspect, the resource set 325 of the PUSCH may include a first set of resources allocated for SDT transmission, and a second set of resources allocated for UCI transmission (e.g., across T UCI in the time domain and across T _UCI in the frequency domain resources across F _UCI ). In some cases, the PUSCH resource set may additionally include a resource set for demodulation reference signal (DMRS) 330.

FIG. 4 illustrates an example of a program flow 400 that supports techniques for UCI transmission with small data transmission, according to aspects of the subject matter. In some examples, the program flow 400 can implement various aspects of the wireless communication system 100, the wireless communication system 200, the resource configuration 300, or any combination thereof, or be implemented by these aspects. For example, program flow 400 illustrates UE 115-b sending a UCI message in the context of a two-step RACH procedure (eg, two-step RA-SDT), as described with reference to Figures 1-3.

In some cases, program flow 400 may include UE 115-b and base station 105-b, which may be examples of corresponding devices as described herein. For example, the UE 115-b and the base station 105-b shown in FIG. 4 may include the examples of the UE 115-a and the base station 105-a shown in FIG. 2, respectively.

In some examples, the operations shown in program flow 400 may be performed by hardware (e.g., including circuits, processing blocks, logic elements, and other elements), code (e.g., software or firmware) executed by a processor or any combination thereof. The following alternative examples may be implemented in which some steps are performed in a different order than described, or some steps are not performed at all. In some cases, steps may include additional functionality not mentioned below, or more steps may be added.

At 405, UE 115-b may receive a control signaling from base station 105-b, wherein the control signaling identifies when UE 115-b is in an inactive state (e.g., RRC inactive state) and/or an idle state (e.g., , RRC idle state), one or more resource sets used for data transmission (e.g., SDT) and UCI messages. For example, the control signaling may indicate a first set of resources and a second set of resources that may be used to send SDT and UCI messages, respectively, when UE 115-b is in an inactive or idle state. In this example, the first set of resources for SDT may include uplink shared resources (eg, PUSCH resources), wherein the second set of resources for UCI transmission may include uplink shared resources (eg, PUSCH resources) and/or uplink control resources (for example, PUCCH resources). In some implementations, the control signaling may include random access information for a random access procedure (eg, a two-step RACH procedure). The control signaling may include system information, RRC reconfiguration messages, or both. For example, the control signaling may include system information for RA-SDT configuration for transmitting SDT in the context of a RACH procedure.

In some aspects, the control signaling may indicate an SDT configuration (e.g., RA-SDT) that defines whether (and when) UE 115-b can be used to determine if (and when) it can Send UCI messages along with a set of rules or conditions for SDT. For example, the control signaling may indicate whether the network supports transmission of UCI messages when UE 115-b is in an inactive or idle state, a resource set for sending SDT and/or UCI messages, etc. By another example, the control signaling may indicate an SDT configuration that indicates whether UCI messages are to be sent separately from SDT, whether UCI messages are to be multiplexed with SDT, whether UCI messages must meet TA validation, etc. In the context of the two-step RACH procedure shown in Figure 4, the network (eg, base station 105-b) may enable and disable frequency hopping and/or coverage enhancement for UCI/SDT transmissions. Furthermore, in the context of RA-SDT configuration, control signaling may indicate whether UCI messages and/or SDT are to be sent in association with, and multiplexed with, random access messages of the RACH procedure. , or both.

The set of resources configured via control signaling and allocated for UCI messages may include PUCCH resources, PUSCH resources, or both. For example, in some cases (e.g., some SDT configurations), control signaling may indicate a common set of PUCCH resources, a dedicated set of PUCCH resources, or both that may be used for UCI messages when UE 115-b is in an inactive or idle state. . For example, the control signaling may indicate a common PUCCH resource set corresponding to pucch-ResourceCommon. In the context of shared PUCCH resources, control signaling may indicate a PUCCH format dedicated to the RA-SDT procedure. Additionally or alternatively, the control signaling (eg, RRCReconfigurationMessage) may include one or more bit field values that UE 115-b may interpret as representing the indicated set of PUCCH resources.

By another example, the control signaling may indicate a dedicated set of PUCCH resources corresponding to PUCCH-Config. For example, where UE 115-b is in an RRC inactive state, UE 115-b may already be connected to the network such that base station 105-b already knows the identity of UE 115-b. Therefore, base station 105-b may configure UE 115-b using a dedicated set of PUCCH resources (eg, via control signaling).

In addition or alternatively, the control signaling may indicate the set of PUSCH resources used for UCI transmission when UE 115-b is in an inactive or idle state. For example, the control signaling may indicate that the UCI message will be multiplexed with MsgA PUSCH resources for initial transmission and retransmission configured for the two-step RA-SDT procedure. In other words, the control signaling may indicate that the UCI message may be multiplexed on the PUSCH resources used to transmit the MsgA of the two-step RACH procedure. As another example, the control signaling may indicate that UCI messages may be multiplexed with Msg3 fallback transmission configured for the RA-SDT procedure. In this case, base station 105-b may detect only the preamble portion of MsgA and may issue a random access response grant for SDT retransmission. In other words, the control signaling may indicate that the UCI message may be multiplexed on the PUSCH resources used to transmit Msg3 of the two-step RACH procedure.

In some aspects, one or more parameters associated with the PUCCH (eg, UCI transmission) may be indicated to the UE 115 , where the one or more parameters include a PUCCH resource index, a number of repetitions for the PUCCH transmission, a Frequency hopping scheme, transmit beam index of PUCCH, OCC of PUCCH, or any combination thereof. Such parameters may be signaled to the UE 115 via a DCI message, MAC-CE message, RRC message, system information message, or any combination thereof. In this case, parameters for UCI transmission (eg, parameters for PUCCH) may be indicated via control signaling, separate control messages, or both.

At 410, UE 115-b, base station 105-b, or both may perform TA verification. In other words, UE 115-b and/or base station 105-b may determine whether the TA for UE 115-b is valid or invalid. In some aspects, UE 115-b and/or base station 105-b may perform TA verification at 410 based on the send/receive control signal transfer at 405.

As previously described herein, a TA associated with UE 115-b may include a timing offset used by UE 115-b to communicate with base station 105-b (or other device), and may be associated with UE 115-b and Propagation delays are associated between base stations 105-b. Therefore, the TA for UE 115-b may be a function of how far UE 115-b is from base station 105-b (e.g., if UE 115-b is farther from base station 105-b, TA is larger if If UE 115-b is closer to base point 105-b, TA is smaller). The base station 105-b can determine/control the TA for the UE 115-b through the TA command. Furthermore, the TA for UE 115-b may only be valid for a defined period of time, where the validity of the TA is controlled by a TA timer. In some aspects, the control signaling at 405 may include a TA command, an indication of a TA timer, or both. In other cases, the TA command and/or TA timer may be transmitted via other signaling from base station 105-b.

In the context of RA-SDT configuration based on the two-step RACH procedure, as shown and described in Figure 4, depending on the resources used to send the UCI message, TA authentication for UCI transmission may or may not be applicable. For example, when the UCI message is to be multiplexed with MsgA PUSCH or Msg3 fallback, UE 115-b can send the UCI message regardless of whether the TA timer is valid (eg, TA authentication is not applicable). In other words, in the case where the UE 115-b is configured to multiplex UCI messages with MsgA or Msg3 of the two-step RACH procedure, the UE 115-b may be configured to send the UCI message even if (except in the case where the TA is valid ) is used in the case where the TA of UE 115-b is invalid. In contrast, where UE 115-b is configured to send UCI messages on the PUCCH resources indicated via control signaling at 405, the TA timer for UE 115-b must be valid. That is, in the context of a RA-SDT configuration for a two-step RACH procedure, UE 115-b may only be able to send UCI messages on PUCCH resources if the TA for UE 115-b is valid, and It may not be possible to send UCI messages on PUCCH resources if the TA for UE 115-b is invalid.

At 415, UE 115-b may generate a UCI message. Specifically, UE 115-b may generate UCI when UE 115-b is in an inactive or idle state and upon deciding that UE 115-b has material (eg, control material) to send to base station 105-b message. UE 115-b may generate a UCI message at 415 based on receiving the control signaling at 405, performing TA verification at 410, or both.

For example, UE 115-b may generate a UCI message at 415 based on determining at 410 that the TA for UE 115-b is valid. As another example, UE 115-b may decide not to require TA authentication for UCI transmissions (e.g., in the case where UE 115-b is configured to multiplex UCI messages with MsgA and/or Msg3 of the two-step RACH procedure). (below) to generate the UCI message at 415.

At 420, UE 115-b may send a random access message to base station 105-b. For example, as shown in Figure 4, UE 115-b may send MsgA (eg, Msg1+Msg3) to the base station as part of a two-step RACH procedure performed between UE 115-b and base station 105-b 105-b. In this case, MsgA may include the RACH preamble and information associated with the RACH procedure. UE 115-b may send the MsgA of the two-step RACH procedure based on receiving control signaling at 405, performing TA verification at 410, generating a UCI message at 415, or any combination thereof.

At 425, UE 115-b may send a data message (eg, SDT) to base station 105-b. UE 115-b may send data messages at 425 while in an inactive or idle state. UE 115-b may send a data message (SDT) based on receiving control signaling at 405, performing TA verification at 410, generating a UCI message at 415, sending a random access message at 420, or any combination thereof. . Specifically, UE 115-b may send the SDT at 425 on at least a portion of a first set of resources for data transmission that was allocated via the control signaling at 405. Additionally, in the event that the control signaling at 405 indicates that the data message is to be included with (e.g., multiplexed with the random access message) the random access message, UE 115-b may send the SDT along with the data message sent at 420 MsgA/Msg3. For example, in some embodiments, UE 115-b may multiplex SDT with the random access message sent at 420 (eg, SDT with MsgA/Msg3).

At 430, UE 115-b may send the UCI message to base station 105-b. UE 115-b may send the UCI message at 430 when in an inactive or idle state. Additionally, UE 115-b may send the UCI message within the uplink BWP configured for RA-SDT (eg, the BWP for RA-SDT indicated via control signaling at 405). UE 115-b may send the UCI message based on receiving control signaling at 405, performing TA verification at 410, generating a UCI message at 415, sending a random access message at 420, or any combination thereof. Specifically, UE 115-b may send the UCI message at 430 on at least a portion of a second set of resources for UCI transmission that was allocated via control signaling at 405.

Additionally, where the control signaling indication at 405 is to include (eg, multiplexed with the random access message) the UCI message, UE 115-b may send the UCI message in conjunction with the random access message at 420 MsgA/Msg3. For example, in some implementations, UE 115-b may multiplex the UCI message with the random access message sent at 420 (eg, UCI multiplexed with MsgA/Msg3). Additionally, in some implementations, UCI messages may be multiplexed with SDT at 425, as shown and described in Figure 3. For example, the control signaling at 405 may include instructions for UE 115-b to multiplex the UCI message with SDT within a second set of resources included in the first resources allocated for SDT. Concentrated. In this aspect, UE 115-b can perform multiplexing via a PUCCH resource set (e.g., a common PUCCH resource corresponding to pucch-ResourceCommon, a dedicated PUCCH resource corresponding to PUCCH-Config), a PUSCH resource set (e.g., with MsgA/Msg3 manual processing) or both, to send UCI messages.

UE 115-b may send the UCI message at 430 based on the TA verification procedure at 410. For example, when the UCI message is to be multiplexed with MsgA PUSCH or Msg3 fallback, UE 115-b can send the UCI message regardless of whether the TA timer is valid (eg, TA authentication is not applicable). In contrast, where UE 115-b is configured to send UCI messages on the PUCCH resources indicated via control signaling at 405, the TA timer for UE 115-b must be valid. That is, in the context of RA-SDT configuration for the two-step RACH procedure, UE 115-b can send UCI messages on PUCCH resources only when the TA for UE 115-b is valid.

The UCI message can include any uplink information, including HARQ feedback information, UE assistance information, etc. For example, the UCI message may include HARQ feedback information in response to contention resolution messages (e.g., contention resolution messages based on contention-based SDT), response to downlink control plane messages and/or downlink user plane messages. HARQ feedback information, HARQ feedback information in response to RRC release messages (e.g., RRCRelease messages used to reconfigure or release SDT resources for RA-SDT or CG-SDT), or any combination thereof. As another example, the UCI message may include a CSI report, a BWP index (e.g., an index of the preferred BWP), a beam failure report, a coverage enhancement request (e.g., a request for coverage enhancement for SDT), a request for termination of the data message set (e.g., a request for coverage enhancement for SDT). For example, early termination request for SDT), UE assistance information multiplexed with HARQ feedback (eg, CSI report multiplexed with HARQ feedback and mapped to UCI), or any combination thereof. For example, the UCI message may include a compact CSI report, which may help the network improve and optimize the spectral efficiency of SDT communications. In this case, the compact CSI report may be aperiodic, semi-static, or both, and may be smaller than the CSI report sent by UE 115-b when UE 115-b is active.

At 435, base station 105-b may send the second random access message of the two-step RACH procedure. For example, as shown in Figure 4, base station 105-b may send MsgB (eg, Msg2+Msg4) to the UE as part of a two-step RACH procedure performed between UE 115-b and base station 105-b 115-b.

The techniques described herein may facilitate more efficient use of resources by enabling UE 115-b to send UCI messages along with SDT when inactive and/or idle in the context of a two-step RACH procedure. In particular, by enabling UE 115-b to send UCI messages along with SDT in an inactive or idle state, the techniques described herein may enable UE 115-b to establish a full wireless connection with base station 105-b (or before without establishing a full wireless connection with base station 105-b), which may reduce the signaling management burden associated with establishing a wireless connection between UE 115-b and the network, and may reduce The delay associated with UCI messages.

Figure 5 illustrates an example of a program flow 500 that supports techniques for UCI transmission with small data transmission, in accordance with aspects of the subject matter. In some examples, the program flow 400 can implement various aspects of the wireless communication system 100, the wireless communication system 200, the resource configuration 300, or any combination thereof, or be implemented by these aspects. For example, program flow 500 illustrates UE 115-b sending a UCI message in the context of a four-step RACH procedure (eg, four-step RA-SDT), as described with reference to Figures 1-3.

In some cases, program flow 500 may include UE 115-c and base station 105-c, which may be examples of corresponding devices as described herein. For example, the UE 115-c and the base station 105-c shown in FIG. 5 may include the examples of the UE 115-a and the base station 105-a shown in FIG. 2, respectively.

In some examples, the operations shown in program flow 500 may be performed by hardware (e.g., including circuits, processing blocks, logic elements, and other elements), code (e.g., software or firmware) executed by a processor or any combination thereof. The following alternative examples may be implemented in which some steps are performed in a different order than described, or some steps are not performed at all. In some cases, steps may include additional functionality not mentioned below, or more steps may be added.

At 505, UE 115-c may receive a control signaling from base station 105-c, wherein the control signaling identifies when UE 115-c is in an inactive state (e.g., RRC inactive state) and/or an idle state (e.g., , RRC idle state), one or more resource sets used for data transmission (e.g., SDT) and UCI messages. For example, the control signaling may indicate a first set of resources and a second set of resources that may be used to send SDT and UCI messages, respectively, when UE 115-c is in an inactive or idle state. In this example, the first set of resources for SDT may include uplink shared resources (eg, PUSCH resources), wherein the second set of resources for UCI transmission may include uplink shared resources (eg, PUSCH resources) and/or uplink control resources (for example, PUCCH resources). In some implementations, the control signaling may include random access information for a random access procedure (eg, a four-step RACH procedure). The control signaling may include system information, RRC reconfiguration messages, or both. For example, the control signaling may include system information for RA-SDT configuration for transmitting SDT in the context of a RACH procedure.

In some aspects, the control signaling may indicate an SDT configuration (e.g., RA-SDT) that defines whether (and when) UE 115-c can be used to determine if (and when) it can Send UCI messages along with a set of rules or conditions for SDT. For example, the control signaling may indicate whether the network supports transmission of UCI messages when UE 115-c is in an inactive or idle state, the resource set for sending SDT and/or UCI messages, etc. As another example, the control signaling may indicate SDT configuration, and the SDT configuration indicates whether the UCI message is to be sent separately from the SDT, whether the UCI message is to be multiplexed with the SDT, whether the UCI message must satisfy TA verification, and so on. In the context of the four-step RACH procedure shown in Figure 5, the network (eg, base station 105-c) may enable and disable frequency hopping and/or coverage enhancement for UCI/SDT transmissions. Furthermore, in the context of RA-SDT configuration, control signaling may indicate whether UCI messages and/or SDT are to be sent in association with, and multiplexed with, random access messages of the RACH procedure. , or both.

The set of resources configured via control signaling and allocated for UCI messages may include PUCCH resources, PUSCH resources, or both. For example, in some cases (e.g., some SDT configurations), control signaling may indicate a common set of PUCCH resources, a dedicated set of PUCCH resources, or both that may be used for UCI messages when UE 115-c is in an inactive or idle state. . For example, the control signaling may indicate a common PUCCH resource set corresponding to pucch-ResourceCommon. In the context of shared PUCCH resources, control signaling may indicate a PUCCH format dedicated to the RA-SDT procedure. Additionally or alternatively, the control signaling (eg, RRCReconfigurationMessage) may include one or more bit field values that UE 115-c may interpret as representing the indicated set of PUCCH resources.

By another example, the control signaling may indicate a dedicated set of PUCCH resources corresponding to PUCCH-Config. For example, while UE 115-c is in an RRC inactive state, UE 115-c may already be connected to the network such that base station 105-c already knows the identity of UE 115-c. Therefore, base station 105-c may configure UE 115-c using a dedicated set of PUCCH resources (eg, via control signaling).

In addition or alternatively, the control signaling may indicate the set of PUSCH resources used for UCI transmission when UE 115-c is in an inactive or idle state. For example, the control signaling may indicate that the UCI message will be multiplexed with Msg3 PUSCH resources for initial transmission and retransmission configured for the four-step RA-SDT procedure. In other words, the control signaling may indicate that the UCI message may be multiplexed on the PUSCH resources used to transmit Msg3 of the four-step RACH procedure.

At 510, UE 115-c may send random access messages (eg, a random access preamble) associated with the four-step RACH procedure between UE 115-c and base station 105-c. For example, as shown in Figure 5, UE 115-c may send Msg1 of the four-step RACH procedure. Msg1 may include a contention-based Physical Random Access Channel (PRACH) preamble. In some cases, UE 115-c may send Msg1 at 510 based on receiving the control signaling at 505.

At 515, UE 115-c may receive a second random access message (e.g., a random access response) from base station 105-c, where the second random access message at 515 is in response to the second random access message at 510. A random access message is received. For example, as shown in Figure 5, base station 105-c may send Msg2 of the four-step RACH procedure. Msg2 may include information associated with the four-step RACH procedure, including the detected preamble identifier for the preamble contained in Msg1, the TA command, the temporary Cellular Radio Network Temporary Identifier (C-RNTI) ) or any combination thereof. Additionally or alternatively, Msg2 may indicate a set of resources (eg, an uplink grant) that UE 115-c may use to send Msg3 of the four-step RACH procedure.

In some aspects, Msg2 may include separate control messages compared to the control signaling in 505. In additional or alternative implementations, the control signaling shown and described at 505 may be included with Msg2 shown and described at 515, or may be the same as Msg2 shown and described at 515. In this aspect, in some cases, Msg2 at 515 may include control signaling that configures UE 115-c to send SDT and UCI messages for RA-SDT in an inactive or idle state. resource set.

At 520, UE 115-c, base station 105-c, or both may perform TA verification. In other words, UE 115-c and/or base station 105-c may determine whether the TA for UE 115-c is valid or invalid. In some aspects, UE 115-c and/or base station 105-c may transmit/receive control signaling based on sending/receiving at 505, sending/receiving Msg1 at 510, sending/receiving Msg2 at 515, or any combination thereof. , to perform TA verification at 520. For example, in some aspects, UE 115-c may perform TA verification based on the TA command received via Msg2 and/or the TA timer.

In the context of the RA-SDT configuration based on the four-step RACH procedure, as shown and described in Figure 5, regardless of whether the UCI message is sent on the PUCCH resource or multiplexed with Msg3 of the four-step RACH procedure, for UCI Transmitted TA verifications may be applicable. For example, when the UCI message is to be multiplexed with Msg3 of the four-step RACH procedure (e.g., PUSCH resources for Msg3), UE 115-c can only send if the TA timer for UE 115-c is valid. UCI message. Similarly, if UE 115-c is configured to send UCI messages on PUCCH resources indicated via control signaling at 505 and/or Msg2 at 515, then the TA timer for UE 115-c must be valid. That is, in the context of the RA-SDT configuration of the four-step RACH procedure, UE 115-c can only send UCI messages on PUCCH resources when the TA for UE 115-c is valid, and in In the case where the TA for UE 115-c is invalid, UCI messages may not be sent on PUCCH resources.

At 525, UE 115-c can generate a UCI message. Specifically, UE 115-c may generate UCI when UE 115-c is in an inactive or idle state and upon deciding that UE 115-c has material (eg, control material) to send to base station 105-c message. UE 115-c may generate UCI messages based on receiving control signaling at 505, sending/receiving Msg1 at 510, sending/receiving Msg2 at 515, performing TA verification at 520, or any combination thereof. For example, UE 115-c may generate a UCI message at 525 based on determining at 520 that the TA for UE 115-c is valid.

At 530, UE 115-c may send a random access message (eg, a scheduled transmission) to base station 105-c. For example, as shown in Figure 5, UE 115-c may send Msg3 to base station 105-c as part of a four-step RACH procedure performed between UE 115-c and base station 105-c. In this case, Msg3 may include an identifier associated with the RACH procedure for contention resolution. UE 115-c may transmit/receive a control signal based on receiving it at 405, sending/receiving Msg1 at 510, sending/receiving Msg2 at 515, performing TA verification at 520, generating a UCI message at 525, or any combination thereof, To send Msg3 of the four-step RACH procedure.

At 535, UE 115-c may send a data message (eg, SDT) to base station 105-c. UE 115-c may send data messages at 535 when in an inactive or idle state. UE 115-c may transfer control signals based on receiving at 405, sending/receiving Msg1 at 510, sending/receiving Msg2 at 515, performing TA verification at 520, generating a UCI message at 525, sending Msg3 at 530, or any combination thereof, to send data messages (SDT).

Specifically, UE 115-c may send the SDT at 535 over at least a portion of a first set of resources used for data transmission via the control signaling at 505 (and/or the Msg2) assigned. Additionally, in the event that control signaling and/or Msg2 indicates that the data message is to be included with the random access message (e.g., multiplexed with the random access message), UE 115-c may send the SDT in conjunction with the random access message sent at 530 Msg3. For example, in some implementations, UE 115-c may multiplex SDT with the random access message sent at 530 (eg, multiplex SDT with Msg3).

At 540, UE 115-c may send the UCI message to base station 105-c. UE 115-c may send the UCI message at 540 when in an inactive or idle state. Additionally, UE 115-c may send the UCI within the uplink BWP configured for RA-SDT (e.g., via control signaling at 505 and/or the BWP for RA-SDT indicated by Msg2 at 515) message. UE 115-c may transfer the control signal based on receiving it at 405, send/receive Msg1 at 510, send/receive Msg2 at 515, perform TA verification at 520, generate a UCI message at 525, and send Msg3 at 530 , sending SDT at 535, or any combination thereof, to send the UCI message. Specifically, UE 115-c may, at 540, send the UCI message on at least a portion of a second set of resources used for UCI transmission via the control signaling at 505 and/or at 515 Msg2 allocated at.

Additionally, where control signaling 505 indicates that the UCI message is to be included with the random access message (e.g., multiplexed with the random access message), UE 115-c may send the UCI message along with Msg3 sent at 530 . For example, in some implementations, UE 115-c may multiplex the UCI message with the random access message sent at 530 (eg, UCI with Msg3 multiplexing). Additionally, in some implementations, UCI messages may be multiplexed with SDT at 535, as shown and described in Figure 3. For example, the control signaling and/or Msg2 may include instructions for UE 115-c to multiplex the UCI message with SDT within a second set of resources included in the first resources allocated for SDT. Concentrated. In this aspect, UE 115-c can perform multiplexing via a PUCCH resource set (e.g., a common PUCCH resource corresponding to pucch-ResourceCommon, a dedicated PUCCH resource corresponding to PUCCH-Config), a PUSCH resource set (e.g., multiplexing with Msg3 ) or both, to send UCI messages.

UE 115-c may send the UCI message at 540 based on the TA verification procedure at 520. As described previously in this article, in the context of the four-step RACH procedure, TA verification for UCI transmissions may be applicable regardless of whether the UCI message is sent on a PUCCH resource or multiplexed with Msg3 of the four-step RACH procedure. For example, when the UCI message is to be multiplexed with Msg3 of the four-step RACH procedure (e.g., PUSCH resource for Msg3), UE 115-c can send the UCI only when the TA timer for UE 115-c is valid message. Similarly, where UE 115-c is configured to send UCI messages on the PUCCH resources indicated via control signaling at 505 and/or Msg2 at 515, the TA timer for UE 115-c must efficient. That is, in the context of an RA-SDT configuration for a four-step RACH procedure, UE 115-c may only be able to send UCI messages on PUCCH resources if the TA for UE 115-c is valid, and may not be able to The UCI message is sent on PUCCH resources if the TA for UE 115-c is invalid.

The UCI message can include any uplink information, including HARQ feedback information, UE assistance information, etc. For example, the UCI message may include HARQ feedback information in response to contention resolution messages (eg, contention-based SDT contention resolution messages), HARQ feedback information in response to downlink control plane messages and/or downlink user plane messages. HARQ feedback information, HARQ feedback information in response to RRC release messages (e.g., RRCRelease messages used to reconfigure or release SDT resources for RA-SDT or CG-SDT), or any combination thereof. As another example, the UCI message may include a CSI report, a BWP index (e.g., an index of the preferred BWP), a beam failure report, a coverage enhancement request (e.g., a request for coverage enhancement for SDT), a request for termination of the data message set (e.g., a request for coverage enhancement for SDT). For example, early termination request for SDT), UE assistance information multiplexed with HARQ feedback (eg, CSI report multiplexed with HARQ feedback and mapped to UCI), or any combination thereof. For example, the UCI message may include a compact CSI report, which may help the network improve and optimize the spectral efficiency of SDT communications. In this case, the compact CSI report may be aperiodic, semi-static, or both, and may be smaller than the CSI report sent by UE 115-b when UE 115-b is active.

At 545, base station 105-c may send a random access message (eg, a contention resolution message) for the four-step RACH procedure. For example, as shown in Figure 5, base station 105-c may send Msg4 to UE 115-c as part of a four-step RACH procedure performed between UE 115-c and base station 105-c. In some aspects, Msg4 may include a contention resolution identifier associated with a RACH procedure performed between corresponding wireless devices.

The techniques described herein may facilitate more efficient use of resources by enabling UE 115-c to send UCI messages along with SDT when inactive and/or idle in the context of a two-step RACH procedure. In particular, by enabling UE 115-c to send UCI messages along with SDT in an inactive or idle state, the techniques described herein may enable UE 115-c to establish a full wireless connection with base station 105-c before (or after) sending a small amount of control data without establishing a full wireless connection with base station 105-c, which can reduce the signaling management burden associated with establishing a wireless connection between UE 115-c and the network, and can reduce the The delay associated with UCI messages.

FIG. 6 illustrates an example of a program flow 600 that supports techniques for UCI transmission with small data transmission, according to aspects of the subject matter. In some examples, the program flow 600 can implement the wireless communication system 100, the wireless communication system 200, the resource configuration 300, any combination thereof, or be implemented by these aspects. For example, program flow 600 illustrates UE 115-b sending a UCI message within resources allocated via a configured grant (eg, CG-SDT), as described with reference to Figures 1-3.

In some cases, program flow 600 may include UE 115-d and base station 105-d, which may be examples of respective devices as described herein. For example, UE 115-d and base station 105-d shown in FIG. 6 may include examples of UE 115-a and base station 105-a, respectively, as shown in FIG. 2 .

In some examples, the operations shown in program flow 600 may be performed by hardware (e.g., including circuits, processing blocks, logic elements, and other elements), code (e.g., software or firmware) executed by a processor or any combination thereof. The following alternative examples may be implemented in which some steps are performed in a different order than described, or some steps are not performed at all. In some cases, steps may include additional functionality not mentioned below, or more steps may be added.

At 605, UE 115-d may receive a control signaling from base station 105-d, wherein the control signaling identifies when UE 115-d is in an inactive state (e.g., RRC inactive state) and/or an idle state (e.g., , RRC idle state), one or more resource sets used for data transmission (e.g., SDT) and UCI messages. For example, the control signaling may indicate a first set of resources and a second set of resources that may be used to send SDT and UCI messages, respectively, when UE 115-d is in an inactive or idle state. In this example, the first set of resources for SDT may include uplink shared resources (eg, PUSCH resources), wherein the second set of resources for UCI transmission may include uplink shared resources (eg, PUSCH resources) and/or uplink control resources (for example, PUCCH resources).

In some implementations, the control signaling may include an RRC release message that releases UE 115-d from an active state (eg, RRC active state) to an inactive state and/or an idle state. In this case, when UE 115-d is in an active state (eg, RRC active state), UE 115-d may receive a control signal transfer (eg, RRCReleaseMessage). In some implementations, the BWP used for SDT communications (e.g., the BWP used for sending/receiving SDT and/or UCI messages in an inactive or idle state) may be active with the UE 115-d in which it receives the CG-SDT configuration. BWP is the same or different. In this aspect, UE 115-d may receive control signaling on the active BWP, where the control signaling indicates a set of resources for SDT and/or UCI messages on the same BWP, a different BWP, or both.

In some aspects, the control signaling may indicate an SDT configuration (e.g., RA-SDT) that defines whether (and when) UE 115-d can be used to determine if (and when) it can Send UCI messages along with a set of rules or conditions for SDT. For example, the control signaling may indicate whether the network supports transmission of UCI messages when UE 115-d is in an inactive or idle state, a resource set for sending SDT and/or UCI messages, etc. Another example is that the control signaling may indicate SDT configuration, which indicates whether UCI messages are to be sent separately from SDT, whether UCI messages are to be multiplexed with SDT, whether UCI messages must meet TA verification, etc. In the context of the CG-SDT configuration shown in Figure 6, the network (eg, base station 105-d) may enable and disable frequency hopping and/or coverage enhancement for UCI/SDT transmissions. Furthermore, in the context of CG-SDT configuration, control signaling may indicate whether UCI messages and/or SDT are to be sent separately, multiplexed with each other, or both.

The set of resources configured via control signaling and allocated for UCI messages may include PUCCH resources, PUSCH resources, or both. For example, in some cases (e.g., some SDT configurations), control signaling may indicate a common set of PUCCH resources, a dedicated set of PUCCH resources, or both that may be used for UCI messages when UE 115-d is in an inactive or idle state. . For example, the control signaling may indicate a common PUCCH resource set corresponding to pucch-ResourceCommon. In the context of shared PUCCH resources, control signaling may indicate a PUCCH format dedicated to the CG-SDT procedure. Additionally or alternatively, the control signaling (eg, RRCReconfigurationMessage) may include one or more bit field values that UE 115-d may interpret as representing the indicated set of PUCCH resources. As another example, the control signaling may indicate a dedicated set of PUCCH resources corresponding to PUCCH-Config. The PUCCH resource index, the number of repetitions of PUCCH transmission, the frequency hopping scheme of PUCCH, the TX beam index of PUCCH and the orthogonal code coverage of PUCCH can be signaled to the UE through DCI, MAC CE, system information or a hybrid signaling scheme. (OCC).

In addition or alternatively, the control signaling may indicate the set of PUSCH resources used for UCI transmission when UE 115-d is in an inactive or idle state. In such cases, the control signaling may indicate that the UCI message will be multiplexed with CG-PUSCH resources configured for the CG-SDT procedure. In other cases, the control signaling may indicate that UCI messages will be multiplexed with grant-based retransmissions of CG-PUSCH. In some aspects, the control signaling may indicate a set of transmission opportunities for SDT and/or UCI messages. For example, the control signaling may include configured authorization instructions/scheduling for sending SDT, UCI messages, or a set of transmission opportunities of both when UE 115-d is in an inactive or idle state. In this case, the control signaling may indicate that SDT and UCI messages will be multiplexed within the same transmission opportunity. In other cases, the control signaling may indicate that UE 115-d will suspend SDT transmission during the transmission opportunity to send UCI messages (e.g., suspend CG-PUSCH transmission to send UCI/PUCCH on the CG-SDT transmission opportunity) . In this aspect, the first set of resources and the second set of resources allocated for SDT and UCI messages respectively may include a set of transmission opportunities associated with PUSCH resources.

In some aspects, when the UCI message is to be multiplexed with the PUSCH resources of the SDT, the multiplexing scheme may be indicated in the RRC release message for CG-SDT (e.g., indicated via control signaling at 605) /parameters.

At 610, UE 115-d may enter an inactive state, an idle state, or both. For example, UE 115-d may receive a control signal transfer (eg, RRCReleaseMessage) at 605 while in an active state, and may subsequently enter or transition to an inactive and/or idle state. For example, in some cases, the RRC release message may release UE 115-d from an active state to an inactive or idle state.

At 615, UE 115-d, base station 105-d, or both may perform TA verification. In other words, UE 115-d and/or base station 105-d may determine whether the TA for UE 115-d is valid or invalid. In some aspects, UE 115-d and/or base station 105-d may perform TA at 615 based on sending/receiving control signaling at 605, entering an inactive or idle state at 610, or both. Verify. For example, in some aspects, UE 115-d may perform TA verification based on the TA command and/or TA timer received via control signaling at 605.

In the context of CG-SDT configuration, as shown and described in Figure 6, regardless of whether the UCI message is sent on PUCCH resources or multiplexed with CG-PUSCH resources for SDT, TA verification for UCI transmission All can be applied. Additionally, in the context of CG-SDT configuration, TA verification for UCI may be based on reference signal received power (RSRP) changes of the downlink reference signal, where the downlink may be configured by the network (e.g., base station 105-d) Reference signal beam set and RSRP threshold for TA verification. The downlink reference signal beams and RSRP thresholds associated with TA verification for UCI may be shared with CG-PUSCH or configured separately for UCI and SDT. In other words, the control signaling may indicate TA verification parameters (e.g., TA command, TA timer) that will be used to perform TA verification for both SDT and UCI messages, or may indicate for SDT and UCI messages respectively. Separate TA verification parameters for UCI messages.

In the case where the UE 115-d wants to multiplex UCI messages with SDT (eg, multiplex UCI with CG-PUSCH), different alternatives/implementations can be used to perform TA verification. For example, in some implementations, TA verification may be required for both UCI messages and SDT (eg, CG-PUSCH) when the TA verification parameters are different. In other words, both SDT and UCI messages may be required to pass separate TA verification before they can be sent. In other implementations, if the TA verification parameters/configuration are the same for SDT and UCI messages, then UE 115-d may be configured to only authenticate when the TA for SDT, UCI, or both passes (e.g., a valid TA). Send both SDT and UCI messages. Additionally, in other implementations, TA verification may be required for one of the SDT (eg, CG-SDT) or UCI messages, regardless of whether the TA verification parameters/configuration are shared for SDT and UCI, or configured separately.

In contrast, in the case where the UE 115-d is to send UCI messages on PUCCH resources, different alternatives/implementations can be used to perform TA verification. For example, in some implementations, UE 115-d may be required to perform TA verification before each transmission of UCI during SDT. In other words, UE 115-d may be configured to perform TA verification before each UCI message sent via PUCCH resources. As another example, in some implementations, UE 115-d and/or base station 105-d may suspend TA verification so that UE 115-d is not required to perform TA verification on UCI messages sent via PUCCH. For example, UE 115-d may suspend TA verification within the time window configured by the network.

At 620, UE 115-d may generate a UCI message. Specifically, UE 115-d may generate UCI when UE 115-d is in an inactive or idle state and upon deciding that UE 115-d has material (eg, control material) to send to base station 105-d message. UE 115-d may generate UCI information at 620 based on receiving a control signal transfer at 605, entering an inactive or idle state at 610, performing TA verification at 615, or any combination thereof. For example, UE 115-d may generate a UCI message at 620 based on a determination at 615 that one or more TAs are valid for UE 115-d.

At 625, UE 115-d may send a data message (eg, SDT) to base station 105-d. UE 115-d may send data messages at 625 while in an inactive or idle state. UE 115-d may send a data message (SDT) based on receiving a control signal transfer at 605, entering an inactive or idle state at 610, performing TA verification at 615, generating a UCI message at 620, or any combination thereof. .

In particular, UE 115-d may send the SDT at 625 on at least a portion of the first set of resources allocated by the control signaling at 605 for data transmission. For example, UE 115-d may send SDT within a PUSCH transmission opportunity configured for SDT via control signaling at 605 (eg, a CG-SDT transmission opportunity).

At 630, UE 115-d may send the UCI message to base station 105-d. UE 115-d may send the UCI message at 630 when in an inactive or idle state. Additionally, UE 115-d may send the UCI message within the uplink BWP configured for CG-SDT (eg, the BWP for CG-SDT indicated via control signaling at 605). UE 115-d may based on receiving a control signal transfer at 405, entering an inactive or idle state at 610, performing TA verification at 615, generating a UCI message at 620, sending an SDT at 625, or any combination thereof. Send UCI message.

In particular, UE 115-d may send the UCI message at 630 on at least a portion of the second set of resources for UCI transmission allocated via the control signaling at 605. For example, UE 115-d may send SDT within a PUSCH transmission opportunity configured via control signaling at 605 (eg, a CG-SDT transmission opportunity). In some cases, UE 115-d may be configured to multiplex the SDT at 625 and the UCI message at 630 within the same transmission opportunity (eg, a PUSCH transmission opportunity) configured via control signaling at 605. In other cases, UE 115-d may send the UCI message and SDT via separate transmission opportunities. For example, in some cases, UE 115-d may avoid sending SDT at the first transmission opportunity (eg, suspend SDT) in order to send the UCI message at the first transmission opportunity. In this case, UE 115-d may send the suspended SDT in a different (eg, subsequent) transmission opportunity.

In additional or alternative implementations, UE 115-d may communicate via a shared PUCCH resource set (e.g., PUCCH resources corresponding to pucch-ResourceCommon), a dedicated PUCCH resource set (e.g., PUCCH resources corresponding to PUCCH-Config), or both. or, to send UCI messages.

UE 115-d may send the UCI message at 630 based on the TA verification procedure at 615. As previously described in this article, in the context of the CG-SDT procedure, regardless of whether the UCI message is sent on PUCCH resources or PUSCH resources (e.g., multiplexed with SDT on CG-PUSCH resources), for UCI transmission All TA verifications can be applied. For example, in the case where UE 115-d is multiplexed with SDT on PUSCH resources, UE 115-d may be based on identifying that the TA for UCI is valid, the TA for SDT is valid, and the TA for both UCI and SDT is valid. Valid, or any combination thereof, to send UCI messages and SDT. In contrast, where UE 115-d is configured to send UCI messages via PUCCH resources, UE 115-d may be configured to perform TA verification before each transmission of UCI, and/or may be configured to pause TA verification (for example, suspend TA verification within the time window configured by the network).

The techniques described herein may facilitate more efficient use of resources by enabling UE 115-d to send UCI messages along with SDT in the context of CG-SDT procedures when inactive and/or idle. In particular, by enabling UE 115-d to send UCI messages along with SDT in an inactive or idle state, the techniques described herein may enable UE 115-d to establish a full wireless connection with base station 105-d (or before sending a small amount of control data without establishing a full wireless connection with the base station 105-d), which can reduce the signaling management burden associated with establishing a wireless connection between the UE 115-d and the network, and can reduce the The delay associated with UCI messages.

7 illustrates a block diagram 700 of a device 705 that supports techniques for UCI transmission with small data transmission, in accordance with aspects of the disclosure. Device 705 may be an example of some aspects of UE 115 as described herein. Device 705 may include a receiver 710, a transmitter 715, and a communications manager 720. Device 705 may also include one or more processors, memory coupled to the one or more processors, and memory executable by the one or more processors to enable the one or more processors to perform the execution herein. Instructions for UCI transfer characteristics in question. Each of these elements may communicate with one another (eg, via one or more busses).

Receiver 710 may provide for receiving, for example, packets, user data, control channels associated with various information channels (e.g., control channels, data channels, information channels related to techniques for UCI transmission with small data transmission) information, or any combination thereof. Information can be communicated to other components of the device 705. Receiver 710 may utilize a single antenna or a set of multiple antennas.

Transmitter 715 may provide means for transmitting signals generated by other elements of device 705 . For example, the transmitter 715 may send packets, user data, control information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to technologies used for UCI transmission with small data transmissions) , or any combination thereof. In some examples, transmitter 715 may be collocated with receiver 710 in a transceiver module. Transmitter 715 may utilize a single antenna, or may utilize a set of multiple antennas.

Communications manager 720, receiver 710, transmitter 715, or various combinations thereof, or various elements thereof, may be examples of components for various aspects of techniques for performing UCI transmissions with small data transmissions, as described herein. . For example, communications manager 720, receiver 710, transmitter 715, or various combinations or elements thereof may support methods for performing one or more of the functions described herein.

In some examples, communication manager 720, receiver 710, transmitter 715, or various combinations or elements thereof may be implemented using hardware (eg, using communication management circuitry). The hardware may include a processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, individual gate or transistor logic devices, individual Hardware components, or any combination thereof, configured as or otherwise supporting means for performing the functions described in this context. In some examples, a processor and memory coupled to the processor may be configured to perform one or more of the functions described herein (eg, by execution by the processor of instructions stored in memory).

Additionally or alternatively, in some examples, communications manager 720, receiver 710, transmitter 715, or various combinations or elements thereof may be implemented using code executed by a processor (eg, as communications management software or firmware) . If implemented with code executed by a processor, the functions of communications manager 720, receiver 710, transmitter 715, or various combinations or elements thereof may be implemented by a general-purpose processor, DSP, central processing unit (CPU), ASIC, FPGA , or any combination of these or other programmable logic devices (e.g., configured to or otherwise support components for performing the functions described in this context).

In some examples, communications manager 720 may be configured to use or otherwise coordinate with receiver 710 , transmitter 715 , or both to perform various operations (e.g., receive, monitoring, sending). For example, communications manager 720 may receive information from receiver 710, send information to transmitter 715, or combine with receiver 710, transmitter 715, or both to receive information, send information, or perform various other operations as described herein. .

For example, communications manager 720 may be configured or otherwise support means for receiving control signaling from a base station that identifies the control signaling used by the UE when the UE is in an inactive or idle state. A first set of resources for data transmission and a second set of resources for UCI transmission. Communications manager 720 may be configured or otherwise support means for generating UCI messages based on the second set of resources when the UE is in one of the inactive or idle states. Communications manager 720 may be configured or otherwise support means for transmitting to a base station on at least a portion of the first set of resources when the UE is in one of an inactive state or an idle state. data message, and sends the UCI message to the base station on the second resource set.

By including or configuring communications manager 720 in accordance with examples as described herein, device 705 (e.g., a processor for controlling or otherwise coupled to receiver 710, transmitter 715, communications manager 720, or combinations thereof ) may support techniques that facilitate more efficient use of resources by enabling the UE 115 to send UCI messages along with SDT when the UE 115 is inactive and/or idle in the context of a CG-SDT procedure. In particular, by enabling the UE 115 to send UCI messages along with SDT when in an inactive or idle state, the techniques described herein may enable the UE 115 to establish a full wireless connection with the base station 105 (or without connecting to the base station 105 A small amount of control data is sent when a complete wireless connection is established, which can reduce the signaling management burden associated with establishing a wireless connection between the UE 115 and the network, and can reduce the latency associated with UCI messages.

8 illustrates a block diagram 800 of a device 805 that supports technology for UCI transmission with small data transmission, in accordance with aspects of the subject matter. Device 805 may be an example of some aspect of device 705 or UE 115 as described herein. Device 805 may include a receiver 810, a transmitter 815, and a communications manager 820. Device 805 may also include a processor. Each of these elements may communicate with one another (eg, via one or more busses).

Receiver 810 may provide for receiving, for example, packets, user data, control channels associated with various information channels (e.g., control channels, data channels, information channels related to techniques for UCI transmission with small data transmission) information, or any combination thereof. Information can be communicated to other components of the device 805. Receiver 810 may utilize a single antenna or a set of multiple antennas.

Transmitter 815 may provide means for transmitting signals generated by other elements of device 805 . For example, the transmitter 815 may send packets, user data, control information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to technologies used for UCI transmission with small data transmissions) , or any combination thereof. In some examples, transmitter 815 may be collocated with receiver 810 in a transceiver module. For example, transmitter 815 may utilize a single antenna, or may utilize a set of multiple antennas.

Device 805 or its various elements may be examples of components for performing various aspects of techniques for UCI transmission with small data transmission, as described herein. For example, the communication manager 820 may include a control signaling reception manager 825, a UCI generation manager 830, an uplink transmission manager 835, or any combination thereof. Communications manager 820 may be examples of various aspects of communications manager 720 as described herein. In some examples, communications manager 820 or its various elements may be configured to use or otherwise coordinate with receiver 810 , transmitter 815 , or both to perform various operations (e.g., , receiving, monitoring, sending). For example, communications manager 820 may receive information from receiver 810, send information to transmitter 815, or combine with receiver 810, transmitter 815, or both to receive information, send information, or perform various other operations as described herein. .

The control signaling reception manager 825 may be configured or otherwise support means for receiving control signaling from a base station, the control signaling being identified by the UE when the UE is in an inactive or idle state. A first set of resources for data transmission and a second set of resources for UCI transmission. UCI generation manager 830 may be configured or otherwise support means for generating UCI messages based on the second set of resources when the UE is in one of the inactive or idle states. The uplink transmission manager 835 may be configured or otherwise support means for transmitting data on at least a portion of the first set of resources when the UE is in one of an inactive state or an idle state. The base station sends the data message and sends the UCI message to the base station on the second resource set.

In some cases, control signaling reception manager 825, UCI generation manager 830, and uplink transmission manager 835 may each be or at least be a processor (eg, a transceiver processor, or a radio processor, or a transmitter processor or receiver processor). The processor may be coupled to the memory and execute instructions stored in the memory, enabling the processor to perform or facilitate the control signal transfer reception manager 825, UCI generation manager 830 and uplink transmission management as discussed herein. Characteristics of device 835. The transceiver processor may be co-located with and/or communicate with the device's transceiver (e.g., to direct its operation). The radio processor may be colocated with and/or communicate with (eg, direct the operation of) the device's radio (eg, NR radio, LTE radio, Wi-Fi radio). The transmitter processor may be co-located with and/or in communication with the device's transmitter (e.g., direct its operation). The receiver processor may be collocated with the device's receiver and/or communicate with the receiver (e.g., direct its operation).

9 illustrates a block diagram 900 of a communications manager 920 that supports technologies for UCI transmission with small data transmission, in accordance with aspects of the subject matter. Communications manager 920 may be an example of communications manager 720, communications manager 820, or some aspect of both described herein. Communications manager 920, or its various elements, may be examples of components of various aspects of the techniques (as described herein) for performing UCI transmissions with small data transmissions. For example, the communication manager 920 may include a control signaling reception manager 925, a UCI generation manager 930, an uplink transmission manager 935, a RACH reception manager 940, a RACH transmission manager 945, a TA manager 950, or any combination thereof. . Each of these elements may communicate with each other directly or indirectly (eg, via one or more buses).

The control signaling reception manager 925 may be configured or otherwise support means for receiving control signaling from a base station, the control signaling being identified by the UE when the UE is in an inactive or idle state. A first set of resources for data transmission and a second set of resources for UCI transmission. The UCI generation manager 930 may be configured or otherwise support means for generating UCI messages based on the second set of resources when the UE is in one of an inactive state or an idle state. The uplink transmission manager 935 may be configured or otherwise support means for transmitting data on at least a portion of the first set of resources when the UE is in one of an inactive state or an idle state. The base station sends the data message and sends the UCI message to the base station on the second resource set.

In some examples, to support reception control signaling, the RACH reception manager 940 may be configured or otherwise support: means for receiving a random access message from a base station for a random access procedure, the random access message A first set of resources and a second set of resources are identified.

In some examples, to support reception control signaling, the control signaling reception manager 925 may be configured or otherwise supported for receiving and releasing the UE from the active state to the base station when the UE is in the active state. Components of a message associated with an inactive state or an idle state, where the message identifies a first set of resources and a second set of resources.

In some examples, to support sending UCI messages, the RACH sending manager 945 may be configured or otherwise support: for sending the UCI message on the second set of resources along with the random access message of the random access procedure. component.

In some examples, the uplink transmission manager 935 may be configured or otherwise support means for transmitting UCI messages using random access messages based on identifying that the TA for the UE is valid. . In some examples, the uplink transmission manager 935 may be configured or otherwise support means for transmitting UCI using a random access message after identifying that the TA for the UE is invalid. message. In some examples, a control signaling is received while the UE is in an active state, the control signaling indicating a set of multiple transmission opportunities for data transmission, the set of multiple transmission opportunities including a first set of resources, wherein the data message and The UCI message is sent within a transmission opportunity in the set of multiple transmission opportunities.

In some examples, to support transmission of data messages and UCI messages, the uplink transmission manager 935 may be configured or otherwise support components for multiplexing data messages and UCI messages within a transmission opportunity. In some examples, in order to support sending data messages and UCI messages, the uplink transmission manager 935 may be configured or otherwise supported: for generating the UCI message to be sent in the first transmission opportunity to avoid sending the UCI message in the first transmission opportunity. A component for sending a data message in the first transmission opportunity in a set of multiple transmission opportunities. In some examples, to support sending data messages and UCI messages, the uplink sending manager 935 may be configured or otherwise support: means for sending UCI messages within the first transmission opportunity based on avoiding sending data messages. . In some examples, in order to support sending data messages and UCI messages, the uplink sending manager 935 may be configured or otherwise support: based on sending the UCI message in the first transmission opportunity, in the multiple transmission opportunities. A component that sends a data message within the second transmission opportunity in the set.

In some examples, the control signaling reception manager 925 may be configured or otherwise support means for receiving, via control signaling, an indication for the UE to multiplex UCI and data messages within the second set of resources. , the second resource set is included in the first resource set, wherein sending data messages and UCI messages is based at least in part on the indication. In some examples, the second set of resources includes a set of common uplink control resources, a set of dedicated uplink control resources, or any combination thereof. In some examples, the first set of resources includes a set of uplink shared resources.

In some examples, the uplink transmission manager 935 may be configured or otherwise support means for transmitting UCI messages based on identifying that the TA for the UE is valid.

In some examples, to support identifying that a TA for a UE is valid, TA manager 950 may be configured or otherwise support means for identifying that a first TA for a UCI message is valid. , the second TA for data messages is valid, the third TA for both UCI messages and data messages is valid, or any combination thereof.

In some examples, the control signaling reception manager 925 may be configured or otherwise support means for receiving an indication of suspension of TA authentication at the UE via control signaling, wherein sending a UCI message is at least Partly in response to the suspension of TA verification. In some examples, the UCI message includes HARQ feedback in response to a contention resolution message, a downlink control plane message, a downlink user plane message, an RRC release message, or any combination thereof. In some examples, the UCI message includes: a first CSI report that is smaller than a second CSI report for the active state, a beam failure report, a BWP index, a coverage enhancement request, a request to terminate a data message set including the data message, or any combination thereof.

In some cases, the control signaling reception manager 925, UCI generation manager 930, uplink transmission manager 935, RACH reception manager 940, RACH transmission manager 945, and TA manager 950 may each be or at least process part of a processor (e.g., a transceiver processor, or a radio processor, or a transmitter processor, or a receiver processor). The processor can be coupled to the memory and execute instructions stored in the memory to enable the processor to perform or facilitate the control signal transfer reception manager 925, UCI generation manager 930, and uplink transmission management discussed herein. 935, RACH receive manager 940, RACH transmit manager 945 and TA manager 950.

10 illustrates a diagram of a system 1000 including a device 1005 that supports techniques for UCI transmission with small data transmission, in accordance with aspects of the disclosure. Device 1005 may be an example of, or include a component of, device 705 , device 805 , or UE 115 as described herein. Device 1005 may communicate wirelessly with one or more base stations 105, UEs 115, or any combination thereof. Device 1005 may include elements for two-way voice and data communications, including elements for sending and receiving communications, such as communications manager 1020, input/output (I/O) controller 1010, transceiver 1015, antenna 1025, Memory 1030, code 1035 and processor 1040. These elements may be in electrical communication or otherwise coupled (eg, operatively, communicatively, functionally, electronically, electrically) via one or more busses (eg, bus 1045).

I/O controller 1010 can manage input and output signals to device 1005. I/O controller 1010 can also manage peripheral devices that are not integrated into device 1005. In some cases, I/O controller 1010 may represent a physical connection or port to external peripheral devices. In some cases, I/O controller 1010 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, or another known operating system. Additionally or alternatively, I/O controller 1010 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I/O controller 1010 may be implemented as part of a processor (eg, processor 1040). In some cases, a user may interact with device 1005 via I/O controller 1010 or via hardware components controlled by I/O controller 1010 .

In some cases, the device 1005 may include a single antenna 1025. However, in some other cases, the device 1005 may have more than one antenna 1025 capable of transmitting or receiving multiple wireless transmissions simultaneously. Transceiver 1015 may communicate bidirectionally via one or more antennas 1025, wired links, or wireless links, as described herein. For example, transceiver 1015 may represent a wireless transceiver and may be in two-way communication with another wireless transceiver. Transceiver 1015 may also include a modem to modulate packets, provide the modulated packets to one or more antennas 1025 for transmission, and decode packets received from one or more antennas 1025. tune. As described herein, transceiver 1015, or transceiver 1015 and one or more antennas 1025 may be examples of transmitter 715, transmitter 815, receiver 710, receiver 810, or any combination or elements thereof.

Memory 1030 may include random access memory (RAM) and read only memory (ROM). Memory 1030 may store computer-readable, computer-executable code 1035 including instructions that, when executed by processor 1040, cause device 1005 to perform the various functions described herein. Code 1035 may be stored in non-transitory computer-readable media such as system memory or other types of memory. In some cases, the code 1035 may not be executed directly by the processor 1040 but instead cause the computer (eg, when compiled and executed) to perform the functions described herein. In some cases, specifically, memory 1030 may contain a basic I/O system (BIOS) that may control basic hardware or software operations (eg, interaction with peripheral components or devices).

Processor 1040 may include an intelligent hardware device (e.g., general purpose processor, DSP, CPU, microcontroller, ASIC, FPGA, programmable logic device, discrete gate or transistor logic element, discrete hardware element, or any combination thereof ). In some cases, processor 1040 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1040. Processor 1040 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1030) to cause device 1005 to perform various functions (e.g., support technology for UCI transmission with small data transmission function or task). For example, device 1005 or elements of device 1005 may include processor 1040 and memory 1030 coupled to processor 1040, processor 1040 and memory 1030 configured to perform various functions described herein.

For example, communications manager 1020 may be configured or otherwise support means for receiving control signaling from a base station that identifies the control signaling used by the UE when the UE is in an inactive or idle state. A first set of resources for data transmission and a second set of resources for UCI transmission. Communications manager 1020 may be configured or otherwise support means for generating UCI messages based on the second set of resources when the UE is in one of the inactive or idle states. Communications manager 1020 may be configured or otherwise support means for transmitting to a base station on at least a portion of a first set of resources when the UE is in one of an inactive state or an idle state. data message, and sends the UCI message to the base station on the second resource set.

By including or configuring the communications manager 1020 in accordance with examples as described herein, the device 1005 can enable the UE 115 to send UCI when in an inactive state and/or idle state in the context of a CG-SDT procedure. Messaging, along with SDT, supports technologies that promote more efficient use of resources. In particular, by enabling the UE 115 to send UCI messages along with SDT when in an inactive or idle state, the techniques described herein may enable the UE 115 to establish a full wireless connection with the base station 105 (or without connecting to the base station 105 A small amount of control data is sent when a complete wireless connection is established, which can reduce the signaling management burden associated with establishing a wireless connection between the UE 115 and the network, and can reduce the latency associated with UCI messages. Additionally, the techniques described herein may reduce power consumption at the UE 115 and increase battery life by preventing the UE 115 from the need to establish a full wireless connection to the network to send small amounts of data.

In some examples, communications manager 1020 may be configured to use, or otherwise interact with, transceiver 1015 , one or more antennas 1025 , or any combination thereof. Coordinate to perform various operations (e.g., receive, monitor, send). Although communications manager 1020 is shown as a separate component, in some examples, one or more functions described with reference to communications manager 1020 may be supported by processor 1040, memory 1030, code 1035, or any combination thereof or implement. For example, code 1035 may include instructions executable by processor 1040 to cause device 1005 to perform aspects of techniques for UCI transmission with small data transmission, as described herein, or processor 1040 and memory 1030 May additionally be configured to perform or support such operations.

11 illustrates a block diagram 1100 of a device 1105 that supports technology for UCI transmission with small data transmission, in accordance with aspects of the subject matter. Device 1105 may be an example of some aspects of base station 105 as described herein. Device 1105 may include a receiver 1110, a transmitter 1115, and a communications manager 1120. Device 1105 may also include one or more processors, memory coupled to the one or more processors, and memory executable by the one or more processors to enable the one or more processors to perform the execution herein. Instructions for UCI transfer characteristics in question. Each of these elements may communicate with one another (eg, via one or more busses).

The receiver 1110 may provide for receiving, for example, packets, user data, control channels associated with various information channels (e.g., control channels, data channels, information channels related to techniques for UCI transmission with small data transmission) information, or any combination thereof. Information can be communicated to other components of the device 1105. Receiver 1110 may utilize a single antenna or a set of multiple antennas.

Transmitter 1115 may provide a means for transmitting signals generated by other elements of device 1105 . For example, the transmitter 1115 may send packets, user data, control information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to technologies used for UCI transmission with small data transmissions) , or any combination thereof. In some examples, transmitter 1115 may be collocated with receiver 1110 in a transceiver module. For example, transmitter 1115 may utilize a single antenna, or may utilize a set of multiple antennas.

Communications manager 1120, receiver 1110, transmitter 1115, or various combinations thereof, or various elements thereof, may be components for performing various aspects of techniques for UCI transmission with small data transmission, as described herein. example. For example, communications manager 1120, receiver 1110, transmitter 1115, or various combinations or elements thereof may support methods for performing one or more of the functions described herein.

In some examples, communication manager 1120, receiver 1110, transmitter 1115, or various combinations or elements thereof may be implemented using hardware (eg, using communication management circuitry). The hardware may include a processor, DSP, ASIC, FPGA or other programmable logic device, individual gate or transistor logic devices, individual hardware elements, or any combination thereof configured or otherwise supported for execution Components of the functionality described in this case content. In some examples, a processor and memory coupled to the processor may be configured to perform one or more of the functions described herein (eg, by execution by the processor of instructions stored in memory).

Additionally or alternatively, in some examples, communications manager 1120, receiver 1110, transmitter 1115, or various combinations or elements thereof may be implemented using code executed by a processor (eg, as communications management software or firmware) . If implemented with code executed by a processor, the functions of communications manager 1120, receiver 1110, transmitter 1115, or various combinations or elements thereof may be implemented by a general purpose processor, DSP, CPU, ASIC, FPGA, or these or other Any combination of programmable logic devices (e.g., configured to or otherwise support components for performing the functions described in this context) executes.

In some examples, communications manager 1120 may be configured to use or otherwise coordinate with receiver 1110 , transmitter 1115 , or both to perform various operations (e.g., receive, monitoring, sending). For example, communications manager 1120 may receive information from receiver 1110, send information to transmitter 1115, or combine with receiver 1110, transmitter 1115, or both to receive information, send information, or perform various other operations as described herein. .

According to examples disclosed herein, communications manager 1120 may support wireless communications at a base station. For example, the communications manager 1120 may be configured or otherwise support means for sending control signaling to the UE that identifies the UE to be used for data while the UE is in an inactive or idle state. A first set of resources for transmission and a second set of resources for UCI transmission. Communications manager 1120 may be configured or otherwise support means for receiving data messages from the UE on at least a portion of the first set of resources when the UE is in one of an inactive state or an idle state. , and receiving the UCI message from the UE on the second resource set.

By including or configuring communications manager 1120 according to examples as described herein, device 1105 (e.g., a processor controlling or otherwise coupled to receiver 1110, transmitter 1115, communications manager 1120, or combinations thereof) can Techniques for promoting more efficient use of resources are supported by enabling the UE 115 to send UCI messages along with SDT when inactive and/or idle in the context of CG-SDT procedures. In particular, by enabling the UE 115 to send UCI messages along with SDT when in an inactive or idle state, the techniques described herein may enable the UE 115 to establish a full wireless connection with the base station 105 (or without connecting to the base station 105 A small amount of control data is sent when a complete wireless connection is established, which can reduce the signaling management burden associated with establishing a wireless connection between the UE 115 and the network, and can reduce the latency associated with UCI messages. Additionally, the techniques described herein may reduce power consumption at the UE 115 and increase battery life by preventing the UE 115 from the need to establish a full wireless connection to the network to send small amounts of data.

12 illustrates a block diagram 1200 of a device 1205 that supports technology for UCI transmission with small data transmission, in accordance with aspects of the subject matter. Device 1205 may be an example of some aspect of device 1105 or base station 105 as described herein. Device 1205 may include a receiver 1210, a transmitter 1215, and a communications manager 1220. Device 1205 may also include a processor. Each of these elements may communicate with one another (eg, via one or more busses).

The receiver 1210 may provide for receiving, for example, packets, user data, control channels associated with various information channels (e.g., control channels, data channels, information channels related to techniques for UCI transmission with small data transmission) information, or any combination thereof. Information can be communicated to other components of the device 1205. Receiver 1210 may utilize a single antenna or a set of multiple antennas.

Transmitter 1215 may provide means for transmitting signals generated by other elements of device 1205 . For example, the transmitter 1215 may send packets, user data, control information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to technologies used for UCI transmission with small data transmissions) , or any combination thereof. In some examples, transmitter 1215 may be collocated with receiver 1210 in a transceiver module. For example, transmitter 1215 may utilize a single antenna, or may utilize a set of multiple antennas.

Device 1205 or its various elements may be examples of components for performing various aspects of techniques for UCI transmission with small data transmission, as described herein. For example, the communications manager 1220 may include a control signaling transmit manager 1225, an uplink receive manager 1230, or any combination thereof. Communications manager 1220 may be various examples of aspects of communications manager 1120 as described herein. In some examples, communications manager 1220 or its various elements may be configured to use or otherwise coordinate with receiver 1210, transmitter 1215, or both to perform various operations ( e.g. receiving, monitoring, sending). For example, communications manager 1220 may receive information from receiver 1210, send information to transmitter 1215, or combine with receiver 1210, transmitter 1215, or both to receive information, send information, or perform various other operations as described herein. .

According to examples disclosed herein, communications manager 1220 may support wireless communications at a base station. The control signaling transmission manager 1225 may be configured or otherwise support means for transmitting control signaling to the UE, the control signaling identification being used by the UE when the UE is in an inactive or idle state. A first set of resources for data transmission and a second set of resources for UCI transmission. The uplink reception manager 1230 may be configured or otherwise support means for receiving data from the UE on at least a portion of the first set of resources when the UE is in one of an inactive state or an idle state. Receive data messages, and receive UCI messages from the UE on the second resource set.

In some cases, the control signaling transmit manager 1225 and the uplink receive manager 1230 may each be, or at least be, a processor (eg, a transceiver processor, or a radio processor, or a transmitter processor, or a receiver processor). part of the device). The processor may be coupled to the memory and execute instructions stored in the memory, enabling the processor to perform or facilitate the control signaling transmit manager 1225 and uplink receive manager 1230 features discussed herein. The transceiver processor may be co-located with and/or communicate with the device's transceiver (e.g., to direct its operation). The radio processor may be colocated with and/or communicate with (eg, direct the operation of) the device's radio (eg, NR radio, LTE radio, Wi-Fi radio). The transmitter processor may be co-located with and/or in communication with the device's transmitter (e.g., direct its operation). The receiver processor may be collocated with the device's receiver and/or communicate with the receiver (e.g., direct its operation).

13 illustrates a block diagram 1300 of a communications manager 1320 that supports technologies for UCI transmission with small data transmission, in accordance with aspects of the disclosure. Communications manager 1320 may be an example of communications manager 1120, communications manager 1220, or some aspect of both described herein. Communications manager 1320, or its various elements, may be examples of components for performing various aspects of techniques for UCI transmission with small data transmission, as described herein. For example, the communication manager 1320 may include a control signaling transmission manager 1325, an uplink reception manager 1330, a RACH transmission manager 1335, a RACH reception manager 1340, or any combination thereof. Each of these elements may communicate with each other directly or indirectly (eg, via one or more buses).

According to examples disclosed herein, communications manager 1320 may support wireless communications at a base station. The control signaling transmission manager 1325 may be configured or otherwise support means for transmitting a control signaling to a UE that identifies a first set of resources for data transmission and when the UE The second set of resources used by the UE for UCI transmission when in an inactive state or idle state. The uplink reception manager 1330 may be configured or otherwise support means for receiving data from the UE on at least a portion of the first set of resources when the UE is in one of an inactive state or an idle state. Receive the data message and receive the UCI message from the UE on the second resource set.

In some examples, to support transmission control signaling, the RACH transmission manager 1335 may be configured or otherwise support means for transmitting a random access message for a random access procedure, wherein the random access message identifies The first resource set and the second resource set.

In some examples, to support transmitting control signaling, the control signaling transmission manager 1325 may be configured or otherwise support means for transmitting to and removing the UE from the active state when the UE is in the active state. A message associated with releasing to an inactive state or an idle state, wherein the message identifies the first resource set and the second resource set.

In some examples, to support receipt of UCI messages, RACH reception manager 1340 may be configured or otherwise support means for receiving random access messages on a second resource set along with random access procedures. UCI message.

In some examples, the control signaling transmission manager 1325 may be configured or otherwise support means for multiplexing UCI and data messages for the UE to be included in the first set of resources via control signaling. An instruction within the second resource set, wherein receiving the data message and the UCI message is at least partially in response to sending the instruction. In some examples, the second set of resources includes a set of common uplink control resources, a set of dedicated uplink control resources, or any combination thereof. In some examples, the first set of resources includes a set of uplink shared resources.

In some examples, the control signaling transmission manager 1325 may be configured or otherwise support means for transmitting, via control signaling, an indication of suspension of TA authentication at the UE, wherein receipt of the UCI message is at least Partly in response to the suspension of TA verification. In some examples, the UCI message includes HARQ feedback in response to a contention resolution message, a downlink control plane message, a downlink user plane message, an RRC release message, or any combination thereof. In some examples, the UCI message includes: a first CSI report that is smaller than a second CSI report for the active state, a beam failure report, a BWP index, a coverage enhancement request, a request to terminate a set of data messages including a data message, or any combination thereof.

In some cases, control signaling transmit manager 1325, uplink receive manager 1330, RACH transmit manager 1335, and RACH receive manager 1340 may each be or at least be a processor (eg, a transceiver processor, or a radio processor, or transmitter processor or receiver processor). The processor may be coupled to the memory and execute instructions stored in the memory, enabling the processor to perform or facilitate the control signal transfer transmission manager 1325, uplink reception manager 1330, RACH transmission management discussed herein. 1335 and RACH reception manager 1340 features.

14 illustrates a diagram of a system 1400 including a device 1405 that supports technology for UCI transmission with small data transmission, in accordance with aspects of the disclosure. Device 1405 may be an example of, or include a component of, device 1105 , device 1205 , or base station 105 as described herein. Device 1405 may communicate wirelessly with one or more base stations 105, UEs 115, or any combination thereof. Device 1405 may include components for two-way voice and data communications, including components for sending and receiving communications, such as communications manager 1420, network communications manager 1410, transceiver 1415, antenna 1425, memory 1430, code 1435, processor 1440 and inter-site communication manager 1445. These elements may be in electrical communication or otherwise coupled (eg, operatively, communicatively, functionally, electronically, electrically) via one or more busses (eg, busbar 1450).

Network communications manager 1410 may manage communications with core network 130 (eg, via one or more wired backhaul links). For example, network communications manager 1410 may manage the transmission of data communications for client devices (eg, one or more UEs 115).

In some cases, the device 1405 may include a single antenna 1425. However, in some other cases, the device 1405 may have more than one antenna 1425 capable of transmitting or receiving multiple wireless transmissions simultaneously. Transceiver 1415 may communicate bidirectionally via one or more antennas 1425, wired links, or wireless links, as described herein. For example, transceiver 1415 may represent a wireless transceiver and may be in two-way communication with another wireless transceiver. Transceiver 1415 may also include a modem to modulate packets to provide modulated packets to one or more antennas 1425 for transmission, and to perform processing on packets received from one or more antennas 1425 Demodulation. As described herein, transceiver 1415 or transceiver 1415 and one or more antennas 1425 may be examples of transmitter 1115, transmitter 1215, receiver 1110, receiver 1210, or any combination or elements thereof.

Memory 1430 may include RAM and ROM. Memory 1430 may store computer-readable, computer-executable code 1435 including instructions that, when executed by processor 1440, cause the device 1405 to perform the various functions described herein. Code 1435 may be stored in non-transitory computer-readable media such as system memory or other types of memory. In some cases, code 1435 may not be executed directly by processor 1440 but may cause a computer (eg, when compiled and executed) to perform the functions described herein. In some cases, specifically, memory 1430 may contain a BIOS that may control basic hardware or software operations (eg, interaction with peripheral components or devices).

Processor 1440 may include an intelligent hardware device (e.g., general purpose processor, DSP, CPU, microcontroller, ASIC, FPGA, programmable logic device, discrete gate or transistor logic element, discrete hardware element, or any combination thereof ). In some cases, processor 1440 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1440. Processor 1440 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1430) to cause device 1405 to perform various functions (e.g., support technology for UCI transmission with small data transmission function or task). For example, device 1405 or elements of device 1405 may include a processor 1440 and memory 1430 coupled to processor 1440, the processor 1440 and memory 1430 being configured to perform the various functions described herein.

Inter-site communications manager 1445 may manage communications with other base stations 105 and may include a controller or scheduler for controlling communications with UE 115 in coordination with other base stations 105 . For example, inter-site communications manager 1445 may coordinate the scheduling of transmissions for UE 115 to implement various interference mitigation techniques such as beamforming or joint transmissions. In some examples, the inter-site communication manager 1445 may provide an X2 interface within the LTE/LTE-A wireless communication network technology to provide communication between the base stations 105 .

According to examples disclosed herein, communications manager 1420 may support wireless communications at a base station. For example, the communications manager 1420 may be configured or otherwise support means for sending control signaling to the UE that identifies the UE to be used for data while the UE is in an inactive or idle state. A first set of resources for transmission and a second set of resources for UCI transmission. Communications manager 1420 may be configured or otherwise support means for receiving data messages from the UE on at least a portion of the first set of resources when the UE is in one of an inactive state or an idle state. , and receiving the UCI message from the UE on the second resource set.

By including or configuring the communications manager 1420 in accordance with examples as described herein, the device 1405 can enable the UE 115 to send UCI when in an inactive state and/or idle state in the context of a CG-SDT procedure. Messaging, along with SDT, supports technologies that promote more efficient use of resources. In particular, by enabling the UE 115 to send UCI messages along with SDT when in an inactive or idle state, the techniques described herein may enable the UE 115 to establish a full wireless connection with the base station 105 (or without connecting to the base station 105 A small amount of control data is sent when a complete wireless connection is established, which can reduce the signaling management burden associated with establishing a wireless connection between the UE 115 and the network, and can reduce the latency associated with UCI messages.

In some examples, communications manager 1420 may be configured to use, or otherwise interact with, transceiver 1415 , one or more antennas 1425 , or any combination thereof. Coordinate to perform various operations (e.g., receive, monitor, send). Although communications manager 1420 is shown as a separate component, in some examples, one or more of the functions described with reference to communications manager 1420 may be supported or performed by processor 1440, memory 1430, code 1435, or any combination . For example, code 1435 may include instructions executable by processor 1440 to cause device 1405 to perform aspects of techniques for UCI transmission with small data transmission, as described herein, or processor 1440 and memory 1430 May additionally be configured to perform or support such operations.

15 illustrates a flowchart of a method 1500 for technology supporting UCI transmission along with small data transmission, according to aspects of the subject matter. The operations of method 1500 may be implemented by a UE or elements thereof as described herein. For example, the operations of method 1500 may be performed by UE 115 as described with reference to FIGS. 1-10. In some examples, a UE may execute a set of instructions to control functional units of the UE to perform the described functions. Additionally or alternatively, the UE may use special purpose hardware to perform aspects of the described functionality.

At 1505, the method may include receiving a control signaling from a base station identifying a first set of resources used by the UE for data transmission when the UE is in an inactive or idle state and a third set of resources used for UCI transmission. Two resource sets. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of operation 1505 may be performed by the control signal transfer reception manager 925 as described with reference to FIG. 9 .

At 1510, the method may include generating a UCI message based on the second set of resources when the UE is in one of an inactive state or an idle state. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of operation 1510 may be performed by UCI generation manager 930 as described with reference to FIG. 9 .

At 1515, the method may include sending a data message to the base station on at least a portion of the first set of resources and to the base station on the second set of resources when the UE is in one of an inactive state or an idle state. The station sends UCI messages. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of operation 1515 may be performed by uplink transmission manager 935 as described with reference to FIG. 9 .

16 illustrates a flowchart of a method 1600 for technologies that support UCI transmission along with small data transmission, according to aspects of the subject matter. The operations of method 1600 may be implemented by a UE or elements thereof as described herein. For example, the operations of method 1600 may be performed by UE 115 as described with reference to FIGS. 1-10. In some examples, a UE may execute a set of instructions to control functional units of the UE to perform the described functions. Additionally or alternatively, the UE may use special purpose hardware to perform aspects of the described functionality.

At 1605, the method may include receiving a random access message for a random access procedure from the base station, the random access message identifying a first set of resources used by the UE for data transmission when the UE is in an inactive state or an idle state. and a second set of resources for UCI transmission. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of operation 1605 may be performed by the control signal transfer reception manager 925 as described with reference to FIG. 9 .

At 1610, the method may include generating a UCI message based on the second set of resources when the UE is in one of an inactive state or an idle state. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of operation 1610 may be performed by UCI generation manager 930 as described with reference to FIG. 9 .

At 1615, the method may include sending a data message to the base station on at least a portion of the first set of resources and to the base station on the second set of resources when the UE is in one of an inactive state or an idle state. The station sends UCI messages. The operations of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of operation 1615 may be performed by uplink transmission manager 935 as described with reference to FIG. 9 .

FIG. 17 illustrates a flowchart of a method 1700 for technologies that support UCI transmission along with small data transmission, according to aspects of the subject matter. The operations of method 1700 may be implemented by a UE or elements thereof as described herein. For example, the operations of method 1700 may be performed by UE 115 as described with reference to FIGS. 1-10. In some examples, a UE may execute a set of instructions to control functional units of the UE to perform the described functions. Additionally or alternatively, the UE may use special purpose hardware to perform aspects of the described functionality.

At 1705, the method may include: receiving, from the base station, a message associated with releasing the UE from the active state to the inactive state or the idle state when the UE is in the active state, wherein the message identifies when the UE is in the inactive state or the idle state. The first resource set used by the UE for data transmission and the second resource set used for UCI transmission in the idle state. The operations of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of operation 1705 may be performed by control signaling reception manager 925 as described with reference to FIG. 9 .

At 1710, the method may include generating a UCI message based on the second set of resources when the UE is in one of an inactive state or an idle state. The operations of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of operation 1710 may be performed by UCI generation manager 930 as described with reference to FIG. 9 .

At 1720, the method may include sending a data message to the base station on at least a portion of the first set of resources and to the base station on the second set of resources when the UE is in one of an inactive state or an idle state. The station sends UCI messages. The operations of 1720 may be performed according to examples as disclosed herein. In some examples, aspects of operation 1720 may be performed by uplink transmission manager 935 as described with reference to FIG. 9 .

18 illustrates a flowchart of a method 1800 for technologies that support UCI transmission with small data transmission, according to aspects of the subject matter. The operations of method 1800 may be implemented by a UE or elements thereof as described herein. For example, the operations of method 1800 may be performed by UE 115 as described with reference to FIGS. 1-10. In some examples, a UE may execute a set of instructions to control functional units of the UE to perform the described functions. Additionally or alternatively, the UE may use special purpose hardware to perform aspects of the described functionality.

At 1805, the method may include receiving a control signaling from a base station identifying a first set of resources used by the UE for data transmission when the UE is in an inactive or idle state and a third set of resources used for UCI transmission. Two resource sets. The operations of 1805 may be performed according to examples as disclosed herein. In some examples, aspects of operation 1805 may be performed by the control signal transfer reception manager 925 as described with reference to FIG. 9 .

At 1810, the method may include generating a UCI message based on the second set of resources when the UE is in one of an inactive state or an idle state. The operations of 1810 may be performed according to examples as disclosed herein. In some examples, aspects of operation 1810 may be performed by UCI generation manager 930 as described with reference to FIG. 9 .

At 1815, the method may include sending the UCI message on the second resource set along with the random access message of the random access procedure when the UE is in one of an inactive state or an idle state. The operations of 1815 may be performed according to examples as disclosed herein. In some examples, aspects of operation 1815 may be performed by RACH transmission manager 945 as described with reference to FIG. 9 .

At 1820, the method may include sending a data message to the base station on at least a portion of the first resource set when the UE is in one of an inactive state or an idle state. The operations of 1820 may be performed according to examples as disclosed herein. In some examples, aspects of operation 1820 may be performed by uplink transmission manager 935 as described with reference to FIG. 9 .

19 illustrates a flowchart of a method 1900 for technology supporting UCI transmission with small data transmission, according to aspects of the subject matter. The operations of method 1900 may be implemented by a base station or components thereof as described herein. For example, the operations of method 1900 may be performed by base station 105 as described with reference to FIGS. 1-6 and 11-14. In some examples, a base station can execute a set of instructions to control functional units of the base station to perform the described functions. Additionally or alternatively, the base station may use special purpose hardware to perform various aspects of the functions described.

At 1905, the method may include sending a control signaling to the UE identifying a first set of resources used by the UE for data transmission when the UE is in an inactive or idle state and a second set of resources used for UCI transmission. Resource set. The operations of 1905 may be performed according to examples as disclosed herein. In some examples, aspects of operation 1905 may be performed by control signaling manager 1325 as described with reference to FIG. 13 .

At 1910, the method may include receiving a data message from the UE on at least a portion of a first set of resources and receiving a UCI from the UE on a second set of resources when the UE is in one of an inactive state or an idle state. message. The operations of 1910 may be performed according to examples as disclosed herein. In some examples, aspects of operation 1910 may be performed by uplink reception manager 1330 as described with reference to FIG. 13 .

The following provides an overview of various aspects of the case:

Aspect 1: A method for wireless communication at a UE, comprising: receiving a control signal transfer from a base station, the control signal transfer identifying a third channel used by the UE for data transmission when the UE is in an inactive state or an idle state. a set of resources and a second set of resources for UCI transmission; when the UE is in one of the inactive state or the idle state, generating a UCI message based at least in part on the second set of resources; and when the UE When in the one of the inactive state or the idle state, send a data message to the base station on at least a portion of the first resource set, and send the UCI message to the base station on the second resource set .

Aspect 2: The method according to aspect 1, wherein receiving the control signal transmission includes: receiving a random access message of a random access procedure from the base station, the random access message identifying the first resource set and the second resource set.

Aspect 3: The method according to any one of aspects 1 to 2, wherein receiving the control signal transmission includes: when the UE is in an active state, receiving from the base station and releasing the UE from the active state. A message associated with the inactive state or the idle state, wherein the message identifies the first resource set and the second resource set.

Aspect 4: The method according to any one of aspects 1 to 3, wherein sending the UCI message includes: sending the UCI message on the second resource set together with a random access message of a random access procedure. .

Aspect 5: The method according to aspect 4, wherein the random access procedure includes a four-step random access procedure, the method further includes: based at least in part on identifying that the TA for the UE is valid, matching the random access procedure with the random access procedure. The UCI message is sent together with the access message.

Aspect 6: The method according to any one of aspects 4 to 5, wherein the random access procedure includes a two-step random access procedure, the method further includes: after identifying that the TA for the UE is invalid After that, the UCI message is sent together with the random access message.

Aspect 7: The method of any one of aspects 1 to 6, wherein receiving the control signal transmission identifying the first set of resources for the data transmission includes: when the UE is in an active state Receiving the control signal transmission indicating a plurality of transmission opportunities for the data transmission, the plurality of transmission opportunities including the first resource set, wherein the data message and the UCI message are in the plurality of transmission opportunities Sent within the transmission opportunity.

Aspect 8: According to the method of aspect 7, sending the data message and the UCI message includes: multiplexing the data message and the UCI message within the transmission opportunity.

Aspect 9: The method of aspects 7 to 8, wherein sending the data message and the UCI message includes: based at least in part on generating the UCI message to be sent in a first transmission opportunity of the plurality of transmission opportunities. Avoiding sending the data message during the first transmission opportunity; sending the UCI message during the first transmission opportunity based at least in part on avoiding sending the data message; and based at least in part on sending the UCI message during the first transmission opportunity. The UCI message is used to send the data message in the second transmission opportunity among the plurality of transmission opportunities.

Aspect 10: The method according to any one of aspects 1 to 9, further comprising: receiving, through the control signal transmission, for the UE to multiplex the UCI and the data message in the second resource set. an indication that the second resource set is included in the first resource set, wherein sending the data message and the UCI message is based at least in part on the indication.

Aspect 11: The method according to any one of aspects 1 to 10, wherein the second resource set includes a common uplink control resource set, a dedicated uplink control resource set, or any combination thereof, and the The first resource set includes a set of uplink shared resources.

Aspect 12: The method of any one of aspects 1 to 11, further comprising: sending the UCI message based at least in part on identifying that the TA for the UE is valid.

Aspect 13: The method according to aspect 12, wherein identifying that the TA for the UE is valid includes: identifying that the first TA for the UCI message is valid and the second TA for the data message is valid. The TA is valid, a third TA is valid for both the UCI message and the data message, or any combination thereof.

Aspect 14: The method according to any one of Aspects 1 to 13, further comprising: receiving, via the control signaling, an indication of suspension of TA authentication at the UE, wherein sending the UCI message is at least Partly in response to this suspension of TA verification.

Aspect 15: The method according to any one of Aspects 1 to 14, wherein the UCI message includes HARQ feedback in response to: contention resolution message, downlink control plane message, downlink usage or plane message, RRC release message, or any combination thereof.

Aspect 16: The method according to any one of aspects 1 to 15, wherein the UCI message includes: a first CSI report smaller than a second CSI report for the active state, a beam failure report, a BWP index, An override enhancement request, a request to terminate the set of data messages that includes the data message, or any combination thereof.

Aspect 17: The method according to any one of Aspects 1 to 16, further comprising: receiving a control message from the base station, the control message indicating one or more parameters associated with the UCI message, the or multiple parameters including resource index, transmit beam index, repetition number, frequency hopping scheme, OCC, or any combination thereof, wherein the control message includes downlink control information message, media access control-control element message, RRC message , system information messages, or any combination thereof.

Aspect 18: A method for wireless communications at a base station, comprising: sending a control signal transfer to a UE, the control signal transfer identifying a third channel used by the UE for data transmission when the UE is in an inactive or idle state. a set of resources and a second set of resources for UCI transmission; and receiving data messages from the UE on at least a portion of the first set of resources when the UE is in one of the inactive state or the idle state, and receiving the UCI message from the UE on the second resource set.

Aspect 19: The method of aspect 18, wherein sending the control signal transmission includes: sending a random access message of a random access procedure, the random access message identifying the first resource set and the second resource set.

Aspect 20: The method according to any one of aspects 18 to 19, wherein sending the control signal transfer includes: when the UE is in an active state, sending and releasing the UE from the active state to A message associated with the inactive state or the idle state, wherein the message identifies the first resource set and the second resource set.

Aspect 21: The method according to any one of aspects 18 to 20, wherein receiving the UCI message includes: receiving the UCI message on the second resource set together with a random access message of a random access procedure .

Aspect 22: The method according to any one of aspects 18 to 21, further comprising: sending, through the control signal transmission, for the UE to multiplex the UCI and the data message in the second resource set. an indication that the second resource set is included in the first resource set, wherein receiving the data message and the UCI message is at least partially in response to sending the indication.

Aspect 23: The method of any one of aspects 18 to 22, wherein the second resource set includes a common uplink control resource set, a dedicated uplink control resource set, or any combination thereof, and the The first resource set includes a set of uplink shared resources.

Aspect 24: The method of any one of Aspects 18 to 23, further comprising: sending, via the control signaling, an indication of suspension of TA authentication at the UE, wherein receiving the UCI message is at least Partly in response to this suspension of TA verification.

Aspect 25: The method of any one of Aspects 18 to 24, wherein the UCI message includes HARQ feedback in response to: contention resolution message, downlink control plane message, downlink usage or plane message, RRC release message, or any combination thereof.

Aspect 26: The method according to any one of aspects 18 to 25, wherein the UCI message includes: a first CSI report smaller than a second CSI report for the active state, a beam failure report, a BWP index, An override enhancement request, a request to terminate the set of data messages that includes the data message, or any combination thereof.

Aspect 27: The method according to any one of aspects 18 to 26, further comprising: sending a control message to the UE, the control message indicating one or more parameters associated with the UCI message, the one or The plurality of parameters include resource index, transmit beam index, repetition number, frequency hopping scheme, OCC, or any combination thereof, wherein the control message includes downlink control information message, media access control-control element message, RRC message, System information messages, or any combination thereof.

Aspect 28: A device including a processor, a memory coupled to the processor, and instructions stored in the memory, the instructions executable by the processor to cause the device to perform aspects 1 to Any of the methods described in 17.

Aspect 29: An apparatus comprising at least one means for performing the method of any one of aspects 1 to 17.

Aspect 30: A non-transitory computer-readable medium storing code including instructions executable by a processor to perform the method of any one of Aspects 1 to 17.

Aspect 31: A device for wireless communication at a base station, including a processor, a memory coupled to the processor, and instructions stored in the memory, the instructions being executable by the processor To cause the device to perform the method described in any one of aspects 18 to 27.

Aspect 32: An apparatus for wireless communication at a base station, comprising at least one component for performing the method of any one of aspects 18 to 27.

Aspect 33: A non-transitory computer-readable medium storing code for wireless communications at a base station, the code including code executable by a processor to perform the method of any one of Aspects 18 to 27 instructions.

It should be noted that the methods described herein describe possible implementations, and that operations and steps may be rearranged or modified, and other implementations are possible. Furthermore, method aspects from two or more of these methods can be combined.

Although various aspects of LTE, LTE-A, LTE-A Pro or NR systems may be described for purposes of example, and LTE, LTE-A, LTE-A Pro or NR may be used in much of the description term, but the techniques described in this article may apply beyond LTE, LTE-A, LTE-A Pro or NR networks. For example, the described techniques may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash- OFDM, and other systems and radio technologies not explicitly mentioned in this article.

The information and signals described in this article may be represented using any of a variety of different technologies and methods. For example, data, instructions, commands, information, signals, bits, symbols and chips that may be mentioned throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

Combinations may be implemented or performed using a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, individual gate or transistor logic, individual hardware elements, or any combination thereof designed to perform the functions described herein. The disclosure herein describes various illustrative blocks and components. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller or state machine. A processor may also be implemented as a combination of computing devices (eg, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented by software executed by a processor, the functionality may be stored on or sent over a computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope of this case and the accompanying claims. For example, due to the nature of software, the functionality described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or a combination of any of these. Features that implement functionality may also be physically located at various locations, including being distributed such that portions of the functionality are implemented at different physical locations.

Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. Non-transitory storage media can be any available media that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electronically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM, or other optical disk storage , disk storage or other magnetic storage device, or any other non-transitory device that can be used to carry or store the desired program code units in the form of instructions or data structures and that can be accessed by a general or special purpose computer, or a general or special purpose processor. Sexual media. Also, any connection is properly termed a computer-readable medium. For example, if the software is sent from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), or wireless technologies such as infrared, radio, and microwave Cables, fiber optic cables, twisted pairs, DSL or wireless technologies such as infrared, radio and microwave are included in the definition of computer readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs. Disks usually reproduce data magnetically, while optical discs use lasers to reproduce data. Reproduce data optically. Combinations of the above are also included within the scope of computer-readable media.

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

The term "decision" or "judgment" covers a wide variety of actions, and thus, "decision" may include calculation, operation, processing, deduction, research, query (e.g., via a lookup table, database, or other data structure), assertion, etc. . In addition, "decision" can also include receiving (for example, receiving information), accessing (for example, accessing data in memory), etc. In addition, "decision" may also include parsing, selecting, selecting, creating, and other such similar actions.

In the drawings, similar elements or features may have the same reference symbols. Additionally, various components of the same type may be distinguished by following the component symbol with a dash and a second label used to distinguish between similar components. If only a first reference number is used in the specification, the description applies to any one of the similar elements having the same first reference number, regardless of the second reference number or other subsequent reference numbers.

The descriptions set forth in the accompanying drawings describe example configurations and are not intended to represent all examples that may be implemented or are within the scope of the claims. As used herein, the term "example" means "serving as an example, instance, or illustration," rather than "preferable" or "advantage over other examples." The detailed description includes specific details for the purpose of providing an understanding of the described technology. However, these techniques can be implemented without these specific details. In some instances, well-known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

The description in this article is provided to enable those who are generally familiar with this technology to implement or use the content of this article. Various modifications to the teachings will be apparent to those skilled in the art, and the overall principles defined herein may be applied to other variations without departing from the scope of the teachings. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

100: Wireless communication system 105: Base station 105-a: Base station 105-b: Base station 105-c: Base station 105-d: Base station 110: Control signal transmission 115: UE 115-a: UE 115-b: UE 115-c: UE 115-d: UE 120: Backhaul link 125: Communication link 130: Core network 135: Device-to-device (D2D) communication link 140: Access network entity 145: Other access networks Channel transmission entity 150: Method 200: Wireless communication system 205: Communication link 210: Control signal transmission 215: SDT 215-a: SDT 215-b: SDT 220: UCI message 220-a: UCI message 220-b: UCI message 225-a: First SDT configuration 225-b: Second SDT configuration 300: Resource configuration 305-a: First SDT configuration 305-b: Second SDT configuration 310-a: Downlink message 310-b: Downlink Route message 315: UCI message 315-a: First UCI message 315-b: Second UCI message 315-c: UCI message 320: SDT 320-a: SDT 320-b: SDT 325: PUSCH resource set 330: Demodulation Reference signal (DMRS) 400: Program flow 405: Step 410: Step 415: Step 420: Step 425: Step 430: Step 435: Step 500: Program flow 505: Step 510: Step 515: Step 520: Step 525: Step 530 : Step 535: Step 540: Step 545: Step 600: Program flow 605: Step 610: Step 615: Step 620: Step 625: Step 630: Step 700: Block diagram 705: Device 710: Receiver 715: Transmitter 720: Communication manager 800: block diagram 805: device 810: receiver 815: transmitter 820: communication manager 825: control signal delivery reception manager 830: UCI generation manager 835: uplink transmission manager 900: block diagram 920 :Communication Manager 925:Control Signal Delivery Receive Manager 930:UCI Generation Manager 935:Uplink Transmit Manager 940:RACH Receive Manager 945:RACH Transmit Manager 950:TA Manager 1000:System 1005:Device 1010 :Input/Output (I/O) Controller 1015:Transceiver 1020:Communication Manager 1025:Antenna 1030:Memory 1035:Code 1040:Processor 1045:Bus 1100:Block Diagram 1105:Device 1110:Receiver 1115 :Transmitter 1120:Communication Manager 1200:Block Diagram 1205:Device 1210:Receiver 1215:Transmitter 1220:Communication Manager 1225:Control Signaling Transmit Manager 1230:Uplink Receive Manager 1300:Block Diagram 1320: Communication Manager 1325: Control signal delivery Transmit Manager 1330: Uplink Receive Manager 1335: RACH Transmit Manager 1340: RACH Receive Manager 1400: System 1405: Device 1410: Network Communications Manager 1415: Transceiver 1420: Communications Manager 1425: Antenna 1430: Memory 1435: Code 1440: Processor 1445: Intersite Communications Manager 1500: Method 1505: Operation 1510: Operation 1515: Operation 1600: Method 1605: Operation 1610: Operation 1615: Operation 1700: Method 1705: Operation 1710: Operation 1800: Method 1805: Operation 1810: Operation 1815: Operation 1820: Operation 1900: Method 1905: Operation 1910: Operation F _SDT : Frequency resource set T _SDT : Time resource set

Figure 1 illustrates an example of a wireless communication system that supports technology for uplink control information (UCI) transmission together with small data transmission, according to aspects of this case.

Figure 2 illustrates an example of a wireless communication system supporting technology for UCI transmission together with small data transmission, according to various aspects of the content of this case.

Figure 3 illustrates an example of resource configuration supporting technology for UCI transmission together with small data transmission, according to various aspects of the content of this case.

Figure 4 illustrates an example of a program flow that supports technology for UCI transmission together with small data transmission, according to aspects of the content of this case.

Figure 5 illustrates an example of a program flow that supports technology for UCI transmission together with small data transmission, according to aspects of the content of this case.

Figure 6 illustrates an example of a program flow that supports technology for UCI transmission together with small data transmission, according to aspects of the content of this case.

7 and 8 illustrate block diagrams of equipment supporting technology for UCI transmission with small data transmission, according to aspects of the subject matter.

Figure 9 illustrates a block diagram of a communications manager supporting technology for UCI transport along with small data transport, according to aspects of the subject matter.

10 illustrates a diagram of a system including a device supporting technology for UCI transmission with small data transmission, in accordance with aspects of the subject matter.

11 and 12 illustrate block diagrams of equipment supporting technology for UCI transmission with small data transmission, according to aspects of the subject matter.

Figure 13 illustrates a block diagram of a communications manager supporting technology for UCI transmission with small data transmission, according to aspects of the subject matter.

14 illustrates a diagram of a system including a device supporting technology for UCI transmission with small data transmission, in accordance with aspects of the subject matter.

15 to 19 illustrate a flowchart of a method for supporting UCI transmission together with small data transmission according to various aspects of the present case.

Domestic storage information (please note in order of storage institution, date and number) without Overseas storage information (please note in order of storage country, institution, date, and number) without

105-a: Base station

115-a:UE

205: Communication link

210:Control signal transmission

215:SDT

215-a:SDT

215-b:SDT

220:UCI message

220-a:UCI information

220-b:UCI message

225-a: First SDT configuration

225-b: Second SDT configuration

Claims (30)

A method for wireless communication at a user equipment (UE), comprising: Receive a control signal transfer from a base station that identifies a first set of resources used by the UE for data transmission when the UE is in an inactive state or an idle state and a first set of resources used for uplink control information transmission. a second resource set; Generating an uplink control information message based at least in part on the second set of resources when the UE is in one of the inactive state or the idle state; and When the UE is in the one of the inactive state or the idle state, send a data message to the base station on at least a portion of the first resource set, and send a data message to the base station on the second resource set. The uplink control information message. According to the method of claim 1, wherein receiving the control signal transmission includes: A random access message of a random access procedure is received from the base station, and the random access message identifies the first resource set and the second resource set. According to the method of claim 1, wherein receiving the control signal transmission includes: When the UE is in an active state, a message associated with releasing the UE from the active state to the inactive state or the idle state is received from the base station, wherein the message identifies the first resource set and the third resource set. Two resource sets. According to the method of claim 1, sending the uplink control information message includes: The uplink control information message is sent on the second resource set together with a random access message of a random access procedure. According to the method of claim 4, wherein the random access procedure includes a four-step random access procedure, the method further includes: The uplink control information message is sent with the random access message based at least in part on identifying that a timing advance for the UE is valid. According to the method of claim 4, wherein the random access procedure includes one or two steps of random access procedures, the method further includes: After identifying that a timing advance for the UE is invalid, the uplink control information message is sent together with the random access message. The method of claim 1, wherein receiving the control signal transmission identifying the first resource set for the data transmission includes: receiving the control signal transmission when the UE is in an active state, the control signal transmission indicating A plurality of transmission opportunities for the data transmission, the plurality of transmission opportunities including the first resource set, wherein the data message and the uplink control information message are sent within a transmission opportunity of the plurality of transmission opportunities of. According to the method of claim 7, sending the data message and the uplink control information message includes: Within the transmission opportunity, the data message and the uplink control information message are multiplexed. According to the method of claim 7, sending the data message and the uplink control information message includes: Avoiding sending the data message in a first transmission opportunity of the plurality of transmission opportunities is based at least in part on generating the uplink control information message to be sent in the first transmission opportunity; sending the uplink control information message during the first transmission opportunity based at least in part on avoiding sending the data message; and The data message is sent in a second transmission opportunity of the plurality of transmission opportunities based at least in part on sending the uplink control information message in the first transmission opportunity. According to the method of claim 1, it also includes: Through the control signal transmission, an instruction is received for the UE to multiplex the uplink control information and the data message in the second resource set, the second resource set being included in the first resource set, wherein Sending the data message and the uplink control information message is based at least in part on the indication. The method of claim 1, wherein the second resource set includes a common uplink control resource set, a dedicated uplink control resource set, or any combination thereof, and wherein the first resource set includes an uplink shared Resource collection. According to the method of claim 1, it also includes: The uplink control information message is sent based at least in part on identifying that a timing advance for the UE is valid. The method according to claim 12, wherein identifying that the timing advance for the UE is valid includes: Identify: a first timing advance for the uplink control information message is valid, a second timing advance for the data message is valid, for the uplink control information message and the data A third timing advance of the message is valid, or any combination thereof. According to the method of claim 1, it also includes: An indication of a suspension of timing advance verification at the UE is received via the control signaling, wherein sending the uplink control information message is at least partially in response to the suspension of timing advance verification. The method of claim 1, wherein the uplink control information message includes a HARQ feedback in response to: a contention resolution message, a downlink control plane message, a downlink user A plane message, a radio resource control release message, or any combination thereof. The method according to claim 1, wherein the uplink control information message includes: a first channel status information report that is smaller than a second channel status information report for an active state, a beam failure report, and a bandwidth portion An index, a coverage enhancement request, a request to terminate a set of data messages that includes the data message, or any combination thereof. According to the method of claim 1, it also includes: A control message is received from the base station. The control message indicates one or more parameters associated with the uplink control information message. The one or more parameters include a resource index, a transmit beam index, a repetition number, A frequency hopping scheme, an orthogonal coverage code, or any combination thereof, wherein the control message includes a downlink control information message, a media access control-control element message, a radio resource control message, and a system information message , or any combination thereof. A method for wireless communication at a base station, including: Send a control signaling to a user equipment (UE), the control signaling identifying a first set of resources used by the UE for data transmission when the UE is in an inactive state or an idle state and for uplink a second set of resources that control the transmission of information; and receiving data messages from the UE on at least a portion of the first set of resources and receiving uplinks from the UE on the second set of resources when the UE is in one of the inactive state or the idle state Control information messages. According to the method of claim 18, sending the control signal transmission includes: A random access message of a random access procedure is sent, the random access message identifies the first resource set and the second resource set. According to the method of claim 18, sending the control signal transmission includes: When the UE is in an active state, sending a message associated with releasing the UE from the active state to the inactive state or the idle state, wherein the message identifies the first resource set and the second resource set. Resource set. According to the method of claim 18, receiving the uplink control information message includes: The uplink control information message is received on the second resource set together with a random access message of a random access procedure. The method of claim 18 further includes: sending, via the control signaling, an instruction for the UE to multiplex the uplink control information and the data message within the second resource set, the second resource set being included in the first resource set, wherein receiving the data message and the uplink control information message is at least partially in response to sending the indication. The method of claim 18, wherein the second resource set includes a common uplink control resource set, a dedicated uplink control resource set, or any combination thereof, and wherein the first resource set includes an uplink shared Resource collection. The method of claim 18 further includes: An indication of a pause in timing advance verification at the UE is sent via the control signaling, wherein receipt of the uplink control information message is at least in part responsive to the pause in timing advance verification. The method of claim 18, wherein the uplink control information message includes a HARQ feedback in response to: a contention resolution message, a downlink control plane message, a downlink user plane message message, a radio resource control release message, or any combination thereof. The method of claim 18, wherein the uplink control information message includes: a first channel status information report that is smaller than a second channel status information report for an active state, a beam failure report, and a bandwidth portion An index, a coverage enhancement request, a request to terminate a set of data messages that includes the data message, or any combination thereof. A device including: a processor; memory coupled to the processor; and Instructions stored in the memory and executable by the processor to cause the device to: Receive a control signal transfer from a base station that identifies a first set of resources used by the UE for data transmission when the UE is in an inactive state or an idle state and a first set of resources used for uplink control information transmission. a second resource set; Generating an uplink control information message based at least in part on the second set of resources when the UE is in one of the inactive state or the idle state; and When the UE is in the one of the inactive state or the idle state, send a data message to the base station on at least a portion of the first resource set, and send a data message to the base station on the second resource set. The uplink control information message. A device according to claim 27, wherein the instructions are further executable by the processor to receive the control signal transfer by being executable by the processor to cause the device to perform the following operations: A random access message of a random access procedure is received from the base station, and the random access message identifies the first resource set and the second resource set. A device according to claim 27, wherein the instructions are further executable by the processor to receive the control signal transfer by being executable by the processor to cause the device to perform the following operations: When the UE is in an active state, a message associated with releasing the UE from the active state to the inactive state or the idle state is received from the base station, wherein the message identifies the first resource set and the second resource set. Resource set. A device for wireless communication at a base station, including: a processor; memory coupled to the processor; and Instructions stored in the memory and executable by the processor to cause the device to: Send a control signaling to a user equipment (UE), the control signaling identifying a first set of resources used for data transmission by the UE when the UE is in an inactive state or an idle state and for uplink a second set of resources for channel control information transmission; and When the UE is in one of the inactive state or the idle state, receive a data message from the UE on at least a portion of the first set of resources, and receive an uplink message from the UE on the second set of resources. Link control information message.