Control messaging for multi-beam communication

Abstract

Some aspects include an apparatus, method, and computer program product for facilitating control messaging for multi-beam communication in a 5G wireless communication system. A node of the 5G network may generate a medium access control control element (MAC CE) to update a user equipment (UE) using different component carrier (CC) settings. The MAC CE may update a CC list to reduce messaging overhead and latency. For example, the MAC CE may indicate an update of a transmission configuration indication (TCI) state of the CC list. Similarly, the MAC CE may be used to update a set of sounding reference signal (SRS) resources and / or a spatial relationship of SRS resources corresponding to the CC list. The MAC CE may also be used to update a plurality of TCI code points having one or two TCI states in a multi-transmit receive point (multi-TRP) scenario.

Description

Related application citation

[0001] This application is a divisional application of the invention patent application with international application number PCT / CN2020 / 083759, international application date of April 8, 2020, entry into the Chinese national phase date of September 30, 2022, Chinese national application number 202080099466.5, and invention title "Control Message Transmission for Multibeam Communication". Background Technology

[0002] Various aspects can typically involve the field of wireless communication. Summary of the Invention

[0003] Some aspects of this disclosure include apparatus and methods for facilitating the transmission of control messages in multi-beam communication.

[0004] In some aspects, a method for updating the Transmission Configuration Indication (TCI) state of multiple component carriers (CCs) may include identifying an update to the TCI state of a CC corresponding to a User Equipment (UE), wherein the CC has a serving cell ID. The method may include: determining, based on the update of the TCI state, a list of CCs including the CC to be updated; and generating a Media Access Control (MAC) element (CE) including the serving cell ID and bit values ​​instructing the UE to update the TCI state of the CCs in the CC list using the serving cell ID. The method may include transmitting the MAC CE to the UE. In some aspects, the method for updating the TCI state of multiple CCs may be implemented using a wireless communication system and / or a network access node, the 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 may be configured as an element to perform the method. The transceiver may communicate with the UE. In some aspects, a non-transitory computer-readable device may store instructions that, when executed by at least one computing device, cause the at least one computing device to perform an element of the method.

[0005] In some aspects, the method may also include transmitting a Radio Resource Control (RRC) message to the UE to configure the CC list.

[0006] In some respects, the method may also include indicating the bit value using a reserved bit of the MAC CE.

[0007] In some aspects, the method may also include the MAC CE including TCI status information to update the TCI status of the Physical Downlink Shared Channel (PDSCH).

[0008] In some respects, the method may also include CORESET information to update the TCI state of the Physical Downlink Control Channel (PDCCH).

[0009] In some respects, the method may also include the bit value being either the most significant bit (MSB) or the least significant bit (LSB) of the TCI status ID.

[0010] In some respects, the method may also include modifying the bit value of a TCI code point having multiple TCI states.

[0011] In some aspects, a method for updating the spatial relationships of sounding reference signals (SRS) for multiple component carriers (CCs) may include identifying updates to the spatial relationships of a set of SRS resources corresponding to the CCs. The method may include determining whether the periodicity of the SRS resource set is aperiodic or periodic. The method may include generating a Media Access Control Element (MAC CE) including bit values ​​in an activation / deactivation bit field that instruct a User Equipment (UE) to update the spatial relationships of CCs in a list of CCs that includes the CC. The method may include transmitting the MAC CE to the UE. In some aspects, the method for updating the spatial relationships of the SRS for multiple CCs may be implemented using a wireless communication system and / or a network access node, the 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 may be configured as an element to perform the method. The transceiver may communicate with the UE. In some aspects, a non-transitory computer-readable device may store instructions that, when executed by at least one computing device, cause the at least one computing device to perform an element of the method.

[0012] In some respects, the method may also include resources in the SRS resource set having the same time-domain pattern.

[0013] In some aspects, the method may further include a second update identifying the spatial relationship of the SRS resource set corresponding to the CC. The method may further include determining that the temporal mode of the SRS resource set corresponding to the second update is semi-persistent. The method may further include: generating a second MAC CE, the second MAC CE including bit values ​​in a reserved bit field indicating that the UE updates the spatial relationship of the CC according to the second update; and transmitting the second MAC CE to the UE.

[0014] In some respects, the value of this bit in the reserved bit field indicates that the UE updates the spatial relationship of the CCs in the CC list that includes the CC.

[0015] In some aspects, the method may further include: identifying a second update of the spatial relationship of SRS resources corresponding to the CC, wherein the CC has an SRS resource cell ID. The method may further include determining, based on the update of the spatial relationship, a list of CCs including the CC to be updated. The method may further include: generating a second MAC CE including the SRS resource cell ID and bits instructing the UE to update the spatial relationship of CCs in the CC list using the SRS resource cell ID; and transmitting the second MAC CE to the UE.

[0016] In some respects, the method may also include a second MAC CE with a length of four octets.

[0017] In some aspects, a method for configuring Transmission Configuration Indicator (TCI) code points for a Physical Downlink Shared Channel (PDSCH) may include identifying the configuration of one or more TCI code points corresponding to a component carrier (CC) of a User Equipment (UE). The method may also include determining that at least one of the one or more TCI code points has multiple TCI states. The method may further include generating a Medium Access Control (MAC) element (CE) including a first value indicating the amount of the one or more TCI code points and a second value indicating the amount of the at least one TCI code point having multiple TCI states. For the at least one TCI code point having multiple TCI states, the method may further include updating the MAC CE to include bits indicating the presence of multiple TCI states. The method may further include transmitting the MAC CE to the UE. In some aspects, the method for configuring the TCI code points for the PDSCH may be implemented using a wireless communication system and / or a network access node, the 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 may be configured as an element performing 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 the method.

[0018] In some aspects, the method may also include the MAC CE comprising: a first octet of data including bits indicating the presence of multiple TCI states and a first TCI state ID; and a second octet of data including a second TCI state ID.

[0019] In some respects, the method may also include reserved bits in the second eight-bit byte data.

[0020] In some aspects, the method may also include the bit indicating to the UE that 8 bits of data following the first TCI state are related to the second TCI state.

[0021] In some aspects, the method may also include updating the MAC CE to include a second bit indicating the presence of a single TCI state among the one or more TCI code points.

[0022] In some respects, the method may also include the second bit indicating to the UE that the subsequent 7 bits of data are related to the single TCI state.

[0023] In some respects, the method may also include the subsequent 7 bits of data including a TCI status ID corresponding to the TCI code point.

[0024] In some aspects, a method for updating the Transmission Configuration Indicator (TCI) state of multiple component carriers (CCs) at a user equipment (UE) may include receiving a Radio Resource Control (RRC) message from a radio access node, the RRC message instructing the UE to configure a list of component carriers (CCs). The method may include receiving a Medium Access Control (MAC) element (CE) from the radio access node, the MAC CE including a serving cell ID corresponding to a component carrier (CC) in the list and a bit value instructing the UE to update the TCI state of the CC list. In response to identifying the bit value, the method may 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 the TCI state of multiple CCs may be implemented using a UE, the UE including a transceiver and at least one processor coupled to the transceiver. The at least one processor may be configured as an element performing the method. The transceiver may communicate with the radio access node. In some aspects, a non-transitory computer-readable device may store instructions that, when executed by at least one computing device, cause the at least one computing device to perform an element of the method.

[0025] In some respects, the method may also include indicating the bit value using a reserved bit of the MAC CE.

[0026] In some aspects, the method may also include the MAC CE including TCI status information to update the TCI status of the Physical Downlink Shared Channel (PDSCH).

[0027] In some respects, the method may also include CORESET information to update the TCI state of the Physical Downlink Control Channel (PDCCH).

[0028] In some respects, the method may also include the bit value being either the most significant bit (MSB) or the least significant bit (LSB) of the TCI status ID.

[0029] In some respects, the method may also include modifying the bit value of a TCI code point having multiple TCI states. Attached Figure Description

[0030] Figure 1 An exemplary system for transmitting control messages for multi-beam communication is shown, based on some aspects of its implementation.

[0031] Figure 2 A block diagram of an exemplary wireless system for transmitting control messages for multi-beam communication is shown, according to some aspects of the implementation.

[0032] Figure 3A A block diagram of a Media Access Control (MAC) control element (CE) for updating the Transmission Configuration Indicator (TCI) status of the Physical Downlink Shared Channel (PDSCH) is shown, based on several aspects.

[0033] Figure 3B A block diagram of a MAC CE for updating the Transmission Configuration Indicator (TCI) status of the Physical Downlink Control Channel (PDCCH) is shown, based on several aspects.

[0034] Figure 4 A block diagram of MACCE for activating and deactivating the probe reference signal (SRS) resource set is shown, based on several aspects.

[0035] Figure 5 A block diagram of MACCE for updating the spatial relationships of probe reference signal (SRS) resources is shown.

[0036] Figure 6A A block diagram of a MAC CE for configuring TCI code points for a PDSCH to support multiple transmit receiver points (multiple TRP) operation is shown, based on several aspects.

[0037] Figure 6B A block diagram of an exemplary MAC CE is shown, indicating multiple TCI states based on several aspects.

[0038] Figure 7 A flowchart is shown showing the TCI status for updating the component carrier (CC) list of user equipment (UE) based on several aspects.

[0039] Figure 8A A flowchart is shown illustrating the spatial relationships of SRS resource sets with different periodicities, based on several aspects used to generate MAC CEs.

[0040] Figure 8BA flowchart is shown illustrating the spatial relationships used to modify the MAC CE to update the CC list, based on several aspects.

[0041] Figure 8C A flowchart is shown illustrating the spatial relationships used to generate a MAC CE to update SRS resources based on several aspects.

[0042] Figure 9 A flowchart is shown for configuring TCI code points for PDSCH to support multiple transmit receiver points (multiple TRP) operation, based on several aspects.

[0043] Figure 10 An exemplary computer system is shown that can be used to implement various aspects.

[0044] The features and advantages of the aspects will become more apparent when viewed in conjunction with the accompanying drawings, in which similar reference characters consistently identify corresponding elements. In the drawings, similar reference numerals generally denote identical, functionally similar, and / or structurally similar elements. The first appearance of an element in the drawing is indicated by the leftmost digit of the corresponding reference numeral. Detailed Implementation

[0045] The following detailed description relates to the accompanying drawings. The same reference numerals may be used in different drawings to identify the same or similar elements. In the following description, specific details, such as particular structures, architectures, interfaces, technologies, etc., are set forth for illustrative and not limiting purposes in order to provide a thorough understanding of all aspects of the subject matter. However, it will be apparent to those skilled in the art that all aspects of the subject matter may be practiced in other examples departing from these specific details. In some cases, descriptions of well-known devices, circuits, and methods have been omitted so as not to obscure the description of the subject matter with unnecessary detail. For the purposes of this document, the phrase "A or B" means (A), (B), or (A and B).

[0046] This disclosure relates to communication between nodes and user equipment (UEs) using 5G wireless communication protocols. For example, the node could be a gNB or ng-eNB node. As part of the 5G standard development, the 3rd Generation Partnership Project (3GPP) has released several documents detailing meeting minutes and development. One such document is referred to as Version 16 (Rel-16).

[0047] Rel-16 provides some descriptions of multi-beam and multiple-input multiple-output (MIMO) communications between nodes and UEs. These communications can utilize multiple transmit and receive antennas to take advantage of multipath propagation. One concept describing these multi-beam communication relationships is "quasi-cooperative localization," or QCL. QCL refers to the detected relationship between multiple signals received from the transmitting antenna array. Specifically, if the properties of the channel transmitting symbols on one antenna port can be inferred from the channel transmitting symbols on another antenna port, then the two antenna ports can be quasi-cooperatively localized.

[0048] To provide an example of this QCL, an example illustrating quasi-cooperative localization (QCL) of signal A and another signal B will be described. For example, a node may transmit signals A and B to a UE using an antenna array or a common transmit / receive point (TRP) from that node. These signals may be reference signals. The same spatial filter may have been applied to the signals. As the signals propagate from the node to the UE, they also propagate through similar channel conditions and experience similar channel properties. Because signals A and 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 characteristics may include, for example, Doppler shift, Doppler spread, average delay, delay spread, and / or other channel effects. Given these issues, if the UE can detect one of the signals and determine the channel properties, this information may help in detecting the other signal. When the UE is able to perform this detection, signals A and B are referred to as quasi-cooperative localization (QCL).

[0049] To help the UE identify QCL signals, Transmission Configuration Indicator (TCI) status information can be transmitted from the node to the UE. The TCI status includes information such as the QCL relationships between different reference signals and / or downlink reference signals. For example, the TCI status can be transmitted in a downlink control information (DCI) message, which describes the QCL relationships of the Channel State Information Reference Signal (CSI-RS) and / or Demodulation Reference Signal (DMRS) sets. The TCI status information may include parameters for the UE to configure the QCL relationships between downlink reference signals of the Physical Downlink Shared Channel (PDSCH) and / or Physical Downlink Control Channel (PDCCH).

[0050] While this TCI state information can facilitate more reliable communication between nodes and the UE, several issues arise when providing this information to the UE. For example, the TCI state may change, and the node may need to update the TCI state information at the UE. Similarly, the UE may need to initially update its TCI state information when communicating with a node. Changes in TCI state information can apply to many different signals or reference signals and / or many different frequency blocks or component carriers (CCs). This update becomes more complex in situations with multiple transmit / receive points (TRPs) or multiple nodes communicating with a particular UE. This situation can introduce overhead and latency issues from nodes sending numerous messages to the UE to update the TCI state and / or spatial relationships of different reference signals and CCs.

[0051] In light of these issues, the aspects described herein reduce the amount of control messages transmitted for updating TCI states to reduce message transmission overhead and latency. Specifically, these aspects describe the use of Media Access Control Control Elements (MAC CEs) to update the TCI states of the CC list. This update is also applicable to multi-TRP scenarios. MAC CEs also allow updating spatial relationship information for Sounding Reference Signal (SRS) resources and / or different SRS resource sets with different periodicity and / or time-domain patterns. Furthermore, MAC CEs can be used to configure TCI code points with multiple TCI states. Using these MAC CE designs reduces the number of messages and / or MAC CEs, providing more efficient TCI state updates and / or reducing latency.

[0052] The various aspects of these features will now be discussed with reference to the corresponding figures.

[0053] Figure 1 An exemplary system 100 for transmitting control messages for multi-beam communication is shown, according to some aspects of its implementation. Figure 1 An exemplary system architecture 100 of a network is illustrated according to various aspects. The following description is provided for an example system 100 operating in combination with LTE system standards and 5G or NR system standards provided by 3GPP technical specifications. However, the exemplary aspects are not limited in this respect, and said aspects can be applied to other networks that benefit from the principles described herein, such as future 3GPP systems (e.g., sixth generation (6G)) systems, IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), etc.

[0054] like Figure 1As shown, system 100 includes UE 110A and UE 110B (collectively referred to as "UE 110" or "UE 110"). In this example, multiple UE 110s are shown as smartphones (e.g., handheld touchscreen mobile computing devices that can connect to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as consumer electronics devices, mobile phones, smartphones, feature phones, tablets, wearable computing devices, personal digital assistants (PDAs), pagers, wireless handheld devices, desktop computers, laptops, in-vehicle infotainment (IVI), in-vehicle entertainment (ICE) devices, instrument cluster (IC), head-up display (HUD) devices, onboard diagnostic (OBD) devices, dashtop mobile equipment (DME), mobile data terminal (MDT), electronic engine management system (EEMS), electronic / engine control unit (ECU), electronic / engine control module (ECM), embedded systems, microcontrollers, control modules, engine management system (EMS), connected or "smart" appliances, MTC devices, M2M, IoT devices, etc.

[0055] UE 110 can be configured to connect to a RAN, including Radio Access Network (RAN) nodes 120A and 120B, for example, through communication coupling. In various respects, 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 terms “NG RAN” or “next-generation RAN” can refer to a RAN operating in an NR or 5G system 100, while the terms “E-UTRAN” can refer to a RAN operating in an LTE or 4G system 100. UE 110 can utilize connections (or channels) individually, each of which includes a physical communication interface or layer (discussed in further detail below). In some respects, UE 110 can communicate with one or more RAN nodes 120.

[0056] In this example, the connection is shown as an air interface for communication coupling and can be consistent with cellular communication protocols such as GSM, CDMA, PTT, POC, UMTS, 3GPP LTE, 5G, NR, and / or any other communication protocols discussed herein. In all respects, UE 110 can directly exchange communication data via the ProSe interface. The ProSe interface may also be referred to as the SL interface and may include one or more logical channels, including but not limited to PSCCH, PSSCH, PSDCH, and PSBCH.

[0057] UE 110A can be configured as an Access Point (AP) (also known as a "WLAN node," "WLAN," "WLAN terminal," "WT," etc.). Connections can include local wireless connections, such as those conforming to any IEEE 802.11 protocol, where the AP will include a Wi-Fi® router. In this example, the AP is shown connected to the Internet but not to the core network of the wireless system (described in further detail below). In various aspects, UE 110A, the RAN, and the AP can be configured to utilize LWA operation and / or LWIP operation. LWA operation may involve RAN nodes 120A and 120B configuring UE 110A, in the RRC_CONNECTED state, to utilize the radio resources of LTE and WLAN. LWIP operation may involve UE 110A using WLAN radio resources via IPsec protocol tunneling to authenticate and encrypt packets (e.g., IP packets) transmitted over the connection. IPsec tunneling may include encapsulating the entire original IP packet and adding a new packet header to protect the original header of the IP packet.

[0058] RAN may include one or more AN nodes or RAN nodes 120A and 120B (collectively referred to as "multiple RAN nodes 120" or "RAN node 120"). As used herein, the terms "access node," "access point," "AN," "RAN node," etc., can describe equipment that provides radio baseband functionality for data and / or voice connections between the network and one or more users. These access nodes may be referred to as BS, gNB, RAN node, eNB, NodeB, RSU, TRxP, or TRP, etc., and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). As used herein, the terms "NG RAN node," etc., can refer to RAN node 120 (e.g., gNB) operating in NR or 5G system 100, while the terms "E-UT RAN node," etc., can refer to RAN node 120 (e.g., eNB) operating in LTE or 4G system 100. Depending on the specifics, RAN node 120 may be implemented as one or more of dedicated physical devices such as macro cell base stations and / or low-power (LP) base stations for providing smaller coverage areas, smaller user capacity, or higher bandwidth compared to macro cells.

[0059] In some aspects, all or part of the RAN node 120 may be implemented as one or more software entities running on a server computer as part of a virtual network, which may be referred to as CRAN and / or Virtual Baseband Unit Pool (vBBUP). In these aspects, CRAN or vBBUP may implement RAN function partitioning, such as PDCP partitioning, where the RRC and PDCP layers are operated by CRAN / vBBUP, while other L2 protocol entities are operated by the individual RAN nodes 120; MAC / PHY partitioning, where the RRC, PDCP, RLC, and MAC layers are operated by CRAN / vBBUP, and the PHY layer is operated by the individual RAN nodes 120; or "lower PHY" partitioning, where the upper portion of the RRC, PDCP, RLC, MAC, and PHY layers is operated by CRAN / vBBUP, while the lower portion of the PHY layer is operated by the individual RAN nodes 120. This virtualization framework allows the idle processor cores of the RAN node 120 to execute other virtualized applications. In some specific implementations, the individual RAN nodes 120 may represent via various F1 interfaces (… Figure 1 (Not shown) Individual gNB-DUs connected to the gNB-CU. In these specific implementations, the gNB-DU may include one or more remote radio head units or RFEMs, and the gNB-CU may be operated by a server (not shown) located in the RAN or by a server pool in a manner similar to CRAN / vBBUP. Alternatively or additionally, one or more RAN nodes in RAN node 120 may be next-generation eNBs (ng-eNBs), which are RAN nodes that provide E-UTRA user plane and control plane protocol terminals to UE 110 and are connected to the 5GC via the NG interface (discussed below).

[0060] In a V2X scenario, one or more of the multiple RAN nodes 120 can be or act as an RSU. The term "roadside unit" or "RSU" can refer to any traffic 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, wherein an RSU implemented in or by a UE can be referred to as a "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 so on. In one example, an RSU is a computing device coupled to radio frequency circuitry located on the roadside that provides connectivity support to passing vehicle UE 110 (vUE 110). An RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicle and pedestrian traffic. The RSU may operate on the 5.9 GHz Direct Near Range Communication (DSRC) band to provide extremely low-latency communication required for high-speed events, such as collision avoidance and traffic warnings. Alternatively, the RSU may operate on the cellular V2X band to provide the aforementioned low-latency communication as well as other cellular communication services. Alternatively, the RSU may operate as a Wi-Fi hotspot (2.4 GHz band) and / or provide connectivity to one or more cellular networks to provide uplink and downlink communication. Some or all of the computing device and the RSU's radio frequency circuitry may be packaged in a weather-resistant package suitable for outdoor installation and may include a network interface controller to provide wired connectivity (e.g., Ethernet) to traffic signal controllers and / or backhaul networks.

[0061] Any node in RAN 120 can serve as the endpoint of the air interface protocol and can be the first point of contact for UE 110. In some respects, any node in RAN 120 can perform various logical functions of the RAN, including but not limited to Radio Network Controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0062] In various respects, UE 110 may be configured to communicate with each other or with any of the RAN nodes 120 on a multi-carrier communication channel using OFDM communication signals, based on various communication technologies such as, but not limited to, OFDMA communication technology (e.g., for downlink communication) or SC-FDMA communication technology (e.g., for uplink and ProSe or sidelink communication), but the scope of these respects is not limited in this respect. OFDM signals may include multiple orthogonal subcarriers.

[0063] In some respects, the downlink resource grid can be used for downlink transmissions from any node in RAN 120 to UE 110, while uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid, called a resource grid or time-frequency resource grid, which represents the physical resources in the downlink within each time slot. This time-frequency plane representation is common practice for OFDM systems, making radio resource allocation intuitive. Each column and row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid comprises multiple resource blocks that describe the mapping of certain physical channels to resource elements. Each resource block comprises a set of resource elements; in the frequency domain, this can represent the minimum amount of resources currently available for allocation. Such resource blocks are used to transmit several different physical downlink channels.

[0064] Depending on the specifics, UE 110 and RAN node 120 transmit data (e.g., transmit and receive data) through licensed media (also referred to as “licensed spectrum” and / or “licensed band”) and unlicensed shared media (also referred to as “unlicensed spectrum” and / or “unlicensed band”). Licensed spectrum may include channels operating in the frequency range of approximately 400 MHz to approximately 3.8 GHz, while unlicensed spectrum may include a 5 GHz band.

[0065] To operate in unlicensed spectrum, UE 110 and RAN node 120 may use LAA, eLAA, and / or feLAA mechanisms. In these specific implementations, UE 110 and RAN node 120 may perform one or more known medium sensing and / or carrier sensing operations to determine whether one or more channels in the unlicensed spectrum are unavailable or otherwise occupied before transmission in the unlicensed spectrum. Medium / carrier sensing operations may be performed according to a Listen-After-Speak (LBT) protocol.

[0066] LBT is a mechanism that equipment (e.g., multiple UEs 110, multiple RAN nodes 120, etc.) uses to sense a medium (e.g., a channel or carrier frequency) and transmit 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 may include CCA, which utilizes at least ED to determine the presence of other signals on the channel in order to determine whether the channel is occupied or idle. This LBT mechanism allows cellular / LAA networks to coexist with existing systems in unlicensed spectrum and with other LAA networks. ED may include sensing RF energy in the intended transmission band over a period of time and comparing the sensed RF energy with predefined or configured thresholds.

[0067] Typically, existing systems in the 5GHz band are WLANs based on IEEE 802.11 technology. WLANs employ a contention-based channel access mechanism called CSMA / CA. Here, when a WLAN node (e.g., a mobile station (MS) such as UE 110, AP, etc.) intends to transmit, the WLAN node can first perform CCA before transmitting. Additionally, in cases where more than one WLAN node senses the channel as idle and transmits simultaneously, a backoff mechanism is used to avoid collisions. This backoff mechanism can be a counter randomly introduced within the CWS, which increases exponentially upon collision and resets to a minimum value upon successful transmission. The LBT mechanism designed for LAA is somewhat similar to WLAN's CSMA / CA. In some specific implementations, the LBT process for DL ​​or UL transmission bursts (including PDSCH or PUSCH transmissions) can have a variable-length LAA contention window between X and Y ECCA time slots, where X and Y are the minimum and maximum values ​​of the LAA's CWS. In one example, the minimum CWS for LAA transmission can be 9 microseconds (µs); however, the size of the CWS and MCOT (e.g., transmission burst) can be based on government regulatory requirements.

[0068] The LAA mechanism is built upon the CA technology of LTE-Advanced systems. In CA, each aggregated carrier is called a CC. A CC can have a bandwidth of 1.4, 3, 5, 10, 15, or 20 MHz, and a maximum of five CCs can be aggregated, thus the maximum aggregated bandwidth is 100 MHz. In FDD systems, the number of aggregated carriers can differ for DL ​​and UL, where the number of UL CCs is equal to or less than the number of DL component carriers. In some cases, individual CCs can have different bandwidths than the other CCs. In TDD systems, the number of CCs and the bandwidth of each CC are usually the same for DL ​​and UL.

[0069] The CA also includes individual serving cells to provide individual CCs. The coverage of serving cells can differ, for example, because CCs on different frequency bands will experience different path losses. The primary serving cell, or PCell, provides the PCC for both UL and DL and handles activities related to RRC and NAS. Other serving cells are called SCells, and each SCell provides individual SCCs for both UL and DL. SCCs can be added and removed as needed, while changing the PCC may require the UE to undergo a handover. In LAA, eLAA, and feLAA, some or all of the SCells can operate in unlicensed spectrum (called "LAA SCells"), and LAA SCells are assisted by PCells operating in licensed spectrum. When a UE is configured to have more than one LAA SCell, the UE can receive UL grants on the configured LAA SCells, indicating different PUSCH start positions within the same subframe.

[0070] The PDSCH carries user data and higher-layer signaling to multiple UEs 110. Among other information, the PDCCH carries information about the transmission format and resource allocation related to the PDSCH channel. It can also inform multiple UEs 110 about the transmission format, resource allocation, and HARQ information related to the uplink shared channel. Typically, downlink scheduling (allocating control and shared channel resource blocks to UEs 110A within the cell) can be performed on any of the multiple RAN nodes 120 based on channel quality information fed back from any of the multiple UEs 110. Downlink resource allocation information can be transmitted on the PDCCH used for (e.g., allocated to) each of the UEs 110.

[0071] PDCCH uses CCEs to transmit control information. Before being mapped to resource elements, the complex-valued symbols of the PDCCH can first be organized into quadruplets, which can then be arranged using a sub-block interleaver for rate matching. One or more of these CCEs can be used to transmit each PDCCH, where each CCE can correspond to nine sets, called REGs, each with four physical resource elements. Four Quadrature Phase Shift Keying (QPSK) symbols can be mapped to each REG. Depending on the DCI size and channel conditions, one or more CCEs can be used to transmit the PDCCH. Four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation level, L=1, 2, 4, or 8) can exist.

[0072] In some aspects, the concept of resource allocation can be applied to control channel information, where the concept of resource allocation is an extension of the above-mentioned concepts. For example, some aspects can utilize EPDCCH that uses PDSCH resources for control information transmission. One or more ECCEs can be used to transmit EPDCCH. Similarly, each ECCE can correspond to a set of nine, each consisting of four physical resource elements, called EREG. In some cases, an ECCE can have a different number of EREGs.

[0073] RAN nodes 120 can be configured to communicate with each other via an interface. In all aspects of system 100 being 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 connected to the EPC (e.g., two or more eNBs, etc.), and / or between two eNBs connected to the EPC. In some specific implementations, the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). X2-U can provide flow control mechanisms for user packets transmitted via the X2 interface and can be used to transmit information about the delivery of user data between eNBs. For example, X2-U can provide specific sequence number information about user data transmitted from the MeNB to the SeNB; information about the successful in-order delivery of PDCP PDUs from the SeNB to the UE 110 for user data; information about PDCP PDUs not delivered to the UE 110; information about the current minimum expected buffer size at the SeNB for transmitting user data to the UE; and so on. The X2-C provides LTE intra-eNB access mobility functions, including context transmission from the source eNB to the destination eNB, user plane transmission control, load management functions, and inter-cell interference coordination functions.

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

[0075] The RAN is shown communicatively coupled to the core network—in this respect, communicatively coupled to the core network (CN) 120. CN 140 may include multiple network elements 130 configured to provide various data and telecommunications services to customers / subscribers (e.g., users of UE 110) connected to CN 140 via the RAN. Components of CN 140 may be implemented in a single physical node or individual physical nodes, including components for reading and executing instructions from machine-readable or computer-readable media (e.g., non-transitory machine-readable storage media). In some aspects, NFV can be used to virtualize any or all of the aforementioned network node functions via executable instructions stored in one or more computer-readable storage media (described in further detail below). A logical example of CN 140 may be referred to as a network slice, and a logical example of a portion of CN 140 may be referred to as a network subslice. NFV architectures and infrastructure can be used to virtualize one or more network functions onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches (optionally implemented by proprietary hardware). In other words, an NFV system can be used to perform a virtual or reconfigurable concrete implementation of one or more EPC components / functions.

[0076] Generally, application server 150 can be a component that provides IP bearer resources for applications to use with the core network (e.g., UMTS PS domain, LTE PS data service, etc.). Application server 150 can also be configured to support one or more communication services for UE 110 via CN 140 (e.g., VoIP sessions, PTT sessions, group communication sessions, social networking services, etc.).

[0077] In all respects, CN 140 can be a 5GC, and RAN can be connected to CN 140 via the NG interface. In all respects, the NG interface can be divided into two parts: the NG user plane (NG-U) interface, which carries traffic data between RAN node 120 and UPF; and the S1 control plane (NG-C) interface, which is the signaling interface between RAN node 120 and AMF.

[0078] Figure 2 A block diagram of an exemplary wireless system 200 for implementing control message transmission for multi-beams is shown. For convenience and not limitation, alternative methods may be used. Figure 1 The elements used to describe system 200. System 200 can be Figure 1The system 200 may include a processor 210, a transceiver 220, a communication infrastructure 230, a memory 235, and an antenna 225, which together 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 may be a bus. The memory 235 may include random access memory (RAM) and / or a cache, and may include control logic (e.g., computer software), computer instructions, and / or data. When executing computer instructions, the processor 210 may be configured to perform the functions described herein for group-based reporting beam management. Alternatively, the processor 210 may include its own internal memory (not shown), and / or may be “hardwired” (as in a state machine) configured to perform the functions described herein for group-based reporting beam management. The antenna 225 coupled to the transceiver 220 may include one or more antennas, an antenna array, and / or may be panels of the same or different types to enable wireless communication over a wireless network.

[0079] In some aspects, RAN node 120 may utilize components of wireless system 200. According to some aspects, processor 210 implements control message transmission for multi-beam communication, either alone or in combination with memory 235 and / or transceiver 220. For example, system 200 may generate Media Access Control (MAC) CEs and transmit these MACCEs to the UE using transceiver 220 and / or antenna 225. The UE receiving the MAC CEs may then update the TCI state information of the communication channels. For example, these MAC CEs may update one or more component carriers (CCs) of PDSCH and / or PDCCH. MAC CEs may also update the spatial relationships of SRS resource sets with different periodicities. TCI states and / or TCI code points may also be updated to support multiple TRP operations.

[0080] Figure 3A A block diagram of a Media Access Control (MAC CE) 300A for updating the Transmission Configuration Indicator (TCI) state of the Physical Downlink Shared Channel (PDSCH) is shown, based on several aspects. As will be further described below, a reserved bit 302 of the MAC CE 300A can be used to indicate whether the list of component carriers (CCs) should be updated based on the updated TCI state. The use of the reserved bit 302 allows multiple TCI states of the PDSCH to be updated using a single MAC CE 300A. The MAC CE 300A is designed to provide simultaneous updates of multiple TCI states and offer overhead savings and reduced latency, rather than using multiple MAC CEs to update the TCI states individually.

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

[0082] Octaves 308, 310, and 312 may include TCI status information indicating whether the TCI status is active or deactivated. For a specific value “Ti”, this field can be set to “1” to indicate that the TCI status is active and mapped to a code point specified in a downlink control information (DCI) message. If this field is set to “0”, the TCI status may be deactivated and may not be mapped to a DCI message. The code point to which the TCI status is mapped can be determined by its sequence number position in the bitmap of the MAC CE 300A.

[0083] The reserved bit 302 can be used to indicate whether the MAC CE 300A updates a single CC or a list of CCs, rather than reserving it for use. A CC can be a frequency block allocated to a specific UE to increase the data rate. CCs can be grouped through 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, CCs can be contiguous or discontinuous within the frequency range. As previously mentioned, each CC can have a corresponding serving cell ID 304.

[0084] In some aspects, when reserved bit 302 is not set or is set to zero, the node may indicate to the UE that MAC CE 300A is being used to update the TCI status of the CC indicated by serving cell ID 304. Conversely, when reserved bit 302 is set or is set to a value, the node may indicate to the UE that MAC CE 300A is being used to update the CC list. This CC list may be configured by Radio Resource Control (RRC) messages and may correspond to the indicated serving cell ID 304. When reserved bit 302 is set, the UE may update the TCI status information of each cell in the same CC list configured by the RRC message. The UE may identify the setting value of reserved bit 302, identify the serving cell ID 304, and then update each CC in the list that includes serving cell ID 304 in the manner indicated by octet bytes 308, 310, 312. In some aspects, the bit setting of reserved bit 302 may be reversed, where a value indicates a single CC update and a zero value indicates updating the entire CC list.

[0085] Using MAC CE 300A in this manner allows nodes to instruct the UE to update the TCI status of multiple CCs using fewer control messages. The use of reserved bit 302 allows for simultaneous updates to the CC list. This update facilitates multi-beam communication and provides flexibility for updating a single CC and / or multiple CCs. The updated TCI status information helps update the TCI status of the PDSCH.

[0086] Figure 3B A block diagram of the MAC CE 300B for updating the Transmission Configuration Indicator (TCI) state of the Physical Downlink Control Channel (PDCCH) is shown, based on several aspects. Similar to the MAC CE 300A, reserved bits in the MAC CE 300B can be used to indicate whether the component carrier (CC) list should be updated based on the updated TCI state. The use of these reserved bits allows multiple TCI states of the PDCCH to be updated using a single MAC CE 300B. The MAC CE 300B is designed to provide simultaneous updates of multiple TCI states and offer overhead savings and reduced latency, rather than using multiple MAC CEs to update the TCI states individually.

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

[0088] Although seven bits are reserved for TCI status ID 318, RRC messages can be configured to capture up to 64 TCI statuses. Due to this configuration, even though seven bits are reserved for TCI status ID 318, six bits can be used to capture 64 TCI statuses. In this way, one bit may be unused in TCI status ID 318. Similar to the MAC CE 300A, this bit can be used to indicate whether the CC list should be updated, rather than not using this bit. Specifically, the most significant bit (MSB) or least significant bit (LSB) of the TCI status ID 318 field can be used to indicate whether the CC list should be updated for the TCI status.

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

[0090] Using MAC CE 300B in this manner allows nodes to instruct the UE to update the TCI status of multiple CCs with fewer control messages. The use of unused bits in TCI status ID 318 allows for simultaneous updates to the CC list. This update facilitates multi-beam communication and provides flexibility for updating a single CC and / or multiple CCs. The updated TCI status information also helps update the TCI status of the PDCCH.

[0091] In some respects, another MAC CE can be defined to provide TCI state information for PDSCHs that include one or two TCI states. For example, this could be a multi-TRP scenario. In this case, the UE may be communicating with multiple nodes, which could lead to the activation of two TCI states. The network can use this MAC CE to update the TCI code points of the PDSCH in the CC list. The updated TCI code points can be applied to a list corresponding to the serving cell ID, as referenced. Figure 3A and Figure 3B As described, the application of updated TCI code points can indicate that multiple TRP operations are activated and / or deactivated for CCs in the list.

[0092] In some respects, updated TCI code points can be applied to a subset of CCs in the CC list based on different conditions. CCs that satisfy one or more of these conditions can be updated. These conditions may include: - CC is configured with at least one CORESET with no value for CORESETPoolIndex or with CORESETPoolIndex set to zero, or at least one CORESET with CORESETPoolIndex set to one.

[0093] - CC in PDSCH-TimeDomainResourceAllocationRepSchemeEnabler At least one entry is configured with RepNum16 .

[0094] - CC configuration has RepSchemeEnabler .

[0095] These conditions can be helpful in updating the TCI state during multi-TRP operations. By using one or more of these conditions, the UE can control the updating of the TCI state even when multiple TCI states correspond to a specific TCI code point.

[0096] Figure 4A block diagram of a MACCE 400 for activating and deactivating Sounding Reference Signal (SRS) resource sets is shown, based on several aspects. A node can transmit the MAC CE 400 to a UE to indicate spatial relationships for the UE to transmit SRS resource sets. The MAC CE 400 can be used to activate and / or deactivate semi-persistent (SP) SRS resource sets. The MAC CE 400 can also be configured to provide spatial relationship data for other periodicity, such as aperiodic or periodic SRS resource sets. Using the MAC CE 400, the UE can update its spatial relationship information when transmitting SRS signals to a node.

[0097] SRS is a reference signal used in the uplink direction from the UE to the node to help the node obtain Channel State Information (CSI) for each UE. CSI describes how the signal propagates from the UE to the node and can represent the effects of scattering, fading, power attenuation with distance, and / or other channel elements. The node can use SRS for resource scheduling, link adaptation, MIMO communication, and / or beam management. UEs can use different periodicities to transmit SRS. For example, different periodicities can be "periodic," "aperiodic," and / or "semi-persistent" (SP). SRS can be identified as SRS resources, which can refer to the location of the SRS in the resource grid in the time and frequency domains. An SRS resource set can refer to the number of SRS resources transmitted at different symbols.

[0098] Given this description and SRS organization, a node can generate MAC CE 400 to update the spatial relationships of the SRS resource set at the UE. Although Figure 4 An exemplary MAC CE 400 for controlling SP SRS resource sets is depicted, but the MAC CE 400 can also be configured to provide spatial relationship updates for both aperiodic and periodic SRS resource sets. In this way, the MAC CE 400 can support spatial relationship updates for different periodicities. As will be further explained below, the MAC CE 400 can also support updates to the spatial relationships of CC lists.

[0099] For SRS resource set scenarios, MAC CE 400 may include an "Activate or Deactivate" (A / D) bit 402, which is used to activate or deactivate the SRS resource set indicated by SRS resource set ID 412. The SP SRS resource set ID 412 may be four bits long. MAC CE 400 may also include a cell ID 408 for the SRS resource set, which indicates the identity of the serving cell or CC that includes the activated or deactivated SP SRS resource set. The cell ID 408 for the SRS resource set may be five bits long. MAC CE 400 may also include a BWP ID 410 for the SRS resource set, which indicates the uplink bandwidth portion that includes the activated or deactivated SR SRS resource set. The BWP ID 410 for the SRS resource set may be two bits long.

[0100] MAC CE 400 may include SUL bit 420. This field indicates whether MAC CE 400 is configured for NUL or SUL carriers. SUL bit 420 can be set to... A "1" indicates that MAC CE 400 is suitable for SUL carrier configuration. SUL bit 420 can be set to "0" to indicate that MAC CE 400 is suitable for NUL carrier configuration.

[0101] The “C” bit 418 and the other eight-bit bytes will now be described. The MAC CE 400 may also include a “C” bit 418, which indicates the presence of the eight-bit bytes containing the Resource Serving Cell ID fields 430, 436 and the Resource BWP ID fields 428, 434. If this field is set to “1”, the eight-bit bytes containing the Resource Serving Cell ID fields 430, 436 and the Resource BWP ID fields 428, 434 are present. If this field is set to “0”, they are not present, and the Resource ID... i The resources indicated in fields 414 and 426 may be located on the serving cell and BWP indicated by cell ID 408 of the SRS resource set and BWP ID 410 of the SRS resource set.

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

[0103] Resource ID fields 414 and 426 may include identifiers for resources used in spatial relation derivation of SRS resource i. Resource ID fields 414 and 426 may indicate a specific reference signal to be used. For example, resource ID 0 may refer to the first SRS resource within the resource set. If F i If set to "0" and the first digit of the Resource ID field is set to "1", then the remainder of the field includes the SSB-index. If F i If the field is set to "0" and the first digit is set to "0", then the remaining part of the field includes... SRS- ResourceId The resource ID field, 414, and 426, can be seven characters long.

[0104] Resource Serving Cell ID fields 430 and 436 indicate the identity of the serving cell in which the resource is located, as used for spatial relation deduction of SRS resource "i". The field length can be five bits. Resource BWP ID fields 428 and 434 may include the BWP-ID of the uplink bandwidth portion in which the resource is located, as used for spatial relation deduction of SRS resource "i". The field length can be two bits.

[0105] Although the MAC CE 400 may also include reserved bits 404 and 416, these reserved bits 404 and 416 can be used to support different SRS resource set periodicity and / or indicate whether the spatial relationship of the CC list is updated.

[0106] 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 periodic, non-periodic, or semi-persistent SRS resource sets, rather than being limited to the semi-persistent case. The MAC CE 400 may also include an indication of whether a specific CC indicated by the cell ID 408 of the SRS resource set should be updated, or whether the list of CCs should be updated.

[0107] When the SRS Resource Set ID field 412 indicates that the SRS resource set is aperiodic or periodic, the UE may ignore the "A / D" bit 402. That is, the "A / D" bit 402 may not indicate an active or deactivated SRS resource set, or the SRS resource set corresponding to the SRS Resource Set ID field 412. Instead, the "A / D" bit 402 can be used to indicate whether a spatial relationship update applies to the cell ID 408 of a specific SRS resource set or to a CC list found in the same CC list as the indicated cell. This list update can be similar to reference... Figure 3A and Figure 3BThe description refers to list updates. In some respects, reserved bits 404 and 416 can be used instead of the "A / D" bit 402 to indicate whether a specific CC or the CC list should be updated. However, in either case, MAC CE 400 can be used to update spatial relationships for multiple SRS resource sets.

[0108] However, in the SP SRS resource set ID field 412 indicating that the SRS resource set is semi-persistent, the "A / D" bit 402 may have a value. In this case, reserved bits 404 and 416 can be used to indicate whether to update a specific CC or the list of CCs.

[0109] In some respects, when the MAC CE 400 is used to update the CC list, the SRS resource spatial relationships are updated when the corresponding SRS resource sets have the same time-domain pattern. For example, in some cases, CCs may have different time-domain patterns. In this case, the spatial relationships may not be applicable to updating the CC list. However, if 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 be applied to the CC list. However, due to differences in time-domain patterns, it may be necessary to update the beam at each resource level.

[0110] Figure 5 A block diagram of a MACCE 500 for updating spatial relationships of Sounding Reference Signal (SRS) resources is shown, based on several aspects. As mentioned above, while some scenarios may benefit from updating the entire set of SRS resources, others may benefit from updating individual SRS resources. For example, updating a specific SRS resource allows for precise location of the resource and updating specific 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 also be used to indicate whether spatial relationships should be updated for a specific CC or CC list. In some aspects, the first 16 bits of the MAC CE 500 may indicate a specific SRS resource, while the last 16 bits may indicate the beam information being updated. The length of the MAC CE 500 can be four octets.

[0111] Specifically, MAC CE 500 may include reserved bits 502, 506, and 508, which can be used to indicate whether a spatial relationship update is for a CC specified by the cell ID 510 of the SRS resource, or whether the spatial relationship update is for a CC list. The updating of the CC list can be similar to reference... Figure 3A and Figure 3B The way it is described occurs. Similar to... Figure 4The cell ID 510 of an SRS resource can refer to the cell in which the SRS resource is located. The cell ID 510 of an SRS resource can correspond to a specific resource, rather than indicating a set of SRS resources. Similarly, the BWP ID 512 of an SRS resource can correspond to the BWP in which the SRS resource is located. The SRS resource ID 514 can be an identifier configured by an RRC message. SRS-ResourceID SUL 510 is similar to SUL 420, as shown in the reference. Figure 4 As described, the use of the cell ID 510, BWP ID 512, and / or SRS resource ID 514 of the SRS resource allows the UE to identify the specific SRS resource that the MAC CE 500 needs to update.

[0112] "C" bit 504 can also be similar to "C" bit 418, as shown in the reference. Figure 4 As described. Specifically, bit 504, "C", indicates the presence of two subsequent octets of bit information. In the MAC CE 500, these two octets provide information about the specific resource being updated. For example, resource ID 516 could be similar to resource IDs 414 and 426, as described in the reference. Figure 4 As described. Resource ID 516 can be the ID of a resource used for spatial relation updates. For example, Resource ID 516 can indicate a specific beam to be used. Resource Serving Cell ID 522 can be the cell ID in which the resource of the spatial relation resides. Resource BWP ID 518 can indicate the BWP ID in which the resource of the spatial relation resides.

[0113] The use of MAC CE 500 allows for specific updates to resources rather than resource sets. MAC CE 500 provides additional flexibility for updating spatial relationships. MAC CE 500 can also be used to update spatial relationships in CC lists to reduce message passing overhead and / or latency.

[0114] Figure 6A A block diagram of the MAC CE 600A, based on several aspects, for configuring TCI code points for the PDSCH to support multiple transmit receiver points (multiple TRP) operation. As previously explained, multiple TRP scenarios may occur when the UE communicates with more than one antenna array or node. In this case, each TCI code point may include one or two TCI states. In this way, the MAC CE 600A provides control messages to support multiple TRP operation and configure TCI code points for the PDSCH.

[0115] 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".

[0116] 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.

[0117] 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.

[0118] Using MAC CE 600A allows for flexible adaptation to TCI code points with one or two TCI states. Using the “C_i” bits 606 and 610, the UE may be able to decode the eight-bit byte to determine whether one or both TCI states should be updated. Furthermore, using reserved bits 602A, 604A, or 614A still allows for list updates to the CC to reduce overhead and latency.

[0119] Figure 6B A block diagram of an exemplary MAC CE 600B indicating multiple TCI states according to some aspects is shown. MAC CE 600B may be an exemplary aspect of MAC CE 600A. Similar to MAC CE 600A, MAC CE 600B may include reserved bits 602B, 604B, 614B, and serving cell ID 616B and BWP ID 620B. MAC CE 600B may provide examples of fields 618B and 622B with exemplary values.

[0120] For example, the MAC CE 600B can use bits similar to those in the TCI code point count field 618B (as in field 618A) to indicate the value "M" "4", as referenced. Figure 6A As described. Similarly, MAC CE 600B can indicate the value "2" in field 622B, which is similar to field 622A and can indicate the number of code points with two TCI states. In this case, the UE can identify the number of octets to be followed in the remaining transmission. Specifically, the UE can identify that two TCI code points will have two TCI states, and therefore will use four octets. The UE can use the "M" value to identify two remaining TCI code points with one TCI state, each TCI state will use one octet. Using this information, the UE can expect to receive six octets. The UE can then identify the values ​​of each "C_i" 632, 634, 638, and 640 to determine whether a particular TCI code point corresponds to one or two TCI states.

[0121] To further illustrate this example, “C_0” 632 can be a zero value, indicating a single TCI state. The TCI state ID (0,1) 644 then provides the state information for that TCI code point. When “C_0” 632 is identified as zero, the UE can identify the following 7 bits as associated with a single TCI state. “C_1” 634 can be a value, indicating the presence of two TCI states. In this way, TCI state ID (1,1) 646 and TCI state ID (1,2) 648 provide information for two TCI states. Reserved bit 636 can be used to maintain the octet configuration of the MAC CE 600B. When “C_1” 634 is identified as a value, the UE can identify the following 15 bits as associated with two TCI states. “C_1” 634 can be a value, indicating the presence of two TCI states. The UE can then identify “C_2” as having a zero value and indicating a single TCI state. Then, TCI status ID (2,1) 650 provides the status information for this TCI code point. For “C_3” 640, the UE can identify one value and two TCI states. TCI status ID (3,1) 652 and TCI status ID (3,2) 654 provide information for the two TCI states. Reserved bit 642 can be used to maintain the eight-bit byte configuration of MAC CE 600B.

[0122] Figure 7 A flowchart 700 is shown illustrating the TCI state for updating the component carrier (CC) list of a user equipment (UE) according to some aspects. In some aspects, a network (such as core network 140, network element 130, application server 150, node 120, and / or radio system 200) can execute flowchart 700. In some aspects, RAN node 120 can use flowchart 700 to generate a MAC CE and transmit it to the UE. Flowchart 700 should be described with reference to RAN node 120; however, flowchart 700 is not limited to this exemplary aspect. Flowchart 700 can be executed on any computing device, such as those described above. Figure 10 The described computer system and / or processing logic components may include hardware (e.g., circuitry, dedicated logic components, programmable logic components, microcode, etc.), software (e.g., instructions that execute on a processing device), or combinations thereof.

[0123] It should be understood that not all steps may be required to perform the disclosure provided herein. Furthermore, as those skilled in the art will understand, some of these steps may be performed simultaneously or in combination with… Figure 7 The different execution sequences are shown.

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

[0125] Updates may also affect one or more CCs. Similarly, updated TCI states can apply to PDSCH and / or PDCCH. In some respects, PDSCH updates can occur in multi-TRP scenarios where TCI code points have one or two TCI states. In this case, a subset of CCs in the CC list can be updated.

[0126] At 704, RAN node 120 can determine whether to update the CC list, including CCs, based on updates to the TCI status. This CC list may have been previously configured by Radio Resource Control (RRC) messages and may correspond to the indicated serving cell ID. For example, the RRC may have previously configured TCI-related parameters. RAN node 120 may have previously transmitted RRC messages to UE 110 to configure the CC list. Updates to the TCI status information may apply to other CCs in the list, which also includes CCs corresponding to the serving cell ID.

[0127] At 706, RAN node 120 can determine whether to update the CC list at UE 110. If the CC list is not updated and RAN node 120 intends to update the CC corresponding to the serving cell ID, RAN node 120 can generate a Media Access Control Element (MAC CE) at 708. This MAC CE may include the serving cell ID and a first value of the TCI state instructing UE 110 to use the serving cell ID to update the CC. For example, the first value may be zero. The MAC CE may also include TCI state information for updating the TCI state at UE 110. RAN node 120 can then transmit the MAC CE to UE 110 at 712. UE 110 can then use the TCI state information included in the MAC CE to update the CC corresponding to the serving cell ID.

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

[0129] The MAC CE generated from flowchart 700 can be similar to MAC CE 300A and 300B, as previously referenced. Figure 3A and Figure 3B As explained. For example, MAC CE 300A can be used to update the TCI status of PDSCH, while MAC CE 300B can be used to update the TCI status of PDCCH. Other values ​​may be included in the MAC CE and may have been previously referenced. Figure 3A and Figure 3B Describe it.

[0130] As previously mentioned, MAC CE can also be used for multiple TRP operations. Similarly, MAC CE can be applied when the CC list includes identified CCs. In some respects, a subset of CCs can be updated based on conditions as described above.

[0131] In some respects, flowchart 900 can be performed on one or more iterations based on changes to the TCI code point. For example, a first MAC CE can be used to update the TCI state, but a second MAC CE can then be used again to update the TCI state. Similarly, the second MAC CE can correspond to updates to the same TCI state or different TCI states. In this way, the aspects described with respect to flowchart 900 are not limited to a single MAC CE.

[0132] Figure 8A A flowchart 800A is shown for generating a MAC CE based on several aspects to update the spatial relationships of SRS resource sets with different periodicity and / or time-domain patterns. Figure 8B A flowchart 800B is shown illustrating the spatial relationships used to modify the MAC CE to update the CC list based on several aspects.

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

[0134] It should be understood that not all steps may be required to perform the disclosure provided herein. Furthermore, as those skilled in the art will understand, some of these steps may be performed simultaneously or in combination with… Figure 8A and Figure 8B The different execution sequences are shown.

[0135] At 802, RAN node 120 can identify updates to the spatial relationships of the sounding reference signal (SRS) resource set corresponding to the component carrier (CC). The spatial relationships of the SRS can be updates to one or more uplink signals transmitted from UE 110 to RAN node 120.

[0136] At 804, RAN node 120 can determine whether the temporal pattern of the SRS resource set is semi-persistent. For example, the temporal pattern and / or periodicity of the SRS resource set can be semi-persistent, aperiodic, or periodic. At 806, if it is determined that the temporal pattern is not semi-persistent, RAN node 120 can use the "Activate / Deactivate" bit field to generate a MAC CE (such as MAC CE 400) to specify whether the list of CCs, including CCs, should be updated based on the updated spatial relations. The "A / D" field can be an unused bit field. 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.

[0137] At 806, if it is determined that the SRS resource set is semi-persistent, RAN node 120 can generate a MAC CE (such as MAC CE 400) at 810 using the reserved bit field to specify whether the list of CCs, including CCs, should be updated based on the updated spatial relationships. This bit may be unavailable because the "A / D" field is used for semi-persistent SRS resource set scenarios. In this way, the reserved bit can be used for this indication.

[0138] At 812, RAN node 120 can determine whether to update the CC list, including CCs, based on the updated spatial relationships. Updating this list may result in reduced message transmission overhead. However, in some respects, the temporal patterns of the elements of the SRS resource set are the same. At 814, RAN node 120 can determine whether to update the CC list. If the list is not updated, at 816, RAN node 120 can modify the MAC CE to indicate that the first value in the bit field is included, indicating that UE 110 should update the spatial relationships of the CCs. The MAC CE may also include a value for the SRS resource set ID and resource ID information for updating the SRS resource set at UE 110. At 820, RAN node 120 can transmit the MAC CE to UE 110.

[0139] Returning to 814, if RAN node 120 determines that the CC list needs to be updated based on updated spatial relationships, then at 818, RAN node 120 may modify the MAC CE to include a second bit value in the bit field indicating that UE 110 should update the spatial relationships of the CCs in the CC list. This CC list may have been previously configured by Radio Resource Control (RRC) messages and may correspond to the cell ID of the indicated SRS resource set. The MAC CE may also include resource ID information for updating the SRS resource set at UE 110.

[0140] Upon receiving a MAC CE, UE 110 can identify the corresponding bit indicating whether the CC list should be updated. Based on the indicated value, UE 110 can identify the specific CC to be updated and / or the CC list to be updated.

[0141] Figure 8C A flowchart 800C is shown for generating a MAC CE to update SRS resources, according to 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 execute flowchart 800C. In some aspects, RAN node 120 can use flowchart 800C to generate a MAC CE and transmit it to the UE. Flowchart 800C should be described with reference to RAN node 120; however, flowchart 800C is not limited to this exemplary aspect. Flowchart 800C can be executed on any computing device, such as those described above. Figure 10 The described computer system and / or processing logic components may include hardware (e.g., circuitry, dedicated logic components, programmable logic components, microcode, etc.), software (e.g., instructions that execute on a processing device), or combinations thereof.

[0142] It should be understood that not all steps may be required to perform the disclosure provided herein. Furthermore, as those skilled in the art will understand, some of these steps may be performed simultaneously or in combination with… Figure 8C The different execution sequences are shown.

[0143] At 822, RAN node 120 can identify updates to the spatial relationships of the sounding reference signal (SRS) resources corresponding to the component carriers (CCs) of user equipment (UE) 110, where each CC has an SRS resource cell ID. This update may be for a specific resource rather than a set of resources. In this way, flowchart 800C can be used to update specific beams identified using the SRS resource cell ID, such as reference... Figure 5 As described.

[0144] At 824, RAN node 120 can determine whether to update the CC list, which includes CCs, based on updates to spatial relationships. This CC list may have been previously configured by Radio Resource Control (RRC) messages and may correspond to the indicated SRS resource ID. Updates to spatial relationship information may apply to other CCs in the list, which also includes CCs corresponding to SRS resource IDs.

[0145] At 826, RAN node 120 can determine whether to update the CC list at UE 110. If the CC list is not updated and RAN node 120 intends to update the CC corresponding to the SRS resource cell ID, RAN node 120 can generate a Media Access Control (MAC) CE at 828. This MAC CE may include the SRS resource cell ID and a first value instructing UE 110 to use the SRS resource cell ID to update the spatial relationship of the CC. Other values ​​such as the SRS resource BWP ID and / or the SRS resource ID can also help identify the SRS resource. Values ​​such as the resource ID, resource serving cell ID, and / or resource BWP ID can indicate the updated SRS spatial relationship. For example, the first value can be zero. The MAC CE can be similar to MAC CE 500, as referenced in [reference missing]. Figure 5 As described. Then, RAN node 120 can transmit the MAC CE to UE 110 at 832. Then, UE 110 can use the resource ID included in the MAC CE to update the CC corresponding to the SRS resource cell ID.

[0146] Returning to 826, RAN node 120 can determine that the CC list needs to be updated. In this case, RAN node 120 can generate a MAC CE, which includes the SRS resource cell ID and a second bit instructing UE 110 to use the SRS resource cell ID to update the spatial relationships of CCs in the CC list. In this way, UE 110 can update the CCs corresponding to the SRS resource cell ID as well as other CCs on the list configured by the RRC message. This MAC CE can then provide spatial relationship updates for multiple CCs, which reduces message transmission overhead. At 832, RAN node 120 can transmit the MAC CE to UE 110.

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

[0148] Figure 9 A flowchart 900 is shown for configuring TCI code points for a PDSCH to support multiple transmit receiver points (multiple TRP) operation, according to 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 execute flowchart 900. In some aspects, RAN node 120 can use flowchart 900 to generate a MAC CE and transmit it to the UE. Flowchart 900 should be described with reference to RAN node 120; however, flowchart 900 is not limited to this exemplary aspect. Flowchart 900 can be executed on any computing device, such as those described above. Figure 10 The described computer system and / or processing logic components may include hardware (e.g., circuitry, dedicated logic components, programmable logic components, microcode, etc.), software (e.g., instructions that execute on a processing device), or combinations thereof.

[0149] It should be understood that not all steps may be required to perform the disclosure provided herein. Furthermore, as those skilled in the art will understand, some of these steps may be performed simultaneously or in combination with… Figure 9 The different execution sequences are shown.

[0150] At position 902, RAN node 120 can identify the configuration of one or more Transport Configuration Indicator (TCI) code points corresponding to the component carrier (CC). This identification can indicate the possible presence of a multi-TRP scenario. RAN node 120 can generate a MAC CE that configures the TCI code points for the PDSCH.

[0151] At 904, RAN node 120 can determine that at least one of one or more TCI code points has multiple TCI states. For example, a TCI code point may have two TCI states. In this case, the code point can communicate with multiple TRPs. However, other code points may still have one TCI state.

[0152] At 906, RAN node 120 may generate a MAC CE, which includes a first value indicating the amount of one or more TCI code points and a second value indicating the amount of at least one TCI code point among the one or more TCI code points having multiple TCI states. This MAC CE may be similar to MAC CE 600A and / or 600B, as referenced. Figure 6A and Figure 6B As described. The first and second values ​​can indicate to the UE 110 the expected number of bits and / or octets in the remaining bits of the MAC CE.

[0153] At 908, for at least one TCI code point having multiple TCI states among one or more TCI code points, RAN node 120 may update the MAC CE to include: a first octet of data including bits indicating the presence of multiple TCI states and a first TCI state ID; and a second octet of data including reserved bits and a second TCI state ID. In this way, the MAC CE may use two octets for two TCI state IDs. In some aspects, the bits in the first octet may indicate that a particular code point has two TCI states. When UE 110 receives the MAC CE and recognizes this bit, UE 110 recognizes that the subsequent octet represents data corresponding to the second TCI state of the code point. At 910, RAN node 120 may transmit the MAC CE to UE 110.

[0154] In some respects, flowchart 900 can be executed on one or more iterations based on changes to the TCI state. For example, a first MAC CE can be used to update the TCI state, but a second MAC CE can then be used again to update the TCI state. Similarly, the second MAC CE can correspond to updates to the same TCI state or different TCI states. In this way, the aspects described with respect to flowchart 700 are not limited to a single MAC CE.

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

[0156] Computer system 1000 may include one or more processors (also referred to as central processing units or CPUs), such as processor 1004. Processor 1004 may be connected to communication infrastructure or bus 1006.

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

[0158] One or more processors in processor 1004 may be graphics processing units (GPUs). In one aspect, a GPU may be a processor with dedicated electronic circuitry designed for processing mathematically intensive applications. The GPU may have efficient parallel architectures for parallel processing of large blocks of data, such as general mathematically intensive data in computer graphics applications, images, videos, etc.

[0159] The computer system 1000 may also include main memory or primary memory 1008, such as random access memory (RAM). Main memory 1008 may include one or more levels of cache. Main memory 1008 may store control logic components (i.e., computer software) and / or data.

[0160] The computer system 1000 may also include one or more auxiliary storage devices or memories 1010. Auxiliary memory 1010 may include, for example, a hard disk drive 1012 and / or a removable storage device or drive 1014. The removable storage drive 1014 may be a floppy disk drive, a magnetic tape drive, an optical disk drive, an optical storage device, a magnetic tape backup device, and / or any other storage device / drive.

[0161] Removable storage drive 1014 can interact with removable storage unit 1018. Removable storage unit 1018 may include a computer-usable or readable storage device on which computer software (control logic components) and / or data are stored. Removable storage unit 1018 may be a floppy disk, magnetic tape, optical disc, DVD, optical storage disc, and / or any other computer data storage device. Removable storage drive 1014 can read from and / or write to removable storage unit 1018.

[0162] Auxiliary storage 1010 may 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 may include, for example, removable storage unit 1022 and interface 1020. Examples of removable storage unit 1022 and interface 1020 may include program boxes and box interfaces (such as those found in video game devices), removable memory chips (such as EPROM or PROM) and associated sockets, memory sticks and USB ports, memory cards and associated memory card slots, and / or any other removable storage unit and associated interface.

[0163] Computer system 1000 may also include a communication or network interface 1024. Communication interface 1024 enables computer system 1000 to communicate and interact with any combination of external devices, external networks, external entities, etc. (individually and collectively referred to by reference numeral 1028). For example, communication interface 1024 may allow computer system 1000 to communicate with external or remote device 1028 via communication path 1026, which may be wired and / or wireless (or a combination thereof), and may include any combination of LAN, WAN, Internet, etc. Control logic components and / or data may be transmitted to and from computer system 1000 via communication path 1026.

[0164] Computer system 1000 may also be (to give a few non-limiting examples) any of a personal digital assistant (PDA), a desktop workstation, a laptop or notebook computer, a netbook, a tablet computer, a smartphone, a smartwatch or other wearable device, appliance, part of the Internet of Things and / or an embedded system, or any combination thereof.

[0165] Computer system 1000 can be a client or server that accesses or hosts any application and / or data through any delivery paradigm, including but not limited to: remote or distributed cloud computing solutions; on-premises or internally deployed software (“internal” 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), Managed 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 models that include any combination of the foregoing examples or other services or delivery paradigms.

[0166] Any applicable data structures, file formats, and outlines in the computer system 400 may be derived from standards including, but not limited to, JavaScript Object Notation (JSON), Extensible Markup Language (XML), 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 outlines may be used alone or in combination with known or open standards.

[0167] In some aspects, tangible, non-transitory devices or articles of art include tangible, non-transitory computer-usable or readable media on which control logic components (software) are stored, which may also be referred to herein as computer program products or program storage devices. This includes, but is not limited to, computer system 1000, main memory 1008, auxiliary memory 1010, and removable storage units 1018 and 1022, as well as tangible articles embodying any combination thereof. Such control logic components, when executed by one or more data processing devices (such as computer system 1000), cause such data processing devices to operate as described herein.

[0168] Based on the teachings contained in this disclosure, it will be apparent to those skilled in the art how to use [other methods]. Figure 10 Other data processing devices, computer systems, and / or computer architectures besides those shown may be used to make and use aspects of this disclosure. In particular, aspects may operate in conjunction with software, hardware, and / or operating system implementations other than those described herein.

[0169] It should be understood that the detailed description section, and not any other section, is intended to be used to interpret the claims. The other sections may set forth one or more, but not all, exemplary aspects contemplated by the inventors, and are therefore not intended to limit this disclosure or the appended claims in any way.

[0170] While this disclosure describes exemplary aspects of exemplary fields and applications, it should be understood that this disclosure is not limited thereto. Other aspects and modifications are possible and are within the scope and spirit of this disclosure. For example, and without limiting the generality of this paragraph, the aspects are not limited to the software, hardware, firmware, and / or entities shown in the figures and / or described herein. Furthermore, the aspects (whether explicitly described herein or not) have significant utility for fields and applications beyond those illustrated herein.

[0171] The aspects have been described here using functional building blocks that illustrate specific implementations of functions and their relationships. For ease of description, the boundaries of these functional building blocks have been arbitrarily defined herein. Alternative boundaries may be defined as long as the specified functions and relationships (or their equivalents) are performed appropriately. Furthermore, alternative aspects may perform functional blocks, steps, operations, methods, etc., in an order different from that described herein.

[0172] References to “an aspect,” “aspect,” “exemplary aspect,” or similar phrases herein indicate that the aspect described may include a particular feature, structure, or characteristic, but each aspect may not necessarily include that particular feature, structure, or characteristic. Furthermore, such terminology does not necessarily refer to the same aspect. Additionally, when a particular feature, structure, or characteristic is described in conjunction with an aspect, whether or not it is explicitly mentioned or described herein, the incorporation of those features, structures, or characteristics into other aspects is within the knowledge of a person skilled in the art. Furthermore, the expressions “coupled” and “connected,” and their derivatives, may be used to describe aspects. These terms are not necessarily intended to be synonyms with each other. For example, some aspects may be described using the terms “connected” and / or “coupled” to indicate that two or more elements are in direct physical and / or electrical contact with each other. However, the term “coupled” may also refer to two or more elements that are not in direct contact with each other but still cooperate and / or interact with each other.

[0173] The breadth and scope of this disclosure should not be limited by any of the foregoing exemplary aspects, but should be defined solely by the following claims and their equivalents.

[0174] As described above, various aspects of this technology may include the collection and use of data available from a variety of sources to, for example, improve or enhance functionality. This disclosure contemplates that, in some instances, such collected data may include personal information data that uniquely identifies or can be used to contact or locate specific individuals. Such personal information data may include demographic data, location-based data, telephone numbers, email addresses, Twitter IDs, home addresses, data or records related to a user's health or fitness level (e.g., vital sign measurements, medication information, exercise information), date of birth, or any other identifying information or personal information. This disclosure recognizes that the use of such personal information data in this technology can be used to benefit users.

[0175] This disclosure assumes that entities responsible for collecting, analyzing, disclosing, transmitting, storing, or otherwise using such personal information data will comply with established privacy policies and / or privacy practices. Specifically, such entities should implement and adhere to privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy and security of personal information data. Such policies should be easily accessible to users and should be updated as data collection and / or use change. Personal information from users should be collected for the entity's lawful and reasonable purposes and not shared or sold outside of these lawful uses. Furthermore, such collection / sharing should only occur upon receiving informed consent from users. In addition, such entities should consider taking any necessary steps to protect and safeguard access to such personal information data and ensure that others with access to such personal information data comply with their privacy policies and processes. Additionally, such entities may be subject to third-party evaluations to demonstrate their compliance with widely accepted privacy policies and practices. Furthermore, policies and practices should be adapted to the specific types of personal information data collected and / or accessed, and to applicable laws and standards, including specific considerations regarding jurisdiction. For example, in the United States, the collection or acquisition of certain health data may be governed by federal and / or state laws, such as the Health Insurance Transfer and Accountability Act (HIPAA); while in other countries, health data may be subject to other regulations and policies and should be handled accordingly. Therefore, different privacy practices should be maintained for different types of personal data in each country.

[0176] Regardless of the foregoing, this disclosure also anticipates allowing users to selectively block aspects of the use or access to their personal information data. That is, this disclosure anticipates providing hardware and / or software components to prevent or block access to such personal information data. For example, the technology can be configured to allow users to selectively participate in the collection of personal information data at any time during or after service registration via an "opt-in" or "opt-out" option. In addition to providing "opt-in" and "opt-out" options, this disclosure envisions providing notifications related to access to or use of personal information. For example, users may be notified when downloading an application that their personal information data will be accessed, and then reminded again just before the application accesses the personal information data.

[0177] Furthermore, the purpose of this disclosure is to manage and process personal information data to minimize the risk of unintentional or unauthorized access or use. Once data is no longer needed, this risk can be minimized by limiting data collection and deleting data. Additionally, and where applicable, including in certain health-related applications, data deidentification can be used to protect user privacy. Deidentification can be facilitated, where appropriate, by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of stored data (e.g., collecting location data at the city level rather than the address level), controlling how data is stored (e.g., aggregating data among users), and / or other methods.

[0178] Therefore, while this disclosure broadly covers the use of personal information data to implement one or more of the various disclosed aspects, it is also contemplated that various aspects can be implemented without access to such personal information data. That is, various aspects of the invention will not be rendered inoperable due to the absence of all or part of such personal information data.

Claims

1. A method for equipping a user (UE), the method comprising: Receive Media Access Control (MAC) CE from the access node; The serving cell is determined based on the MAC CE. The serving cell is confirmed to be in the cell list; as well as Update the Transmission Configuration Indicator (TCI) status information for the cells in the cell list.

2. The method of claim 1, wherein determining that the serving cell is in the cell list further comprises: Receive Radio Resource Control (RRC) messages from the access node; as well as Based on the RRC message, it is determined that the cell list includes the serving cell.

3. The method according to claim 2, further comprising: In response to determining, based on the RRC message, that the cell list includes the serving cell, the TCI status information of all cells in the cell list is updated.

4. The method of claim 2, wherein determining that the serving cell is in the cell list further comprises: Determine the component carrier CC corresponding to the serving cell; Determine the CC list based on the RRC message; It is determined that the CC list includes the CC; as well as Determine that the CC list corresponds to the cell list.

5. The method of claim 1, wherein updating the TCI status information of cells in the cell list is based on an indicator bit in the MAC CE.

6. The method of claim 5, wherein the indicator bit is a reserved bit in the MAC CE.

7. The method of claim 1, wherein the MAC CE includes the TCI status information.

8. The method according to claim 1, wherein the TCI information is used for the Physical Downlink Shared Channel (PDSCH).

9. The method of claim 1, wherein the MAC CE includes the serving cell ID of the serving cell.

10. An apparatus comprising: Memory; as well as A processor, coupled to the memory, is configured to: Receive Media Access Control (MAC) CE from the access node; The serving cell is determined based on the MAC CE. Determine that the serving cell is in the cell list; and Update the Transmission Configuration Indicator (TCI) status information for the cells in the cell list.

11. The apparatus of claim 10, wherein, in order to determine that the serving cell is in the cell list, the processor is further configured to: Receive Radio Resource Control (RRC) messages from the access node; and Based on the RRC message, it is determined that the cell list includes the serving cell.

12. The apparatus of claim 11, wherein, in order to determine that the serving cell is in the cell list, the processor is further configured to: Determine the component carrier CC corresponding to the serving cell; Determine the CC list based on the RRC message; Determine that the CC list includes the CC; and Determine that the CC list corresponds to the cell list.

13. The apparatus of claim 10, wherein the processor is further configured to: update the TCI status information of cells in the cell list based on an indication bit in the MAC CE.

14. The apparatus of claim 13, wherein the indication bit is a reserved bit in the MAC CE.

15. The apparatus of claim 10, wherein the MAC CE includes the TCI status information.

16. The apparatus of claim 10, wherein the TCI information is used for the Physical Downlink Shared Channel (PDSCH).

17. The apparatus of claim 10, wherein the MAC CE includes the serving cell ID of the serving cell.

18. A non-transitory computer-readable medium (CRM) comprising instructions that, when executed by one or more processors of a user-equipped UE, cause the UE to perform operations, the operations including: Receive Media Access Control (MAC) CE from the access node; The serving cell is determined based on the MAC CE. The serving cell is confirmed to be in the cell list; as well as Update the Transmission Configuration Indicator (TCI) status information for the cells in the cell list.

19. The non-transient CRM of claim 18, wherein determining that the serving cell is in the cell list further comprises: Receive Radio Resource Control (RRC) messages from the access node; as well as Based on the RRC message, it is determined that the cell list includes the serving cell.

20. The non-transient CRM of claim 19, wherein determining that the serving cell is in the cell list further includes: Determine the component carrier CC corresponding to the serving cell; Determine the CC list based on the RRC message; It is determined that the CC list includes the CC; as well as Determine that the CC list corresponds to the cell list.

21. A method performed at an access node, the method comprising: Update the spatial relationships of the sounding reference signal (SRS) resource set corresponding to the component carrier (CC); Determine whether the periodicity of the SRS resource set is aperiodic or periodic; Generate a Media Access Control (MAC) CE, the MAC CE including bit values ​​in an activation / deactivation bit field, the bit values ​​indicating to the User Equipment (UE) to update the spatial relationships of CCs in a CC list including the CC; as well as The MAC CE is transmitted to the UE.

22. The method of claim 21, wherein the resources of the SRS resource set have the same time-domain pattern.

23. The method of claim 21, further comprising: A second update identifying the spatial relationships of the SRS resource set corresponding to the CC; The temporal mode of the SRS resource set corresponding to the second update is determined to be semi-persistent; A second MAC CE is generated, the second MAC CE including bit values ​​in a reserved bit field, the bit values ​​indicating that the UE updates the spatial relationship of the CC according to the second update; as well as The second MAC CE is transmitted to the UE.

24. The method of claim 22, wherein the bit value in the reserved bit field indicates that the UE updates the spatial relationship of CCs in a CC list including the CC.

25. The method of claim 21, further comprising: A second update identifies the spatial relationships of SRS resources corresponding to the CC, wherein the CC has an SRS resource cell ID; Based on the update of the spatial relationship, it is determined that the list of CCs including the CCs needs to be updated; Generate a second MAC CE, the second MAC CE including the SRS resource cell ID and a bit value instructing the UE to use the SRS resource cell ID to update the spatial relationship of CCs in the CC list; as well as The second MAC CE is transmitted to the UE.

26. The method of claim 25, wherein the length of the second MAC CE is four octets.

27. A method performed at an access node, the method comprising: Identify the configuration of one or more Transmission Configuration Indicator (TCI) code points corresponding to the component carrier CC of the User Equipment (UE); Determine that at least one of the one or more TCI code points has multiple TCI states; Generate a Media Access Control (MAC) CE, the MAC CE including a first value indicating the amount of the one or more TCI code points and a second value indicating the amount of the at least one TCI code point having multiple TCI states among the one or more TCI code points; For at least one TCI code point among the one or more TCI code points that has multiple TCI states, update the MAC CE to include a bit indicating the presence of multiple TCI states; and The MAC CE is transmitted to the UE.

28. The method of claim 27, wherein the MAC CE comprises: The first eight-bit byte data includes a bit indicating the presence of multiple TCI states and a first TCI state ID; And a second octet of data, which includes a second TCI status ID.

29. The method of claim 28, wherein the second eight-bit byte data includes reserved bits.

30. The method of claim 27, wherein the bit direction indicating to the UE is related to the second TCI state by the 8-bit data following the first TCI state.

31. The method according to claim 27, further comprising: Update the MAC CE to include a second bit indicating that a single TCI state exists among the one or more TCI code points.

32. The method of claim 31, wherein the second bit indicates to the UE that the subsequent 7 bits of data are related to the single TCI state.

33. The method of claim 32, wherein the subsequent 7 bits of data include a TCI status ID corresponding to the TCI code point.

Images