Feedback messaging of cell handover commands

Abstract

Methods, systems, and devices for wireless communication are described. A UE may monitor one or more resources of a channel associated with a first cell of a network entity for a medium access control-control element (MAC-CE) message associated with a handover procedure of the UE. The UE may receive the MAC-CE message, which may include a cell handover command that indicates a handover from the first cell to a second cell as part of the handover procedure of the UE. The UE may transmit a feedback message for the MAC-CE, the feedback message indicating a decoding result of the MAC-CE message. Additionally or alternatively, the UE may initiate a timer associated with the handover procedure from the first cell to the second cell according to the cell handover command. Thus, the UE may communicate one or more messages associated with the handover procedure based on the status of the timer.

Description

Technical Field

[0001] The following relates to wireless communications, including feedback messaging for cell handover commands. Background Art

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, and more. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple-access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform-spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple-access communication system may include one or more base stations, each of which supports wireless communication for communication devices, which may be referred to as user equipment (UE). Summary of the Invention

[0003] The described techniques relate to improved methods, systems, devices, and apparatuses for supporting feedback messaging for cell handover commands. For example, the described techniques provide reduced latency associated with handover procedures by supporting cell handover commands included in Layer 2 (L2) signaling. For example, a user equipment (UE) may monitor the time-frequency resources of a channel associated with a current source cell (serving cell, primary cell, a cell currently supporting communications for the UE, etc.) and may receive a Medium Access Control-Control Element (MAC-CE) message (e.g., via L2 signaling from the serving cell) including a cell handover command. The cell handover command may instruct the UE to handover from the current source cell to a target cell as part of a handover procedure (e.g., may instruct the UE to handover from one cell to another). In response, the UE may send a feedback message to a network entity indicating an acknowledgment (ACK) or negative ACK (NACK) of the MAC-CE message used to perform the handover procedure associated with the cell handover command. In some examples, the UE may send the feedback message to the current source cell. Additionally or alternatively, the UE may send the feedback message to the target cell.

[0004] In some cases, the UE may determine whether the handover to the target cell is successful based on the status of a timer. For example, the UE may initiate the timer in response to receiving a MAC-CE message or in response to sending a feedback message. In some examples, the UE may stop the timer in response to receiving a first downlink message from the target cell or in response to sending an acknowledgment message of the first downlink message to the network entity via the target cell. If the timer expires, the UE may switch back to the source cell and send a handover failure message (e.g., via or to the source cell). BRIEF DESCRIPTION OF THE DRAWINGS

[0005] Figure 1 An example of a wireless communication system supporting feedback messaging for cell handover commands according to one or more aspects of the present disclosure is illustrated.

[0006] Figure 2 An example of a network architecture supporting feedback messaging for cell handover commands according to one or more aspects of the present disclosure is illustrated.

[0007] Figure 3 An example of a wireless communication system supporting feedback messaging for cell handover commands according to one or more aspects of the present disclosure is illustrated.

[0008] Figure 4 An example of a process flow for supporting feedback messaging for a cell handover command in accordance with one or more aspects of the present disclosure is illustrated.

[0009] Figure 5 An example of a process flow for supporting feedback messaging for a cell handover command in accordance with one or more aspects of the present disclosure is illustrated.

[0010] Figure 6 and Figure 7 A block diagram illustrating a device supporting feedback messaging for a cell handover command according to one or more aspects of the present disclosure is illustrated.

[0011] Figure 8 A block diagram illustrating a communications manager supporting feedback messaging for cell handover commands in accordance with one or more aspects of the present disclosure is illustrated.

[0012] Figure 9 A diagram illustrating a system including a device supporting feedback messaging for a cell handover command in accordance with one or more aspects of the present disclosure is illustrated.

[0013] Figure 10 and Figure 11 A block diagram illustrating a device supporting feedback messaging for a cell handover command according to one or more aspects of the present disclosure is illustrated.

[0014] Figure 12A block diagram illustrating a communications manager supporting feedback messaging for cell handover commands in accordance with one or more aspects of the present disclosure is illustrated.

[0015] Figure 13 A diagram illustrating a system including a device supporting feedback messaging for a cell handover command in accordance with one or more aspects of the present disclosure is illustrated.

[0016] Figures 14 to 18 A flow chart illustrating a method of supporting feedback messaging for a cell handover command according to one or more aspects of the present disclosure is illustrated. DETAILED DESCRIPTION

[0017] In some examples of wireless communications, a network entity may support communications via multiple cells. Of these multiple cells, one or more activated cells may be used for data and control communications (e.g., to support uplink and downlink communications) with a user equipment (UE). A cell may refer to a logical communication entity used for communications between a UE and a network entity. In some examples, a cell may also refer to a geographic area or portion of a geographic area in which the logical communication entity operates. At least one of the cells associated with the communication may be configured as a primary cell (PCell) (e.g., a source cell). The PCell may refer to the cell with which the UE is currently communicating and is the cell with which the UE conducts the majority of its communications with the network entity. In some cases (e.g., if the UE is mobile, if network conditions change), communication quality may be improved by switching the source cell to a second cell (e.g., a target cell). Such techniques may be referred to as cell mobility, cell mobility management, or inter-cell mobility, among others. According to some techniques, layer 3 (L3) signaling may be used to change the source cell to another cell, however, L3 signaling may be associated with higher latency or higher overhead compared to other signaling (eg, layer 1 (L1) or layer 2 (L2) signaling).

[0018] The network can reduce the latency associated with the handover process by supporting L2 signaling for cell switching, where an L2 message (e.g., a Medium Access Control-Control Element (MAC-CE) message) includes a cell handover command. For example, a UE may be configured to monitor one or more resources of a channel associated with a source cell and may receive a MAC-CE message (e.g., via L2 signaling) including a cell handover command instructing the UE to switch communications from a current source cell to a target cell. In response, the UE may send a feedback message to a network entity, indicating an acknowledgment (ACK) or a negative ACK (NACK) of the MAC-CE message used to perform the handover process associated with the cell handover command. In some examples, the UE may send the feedback message to the current source cell. Additionally or alternatively, the UE may send the feedback message to the target cell.

[0019] In some cases, the UE may determine whether the handover to the target cell is successful based on the status of a timer, which may be configured for the UE or pre-configured at the UE. In some examples, the UE may initiate the timer in response to receiving a MAC-CE message or in response to sending a feedback message. The UE may stop the timer in response to receiving a first downlink message from the target cell or in response to sending an acknowledgment message of the first downlink message to the network entity via the target cell. If the timer expires, the UE may switch back to the source cell and send a handover failure message (e.g., via the source cell).

[0020] Various aspects of the present disclosure are first described in the context of a wireless communication system. Various aspects of the present disclosure are further described in the context of process flow diagrams. Various aspects of the present disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flow diagrams related to feedback messaging for cell handover commands.

[0021] Figure 1 An example of a wireless communication system 100 that supports feedback messaging for cell handover commands according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 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, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating according to other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0022] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100 and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other nomenclature. In some examples, the network entities 105 and the UEs 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entities 105 may support a coverage area 110 (e.g., a geographic coverage area) within which the UEs 115 and the network entities 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area within which the network entities 105 and the UEs 115 may support signal communication based on one or more radio access technologies (RATs).

[0023] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile or both stationary and mobile at different times. The UEs 115 may be devices that take different forms or have different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. The UEs 115 described herein may be capable of supporting communications with various types of devices, such as Figure 1 Other UEs 115 or network entities 105 are shown.

[0024] As described herein, a node of wireless communication system 100 (which may be referred to as a network node or wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be UE 115. As another example, the node may be network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from the second node.

[0025] In some examples, network entities 105 can communicate with core network 130, with each other, or both. For example, network entities 105 can communicate with core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entities 105 can communicate with each other via backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols), either directly (e.g., between network entities 105) or indirectly (e.g., via core network 130). In some examples, network entities 105 can communicate with each other via midhaul communication links 162 (e.g., according to a midhaul interface protocol) or fronthaul communication links 168 (e.g., according to a fronthaul interface protocol), or any combination thereof. Backhaul communication links 120, midhaul communication links 162, or fronthaul communication links 168 can be or include one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

[0026] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next-generation Node B, or a gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next-generation eNB (ng-eNB), a Home Node B, a Home evolved Node B, or other suitable terminology). In some examples, the network entity 105 (e.g., the base station 140) may be implemented in a converged (e.g., monolithic, stand-alone) base station architecture that may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as the base station 140).

[0027] In some examples, the network entity 105 can be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that can be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 can include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, smart radio head, remote radio head (RRH), remote radio unit (RRU), or transmit receive point (TRP). One or more components of the network entity 105 in the disaggregated RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the disaggregated RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0028] The functional split between CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a functional split of the protocol stack can be employed between CU 160 and DU 165, such that CU 160 can support one or more layers of the protocol stack and DU 165 can support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionality and signaling (e.g., Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as Layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via the one or more RUs 170). In some cases, the functional split between the CU 160 and the DU 165 or between the DU 165 and the RU 170 may be within the protocol layer (e.g., some functions of a protocol layer may be performed by one of the CU 160, DU 165, or RU 170, while other functions of the protocol layer may be performed by a different one of the CU 160, DU 165, or RU 170). The CU 160 may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and the DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., an open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented according to interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 communicating via such communication links.

[0029] In some wireless communication systems (e.g., wireless communication system 100), the infrastructure and spectrum resources used for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as a donor entity or IAB donor. One or more DUs 165 or one or more RUs 170 may be partially controlled by one or more CUs 160 associated with a donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication link 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by the coupled IAB donor's DU 165. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the disaggregated RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0030] For example, an access network (AN) or RAN may include communications between an access node (e.g., an IAB donor), IAB node 104, and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). In other words, the IAB donor may refer to a RAN node with a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170). In this case, the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and IAB node 104 may communicate via the F1 interface according to a protocol that defines signaling messages (e.g., the F1 AP protocol). Additionally or alternatively, CU 160 may communicate with the core network via an interface (which may be an example of a portion of a backhaul link) and may communicate with other CUs 160 (e.g., CUs 160 associated with alternative IAB donors) via an Xn-C interface (which may be an example of a portion of a backhaul link).

[0031] An IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, wireless self-backhaul capabilities, etc.). A DU 165 may act as a distributed scheduling node toward child nodes associated with the IAB node 104, and an IAB-MT may act as a scheduled node toward a parent node associated with the IAB node 104. In other words, an IAB donor may be referred to as a parent node that communicates with one or more child nodes (e.g., the IAB donor may relay transmissions for UEs via one or more other IAB nodes 104). Additionally or alternatively, depending on the relay chain or configuration of the AN, an IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104. Thus, the IAB-MT entity of the IAB node 104 may provide a Uu interface for the child IAB node 104 to receive signaling from the parent IAB node 104 , and a DU interface (eg, DU 165 ) may provide a Uu interface for the parent IAB node 104 to signal to the child IAB node 104 or the UE 115 .

[0032] For example, IAB node 104 may be referred to as a parent node supporting communications for child IAB nodes, or as a child IAB node associated with an IAB donor, or both. The IAB donor may include a CU 160 having a wired or wireless connection to the core network 130 (e.g., backhaul communication link 120) and may serve as a parent node for IAB node 104. For example, the DU 165 of the IAB donor may relay transmissions to UE 115 via IAB node 104, or may directly signal transmissions to UE 115, or both. The CU 160 of the IAB donor may signal the establishment of a communication link to IAB node 104 via the F1 interface, and IAB node 104 may schedule transmissions (e.g., transmissions relayed from the IAB donor to UE 115) via the DU 165. In other words, data may be relayed to and from IAB node 104 via signaling via the NR Uu interface of the MT to IAB node 104. Communications with the IAB node 104 may be scheduled by the DU 165 of the IAB donor, and communications with the IAB node 104 may be scheduled by the DU 165 of the IAB node 104 .

[0033] Where the techniques described herein are applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support feedback messaging for cell handover commands as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the disaggregated RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

[0034] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects, such as appliances or vehicles, meters, etc.

[0035] The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 shown.

[0036] UE 115 and network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" may refer to a set of RF spectrum resources with a physical layer structure defined to support communication link 125. For example, a carrier used for communication link 125 may comprise a portion of an RF spectrum band (e.g., a bandwidth part (BWP)) operating according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling to coordinate carrier operation, user data, or other signaling. The wireless communication system 100 may support communications with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between those devices and any portion (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send," "receive," or "communicate" when referring to the network entity 105 may refer to any portion of the network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0037] The signal waveform transmitted via a carrier wave may include multiple subcarriers (e.g., using a multicarrier modulation (MCM) technique such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In systems employing MCM techniques, a resource element may refer to the resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in a transmission duration) and a relatively high-order modulation scheme may correspond to relatively high-speed communication. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communications with UE 115.

[0038] The time interval for the network entity 105 or the UE 115 may be expressed as a multiple of a basic time unit, which may be, for example, a sampling period. Seconds, for this can indicate the supported subcarrier spacing, and The supported discrete Fourier transform (DFT) size may be indicated. Time intervals of communication resources may be organized according to radio frames, each of which has a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0039] Each frame may include a plurality of 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 (e.g., in the time domain) into subframes, and each subframe may be further divided into a certain number of 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 may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended to the front of each symbol period). In some wireless communication systems 100, the time slot may be further divided into a plurality of mini-slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0040] A subframe, slot, mini-slot, or symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a Transmit Time Interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).

[0041] Physical channels may be multiplexed using carriers for communication according to various techniques. Physical control channels and physical data channels may be multiplexed for signaling via downlink carriers, for example, using one or more of time division multiplexing (TDM), frequency division multiplexing (FDM), or hybrid TDM-FDM techniques. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across the system bandwidth of a carrier or a subset of that bandwidth. One or more control regions (e.g., CORESETs) may be configured for a group of UEs 115. For example, one or more of UEs 115 may monitor or search the control region for control information according to one or more search space sets, where each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of a control channel candidate may refer to the number of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to multiple UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0042] Network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with network entity 105 (e.g., using a carrier) and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other identifier) used to distinguish between adjacent cells. In some examples, a cell may also refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) within which the logical communication entity operates. Depending on various factors, such as the capabilities of network entity 105, such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or include a building, a subset of buildings, or an external space between or overlapping coverage areas 110.

[0043] A macro cell typically covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to UEs 115 that have a service subscription with a network provider that supports the macro cell. Compared to a macro cell, a small cell may be associated with a lower-power network entity 105 (e.g., a lower-power base station 140) and may operate using the same or different frequency bands (e.g., licensed or unlicensed) as the macro cell. A small cell may provide unrestricted access to UEs 115 that have a service subscription with the network provider, or may provide restricted access to UEs 115 associated with the small cell (e.g., UEs 115 in a closed subscriber group (CSG) or UEs 115 associated with users in a home or office). A network entity 105 may support one or more cells and may also support communication via one or more cells using one or more component carriers.

[0044] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.

[0045] In some examples, network entities 105 (e.g., base stations 140, RUs 170) can be mobile and, therefore, provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies can overlap, but the different coverage areas 110 can be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies can be supported by different network entities 105. The wireless communication system 100 can include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0046] The wireless communication system 100 may support synchronous or asynchronous operation. For synchronous operation, the network entities 105 (e.g., base stations 140) may have similar frame timing, and transmissions from different network entities 105 may be approximately aligned in time. For asynchronous operation, the network entities 105 may have different frame timing, and in some examples, transmissions from different network entities 105 may not be aligned in time. The techniques described herein may be used for either synchronous or asynchronous operation.

[0047] 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 communication (URLLC). The UE 115 may be designed to support ultra-reliable, low-latency, or critical functionality. Ultra-reliable communication may include private or group communication and may be supported by one or more services such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functionality may include prioritization of services, and such services may 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.

[0048] In some examples, a UE 115 may be configured to support communication directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which may support aspects of such D2D communication as configured (e.g., scheduled) by the network entity 105. In some examples, one or more UEs 115 in such a group may be outside of the coverage area 110 of the network entity 105 or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, network entity 105 may facilitate scheduling of resources for D2D communications. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105.

[0049] The 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 (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to external networks. The control plane entities may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management, for UEs 115 served by network entities 105 (e.g., base stations 140) associated with the core network 130. User IP packets may be delivered via the user plane entities, which may provide IP address allocation and other functions. The user plane entities may connect to IP services 150 of one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0050] The wireless communication system 100 can operate using one or more frequency bands that can range from 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length. UHF waves can be blocked or redirected by buildings and environmental features (which can be referred to as clusters), but these waves can penetrate structures sufficiently for a macrocell to provide service to UEs 115 located indoors. Communication using UHF waves can be associated with smaller antennas and a shorter range (e.g., less than 100 kilometers) compared to communication using the lower frequencies and longer wavelengths in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0051] The wireless communication system 100 can utilize both licensed RF spectrum bands and unlicensed RF spectrum bands. For example, the wireless communication system 100 can use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ license-assisted access (LAA), LTE-unlicensed (LTE-U) radio access technology, or NR technology. When operating using an unlicensed RF spectrum band, devices such as the network entity 105 and the UE 115 can employ carrier sensing for conflict detection and avoidance. In some examples, operations using the unlicensed band can be based on a carrier aggregation configuration (e.g., LAA) in conjunction with component carriers operating using a licensed band. Operations using the unlicensed spectrum can include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among others.

[0052] A network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input, multiple-output (MIMO) communications, or beamforming. The antennas of the network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with the network entity 105 may be located at different geographic locations. The network entity 105 may include an antenna array having a set of multiple rows and columns of antenna ports that the network entity 105 may use to support beamforming for communications with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panels may support RF beamforming for signals transmitted via the antenna ports.

[0053] 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 or receiving device (e.g., network entity 105, UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals communicated via antenna elements of an antenna array so that some signals propagating along a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals communicated via the antenna elements can include the transmitting or receiving device applying an amplitude offset, a phase offset, or both to the signals carried by the antenna elements associated with that device. The adjustments associated with each of these antenna elements can be defined by a set of beamforming weights associated with a particular orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0054] The wireless communication system 100 may be a packet-based network operating according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer may be IP-based. The RLC layer may perform packet segmentation and reassembly for communication via logical channels. The MAC layer may perform priority processing and multiplexing of logical channels into transport channels. The MAC layer may also implement error detection techniques, error correction techniques, or both to support retransmissions to improve link efficiency. In the control plane, the RRC layer may provide for the establishment, configuration, and maintenance of RRC connections between the UE 115 and the network entity 105 or the core network 130 for radio bearers supporting user plane data. The PHY layer may map transport channels to physical channels.

[0055] UE 115 and network entity 105 may support retransmission of data to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correct data reception via a communication link (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, a device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a particular slot for data received via previous symbols in that slot. In other examples, the device may provide HARQ feedback in subsequent slots or based on some other time interval.

[0056] In some examples of wireless communication system 100, network entity 105 may include multiple cells (e.g., supported by DU 165 associated with network entity 105). Among these multiple cells, one or more activated cells may be or represent cells used for data and control communications with UE 115 to support uplink and downlink communications. A cell may refer to a logical communication entity used for communications between UE 115 and network entity 105. In some examples, a cell may also refer to a geographic area or portion of a geographic area in which the logical communication entity operates. At least one of the cells associated with the communication may be configured as a PCell (e.g., a source cell). The PCell may refer to the cell in which UE 115 is currently communicating and is the cell with which UE 115 conducts the majority of its communications with network entity 105. In some situations (e.g., if UE 115 is mobile, if network conditions change), communication quality may be improved by changing the source cell to a second cell (e.g., a target cell). Such techniques may be referred to as cell mobility, cell mobility management, inter-cell mobility, etc.

[0057] In some examples, UE 115 may be configured to monitor one or more resources of a channel associated with a current source cell and may receive a MAC-CE message (e.g., via L2 signaling) including a cell handover command instructing to hand over communications from the current source cell to a target cell. In response, UE 115 may send a feedback message to network entity 105 indicating an ACK or NACK for a MAC-CE message used to perform a handover procedure associated with the cell handover command. In some examples, UE 115 may send the feedback message to the current source cell. Additionally or alternatively, UE 115 may send the feedback message to the target cell.

[0058] In some cases, UE 115 may determine whether the handover to the target cell is successful based on the status of a configured timer. In some examples, UE 115 may initiate the timer in response to receiving a MAC-CE message. In some examples, UE 115 may initiate the timer in response to sending a feedback message. In some examples, UE 115 may stop the timer in response to receiving a first downlink message from the target cell. In some examples, UE 115 may stop the timer in response to sending an acknowledgment message of the first downlink message to network entity 105 via the target cell. If the timer expires, UE 115 may switch back to the source cell and send a handover failure message to network entity 105 (e.g., via the source cell).

[0059] Figure 2 An example network architecture 200 (e.g., a decomposed base station architecture, a decomposed RAN architecture) supporting feedback messaging for cell handover commands according to one or more aspects of the present disclosure is illustrated. Network architecture 200 may illustrate an example for implementing one or more aspects of wireless communication system 100. Network architecture 200 may include one or more CUs 160-a that may communicate directly with a core network 130-a via a backhaul communication link 120-a, or indirectly with the core network 130-a via one or more decomposed network entities 105 (e.g., a near-RT RIC 175-b via an E2 link, a non-RT RIC 175-a associated with an SMO 180-a (e.g., an SMO framework), or both). CUs 160-a may communicate with one or more DUs 165-a via corresponding midhaul communication links 162-a (e.g., an F1 interface). DUs 165-a may communicate with one or more RUs 170-a via corresponding fronthaul communication links 168-a. A RU 170-a may be associated with a corresponding coverage area 110-a and may communicate with a UE 115-a via one or more communication links 125-a. In some implementations, a UE 115-a may be simultaneously served by multiple RUs 170-a.

[0060] Each of the network entities 105 of the network architecture 200 (e.g., CU 160-a, DU 165-a, RU 170-a, non-RT RIC 175-a, near-RT RIC 175-b, SMO 180-a, open cloud (O-Cloud) 205, open eNB (O-eNB) 210) may include one or more interfaces or may be coupled to one or more interfaces configured to receive or transmit signals (e.g., data, information) via a wired or wireless transmission medium. Each network entity 105, or an associated processor (e.g., a controller) that provides instructions to an interface of the network entity 105, may be configured to communicate with one or more of the other network entities 105 via the transmission medium. For example, these network entities 105 may include a wired interface configured to receive signals on the wired transmission medium or to transmit signals to one or more of the other network entities 105 over the wired transmission medium. Additionally or alternatively, the network entity 105 may include a wireless interface, which may include a receiver, transmitter, or transceiver (e.g., an RF transceiver) configured to receive signals over a wireless transmission medium, or to transmit signals over a wireless transmission medium to one or more of the other network entities 105, or both.

[0061] In some examples, CU 160-a may host one or more higher layer control functions. Such control functions may include RRC, PDCP, SDAP, etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by CU 160-a. CU 160-a may be configured to handle user plane functionality (e.g., CU-UP), control plane functionality (e.g., CU-CP), or a combination thereof. In some examples, CU 160-a may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units may communicate bidirectionally with the CU-CP units via an interface (such as an E1 interface). As needed, CU 160-a may be implemented to communicate with DU 165-a for network control and signaling.

[0062] DU 165-a may correspond to a logical unit that includes one or more functions (e.g., base station functions, RAN functions) for controlling the operation of one or more RUs 170-a. In some examples, DU 165-a may at least partially host one or more of the RLC layer, the MAC layer, and one or more aspects of the PHY layer (e.g., high PHY layers, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, etc.), depending at least in part on functional partitioning, such as those defined by the Third Generation Partnership Project (3GPP). In some examples, DU 165-a may also host one or more low PHY layers. Each layer may be implemented using an interface that is configured to communicate signals with other layers hosted by DU 165-a or with control functions hosted by CU 160-a.

[0063] In some examples, lower layer functionality may be implemented by one or more RUs 170-a. For example, a RU 170-a controlled by a DU 165-a may correspond to a logical node that hosts RF processing functionality or low PHY layer functionality (e.g., performing fast Fourier transforms (FFTs), inverse FFTs (iFFTs), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 170-a may be implemented to handle over-the-air (OTA) communications with one or more UEs 115-a. In some implementations, real-time and non-real-time aspects of control and user plane communications with the RU 170-a may be controlled by the corresponding DU 165-a. In some examples, such a configuration may enable the DU 165-a and CU 160-a to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0064] SMO 180-a can be configured to support RAN deployment and provisioning for both non-virtualized and virtualized network entities 105. For non-virtualized network entities 105, SMO 180-a can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface (e.g., an O1 interface). For virtualized network entities 105, SMO 180-a can be configured to interact with a cloud computing platform (e.g., O-Cloud 205) via a cloud computing platform interface (e.g., an O2 interface) to perform network entity lifecycle management (e.g., to instantiate virtualized network entities 105). Such virtualized network entities 105 can include, but are not limited to, CU 160-a, DU 165-a, RU 170-a, and near-RT RIC 175-b. In some implementations, SMO 180-a can communicate with components configured according to a 4G RAN (e.g., via the O1 interface). Additionally or alternatively, in some implementations, the SMO 180-a may communicate directly with one or more RUs 170-a via an 01 interface.The SMO 180-a may also include a non-RT RIC 175-a configured to support the functionality of the SMO 180-a.

[0065] The non-RT RIC 175-a may be configured to include logic that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) or machine learning (ML) workflows (including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 175-b). The non-RT RIC 175-a may be coupled to or in communication with the near-RT RIC 175-b (e.g., via an A1 interface). The near-RT RIC 175-b may be configured to include logic that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface connecting one or more CUs 160-a, one or more DUs 165-a, or both, and the O-eNB 210 to the near-RT RIC 175-b (e.g., via an E2 interface).

[0066] In some examples, non-RT RIC 175-a may receive parameters or external enrichment information from an external server to generate an AI / ML model to be deployed in near-RT RIC 175-b. This information may be utilized by near-RT RIC 175-b and may be received from a non-network data source or from a network function at SMO 180-a or non-RT RIC 175-a. In some examples, non-RT RIC 175-a or near-RT RIC 175-b may be configured to tune RAN behavior or performance. For example, non-RT RIC 175-a may monitor long-term trends and patterns in performance and employ AI or ML models to execute corrective actions through SMO 180-a (e.g., via reconfiguration of O1) or through the generation of RAN management policies (e.g., A1 policies).

[0067] In some examples, components of the network entity 105 may support communication via multiple cells. For example, a DU 165-a associated with the network entity 105 may support communication for one or more UEs 115-a via one or more cells. In some examples, one or more of the cells may be activated to communicate with the UE 115-a. That is, the DU 165-a may communicate with the UE 115-a via the cell using the RU 170-a. For example, the DU 165-a may be configured as a PCell and may send a message (e.g., a MAC-CE message) to the RU 170-a. The RU 170-a may send (e.g., relay) a message to the UE 115-a indicating that the UE 115-a is changing from the PCell to a second cell (e.g., a target cell), which may be supported by the same DU 165-a or another DU 165-a.

[0068] The MAC-CE message may be sent via L2 signaling and may include a cell handover command instructing UE 115-a to handover communications from a source cell to a target cell. The target cell may be associated with and support communications for a corresponding coverage area 110-a. In response, UE 115-a may send a feedback message to DU 165-a via RU 170-a. The feedback message may indicate ACK or NACK feedback for the MAC-CE message. In some examples, UE 115-a may send the feedback message to DU 165-a via the PCell, or may send the feedback message to DU 165-a supporting the target cell via the target cell.

[0069] Figure 3An example of a wireless communication system 300 that supports feedback messaging for cell handover commands according to one or more aspects of the present disclosure is illustrated. In some examples, the wireless communication system 300 may implement or be implemented by one or more aspects of the wireless communication system 100 and the network architecture 200. For example, the wireless communication system 300 may include network entities 105-a and 105-b and UE 115-b, which may be reference Figure 1 Examples of network entities 105 and UEs 115 are described. The network entities 105-a and 105-b may include a cell set 310 (eg, supported by one or more DUs 165), where each cell 305 in the cell set 310 may represent a reference Figure 1 and Figure 2 Any one or more of the examples of cells described. In some examples, the network entity 105 may include Figure 1 Each of the illustrated cells 305, while in some other examples, the network entity 105 may include Figure 1 At least a subset or portion of the illustrated cells 305.

[0070] One or more of the cells 305 may communicate with the UE 115-b, for example, to support uplink or downlink communications with the network entity 105-a or with another network entity 105 (e.g., the network entity 105-b). For example, the UE 115-b may communicate with an activated subset 315 of cells 305, which may include cells 305-a, 305-b, and 305-c (e.g., as well as other cells 305). At least one of the cells 305 in the activated subset 315 may be configured as a PCell (e.g., cell 305-a may be the PCell for the UE 115-b). In some examples, the PCell may refer to the source cell 305 on which the UE 115-b performs an initial connection with the network entity 105-a or reestablishes a connection with the network entity 105-a, and is the cell 305 with which the UE 115-b performs the majority of communications with the network entity 105-a.

[0071] In some cases (e.g., if UE 115-b is mobile or if network conditions change), communication quality can be improved by changing the PCell to another cell 305, or by changing one or more cells 305 in the active subset 315 (e.g., by activating one or more cells 305 outside of the active subset 315 to include them in the active subset 315). For example, the inactive subset 320 of cells 305 may include cells 305-d and 305-e (e.g., as well as other cells 305). Thus, network entity 105-a or network entity 105-b may transition one or more cells 305 from the inactive subset 320 to the active subset 315. Such techniques may be referred to as cell mobility, cell mobility management, inter-cell mobility, etc. In some cases, network entity 105-a (e.g., or network entity 105-b) may provide higher layer signaling, or L3 signaling, to perform inter-cell mobility (e.g., switching the PCell, changing the active subset 315 of cells 305). Such signaling may be referred to as handover, L3 handover, handover command, etc., and may be associated with increased latency or delay compared to, for example, lower layer signaling, such as L1 signaling and L2 signaling.

[0072] In some cases, the network entity 105-a and the UE 115-b may use L1 or L2 signaling to support inter-cell mobility, which may be referred to as L1 / L2 inter-cell mobility, L1 / L2 mobility, or L1 / L2 cell mobility management, among others. Thus, the network entity 105-a may indicate a handover from a source cell 305 (e.g., cell 305-a) to a target cell 305 (e.g., cell 305-b) via L1 / L2 triggered mobility. For example, the UE 115-b may receive (e.g., via L2 signaling 325) a MAC-CE message 330 that may include a cell handover command indicating a handover of the PCell from the source cell 305 (e.g., cell 305-a) to the target cell 305 (e.g., cell 305-b). In some examples, the current PCell (e.g., cell 305-a) may be configured to send the MAC-CE message 330 via a physical downlink shared channel (PDSCH).

[0073] Upon receiving the MAC-CE message 330, the UE 115-b may send a feedback message 335. In some examples, the feedback message 335 may include an ACK indicating successful decoding of the MAC-CE message 330, or may include a NACK indicating unsuccessful decoding of the MAC-CE message 330. In some examples, the UE 115-b may send the feedback message 335 to the current PCell (e.g., cell 305-a) (e.g., via L2 signaling 325). Additionally or alternatively, the UE 115-b may send the feedback message 335 to the target cell 305 (e.g., cell 305-b) indicated in the MAC-CE message 330 (e.g., via L2 signaling 325). In some examples, the MAC-CE message 330 may include a time offset associated with the UE 115-b sending the feedback message 335. For example, in response to receiving the MAC-CE message 330, the UE 115-b may wait for a duration indicated by the time offset before sending the feedback message 335.

[0074] In some cases, the feedback message 335 may be an example of uplink control information (UCI). Thus, the UE 115-b may transmit the UCI including the feedback message 335 via a physical uplink control channel (PUCCH), a scheduling request PUCCH (SR-PUCCH), or a physical uplink shared channel (PUSCH). In some examples, the UE 115-b may use a channel resource index to determine the uplink channel on which to transmit the feedback message 335. For example, the UE 115-b may receive a channel resource index (e.g., a PUCCH resource index, a PUSCH resource index, or both) as part of the MAC-CE message 330, which may indicate one or more resources associated with the uplink channel. Thus, the UE 115-b may transmit the feedback message 335 using the one or more resources included in the channel resource index, as indicated in the MAC-CE message 330.

[0075] Additionally or alternatively, feedback message 335 may be an example of a MAC-CE response message. For example, UE 115-b may send feedback message 335 as a dedicated acknowledgment MAC-CE, where the dedicated acknowledgment MAC-CE may include a decoding result of MAC-CE message 330 (e.g., an ACK or NACK indication associated with decoded MAC-CE message 330). In some examples, UE 115-b may send the dedicated acknowledgment MAC-CE to the current PCell (e.g., cell 305-a). Additionally or alternatively, UE 115-b may send the dedicated acknowledgment MAC-CE to the target cell 305 (e.g., cell 305-b).

[0076] In some cases, UE 115-b may initiate a timer 355 associated with performing a handover procedure from source cell 305 to target cell 305 and communicate one or more messages with network entity 105-a based on the status of timer 355. In some examples, UE 115-b may receive an indication of timer 355 from network entity 105-a. For example, UE 115-b may receive the indication of timer 355 as part of MAC-CE message 330. Additionally or alternatively, UE 115-b may receive the indication of timer 355 from network entity 105-a in signaling separate from MAC-CE message 330 (e.g., separate L1, L2, or L3 signaling). Additionally or alternatively, UE 115-b may be pre-configured with timer 355.

[0077] UE 115-b may start timer 355 based on communicating one or more messages with network entity 105-a. In some examples, UE 115-b may start timer 355 in response to receiving a cell handover command included in MAC-CE message 330. In some examples, UE 115-b may start timer 355 in response to sending feedback message 335 for the cell handover command.

[0078] UE 115-b may stop timer 355 based on communicating one or more messages with network entity 105-a. For example, UE 115-b may receive (e.g., via a PDSCH) a downlink message 340 from a target cell 305 (e.g., cell 305-b). In some cases, downlink message 340 may be DCI that schedules a transport block for a HARQ identifier (e.g., for a PDSCH or PUSCH). In some examples, the DCI may additionally include a new data allocation indicator (NDI) associated with the transport block, and UE 115-b may stop timer 355 based on the DCI including the NDI. In some examples, UE 115-b may send an acknowledgment message 345 to the target cell 305 associated with receiving the DCI that scheduled the transport block. In some examples, UE 115-b may stop timer 355 based on sending acknowledgment message 345.

[0079] In some examples, a timer 355 at UE 115-b may expire. In such an example, UE 115-b may determine that the handover process has failed and switch communications back to the original PCell (e.g., cell 305-a). Consequently, UE 115-b may send a handover failure message 350 to network entity 105-a (e.g., cell 305-a), which may indicate that the handover process has failed based on the expiration of timer 355. In some examples, network entity 105-a may also be configured with timer 355 and may identify the status of timer 355 concurrently with UE 115-b. In the example where the handover process has failed, network entity 105-a may send a second MAC-CE message 330 including a cell handover command. In some examples, the second MAC-CE message 330 may include the same information as the previous MAC-CE message 330 (e.g., the same target cell 305, the same resource pool index, the same time offset). In some examples, the second MAC-CE message 330 may include different information than the previous MAC-CE message 330 (eg, a different target cell 305 , a different resource pool index, a different time offset).

[0080] Figure 4 An example of a process flow 400 for supporting feedback messaging for a cell handover command according to one or more aspects of the present disclosure is illustrated. In some examples, the process flow 400 can implement aspects of wireless communication systems 100 to 300. The process flow 400 includes a UE 115-c and a network entity 105-c, which can be as described in reference Figures 1 to 3 1 and 105. As illustrated, the network entity 105-c may include one or more cells 405 (e.g., cell 405-a and cell 405-b) that the network entity 105-c may use to communicate with the UE 115-c. The following alternative examples may be implemented in which some of the steps are performed in a different order than described, or not performed at all. In some cases, the steps may include additional features not described below, or other steps may be added. Furthermore, while the process flow 400 illustrates the processes between a single UE 115 and a single network entity 105, it should be understood that these processes may occur between any number of network devices and types of network devices. For example, the cell 405 may be associated with additional network entities 105 not illustrated in the process flow 400.

[0081] At 410 , the UE 115 - c may monitor one or more resources of a channel (eg, a PDSCH) associated with the cell 405 - a for MAC-CE messages associated with a handover procedure for the UE 115 - c .

[0082] At 415 , the UE 115 - c may receive a MAC-CE message via the channel and from the cell 405 - a (eg, a source cell) based on the monitoring.

[0083] At 420, UE 115-c may decode the MAC-CE message based on monitoring the one or more resources. In some examples, the MAC-CE message may include a cell handover command indicating a handover from cell 405-a (e.g., a source cell) to cell 405-b (e.g., a target cell) as part of a handover procedure for UE 115-c.

[0084] At 425, UE 115-c may send a feedback message for the MAC-CE message based on decoding the MAC-CE message. In some examples, the feedback message may indicate a decoding result of decoding the MAC-CE message. Additionally or alternatively, the feedback message may include a decoding result of a cell handover command.

[0085] In some examples, UE 115-c may send a feedback message to cell 405-b and via an uplink channel associated with cell 405-b. The decoding result may include an ACK or NACK for decoding the MAC-CE message. In some examples, the uplink channel associated with cell 405-b may be a PUCCH or a PUSCH. Additionally or alternatively, the feedback message may be UCI.

[0086] In some examples, UE 115-c may send a feedback message to cell 405-b and via an uplink channel associated with cell 405-b. The decoding result may include an ACK or NACK for decoding the MAC-CE message. In some examples, the uplink channel associated with cell 405-b may be a PUCCH, a dedicated SR-PUCCH, or a PUSCH. Additionally or alternatively, the feedback message may be UCI.

[0087] In some examples, UE 115-c may send the feedback message using uplink resources (e.g., PUCCH or PUSCH resource index) that may be indicated by the MAC-CE message. In some examples, UE 115-c may send the feedback message according to a delay. For example, the time delay may be associated with feedback for a MAC cell handover command configured at UE 115-c. Additionally or alternatively, UE 115-c may send the feedback according to a time offset that may be indicated by the MAC-CE message.

[0088] In some examples, UE 115-c may send the feedback message via a MAC-CE dedicated for feedback regarding the cell handover command indicated by the MAC-CE message. In some examples, UE 115-c may send the MAC-CE dedicated for feedback to cell 405-a. In some examples, UE 115-c may send the MAC-CE dedicated for feedback to cell 405-b.

[0089] Figure 5 An example of a process flow 500 for supporting feedback messaging for a cell handover command according to one or more aspects of the present disclosure is illustrated. In some examples, the process flow 500 can implement aspects of wireless communication systems 100 to 300 and process flow 400. The process flow 500 includes a UE 115-d and a network entity 105-d, which can be as described in reference Figures 1 to 4 1 and 105. As illustrated, the network entity 105-d may include one or more cells 505 (e.g., cell 505-a and cell 505-b) that the network entity 105-d may use to communicate with the UE 115-d. The following alternative examples may be implemented in which some of the steps are performed in a different order than described, or not performed at all. In some cases, the steps may include additional features not described below, or other steps may be added. Furthermore, while the process flow 500 illustrates the processes between a single UE 115 and a single network entity 105, it should be understood that these processes may occur between any number of network devices and types of network devices. For example, the cell 505 may be associated with additional network entities 105 not illustrated in the process flow 500.

[0090] At 515 , UE 115 - d may monitor one or more resources of a channel (eg, PDSCH) associated with cell 505 - a for MAC-CE messages associated with a handover procedure for UE 115 - d .

[0091] At 520, UE 115-d may receive a MAC-CE message based on monitoring the one or more resources. In some examples, the MAC-CE message may include a cell handover command indicating a handover from cell 505-a (e.g., a source cell) to cell 505-b (e.g., a target cell) as part of a handover procedure for UE 115-d.

[0092] In some examples, UE 115-d may initiate timer 510 associated with the handover process from cell 505-a to cell 505-b according to the cell switching command. For example, UE 115-d may initiate timer 510 in response to receiving a MAC-CE message.

[0093] At 525, UE 115-d may send a feedback message for the MAC-CE message based on receiving the MAC-CE message. In some examples, UE 115-d may initiate timer 510 in response to sending the feedback message.

[0094] At 530, UE 115-d may receive, via a data channel associated with cell 505-b, DCI scheduling a transport block for the HARQ identifier. In some examples, the DCI may schedule a transport block for the PUSCH or PDSCH. In some examples, the DCI may be the first message received by UE 115-d after switching from cell 505-a to cell 505-b. In some examples, the DCI may also include an NDI associated with the transport block, and UE 115-d may stop timer 510 based on receiving the DCI including the NDI associated with the transport block.

[0095] At 535, UE 115-d may send an acknowledgment message associated with receiving the DCI scheduling the transport block to cell 505-b. In some examples, UE 115-d may stop timer 510 based on sending the acknowledgment message.

[0096] In some cases, timer 510 may expire. Thus, at 540, UE 115-d may send a handover failure message indicating that the handover process from cell 505-a to cell 505-b failed based on the expiration of the timer.

[0097] Figure 6 A block diagram 600 illustrates a device 605 that supports feedback messaging for cell handover commands according to one or more aspects of the present disclosure. The device 605 may be an example of aspects of the UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. The device 605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0098] Receiver 610 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to feedback messaging for cell handover commands, data channels, information channels). The information may be delivered to other components of device 605. Receiver 610 may utilize a single antenna or a collection of multiple antennas.

[0099] Transmitter 615 may provide means for transmitting signals generated by other components of device 605. For example, transmitter 615 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to feedback messaging for cell handover commands, data channels, information channels). In some examples, transmitter 615 may be co-located with receiver 610 in a transceiver module. Transmitter 615 may utilize a single antenna or a collection of multiple antennas.

[0100] The communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of feedback messaging for a cell handover command as described herein. For example, the communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0101] In some examples, the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting components for performing the functions described herein. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0102] Additionally or alternatively, in some examples, the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be performed by a general-purpose processor (e.g., configured as or otherwise supporting means for performing the functions described herein), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0103] In some examples, communication manager 620 can be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise coordinating with receiver 610, transmitter 615, or both. For example, communication manager 620 can receive information from receiver 610, transmit information to transmitter 615, or otherwise integrate with receiver 610, transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

[0104] According to examples as disclosed herein, the communication manager 620 may support wireless communications. For example, the communication manager 620 may be configured as or otherwise support a component for monitoring one or more resources of a channel associated with a first cell for a medium access control message associated with a handover procedure for a UE. The communication manager 620 may be configured as or otherwise support a component for decoding a medium access control message based on monitoring the one or more resources, the medium access control message including a cell handover command indicating a handover from the first cell to the second cell as part of the handover procedure for the UE. The communication manager 620 may be configured as or otherwise support a component for sending a feedback message for the medium access control message based on decoding the medium access control message, the feedback message indicating a decoding result of decoding the medium access control message.

[0105] Additionally or alternatively, the communication manager 620 may support wireless communications according to examples as disclosed herein. For example, the communication manager 620 may be configured as or otherwise support components for monitoring one or more resources of a channel associated with a first cell for a media access control message associated with a handover procedure for a UE. The communication manager 620 may be configured as or otherwise support components for receiving a media access control message based on monitoring the one or more resources, the media access control message including a cell handover command indicating a handover from the first cell to the second cell as part of a handover procedure for the UE. The communication manager 620 may be configured as or otherwise support components for initiating a timer associated with a handover procedure from the first cell to the second cell based on the cell handover command. The communication manager 620 may be configured as or otherwise support components for communicating one or more messages associated with the handover procedure based on a status of the timer.

[0106] By including or configuring a communication manager 620 according to examples as described herein, the device 605 (e.g., a processor controlling or otherwise coupled with the receiver 610, the transmitter 615, the communication manager 620, or a combination thereof) can support techniques for reducing processing, reducing latency, and more efficiently utilizing communication resources.

[0107] Figure 7 A block diagram 700 illustrates a device 705 that supports feedback messaging for cell handover commands according to one or more aspects of the present disclosure. The device 705 may be an example of aspects of the device 605 or UE 115 as described herein. The device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. The device 705 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0108] Receiver 710 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to feedback messaging for cell handover commands, data channels, information channels). The information may be delivered to other components of device 705. Receiver 710 may utilize a single antenna or a collection of multiple antennas.

[0109] The transmitter 715 may provide means for transmitting signals generated by other components of the device 705. For example, the transmitter 715 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to feedback messaging for cell handover commands, data channels, information channels). In some examples, the transmitter 715 may be co-located with the receiver 710 in a transceiver module. The transmitter 715 may utilize a single antenna or a collection of multiple antennas.

[0110] Device 705 or its various components may be examples of components for performing various aspects of feedback messaging for cell handover commands as described herein. For example, communications manager 720 may include resource monitoring component 725, decoding component 730, transmitting component 735, receiving component 740, timing component 745, or any combination thereof. Communications manager 720 may be an example of various aspects of communications manager 620 as described herein. In some examples, communications manager 720 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise coordinating with receiver 710, transmitter 715, or both. For example, communications manager 720 may receive information from receiver 710, transmit information to transmitter 715, or be integrated with receiver 710, transmitter 715, or both to obtain information, output information, or perform various other operations as described herein.

[0111] According to examples as disclosed herein, the communication manager 720 may support wireless communications. The resource monitoring component 725 may be configured as or otherwise support a component for monitoring one or more resources of a channel associated with a first cell for a medium access control message associated with a handover procedure of a UE. The decoding component 730 may be configured as or otherwise support a component for decoding a medium access control message based on monitoring the one or more resources, the medium access control message including a cell handover command indicating a handover from the first cell to the second cell as part of the handover procedure of the UE. The sending component 735 may be configured as or otherwise support a component for sending a feedback message for the medium access control message based on decoding the medium access control message, the feedback message indicating a decoding result of decoding the medium access control message.

[0112] Additionally or alternatively, the communication manager 720 may support wireless communications according to examples as disclosed herein. The resource monitoring component 725 may be configured as or otherwise support a component for monitoring one or more resources of a channel associated with the first cell for a medium access control message associated with a handover process for the UE. The receiving component 740 may be configured as or otherwise support a component for receiving a medium access control message based on monitoring the one or more resources, the medium access control message including a cell handover command indicating a handover from the first cell to the second cell as part of a handover process for the UE. The timing component 745 may be configured as or otherwise support a component for initiating a timer associated with the handover process from the first cell to the second cell based on the cell handover command. The timing component 745 may be configured as or otherwise support a component for communicating one or more messages associated with the handover process based on a status of the timer.

[0113] Figure 8 A block diagram 800 illustrates a communication manager 820 that supports feedback messaging for a cell handover command, in accordance with one or more aspects of the present disclosure. The communication manager 820 can be an example of aspects of the communication manager 620, the communication manager 720, or both, as described herein. The communication manager 820 or its various components can be examples of means for performing various aspects of feedback messaging for a cell handover command, as described herein. For example, the communication manager 820 can include a resource monitoring component 825, a decoding component 830, a transmitting component 835, a receiving component 840, a timing component 845, or any combination thereof. Each of these components can communicate with each other, directly or indirectly (e.g., via one or more buses).

[0114] According to examples as disclosed herein, the communication manager 820 may support wireless communications. The resource monitoring component 825 may be configured as or otherwise support a component for monitoring one or more resources of a channel associated with a first cell for a medium access control message associated with a handover procedure of a UE. The decoding component 830 may be configured as or otherwise support a component for decoding a medium access control message based on monitoring the one or more resources, the medium access control message including a cell handover command indicating a handover from the first cell to the second cell as part of the handover procedure of the UE. The sending component 835 may be configured as or otherwise support a component for sending a feedback message for the medium access control message based on decoding the medium access control message, the feedback message indicating a decoding result of decoding the medium access control message.

[0115] In some examples, to support sending the feedback message, the sending component 835 can be configured as or otherwise support means for sending an indication of a decoding result of the cell handover command in a feedback message.

[0116] In some examples, the receiving component 840 may be configured as or otherwise support means for receiving, based on monitoring, a medium access control message via a channel and from a first cell, wherein the channel comprises a physical downlink shared channel, wherein a feedback message indicating a decoding result is sent to the first cell and via an uplink channel associated with a second cell, the decoding result comprising an acknowledgment or a negative acknowledgment of decoding of the medium access control message.

[0117] In some examples, the uplink channel associated with the first cell is a physical uplink control channel or a physical uplink shared channel, and the feedback message is uplink control information.

[0118] In some examples, the receiving component 840 may be configured as or otherwise support a component for: receiving, based on monitoring, a medium access control message via a channel and from a first cell, wherein the channel includes a physical downlink shared channel, wherein a feedback message indicating a decoding result is sent to a second cell and via an uplink channel associated with the first cell, the decoding result including an acknowledgment or a negative acknowledgment of the decoding of the medium access control message.

[0119] In some examples, the uplink channel associated with the second cell is a physical uplink control channel, a dedicated physical uplink control channel for scheduling requests, or a physical uplink shared channel, and the feedback message is uplink control information.

[0120] In some examples, to support sending the feedback message, the sending component 835 can be configured as or otherwise support means for sending the feedback message using uplink resources indicated by the medium access control message based on the decoding.

[0121] In some examples, to support sending the feedback message, the sending component 835 can be configured as or otherwise support means for sending the feedback message according to a time offset indicated by the medium access control message based on the decoding.

[0122] In some examples, to support sending the feedback message, the sending component 835 can be configured as or otherwise support means for sending the feedback message after a time delay associated with feedback for a medium access control cell handover command.

[0123] In some examples, to support sending a feedback message, the sending component 835 may be configured as or otherwise support a component for sending a feedback message to the first cell via a medium access control control element dedicated to feedback on a cell switching command indicated by a medium access control message.

[0124] In some examples, to support sending the feedback message, the sending component 835 may be configured as or otherwise support a component for sending the feedback message to the second cell via a medium access control control element dedicated to feedback on the cell switching command indicated by the medium access control message.

[0125] Additionally or alternatively, the communication manager 820 may support wireless communications according to examples as disclosed herein. In some examples, the resource monitoring component 825 may be configured as or otherwise support a component for monitoring one or more resources of a channel associated with the first cell for a medium access control message associated with a handover process for the UE. The receiving component 840 may be configured as or otherwise support a component for receiving a medium access control message based on monitoring the one or more resources, the medium access control message including a cell handover command indicating a handover from the first cell to the second cell as part of the handover process for the UE. The timing component 845 may be configured as or otherwise support a component for initiating a timer associated with the handover process from the first cell to the second cell based on the cell handover command. In some examples, the timing component 845 may be configured as or otherwise support a component for communicating one or more messages associated with the handover process based on the state of the timer.

[0126] In some examples, to support initiating a timer, timing component 845 can be configured as or otherwise support means for initiating a timer associated with a handover process in response to receiving a medium access control message.

[0127] In some examples, to support communicating the one or more messages associated with the handover process, the sending component 835 may be configured as or otherwise support a component for sending a feedback message for the media access control message based on receiving the media access control message, wherein a timer associated with the handover process is initiated in response to sending the feedback message.

[0128] In some examples, to support communicating the one or more messages associated with the handover process, the receiving component 840 may be configured as or otherwise support a component for receiving downlink control information scheduling a transport block for a hybrid automatic repeat request identifier via a data channel associated with the second cell.

[0129] In some examples, the downlink control information also includes a new data allocation indicator associated with the transport block, and the timing component 845 can be configured as or otherwise support a component for stopping the timer based on receiving the downlink control information including the new data allocation indicator associated with the transport block.

[0130] In some examples, the transmitting component 835 can be configured as or otherwise support means for transmitting to the second cell an acknowledgment message associated with receiving downlink control information of a scheduled transport block. In some examples, the timing component 845 can be configured as or otherwise support means for stopping a timer based on transmitting the acknowledgment message.

[0131] In some examples, the data channel is a physical uplink shared channel or a physical downlink shared channel.

[0132] In some examples, to support communicating the one or more messages associated with the handover process, the sending component 835 may be configured as or otherwise support a component for sending a handover failure message indicating a failure of the handover process from the first cell to the second cell based on expiration of a timer.

[0133] Figure 9A diagram illustrates a system 900 including a device 905 that supports feedback messaging for cell handover commands, according to one or more aspects of the present disclosure. Device 905 may be an example of, or include components of, device 605, device 705, or UE 115, as described herein. Device 905 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. Device 905 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communications manager 920, an input / output (I / O) controller 910, a transceiver 915, an antenna 925, memory 930, code 935, and a processor 940. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, or electrically) via one or more buses (e.g., bus 945).

[0134] I / O controller 910 can manage input and output signals for device 905. I / O controller 910 can also manage peripheral devices that are not integrated into device 905. In some cases, I / O controller 910 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 910 can 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 910 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 910 may be implemented as part of a processor (such as processor 940). In some cases, a user may interact with device 905 via I / O controller 910 or via hardware components controlled by I / O controller 910.

[0135] In some cases, the device 905 may include a single antenna 925. However, in some other cases, the device 905 may have more than one antenna 925, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 915 may communicate bidirectionally via one or more antennas 925, wired, or wireless links, as described herein. For example, the transceiver 915 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 915 may also include a modem for modulating packets; providing the modulated packets to the one or more antennas 925 for transmission; and demodulating packets received from the one or more antennas 925. The transceiver 915, or the transceiver 915 and the one or more antennas 925, may be examples of the transmitter 615, the transmitter 715, the receiver 610, the receiver 710, or any combination thereof, or components thereof, as described herein.

[0136] The memory 930 may include random access memory (RAM) and read-only memory (ROM). The memory 930 may store computer-readable, computer-executable code 935 including instructions that, when executed by the processor 940, cause the device 905 to perform the various functions described herein. The code 935 may be stored in a non-transitory computer-readable medium (such as system memory or another type of memory). In some cases, the code 935 may not be directly executable by the processor 940, but may (for example, when compiled and executed) cause the computer to perform the functions described herein. In some cases, the memory 930 may also contain, among other things, a basic I / O system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0137] The processor 940 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, the processor 940 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 940. The processor 940 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 930) to cause the device 905 to perform various functions (e.g., functions or tasks supporting the reception and transmission of feedback messages for cell handover commands). For example, the device 905 or a component of the device 905 may include the processor 940 and the memory 930 coupled to or coupled to the processor 940, the processor 940 and the memory 930 being configured to perform the various functions described herein.

[0138] According to examples as disclosed herein, the communication manager 920 may support wireless communications. For example, the communication manager 920 may be configured as or otherwise support a component for monitoring one or more resources of a channel associated with a first cell for a medium access control message associated with a handover procedure for a UE. The communication manager 920 may be configured as or otherwise support a component for decoding a medium access control message based on monitoring the one or more resources, the medium access control message including a cell handover command indicating a handover from a first cell to a second cell as part of a handover procedure for the UE. The communication manager 920 may be configured as or otherwise support a component for sending a feedback message for the medium access control message based on decoding the medium access control message, the feedback message indicating a decoding result of decoding the medium access control message.

[0139] Additionally or alternatively, the communication manager 920 may support wireless communications according to the examples disclosed herein. For example, the communication manager 920 may be configured as or otherwise support a component for monitoring one or more resources of a channel associated with the first cell for a media access control message associated with a handover process for the UE. The communication manager 920 may be configured as or otherwise support a component for receiving a media access control message based on monitoring the one or more resources, the media access control message including a cell handover command indicating a handover from the first cell to the second cell as part of the handover process for the UE. The communication manager 920 may be configured as or otherwise support a component for initiating a timer associated with the handover process from the first cell to the second cell based on the cell handover command. The communication manager 920 may be configured as or otherwise support a component for communicating one or more messages associated with the handover process based on the status of the timer.

[0140] By including or configuring a communication manager 920 according to examples as described herein, the device 905 may support techniques for improving communication reliability, reducing latency, improving user experience associated with reduced processing, lowering power consumption, more efficient use of communication resources, improving coordination between devices, extending battery life, and improving utilization of processing power.

[0141] In some examples, the communication manager 920 can be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise coordinating with the transceiver 915, one or more antennas 925, or any combination thereof. Although the communication manager 920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 920 can be supported or performed by the processor 940, the memory 930, the code 935, or any combination thereof. For example, the code 935 can include instructions executable by the processor 940 to cause the device 905 to perform various aspects of feedback messaging for a cell handover command as described herein, or the processor 940 and the memory 930 can be otherwise configured to perform or support such operations.

[0142] Figure 10 A block diagram 1000 illustrates a device 1005 that supports feedback messaging for cell handover commands according to one or more aspects of the present disclosure. The device 1005 may be an example of aspects of the network entity 105 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0143] Receiver 1010 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be delivered to other components of device 1005. In some examples, receiver 1010 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1010 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0144] Transmitter 1015 may provide means for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1005. For example, transmitter 1015 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1015 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1015 may support outputting information by transmitting signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1015 and receiver 1010 may be co-located in a transceiver, which may include or be coupled to a modem.

[0145] The communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of feedback messaging for a cell handover command as described herein. For example, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0146] In some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof can be implemented in hardware (e.g., in a communication management circuit). The hardware can include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting components for performing the functions described herein. In some examples, a processor and a memory coupled to the processor can be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0147] Additionally or alternatively, in some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be performed by a general-purpose processor (e.g., configured as or otherwise supporting means for performing the functions described in this disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0148] In some examples, communication manager 1020 can be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise coordinating with receiver 1010, transmitter 1015, or both. For example, communication manager 1020 can receive information from receiver 1010, transmit information to transmitter 1015, or be integrated with receiver 1010, transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0149] According to examples as disclosed herein, the communication manager 1020 may support wireless communications. For example, the communication manager 1020 may be configured as or otherwise support a component for sending a medium access control message including a cell handover command via one or more resources of a channel associated with a first cell, the cell handover command indicating a handover from the first cell to a second cell as part of a handover procedure for a UE. The communication manager 1020 may be configured as or otherwise support a component for receiving a feedback message for the medium access control message based on sending the medium access control message, the feedback message indicating a decoding result of the medium access control message. The communication manager 1020 may be configured as or otherwise support a component for communicating one or more messages associated with the handover procedure based on the decoding result indicated by the feedback message.

[0150] By including or configuring a communication manager 1020 according to examples as described herein, the device 1005 (e.g., a processor controlling or otherwise coupled to the receiver 1010, the transmitter 1015, the communication manager 1020, or a combination thereof) may support techniques for reducing processing, lowering power consumption, and more efficiently utilizing communication resources.

[0151] Figure 11 A block diagram 1100 illustrates a device 1105 that supports feedback messaging for a cell handover command according to one or more aspects of the present disclosure. The device 1105 may be an example of aspects of the device 1005 or network entity 105 as described herein. The device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. The device 1105 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0152] Receiver 1110 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be delivered to other components of device 1105. In some examples, receiver 1110 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1110 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0153] Transmitter 1115 may provide means for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1105. For example, transmitter 1115 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1115 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1115 may support outputting information by transmitting signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1115 and receiver 1110 may be co-located in a transceiver, which may include or be coupled to a modem.

[0154] Device 1105 or its various components may be examples of means for performing various aspects of feedback messaging for a cell handover command as described herein. For example, communications manager 1120 may include a sending component 1125, a receiving component 1130, a feedback analysis component 1135, or any combination thereof. Communications manager 1120 may be an example of various aspects of communications manager 1020 as described herein. In some examples, communications manager 1120 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise coordinating with receiver 1110, transmitter 1115, or both. For example, communications manager 1120 may receive information from receiver 1110, transmit information to transmitter 1115, or be integrated with receiver 1110, transmitter 1115, or both to obtain information, output information, or perform various other operations as described herein.

[0155] According to examples as disclosed herein, the communication manager 1120 can support wireless communications. The sending component 1125 can be configured to function as or otherwise support means for transmitting a medium access control message including a cell handover command via one or more resources of a channel associated with a first cell, the cell handover command indicating a handover from the first cell to the second cell as part of a handover procedure for the UE. The receiving component 1130 can be configured to function as or otherwise support means for receiving a feedback message for the medium access control message based on the sending of the medium access control message, the feedback message indicating a decoding result of the medium access control message. The feedback analysis component 1135 can be configured to function as or otherwise support means for communicating one or more messages associated with the handover procedure based on the decoding result indicated by the feedback message.

[0156] Figure 12 Block diagram 1200 illustrates a communication manager 1220 supporting feedback messaging for a cell handover command, according to one or more aspects of the present disclosure. Communication manager 1220 may be an example of aspects of communication manager 1020, communication manager 1120, or both, as described herein. Communication manager 1220 or its individual components may be examples of means for performing various aspects of feedback messaging for a cell handover command, as described herein. For example, communication manager 1220 may include a sending component 1225, a receiving component 1230, a feedback analysis component 1235, or any combination thereof. Each of these components may communicate with one another directly or indirectly (e.g., via one or more buses), and this communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of the protocol stack (e.g., between protocol layers of the protocol stack, within a device, component, or virtualized component associated with network entity 105, or between devices, components, or virtualized components associated with network entity 105), or any combination thereof.

[0157] According to examples as disclosed herein, the communication manager 1220 can support wireless communications. The sending component 1225 can be configured to function as or otherwise support means for transmitting a medium access control message including a cell handover command via one or more resources of a channel associated with a first cell, the cell handover command indicating a handover from the first cell to the second cell as part of a handover procedure for the UE. The receiving component 1230 can be configured to function as or otherwise support means for receiving a feedback message for the medium access control message based on the sending of the medium access control message, the feedback message indicating a decoding result of the medium access control message. The feedback analysis component 1235 can be configured to function as or otherwise support means for communicating one or more messages associated with the handover procedure based on the decoding result indicated by the feedback message.

[0158] Figure 13 A diagram illustrates a system 1300 including a device 1305 supporting feedback messaging for cell handover commands, according to one or more aspects of the present disclosure. Device 1305 may be an example of, or include components of, device 1005, device 1105, or network entity 105, as described herein. Device 1305 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof. This communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1305 may include components that support outgoing and incoming communications, such as a communications manager 1320, a transceiver 1310, an antenna 1315, memory 1325, code 1330, and a processor 1335. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, or electrically) via one or more buses (e.g., bus 1340).

[0159] The transceiver 1310 may support bidirectional communication via a wired link, a wireless link, or both as described herein. In some examples, the transceiver 1310 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1310 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1305 may include one or more antennas 1315, which may be capable of transmitting or receiving wireless transmissions (e.g., concurrently). The transceiver 1310 may also include a modem to: modulate a signal; provide the modulated signal for transmission (e.g., via one or more antennas 1315, via a wired transmitter); receive the modulated signal (e.g., from one or more antennas 1315, from a wired receiver); and demodulate the signal. In some implementations, the transceiver 1310 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1315 configured to support various receive or obtain operations, or one or more interfaces coupled to one or more antennas 1315 configured to support various transmit or output operations, or a combination thereof. In some implementations, the transceiver 1310 may include or be configured to be coupled to one or more processors or memory components operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other output, or any combination of these operations. In some implementations, the transceiver 1310, or the transceiver 1310 and one or more antennas 1315, or the transceiver 1310 and one or more antennas 1315 and one or more processors or memory components (e.g., processor 1335 or memory 1325 or both) may be included in a chip or chip assembly installed in the device 1305. In some examples, the transceiver may be operable to support communications via one or more communication links (eg, communication link 125 , backhaul communication link 120 , midhaul communication link 162 , fronthaul communication link 168 ).

[0160] Memory 1325 may include RAM and ROM. Memory 1325 may store computer-readable, computer-executable code 1330 including instructions that, when executed by processor 1335, cause device 1305 to perform the various functions described herein. Code 1330 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, code 1330 may not be directly executable by processor 1335, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 1325 may also contain, for example, a BIOS that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0161] The processor 1335 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof). In some cases, the processor 1335 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1335. The processor 1335 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1325) to cause the device 1305 to perform various functions (e.g., functions or tasks supporting the reception and transmission of feedback messages for cell handover commands). For example, the device 1305 or a component of the device 1305 may include the processor 1335 and the memory 1325 coupled to the processor 1335, the processor 1335 and the memory 1325 being configured to perform the various functions described herein. Processor 1335 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software (such as an operating system, virtual machine, or container instance)) that can host functionality for performing the functions of device 1305 (e.g., by executing code 1330). Processor 1335 may be any suitable processor or processors capable of executing scripts or instructions of one or more software programs stored in device 1305 (such as within memory 1325). In some implementations, processor 1335 may be a component of a processing system. A processing system generally refers to a system or series of machines or components that receives inputs and processes those inputs to produce a set of outputs (which may be delivered to, for example, other systems or components of device 1305). For example, a processing system of device 1305 may refer to a system that includes various other components or subcomponents of device 1305 (such as processor 1335, transceiver 1310, communications manager 1320, or other components or combinations of components of device 1305). The processing system of device 1305 can interface with other components of device 1305 and can process information (such as input or signals) received from other components or output information to other components. For example, a chip or modem of device 1305 may include a processing system and one or more interfaces for outputting information, receiving information, or both. The one or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to receive information, or the same interface configured to output information and receive information, and so on. In some implementations, the one or more interfaces may refer to an interface between the processing system of the chip or modem and a transmitter, allowing device 1305 to transmit information output from the chip or modem. Additionally or alternatively, in some implementations, the one or more interfaces may refer to an interface between the processing system of the chip or modem and a receiver, allowing device 1305 to receive information or signal input and pass the information to the processing system.One of ordinary skill in the art will readily recognize that the first interface may also obtain information or signal input, and the second interface may also output information or signal output.

[0162] In some examples, bus 1340 may support communications for protocol layers of a protocol stack (e.g., within a protocol layer). In some examples, bus 1340 may support communications associated with logical channels of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within components of device 1305 or between different components of device 1305 that may be co-located or located in different locations (e.g., where device 1305 may refer to a system in which one or more of communication manager 1320, transceiver 1310, memory 1325, code 1330, and processor 1335 may be located in one component or divided between different components).

[0163] In some examples, communication manager 1320 can manage various aspects of communications with core network 130 (e.g., via one or more wired or wireless backhaul links). For example, communication manager 1320 can manage the delivery of data communications for client devices, such as one or more UEs 115. In some examples, communication manager 1320 can manage communications with other network entities 105 and can include a controller or scheduler for controlling communications with UEs 115 in coordination with other network entities 105. In some examples, communication manager 1320 can support an X2 interface within LTE / LTE-A wireless communication network technology to provide communications between network entities 105.

[0164] According to examples as disclosed herein, the communication manager 1320 may support wireless communications. For example, the communication manager 1320 may be configured as or otherwise support means for sending a medium access control message including a cell handover command via one or more resources of a channel associated with a first cell, the cell handover command indicating a handover from the first cell to a second cell as part of a handover procedure for a UE. The communication manager 1320 may be configured as or otherwise support means for receiving a feedback message for the medium access control message based on sending the medium access control message, the feedback message indicating a decoding result of the medium access control message. The communication manager 1320 may be configured as or otherwise support means for communicating one or more messages associated with the handover procedure based on the decoding result indicated by the feedback message.

[0165] By including or configuring a communication manager 1320 according to the examples described herein, the device 1305 can support techniques for improving communication reliability, reducing latency, improving the user experience associated with reduced processing, lowering power consumption, more efficiently utilizing communication resources, improving coordination between devices, extending battery life, and improving utilization of processing power.

[0166] In some examples, the communication manager 1320 can be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise coordinating with the transceiver 1310, one or more antennas 1315 (e.g., where applicable), or any combination thereof. Although the communication manager 1320 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1320 can be supported or performed by the transceiver 1310, the processor 1335, the memory 1325, the code 1330, or any combination thereof. For example, the code 1330 can include instructions executable by the processor 1335 to cause the device 1305 to perform various aspects of feedback messaging for a cell handover command as described herein, or the processor 1335 and the memory 1325 can be otherwise configured to perform or support such operations.

[0167] Figure 14 A flow chart illustrating a method 1400 for supporting feedback messaging for cell handover commands according to one or more aspects of the present disclosure is illustrated. The operations of the method 1400 may be implemented by a UE or components thereof as described herein. For example, the operations of the method 1400 may be implemented by a UE or components thereof as described herein. Figures 1 to 9 The described functions may be performed by the UE 115. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0168] At 1405, the method may include monitoring one or more resources of a channel associated with the first cell for a medium access control message associated with a handover process of the UE. The operations of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described in reference to Figure 8 The resource monitoring component 825 described is executed.

[0169] At 1410, the method may include decoding a medium access control message based on monitoring the one or more resources, the medium access control message including a cell handover command, the cell handover command indicating a handover from a first cell to a second cell as part of a handover procedure for the UE. The operations of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed as described with reference to Figure 8The decoding component 830 described is performed.

[0170] At 1415, the method may include sending a feedback message for the medium access control message based on decoding the medium access control message, the feedback message indicating a decoding result of decoding the medium access control message. The operations of 1415 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1415 may be performed as described in reference to Figure 8 The sending component 835 is described to perform.

[0171] Figure 15 A flow chart illustrating a method 1500 for supporting feedback messaging for cell handover commands according to one or more aspects of the present disclosure is illustrated. The operations of the method 1500 may be implemented by a UE or components thereof as described herein. For example, the operations of the method 1500 may be implemented by a UE or components thereof as described herein. Figures 1 to 9 The described functions may be performed by the UE 115. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0172] At 1505, the method may include monitoring one or more resources of a channel associated with the first cell for a medium access control message associated with a handover process of the UE. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Figure 8 The resource monitoring component 825 described is executed.

[0173] At 1510, the method may include receiving, based on monitoring, a medium access control message from a first cell via a channel, wherein the channel includes a physical downlink shared channel, wherein a feedback message indicating a decoding result is sent to the first cell via an uplink channel associated with a second cell, the decoding result including an acknowledgement or a negative acknowledgement of decoding the medium access control message. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed by methods as described in reference to Figure 8 The receiving component 840 described is executed.

[0174] At 1515, the method may include decoding a medium access control message based on monitoring the one or more resources, the medium access control message including a cell handover command, the cell handover command indicating a handover from a first cell to a second cell as part of a handover procedure for the UE. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described with reference to Figure 8 The decoding component 830 described is performed.

[0175] At 1520, the method may include sending a feedback message for the medium access control message based on decoding the medium access control message, the feedback message indicating a decoding result of decoding the medium access control message. The operations of 1520 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1520 may be implemented as described in reference to Figure 8 The sending component 835 is described to perform.

[0176] Figure 16 A flow chart illustrating a method 1600 for supporting feedback messaging of a cell handover command according to one or more aspects of the present disclosure is illustrated. The operations of the method 1600 may be implemented by a UE or components thereof as described herein. For example, the operations of the method 1600 may be implemented by a UE or components thereof as described herein. Figures 1 to 9 The described functions may be performed by the UE 115. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0177] At 1605, the method may include monitoring one or more resources of a channel associated with the first cell for a medium access control message associated with a handover procedure of the UE. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Figure 8 The resource monitoring component 825 described is executed.

[0178] At 1610, the method may include receiving a medium access control message based on monitoring the one or more resources, the medium access control message including a cell handover command, the cell handover command indicating a handover from a first cell to a second cell as part of a handover procedure for the UE. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described with reference to Figure 8 The receiving component 840 described is executed.

[0179] At 1615, the method may include initiating a timer associated with a handover process from the first cell to the second cell according to the cell handover command. The operations of 1615 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described in reference to Figure 8 The timing component 845 described is executed.

[0180] At 1620, the method may include communicating one or more messages associated with the handover process based on the status of the timer. The operations of 1620 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1620 may be implemented as described in reference to Figure 8 The timing component 845 described is executed.

[0181] Figure 17 A flow chart illustrating a method 1700 for supporting feedback messaging for cell handover commands according to one or more aspects of the present disclosure is illustrated. The operations of the method 1700 may be implemented by a UE or components thereof as described herein. For example, the operations of the method 1700 may be implemented by a UE or components thereof as described herein. Figures 1 to 9 The described functions may be performed by the UE 115. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0182] At 1705, the method may include monitoring one or more resources of a channel associated with the first cell for a medium access control message associated with a handover procedure of the UE. The operations of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described in reference to Figure 8 The resource monitoring component 825 described is executed.

[0183] At 1710, the method may include receiving a medium access control message based on monitoring the one or more resources, the medium access control message including a cell handover command, the cell handover command indicating a handover from a first cell to a second cell as part of a handover procedure for the UE. The operations of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described with reference to Figure 8 The receiving component 840 described is executed.

[0184] At 1715, the method may include initiating a timer associated with a handover process from the first cell to the second cell according to the cell handover command. The operations of 1715 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1715 may be performed as described in reference to Figure 8 The timing component 845 described is executed.

[0185] At 1720, the method may include communicating one or more messages associated with the handover process based on the status of the timer. The operations of 1720 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1720 may be implemented as described in reference to Figure 8 The timing component 845 described is executed.

[0186] At 1725, the method may include sending a feedback message for the medium access control message based on receiving the medium access control message, wherein a timer associated with the handover process is initiated in response to sending the feedback message. The operations of 1725 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1725 may be performed as described in reference to Figure 8 The sending component 835 is described to perform.

[0187] Figure 18 A flow chart illustrating a method 1800 for supporting feedback messaging of a cell handover command according to one or more aspects of the present disclosure is illustrated. The operations of the method 1800 may be implemented by a network entity or component thereof as described herein. For example, the operations of the method 1800 may be implemented by a network entity or component thereof as described herein. Figures 1 to 5 as well as Figures 10 to 13 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0188] At 1805, the method may include sending a medium access control message including a cell handover command via one or more resources of a channel associated with the first cell, the cell handover command indicating a handover from the first cell to the second cell as part of a handover procedure for the UE. The operations of 1805 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1805 may be performed as described in reference to Figure 12 The sending component 1225 is described to perform.

[0189] At 1810, the method may include receiving a feedback message for the medium access control message based on sending the medium access control message, the feedback message indicating a decoding result of the medium access control message. The operations of 1810 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1810 may be performed by reference to Figure 12 The receiving component 1230 described is executed.

[0190] At 1815, the method may include communicating one or more messages associated with the handover process based on the decoding result indicated by the feedback message. The operations of 1815 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 1815 may be performed as described in reference to Figure 12 The described feedback analysis component 1235 is performed.

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

[0192] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and the terminology of LTE, LTE-A, LTE-A Pro, or NR may be used throughout much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described 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 herein.

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

[0194] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or executed using a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor 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 (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0195] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functions may be stored as one or more instructions or codes of a computer-readable medium, or sent using one or more instructions or codes of a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these. Features that implement the functions may also be physically located at different locations, including being distributed so that the various parts of the functions are implemented at different physical locations.

[0196] Computer-readable media includes both non-transitory computer storage media and communication media, including any media that facilitates the transfer of computer programs from one location 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 can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory media that can be used to carry or store desired program code components in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. In addition, any connection is appropriately referred to as a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwaves, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwaves are included within the definition of computer-readable media. As used herein, disk and disc include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs. Disks can reproduce data magnetically, while discs can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0197] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so 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 (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of this disclosure. 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."

[0198] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, searching (such as by searching in a table, database, or other data structure), ascertaining, and the like. Additionally, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), and the like. Additionally, "determining" may include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

[0199] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between similar components. If only the first reference label is used in the specification, the description applies to any of the similar components having the same first reference label, regardless of the second or subsequent reference labels.

[0200] The description set forth herein in conjunction with the accompanying drawings describes example configurations and does not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," rather than "preferred" or "having advantages over other examples." The detailed description includes specific details to provide an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

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

Claims

1. A device for wireless communication, the device comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: monitoring one or more resources of a channel associated with the first cell for a medium access control message associated with a handover procedure of the apparatus; decoding the medium access control message based at least in part on monitoring the one or more resources, the medium access control message comprising a cell handover command indicating a handover from the first cell to a second cell as part of the handover procedure of the apparatus; as well as A feedback message for the medium access control message is sent based at least in part on the decoding of the medium access control message, the feedback message indicating a decoding result of the decoding of the medium access control message.

2. The apparatus of claim 1 , wherein the instructions for sending the feedback message are executable by the processor to cause the apparatus to: An indication of a result of decoding the cell handover command is sent in the feedback message.

3. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: Based at least in part on the monitoring, the medium access control message is received from the first cell via the channel, wherein the channel comprises a physical downlink shared channel, wherein the feedback message indicating the decoding result is sent to the first cell and via an uplink channel associated with the second cell, the decoding result comprising an acknowledgment or a negative acknowledgment of the decoding of the medium access control message. 4 . The apparatus of claim 3 , wherein the uplink channel associated with the first cell is a physical uplink control channel or a physical uplink shared channel, and the feedback message is uplink control information.

5. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: Based at least in part on the monitoring, the medium access control message is received from the first cell via the channel, wherein the channel comprises a physical downlink shared channel, wherein the feedback message indicating the decoding result comprising an acknowledgment or a negative acknowledgment of the decoding of the medium access control message is sent to the second cell via an uplink channel associated with the first cell.

6. The apparatus according to claim 5, wherein the uplink channel associated with the second cell is a physical uplink control channel, a dedicated physical uplink control channel for scheduling request, or a physical uplink shared channel, and the feedback message is uplink control information.

7. The apparatus of claim 1 , wherein the instructions for sending the feedback message are executable by the processor to cause the apparatus to: Based at least in part on the decoding, the feedback message is sent using uplink resources indicated by the medium access control message.

8. The apparatus of claim 1 , wherein the instructions for sending the feedback message are executable by the processor to cause the apparatus to: Based at least in part on the decoding, the feedback message is sent according to a time offset indicated by the medium access control message.

9. The apparatus of claim 1 , wherein the instructions for sending the feedback message are executable by the processor to cause the apparatus to: The feedback message is sent after a time delay associated with feedback for a medium access control cell handover command.

10. The apparatus of claim 1 , wherein the instructions for sending the feedback message are executable by the processor to cause the apparatus to: The feedback message is sent to the first cell via a medium access control element dedicated for feedback on the cell handover command indicated by the medium access control message.

11. The apparatus of claim 1 , wherein the instructions for sending the feedback message are executable by the processor to cause the apparatus to: The feedback message is sent to the second cell via a medium access control element dedicated for feedback on the cell handover command indicated by the medium access control message.

12. An apparatus for wireless communication, the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: monitoring one or more resources of a channel associated with the first cell for a medium access control message associated with a handover procedure of the apparatus; receiving the medium access control message based at least in part on monitoring the one or more resources, the medium access control message comprising a cell handover command indicating a handover from the first cell to a second cell as part of the handover procedure of the apparatus; Initiating a timer associated with the handover process from the first cell to the second cell according to the cell handover command; as well as One or more messages associated with the handover process are communicated based at least in part on a status of the timer.

13. The apparatus of claim 12, wherein the instructions for initiating the timer are executable by the processor to cause the apparatus to: The timer associated with the handover process is initiated in response to receiving the medium access control message.

14. The apparatus of claim 12, wherein the instructions for communicating the one or more messages associated with the handover process are executable by the processor to cause the apparatus to: A feedback message for the medium access control message is sent based at least in part on receiving the medium access control message, wherein the timer associated with the handover process is initiated in response to sending the feedback message.

15. The apparatus of claim 12, wherein the instructions for communicating the one or more messages associated with the handover process are executable by the processor to cause the apparatus to: Downlink control information scheduling a transport block for a hybrid automatic repeat request identifier is received via a data channel associated with the second cell.

16. The apparatus of claim 15 , wherein the downlink control information further comprises a new data allocation indicator associated with the transport block, and the instructions are further executable by the processor to cause the apparatus to: The timer is stopped based at least in part on receiving the downlink control information including the new data allocation indicator associated with the transport block.

17. The apparatus of claim 15, wherein the instructions are further executable by the processor to cause the apparatus to: sending, to the second cell, an acknowledgment message associated with receiving the downlink control information scheduling the transport block; and The timer is stopped based at least in part on sending the confirmation message.

18. The apparatus of claim 15, wherein the data channel is a physical uplink shared channel or a physical downlink shared channel.

19. The apparatus of claim 12, wherein the instructions for communicating the one or more messages associated with the handover process are executable by the processor to cause the apparatus to: A handover failure message is sent indicating that the handover process from the first cell to the second cell failed based at least in part on the expiration of the timer.

20. An apparatus for wireless communication, the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: sending a medium access control message including a cell handover command via one or more resources of a channel associated with a first cell, the cell handover command instructing handover from the first cell to a second cell as part of a handover procedure for a user equipment (UE); receiving a feedback message for the medium access control message based at least in part on sending the medium access control message, the feedback message indicating a result of decoding the medium access control message; as well as One or more messages associated with the handover process are communicated according to the decoding result indicated by the feedback message.

Images