Signaling details for temporary reference signal based secondary cell activation

Abstract

Certain aspects of this application provide techniques for a method of wireless communication by a user equipment (UE), the method comprising: receiving a radio resource control (RRC) signal delivery that configures the UE to have one or more per-carrier reference signal (RS) configurations; receiving a dynamic signal delivery that initiates a cocell and indicates at least one of the one or more per-carrier RS ​​configurations; and monitoring temporary RSs on the cocell at least in part based on at least one RS configuration indicated by the dynamic signal delivery among the one or more RS configurations.

Description

Technical Field

[0001] This patent application claims priority to U.S. Application No. 17 / 979,739, filed November 2, 2022, which claims the benefit and priority to U.S. Application No. 63 / 275,821, filed November 4, 2021, which has been assigned to the assignee of this application and whose entire contents are expressly incorporated herein by reference, as fully set forth below and for all applicable purposes.

[0002] In summary, the subject matter of this application relates to wireless communication, and more specifically, to a technique for monitoring temporary reference signals (temporary RS) on a cocell based on a reference signal (RS) configuration. Prior Technology

[0003] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, broadcasting, or other similar services. These wireless communication systems can employ multiplexing access technologies that support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, or other resources). For example, multiplexing access technologies can rely on any of code division, time division, frequency division orthogonal frequency division, single-carrier frequency division, or time division synchronous code division. These and other multiplexing access technologies have been adopted in various telecommunications standards to provide common protocols that enable different wireless devices to communicate at the city, national, regional, and even global levels.

[0004] Despite significant technological advancements in wireless communication systems over the years, challenges remain. For example, complex and dynamic environments can still attenuate or block signals between wireless transmitters and receivers, disrupting various established wireless channel measurement and reporting mechanisms used to manage and optimize the use of limited wireless channel resources. Therefore, there is a need for further improvements to wireless communication systems to overcome these challenges. Summary of the Invention

[0005] One approach provides a method for wireless communication by a user equipment (UE). In summary, the method includes: receiving a radio resource control (RRC) signal transmission configuring the UE to have one or more per-carrier reference signal (RS) configurations; receiving a dynamic signal transmission activating a secondary cell and indicating at least one of the one or more per-carrier RS ​​configurations; and monitoring temporary RSs on the secondary cell based at least in part on the at least one RS configuration indicated by the dynamic signal transmission among the one or more RS configurations.

[0006] One approach provides a method for wireless communication by a network entity. In summary, the method includes: transmitting a Radio Resource Control (RRC) signal transmission that configures a User Equipment (UE) to have one or more per-carrier Reference Signal (RS) configurations; and transmitting a dynamic signal transmission that initiates a secondary cell and indicates at least one of the one or more per-carrier RS ​​configurations.

[0007] Other embodiments include: an apparatus operable to, configured to, or otherwise adapted to perform the methods described above and elsewhere herein; a non-transitory computer-readable medium including instructions that, when executed by one or more processors of the apparatus, cause the apparatus to perform the methods described above and elsewhere herein; a computer program product embodied on a computer-readable storage medium, including code for performing the methods described above and elsewhere herein; and an apparatus including units for performing the methods described above and elsewhere herein. For example, an apparatus may include a processing system, a device having a processing system, or a processing system coordinated via one or more networks.

[0008] For illustrative purposes, the following description and figures illustrate certain features. Simple Explanation of the Diagram

[0009] The accompanying drawings illustrate certain features of the various states described herein and are not intended to limit the scope of this case.

[0010] Figure 1 is a block diagram conceptually illustrating an example wireless communication network.

[0011] Figure 2 is a block diagram that conceptually illustrates various forms of network entities and user devices.

[0012] Figures 3A-3D illustrate various instance types of data structures used in wireless communication networks.

[0013] Figure 4 is a schematic diagram of the Channel Status Information (CSI) resource configuration for the illustrated example.

[0014] Figure 5 illustrates an example isochron of a co-cell (SCell) initiation based on a temporary reference signal (RS).

[0015] Figures 6A and 6B illustrate instance isochrones for different options used to trigger a temporary RS for SCell startup.

[0016] Figure 7 illustrates the isochrones used for temporary RS.

[0017] Figure 8 is a dialing flowchart illustrating the first instance of a temporary RS-based SCell startup based on some states according to the content of this case.

[0018] Figure 9 is a dialing flowchart illustrating a second instance of SCell startup based on a temporary RS, according to some of the states described in this case.

[0019] Figure 10 is a schematic diagram illustrating some examples of CSI resource configuration based on the content of this case.

[0020] Figure 11 illustrates some examples of wireless communication operations performed by a UE, based on the content of this case.

[0021] Figure 12 illustrates some examples of wireless communication by network entities, based on the content of this case.

[0022] Figure 13 illustrates some examples of wireless communication operations performed by a UE, based on the content of this case.

[0023] Figure 14 illustrates some examples of wireless communication operations performed by network entities, based on the content of this case.

[0024] Figure 15 illustrates the various states of the example communication device.

[0025] Figure 16 illustrates the various states of the example communication device. Implementation

[0026] Various forms of this case provide apparatus, methods, processing systems, and computer-readable media for a UE to determine, based on RS configuration, the provisional reference signal (RS) to be monitored on a co-cell (SCell).

[0027] Some wireless communication systems support different cell types, such as primary cells (PCells) and secondary cells (SCells). A primary cell typically refers to the cell in which the user equipment (UE) performs the initial connection establishment procedure and initiates the connection reconstruction procedure, or the cell designated as the primary cell during handover. An SCell typically refers to a cell that operates on a different frequency than the primary cell, where the cell can be configured once a Radio Resource Control (RRC) connection is established, and the cell can be used to provide additional radio resources.

[0028] After the UE receives the command to initiate an SCell, there may be a delay that allows the UE to monitor a reference signal known as a Synchronization Signal Block (SSB) before sending a Channel State Information (CSI) report. The UE will use this reference signal to adjust its time and frequency tracking. Because there can be relatively long periods between SSBs, this delay can be quite significant. In some cases, to reduce this delay, an aperiodic temporary reference signal (temporary RS) can be sent after the SCell has been initiated, at a time earlier than the next SSB. The earlier timing of this temporary RS allows the UE to perform measurements and send CSI reports in the SCell more quickly compared to waiting for subsequent SSBs.

[0029] In this way, using ad hoc RSs can reduce SCell initiation latency and enable efficient use of SCells for data communication. One challenge with ad hoc RS-based SCell initiation lies in configuring the UE with details for the ad hoc RS and instructing the UE on triggering the ad hoc RS. In other words, the challenge is instructing the UE on which ad hoc RS to monitor in the SCell after receiving an instruction to initiate the SCell.

[0030] The first option to address this challenge is to define a new set of RRC parameters to configure the ephemeral RS and to trigger it using the corresponding New Media Access Control (MAC) control element (CE). Unfortunately, this option may require additional specification effort to define signal delivery for parameters that may be similar to existing parameters, resulting in redundant effort and an increased signal delivery management burden (since all RRC parameters associated with triggering the ephemeral RS must be repeated for each carrier).

[0031] The second option is to reuse existing RRC parameters for aperiodic CSI-RS and / or Tracking Reference Signal (TRS). Unfortunately, the trigger state (used to initiate aperiodic CSI-RS / TRS) is typically configured for all carriers (not just SCell carriers), which is less flexible and results in suboptimal communication performance.

[0032] The various versions of this paper provide the following flexible methods: signaling the ephemeral RS configuration to the UE and signaling the activation of the ephemeral RS. As will be described in more detail below, according to certain versions, the RRC signaling mechanism, including a per-carrier aperiodic trigger state list (each trigger state list associated with one or more RS configurations), can avoid the need to repeat other RRC parameters and allow the reuse of some RRC parameters. According to certain versions, dynamic signaling such as MAC-CE can activate the SCell and can also indicate the RS configuration to be monitored in the SCell. Compared to the management burden associated with repeating all RRC parameters related to triggering the ephemeral RS, the signaling mechanism proposed in this paper can result in a reduced RRC management burden.

[0033] Depending on certain patterns, the signal transmission mechanism proposed in this paper can allow MAC-CE or other signal transmissions to indicate trigger states for different carriers respectively. Unlike methods that reuse all RRC parameters for all carriers, MAC-CE or other signal transmissions with separate trigger state indication fields for different carriers can allow for flexible temporary RS indications. Introduction to wireless communication networks

[0034] Figure 1 illustrates an example in which various wireless communication systems 100 described herein can be implemented.

[0035] Typically, a wireless communication system 100 includes a network entity 102, a user equipment (UE) 104, and one or more core networks (such as an evolved packet core (EPC) 160 and a 5G core (5GC) network 190) that interact to provide wireless communication services.

[0036] Network entity 102 can provide user equipment 104 with access points to EPC 160 and / or 5GC 190, and can perform one or more of the following functions: transmission of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), user and equipment tracking, RAN information management (RIM), paging, location, delivery of warning messages, and other functions. In various contexts, network entity may include and / or be referred to as gNB, NodeB, eNB, ng-eNB (e.g., an eNB that has been enhanced to provide connectivity to both EPC 160 and 5GC 190), access point, base station transceiver, radio base station, radio transceiver, or transceiver functional unit, or transmit / receive point.

[0037] Network entity 102 communicates wirelessly with UE 104 via communication link 120. Each of network entities 102 can provide communication coverage for a corresponding geographic coverage area 110, and in some cases, geographic coverage areas 110 may overlap. For example, a small cell 102' (e.g., a low-power base station) may have a coverage area 110' that overlaps with the coverage areas 110 of one or more macrocells (e.g., high-power base stations).

[0038] The communication link 120 between network entity 102 and UE 104 may include uplink (UL) (also known as reverse link) transmission from user equipment 104 to network entity 102 and / or downlink (DL) (also known as forward link) transmission from network entity 102 to user equipment 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna technology, which in various configurations includes spatial multiplexing, beamforming, and / or transmit diversity.

[0039] Examples of UE 104 include cellular phones, smartphones, conversation initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radio units, global positioning systems, multimedia devices, video equipment, digital audio players, cameras, game consoles, tablet devices, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, medical devices, implants, sensors / actuators, displays, or other similar devices. Some UEs in UE 104 can be Internet of Things (IoT) devices (e.g., parking meters, air pumps, ovens, vehicles, heart monitors, or other IoT devices), always-on (AON) devices, or edge processing devices. UE 104 may also be more commonly referred to as a station, mobile station, subscriber station, mobile unit, user unit, radio unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, mobile phone, user agent, mobile service client, or client.

[0040] Compared to lower-frequency communications, communications using higher frequency bands may have higher path loss and shorter range. Therefore, certain network entities (e.g., 180 in Figure 1) can utilize beamforming 182 with UE 104 to improve path loss and range. For example, network entity 180 and UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming.

[0041] In some cases, network entity 180 may transmit beamformed signals to UE 104 in one or more transmit directions 182'. UE 104 may receive beamformed signals from network entity 180 in one or more receive directions 182''. UE 104 may also transmit beamformed signals to network entity 180 in one or more transmit directions 182''. Network entity 180 may also receive beamformed signals from UE 104 in one or more receive directions 182''. Subsequently, network entity 180 and UE 104 may perform beamforming to determine the optimal receive and transmit directions for each of network entity 180 and UE 104. It is worth noting that the transmit and receive directions for network entity 180 may be the same or different. Similarly, the transmit and receive directions for UE 104 may be the same or different.

[0042] The wireless communication network 100 includes a Channel Status Information (CSI) reporting component 199, which can be configured to send CSI reports and / or RS configurations. The wireless network 100 also includes a CSI reporting component 198, which can be configured to receive CSI report configurations.

[0043] Figure 2 illustrates the various states of instance network entity 102 and user equipment (UE) 104.

[0044] Typically, network entity 102 includes various processors (e.g., 220, 230, 238, and 240), antennas 234a-t (collectively referred to as 234), transceivers 232a-t (collectively referred to as 232) including modulators and demodulators, and other configurations that enable wireless transmission of data (e.g., data source 212) and wireless reception of data (e.g., data slot 239). For example, network entity 102 can transmit and receive data between itself and user equipment 104.

[0045] Network entity 102 includes a controller / processor 240, which can be configured to implement various functions related to wireless communication. In the illustrated example, controller / processor 240 includes a CSI reporting component 241, which may represent CSI reporting component 199 in FIG1. ​​It is worth noting that although CSI reporting component 241 is illustrated as one state of controller / processor 240, in other implementations, CSI reporting component 241 may be implemented supplementarily or alternatively in various other states of network entity 102.

[0046] Typically, user equipment 104 includes various processors (e.g., 258, 264, 266, and 280), antennas 252a-r (collectively referred to as 252), transceivers 254a-r (collectively referred to as 254) including modulators and demodulators, and other features that enable wireless transmission of data (e.g., data source 262) and wireless reception of data (e.g., data slot 260).

[0047] In various forms, for example, network devices, network entities, or network nodes can be implemented as aggregated network entities, decomposed network entities, components of network entities, integrated access and backhaul (IAB) nodes, relay nodes, and sidelink nodes.

[0048] The decomposed network entity architecture may include one or more central units (CUs) that can communicate directly with the core network via a backhaul link, or indirectly with the core network via one or more decomposed network entity units (such as via an E2 link through a near-real-time (near-RT) RAN Intelligent Controller (RIC), or a non-real-time (non-RT) RIC associated with the Service Management and Orchestration (SMO) framework 205, or both). CUs may communicate with one or more distributed units (DUs) via appropriate midrange links (such as an F1 interface). DUs may communicate with one or more radio units (RUs) via appropriate frontend links. RUs may communicate with the corresponding UE 104 via one or more radio frequency (RF) access links. In some implementations, UE 104 may be served by multiple RUs simultaneously.

[0049] Each of these units (e.g., CU, DU, RU) and the near-RT RIC, non-RT RIC, and SMO frameworks may include or be coupled to one or more interfaces, which are configured to receive or transmit signals, data, or information (collectively referred to as signals) via wired or wireless transmission media. Each of these units, or an associated processor or controller providing instructions to the communication interface of these units, may be configured to communicate with one or more other units via transmission media. For example, these units may include wired interfaces configured to receive signals on a wired transmission media or transmit signals to one or more other units. Alternatively or additionally, these units may include wireless interfaces (which may include receivers, transmitters, or transceivers (such as radio frequency (RF) transceivers)) configured to receive signals on a wireless transmission media or transmit signals to one or more other units, or both.

[0050] In some implementations, the CU can manage one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Service Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to transmit signals with other control functions managed by the CU. The CU can be configured to handle user plane functions (e.g., Central Unit-User Plane (CU-UP)), control plane functions (e.g., Central Unit-Control Plane (CU-CP)), or combinations thereof. In some implementations, the CU can be logically divided into one or more CU-UP units and one or more CU-CP units. CU-UP units can communicate bidirectionally with CU-CP units via an interface, such as the E1 interface implemented in an O-RAN configuration. The CU can be implemented to communicate with the DU as needed for network control and signal transmission.

[0051] A DU can correspond to a logical unit that includes one or more network entity functions to control the operation of one or more RUs. In some configurations, at least in part depending on the functional partitioning (such as that defined by the 3rd Generation Partnership Project (3GPP), a DU can manage one or more of the following: the Radio Link Control (RLC) layer, the Media Access Control (MAC) layer, and one or more high entity (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation). In some configurations, a DU can also manage one or more low PHY layers. Each layer (or module) can be implemented using an interface configured to transmit signals with other layers (and modules) managed by the DU or with control functions managed by the CU.

[0052] Lower-level functions can be implemented by one or more RUs. In some deployments, at least in part based on functional partitioning (such as lower-level function partitioning), an RU controlled by a DU can correspond to a logical node that manages: RF processing functions or low-PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, etc.) or both. In such an architecture, an RU can be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, the real-time and non-real-time nature of control and user plane communications with the RU can be controlled by the corresponding DU. In some scenarios, this configuration allows DUs and CUs to be implemented in cloud-based RAN architectures (such as vRAN architectures).

[0053] The SMO framework can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operation and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework can be configured to interact with cloud computing platforms (such as Open Cloud (O-Cloud)) via a cloud computing platform interface (such as the O2 interface) to perform network element lifecycle management (such as generating physical virtualized network elements). Such virtualized network elements can include, but are not limited to, CUs, DUs, RUs, and near-RT RICs. In some implementations, the SMO framework can communicate with 4G RAN hardware models, such as Open eNBs (O-eNBs), via the O1 interface. Furthermore, in some implementations, the SMO framework can communicate directly with one or more RUs via the O1 interface. The SMO framework may also include non-RTR ICs configured to support the functionality of the SMO framework.

[0054] Non-RT RICs can be configured to include the following logical functions: These functions enable non-real-time control and optimization of RAN elements and resources; policy-based guidance for artificial intelligence / machine learning (AI / ML) workflows (including model training and updates); or applications / features in near-RT RICs. Non-RT RICs can be coupled to or communicate with near-RT RICs (e.g., via the A1 interface). Near-RT RICs can be configured to include the following logical functions: These functions enable near-real-time control and optimization of RAN elements and resources through data collection and actions on interfaces (e.g., via the E2 interface) that connect one or more CUs, one or more DUs, or both, and O-eNBs to the near-RT RIC.

[0055] In some implementations, to generate AI / ML models to be deployed in a near-RT RIC, a non-RT RIC can receive parameters or rich external information from an external server. Such information can be utilized by the near-RT RIC 225 and can be received from non-network data sources or network functions at the SMO framework or non-RT RIC. In some instances, a non-RT RIC or near-RT RIC can be configured to tune RAN behavior or performance. For example, a non-RT RIC can monitor long-term trends and patterns in performance and employ AI / ML models to perform corrective actions via the SMO framework (such as reconfiguration via O1) or by establishing RAN management policies (such as A1 policies).

[0056] User equipment 104 includes a controller / processor 280, which can be configured to implement various functions related to wireless communication. In the illustrated example, the controller / processor 280 includes a CSI reporting component 281, which may represent the CSI reporting component 198 in FIG1. ​​It is worth noting that although the CSI reporting component 281 is illustrated as one version of the controller / processor 280, in other implementations, the CSI reporting component 281 may be implemented supplementarily or alternatively in various other versions of user equipment 104.

[0057] Figures 3A-3D illustrate various data structures for wireless communication networks (such as the wireless communication network 100 of Figure 1). Specifically, Figure 3A is a schematic diagram 300 showing an example of a first sub-frame within a 5G (e.g., 5G NR) frame structure, Figure 3B is a schematic diagram 330 showing an example of a DL channel within a 5G sub-frame, Figure 3C is a schematic diagram 350 showing an example of a second sub-frame within a 5G frame structure, and Figure 3D is a schematic diagram 380 showing an example of a UL channel within a 5G sub-frame.

[0058] Further discussion of Figures 1, 2 and 3A-3D will be provided later in this article. Instance CSI report configuration

[0059] Channel State Information (CSI) refers to the channel properties of a communication link. CSI can represent, for example, the combined effects of scattering, fading, and power attenuation with the distance between the transmitter and receiver. Channel estimation can be performed using pilot frequencies (such as the CSI Reference Signal (CSI-RS)) to determine these effects on the channel. CSI can be used to adapt transmission based on the current channel conditions, which is useful for achieving reliable communication, especially at high data rates in multi-antenna systems. CSI is typically measured, quantized, and fed back to the transmitter at the receiver.

[0060] The time and frequency resources that can be used by the User Equipment (UE) to report CSI are controlled by network entities (e.g., gNB). CSI may include Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), CSI-RS Resource Indicator (CRI), SS / PBCH Block Resource Indicator (SSBRI), Layer Indicator (LI), Rank Indicator (RI), and / or L1-RSRP. However, additional or other information may be included in the report, as described below.

[0061] The UE can be configured by a network entity for CSI reporting. For example, the network entity can configure the UE to have one or more CSI reporting configurations. The CSI reporting configuration can be provided to the UE via higher-level signaling (e.g., CSI-ReportConfig) such as Radio Resource Control (RRC) signaling. The CSI reporting configuration can be associated with CSI-RS resources used for Channel Measurement (CM), Interference Measurement (IM), or both.

[0062] For example, Figure 4 illustrates a CSI report configuration with CSI-RS resource mapping for CSI aperiodic triggering states. The various information elements (IEs) and corresponding fields shown in Figure 4 are defined in standards (e.g., in 3GPP 38.331). The CSI report configuration is used to configure CSI-RS resources for measurement (e.g., CSI-ResourceConfig in Figure 4). CSI-RS resources provide the UE with a configuration of CSI-RS ports or groups of CSI-RS ports mapped to time and frequency resources (e.g., resource elements (REs)). CSI-RS resources can be zero-power (ZP) or non-zero-power (NZP) resources (each defined by the element NZP-CSI-Resource associated with NZP-CSI-RS-ResourceSet). In Figure 4, NZP resources can be allocated for aperiodic triggering state signal delivery in the CSI-RS-ResourceSetList. At least one NZP CSI-RS resource can be configured for the CM.

[0063] As shown in the figure, the CSI-ApereodicTriggerStateList information element (IE) 410 can include a list of CSI-AperiodicTrigger States. To trigger one of the trigger states in the list, DCI or MAC-CE can indicate an encoding point. As shown, each trigger state can be associated with one or more CSI-AssociatedReportConfigInfoIEs. In the example shown, the first trigger state in the list is associated with two CSI-AssociatedReportConfigInfoIEs (420-1 and 420-2). By associating multiple RS configurations with a single trigger state, multiple aperiodic RSs can be triggered simultaneously.

[0064] The CSI-AssociatedReportConfigInfo IE can include various fields such as reportConfigId, resourceSet, and qcl-Info. reportConfigId maps to a specific CSI-ReportConfig IE. The resource set field can refer to the entry number of a CSI-RS-ResourceSet in the CSI-ResourceConfig IE. The qcl-info field can refer to the Transport Configuration Information (TCI) status list for CSI-RS-Resources in the CSI-RS-ResourceSet IE.

[0065] For a Type II coding book, a PMI is a linear combination of beams; it has a subset of orthogonal beams to be used for the linear combination, and amplitude and phase for each layer and each polarization of each beam. For any type of PMI, configured broadband (WB) PMIs and / or subband (SB) PMIs can exist.

[0066] CSI reporting configuration allows the UE to be configured for non-periodic, periodic, or semi-persistent CSI reporting. For periodic CSI, the UE can be configured with periodic CSI-RS resources. Periodic CSI on the Physical Uplink Control Channel (PUCCH) can be triggered via RRC. Semi-persistent CSI reporting on the Physical Uplink Control Channel (PUCCH) can be initiated via the Media Access Control (MAC) control element (CE).

[0067] The UE can report CSI Feedback (CSF) based on CSI reporting configuration and CSI reporting triggering. For example, the UE can measure the channels on which triggered CSI-RS resources (associated with the CSI reporting configuration) are transmitted. Based on the measurement, the UE can select preferred CSI-RS resources. The UE reports the CSF for the selected CSI-RS resources. LI can be calculated based on the reported CQI, PMI, RI, and CRI; CQI can be calculated based on the reported PMI, RI, and CRI; PMI can be calculated based on the reported RI and CRI; and RI can be calculated based on the reported CRI.

[0068] Each CSI reporting configuration can be associated with a single downlink (DL) bandwidth portion (BWP). The CSI reporting settings configuration can define the CSI reporting band as a subset of the sub-bands of the BWP. The associated DL BWP can be indicated by a higher-layer parameter (e.g., bwp-Id) in the CSI reporting configuration for channel measurements and contains parameters for a CSI reporting band, such as the codebook configuration for CSI, time-domain behavior, frequency nuances, measurement constraint configuration, and CSI-related quantities to be reported by the UE. Each CSI resource setting can reside within a DL BWP identified by higher-layer parameters, and all CSI resource settings can be linked to a CSI reporting setting with the same DL BWP.

[0069] In some systems, the UE can be configured via higher-layer signal transmission (e.g., in CSI report configuration) to have one of two possible subband sizes (e.g., reportFreqConfiguration included in CSI-ReportConfig), indicating the frequency nuance of the CSI report, where the subband can be defined as... The number of adjacent Physical Resource Blocks (PRBs) depends on the total number of PRBs in the bandwidth portion. The UE may also receive an indication of the sub-band for which CSI feedback is requested. In some instances, a sub-band mask is configured for the requested sub-band used for CSI reporting. The UE calculates a precoder for each requested sub-band and finds a PMI that matches the calculated precoder on each of these sub-bands. Instance signaling details for co-cell initiation based on transient RS

[0070] This document provides various forms of apparatus, methods, processing systems, and computer-readable media for a UE to determine, based on RS configuration, the temporary reference signal (RS) to be monitored on a co-cell. In some forms, the RS configuration may be associated with a trigger state.

[0071] For example, the techniques described herein can provide details of signal delivery for configuring and triggering the temporary RS 504 indicated in the instance isochronous line 500 of Figure 5.

[0072] As shown in Figure 5, after the UE receives the start command 508 for starting the SCell (sent in the PCell), the SCell may not be considered active until 3 ms after the UE sends an acknowledgment (ACK) 510. Additionally, there is an extra delay that allows the UE to monitor reference signals (such as SSB 502) before sending Channel State Information (CSI) reports, which the UE can use to adjust its time and frequency tracking. The sum of these delays is marked in Figure 5 and referred to as 𝑇 𝑎𝑐𝑡𝑖𝑣𝑎𝑡𝑖𝑜𝑛 𝑡𝑖𝑚𝑒.

[0073] As mentioned earlier, if the UE will rely on SSBs for initial CSI measurements in the SCell, there may be significant delays due to the relatively long time intervals between SSBs. Compared to waiting for subsequent SSBs, using temporary RSs can significantly reduce SCell startup time by allowing the UE to send valid CSI reports more quickly.

[0074] Based on certain aspects of this case, using similar RRC signal transmissions for aperiodic CSI-RS and temporary RS, the UE can be configured by RRC for temporary RS, where the triggering state is defined using a "per-carrier" structure (as described in more detail below with reference to Figure 10). Temporary RS can be triggered by indicating one of the triggering states (and details of the temporary RS indicated to the UE).

[0075] Various options exist for triggering a temporary RS after SCell initiation. For example, as shown in Figure 6A, the Physical Downlink Shared Channel (PDSCH) can carry a MAC CE that initiates the SCell and also triggers a temporary RS. In the example shown, the UE receives and acknowledges (via Hybrid Automatic Repeat Request Acknowledgment HARQ-ACK) the MAC CE in the PCell. 3 ms after the HARQ-ACK, the SCell can be considered initiated, and a temporary RS can be sent.

[0076] In some cases, the MAC CE can (e.g., via bit fields / coded points) indicate at least one trigger state from a per-carrier aperiodic state list for the SCell carrier. The UE can then monitor temporary RSs on the SCell based on the RS configuration associated with the at least one trigger state indicated in the MAC CE.

[0077] In this way, the bit field / coded point in the MAC CE can indicate one of a plurality of per-carrier RS ​​configurations notified by RRC signals. Subsequently, the UE can monitor the temporary RS on the SCell based on the indicated RS configuration.

[0078] As shown in the example isochron 600B of Figure 6B, according to another option, the MAC CE carried in PDSCH 612 can trigger SCell initiation, while the downlink control information (DCI) 514 can trigger temporary RS 604. In this case, the DCI can (e.g., via bit fields / coded points) indicate at least one triggering state from a per-carrier aperiodic state list for the SCell carrier. Subsequently, the UE can monitor the temporary RS on the SCell based on the RS configuration associated with the at least one triggering state indicated in the DCI.

[0079] The RS configuration associated with the coding point indicated in the MAC CE or DCI (e.g., a temporary RS trigger state) can be configured in various forms. For example, Figure 7 illustrates an example isochronous line 700, where the temporary RS has two short pulses 706 of an aperiodic tracking reference signal (A-TRS) 704. In the example shown, each short pulse spans two time slots and four CSI-RS resources.

[0080] This flexibility in defining temporary RS states helps cover multiple SCell startup scenarios. For example, in the first scenario, the SCell to be started can be known and can belong to FR1. If the SCell measurement period is equal to or less than 2400 ms, a short pulse (e.g., a short pulse spanning 2 time slots with four CSI-RS resources) can be used for time and frequency tracking. If the SCell measurement period is greater than 2400 ms, a short pulse (2 time slots with four CSI-RS resources) can be used for automatic gain control (AGC). In addition to the short pulse used for AGC, a separate short pulse (2 time slots with four CSI-RS resources) can be used for time and frequency tracking. For 15 kHz and 30 kHz, the minimum gap between the RS symbol used for AGC and the RS symbol used for time and frequency acquisition is 2 time slots, while for 60 kHz it is 3 time slots.

[0081] In the second scenario, the SCell may be unknown and belong to FR1. When the SCell is adjacent to an active service cell in the same frequency band (e.g., continuous CA within the band), and the power difference between the service cell and the SCell to be initiated is less than or equal to 6 dB, a short pulse (2 time slots with four CSI-RS resources) can be used for AGC. Another short pulse (2 time slots with four CSI-RS resources) can be used for time and frequency tracking.

[0082] In the third scenario, the SCell can belong to FR2. If there is at least one active serving cell in the FR2 band and a temporary RS is provided for the target SCell, a short pulse (two time slots with four CSI-RS resources) can be used for time / frequency tracking. If there is no active serving cell in the FR2 band and the SCell to be activated is known to the UE, a short pulse (two time slots with four CSI-RS resources) is necessary for time / frequency tracking. If the SCell to be activated is unknown and there is no active serving cell in the FR2 band, the temporary RS may not be used for AGC, and there may be various considerations regarding how to use the temporary RS for time / frequency tracking.

[0083] Figure 8 is a dialing flowchart 800 illustrating SCell initiation and temporary RS indication via MAC CE (e.g., consistent with the example shown in Figure 6A). In some cases, the network entity illustrated in Figure 8 and / or Figure 9 may be an example of network entity 102 illustrated and described with respect to Figures 1 and 3, or an example of a decomposed network entity illustrated and described with respect to Figure 2. Similarly, the UE illustrated in Figure 8 and / or Figure 9 may be an example of UE 104 illustrated and described with respect to Figures 1 and 3.

[0084] As mentioned above, the UE can be configured to have multiple per-carrier RS ​​configurations notified by RRC signals.

[0085] For example, as shown in the figure, at 806, the UE can receive a Radio Resource Control (RRC) signal delivery. This RRC signal delivery configures the UE to report Channel State Information (CSI) using a per-carrier aperiodic trigger state list for one or more types of Reference Signals (RS). At 808, the network entity initiates a SCell and triggers a temporary RS via the MAC CE. As mentioned earlier, the bit fields / coded points in the MAC CE can indicate one of a plurality of per-carrier RS ​​configurations notified by the RRC signal. For example, as shown in Figure 8, the MAC CE can (via bit fields / coded points) indicate the trigger state associated with at least one per-carrier RS ​​configuration.

[0086] As shown in the figure, at 810, the UE can then monitor the ad hoc RS on the cocell, at least in part, based on at least one RS configuration associated with at least one trigger state indicated in the MAC CE (at 808). Compared to conventional SSB-based SCell startup scenarios, ad hoc RS allows the UE to initiate communication in the SCell more quickly. For example, based on ad hoc RS measurements, the UE can generate and send a CSI report, for instance, before the SBB becomes available.

[0087] Figure 9 is a dialing flowchart 900 illustrating SCell initiation via MAC CE and temporary RS indication via DCI (e.g., consistent with the example shown in Figure 6B).

[0088] As shown in the figure, at 906, the UE can receive an RRC signal delivery that configures the UE to perform CSI reporting using a per-carrier aperiodic triggered state list for one or more types of reference signals (RS). Following the RRC configuration, at 908, the network entity initiates a SCell via MAC CE, and at 910, triggers a temporary RS via DCI. As illustrated, at 912, the UE can then monitor the temporary RS on the cocell, at least in part, based on at least one RS configuration indicated in the DCI (at 910).

[0089] Figure 10 illustrates an example of a per-carrier aperiodic trigger state list 1010 for a temporary RS as proposed herein. The example shown illustrates an RRC signal transmission including a first CSI aperiodic trigger state list 1010-1 for a first CC (CC1) and a second CSI aperiodic trigger state list 1010-2 for a second CC (CC2). Each CSI aperiodic trigger state list may be an RRC information element indicating multiple trigger states (e.g., CSI aperiodic trigger states) for a corresponding carrier. An RRC signal transmission may include multiple CSI aperiodic trigger state lists, each corresponding to a different carrier. As used herein, the term "CSI aperiodic trigger state list" means an indication of multiple CSI aperiodic trigger states.

[0090] As mentioned earlier, trigger signal delivery (e.g., MAC-CE, DCI, or other control information) can trigger trigger states from a CSI aperiodic trigger state list. For example, a trigger signal delivery may include a trigger state indication field, which includes coded points or bit maps indicating trigger states in the CSI aperiodic trigger state list. The trigger signal delivery can indicate the trigger state for each carrier. For example, as shown in Figure 10, the trigger signal delivery may include a trigger state indication field for each carrier associated with a corresponding CSI aperiodic trigger state list for that carrier. In this way, the trigger signal delivery can indicate trigger states (e.g., CSI aperiodic trigger states from the CSI aperiodic trigger state list) on a carrier-by-carrier basis. Therefore, based on the CSI aperiodic trigger state list provided on a carrier-by-carrier basis, CSI report configurations (e.g., as indicated by CSI-ReportConfig) associated with each corresponding trigger state can be configured and triggered for each carrier.

[0091] As shown in the figure, each trigger state can be associated with one or more CSI-RS configurations (CSI-AssociatedReportConfigInfo). In the example shown, the first trigger state in the list for CC1 is associated with two CSI-RS configurations (1020-1 and 1020-2). By associating multiple RS configurations with a single trigger state, multiple aperiodic RSs can be triggered simultaneously (and used as temporary RSs).

[0092] The carrier that triggers a temporary RS over a given trigger state can be a carrier associated with a list of associated trigger states. For example, if a trigger state from list 1010-1 for CC1 is triggered, then the CSI-ResourceConfigID carrier can be assumed to be CC1.

[0093] As mentioned above, a MAC-CE can initiate a SCell and indicate the RS configuration to be monitored in the SCell. Various methods exist for designing a MAC-CE suitable for indicating RS configuration in the manner proposed herein (e.g., via indicating a trigger state for triggering a temporary RS).

[0094] Depending on an option, MAC-CE can have multiple bit blocks (which may be referred to as Z-bit blocks), where each SCell has a defined Z-bit block, where the value of Z is greater than or equal to zero. For a given SCell, the Z-bit block can indicate a temporary RS (e.g., using a configuration index for the SCell). In some cases, the nth coded point of the Z-bit block can indicate the nth trigger state in the trigger state list for the SCell. A zero value for the Z-bit block can indicate that no temporary RS resource is available for transmission for the corresponding SCell.

[0095] In some cases, the SCell to be launched can be indicated by certain values ​​(C values) in the MAC CE, which also triggers a temporary RS. In cases where a separate DCI is used to trigger a temporary RS, the C value of the existing SCell launch / delaunch MAC CE (e.g., in the traditional MAC CE format) can be used to indicate the SCell to be launched. Instance methods

[0096] Figure 11 illustrates an example operation 1100 for wireless communication by a UE. Operation 1100 can be performed, for example, by a UE (e.g., UE 104 in Figure 1) to monitor a temporary RS on a cocell based on a reference signal (RS) configuration associated with a trigger state.

[0097] At 1110, the UE receives a Radio Resource Control (RRC) signal transmission that configures the UE to perform Channel State Information (CSI) reporting using a per-carrier aperiodic triggered state list for one or more types of Reference Signals (RS).

[0098] At 1120, the UE receives a dynamic signal transmission that activates a secondary cell and indicates at least one trigger state from the per-carrier aperiodic trigger state list associated with the secondary cell.

[0099] At 1130, the UE monitors the temporary RS on the cocell based at least in part on at least one RS configuration associated with at least one trigger state.

[0100] Figure 12 illustrates an example operation 1200 for wireless communication by a network entity. Operation 1200 can be performed, for example, by a network entity (e.g., network entity 102 in Figure 1) to send a dynamic signal transmission indicating at least one trigger state from a list of aperiodic trigger states for each carrier.

[0101] At 1210, the network entity sends an RRC signal to the UE, which configures the UE to perform CSI reporting using a per-carrier aperiodic triggering state list for one or more types of RS.

[0102] At 1220, the network entity sends a dynamic signal transmission to initiate a secondary cell and instructs the transmission of at least one trigger state from the per-carrier aperiodic trigger state list associated with the secondary cell, in order to trigger the UE to monitor the temporary RS transmitted on the secondary cell at least in part based on at least one RS configuration associated with at least one trigger state.

[0103] Figure 13 illustrates an example operation 1300 for wireless communication by a UE. Operation 1300 can be performed, for example, by a UE (such as UE 104 in Figure 1) to monitor a temporary reference signal (RS) on a cocell based on an RS configuration associated with a trigger state.

[0104] At 1310, the UE receives a Radio Resource Control (RRC) signal transmission that configures the UE to have one or more per-carrier reference signals (RS) configurations.

[0105] At 1320, the UE receives a dynamic signal delivery that initiates a co-cell and indicates at least one of one or more per-carrier RS ​​configurations.

[0106] At 1330, the UE monitors the temporary RS on the cocell based at least in part on at least one RS configuration indicated by dynamic signaling in one or more RS configurations.

[0107] Figure 14 illustrates an example operation 1400 for wireless communication by a network entity. Operation 1400 can be performed, for example, by a network entity (e.g., network entity 102 in Figure 1) to send a dynamic signal transmission indicating at least one trigger state from a list of aperiodic trigger states for each carrier.

[0108] At 1410, the network entity sends a Radio Resource Control (RRC) signal to the UE, which configures the user equipment (UE) to have one or more per-carrier reference signals (RS) configurations.

[0109] At 1420, the network entity sends a dynamic signal transmission that initiates a secondary cell and instructs at least one per-carrier RS ​​configuration from one or more per-carrier RS ​​configurations for temporary RS transmissions on the secondary cell. Examples of wireless communication devices

[0110] Figure 15 illustrates an example communication device 1500, which includes various components operable to, configured to, or adapted to perform operations for the techniques disclosed herein (such as those illustrated and described with respect to Figures 11 and 13). In some instances, the communication device 1500 may be, for example, a user device 104 as described with respect to Figures 1 and 2.

[0111] Communication device 1500 includes a processing system 1502 coupled to transceiver 1508 (e.g., transmitter and / or receiver). Transceiver 1508 is configured to transmit (or send) and receive signals for communication device 1500, such as the various signals described herein, via antenna 1510. Processing system 1502 may be configured to perform processing functions for communication device 1500, including processing signals received and / or to be transmitted by communication device 1500.

[0112] Processing system 1502 includes one or more processors 1520 coupled to computer-readable media / memory 1530 via bus 1506. In some embodiments, computer-readable media / memory 1530 is configured to store instructions (e.g., computer-executable code) that, when executed by one or more processors 1520, cause one or more processors 1520 to perform the operations shown in Figures 11 and 13, or other operations for performing the various techniques discussed herein for receiving channel status information (CSI) reports with a per-carrier-triggered status list.

[0113] In the illustrated example, the computer-readable media / memory 1530 stores: code 1531 for receiving an RRC signal transmission that configures the UE to perform CSI reporting using a per-carrier aperiodic trigger state list for one or more types of RS; code 1532 for receiving a dynamic signal transmission that initiates a cocell and indicates at least one trigger state from the per-carrier aperiodic trigger state list associated with the cocell; and code 1533 for monitoring temporary RSs on the cocell based at least in part on at least one RS configuration associated with at least one trigger state. In addition, the computer-readable media / memory 1530 stores: code for receiving a Radio Resource Control (RRC) signal transmission that configures the UE to have one or more per-carrier reference signal (RS) configurations; code for receiving a dynamic signal transmission that initiates a helper cell and indicates at least one of the one or more per-carrier RS ​​configurations; and code for monitoring a temporary RS on the helper cell based at least in part on at least one RS configuration indicated by the dynamic signal transmission among the one or more RS configurations.

[0114] In the illustrated example, one or more processors 1520 include circuitry configured to implement code stored in computer-readable media / memory 1530, comprising: circuitry 1521 for receiving an RRC signal transmission that configures the UE to perform CSI reporting using a per-carrier aperiodic trigger state list for one or more types of RS; circuitry 1522 for receiving a dynamic signal transmission that initiates a co-cell and indicates at least one trigger state from the per-carrier aperiodic trigger state list associated with the co-cell; and circuitry 1523 for monitoring temporary RSs on the co-cell based at least in part on at least one RS configuration associated with at least one trigger state. Furthermore, one or more processors 1520 include circuitry configured to implement code stored in computer-readable media / memory 1530, comprising: circuitry for RRC signal transmission that configures the UE to have one or more per-carrier RS ​​configurations; circuitry for receiving dynamic signal transmission that initiates a co-cell and indicates at least one of the one or more per-carrier RS ​​configurations; and circuitry for monitoring temporary RS on the co-cell based at least in part on at least one RS configuration indicated by the dynamic signal transmission among the one or more RS configurations.

[0115] Various components of the communication device 1500 can provide units for performing the methods described herein (including with respect to Figures 11 and 13).

[0116] In some instances, the unit for transmitting or sending (or the unit for outputting for transmission) may include the transceiver 254 and / or antenna 252 of the user equipment 104 shown in FIG. 2 and / or the transceiver 1508 and antenna 1510 of the communication device 1500 shown in FIG. 15.

[0117] In some instances, the unit for receiving (or the unit for obtaining) may include transceiver 254 and / or antenna 252 of user equipment 104 shown in FIG. 2 and / or transceiver 1508 and antenna 1510 of communication equipment 1500 shown in FIG. 15.

[0118] In some instances, the unit used for receiving and / or monitoring may include various processing system components, such as one or more processors 1520 in FIG15, or various forms of user equipment 104 illustrated in FIG2, including a receive processor 258, a transmit processor 264, a TX MIMO processor 266, and / or a controller / processor 280 (including a CSI report configuration 281 for receiving a per-carrier trigger status list).

[0119] It is worth noting that Figure 15 is an example, and many other examples and configurations of the communication device 1500 are possible.

[0120] Figure 16 illustrates an example communication device 1600, which includes various components operable to, configured to, or adapted to perform operations for the techniques disclosed herein (such as those illustrated and described with respect to Figures 12 and 14). In some instances, the communication device 1600 may be a network entity 102 as described, for example, with respect to Figures 1 and 2.

[0121] The communication device 1600 includes a processing system 1602 coupled to a transceiver 1608 (e.g., a transmitter and / or receiver). The transceiver 1608 is configured to transmit (or send) and receive signals for the communication device 1600, such as the various signals described herein, via an antenna 1610. The processing system 1602 may be configured to perform processing functions for the communication device 1600, including processing signals received and / or to be transmitted by the communication device 1600.

[0122] Processing system 1602 includes one or more processors 1620 coupled to computer-readable media / memory 1630 via bus 1606. In some embodiments, computer-readable media / memory 1630 is configured to store instructions (e.g., computer-executable code) that, when executed by one or more processors 1620, cause one or more processors 1620 to perform the operations shown in Figures 12 and 14, or other operations for performing the various techniques discussed herein for transmitting CSI reports with a per-carrier-triggered status list.

[0123] In the illustrated example, the computer-readable media / memory 1630 stores: code 1631 for sending an RRC signal transmission to the UE, the RRC signal transmission configuring the UE to perform CSI reporting using a per-carrier aperiodic trigger state list for one or more types of RS; and code 1632 for sending a dynamic signal transmission to initiate a secondary cell and indicate at least one trigger state from the per-carrier aperiodic trigger state list associated with the secondary cell, to trigger the UE to monitor temporary RS transmitted on the secondary cell at least in part based on at least one RS configuration associated with at least one trigger state. Furthermore, the computer-readable media / memory 1630 stores: code for sending an RRC signal transmission to the UE, the RRC configuring the UE to have one or more per-carrier RS ​​configurations; and code for sending a dynamic signal transmission to initiate a secondary cell and indicate at least one per-carrier RS ​​configuration from one or more per-carrier RS ​​configurations for temporary RS transmission on the secondary cell.

[0124] In the illustrated example, one or more processors 1620 include circuitry configured to implement code stored in computer-readable media / memory 1630, comprising: circuitry 1621 for sending an RRC signal transmission to the UE, the RRC signal transmission configuring the UE to perform CSI reporting using a per-carrier aperiodic trigger state list for one or more types of RS; and circuitry 1622 for sending a start cocell and indicating at least one trigger state from the per-carrier aperiodic trigger state list associated with the cocell, to trigger the UE to monitor temporary RS transmitted on the cocell at least in part based on at least one RS configuration associated with at least one trigger state. Furthermore, one or more processors 1620 include circuitry configured to implement code stored in computer-readable media / memory 1630, comprising: circuitry for sending an RRC signal transmission to the UE, the RRC configuring the UE to have one or more per-carrier RS ​​configurations; and circuitry for sending a dynamic signal transmission that initiates a co-cell and indicates at least one per-carrier RS ​​configuration among the one or more per-carrier RS ​​configurations for temporary RS transmission on the co-cell.

[0125] Various components of the communication device 1600 can provide units for performing the methods described herein (including with respect to Figures 12 and 14).

[0126] In some instances, the unit for transmitting or sending (or the unit for outputting for transmission) may include transceiver 232 and / or antenna 234 of network entity 102 shown in FIG2 and / or transceiver 1608 and antenna 1610 of communication device 1600 in FIG16.

[0127] In some instances, the unit for receiving (or the unit for obtaining) may include transceiver 232 and / or antenna 234 of the network entity shown in FIG2 and / or transceiver 1608 and antenna 1610 of communication device 1600 in FIG16.

[0128] In some instances, the unit used for transmitting may include various processing system components, such as one or more processors 1620 in FIG16, or various forms of network entity 102 illustrated in FIG2, including receiver processor 238, transmitter processor 220, TX MIMO processor 230 and / or controller / processor 240 (including CSI reporting component 241).

[0129] It is worth noting that Figure 16 is an example, and many other examples and configurations of the communication device 1600 are possible. Example Terms

[0130] Implementation examples are described in the following numbered clauses:

[0131] Clause 1: A method for wireless communication by a user equipment (UE), comprising: receiving a radio resource control (RRC) signal transmission, the RRC signal transmission configuring the UE to have one or more per-carrier reference signal (RS) configurations; receiving a dynamic signal transmission, the dynamic signal transmission activating a secondary cell and indicating at least one of the one or more per-carrier RS ​​configurations; and monitoring temporary RS on the secondary cell based at least in part on the at least one RS configuration indicated by the dynamic signal transmission among the one or more RS configurations.

[0132] Clause 2: The method of Clause 1, wherein the provisional RS includes at least one of CSI-RS or Tracking RS (TRS).

[0133] Clause 3: The method according to any one of Clauses 1-2, wherein the at least one RS configuration associated with at least one trigger state in one or more RS configurations includes an RS configuration associated with a CSI reporting configuration for a list of carriers with a per-carrier aperiodic trigger states associated with the cocell.

[0134] Clause 4: The method according to any one of Clauses 1-3, wherein the dynamic signal transmission includes initiating the Media Access Control (MAC) control element (CE) of the co-cell.

[0135] Clause 5: According to the method of Clause 4, the dynamic signal transmission also includes downlink control information (DCI) indicating at least one trigger state.

[0136] Clause 6: The method according to any one of Clauses 4-5, wherein the MAC CE indicates the at least one trigger state.

[0137] Clause 7: The method according to any one of Clauses 4-6, wherein the MAC CE includes a bit block associated with the co-cell.

[0138] Clause 8: According to the method of Clause 7, wherein the bit block identifies the at least one RS configuration in one or more RS configurations that indicates the temporary RS.

[0139] Clause 9: The method according to any one of Clauses 7-8, wherein the zero value of the bit block indicates that a temporary RS is not used for the co-cell.

[0140] Clause 10: The method according to any one of Clauses 4-9, wherein: the MAC CE initiates a plurality of co-cells; and the MAC CE includes a plurality of bit blocks, wherein each of the bit blocks is associated with a different co-cell among the plurality of co-cells initiated by the MAC CE.

[0141] Clause 11: A method for wireless communication by a network entity, comprising: transmitting a Radio Resource Control (RRC) signal transmission that configures a User Equipment (UE) to have one or more per-carrier Reference Signal (RS) configurations; and transmitting a dynamic signal transmission that initiates a secondary cell and indicates at least one of the one or more per-carrier RS ​​configurations for temporary RS transmissions on the secondary cell.

[0142] Clause 12: The method of Clause 11, wherein the provisional RS includes at least one of a CSI-RS or a tracking RS (TRS).

[0143] Clause 13: The method according to any one of Clauses 11-12, wherein the at least one RS configuration associated with at least one trigger state in one or more RS configurations includes an RS configuration associated with a CSI reporting configuration for a list of carrier-based non-periodic trigger states associated with the cocell.

[0144] Clause 14: The method according to any one of Clauses 11-13, wherein the dynamic signal transmission includes initiating the media access control (MAC) control element (CE) of the co-cell.

[0145] Clause 15: The method of Clause 14, wherein the dynamic signal transmission also includes downlink control information (DCI) indicating at least one trigger state.

[0146] Clause 16: The method according to any one of Clauses 14-15, wherein the MAC CE indicates at least one trigger state.

[0147] Clause 17: The method of Clause 16, wherein the MAC CE comprises a plurality of bit blocks, each bit block being associated with a different cocell.

[0148] Clause 18: The method of Clause 17, wherein the bit block identifies the at least one RS configuration in one or more RS configurations that indicates the temporary RS.

[0149] Clause 19: The method according to any one of Clauses 16-18, wherein the network entity is configured to set a bit block to a zero value to indicate that a temporary RS is not used for the auxiliary cell.

[0150] Clause 20: The method according to any one of Clauses 14-19, wherein: the MAC CE initiates a plurality of co-cells; and the MAC CE includes a plurality of bit blocks, wherein each of the bit blocks is associated with a different co-cell among the plurality of co-cells initiated by the MAC CE.

[0151] Clause 21: A method for wireless communication by a user equipment (UE), comprising: receiving a radio resource control (RRC) signal transmission that configures the UE to perform channel state information (CSI) reporting using a per-carrier aperiodic trigger state list for one or more types of reference signals (RS); receiving a dynamic signal transmission that activates a secondary cell and indicates at least one trigger state from a per-carrier aperiodic trigger state list associated with the secondary cell; and monitoring temporary RS on the secondary cell based at least in part on at least one RS configuration associated with the at least one trigger state among the one or more RS configurations.

[0152] Clause 22: The method of Clause 21, wherein the provisional RS includes at least one of a CSI-RS or a tracking RS (TRS).

[0153] Clause 23: The method according to any one of Clauses 21 to 22, wherein the at least one RS configuration associated with the at least one trigger state in the one or more RS configurations includes an RS configuration associated with a CSI reporting configuration for a list of carriers with a per-carrier aperiodic trigger states associated with the cocell.

[0154] Clause 24: The method according to any one of Clauses 21 to 23, wherein the dynamic signal transmission includes initiating the media access control (MAC) control element (CE) of the co-cell.

[0155] Clause 25: The method of Clause 24, wherein the dynamic signal transmission also includes downlink control information (DCI) indicating the at least one trigger state.

[0156] Clause 26: The method according to any one of Clauses 24 to 25, wherein the MAC CE indicates the at least one trigger state.

[0157] Clause 27: The method of Clause 26, wherein the MAC CE comprises a plurality of bit blocks, each bit block being associated with a different cocell.

[0158] Clause 28: According to the method of Clause 27, the bit block associated with the auxiliary cell initiated by the MAC CE indicates the temporary RS by indicating the at least one trigger state associated with the auxiliary cell from the per-carrier non-periodic trigger state list.

[0159] Clause 29: The method of Clause 28, wherein the UE is configured to interpret a zero value for a bit block as an indication that a temporary RS is not triggered for a cocell associated with the bit block.

[0160] Clause 30: The method according to any one of Clauses 26 to 29, wherein a separate set of bits in the MAC CE indicates the activated co-cell.

[0161] Clause 31: A method for wireless communication by a network entity, comprising: sending a Radio Resource Control (RRC) signal to a User Equipment (UE), the RRC signal configuring the UE to perform Channel State Information (CSI) reporting using a per-carrier aperiodic trigger state list for one or more types of RS; and sending a dynamic signal to activate a secondary cell and indicate at least one trigger state from the per-carrier aperiodic trigger state list associated with the secondary cell, to trigger the UE to monitor temporary RS transmitted on the secondary cell at least in part based on at least one RS configuration associated with the at least one trigger state in one or more RS configurations.

[0162] Clause 32: The method of Clause 31, wherein the provisional RS includes at least one of a CSI-RS or a tracking RS (TRS).

[0163] Clause 33: The method according to any one of Clauses 31 to 32, wherein the at least one RS configuration associated with the at least one trigger state in one or more RS configurations includes an RS configuration associated with a CSI reporting configuration for a list of carriers with a per-carrier aperiodic trigger states associated with the cocell.

[0164] Clause 34: The method according to any one of Clauses 31 to 33, wherein the dynamic signal transmission includes initiating the media access control (MAC) control element (CE) of the co-cell.

[0165] Clause 35: The method according to Clause 34, wherein the dynamic signal transmission also includes downlink control information (DCI) indicating the at least one trigger state.

[0166] Clause 36: The method according to any one of Clauses 34 to 35, wherein the MAC CE indicates the at least one trigger state.

[0167] Clause 37: The method of Clause 36, wherein the MAC CE comprises a plurality of bit blocks, each bit block being associated with a different cocell.

[0168] Clause 38: According to the method of Clause 37, the bit block associated with the auxiliary cell initiated by the MAC CE indicates the temporary RS by indicating at least one trigger state associated with the auxiliary cell from the per-carrier non-periodic trigger state list.

[0169] Clause 39: The method according to any one of Clauses 36 to 38, wherein a separate set of bits in the MAC CE indicates the activated co-cell.

[0170] Clause 40: An apparatus comprising: a memory including executable instructions; and one or more processors configured to execute the executable instructions and cause the apparatus to perform the method according to any one of Clauses 1-39.

[0171] Clause 41: An apparatus comprising: a unit for performing the method according to any one of Clauses 1-39.

[0172] Clause 42: A non-transitory computer-readable medium comprising executable instructions that, when executed by one or more processors of a device, cause the device to perform the method according to any one of Clauses 1-39.

[0173] Clause 43: A computer program product embodied on a computer-readable storage medium, including code for performing the method pursuant to any one of Clauses 1-39. Additional wireless communication network considerations

[0174] The techniques and methods described herein can be used in a variety of wireless communication networks (or wireless wide area networks (WWAN)) and radio access technologies (RAT). Although terms commonly associated with 3G, 4G, and / or 5G (e.g., 5G New Radio (NR)) wireless technologies may be used in this document to describe various forms, the forms of the content herein are equally applicable to other communication systems and standards not explicitly mentioned herein.

[0175] 5G wireless communication networks can support a variety of advanced wireless communication services, such as enhanced mobile broadband (eMBB), millimeter wave (mmWave), machine-type communications (MTC), and / or mission-critical services targeting ultra-reliable low-latency communications (URLLC). These and other services may include latency and reliability requirements.

[0176] Returning to Figure 1, the various states of this case can be executed within the instance wireless communication network 100.

[0177] In 3GPP, the term "cell" can refer to the coverage area of ​​a Node B and / or the narrowband subsystem serving that coverage area, depending on the context in which the term is used. In NR systems, the term "cell" is used interchangeably with network entities, next-generation Node Bs (gNBs or gNodeBs), access points (APs), distributed units (DUs), carriers, or transmit / receive points. Network entities can provide communication coverage for macrocells, picocells, femtocells, and / or other types of cells.

[0178] Macro cells typically cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access by UEs with service subscriptions. Pico cells cover a relatively small geographic area (e.g., a stadium) and allow unrestricted access by UEs with service subscriptions. Femto cells cover a relatively small geographic area (e.g., a residential area) and allow restricted access by UEs associated with that femto cell (e.g., UEs in a Closed Subscriber Group (CSG) and UEs for users in a residential area). The network entity used for a macro cell may be referred to as a macro base station (BS). The network entity used for a pico cell may be referred to as a pico BS. The network entity used for a femto cell may be referred to as a femto BS, a home BS, or a home node B.

[0179] Network entity 102 configured for 4G LTE (collectively referred to as Evolutionary Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with EPC 160 via a first backhaul link 132 (e.g., S1 interface). Network entity 102 configured for 5G (e.g., 5G NR or Next Generation RAN (NG-RAN)) can interface with 5GC 190 via a second backhaul link 184. Network entities 102 can communicate directly or indirectly with each other (e.g., via EPC 160 or 5GC 190) on a third backhaul link 134 (e.g., X2 interface). The third backhaul link 134 can typically be wired or wireless.

[0180] Wireless communication network 100 can subdivide the electromagnetic spectrum into various categories, bands, channels, or other characteristics. In some cases, this subdivision is based on wavelength and frequency, where frequency may also be referred to as carrier, subcarrier, frequency channel, tone, or subband. For example, 3GPP currently defines frequency range 1 (FR1) as including 410 MHz–7125 MHz, which is often (interchangeably) referred to as "below 6 GHz". Similarly, 3GPP currently defines frequency range 2 (FR2) as including 24,250 MHz–52,600 MHz, which is sometimes also (interchangeably) referred to as "millimeter wave" ("mmW" or "mmWave"). Network entities configured to communicate using mmWave / near mmWave radio frequency bands (e.g., mmWave network entities, such as network entity 180) can utilize beamforming (e.g., 182) with UE (e.g., 104) to improve path loss and range.

[0181] The small cell 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, the small cell 102' can employ NR and use the same 5 GHz unlicensed spectrum as used by the Wi-Fi AP 150. Employing NR in unlicensed spectrum can improve coverage of the access network and / or increase the capacity of the access network.

[0182] Some network entities (such as gNB 180) can operate in conventional sub-6 GHz spectrum, millimeter wave (mmWave) frequencies, and / or near-mmWave frequencies to communicate with UE 104. When gNB 180 operates in mmWave or near-mmWave frequencies, gNB 180 can be referred to as an mmWave network entity.

[0183] The communication link 120 between network entity 102 and, for example, UE 104 can be via one or more carriers. For example, network entity 102 and UE 104 can use a spectrum of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, and other MHz) bandwidth per carrier, allocated in carrier aggregation for transmission in each direction. Carriers can be adjacent to each other or can be non-adjacent. Carrier allocation can be asymmetric with respect to DL and UL (e.g., more or fewer carriers can be allocated for DL ​​compared to UL). Component carriers can include primary component carriers and one or more secondary component carriers. The primary component carrier can be referred to as the primary cell (PCell), and the secondary component carriers can be referred to as secondary cells (SCells).

[0184] The wireless communication system 100 also includes a Wi-Fi access point (AP) 150, which communicates with a Wi-Fi station (STA) 152 via a communication link 154 in, for example, unlicensed spectrum of 2.4 GHz and / or 5 GHz. When communicating in unlicensed spectrum, the STA 152 / AP 150 can perform an idle channel assessment (CCA) before communication to determine whether the channel is available.

[0185] Some UEs 104 can communicate with each other using device-to-device (D2D) communication link 158. D2D communication link 158 can use DL / UL WWAN spectrum. D2D communication link 158 can use one or more sideline channels, such as the physical sideline broadcast channel (PSBCH), physical sideline discovery channel (PSDCH), physical sideline shared channel (PSSCH), and physical sideline control channel (PSCCH). D2D communication can be via a wide variety of wireless D2D communication systems, such as FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, 4G (e.g., LTE), or 5G (e.g., NR), to name a few.

[0186] EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a service gateway 166, a Multimedia Broadcast Multicast Service (MBMS) gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) gateway 172. MME 162 can communicate with the Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signal transfer between UE 104 and EPC 160. Typically, MME 162 provides bearer and connection management.

[0187] Typically, user Internet Protocol (IP) packets are transmitted via service gateway 166, which is itself connected to PDN gateway 172. PDN gateway 172 provides IP address allocation and other functions to the UE. PDN gateway 172 and BM-SC 170 are connected to IP service 176, which may include, for example, the Internet, intranet, IP Multimedia Subsystem (IMS), PS streaming service, and / or other IP services.

[0188] The BM-SC 170 provides functions for MBMS user service setup and delivery. The BM-SC 170 can act as an entry point for MBMS delivery to content providers, authorize and initiate MBMS bearer services within the Public Land Mobile Network (PLMN), and schedule MBMS delivery. The MBMS gateway 168 can distribute MBMS traffic to network entities 102 belonging to the Multicast-Broadcast Single Frequency Network (MBSFN) area that broadcasts specific services, and can be responsible for communication period management (start / stop) and collecting billing information related to eMBMS.

[0189] 5GC 190 may include Access and Mobility Management Functions (AMF) 192, other AMFs 193, Communication Management Functions (SMF) 194, and User Plane Functions (UPF) 195. AMF 192 can communicate with Unified Data Management (UDM) 196.

[0190] The AMF 192 is typically the control node that handles signal transmission between UE 104 and 5GC 190. Typically, the AMF 192 provides QoS flow and communication period management.

[0191] All user Internet Protocol (IP) packets are transmitted via UPF 195, which connects to IP service 197 and provides the UE with IP address allocation and other functions for 5GC 190. IP service 197 may include, for example, the Internet, intranet, IP Multimedia Subsystem (IMS), PS streaming service, and / or other IP services.

[0192] Returning to Figure 2, various example components of network entity 102 and UE 104 (e.g., wireless communication network 100 of Figure 1) are illustrated, which can be used to implement various forms of the content of this case.

[0193] At network entity 102, the transmitting processor 220 can receive data from data source 212 and control information from controller / processor 240. The control information can be used for the entity broadcast channel (PBCH), entity control format indicator channel (PCFICH), entity mixed ARQ indicator channel (PHICH), entity downlink control channel (PDCCH), group common PDCCH (GC PDCCH), and other channels. In some instances, the data can be used for the entity downlink shared channel (PDSCH).

[0194] The Media Access Control (MAC)-Control Element (MAC-CE) is a MAC layer communication structure used for exchanging control commands between wireless nodes. The MAC-CE can be carried in shared channels (such as the Physical Downlink Shared Channel (PDSCH), Physical Uplink Shared Channel (PUSCH), or Physical Side-Link Shared Channel (PSSCH)).

[0195] Processor 220 can process (e.g., encoding and symbol mapping) data and control information separately to obtain data symbols and control symbols. Transmitter processor 220 can also generate reference symbols, such as those used for the primary synchronization signal (PSS), secondary synchronization signal (SSS), PBCH demodulation reference signal (DMRS), and channel status information reference signal (CSI-RS).

[0196] The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, and / or reference symbols (if applicable), and can provide output symbol streams to the modulators (MODs) in transceivers 232a-232t. Each modulator in transceivers 232a-232t can process its respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modulator can further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The downlink signals from the modulators in transceivers 232a-232t can be transmitted via antennas 234a-234t respectively.

[0197] At UE 104, antennas 252a-252r can receive downlink signals from network entity 102 and can provide the received signals to demodulators (DEMODs) in transceivers 254a-254r respectively. Each demodulator in transceivers 254a-254r can modulate (e.g., filter, amplify, downconvert, and digitize) its respective received signal to obtain an input sample. Each demodulator can further process the input sample (e.g., for OFDM) to obtain received symbols.

[0198] MIMO detector 256 can obtain received symbols from all demodulators in transceivers 254a-254r, perform MIMO detection on the received symbols (if applicable), and provide the detected symbols. Receiver processor 258 can process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for UE 104 to data slot 260, and provide decoded control information to controller / processor 280.

[0199] On the uplink, at UE 104, the transmitting processor 264 can receive and process data from data source 262 (e.g., for the Entity Uplink Shared Channel (PUSCH)) and control information from controller / processor 280 (e.g., for the Entity Uplink Control Channel (PUCCH)). The transmitting processor 264 can also generate reference symbols for reference signals (e.g., for the Sounding Reference Signal (SRS)). Symbols from the transmitting processor 264 can be pre-encoded by the TX MIMO processor 266 (if applicable), further processed by the modulators in transceivers 254a-254r (e.g., for SC-FDM), and transmitted to network entity 102.

[0200] At network entity 102, uplink signals from UE 104 can be received by antennas 234a-t, processed by demodulators in transceivers 232a-232t, detected by MIMO detector 236 (if applicable), and further processed by receiver processor 238 to obtain decoded data and control information transmitted by UE 104. Receiver processor 238 can provide decoded data to data slot 239 and decoded control information to controller / processor 240.

[0201] Memory 242 and 282 can store data and code for network entity 102 and UE 104, respectively.

[0202] Scheduler 244 can schedule UE to perform data transmission on downlink and / or uplink.

[0203] 5G can utilize Orthogonal Frequency Division Multiplexing (OFDM) with a Cyclic Prefix (CP) on both the uplink and downlink. 5G can also support half-duplex operation using Time Division Duplex (TDD). OFDM and Single Carrier Frequency Division Multiplexing (SC-FDM) divide the system bandwidth into multiple orthogonal subcarriers, often referred to as tones and bands. Data can be used to modulate each subcarrier. Modulation symbols are transmitted using OFDM in the frequency domain and SC-FDM in the time domain. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers can depend on the system bandwidth. In some instances, the minimum resource configuration, called a Resource Block (RB), can be 12 consecutive subcarriers. The system bandwidth can also be divided into subbands. For example, a subband can cover multiple RBs. NR can support a basic subcarrier spacing (SCS) of 15 kHz, and can define other SCSs (e.g., 30 kHz, 60 kHz, 120 kHz, 240 kHz, and other SCSs) with respect to the basic SCS.

[0204] As mentioned above, Figures 3A-3D illustrate various instances of data structures used in wireless communication networks (such as the wireless communication network 100 in Figure 1).

[0205] In various configurations, the 5G frame structure can be Frequency Division Duplex (FDD), where, for a given set of subcarriers (carrier system bandwidth), subframes within that set are dedicated to either DL or UL. The 5G frame structure can also be Time Division Duplex (TDD), where, for a given set of subcarriers (carrier system bandwidth), subframes within that set are dedicated to both DL and UL. In the examples provided in Figures 3A and 3C, the 5G frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (mostly DL), where D is DL, U is UL, and X is flexible between DL / UL, and subframe 3 is configured with slot format 34 (mostly UL). Although subframes 3 and 4 are shown as having slot formats 34 and 28 respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are all DL and all UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The UE is configured with a slot format via the received Slot Format Indicator (SFI) (either dynamically configured via DL Control Information (DCI) or semi-statically / statically configured via Radio Resource Control (RRC) signals). Note that the following description also applies to 5G frame structures as TDD.

[0206] Other wireless communication technologies can have different frame structures and / or different channels. A frame (10 ms) can be divided into 10 equal-sized subframes (1 ms). Each subframe can include one or more time slots. Subframes can also include micro-time slots, which can include 7, 4, or 2 symbols. In some instances, each time slot can include 7 or 14 symbols, depending on the time slot configuration.

[0207] For example, for slot configuration 0, each slot can include 14 symbols, while for slot configuration 1, each slot can include 7 symbols. Symbols on the DL can be Cyclic Prefix (CP) OFDM (CP-OFDM) symbols. Symbols on the UL can be CP-OFDM symbols (for high-volume scenarios) or Discrete Fourier Transform (DFT) Extended OFDM (DFT-s-OFDM) symbols (also known as Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols) (for power-constrained scenarios; limited to a single stream).

[0208] The number of time slots within a subframe can be based on the time slot configuration and the digital scheme (numerology). For time slot configuration 0, different digital schemes (µ) 0 to 5 allow 1, 2, 4, 8, 16, and 32 time slots per subframe, respectively. For time slot configuration 1, different digital schemes 0 to 2 allow 2, 4, and 8 time slots per subframe, respectively. Accordingly, for time slot configuration 0 and digital scheme µ, there are 14 symbols / time slots and 2µ time slots / subframe. The subcarrier spacing and symbol length / duration are functions of the digital scheme. The subcarrier spacing can be equal to... kHz, where μ is the subcarrier spacing for digital schemes 0 through 5. Therefore, digital scheme µ=0 has a subcarrier spacing of 15 kHz, and digital scheme µ=5 has a subcarrier spacing of 480 kHz. The symbol length / duration is negatively correlated with the subcarrier spacing. Figures 3A-3D provide examples of slot configuration 0 with 14 symbols per slot and digital scheme µ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 µs.

[0209] A resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also known as a physical RB (PRB)), which extends 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0210] As shown in Figure 3A, some REs in the REs carry reference (pilot) signals (RS) for the UE (e.g., UE 104 in Figures 1 and 2). The RS may include a demodulation RS (DM-RS) for channel estimation at the UE (indicated as Rx for a specific configuration, where 100x is the port number, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS). The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0211] Figure 3B illustrates examples of various DL channels within a sub-frame of a frame. The physical downlink control channel (PDCCH) carries the DCI within one or more control channel elements (CCEs). Each CCE includes nine RE groups (REGs), and each REG includes four consecutive REs in an OFDM symbol.

[0212] The primary synchronization signal (PSS) can be located within symbol 2 of a specific subframe of the frame. The PSS is used by UE 104 (e.g., 104 in Figures 1 and 2) to determine subframe / symbol timing and entity layer identification.

[0213] The secondary synchronization signal (SSS) can be located within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the physical layer cell identifier group number and the radio frame timing.

[0214] Based on the entity layer identifier and entity layer cell identifier group number, the UE can determine the entity cell identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DM-RS. The entity broadcast channel (PBCH) (which carries the main information block (MIB)) can be logically packetized with the PSS and SSS to form a synchronization signal (SS) / PBCH block. The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The entity downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (such as the system information block (SIB)), and paging messages.

[0215] As shown in Figure 3C, some REs in the REs carry DM-RS for channel estimation at network entities (indicated as R for a specific configuration, but other DM-RS configurations are possible). The UE can transmit DM-RS for the Entity Uplink Control Channel (PUCCH) and for the Entity Uplink Shared Channel (PUSCH). PUSCH DM-RS can be transmitted in the first one or two symbols before the PUSCH. PUCCH DM-RS can be transmitted in different configurations depending on whether a short or long PUCCH is transmitted and the specific PUCCH format used. The UE can transmit a Sound Reference Signal (SRS). SRS can be transmitted in the last symbol of a subframe. SRS can have a comb structure, and the UE can transmit SRS on one of these combs. SRS can be used by network entities for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0216] Figure 3D illustrates examples of various UL channels within sub-frames of a frame. The PUCCH can be positioned as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and HARQ ACK / NACK feedback. The PUSCH carries data and can also be used to carry buffer status reports (BSR), power headroom reports (PHR), and / or UCI. Additional considerations

[0217] The foregoing description provides an example of monitoring a temporary RS on a cocell based on a reference signal (RS) configuration associated with a trigger state in a communication system. The foregoing description is provided to enable anyone skilled in the art to implement the various embodiments described herein. The embodiments discussed herein are not limited to the scope, applicability, or embodiments set forth in the claims. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments. For example, changes can be made to the functionality and arrangement of the elements discussed without departing from the scope of this invention. Various procedures or components can be omitted, substituted, or added as appropriate in the embodiments. For example, the described methods can be performed in a different order than described, and various steps can be added, omitted, or combined. Furthermore, features described with respect to some embodiments can be combined into others. For example, an apparatus or a method can be implemented using any number of embodiments set forth herein. Furthermore, the scope of this case is intended to encompass any apparatus or method implemented using a structure, function, or structure and function other than or different from the various forms of disclosure described herein. It should be understood that any form of disclosure described herein may be embodied by one or more elements of the claim.

[0218] The techniques described in this article can be used in various wireless communication technologies, such as 5G (e.g., 5G NR), 3GPP Long Term Evolution (LTE), improved LTE (LTE-A), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), Time Division Synchronous Code Division Multiple Access (TD-SCDMA), and other networks. The terms "network" and "system" are often used interchangeably. CDMA networks can implement radio technologies such as Universal Terrestrial Radio Access (UTRA), cdma2000, and others. UTRA includes Wideband CDMA (WCDMA) and other variations of CDMA. cdma2000 encompasses the IS-2000, IS-95, and IS-856 standards. TDMA networks can implement radio technologies such as Global System for Mobile Communications (GSM). OFDMA networks can implement radio technologies such as NR (e.g., 5G RA), Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, and others. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). LTE and LTE-A are versions of UMTS using E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization called the 3rd Generation Partnership Project (3GPP). cdma2000 and UMB are described in documents from an organization called the 3rd Generation Partnership Project 2 (3GPP2). NR is an emerging wireless communication technology currently being deployed.

[0219] The various illustrative logic blocks, modules, and circuits described in connection with this case may be implemented or executed using a general-purpose processor, DSP, ASIC, field-programmable gate array (FPGA) or other programmable logic device (PLD), individual gate or transistor logic, individual hardware components, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, a system-on-a-chip (SoC), or any other such configuration.

[0220] If implemented in hardware, the instance hardware setup may include a processing system within a wireless node. The processing system can be implemented using a bus architecture. Depending on the specific application and overall design constraints of the processing system, the bus may include any number of interconnecting buses and bridges. The bus can connect various circuits, including processors, machine-readable media, and bus interfaces. In addition, the bus interface can also be used to connect network interface cards (NICs) to the processing system via the bus. The NIC can be used to implement signal processing functions at the PHY layer. In the case of a user device (see Figure 1), a user interface (e.g., a keypad, display, mouse, joystick, touchscreen, biometric sensor, proximity sensor, light-emitting element, etc.) can also be connected to the bus. The bus can also connect various other circuits, such as timing sources, peripherals, voltage regulators, power management circuits, etc., which are well known in the art to which this invention pertains and will therefore not be described further. The processor may be implemented using one or more general-purpose and / or dedicated processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuitry capable of executing software. Those skilled in the art will recognize how the functions described for a processing system can be optimally implemented, depending on the specific application and the overall design constraints imposed on the system as a whole.

[0221] If implemented in software, such functionality can be stored as one or more instructions or codes on or transmitted via a computer-readable medium. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted to mean instructions, data, or any combination thereof. Computer-readable media includes both computer storage media and communication media, with communication media encompassing any media that facilitates the transfer of computer programs from one location to another. The processor can be responsible for managing buses and general-purpose processing, including executing software modules stored on machine-readable storage media. The computer-readable storage media can be coupled to the processor so that the processor can read information from and write information to the storage media. Alternatively, the storage media can be an integral part of the processor. For example, machine-readable media can include transmission lines, data-modulated carrier waves, and / or separate computer-readable storage media containing instructions stored thereon, all accessible to the processor via a bus interface. Alternatively or additionally, machine-readable media, or any portion thereof, may be integrated into the processor; for example, this could be cache memory and / or general-purpose temporary registers. Examples of machine-readable storage media include, for instance, RAM (Random Access Memory), flash memory, ROM (Read-Only Memory), PROM (Programmable Read-Only Memory), EPROM (Erasable Programmable Read-Only Memory), EEPROM (Electronic Erasable Programmable Read-Only Memory), temporary registers, magnetic disks, optical disks, hard drives, or any other suitable storage media, or any combination thereof. Machine-readable media may be embodied in computer program products.

[0222] Software modules can include a single instruction or many instructions, and can be distributed across several different code segments, within different programs, and across multiple storage media. Computer-readable media can include multiple software modules. Software modules include instructions that, when executed by a device such as a processor, cause the processing system to perform various functions. Software modules can include sending modules and receiving modules. Each software module can reside in a single storage device or be distributed across multiple storage devices. For example, when a trigger event occurs, a software module can be loaded from a hard drive into RAM. During the execution of a software module, the processor can load some of the instructions into cache memory to increase access speed. Subsequently, one or more cache memory lines can be loaded into a general temporary register for execution by the processor. It will be understood that when the functionality of a software module is referred to below, this functionality is implemented by the processor when executing the instructions from that software module.

[0223] As used in this article, the phrase "at least one of" in a list of items refers to any combination of those items, including a single member. For example, "at least one of a, b, or c" is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination with multiples of the same element (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0224] As used herein, the term "decision" encompasses a wide variety of actions. For example, "decision" can include calculation, operation, processing, deduction, investigation, examination (e.g., examining a table, database, or other data structure), ascertainment, and so on. Furthermore, "decision" can include receiving (e.g., receiving information), accessing (e.g., accessing data in memory), and so on. Additionally, "decision" can include parsing, selecting, choosing, creating, and so on.

[0225] The methods disclosed herein include one or more steps or actions for implementing the methods. These method steps and / or actions can be interchanged without departing from the scope of the claim. In other words, unless a specific order of steps or actions is specified, the order and / or use of a particular step and / or action can be modified without departing from the scope of the claim. Furthermore, the various operations of the methods described above can be performed by any suitable unit capable of performing the corresponding function. These units can include various hardware and / or software components and / or modules, including but not limited to: circuits, application-specific integrated circuits (ASICs), or processors. Typically, in the presence of operations as shown in the figures, those operations can have corresponding paired units plus functional components with similar numbering.

[0226] The following claims are not intended to be limited to the forms shown herein, but are given the full scope consistent with the wording of the claims. Within the claims, unless expressly stated otherwise, references to singular elements are not intended to mean "one and only one," but rather "one or more." Unless otherwise expressly stated, the term "some" means one or more. No claim element is to be interpreted under patent law unless it is expressly stated using the phrase "unit for…" or, in the case of a method claim, using the phrase "step for…". All structural and functional equivalents of the elements of the various forms described herein are expressly incorporated herein by reference and intended to be included by the claims, such structural and functional equivalents being known or to be known by one of ordinary skill in the art to which this invention pertains. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is expressly stated in the claims.

[0227] 100: Wireless Communication System 102: Network Entity 102': Small cells 104: User Equipment (UE) 110: Coverage Area 110': Coverage area 120: Communication Link 132: First reload link 134: Third reload link 150: Wi-Fi AP 152: Wi-Fi Station (STA) 154: Communication Link 158:D2D communication link 160: Evolution Packet Core (EPC) 162: Management Entity (MME) 164: Other MMEs 166: Service Gateway 168: Multimedia Broadcast Multicast Service (MBMS) Gateway 170: Broadcast Multicast Service Center (BM-SC) 172: Packet Data Network (PDN) Gateway 174: Home Subscriber Server (HSS) 176: IP Service 182: Beamforming 182': Sending direction 182'': Receiving direction 184: Second reload link 190: 5G Core (5GC) Network 192: Access and Mobility Management Functions (AMF) 193: Other AMF 194: Communication Management Function (SMF) 195: User Plane Function (UPF) 196: Unified Data Management (UDM) 197: IP Service 198: CSI Reporting Component 199: CSI Reporting Component 212: Source 220: Sending Processor 230:TX MIMO processor 232a: Transceiver 232t: Transceiver 234a: Antenna 234t: Antenna 236: MIMO Detector 238: Receiver Processor 239: Data Slot 240: Controller / Processor 241: CSI Reporting Components 242: Memory 244: Scheduler 252a: Antenna 252r: Antenna 254a: Transceiver 254r: Transceiver 256: MIMO Detector 258: Receiver Processor 260: Data Slot 262: Source 264: Send Processor 266:TX MIMO processor 280: Controller / Processor 281: CSI Reporting Component 282: Memory 300: Schematic diagram 330: Schematic diagram 350: Schematic diagram 380: Schematic diagram 410: Information Elements (IE) 420-1: Information Elements (IE) 420-2: Information Elements (IE) 500: Isochrones 502:SSB 504: Temporary RS 508: Startup command 510: Acknowledgement (ACK) 604: Temporary RS 612:PDSCH 700: Isochrones 704: Aperiodic Tracking Reference Signal (A-TRS) 706: Short pulse 800: Call Flowchart 806: Program 808: Program 810: Program 900: Call Flowchart 906: Program 908: Program 910: Program 912: Program 1010-1: List of First CSI Non-periodic Triggering States 1010-2: List of Second CSI Aperiodic Triggering States 1020-1: CSI-RS Configuration 1020-2: CSI-RS Configuration 1100: Operation 1110: Square 1120: Square 1130: Square 1200: Operation 1210: Square 1220: Square 1300: Operation 1310: Square 1320: Square 1330: Square 1400: Operation 1410: Square 1420: Square 1500: Communication equipment 1502: Processing System 1506: Busbar 1508: Transceiver 1510: Antenna 1520: Processor 1521: Circuit 1522: Circuit 1523: Circuit 1530: Computer-readable media / memory 1531: Code 1532: Code 1533: Code 1600: Communication equipment 1602: Processing System 1606: Busbar 1608: Transceiver 1610: Antenna 1620: Processor 1621: Circuit 1622: Circuit 1630: Computer-readable media / memory 1631: Code 1632: Code ACK: Confirmation CSI-RS: CSI Reference Signal DMRS: Demodulation Reference Signal PBCH: Physical Broadcast Channel PDCCH: Physical Downlink Control Channel PDSCH: Entity Downlink Shared Channel PSS: Primary Synchronization Signal PUCCH: Entity Uplink Control Channel PUSCH: Entity Uplink Shared Channel RB: Resource Block SSS: Secondary Synchronization Signal

[0228] Domestic storage information (please note in order of storage institution, date, and number) none Overseas storage information (please note in the order of storage country, institution, date, and number) none

Claims

1. A method for wireless communication by a user equipment (UE), comprising the steps of: receiving a radio resource control (RRC) signal transmission, the RRC signal transmission configuring the UE to have one or more per-carrier reference signal (RS) configurations; receiving a dynamic signal transmission, the dynamic signal transmission activating a slave cell and indicating at least one of the one or more per-carrier RS ​​configurations, wherein: The at least one per-carrier RS ​​configuration is associated with at least one trigger state of a per-carrier aperiodic trigger state list associated with the cocell; and the at least one per-carrier RS ​​configuration includes an RS configuration associated with a CSI reporting configuration for a carrier of the per-carrier aperiodic trigger state list associated with the cocell; and a temporary RS on the cocell is monitored at least in part based on the at least one per-carrier RS ​​configuration indicated by the dynamic signal transmission.

2. The method according to claim 1, wherein the temporary RS includes at least one of a CSI-RS or a tracking RS (TRS).

3. The method according to claim 1, wherein the dynamic signal transmission includes initiating a Media Access Control (MAC) element (CE) of the co-cell.

4. According to the method of request item 3, wherein the dynamic signal transmission also includes downlink control information (DCI) indicating at least one trigger state.

5. According to the method of request item 3, wherein the MAC CE indicates at least one trigger state.

6. The method according to claim 3, wherein the MAC CE includes a first-order block associated with the co-cell.

7. The method according to request item 6, wherein the first bit block identifier indicates the at least one per-carrier RS ​​configuration of the temporary RS.

8. According to the method of request item 6, wherein: The MAC CE includes a second bit block associated with another co-cell; and a zero value in the second bit block indicates that a temporary RS is not used for the other co-cell.

9. According to the method of request item 3, wherein: The MAC CE initiates multiple co-cells; and the MAC CE includes multiple bit blocks, wherein each of the bit blocks is associated with a different co-cell among the multiple co-cells initiated by the MAC CE.

10. A method for wireless communication by a network entity, comprising the steps of: transmitting a Radio Resource Control (RRC) signal transmission that configures a User Equipment (UE) to have one or more per-carrier Reference Signal (RS) configurations; and transmitting a dynamic signal transmission that initiates a secondary cell and indicates at least one per-carrier RS ​​configuration among the one or more per-carrier RS ​​configurations for the transmission of a temporary RS on the secondary cell, wherein the at least one per-carrier RS ​​configuration is associated with at least one trigger state of a per-carrier aperiodic trigger state list associated with the secondary cell; and the at least one per-carrier RS ​​configuration includes an RS configuration associated with a CSI reporting configuration for a carrier of the per-carrier aperiodic trigger state list associated with the secondary cell.

11. The method according to claim 10, wherein the temporary RS includes at least one of a CSI-RS or a tracking RS (TRS).

12. The method of claim 10, wherein the dynamic signal transmission includes initiating a media access control (MAC) control element (CE) of the co-cell.

13. The method according to request item 12, wherein the dynamic signal transmission also includes downlink control information (DCI) indicating at least one trigger state.

14. The method of request item 12, wherein the MAC CE indicates at least one trigger state.

15. According to the method of request item 14, wherein: The MAC CE includes multiple bit blocks, each including a first bit block associated with the co-cell; and each different bit block of the multiple bit blocks is associated with a different co-cell.

16. The method according to request item 15, wherein the first bit block identifier indicates the at least one per-carrier RS ​​configuration of the temporary RS.

17. According to the method of request item 14, wherein: The MAC CE includes a second bit block associated with another co-cell; and a zero value in the second bit block indicates that a temporary RS is not used for the other co-cell.

18. According to the method of request item 12, wherein: The MAC CE initiates multiple co-cells; and the MAC CE includes multiple bit blocks, wherein each of the bit blocks is associated with a different co-cell among the multiple co-cells initiated by the MAC CE.

19. An apparatus for wireless communication, comprising: At least one processor; and a memory coupled to the at least one processor, the memory including code executable by the at least one processor to cause the device to: receive a Radio Resource Control (RRC) signal transmission that configures a User Equipment (UE) to have one or more per-carrier Reference Signal (RS) configurations; receive a dynamic signal transmission that initiates a co-cell and indicates at least one of the one or more per-carrier RS ​​configurations, wherein: the at least one per-carrier RS ​​configuration is associated with at least one trigger state of a per-carrier aperiodic trigger state list associated with the co-cell; and the at least one per-carrier RS ​​configuration includes an RS configuration associated with a CSI reporting configuration for a carrier of the per-carrier aperiodic trigger state list associated with the co-cell; and monitor a temporary RS on the co-cell based at least in part on the at least one per-carrier RS ​​configuration indicated by the dynamic signal transmission.

20. The apparatus according to claim 19, wherein the dynamic signal transmission includes a media access control (MAC) control element (CE) that initiates the co-cell.

21. The apparatus according to claim 20, wherein the MAC CE includes a first-order block associated with the co-cell.

22. The apparatus according to claim 21, wherein the first bit block identifier indicates the at least one per-carrier RS ​​configuration of the temporary RS.

23. The apparatus according to claim 21, wherein: The MAC CE includes a second bit block associated with another co-cell; and a zero value in the second bit block indicates that a temporary RS is not used for the other co-cell.

24. An apparatus for wireless communication, comprising: At least one processor; and a memory coupled to the at least one processor, the memory including code executable by the at least one processor to cause the device to: transmit a Radio Resource Control (RRC) signal transmission that configures a User Equipment (UE) to have one or more per-carrier Reference Signal (RS) configurations; and transmit a dynamic signal transmission that initiates a co-cell and indicates at least one per-carrier RS ​​configuration in the one or more per-carrier RS ​​configurations for the transmission of a temporary RS on the co-cell, wherein: the at least one per-carrier RS ​​configuration is associated with at least one trigger state in a per-carrier aperiodic trigger state list associated with the co-cell; and the at least one per-carrier RS ​​configuration includes an RS configuration associated with a CSI reporting configuration for a carrier in the per-carrier aperiodic trigger state list associated with the co-cell.

25. The apparatus according to claim 24, wherein the dynamic signal transmission includes a media access control (MAC) control element (CE) that initiates the co-cell.

26. The apparatus according to claim 25, wherein: The MAC CE includes multiple bit blocks, each including a first bit block associated with the co-cell; and each different bit block of the multiple bit blocks is associated with a different co-cell.

27. The apparatus according to claim 26, wherein the first bit block identifier indicates the at least one per-carrier RS ​​configuration of the temporary RS.

28. The apparatus according to claim 26, wherein: The MAC CE includes a second bit block associated with another co-cell; and a zero value in the second bit block indicates that a temporary RS is not used for the other co-cell.

Images