Control message transmission for multi-beam communication

Abstract

Some aspects include apparatus, methods, and computer program products for facilitating control messaging for multi-beam communications in 5G wireless communications systems. A node of a 5G network can generate a medium access control control element (MAC CE) to update a user equipment (UE) using different component carrier (CC) settings. The MAC CE can update a CC list to reduce messaging overhead and latency. For example, the MAC CE can indicate an update of transmission configuration indication (TCI) states for a CC list. Similarly, the MAC CE can be used to update a spatial relation for a sounding reference signal (SRS) resource set and / or SRS resources corresponding to the CC list. The MAC CE can also be used to update multiple TCI codepoints with one or two TCI states in a multi-transmission reception point (multi-TRP) scenario.

Description

BACKGROUND

[0001] Various aspects can generally relate to the field of wireless communication. SUMMARY

[0002] Some aspects of the disclosure include apparatuses and methods for facilitating control messaging for multi-beam communications.

[0003] In some aspects, a method for updating transmission configuration indication (TCI) states of a plurality of component carriers (CCs) can include identifying an update to a TCI state corresponding to a CC of a user equipment (UE), where the CC has a serving cell ID. The method can include determining, based on the update to the TCI state, that a list of CCs including the CC is to be updated, and generating a medium access control control element (MAC CE) including the serving cell ID and a bit value indicating that the UE is to update TCI states of CCs in the list of CCs using the serving cell ID. The method can include transmitting the MAC CE to the UE. In some aspects, the method for updating TCI states of a plurality of CCs can be implemented using a wireless communication system and / or network access node including a transceiver and at least one processor coupled to the transceiver. The at least one processor can be configured to perform elements of the method. The transceiver can communicate with the UE. In some aspects, a non-transitory computer- readable device can store instructions that, when executed by at least one computing device, cause the at least one computing device to perform elements of the method.

[0004] In some aspects, the method can further include transmitting a radio resource control (RRC) message to the UE to configure the list of CCs.

[0005] In some aspects, the method can further include the bit value indicating using a reserved bit of the MAC CE.

[0006] In some aspects, the method can further include the MAC CE including TCI state information to update a TCI state of a physical downlink shared channel (PDSCH).

[0007] In some aspects, the method can further include CORESET information to update a TCI state of a physical downlink control channel (PDCCH).

[0008] In some aspects, the method can further include the bit value being a most significant bit (MSB) or a least significant bit (LSB) of a TCI state ID.

[0009] In some aspects, the method can further include the bit value modifying a TCI codepoint having a plurality of TCI states.

[0010] In some aspects, a method for updating a spatial relation of a sounding reference signal (SRS) of a plurality of component carriers (CCs) can include identifying an update of a spatial relation of a set of SRS resources corresponding to a CC. The method can include determining that a periodicity of the set of SRS resources is aperiodic or periodic. The method can include generating a medium access control element (MAC CE) including a bit value in an activation / deactivation bit field indicating a user equipment (UE) to update a spatial relation of a CC in a list of CCs including the CC. The method can include transmitting the MAC CE to the UE. In some aspects, the method for updating a spatial relation of a SRS of a plurality of CCs can be implemented using a wireless communication system and / or network access node including a transceiver and at least one processor coupled to the transceiver. The at least one processor can be configured to perform elements of the method. The transceiver can communicate with the UE. In some aspects, a non-transitory computer- readable device can store instructions that, when executed by at least one computing device, cause the at least one computing device to perform elements of the method.

[0011] In some aspects, the method can further include resources in the set of SRS resources having a same time domain pattern.

[0012] In some aspects, the method can further include identifying a second update of the spatial relation of the set of SRS resources corresponding to the CC. The method can further include determining that a time domain pattern of the set of SRS resources corresponding to the second update is semi-persistent. The method can further include generating a second MAC CE including a bit value in a reserved bit field indicating the UE to update the spatial relation of the CC according to the second update and transmitting the second MAC CE to the UE.

[0013] In some aspects, the bit value in the reserved bit field indicates the UE to update the spatial relation of a CC in a list of CCs including the CC.

[0014] In some aspects, the method can further include identifying a second update of a spatial relation of an SRS resource corresponding to the CC, where the CC has an SRS resource cell ID. The method can further include determining, based on the update of the spatial relation, to update a list of CCs including the CC. The method can further include generating a second MAC CE including the SRS resource cell ID and a bit value indicating the UE to update a spatial relation of a CC in the list of CCs using the SRS resource cell ID and transmitting the second MAC CE to the UE.

[0015] In some aspects, the method can further include a length of the second MAC CE being four octets.

[0016] In some aspects, a method for configuring transmission configuration indication (TCI) codepoints for a physical downlink shared channel (PDSCH) can include identifying a configuration of one or more TCI codepoints corresponding to a component carrier (CC) for a user equipment (UE). The method can further include determining that at least one TCI codepoint of the one or more TCI codepoints has multiple TCI states. The method can further include generating a medium access control control element (MAC CE) including a first value indicating a quantity of the one or more TCI codepoints and a second value indicating a quantity of the at least one TCI codepoint of the one or more TCI codepoints that has multiple TCI states. For the at least one TCI codepoint of the one or more TCI codepoints that has multiple TCI states, the method can further include updating the MAC CE to include a bit indicating that there are multiple TCI states. The method can further include transmitting the MAC CE to the UE. In some aspects, the method for configuring the TCI codepoints for the PDSCH can be implemented using a wireless communication system and / or network access node including a transceiver and at least one processor coupled to the transceiver. The at least one processor can be configured to perform elements of the method. The transceiver can communicate with the UE. In some aspects, a non-transitory computer- readable device can store instructions that, when executed by at least one computing device, cause the at least one computing device to perform elements of the method.

[0017] In some aspects, the method can further include the MAC CE including: first octet data including the bit indicating that there are multiple TCI states and a first TCI state ID; and second octet data including a second TCI state ID.

[0018] In some aspects, the method can further include the second octet data including a reserved bit.

[0019] In some aspects, the method can further include the bit indicating to the UE that 8 bits of data following the first TCI state are related to a second TCI state.

[0020] In some aspects, the method can further include updating the MAC CE to include a second bit indicating that a TCI codepoint of the one or more TCI codepoints has a single TCI state.

[0021] In some aspects, the method can further include the second bit indicating to the UE that 7 bits of data following are related to the single TCI state.

[0022] In some aspects, the method can further include the 7 bits of data following including a TCI state ID corresponding to the TCI codepoint.

[0023] In some aspects, a method for updating transmission configuration indication (TCI) states of a plurality of component carriers (CCs) at a user equipment (UE) can include receiving, from a wireless access node, a radio resource control (RRC) message indicating the UE is configured a list of component carriers (CCs). The method can include receiving, from the wireless access node, a medium access control control element (MAC CE) including a serving cell ID corresponding to a component carrier (CC) in the list and a bit value indicating the UE is to update a transmission configuration indicator (TCI) state of the CC list. In response to identifying the bit value, the method can include identifying the CC list using the serving cell ID and updating the TCI state of the CC in the CC list. In some aspects, the method for updating TCI states of a plurality of CCs can be implemented by a UE including a transceiver and at least one processor coupled to the transceiver. The at least one processor can be configured to perform elements of the method. The transceiver can communicate with the wireless access node. In some aspects, a non-transitory computer- readable device can store instructions that, when executed by at least one computing device, cause the at least one computing device to perform elements of the method.

[0024] In some aspects, the method can further include the bit value indicating using a reserved bit of the MAC CE.

[0025] In some aspects, the method can further include the MAC CE including TCI state information to update a TCI state of a physical downlink shared channel (PDSCH).

[0026] In some aspects, the method can further include CORESET information to update a TCI state of a physical downlink control channel (PDCCH).

[0027] In some aspects, the method can further include the bit value being a most significant bit (MSB) or a least significant bit (LSB) of a TCI state ID.

[0028] In some aspects, the method can further include the bit value modifying a TCI codepoint having a plurality of TCI states. BRIEF DESCRIPTION OF DRAWINGS

[0029] Figure 1 An example system implementing control message transmission for multi-beam communications is shown in accordance with some aspects.

[0030] Figure 2 A block diagram of an example wireless system of an electronic device implementing control message transmission for multi-beam communications is shown in accordance with some aspects.

[0031] Figure 3AA block diagram illustrating a medium access control control element (MAC CE) for updating transmission configuration indication (TCI) states for a physical downlink shared channel (PDSCH), in accordance with some aspects, is shown.

[0032] Figure 3B A block diagram illustrating a MAC CE for updating transmission configuration indication (TCI) states for a physical downlink control channel (PDCCH), in accordance with some aspects, is shown.

[0033] Figure 4 A block diagram illustrating a MAC CE for activating and deactivating a sounding reference signal (SRS) resource set, in accordance with some aspects, is shown.

[0034] Figure 5 A block diagram illustrating a MAC CE for updating a spatial relation for a sounding reference signal (SRS) resource, in accordance with some aspects, is shown.

[0035] Figure 6A A block diagram illustrating a MAC CE for configuring TCI codepoints for a PDSCH to support multi-transmission reception point (multi-TRP) operation, in accordance with some aspects, is shown.

[0036] Figure 6B A block diagram illustrating an example MAC CE indicating multiple TCI states, in accordance with some aspects, is shown.

[0037] Figure 7 A flow diagram illustrating a MAC CE for updating TCI states for a component carrier (CC) list of a user equipment (UE), in accordance with some aspects, is shown.

[0038] Figure 8A A flow diagram illustrating a MAC CE for generating to update spatial relations for SRS resource sets with different periodicities, in accordance with some aspects, is shown.

[0039] Figure 8B A flow diagram illustrating a MAC CE for modifying to update spatial relations for a CC list, in accordance with some aspects, is shown.

[0040] Figure 8C A flow diagram illustrating a MAC CE for generating to update spatial relations for SRS resources, in accordance with some aspects, is shown.

[0041] Figure 9 A flow diagram illustrating a MAC CE for configuring TCI codepoints for a PDSCH to support multi-transmission reception point (multi-TRP) operation, in accordance with some aspects, is shown.

[0042] Figure 10 An example computer system that can be used for implementing various aspects is shown.

[0043] The features and advantages of the aspects will become more apparent from the detailed description set forth below when taken in conjunction with the drawings, in which like reference characters identify corresponding elements throughout the several views. In the drawings, like reference numbers generally indicate identical, functionally similar, and / or structurally similar elements. The drawing in which an element first appears is indicated by the leftmost digit(s) in the corresponding reference number. DETAILED DESCRIPTION

[0044] The following detailed description relates to the drawings. Like reference numerals are generally employed there throughout, indicating corresponding or similar elements. In the following description, for the purposes of explanation, specific details are set forth in order to provide a thorough understanding of aspects of the various aspects. However, it will be apparent to one skilled in the art that aspects of the various aspects can practice without these specific details. In some instances, well-known devices, circuits, and methodologies have not been described in detail in order to avoid obscuring aspects of the various aspects. As used in this document, the phrase “A or B” means (A), (B), or (A and B).

[0045] The present disclosure relates to communications between a node and a user equipment (UE) using 5G wireless communication protocols. For example, the node can be a gNB or ng-eNB node. As part of the development of the 5G standard, the 3rd Generation Partnership Project (3GPP) has published several documents detailing meeting notes and development. One such document is referred to as Release 16 (Rel-16).

[0046] Rel-16 provides some description of multi-beam and multiple-input multiple-output (MIMO) communications between a node and a UE. These communications can use multiple transmit antennas and receive antennas to exploit multipath propagation. One concept that describes these multi-beam communication relationships is “quasi co-location” or QCL. QCL refers to a detected relationship between multiple signals received from an antenna array of a transmission. Specifically, two antenna ports can be quasi co-located if properties of a channel that conveys symbols on one antenna port can be inferred from a channel that conveys symbols on the other antenna port.

[0047] To provide an example of this QCL, an example showing that signal A is quasi co-located with another signal B will be described. For example, a node can transmit signal A and signal B to a UE using an antenna array or from a common transmission / reception point (TRP) of the node. These signals can be reference signals. The same spatial filter can have been applied to the signals. When the signals propagate from the node to the UE, the signals can also propagate through similar channel conditions and experience similar channel properties. Since signal A and signal B experience similar channel properties, when received at the UE, the UE can detect the channel properties experienced by signal A and then detect signal B. Channel properties can include, for example, Doppler shift, Doppler spread, average delay, delay spread, and / or other channel effects. In view of these issues, if the UE can detect one of the signals and determine the channel properties, this information can help detect the other signal. When the UE is able to perform this detection, signal A and signal B are referred to as quasi co-located (QCL).

[0048] To help the UE identify QCL signals, transmission configuration indicator (TCI) state information can be transmitted from the node to the UE. The TCI state includes information such as QCL relationships between different reference signals and / or downlink reference signals. For example, the TCI state can be transmitted in a downlink control information (DCI) message that describes the QCL relationships of a channel state information reference signal (CSI-RS) and / or a demodulation reference signal (DMRS) set. The TCI state information can include parameters for the UE to configure the QCL relationships between downlink reference signals for a physical downlink shared channel (PDSCH) and / or a physical downlink control channel (PDCCH).

[0049] While this TCI state information can help provide more reliable communication between the node and the UE, some issues can arise when providing this information to the UE. For example, the TCI state can change and the node can need to update the TCI state information at the UE. Similarly, the UE can need to update the TCI state information initially when communicating with the node. Changes to the TCI state information can apply to many different signals or reference signals and / or many different frequency blocks or component carriers (CCs). This updating is more complex in cases where multiple transmission / reception points (TRPs) or multiple nodes are communicating with a particular UE. This situation can introduce overhead and latency issues from the node sending many messages to the UE to update the TCI state and / or spatial relationships for different reference signals and CCs.

[0050] In view of these issues, aspects described herein reduce the amount of control messaging for updating TCI states to reduce messaging overhead and latency. In particular, these aspects describe using medium access control control elements (MAC CEs) to update TCI states for a CC list. This update can also apply to multi-TRP scenarios. The MAC CEs also allow for updating spatial relation information for sounding reference signal (SRS) resources and / or different SRS resource sets with different periodicity and / or time-domain patterns. Further, the MAC CEs can be used to configure a TCI codepoint with multiple TCI states. Using these MAC CE designs, the number of messages and / or MAC CEs can be reduced to provide more efficient TCI state updates and / or reduce latency.

[0051] Various aspects of these features will now be discussed with respect to corresponding drawings.

[0052] Figure 1 An example system 100 implementing control messaging for multi-beam communications according to some aspects is shown. Figure 1 An example system architecture 100 of a network is shown in accordance with various aspects. The following description is provided for an example system 100 operating in conjunction with LTE system standards and 5G or NR system standards provided by 3GPP Technical Specifications. However, the example aspects are not limited in this regard and the described aspects can apply to other networks that benefit from the teachings described herein, such as future 3GPP systems (e.g., Sixth Generation (6G)) systems, IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), and the like.

[0053] As Figure 1 shown, the system 100 includes UE 110A and UE 110B (collectively referred to as “UEs 110” or “UE 110”). In this example, multiple UEs 110 are shown as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but can also include any mobile or non-mobile computing device, such as consumer electronics devices, mobile phones, smartphones, feature phones, tablet computers, wearable computer devices, Personal Digital Assistants (PDAs), pagers, wireless handsets, desktop computers, laptop computers, in-vehicle infotainment (IVI), in-car entertainment (ICE) devices, instrument cluster (IC), head-up display (HUD) devices, onboard diagnostic (OBD) devices, dashtop mobile equipment (DME), mobile data terminals (MDTs), Electronic Engine Management System (EEMS), electronic / engine control units (ECUs), electronic / engine control modules (ECMs), embedded systems, microcontrollers, control modules, engine management system (EMS), networked or “smart” appliances, MTC devices, M2M, IoT devices, and the like.

[0054] The UEs 110 can be configured to connect with and / or communicate directly with a Radio Access Network (RAN) including RAN nodes 120A, 120B, for example, communicatively coupled. In aspects, the RAN can be an NG RAN or a 5G RAN, an E-UTRAN, or a legacy RAN such as a UTRAN or GERAN. As used herein, the term “NG RAN” or “Next Generation RAN” and the like can refer to a RAN that operates in an NR or 5G system 100, while the term “E-UTRAN” and the like can refer to a RAN that operates in an LTE or 4G system 100. The UEs 110 can utilize connections (or channels) including a physical communications interface or layer (discussed in further detail below), each of which can comprise a logical and / or a physical connection. The UEs 110 may, in some cases, communicate with one or more RAN nodes 120.

[0055] In this example, the connection is illustrated as an air interface to implement underlaying wireless communications, and can be consistent with cellular communications protocols, such as a GSM protocol, a CDMA network protocol, a PTT protocol, a POC protocol, a UMTS protocol, a 3GPP LTE protocol, a 5G protocol, a NR protocol, and / or any other communication protocol discussed herein. In aspects, UEs 110 can directly exchange communication data via a ProSe interface. The ProSe interface can alternatively be referred to as a SL interface, and can include one or more logical channels, including but not limited to, a PSCCH, a PSSCH, a PSDCH, and a PSBCH.

[0056] The UE 110A can be configured to access an Access Point (AP) (also referred to as “WLAN node,” “WLAN,” “WLAN terminal,” “WT,” etc.). The connection can include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, in which the AP would include a wireless fidelity The UE 110A can be configured to access an Access Point (AP) (also referred to as “WLAN node,” “WLAN,” “WLAN terminal,” “WT,” etc.). The connection can include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, in which the AP would include a wireless fidelity

[0057] The RAN can include one or more ANs or RAN nodes 120A and 120B (collectively referred to as“a plurality of RAN nodes 120” or“RAN nodes 120”). As used herein, the terms“access node,”“access point,”“AN,”“RAN node,” and the like can describe equipment

[0058] In some aspects, all or a portion of RAN nodes 120 can be implemented as one or more software entities running on server computers as part of a virtual network, which can be referred to as a CRAN and / or a virtual baseband unit pool (vBBUP). In these aspects, the CRAN or vBBUP can implement a RAN function split, such as a PDCP split wherein RRC and PDCP layers are operated by the CRAN / vBBUP and other L2 protocol entities are operated by individual RAN nodes 120; a MAC / PHY split wherein RRC, PDCP, RLC, and MAC layers are operated by the CRAN / vBBUP and the PHY layer is operated by individual RAN nodes 120; or a “lower PHY” split wherein RRC, PDCP, RLC, MAC layers, and an upper part of the PHY layer are operated by the CRAN / vBBUP and a lower part of the PHY layer is operated by individual RAN nodes 120. This virtualized framework allows the freed-up processor cores of RAN nodes 120 to perform other virtualized applications. In some implementations, individual RAN nodes 120 can represent a CU, and / or a distributed unit (DU), that Figure 1(not shown) connected to the gNB-CU. In these implementations the gNB-DU can include one or more remote radio head or RFEMs and the gNB-CU can be operated by a server (not shown) located in the RAN or by a pool of servers in a similar manner as a CRAN / vBBUP. Additionally or alternatively one or more RAN nodes 120 can be a next generation eNB (ng-eNB), which is a RAN node that provides E-UTRA user plane and control plane protocol terminations and that is connected to a 5GC via an NG interface (discussed infra) for UEs 110.

[0059] In V2X scenarios one or more of the RAN nodes 120 can be or act as RSUs. The term“Road Side Unit” or“RSU” can refer to any transportation infrastructure entity used for V2X communication. An RSU can be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, where an RSU implemented in or by a UE can be referred to as“UE-type RSU,” an RSU implemented in or by an eNB can be referred to as an“eNB-type RSU,” an RSU implemented in or by a gNB can be referred to as a“gNB-type RSU,” and the like. In one example, an RSU is a computing device coupled with radio frequency circuitry located on a road side that provides connectivity support to passing vehicle UEs 110 (vUEs 110). The RSU can also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicle and pedestrian traffic. The RSU can operate on 5.9 GHz Direct Short Range Communications (DSRC) band to provide extremely low latency communications required for high speed events such as crash avoidance, traffic warnings, etc. Additionally or alternatively, the RSU can operate on the cellular V2X frequency band to provide the

[0060] Any of the RAN nodes 120 can terminate the air interface protocol and can be the first point of contact for a UE 110. In some aspects, any of the RAN nodes 120 can fulfill various logical functions for the RAN, including but not limited to radio network control (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0061] In aspects, UEs 110 can be configured to communicate using OFDM communication signals with each other or with any of the RAN nodes 120 over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, OFDMA communication techniques (e.g., for downlink communications) or SC-FDMA communication techniques (e.g., for uplink and ProSe or sidelink communications), although the scope of the aspects is not limited in this respect. The OFDM signals can comprise a plurality of orthogonal subcarriers.

[0062] In some aspects, a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 120 to the UEs 110, while uplink transmissions can utilize a similar approach. The grid can be a time-frequency grid, called a resource grid or time-frequency resource grid, which is the physical resource in the downlink in each slot. For an OFDM system, such a time-frequency plane representation is a common practice as it makes it easy to describe and implement the various physical channels in the downlink. The resource grid is only in the time domain for an SC-FDMA system. In the time domain, the resource grid can consist of multiple consecutive subframes, where a subframe is 1 ms in duration and consists of two consecutive slots. In the frequency domain, the resource grid can consist of multiple contiguous subcarriers, given the bandwidth of the air interface and the number of subcarriers that is used for transmission. Each resource grid consists of a number of physical resource blocks (PRBs), where each PRB can correspond to one slot (5 ms) in the time domain and 12 subcarriers in the frequency domain. In the downlink, each UE 110 can be configured with one or more resource blocks. The resource grids can be used by some physical channels, such as the physical downlink shared channel (PDSCH) and physical uplink shared channel (PUSCH).

[0063] According to various aspects, UEs 110 and RAN nodes 120 transmit data (e.g., transmit data and receive data) over a licensed medium (also referred to as “licensed spectrum” and / or “licensed bands”) and an unlicensed shared medium (also referred to as “unlicensed spectrum” and / or “unlicensed bands”). The licensed spectrum can include channels that operate in the frequency range of approximately 400 MHz to approximately 3.8 GHz, while the unlicensed spectrum can include the 5 GHz band.

[0064] To operate in the unlicensed spectrum, the UEs 110 and the RAN nodes 120 can operate using LAA, eLAA, and / or feLAA mechanisms. In these implementations, the UEs 110 and the RAN nodes 120 can perform one or more known clear channel assessment (CCA) check procedures to determine whether one or more channels in the unlicensed spectrum is unavailable for use or otherwise occupied before transmitting in the unlicensed spectrum. The CCA check procedures can be performed according to Listen Before Talk (LBT) procedures.

[0065] LBT is a mechanism by which equipment (e.g., UEs 110, RAN nodes 120, etc.) senses a medium (e.g., a channel or carrier frequency) and transmits when the medium is sensed to be idle (or when a specific channel in the medium is sensed to be unoccupied). The medium sensing operation can include a CCA, which utilizes at least ED to determine the presence or absence of other signals on a channel to determine if the channel is occupied or clear. This LBT mechanism allows cellular / LAA networks to coexist with incumbent systems in the unlicensed spectrum, as well as with other LAA networks. The ED can include sensing RF energy present over a period of time and a predefined or configured threshold value that the sensed RF energy is compared to.

[0066] Generally, incumbent systems in the 5 GHz band are WLANs based on IEEE 802.11 technology. The WLANs employ a contention-based channel access mechanism, known as CSMA / CA. Here, when a WLAN node (e.g., mobile station (MS), such as a UE 110, an AP, etc.) intends to transmit, the WLAN node can first perform a CCA prior to the transmission. Additionally, in cases where more than one WLAN node senses the channel to be idle and transmits at the same time, a backoff mechanism is used to avoid collisions. The backoff mechanism can be a counter that is randomly introduced within the CWS, which is increased exponentially upon a collision and reset to a minimum value upon a successful transmission. The LBT mechanism designed for LAA is somewhat similar to the CSMA / CA of WLANs. In some implementations, the LBT procedure for a DL or UL transmission burst (comprising PDSCH or PUSCH transmissions) can have a variable length LAA contention window between X and Y ECCA slots, where X and Y are the minimum and maximum values of the CWS for LAA. In one example, the minimum CWS for LAA transmissions can be 9 microseconds (ps); however, the size of the CWS and the MCOT (e.g., transmission burst) can be based on government regulatory requirements.

[0067] The LAA mechanisms build on the CA techniques of the LTE-Advanced system. In CA, each aggregated carrier is known as a CC. A CC can have a bandwidth of 1.4, 3, 5, 10, 15, or 20 MHz, and up to five CCs can be aggregated, resulting in a maximum aggregated bandwidth of 100 MHz. In FDD systems, the number of aggregated carriers can be different for DL and UL, with the number of UL CCs being equal to or lower than the number of DL component carriers. In some cases, individual CCs can have a different bandwidth than other CCs. In TDD systems, the number of CCs and the bandwidth of each CC is normally the same for DL and UL.

[0068] CA also contains individual serving cells to provide individual CCs. The coverage of the serving cells can differ, for example, because CCs on different frequency bands will experience different pathloss. A primary serving cell or PCell provides the PCC for both UL and DL, and can handle RRC and NAS related activities. Other serving cells are referred to as SCells, and each can provide individual SCCs for both UL and DL. SCCs can be added and removed as required, while changing the PCC can require the UE 110 to undergo a handover. In LAA, eLAA, and feLAA, some or all of the SCells can operate in unlicensed spectrum (referred to as “LAA SCells”), and are assisted by a PCell operating in licensed spectrum. When a UE is configured with more than one LAA SCell, the UE can receive a UL grant on a configured LAA SCell indicating different PUSCH starting positions within the same subframe.

[0069] The PDSCH carries user data and higher-layer signaling to the various UEs 110. Among other things, the PDCCH carries information about the transport format and resource allocations related to the PDSCH channel. It can also convey information about the transport format, resource allocation, and HARQ information related to the uplink shared channel to the various UEs 110. In general, downlink scheduling (assigning control and shared channel resource blocks to the UE 110As within a cell) can be performed at any of the RAN nodes 120 based on channel quality information fed back from any of the UEs 110. The downlink resource assignment information can be sent to a UE 110 on the PDCCH.

[0070] The PDCCH uses CCEs to deliver control information. Before being mapped to resource elements, the PDCCH complex-valued symbols can first be organized into quadruplets, which can then be permuted using a sub-block interleaver to achieve rate matching. One or more of these CCEs can be used to transmit each PDCCH, where the number of CCEs used can be dependent on the length of the DCI and the channel condition. Four or more different PDCCH formats can be defined in LTE, which can have different numbers of CCEs (e.g., aggregation level, L=1, 2, 4, or 8) and can use one or more of these CCEs to transmit the PDCCH.

[0071] Some aspects can use concepts for resource allocation for control channel information that are an extension of the above-described concepts. For example, some aspects can utilize an EPDCCH that uses PDSCH resources for control information transmission. The EPDCCH can be transmitted using one or more ECCEs. Similar to above, each ECCE can correspond to nine sets of four physical resource elements known as an EREG. In some cases, an ECCE can have other numbers of EREGs.

[0072] The RAN nodes 120 can be configured to communicate with one another via an interface. In aspects where the system 100 is an LTE system (e.g., when the core network (CN) 140 is an EPC), the interface can be an X2 interface. The X2 interface can be defined between two or more RAN nodes 120 that connect to the EPC, such as two or more eNBs and / or between two eNBs connected to the EPC. In some implementations, the X2 interface can include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). The X2-U can provide flow control mechanisms for user data packets transferred over the X2 interface, and can be used to communicate information about the delivery of user data between eNBs. For example, the X2-U can provide specific sequence number information for user data transmitted from a MeNB to an SeNB; information about successful in-sequence delivery of PDCP PDUs to a UE 110 from the SeNB for user data; information for PDCP PDUs that were not delivered to the UE 110; information about a current minimum desired buffer size at the SeNB for transmitting user data to the UE; and the like. The X2-C can provide intra-LTE access mobility functions, including context transfer from a source eNB to a target eNB, user plane transport control, and the like; load management functions; and inter-cell interference coordination functions.

[0073] In aspects where the system 100 is a 5G or NR system (e.g., when the CN 140 is a 5GC), the interface can be an Xn interface. The Xn interface is defined between two or more RAN nodes 120 (e.g., two or more gNBs, etc.) connected to a 5GC, between a RAN node 120 (e.g., gNB) and an eNB connected to 5GC, and / or between two eNBs connected to 5GC. In some implementations, the Xn interface can include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U can provide non-guaranteed delivery of user plane PDUs and support / provide data forwarding and traffic control functionality. The Xn-C can provide management and error handling functionality, functionality to manage the Xn-C interface; mobility support for UE 110 in a connected mode (e.g., CM-CONNECTED) including functionality to manage the connected mode mobility of a UE 110 between one or more RAN nodes 120. The mobility support can include context transfer from an old (source) serving RAN node 120 to new (target) serving RAN node 120; and control of user plane tunnels between an old (source) serving RAN node 120 to new (target) serving RAN node 120. A protocol stack of the Xn-U can include a transport network layer built on Internet Protocol (IP) transport layer, and a GTP-U layer on top of UDP and / or IP layers to carry user plane PDUs. The Xn-C protocol stack can include an application layer signaling protocol (called Xn Application Protocol (Xn-AP)) and a transport network layer built on SCTP. The SCTP can be on top of IP layer, and can provide guaranteed delivery of application layer messages. In the transport IP layer, point-to-point transmission is used to deliver the signaling PDUs. In other implementations, the Xn-U protocol stack and / or the Xn-C protocol stack can be the same as or similar to the user plane and / or control plane protocol stacks shown and described herein.

[0074] The RAN is shown to include base stations 1 10a, 1 10b, and 1 10c, which provide wireless access to the core network 140 for one or more mobile stations 120a, 120b, and 120c. Wireless access can be provided according to one or more radio technologies, such as GSM, CDMA2000, NR, LTE, 5G, or others. The base stations 1 10a, 1 10b, and 1 10c utilize a spectrum that can include a low- frequency spectrum, high-frequency spectrum, C-band, X-band, K-band, millimeter wave (mmWave) spectrum, or the like. In some aspects, wireless communications can be conducted using a hybrid frequency / time / doppler / space modulation scheme. Base stations 1 10a, 1 10b, and 1 10c can each comprise a base transceiver station, a cell, a gNB, a next generation NodeB (gNB), a radio base station, a radio transceiver, a New Radio (NR) NodeB (gNB), a NodeB, a femto cell, a pico cell, a home eNodeB, a home gNodeB, a relay, or the like. In some aspects, the base stations 1 10a, 1 10b, and 1 10c can be implemented as a virtual base station functionally similar to a gNB, implemented in software executed by one or more physical computing devices.

[0075] Generally, the application server 150 can be an element of a network that provides content or services to a client (e.g., UEs 1 10). In some aspects, the application server 150 can be used to facilitate one or more services (e.g., VoIP, PTT services, group communication services, social networking services, etc.) for the UEs 1 10 via the core network 140.

[0076] In aspects, the CN 140 can be a 5GC, and the RAN can interface with the CN 140 via an NG interface. In aspects, the NG interface can be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the RAN nodes 120 and a UPF, and an NG control plane (NG-C) interface, which is a signaling interface between the RAN nodes 120 and AMFs.

[0077] Figure 2 A block diagram of an example wireless system 200 implementing an electronic device for control messaging for multiple beams is shown. For ease of illustration and not limitation, the system 200 can be described utilizing elements from Figure 1 The system 200 can be a Figure 1The system 200 can include a processor 210, a transceiver 220, a communication infrastructure 230, a memory 235, and an antenna 225 that collectively perform operations to implement group-based reporting beam management. The transceiver 220 transmits and receives 5G wireless communication signals via the antenna 225. The communication infrastructure 230 can be a bus. The memory 235 can include random access memory (RAM) and / or cache and can include control logic (e.g., computer software), computer instructions, and / or data. In executing the computer instructions, the processor 210 can be configured to perform the functions described herein for group-based reporting beam management. Alternatively, the processor 210 can include its own internal memory (not shown) and / or can be “hardwired” (as in a state machine) to perform the functions described herein for group-based reporting beam management. The antenna 225 coupled to the transceiver 220 can include one or more antennas, antenna arrays, and / or can be the same or different types of panels to enable wireless communication over a wireless network.

[0078] In some aspects, the RAN nodes 120 can utilize the components of the wireless system 200. According to some aspects, the processor 210, alone or in combination with the memory 235 and / or the transceiver 220, implements control messaging for multi-beam communications. For example, the system 200 can generate medium access control control elements (MAC CEs) and transmit these MAC CEs to UEs using the transceiver 220 and / or the antenna 225. The UEs receiving the MAC CEs can then update TCI state information for a communication channel. For example, the MAC CEs can update one or more component carriers (CCs) for a PDSCH and / or a PDCCH. The MAC CEs can also update spatial relations for SRS resource sets with different periodicities. The TCI states and / or TCI codepoints can also be updated to support multi-TRP operation.

[0079] Figure 3A A block diagram illustrating a medium access control control element (MAC CE) 300A for updating transmission configuration indication (TCI) states for a physical downlink shared channel (PDSCH) is shown, according to some aspects. As will be described further below, a reserved bit 302 of the MAC CE 300A can be used to indicate whether a list of component carriers (CCs) is to be updated based on updated TCI states. The use of the reserved bit 302 can allow for multiple TCI states of a PDSCH to be updated using a single MAC CE 300A. The MAC CE 300A design can provide for simultaneous updating of multiple TCI states and provide for an overhead savings and reduced latency, rather than using multiple MAC CEs to update the TCI states individually.

[0080] The MAC CE 300A can be a control message transmitted from a node to a UE to provide the UE with TCI state data. For example, the node can be a RAN node 120 and the UE can be a UE 110, as described with reference to FIG. 1. Figure 1 The MAC CE 300A can be a bitmap organized into 8-bit octets. The MAC CE 300A can include a reserved bit 302, a serving cell ID 304, a bandwidth part (BWP) ID 306, and octets 308, 310, 312 indicating TCI state information. The serving cell ID 304 can be a field indicating the identity of a serving cell to which the MAC CE 300A applies. As will be further described below, each component carrier (CC) can correspond to its own serving cell ID 304. The length of the serving cell ID 304 can be five bits. The BWP ID 306 can indicate a downlink bandwidth part to which the MAC CE 300A applies. The length of the BWP ID 306 can be two bits.

[0081] The octets 308, 310, 312 can include TCI state information indicating an activation or deactivation state of a TCI state. For a particular value “Ti”, the field can be set to “1” to indicate that the TCI state is activated and mapped to a codepoint specified in a downlink control information (DCI) message. If the field is set to “0”, the TCI state can be deactivated and can not be mapped to a DCI message. The codepoint to which the TCI state is mapped can be determined by its ordinal position in the bitmap of the MAC CE 300A.

[0082] Turning to the reserved bit 302, the reserved bit 302 can be used to indicate whether the MAC CE 300A is updating a single CC or a list of CCs, rather than being reserved for non-use. A CC can be a block of frequencies assigned to a particular UE to increase data rates. CCs can be grouped by intra-band aggregation and / or inter-band aggregation. For intra-band aggregation, each CC can be in the same frequency band, while inter-band aggregation can organize each CC into different frequency bands. For intra-band aggregation, the CCs can be contiguous or non-contiguous in a frequency range. As previously described, each CC can have a corresponding serving cell ID 304.

[0083] In some aspects, when the reserved bit 302 is not set or set to a zero value, the node can indicate to the UE that the MAC CE 300A is being used to update the TCI state for the CC indicated by the serving cell ID 304. Conversely, when the reserved bit 302 is set or set to a one value, the node can indicate to the UE that the MAC CE 300A is being used to update a list of CCs. This list of CCs can be configured by a radio resource control (RRC) message and can correspond to the indicated serving cell ID 304. When the reserved bit 302 is set, the UE can update the TCI state information for each cell in the same list of CCs configured by the RRC message. The UE can identify the set value of the reserved bit 302, identify the serving cell ID 304, and then update each CC in the list that includes the serving cell ID 304 in the manner indicated by the octets 308, 310, 312. In some aspects, the bit setting of the reserved bit 302 can be reversed, where a one value indicates a single CC update and a zero value indicates an update to a list of CCs.

[0084] Using the MAC CE 300A in this manner can allow a node to indicate to a UE to update the TCI state for multiple CCs using fewer control messages. The use of the reserved bit 302 can allow for the simultaneous update of a list of CCs. This update can help facilitate multi-beam communications and provide flexibility for updating a single CC and / or updating multiple CCs. The updated TCI state information can help update the TCI state for a PDSCH.

[0085] Figure 3B A block diagram illustrating a MAC CE 300B for updating transmission configuration indication (TCI) states for a physical downlink control channel (PDCCH) is shown, according to some aspects. Similar to the MAC CE 300A, a reserved bit in the MAC CE 300B can be used to indicate whether to update a list of component carriers (CCs) based on the updated TCI state. The use of this reserved bit can allow for the use of a single MAC CE 300B to update multiple TCI states for a PDCCH. The MAC CE 300B design can provide for the simultaneous update of multiple TCI states and provide for an overhead savings and reduced latency, rather than using multiple MAC CEs to update the TCI states individually.

[0086] The MAC CE 300B can be a control message transmitted from a node to a UE to provide TCI state data to the UE. For example, the node can be a RAN node 120 and the UE can be a UE 110, as referenced to FIG. 1. The MAC CE 300B can be used to update the TCI state for a PDCCH. The PDCCH can be a PDCCH 140, as referenced to FIG. 1. Figure 1The MAC CE 300B can be a bitmap organized into 8-bit octets. The MAC CE 300B can include a serving cell ID 314, a CORESET ID 316A-316B, and a TCI state ID 318. Similar to the MAC CE 300A, the serving cell ID 314 can be a field indicating the identity of the serving cell to which the MAC CE 300B applies. Each component carrier (CC) can correspond to its own serving cell ID 314. The length of the serving cell ID 314 can be five bits. The CORESET ID 316A-316B can be an identification of a control resource set to which the MAC CE 300B applies to update a TCI state. The CORESET corresponds to a PDCCH. The length of the CORESET ID 316A-316B can be four bits and can be conveyed in two octets. The TCI state ID 318 can be a TCI state applicable to the CORESET identified by the CORESET ID 316A-316B. Based on the octet alignment, seven bits can be reserved for the TCI state ID 318.

[0087] While seven bits are reserved for the TCI state ID 318, an RRC message can configure up to 64 TCI states. Because of this configuration, even though seven bits are reserved for the TCI state ID 318, 6 bits can be used to capture 64 TCI states. In this way, one bit can not be used in the TCI state ID 318. Similar to the MAC CE 300A, this bit can be used to indicate whether a list of CCs is to be updated instead of not using this bit. Specifically, the most significant bit (MSB) or the least significant bit (LSB) of the TCI state ID 318 field can be used to indicate whether to update a list of CCs.

[0088] Similar to the MAC CE 300A, when this bit is not set or set to a zero value, the node can indicate to the UE that the MAC CE 300B is being used to update the TCI state of the CC indicated by the serving cell ID 314. Conversely, when this bit is set or set to a one value, the node can indicate to the UE that the MAC CE 300B is being used to update a list of CCs. This list of CCs can be configured by a radio resource control (RRC) message and can correspond to the indicated serving cell ID 314. When the bit is set, the UE can update the TCI state information for each cell in the same list of CCs configured by the RRC message. The UE can identify the set value of the bit, identify the serving cell ID 314, and then update each CC in the list including the serving cell ID 314 in the manner indicated by the six bits of the TCI state ID 318. In some aspects, the bit setting of the unused bit can be reversed, where a one value indicates a single CC update and a zero value indicates updating a list of CCs.

[0089] Using the MAC CE 300B in this manner can allow the node to instruct the UE to update the TCI states for multiple CCs using fewer control messages. The use of the unused bits of the TCI state ID 318 can allow for the simultaneous updating of the list of CCs. This updating can help facilitate multi-beam communications and provide flexibility for updating a single CC and / or updating multiple CCs. The updated TCI state information can help update the TCI state for the PDCCH.

[0090] In some aspects, another MAC CE can be defined and provide TCI state information for PDSCHs including one or two TCI states. This can be the case, for example, in a multi-TRP scenario. In this case, the UE can be communicating with multiple nodes, which can result in the activation of two TCI states. The network can use this MAC CE to update the TCI codepoint for PDSCHs in a list of CCs. The updated TCI codepoint can be applied to the list corresponding to the serving cell ID, as described with reference to Figure 3A and Figure 3B The application of the updated TCI codepoint can indicate that multi-TRP operation is activated and / or deactivated for the CCs in the list.

[0091] In some aspects, the updated TCI codepoint can be applied to a subset of the CCs in the list of CCs according to different conditions. The CCs that satisfy one or more of these conditions can be updated. These cases can include:

[0092] - The CC is configured with at least one CORESET with a CORESETPoolIndex value of none or CORESETPoolIndex set to zero, or at least one CORESET with CORESETPoolIndex set to one.

[0093] - The CC is configured with RepNuml6 in at least one entry of PDSCH-TimeDomainResourceAllocationRepSchemeEnabler.

[0094] - The CC is configured with RepSchemeEnabler.

[0095] Updating the TCI states in a multi-TRP operation, these conditions can be helpful. By using one or more of these conditions, the UE can control the updating of the TCI states even when multiple TCI states correspond to a particular TCI codepoint.

[0096] Figure 4A block diagram illustrating a MAC CE 400 for activating and deactivating sounding reference signal (SRS) resource sets according to some aspects is shown. A node can transmit the MAC CE 400 to a UE to indicate a spatial relation for the UE to transmit a SRS resource set. The MAC CE 400 can be used to activate and / or deactivate a semi-persistent (SP) SRS resource set. The MAC CE 400 can also be configured to provide spatial relation data for other periodicities, such as aperiodic or periodic SRS resource sets. Using the MAC CE 400, a UE can update its spatial relation information when transmitting SRS signals to a node.

[0097] SRSs are reference signals used in the uplink direction from a UE to a node to help the node obtain channel state information (CSI) for each UE. The CSI can describe how signals propagate from the UE to the node and can represent the effects of scattering, fading, power decay with distance, and / or other channel elements. The node can use the SRSs for resource scheduling, link adaptation, MIMO communication, and / or beam management. A UE can transmit SRSs using different periodicities. For example, different periodicities can be “periodic,” “aperiodic,” and / or “semi-persistent” (SP). SRSs can be identified as SRS resources, which can refer to the location of the SRS in time and frequency domain in a resource grid. A SRS resource set can refer to the number of SRS resources transmitted at different symbols.

[0098] In view of this description and SRS organization, a node can generate a MAC CE 400 to update the spatial relation of a SRS resource set at a UE. While Figure 4 While an example MAC CE 400 is depicted for controlling a SP SRS resource set, the MAC CE 400 can also be configured to provide spatial relation updates for aperiodic and periodic SRS resource sets. In this way, the MAC CE 400 can support spatial relation updates for different periodicities. As will be further explained below, the MAC CE 400 can also support updates of the spatial relation of a CC list.

[0099] For the SRS resource set scenario, the MAC CE 400 can include an “Activate or Deactivate” (A / D) bit 402 that is used to activate or deactivate the SRS resource set indicated by the SRS resource set ID 412. The length of the SP SRS resource set ID 412 can be four bits in length. The MAC CE 400 can also include a cell ID 408 of the SRS resource set that can indicate the identity of the serving cell or CC that includes the activated or deactivated SP SRS resource set. The length of the cell ID 408 of the SRS resource set can be five bits. The MAC CE 400 can also include a BWP ID 410 of the SRS resource set that can indicate the uplink bandwidth part that includes the activated or deactivated SR SRS resource set. The length of the BWP ID 410 of the SRS resource set can be two bits.

[0100] The MAC CE 400 can include a SUL bit 420. This field indicates whether the MAC CE 400 is applicable to NUL carrier or SUL carrier configuration. The SUL bit 420 can be set to

[0101] “1” to indicate that the MAC CE 400 is applicable to SUL carrier configuration. The SUL bit 420 can be set to “0” to indicate that the MAC CE 400 is applicable to NUL carrier configuration.

[0102] The “C” bit 418 will now be described along with the other octets. The MAC CE 400 can also include a “C” bit 418 that can indicate whether the octets containing the resource serving cell ID fields 430, 436 and resource BWP ID fields 428, 434 are present. If this field is set to “1”, the octets containing the resource serving cell ID fields 430, 436 and resource BWP ID fields 428, 434 are present. If this field is set to “0”, they are not present and the resources indicated in the resource ID i fields 414, 426 can be located on the serving cell and BWP indicated by the cell ID 408 of the SRS resource set and the BWP ID 410 of the SRS resource set.

[0103] The “F” bits 406, 422 can refer to the type of resource used as the spatial relation for the SRS resource. F0 can refer to the first SRS resource within the resource set, while F1 refers to the second SRS resource, and so on. The “F” bit 406 can be set to “1” to indicate that an NZP CSI-RS resource index is used. The “F” bit 406 can be set to “0” to indicate that an SSB index or an SRS resource index is used.

[0104] The resource ID field 414, 426 can include an identifier of a resource for spatial relation derivation of the SRS resource i. The resource ID field 414, 426 can indicate a particular reference signal to use. For example, resource ID 0 can refer to the first SRS resource within a resource set. If F i is set to “0” and the first bit of the resource ID field is set to “1”, the remaining part of this field includes an SSB-Index. If F i is set to “0” and the first bit of the field is set to “0”, the remaining part of this field includes an SRS-ResourceId. The length of the resource ID field 414, 426 can be seven bits.

[0105] The resource serving cell ID field 430, 436 can indicate the identity of the serving cell in which the resource for spatial relation derivation of the SRS resource “i” is located. The length of the field can be five bits. The resource BWP ID field 428, 434 can include the BWP-ID of the uplink bandwidth part in which the resource for spatial relation derivation of the SRS resource “i” is located. The length of the field can be two bits.

[0106] While the MAC CE 400 can also include reserved bits 404, 416, these reserved bits 404, 416 can be used to support different SRS resource set periodicities and / or indicate whether to update the spatial relations of the CC list.

[0107] For example, in some aspects, the SP SRS resource set ID field 412 can be used to indicate the periodicity and / or time domain pattern of the SRS resource set. For example, the four bits of the SP SRS resource set ID field 412 can indicate that the MAC CE 400 can be used to update a periodic, aperiodic, or semi-persistent SRS resource set, rather than being limited to only semi-persistent cases. The MAC CE 400 can also include an indication of whether to update a particular CC indicated by the cell ID 408 of the SRS resource set or whether to update the CC list.

[0108] When the SRS resource set ID field 412 indicates that the SRS resource set is aperiodic or periodic, the UE can ignore the “A / D” bit 402. That is, the “A / D” bit 402 can not indicate an activated or deactivated or indicated SRS resource set corresponding to the SRS resource set ID field 412. Rather, the “A / D” bit 402 can be used to indicate whether the spatial relation update applies to the cell ID 408 of a particular SRS resource set or to the CC list found in the same CC list as the indicated cell. This list update can be similar to the reference Figure 3A and Figure 3BList update is described. In some aspects, a reserved bit 404, 416 can be used instead of the“A / D” bit 402 to indicate whether a particular CC or a CC list is to be updated. However, in either case, the MAC CE 400 can be used to update spatial relations for multiple SRS resource sets.

[0109] However, in aspects where the SP SRS resource set ID field 412 indicates that the SRS resource set is semi-persistent, the“A / D” bit 402 can have a value of one. In this case, the reserved bits 404, 416 can be used to indicate whether a particular CC or a CC list is to be updated.

[0110] In some aspects, when the MAC CE 400 is used to update a CC list, the SRS resource spatial relations are updated when the corresponding SRS resource sets have the same time domain pattern. For example, in some cases, the CCs can have different time domain patterns. In this case, the spatial relations can not apply to the updated CC list. However, in cases where the CCs in the list have the same periodicity and / or time domain pattern as indicated from the SP SRS resource set ID field 412, the MAC CE 400 can apply to the CC list. However, due to the difference in time domain patterns, the beams can need to be updated on a per resource level.

[0111] Figure 5 A block diagram of a MAC CE 500 for updating spatial relations for sounding reference signal (SRS) resources is shown, in accordance with some aspects. As described above, while some scenarios can benefit from an update of SRS resource sets, some other scenarios can benefit from an update of individual SRS resources. For example, an update of a particular SRS resource can allow for precise positioning of the resource and updating of particular beams for that resource. The MAC CE 500 can be a control message that provides this type of resource level update. The MAC CE 500 can provide more precise resource updates. The MAC CE 500 can still be used to indicate whether the spatial relations are to be updated for a particular CC or a CC list. In some aspects, the first 16 bits of the MAC CE 500 can indicate a particular SRS resource, while the last 16 bits can indicate updated beam information. The length of the MAC CE 500 can be four octets.

[0112] In particular, the MAC CE 500 can include reserved bits 502, 506, 508 that can be used to indicate whether the spatial relation update is for a CC specified by a cell ID 510 of the SRS resource or whether the spatial relation update is for a CC list. The update of a CC list can occur in a similar manner as described with reference to Figure 3A and Figure 3B The MAC CE 500 can be used to update spatial relations for multiple SRS resources. In some aspects, the MAC CE 500 can be used to update spatial relations for a particular SRS resource. In some aspects, the MAC CE 500 can be used to update spatial relations for a CC list. Figure 4The cell ID 510 of the SRS resource can refer to the cell in which the SRS resource is located. The cell ID 510 of the SRS resource can correspond to a particular resource, rather than indicating a set of SRS resources. Similarly, the BWP ID 512 of the SRS resource can correspond to the BWP in which the SRS resource is located. The SRS resource ID 514 can be an identification SRS-ResourceID configured by a RRC message. The SUL 510 can be similar to the SUL 420, as described with reference to Figure 4 The use of the cell ID 510 of the SRS resource, the BWP ID 512 of the SRS resource, and / or the SRS resource ID 514 can allow the UE to identify the particular SRS resource that the MAC CE 500 is updating.

[0113] The “C” bit 504 can also be similar to the “C” bit 418, as described with reference to Figure 4 In particular, the “C” bit 504 can indicate whether there is bit information for the subsequent two octets. In the MAC CE 500, the two octets can provide information for the particular resource being updated. For example, the resource ID 516 can be similar to the resource ID 414, 426, as described with reference to Figure 4 The resource ID 516 can be an ID of a resource for spatial relation update. For example, the resource ID 516 can indicate a particular beam to use. The resource serving cell ID 522 can be a cell ID in which the resource for spatial relation is located. The resource BWP ID 518 can indicate a BWP ID in which the resource for spatial relation is located.

[0114] The use of the MAC CE 500 can allow for particular updates of resources, rather than resource sets. The MAC CE 500 can provide additional flexibility for updating spatial relations. The MAC CE 500 can also be used to update spatial relations for a CC list to reduce messaging overhead and / or reduce latency.

[0115] Figure 6A A block diagram illustrating a MAC CE 600A for configuring TCI codepoints for PDSCH to support multi-transmission reception point (multi-TRP) operation is shown, according to some aspects. As previously explained, a multi-TRP scenario can arise when a UE communicates with more than one antenna array or node. In this case, each TCI codepoint can include 1 or 2 TCI states. In this way, the MAC CE 600A provides a control message to support multi-TRP operation and configure TCI codepoints for PDSCH.

[0116] Similar to the previously described MAC CE, MAC CE 600A may include reserved bits 602A, 604A, and 614A. Reserved bits 602A, 604A, and 614A can be used to indicate whether the TCI status should be updated for a CC or for a CC list. MAC CE 600A may include serving cell ID 616A and BWP ID 620A, which may be similar to serving cell ID 304 and BWP ID 306, as referenced. Figure 3A As described. The MAC CE 600A may include multiple TCI code point fields 618A, which may be three bits to indicate the number "M". These three bits can be used to indicate up to eight TCI code points, or multiple TCI code points from 1 to 8. The value of M provides this number. However, each TCI code point may have one or two TCI states. To capture this information, the MAC CE 600A may include a field 622A, which may indicate the number of TCI code points with two TCI states. Field 622A may be a count of the number of "C_i" bit values ​​606, 610 with non-zero values, such as being set to a value of "1". When the "C_i" bit values ​​606, 610 have a value of "1", the corresponding TCI code point may have two TCI states. For example, "C_i" may indicate whether a second TCI state is used for TCI code point "i".

[0117] The MAC CE 600A may include TCI state ID (0,1) 624 and TCI state ID (0,2) 626 to illustrate an example of "C_0" 606 having two TCI states. TCI state ID (0,1) 624 may be the first TCI state of TCI code point "0", while TCI state ID (0,2) 626 may be the second TCI state of TCI code point "0". Reserved bit 608 may be included to preserve the eight-bit byte configuration of the MAC CE 600A.

[0118] Similarly, the MAC CE 600A may include TCI state ID (M-1,1) 628 and TCI state ID (M-1,2) 630 to illustrate an example where “C_(M-1)” 610 has two TCI states. TCI state ID (M-1,1) 628 may be the first TCI state of TCI code point “M-1”, while TCI state ID (M-1,2) 630 may be the second TCI state of TCI code point “M-1”. Reserved bit 612 may be included to preserve the eight-bit byte configuration of the MAC CE 600A.

[0119] Using MAC CE 600A can allow for flexibility in accommodating TCI codepoints with one or two TCI states. Using the “C_i” bits 606, 610, the UE can be able to decode the octets to determine whether to update one or two TCI states. Further, using the reserved bits 602A, 604A, or 614A can still provide list updates for CCs to reduce overhead and latency.

[0120] Figure 6B A block diagram illustrating an example MAC CE 600B indicating multiple TCI states is shown, in accordance with some aspects. The MAC CE 600B can be an example aspect of the MAC CE 600A. Similar to the MAC CE 600A, the MAC CE 600B can include reserved bits 602B, 604B, 614B, as well as a serving cell ID 616B and a BWP ID 620B. The MAC CE 600B can provide an example of the fields 618B and 622B having example values.

[0121] For example, the MAC CE 600B can use bits of a TCI codepoint quantity field 618B, which can be similar to the field 618A, to indicate an “M” value of “4,” as described with reference to Figure 6A Similarly, the MAC CE 600B can indicate a value of “2” for the field 622B, which can be similar to the field 622A and can indicate the quantity of codepoints with two TCI states. In this case, the UE can identify the quantity of octets to follow in the remaining transmissions. Specifically, the UE can identify that two of the TCI codepoints will have two TCI states, and thus four octets will be used. The UE can use the “M” value to identify the two remaining TCI codepoints with one TCI state, each of which will use one octet. With this information, the UE can expect to receive six octets. The UE can then identify the value of each “C_i” 632, 634, 638, and 640 to determine whether a particular TCI codepoint corresponds to one or two TCI states.

[0122] To further illustrate this example, "C_0" 632 can be a zero value, which can indicate a single TCI state. TCI state ID (0, 1) 644 can then provide state information for that TCI codepoint. Upon identifying "C_0" 632 as a zero value, the UE can identify the subsequent 7 bits as being related to a single TCI state. "C_1" 634 can be a value, which can indicate the presence of two TCI states. In this way, TCI state ID (1, 1) 646 and TCI state ID (1, 2) 648 can provide information for the two TCI states. Reserved bit 636 can be used to maintain the octet configuration of MAC CE 600B. Upon identifying "C_1" 634 as a value of one, the UE can identify the subsequent 15 bits as being related to two TCI states. "C_1" 634 can be a value, which can indicate the presence of two TCI states. The UE can continue to identify "C_2" as having a zero value and indicating a single TCI state. TCI state ID (2, 1) 650 can then provide state information for that TCI codepoint. For "C_3" 640, the UE can identify a value of one and can identify two TCI states. TCI state ID (3, 1) 652 and TCI state ID (3, 2) 654 can provide information for the two TCI states. Reserved bit 642 can be used to maintain the octet configuration of MAC CE 600B.

[0123] Figure 7 A flow diagram 700 for updating TCI states for a component carrier (CC) list of a user equipment (UE) is shown, in accordance with some aspects. In some aspects, a network, such as core network 140, network element 130, application server 150, node 120, and / or wireless system 200, can perform flow diagram 700. In some aspects, RAN node 120 can use flow diagram 700 to generate and transmit a MAC CE to a UE. Flow diagram 700 should be described with reference to RAN node 120; however, flow diagram 700 is not limited to this example aspect. Flow diagram 700 can be executed on any computing device, such as, for example, the computer systems described with reference to Figure 10 The processing logic described can be hardware (e.g., circuitry, dedicated logic, programmable logic, microcode, etc.), software (e.g., instructions executed on a processing device), or a combination thereof.

[0124] It should be understood that all of the steps can not be required to perform the disclosure provided herein. In addition, some of the steps can be performed simultaneously, or in a different order than Figure 7 shown, as will be understood by one of ordinary skill in the art.

[0125] At 702, the RAN node 120 can identify an update to a transmission configuration indicator (TCI) state of a component carrier (CC) corresponding to a user equipment (UE) 110, where the CC has a serving cell ID. This update can be an update to a beam or a QCL signal. For example, the UE 110 can assume a QCL relationship between different reference signals. However, the RAN node 120 can update this assumption and can provide an updated definition for the QCL assumption. In this way, the RAN node 120 can provide an initial definition of the TCI state and / or can update an existing definition at the UE 110.

[0126] The update can also affect one or more CCs. Similarly, the updated TCI state can apply to PDSCH and / or PDCCH. In some aspects, the update for PDSCH can occur in a multi-TRP scenario where a TCI codepoint has one or two TCI states. In this case, a subset of CCs in a CC list can be updated.

[0127] At 704, the RAN node 120 can determine whether to update a CC list including the CC based on the update to the TCI state. This CC list can have been previously configured by a radio resource control (RRC) message and can correspond to the indicated serving cell ID. For example, the RRC can have previously configured TCI related parameters. The RAN node 120 can have previously transmitted an RRC message to the UE 110 to configure the CC list. The update to the TCI state information can apply to other CCs in the list that also include the CC corresponding to the serving cell ID.

[0128] At 706, the RAN node 120 can determine whether to update the CC list at the UE 110. If the CC list is not updated and the RAN node 120 intends to update the CC corresponding to the serving cell ID, the RAN node 120 can generate a medium access control control element (MAC CE) at 708. This MAC CE can include the serving cell ID and a first bit value indicating that the UE 110 is to update the TCI state of the CC using the serving cell ID. For example, the first bit value can be a zero value. The MAC CE can also include TCI state information for updating the TCI state at the UE 110. The RAN node 120 can then transmit the MAC CE to the UE 110 at 712. The UE 110 can then update the CC corresponding to the serving cell ID using the TCI state information included in the MAC CE.

[0129] Returning 706, the RAN node 120 can determine to update the CC list. In this case, the RAN node 120 can generate a MAC CE that includes a serving cell ID and a second bit value indicating that the UE 110 update the TCI state of the CCs in the CC list, the TCI state including the serving cell ID. In this way, the UE 110 can update the CCs corresponding to the serving cell ID and other CCs on the list configured by the RRC message. The MAC CE can also include TCI state information for updating the TCI state at the UE 110. This MAC CE can then provide TCI updates for multiple CCs, which can reduce messaging overhead. At 712, the RAN node 120 can transmit the MAC CE to the UE 110.

[0130] The MAC CE generated from the flowchart 700 can be similar to the MAC CEs 300A and 300B, as previously described with reference to Figure 3A and Figure 3B For example, the MAC CE 300A can be used to update the TCI state for the PDSCH, while the MAC CE 300B can be used to update the TCI state for the PDCCH. Other values can be included in the MAC CE and can have been previously described with reference to Figure 3A and Figure 3B

[0131] As previously described, the MAC CE can also be used for multi-TRP operations. Similarly, the MAC CE can apply in cases where the CC list includes identified CCs. In some aspects, a subset of the CCs can be updated based on some conditions as previously described.

[0132] In some aspects, the flowchart 900 can be performed over one or more iterations depending on changes to the TCI codepoint. For example, a first MAC CE can be used to update the TCI state, but then a second MAC CE can be used to update the TCI state again. Similarly, the second MAC CE can correspond to an update of the same TCI state or a different TCI state. In this way, the aspects described with respect to the flowchart 900 are not limited to a single MAC CE.

[0133] Figure 8A A flowchart 800A is shown for generating a MAC CE to update the spatial relations for SRS resource sets having different periodicities and / or time-domain patterns, according to some aspects. Figure 8B A flowchart 800B is shown for modifying a MAC CE to update the spatial relations for a CC list, according to some aspects.

[0134] ​In some aspects, the network (such as the core network 140, the network element 130, the application server 150, the node 120, and / or the wireless system 200) can perform the flowcharts 800A and 800B. In some aspects, the RAN node 120 can use the flowcharts 800A and 800B to generate and transmit a MAC CE to a UE. The flowcharts 800A and 800B will be described with reference to the RAN node 120; however, the flowcharts 800A and 800B are not limited to this exemplary aspect. The flowcharts 800A and 800B can be executed on any computing device, such as, for example, the computing device described with reference to FIG. 1. Figure 10 The described computer system and / or processing logic can comprise hardware (e.g., circuitry, dedicated logic, programmable logic, microcode, etc.), software (e.g., instructions executed on a processing device), or a combination thereof.

[0135] It should be understood that not all steps can be required to perform the disclosure provided herein. In addition, some of the steps can be performed simultaneously, or in a different order than as shown, as would be understood by one of ordinary skill in the art. Figure 8A and Figure 8B in a different order than as shown.

[0136] At 802, the RAN node 120 can identify an update to a spatial relation of a sounding reference signal (SRS) resource set corresponding to a component carrier (CC). The spatial relation of the SRS can be an update to one or more uplink signals transmitted by the UE 110 to the RAN node 120.

[0137] At 804, the RAN node 120 can determine whether a time domain pattern of the SRS resource set is semi-persistent. For example, the time domain pattern and / or periodicity of the SRS resource set can be semi-persistent, aperiodic, or periodic. At 806, if it is determined that the time domain pattern is not semi-persistent, the RAN node 120 can generate a MAC CE (such as the MAC CE 400) using an “activate / deactivate” bit field to specify whether to update a list of CCs including the CC based on the updated spatial relation. The “A / D” field can be a bit field that is not used. Since the “A / D” field is not used for periodic or aperiodic SRS resource set updates, this bit can be used to indicate whether the spatial relation update is for the indicated CC or for a list of CCs corresponding to the same list of CCs as the indicated CC.

[0138] At 806, if it is determined that the SRS resource set is semi-persistent, the RAN node 120 can generate a MAC CE (such as the MAC CE 400) using a reserved bit field at 810 to specify whether to update a list of CCs including the CC based on the updated spatial relation. Since the “A / D” field is used for semi-persistent SRS resource set scenarios, this bit can not be available. In this way, the reserved bit can be used for this indication.

[0139] At 812, the RAN node 120 can determine whether to update a list of CCs including the CC based on the updated spatial relation. Updating this list can result in reduced messaging overhead. However, in some aspects, the time domain pattern of the elements of the SRS resource set is the same. At 814, the RAN node 120 can determine whether to update the list of CCs. If the list is not updated, at 816, the RAN node 120 can modify the MAC CE to indicate a first bit value in a bit field that indicates the UE 110 to update the spatial relation of the CC. The MAC CE can also include a value for the SRS resource set ID and resource ID information to update the SRS resource set at the UE 110. At 820, the RAN node 120 can transmit the MAC CE to the UE 110.

[0140] Returning to 814, if the RAN node 120 determines to update the list of CCs based on the updated spatial relation, at 818, the RAN node 120 can modify the MAC CE to include a second bit value in a bit field that indicates the UE 110 to update the spatial relation of the CCs in the list of CCs. This list of CCs can have been previously configured by a radio resource control (RRC) message and can correspond to the cell ID of the indicated SRS resource set. The MAC CE can also include resource ID information to update the SRS resource set at the UE 110.

[0141] Upon receiving the MAC CE, the UE 110 can identify the corresponding bit that indicates whether to update the list of CCs. Depending on the indicated value, the UE 110 can identify the particular CC to update and / or the list of CCs to update.

[0142] Figure 8C A flowchart 800C for generating a MAC CE to update a spatial relation of an SRS resource is shown in accordance with some aspects. In some aspects, a network such as the core network 140, network element 130, application server 150, node 120, and / or wireless system 200 can perform the flowchart 800C. In some aspects, the RAN node 120 can use the flowchart 800C to generate and transmit a MAC CE to a UE. The flowchart 800C should be described with reference to the RAN node 120; however, the flowchart 800C is not limited to this exemplary aspect. The flowchart 800C can be executed on any computing device such as, for example, with reference toFigure 10 The described computer system and / or processing logic can comprise hardware (e.g., circuitry, dedicated logic, programmable logic, microcode, etc.), software (e.g., instructions executed on a processing device), or a combination thereof.

[0143] It should be understood that all of the steps can not be required to perform the disclosure provided herein. In addition, some of the steps can be performed simultaneously, or in a different order than described, as will be understood by one of ordinary skill in the art. Figure 8C

[0144] At 822, the RAN node 120 can identify an update of a spatial relation of a sounding reference signal (SRS) resource corresponding to a component carrier (CC) of a user equipment (UE) 110, where the CC has an SRS resource cell ID. This update can be for a particular resource, rather than a set of resources. In this way, the flowchart 800C can be used to update a particular beam identified using the SRS resource cell ID, as described with reference to Figure 5

[0145] At 824, the RAN node 120 can determine whether to update a list of CCs including the CC based on the update of the spatial relation. This list of CCs can have been previously configured by a radio resource control (RRC) message, and can correspond to the indicated SRS resource ID. The update of the spatial relation information can apply to other CCs in the list that also include the CC corresponding to the SRS resource ID.

[0146] At 826, the RAN node 120 can determine whether to update the list of CCs at the UE 110. If the list of CCs is not updated and the RAN node 120 intends to update the CC corresponding to the SRS resource cell ID, the RAN node 120 can generate a medium access control control element (MAC CE) at 828. This MAC CE can include the SRS resource cell ID and a first bit value indicating that the UE 110 is to update the spatial relation of the CC using the SRS resource cell ID. Other values, such as an SRS resource BWP ID and / or an SRS resource ID, can also help to identify the SRS resource. Values such as a resource ID, a resource serving cell ID, and / or a resource BWP ID can indicate the updated SRS spatial relation. For example, the first bit value can be a zero value. The MAC CE can be similar to the MAC CE 500, as described with reference to Figure 5

[0147] ​​​Returning to 826, the RAN node 120 can determine to update the CC list. In this case, the RAN node 120 can generate a MAC CE that includes the SRS resource cell ID and a second bit value that indicates for the UE 110 to use the SRS resource cell ID to update the spatial relation for the CCs in the CC list. In this way, the UE 110 can update the CC corresponding to the SRS resource cell ID and other CCs on the list configured by the RRC message. This MAC CE can then provide spatial relation updates for multiple CCs, which can reduce messaging overhead. At 832, the RAN node 120 can transmit the MAC CE to the UE 110.

[0148] In some aspects, the flowcharts 800A, 800B, and / or 800C can be performed over one or more iterations according to changes to the SRS resource set or resources. For example, a first MAC CE can be used to update the SRS resource set, but then a second MAC CE can be used again to update the SRS resource set. Similarly, the second MAC CE can correspond to an update to a particular resource of the resource set. In this way, the aspects described with respect to the flowcharts 800A, 800B, and / or 800C are not limited to a single MAC CE.

[0149] Figure 9 A flowchart 900 for configuring TCI codepoints for PDSCH to support multi- transmission reception point (multi-TRP) operation is shown in accordance with some aspects. In some aspects, a network such as the core network 140, network element 130, application server 150, node 120, and / or wireless system 200 can perform the flowchart 700. In some aspects, the RAN node 120 can generate and transmit a MAC CE to a UE using the flowchart 900. The flowchart 900 should be described with reference to the RAN node 120; however, the flowchart 900 is not limited to this example aspect. The flowchart 900 can be performed on any computing device such as, for example, the computer systems described with reference to Figure 10 The processing logic described can be hardware (e.g., circuitry, dedicated logic, programmable logic, microcode, etc.), software (e.g., instructions executed on a processing device), or a combination thereof.

[0150] It should be understood that all of the steps can not be required to perform the disclosure provided herein. In addition, some of the steps can be performed simultaneously, or in a different order than Figure 9 shown.

[0151] At 902, the RAN node 120 can identify a configuration corresponding to one or more transmission configuration indicator (TCI) codepoints for a component carrier (CC). This identification can indicate that a multi-TRP scenario can be present. The RAN node 120 can generate a MAC CE that configures the TCI codepoints for the PDSCH.

[0152] At 904, the RAN node 120 can determine that at least one of the one or more TCI codepoints has multiple TCI states. For example, a TCI codepoint can have two TCI states. In this case, the codepoint can be in communication with multiple TRPs. However, other codepoints can still have one TCI state.

[0153] At 906, the RAN node 120 can generate a MAC CE that includes a first value indicating a quantity of the one or more TCI codepoints and a second value indicating a quantity of at least one of the one or more TCI codepoints that has multiple TCI states. This MAC CE can be similar to the MAC CEs 600A and / or 600B, as described with reference to FIGs. 6A and 6B. The first value and the second value can indicate to the UE 110 a number of bits and / or octets expected in the remaining bits of the MAC CE. Figure 6A and Figure 6B The first value and the second value can indicate to the UE 110 a number of bits and / or octets expected in the remaining bits of the MAC CE.

[0154] At 908, for at least one of the one or more TCI codepoints that has multiple TCI states, the RAN node 120 can update the MAC CE to include: first octet data including a bit indicating that multiple TCI states are present and a first TCI state ID; and second octet data including a reserved bit and a second TCI state ID. In this way, the MAC CE can use two octets for two TCI state IDs. In some aspects, the bit in the first octet can indicate that a particular codepoint has two TCI states. When the UE 110 receives the MAC CE and identifies this bit, the UE 110 can recognize that the subsequent octet represents data for a second TCI state corresponding to the codepoint. At 910, the RAN node 120 can transmit the MAC CE to the UE 110.

[0155] In some aspects, the flowchart 900 can be performed over one or more iterations according to changes to the TCI states. For example, a first MAC CE can be used to update the TCI states, but then a second MAC CE can be used again to update the TCI states. Similarly, the second MAC CE can correspond to an update of the same TCI states or different TCI states. In this way, aspects described with respect to the flowchart 700 are not limited to a single MAC CE.

[0156] Figure 10An example computer system that can be used to implement various aspects is shown. One or more well-known computer systems, such as Figure 10 The computer system 1000 shown can be used to implement various aspects. For example, one or more computer systems 1000 can be used to implement any of the aspects discussed herein, as well as combinations and sub-combinations of the aspects.

[0157] The computer system 1000 can include one or more processors (also referred to as central processing units or CPUs), such as the processor 1004. The processor 1004 can be connected to a communication infrastructure or bus 1006.

[0158] The computer system 1000 can also include user input / output devices 1003, such as monitors, keyboards, pointing devices, etc., that communicate via the user input / output interface 1002 with the communication infrastructure 1006.

[0159] One or more of the processors 1004 can be a graphics processing unit (GPU). In one aspect, a GPU can be a processor that is designed for specialized electronic circuitry of a computer specifically for processing mathematically intensive applications. The GPU can have an efficient, parallel structure that is useful for parallel processing of large blocks of data, such as general-purpose mathematically intensive data of computer graphics applications, images, video, etc.

[0160] The computer system 1000 can also include a main or primary memory 1008, such as random access memory (RAM). The main memory 1008 can include one or more levels of cache. The main memory 1008 can have stored therein control logic (i.e., computer software) and / or data.

[0161] The computer system 1000 can also include one or more secondary storage devices or memory 1010. The secondary storage 1010 can include, for example, a hard disk drive 1012 and / or a removable storage drive 1014. The removable storage drive 1014 can be a floppy disk drive, a magnetic tape drive, an optical disk drive, a magneto-optical drive, a tape backup device, and / or any other storage device / drive.

[0162] The removable storage drive 1014 can interact with a removable storage unit 1018. The removable storage unit 1018 can include a computer-usable or computer-readable storage device having stored thereon computer software (control logic) and / or data. The removable storage unit 1018 can be a floppy disk, magnetic tape, optical disk, DVD, magneto-optical disk, and / or any other storage device.

[0163] Auxiliary memory 1010 can include other means, devices, components, tools or other methods for allowing computer programs and / or other instructions and / or data to be accessed by computer system 1000. Such means, devices, components, tools or other methods can include, for example, removable storage units 1022 and interfaces 1020. Examples of removable storage units 1022 and interfaces 1020 can include a program cartridge and cartridge interface (such as that found in video game devices), a removable memory chip (such as an EPROM or PROM) and associated socket, a memory stick and USB port, a memory card and associated memory card slot, and / or any other removable storage unit and associated interface.

[0164] Computer system 1000 can also include a communications or network interface 1024. Communications interface 1024 can enable computer system 1000 to communicate and interact with any

[0165] Computer system 1000 can be any of a wide variety of computing devices, including, but not limited to, a personal digital assistant (PDA), desktop workstation, laptop or notebook computer, netbook, tablet, smartphone, smart watch or other wearable device, appliance, part of the Internet of Things, and / or embedded system, or any combination thereof.

[0166] Computer system 1000 can be a client or a server accessing or hosting any of the applications and / or data through any delivery paradigm, including but not limited to: remote or distributed cloud computing solutions; local or internal deployment software (“on-premises” cloud-based solutions); “as a service” models (e.g., content as a service (CaaS), digital content as a service (DCaaS), software as a service (SaaS), management software as a service (MSaaS), platform as a service (PaaS), desktop as a service (DaaS), framework as a service (FaaS), backend as a service (BaaS), mobile backend as a service (MBaaS), infrastructure as a service (IaaS), etc.); and / or hybrid modes including any combination of the foregoing examples or other services or delivery paradigms.

[0167] Any applicable data structures, file formats, and schema in computer system 400 can be exported from standards including, but not limited to, JavaScript Object Notation (JSON), Extensible Markup Language (XML), Yet Another Markup Language (YAML), Extensible HyperText Markup Language (XHTML), Wireless Markup Language (WML), MessagePack, XML User Interface Language (XUL), or any other functionally similar representation, alone or in combination. Alternatively, proprietary data structures, formats, or schema can be used, alone or in combination with known or open standards.

[0168] In some aspects, a tangible, non-transitory apparatus or article of manufacture includes a tangible, non-transitory computer-usable or readable medium having control logic (software) stored thereon to cause a computer system to perform functions as described herein, which can also be referred to as a computer program product or program storage device. This includes, but is not limited to, computer system 1000, main memory 1008, secondary memory 1010, and removable storage units 1018 and 1022, and tangible articles of manufacture embodying any combination of the foregoing. Such control logic, when executed by one or more data processing devices, such as computer system 1000, can cause such data processing devices to operate as described herein.

[0169] Based on the teachings herein, it will be obvious to those skilled in the relevant arts how to make and use aspects of the present disclosure using other data processing devices, computer systems, and / or computer architectures other than those described herein. Figure 10 In particular, aspects can operate with software, hardware, and / or operating systems other than those described herein.

[0170] It is to be understood that the detailed description is intended to be illustrative and not restrictive. Any and all examples, or equivalents, are intended to be included within the scope of the present disclosure. The specification is to be treated as exemplary and non-limiting in nature.

[0171] Although the present disclosure describes example aspects of example fields and applications, it is understood that the present disclosure is not limited to such. Other aspects and modifications are possible, and are within the scope and spirit of the present disclosure. For example, and without limitation, aspects are not limited to the software, hardware, firmware, and / or entities illustrated in the figures and / or described herein. Further, aspects, whether explicitly described herein or not, have significant utility outside the example described herein.

[0172] Aspects have been described herein with the aid of functional building blocks describing particular implementations thereof. Boundaries between the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified

[0173] Reference throughout this specification to “one aspect”, “an aspect”, “certain aspects” or similar language can indicate that a described aspect can include, but do not require, every feature or combination of features described. Alternatively, a described aspect can include, but not require, every individual feature specified. Additionally, such terminology can not necessarily refer to the same aspect. Further, the described aspects can be implemented in a variety of environments and systems including, but not limited to, medical devices, medical systems, and other electronic systems. Moreover, such terminology can not necessarily refer to the same aspect. Further, when a particular feature, structure, or characteristic is described in connection with an aspect, it is submitted that it is within the purview of one of ordinary skill in the art to effect such feature, structure, or characteristic in connection with other aspects whether or not explicitly described or made

[0174] The breadth and scope of the present disclosure should not be limited by any of the above-described exemplary aspects, but should be defined only in accordance with the following claims and their equivalents.

[0175] As described above, various aspects of the technology can include gathering and using data available from a variety of sources to, for example, improve or enhance functionality. The present disclosure contemplates that, in some instances, this gathered data can include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data can include demographic data, location-based data, telephone numbers, email addresses, twitter ID’s, home addresses, data or records pertaining to a user’s health or wellness, date of birth, or any other identifying or personal information. The present disclosure recognizes that the use of such personal information data, in some instances, can be used to the benefit of the user. The present disclosure further contemplates that, in some instances, the use of such personal information data can be used to the benefit of the provider of a computing device.

[0176] The present disclosure contemplates that the entities responsible for the collection, analysis, disclosure, transfer, storage, or other use of such personal information data will comply with well-established privacy policies and / or privacy practices. In particular, such entities should implement and consistently use privacy policies and practices that are generally recognized as industry best practices. In addition, such entities should adhere to specialized standards governing practices concerning used technologies, and should comply with any requirements dictated by an industry-regulating body. Furthermore, the user should be provided with appropriate access, such as via a web site, to information about privacy practices at such entities. Additionally, such entities should allow the user to review and request changes to his or her personal information data. In particular, such entities should allow users to review and request changes to their personal information data, such as by providing access to a user account via a web site. In addition, user data should be stored no longer than is necessary for legitimate business uses - or for legal requirements.

[0177] Regardless of the previous options, the present disclosure also contemplates that the user will selectively block the use, or collection, of certain personal information data (e.g., location data). That is, the present disclosure contemplates that a user will utilize at least one hardware and / or software element to prevent the use of, or access to, certain personal information data. For example, a user may

[0178] Furthermore, the present disclosure contemplates that, in at least some embodiments, data and / or privacy protection mechanisms can be employed to protect personal information data. In particular, certain data collection or use practices can be monitored, managed, or limited, e.g., in keeping with industry standards and / or customer policies and / or preferences. In addition, certain data can be de-identified, so that personally identifiable information is removed and / or cannot be derived. In some embodiments, de-identified data can be stored separately from identified or identifiable data, or can be combined with other de-identified data.

[0179] Thus, although the present disclosure can broadly cover techniques using personal information data to implement one or more various disclosed aspects, the present disclosure also contemplates that the various aspects can also be implemented without the need for accessing such personal information data. That is, the various aspects of the present technology are not rendered inoperable due to the lack of access to such personal information data.

Claims

1. A method performed at an access node, the method comprising: identifying an update of a transmission configuration indicator, TCI, state corresponding to a component carrier, CC, of a user equipment, UE, wherein the CC has a serving cell ID; based on the update of the TCI state, determining that a list of CCs including the CC is to be updated; generating a medium access control control element, MAC CE, including the serving cell ID and a bit value indicating that the UE is to update TCI states of CCs in the list of CCs using the serving cell ID; and transmitting the MAC CE to the UE, wherein the bit value modifies a TCI codepoint having multiple TCI states.

2. The method of claim 1, further comprising: transmitting a radio resource control, RRC, message to the UE to configure the list of CCs.

3. The method of claim 1, wherein the bit value is indicated using a reserved bit of the MAC CE.

4. The method of claim 1, wherein the MAC CE includes TCI state information to update TCI states of a physical downlink shared channel, PDSCH.

5. The method of claim 1, wherein the MAC CE includes CORESET information to update TCI states of a physical downlink control channel, PDCCH.

6. The method of claim 1, wherein the bit value is a most significant bit, MSB, or a least significant bit, LSB, of a TCI state ID.

7. A method performed at a user equipment, UE, the method comprising: receiving a radio resource control, RRC, message from a wireless access node, the RRC message indicating that the UE is to configure a list of component carriers, CCs; receiving a medium access control control element, MAC CE, from the wireless access node, the MAC CE including a serving cell ID corresponding to a component carrier, CC, of the list and a bit value indicating that the UE is to update transmission configuration indicator, TCI, states of the list of CCs; in response to identifying the bit value, identifying the list of CCs using the serving cell ID; and updating the TCI states of the CCs in the list of CCs, wherein the bit value modifies a TCI codepoint having multiple TCI states.

8. The method of claim 7, wherein the bit value is indicated using a reserved bit of the MAC CE.

9. The method of claim 7, wherein the MAC CE includes TCI state information to update TCI states of a physical downlink shared channel, PDSCH.

10. The method of claim 7, wherein the MAC CE includes CORESET information to update TCI states of a physical downlink control channel, PDCCH.

11. The method of claim 7, wherein the bit value is a most significant bit, MSB, or a least significant bit, LSB, of a TCI state ID.

12. An apparatus for communication, comprising: a memory; and a processor coupled to the memory, the processor configured to: ​ ​ ​ receiving, from a radio access node, a radio resource control, RRC, message indicating a list of component carriers, CCs, configured for a UE; receiving, from the radio access node, a medium access control control element, MAC CE, including a serving cell ID corresponding to a component carrier, CC, in the list and a bit value indicating a transmission configuration indicator, TCI, state for the UE to update the list of CCs; in response to identifying the bit value, using the serving cell ID to identify the list of CCs; and updating a TCI state of a CC in the list of CCs, wherein the bit value modifies a TCI codepoint having a plurality of TCI states.

13. The apparatus of claim 12, wherein the bit value is indicated using a reserved bit of the MAC CE.

14. The apparatus of claim 12, wherein the MAC CE includes TCI state information to update a TCI state of a physical downlink shared channel, PDSCH.

15. The apparatus of claim 12, wherein the MAC CE includes CORESET information to update a TCI state of a physical downlink control channel, PDCCH.

16. The apparatus of claim 12, wherein the bit value is a most significant bit, MSB, or a least significant bit, LSB, of a TCI state ID.

Images