Apparatuses for measurement reporting via channel state information activation or deactivation

Abstract

Systems, methods, apparatus, and computer programs supporting periodic and SP reports on PUCCH. One method may include a UE receiving at least one LTM CSI report configuration from a network entity via radio resource configuration; receiving from the network entity at least one control message configured to enable or disable at least one of the at least one LTM CSI report configuration; and transmitting an L1 measurement report to the network entity based on at least one of the at least one control message.

Description

Technical Field

[0001] In 3GPP, Layer 1 (L1) / Layer 2 (L2) Triggered Mobility (LTM) is a cell switching procedure where the serving cell (e.g., primary cell (PCell) or primary secondary cell (PSCell)) of a UE can be switched by the network by sending an LTM cell switching command. The LTM switch command can be delivered by Media Access Control (MAC) signaling using MAC Control Elements (CE). Thus, it is now possible to change between cells without using Radio Resource Control (RRC) signaling as an L3 based handover. The LTM cell switching decision can be based on measurements (e.g., L1 measurements) that can be performed and reported (e.g., L1 measurement reports) by the UE. The measurements and reports can be based on LTM candidate cell configurations provided by the network for one or more LTM candidate cells. The LTM candidate cells can include neighboring cells and / or any current serving cell (e.g., SCell) of the UE. Improvements in LTM procedures and techniques are desired. Prior Art

[0002] Examples of mobile or wireless telecommunications systems may include radio frequency (RF) 5G RAT, Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), LTE Evolved UTRAN (E-UTRAN), LTE Advanced (LTE-A), LTE-A Pro, NR access technology, and / or MulteFire Alliance. 5G wireless system refers to the next generation (NG) radio system and network architecture. A 5G system is usually built on a 5G NR, but a 5G (or NG) network can also be built on E-UTRA radio. NR is expected to support service classes such as enhanced mobile broadband (eMBB), ultra-reliable low latency communications (URLLC), and massive machine type communications (mMTC). NR is expected to provide extremely high bandwidth, ultra-robust, low latency connectivity, and massive network connections to support the Internet of Things (IoT). Next Generation Radio Access Network (NG-RAN) represents the radio access network (RAN) for 5G, which can provide radio access for NR, LTE, and LTE-A. Note that in 5G, a node that provides radio access functions to a user equipment (e.g., similar to a Node B in UTRAN, an evolved Node B (eNB) in LTE) may be referred to as a next-generation Node B (gNB) when built on an NR radio, and may be referred to as a next-generation eNB (NG-eNB) when built on an E-UTRA radio. Summary of the invention

[0003] According to some exemplary embodiments, a method may include receiving, by a user equipment, at least one LTM CSI reporting configuration from a network entity via RRC. The method may further include receiving, by the user equipment, at least one control message configured to enable or disable at least one of the at least one LTM CSI reporting configuration from the network entity. The method may further include transmitting, by the user equipment, an L1 measurement report to the network entity based on at least one of the at least one control message.

[0004] According to certain exemplary embodiments, an apparatus may include means for receiving at least one LTM CSI reporting configuration from a network entity via RRC. The apparatus may further include means for receiving at least one control message configured to enable or disable at least one of the at least one LTM CSI reporting configuration from the network entity. The apparatus may further include means for transmitting an L1 measurement report to the network entity based on at least one of the at least one control message.

[0005] According to various exemplary embodiments, a non-transitory computer-readable medium may include program instructions that, when executed by a device, cause the device to at least perform a method. The method may include receiving at least one LTM CSI reporting configuration from a network entity via RRC. The method may further include receiving at least one control message configured to enable or disable at least one of the at least one LTM CSI reporting configuration from the network entity. The method may further include transmitting an L1 measurement report to the network entity based on at least one of the at least one control message.

[0006] According to some exemplary embodiments, a computer program product may perform a method. The method may include receiving at least one LTM CSI reporting configuration from a network entity via RRC. The method may further include receiving at least one control message configured to enable or disable at least one of the at least one LTM CSI reporting configuration from the network entity. The method may further include transmitting an L1 measurement report to the network entity based on at least one of the at least one control message.

[0007] According to certain exemplary embodiments, a device may include at least one processor and at least one memory storing instructions, wherein the instructions, when executed by the at least one processor, cause the device to at least receive at least one LTM CSI reporting configuration via RRC from a network entity. The at least one memory and the instructions, when executed by the at least one processor, may further cause the device to at least receive at least one control message configured to enable or disable at least one of the at least one LTM CSI reporting configurations from the network entity. The at least one memory and the instructions, when executed by the at least one processor, may further cause the device to at least transmit an L1 measurement report to the network entity based on at least one of the at least one control message.

[0008] According to various exemplary embodiments, an apparatus may include receiving circuitry configured to receive at least one LTM CSI reporting configuration from a network entity via RRC. The apparatus may further include receiving circuitry configured to receive at least one control message configured to enable or disable at least one of the at least one LTM CSI reporting configuration from the network entity. The apparatus may further include transmitting circuitry configured to transmit an L1 measurement report to the network entity based on at least one of the at least one control message.

[0009] According to some exemplary embodiments, a method may include transmitting, by a network entity, at least one LTM CSI reporting configuration via RRC to a user equipment. The method may further include transmitting, by the network entity, at least one control message configured to enable or disable at least one of the at least one LTM CSI reporting configuration to the user equipment. The method may further include receiving, by the network entity, an L1 measurement report from the user equipment based on at least one of the at least one control message.

[0010] According to certain exemplary embodiments, an apparatus may include means for transmitting at least one LTM CSI reporting configuration via RRC to a user equipment. The apparatus may further include means for transmitting at least one control message configured to enable or disable at least one of the at least one LTM CSI reporting configuration to the user equipment. The apparatus may further include means for receiving an L1 measurement report from the user equipment based on at least one of the at least one control message.

[0011] According to various exemplary embodiments, a non-transitory computer-readable medium may include program instructions that, when executed by a device, cause the device to at least perform a method. The method may include transmitting at least one LTM CSI reporting configuration via RRC to a user equipment. The method may further include transmitting at least one control message configured to enable or disable at least one of the at least one LTM CSI reporting configuration to the user equipment. The method may further include receiving an L1 measurement report from the user equipment based on at least one of the at least one control message.

[0012] According to some exemplary embodiments, a computer program product may perform a method. The method may include transmitting at least one LTM CSI reporting configuration via RRC to a user equipment. The method may further include transmitting at least one control message configured to enable or disable at least one of the at least one LTM CSI reporting configuration to the user equipment. The method may further include receiving an L1 measurement report from the user equipment based on at least one of the at least one control message.

[0013] According to certain exemplary embodiments, an apparatus may include at least one processor and at least one memory storing instructions, the instructions, when executed by the at least one processor, causing the apparatus to at least transmit at least one LTM CSI reporting configuration via RRC to a user equipment. The at least one memory and the instructions, when executed by the at least one processor, may further cause the apparatus to at least transmit at least one control message configured to enable or disable at least one of the at least one LTM CSI reporting configuration to the user equipment. The at least one memory and the instructions, when executed by the at least one processor, may further cause the apparatus to at least receive an L1 measurement report from the user equipment according to at least one of the at least one control message.

[0014] According to various exemplary embodiments, an apparatus may include a transmitting circuit system configured to transmit at least one LTM CSI reporting configuration via RRC to a user equipment. The apparatus may further include a transmitting circuit system configured to transmit at least one control message configured to enable or disable at least one of the at least one LTM CSI reporting configuration to the user equipment. The apparatus may further include a receiving circuit system configured to receive an L1 measurement report from the user equipment based on at least one of the at least one control message. Simple diagram description

[0015] For a proper understanding of one of the illustrative embodiments, reference should be made to the accompanying drawings, in which:

[0016] Figure 1 illustrates an example of a signaling diagram;

[0017] Figure 2 illustrates an example of an SP report on a PUCCH enable / disable MAC CE;

[0018] Figure 3 is an example of an SP CSI report on the PUCCH illustrating an example of enabling / disabling a MAC CE command;

[0019] Figure 4 illustrates an example of enabling / disabling a MAC CE command for an SP LTM CSI report on a PUCCH by means of a bit for a two-state toggle SpCellInclusion;

[0020] FIG5 illustrates an example of a signaling diagram according to certain exemplary embodiments;

[0021] 6A to 6B illustrate an example of another signaling diagram according to some exemplary embodiments;

[0022] FIG7 illustrates an example of another signaling diagram according to various exemplary embodiments;

[0023] FIG8 illustrates an example of a flow chart of a method according to various exemplary embodiments;

[0024] FIG9 illustrates an example of a flow chart of a method according to certain exemplary embodiments;

[0025] FIG. 10 illustrates an example of various network devices according to some exemplary embodiments; and

[0026] FIG. 11 illustrates an example of a 5G network and system architecture according to certain exemplary embodiments. Implementation

[0027] It will be readily understood that the components of certain exemplary embodiments, as generally described and illustrated in the figures herein, may be arranged and designed in a variety of different configurations. Therefore, the following detailed description of some exemplary embodiments of systems, methods, apparatuses, and computer program products for providing support for aperiodic, periodic, and SP reporting on PUCCH / PUSCH or using a MAC CE is not intended to limit the scope of certain exemplary embodiments, but rather is representative of selected exemplary embodiments.

[0028] In 3GPP, LTM is a cell switching procedure where the serving cell of a UE (e.g., a PCell or a PSCell) can be switched by the network by sending an LTM cell switching command. An LTM switch command can be delivered by MAC signaling using a MAC CE. Thus, it is now possible to change between cells without using RRC signaling as an L3 based handover. LTM cell switching decisions can be based on measurements (e.g., L1 measurements) that can be performed and reported by the UE (e.g., L1 measurement reports). The measurements and reports can be based on LTM candidate cell configurations provided by the network for one or more LTM candidate cells. LTM candidate cells can include neighboring cells and / or any current serving cell (e.g., SCell) of the UE.

[0029] Before a nest switch, a network may optionally enable one or more transmission configuration indicator (TCI) states for one or more candidate nests. Once a candidate nest TCI state is enabled, the UE may track the timing of enabled TCI states. The UE may also perform early uplink (UL) synchronization before a nest switch (if requested by the network).

[0030] FIG1 illustrates an exemplary LTM procedure. In step 1, the UE may send a MeasurementReport message to the gNB (i.e., base station). The gNB may determine to configure LTM and initiate candidate nest preparation. In step 2, the gNB may send an RRCReconfiguration message to the UE, which includes an LTM candidate nest configuration of at least one candidate nest. In step 3, the UE may store the LTM candidate nest configuration and send an RRCReconfigurationComplete message to the gNB.

[0031] In step 4a, the UE may perform DL synchronization with the candidate nest before receiving the nest switch command. In step 4b, the UE may perform early timing advance (TA) acquisition with the candidate nest requested by the network before receiving the nest switch command. For example, this may be performed via a contention-free random access (CFRA) triggered by a physical downlink control channel (PDCCH) command from the source nest. The UE may then transmit a preamble code toward the indicated candidate nest. In order to minimize data interruption of the source nest due to the CFRA toward the candidate nest, the UE may not receive a random access response (RAR) for the purpose of TA value acquisition. The TA value of the candidate nest may be indicated in the nest switch command. The UE may not maintain a TA timer for the candidate nest and may instead rely on the network implementation to ensure TA validity.

[0032] In step 5, the UE may perform L1 measurements on the configured candidate cell and may transmit a lower layer measurement report to the gNB. Measurements such as L1 measurements may be performed according to the RRC reconfiguration of step 2. In step 6, the gNB may determine to perform a cell handover to a target cell and may transmit a MAC CE triggering a cell handover by including a candidate configuration index of the target cell. The UE may switch to the target cell and apply the configuration indicated by the candidate configuration index.

[0033] In step 7, if the UE does not have a valid TA for the target cell, the UE may perform a random access procedure toward the target cell.

[0034] In step 8, the UE may complete the LTM nest switching procedure (e.g., by sending an RRCReconfigurationComplete message to the target nest). If the UE has performed an RA procedure in step 7, the UE may consider the LTM execution to be successfully completed when the random access procedure is successfully completed. For LTM without a random access channel (RACH), the UE may consider the LTM execution to be successfully completed when the UE determines that the network has successfully received its first UL data. The UE may determine the successful reception of its first UL data by receiving a PDCCH addressing the nested radio network temporary identifier (C-RNTI) of the UE in the target nest, which may schedule a new transmission after the first UL data. It should be noted that steps 4 to 8 may be performed multiple times for subsequent LTM nest switching using the LTM candidate nest configuration provided in step 2.

[0035] In LTM, the UE can perform a MAC reset. Using RRC signaling, the network can control whether the UE performs radio link control (RLC) re-establishment and packet data convergence protocol (PDCP) data recovery during nested handover. The PDCP data recovery procedure can be applied to RLC acknowledged mode (AM) data radio bearer (DRB) for LTM nested handover between distributed units (DUs).

[0036] For LTM, information about measurement resources (e.g., synchronization signal blocks (SSBs) or CSI-RS) from the LTM candidate nest may be provided to the UE so that the UE can perform measurements. The UE may also be configured with an L1 measurement reporting configuration, in which the UE can report measurements. For LTM, periodic and SP reporting on PUCCH, SP reporting on the physical uplink shared channel (PUSCH), and aperiodic reporting on PUSCH are supported.

[0037] Each reporting configuration (e.g. LTM-CSI-ReportConfig) may be associated with an LTM resource configuration for channel measurements and may contain parameters for time domain behavior provided by ltm-ReportConfigType (i.e. periodic, SP reporting on PUCCH, SP reporting on PUSCH, aperiodic reporting on PUSCH), the number of candidate cells and the number of reference signals per candidate cell provided by noOfReportedCells and noOfReportedRS-PerCell respectively, and if spCellInclusion is configured, the L1 measurement results associated with the current special cell (SpCell) are included.

[0038] The time domain behavior of LTM-CSI-ReportConfig may be indicated by the higher layer parameter ltm-ReportConfigType and may be set to "aperiodic", "semiPersistentOnPUCCH", "semiPersistentOnPUSCH", or "periodic". For "periodic" and "semiPersistentOnPUCCH" / "semiPersistentOnPUSCH" CSI reporting, the configured periodicity and time slot offset may be applied in the numerology of the UL bandwidth part (BWP) over which the CSI report is configured to be transmitted.

[0039] A set of LTM CSI reporting configurations containing one or more CSI reporting configurations (e.g., LTM-CSI-ReportConfigs) may be grouped separately from legacy CSI reporting configurations (i.e., for servo-nested beam management and CSI acquisition). Each of the CSI reporting configurations (i.e., LTM and legacy) may have its own identifier (ID) space (e.g., reporting configuration identity), running from 0 to a predetermined number. For example, a legacy CSI report may be referred to as a CSI report (servo-nested CSI report).

[0040] A UE may be configured with one or more CSI reporting configurations, wherein each reporting configuration may include an LTM CSI resource configuration containing information about resources to be used for channel measurements (e.g., L1 reference signal received power (RSRP) measurements). An LTM resource configuration may contain SSBs from one or more candidate nests. For each reporting configuration, the UE may be configured to report M beams from each of the L configured candidate nests (i.e., each LTM CSI resource setting (LTM-CSI-ResourceConfig) may contain a configuration of an LTM-CSI-SSB-ResourceSet, which includes a list of Z ≥ 1 synchronization signal (SS) / physical broadcast channel (PBCH) block indices (given by ltm-CSI-SSB-ResourceList) and a list of Z LTM-CandidateIds (given by ltm-CandidateIDList), which means the candidate nests associated with the SS / PBCH block indices). For each candidate cell, the UE can determine the time domain behavior of an SS / PBCH block resource from ssb-Periodicity and ssb-PositionsInBurst. The frequency domain behavior of an SS / PBCH block resource can be determined by higher layer parameters subCarrierSpacing and ssbFrequency.

[0041] If a UE group is configured with an LTM-CSI-ReportConfig, and if the UE group is configured with spCellInclusion, the UE may report different SSBRIs for the current SpCell and each of the noOfReportedCells-1 candidate nests in a single reporting entity noOfReportedRS-PerCell. Otherwise, the UE may report different SS / PBCH block resource indicators (SSBRIs) for each of the noOfReportedCell candidate nests in a single reporting entity noOfReportedRS-PerCell, where SSBRI k (k ≥ 0) corresponds to the (k+1)th entry of the associated ltm-CSI-SSB-ResourceList configured in the corresponding LTM-CSI-SSB-ResourceSet.

[0042] If spCellInclusion is assembled, the SSB resources associated with the current SpCell in the ltm-CSI-SSB-ResourceList can be a table entry in which the physical cell identity (PCI) and frequency information (for example, given by the SSB frequency) of the associated candidate cell (given in the ltm-CandidateIdList) are equal to the PCI and frequency information (given by the SSB frequency) of the current SpCell.

[0043] For gNB scheduled L1 measurement reporting for Rel-18, LTM can support reporting as UCI; similarly, SP reporting can be supported on PUSCH, and aperiodic reporting can be supported on PUSCH. Reports for serving cells and candidate cells for intra-frequency and / or inter-frequency can be included in a single reporting entity.

[0044] For beam selection for SSB based L1-RSRP measurement reporting, beam selection may be performed across L nests from the configured (or enabled if introduced) nests (i.e., M beams for each of the L nests). M x L ​​beams may be reported in a single reporting instance. The maximum value of M and L may be based on UE capabilities, and at least M × L = 4 as UE capabilities may be supported. The values ​​of M and L may be configurable among the UEs in the reporting configuration. Additionally, periodic and SP reporting on PUCCH may be supported for scheduled L1 measurement reporting for gNBs. For beam selection for SSB based L1-RSRP measurement reporting, currently the inclusion of SpCell in the L1 measurement report may be configurable.

[0045] For beam selection for SSB-based L1-RSRP measurement reporting, for the values ​​of M and L, the RRC-configured candidate values ​​may be M = 1, 2, 3, 4, and L = 1, 2, 3, 4. The UE capability may determine the maximum value of M*L and the combination of M and L.

[0046] Absolute and differential values ​​are available for L1-RSRP reporting. For absolute L1-RSRP, the L1-RSRP value can be quantized to a 7-bit value in the range [-140, -44] dBm with 1 dB steps. For differential L1-RSRP, the L1-RSRP value can be quantized to a 4-bit value, where the differential L1-RSRP value can be calculated from a reference L1-RSRP value with 2 dB steps.

[0047] Each L1-RSRP report may include the SSBRI in the grouped candidate nest. The bit size of the SSBRI may be ,in The number of SSBs allocated in the corresponding resource set is reported. The following formats can be used for reporting: [CSI] [Report Number] [CSI] [Field] CSI Report #n SSBRI #1 (if reported) SSBRI #2 (if reported) : SSBRI #L*M (if reported) RSRP #1 (if reported) Differential RSRP #2 (if reported) : Differential RSRP #L*M (if reported)

[0048] The Information Element (IE) LTM-CSI-ReportConfig may be used to configure the reports on the cells in which the LTM-CSI-ReportConfig is to be included. IE LTM-CSI-ReportConfig can be configured as follows: -- ASN1START -- TAG-LTM-CSI-REPORTCONFIG-START LTM-CSI-ReportConfig-r18 ::= SEQUENCE { ltm-CSI-ReportConfigId-r18 LTM-CSI-ReportConfigId-r18 ltm-ResourcesForChannelMeasurement-r18 LTM-CSI-ResourceConfigId-r18 ltm-ReportConfigType-r18 CHOICE { periodic-r18 SEQUENCE { reportSlotConfig-r18 CSI-ReportPeriodicityAndOffset, pucch-CSI-ResourceList-r18 SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-Resource}, semiPersistentOnPUCCH-r18 SEQUENCE { reportSlotConfig-r18 CSI-ReportPeriodicityAndOffset, pucch-CSI-ResourceList-r18 SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-Resource},}, ltm-ReportContent-r18 LTM-ReportContent-r18 ...} LTM-ReportContent-r18 ::= SEQUENCE { noOfReportedCells-r18 ENUMERATED {n1,n2,n3,n4} noOfReportedRS-PerCell-r18 ENUMERATED {n1,n2,n3,n4} spCellInclusion-r18 ENUMERATED {true} OPTIONAL, -- Need R} -- TAG-LTM-CSI-REPORTCONFIG-STOP -- ASN1STOP .

[0049] LTM-CSI-ReportConfig may also include the following field descriptions: LTM-CSI-ReportConfig Field Descriptions [ , ltm-CSI-ReportConfigId , ]This field is used to identify an LTM-CSI-ReportConfig. [ , ltm-ReportContent , ] This field defines the content of the LTM L1 measurement report. [ , ltm-ResourcesForChannelMeasurement , ]This field indicates the resource used for LTM L1 measurement. [ , pucch-CSI-ResourceList , ] indicates which PUCCH resource is to be used for reporting on PUCCH. [ , reportConfigType , ] This field describes how to report the time domain behavior of the L1 measurement. [ , reportSlotConfig , ] Periodicity and time slot offset (see TS 38.214

[19] , clause 5.2.1.4). LTM-ReportContent field description [ , noOfReportedCells , ] This field defines how many nests are reported within a single L1 measurement reporting instance. [ , noOfReportedRS-PerCell , ]This field defines how many RS are reported per cell within a single L1 measurement reporting instance. [ , spCellInclusion , ] This field indicates whether the UE should include an L1 measurement report associated with the current SpCell. This field is only configured if the current SpCell is configured as a LTM candidate cell.

[0050] The IE LTM-CSI-ResourceConfig may define a group of one or more CSI resources for an LTM candidate nest configuration. IE LTM-CSI-ResourceConfig can be configured as follows: -- ASN1START -- TAG-LTM-CSI-RESOURCECONFIG-START LTM-CSI-ResourceConfig-r18 ::= SEQUENCE { ltm-CSI-ResourceConfigId-r18 LTM-CSI-ResourceConfigId-r18, ltm-CSI-SSB-ResourceSet-r18 LTM-CSI-SSB-ResourceSet-r18, ...} LTM-CSI-SSB-ResourceSet-r18 ::= SEQUENCE { ltm-CSI-SSB-ResourceSetId-r18 LTM-CSI-SSB-ResourceSetId-r18, ltm-CSI-SSB-ResourceList-r18 SEQUENCE (SIZE (1..maxNrofLtmCSI-SSB-ResourcesPerSet-r18)) OF SSB-Index, ltm-CandidateIdList-r18 SEQUENCE (SIZE (1..maxNrofLtmCSI-SSB-ResourcesPerSet-r18)) OF LTM-CandidateId-r18} -- TAG-LTM-CSI-RESOURCECONFIG-STOP -- ASN1STOP

[0051] IE LTM-CSI-ResourceConfig may also include the following fields: [ , LTM-CSI-ResourceConfig , ] [Field Description] [ , ltm-CSI-ResourceConfigId , ]This field is used to identify an instance of LTM-CSI-ResourceConfigIE. [ , ltm-CSI-SSB-ResourceSet , ]This field defines a SS / PBCH block resource set from one or more LTM candidate nests. [ , LTM-CSI-SSB-ResourceSet , ] [Field Description] [ , ltm-CandidateIdList , ] This field indicates the LTM candidate nest ID associated with the SSB in ltm-CSI-SSB-ResourceList. The list has the same number of entries as ltm-CSI-SSB-ResourceList. [ , ltm-CSI-SSB-ResourceList , ]This field is used to indicate SS / PBCH block resources from one or more LTM candidate nests. [ , ltm-CSI-SSB-ResourceSetId , ]This field is used to identify the SS / PBCH block resource set.

[0052] For SP reporting on PUCCH, the PUCCH resource used to transmit the CSI report can be configured by reportConfigType. SP reporting on PUCCH can be enabled by an activation command, which can select one of the SP reporting configurations for use by the UE on PUCCH. When the UE transmits a PUCCH with hybrid automatic repeat request (HARQ)-acknowledgement (ACK) information in the time slot n corresponding to the physical data shared channel (PDSCH) carrying the activation command, it can select the PUCCH resource used to transmit the CSI report in the time slot n corresponding to the physical data shared channel (PDSCH) carrying the activation command. The first time slot thereafter starts to apply the indicated SP reporting configuration, where µ is the subcarrier spacing (SCS) configuration used for PUCCH.

[0053] When a UE transmits a PUCCH with HARQ-ACK information in slot n corresponding to the PDSCH carrying the activation command, a UE may perform SP CSI reporting on the PUCCH applied starting from the first slot after slot 𝑛 + 3𝑁𝑠𝑙𝑜𝑡 𝑠𝑢𝑏𝑓𝑟𝑎𝑚𝑒,μ, where μ is the SCS configuration used for the PUCCH. The activation command shall contain one or more reporting configurations that are configured with the associated CSI resource configuration.

[0054] FIG. 2 illustrates an example of an SP CSI report on a PUCCH enable / disable MAC CE. The SP CSI report on the PUCCH enable / disable MAC CE may be identified by a MAC sub-header with a logical channel ID (LCID) value of 25. It may have a fixed size of 16 bits and include several fields, such as the servo nest ID: This field may indicate the identity of the servo nest to which the MAC CE applies; the length of the field may be 5 bits. The MAC sub-header may also include a BWP ID field, which indicates a UL BWP that the MAC CE applies as the code point of the DCI bandwidth part indicator field; the length of the BWP ID field may be 2 bits. The MAC sub-header may also include a Si field, which indicates the enable / disable status of the SP CSI report configuration in the csi-ReportConfigToAddModList. S 0 means the reporting configuration that may include PUCCH resources for SP CSI reporting in the indicated BWP and may have the lowest CSI-ReportConfigId in the list with type set to semiPersistentOnPUCCH, S 1 means the reporting configuration that may include PUCCH resources for SP CSI reporting in the indicated BWP and has the second lowest CSI-ReportConfigId, and so on. If the number of reporting configurations in the list with type set to semiPersistentOnPUCCH in the indicated BWP is less than i + 1, the MAC entity may ignore the S i field. The S i field may be set to 1 to indicate that the corresponding SP CSI reporting configuration may be enabled. The S i field may be set to 0 to indicate that the corresponding SP CSI reporting configuration i should be disabled. The MAC sub-header may also include a reserved bit R set to 0.

[0055] For LTM, a set of LTM CSI reporting configurations separate from the legacy CSI reporting configurations used for intra-cell / inter-cell beam management and servo-cell CSI acquisition (i.e., legacy CSI reporting for servo-cell in this document) may support Rel-18 LTM. LTM CSI reporting configurations and legacy CSI reporting configurations may have their own (i.e., independent) configuration identifier spaces to indicate the corresponding reporting configurations (i.e., LTM-CSI-ReportConfigId for uniquely representing an LTM CSI reporting configuration has a value from 0 to a maximum value (M1 = maximum number of LTM CSI reporting configurations), and CSI-ReportConfigId for uniquely representing a legacy CSI reporting configuration has a value from 0 to a maximum value (M2 = maximum number of CSI reporting configurations).

[0056] LTM and servo-nested (e.g., legacy or beam-managed) CSI reporting may support semi-permanent reporting on PUCCH. For servo-nested semi-permanent reporting on PUCCH, a MAC-CE may enable / disable semi-permanent reporting on PUCCH by indicating one or more CSI reporting configuration IDs to be enabled and / or disabled. The UE may not be able to determine whether a given MAC-CE is a servo-nested (i.e., legacy) CSI reporting or for LTM CSI reporting if the same MAC-CE command is for LTM semi-permanent reporting on PUCCH. In various embodiments, legacy CSI reporting may refer to CSI reporting (e.g., servo-nested CSI reporting).

[0057] A reporting configuration for LTM reporting (e.g., including a configuration for SpCellInclusion indicating whether the current SpCell measurement is to be included in the report, and an associated resource configuration including resource signal information for one or more candidate cells to be considered for measurement and reporting) is provided in the RRC configuration. In addition, dynamically enabled / triggered LTM reports (SP reports on PUCCH (e.g., up to 4), SP reports on PUSCH, aperiodic reports) may have a limited number of RRC configured reporting configurations. As the UE moves, there may be a need to update the configuration of an RRC configured reporting configuration. With a limited number of RRC configured reporting configurations, any update may require an RRC reconfiguration, which is a slower process.

[0058] Certain exemplary embodiments described herein may have various benefits and / or advantages to overcome the above disadvantages. For example, certain exemplary embodiments may provide a solution for a UE to determine whether a given MAC-CE for SP CSI reporting on PUCCH (or PUSCH) activation / deactivation is for serving nested CSI reporting or for LTM CSI reporting. Similarly, some exemplary embodiments may dynamically update a reporting configuration for a CSI reporting configuration for LTM. Therefore, certain exemplary embodiments discussed below are directed to improvements in computer-related technologies.

[0059] Some exemplary embodiments may provide a signaling method for indicating to a UE whether the activation / deactivation of one or more SP reporting on a PUCCH configuration applies to an LTM reporting configuration or a servo cell reporting configuration (e.g., for legacy reporting of servo cell CSI). Some exemplary embodiments may also provide a signaling method for dynamically updating a reporting configuration for an LTM CSI report (i.e., for including the configuration of the current servo cell (e.g., SpCell) measurement in each report for one or more LTM CSI reporting configurations that are activated / triggered). In addition, various exemplary embodiments may provide a method for determining whether to report on one or more SP reporting configurations for legacy servo cell BM / CSI when one or more LTM SP reporting on a PUCCH is activated or disabled. In various exemplary embodiments, the CSI report may include reporting one or more of a channel quality indicator (CQI), a precoding matrix indicator (PMI), a CSI-RS resource indicator (CRI), a SS / PBCH block resource indicator (SSBRI), a layer indicator (LI), a rank indicator (RI), L1-RSRP, L1-SINR signal and interference plus noise ratio, or CapabilityIndex.

[0060] FIG5 illustrates an example of a signaling diagram 500 for enabling / disabling MAC CE by means of a server nest / LTM (S / L) field. According to certain exemplary embodiments, UE 510 may be similar to UE 1020, and source nest 520, CU 530, and target nest 540 may be similar to NE 1010, as shown in FIG10. S / L or the S / L field may mean server nest CSI report / LTM CSI report.

[0061] In operation 501, CU 530 may send an RRC reconfiguration message to UE 510.

[0062] In operation 502, UE 510 may send an RRC reconfiguration complete message to CU 530.

[0063] At operation 503, the source nest 520 may send a MAC CE SP to the UE 510 on PUCCH activation of one or more reporting configurations S 0 ... Si, wherein an S / L field may be set to indicate a value of LTM. Alternatively, the S / L field (or a field in a downlink control message such as MAC CE) may be set to indicate a value of the serving nest CSI report.

[0064] In various exemplary embodiments, SP reporting, PUCCH and / or PUSCH CSI reporting may be used (ie, PUCCH and PUSCH may be used interchangeably). Alternatively, SP reporting may be used for MAC CE CSI reporting.

[0065] In any example herein, CSI reporting herein may refer to any time type, such as semi-permanent, periodic, or aperiodic.

[0066] In certain exemplary embodiments, signaling of SP reporting on PUCCH for LTM (i.e., activation and / or deactivation of reporting configurations) may be conveyed in a MAC CE, wherein a field in a MAC CE indicates whether activation / deactivation of one or more SP reporting configurations applies to LTM reporting configurations or servo-nested reporting configurations (e.g., legacy reporting for servo-nested beam management (BM) and CSI). For example, an identifier may be used to uniquely identify the activation / deactivation MAC-CE command for SP LTM CSI reporting on PUCCH. A unique logical channel ID (LCID) and / or a unique extended LCID (eLCID) may be used in the MAC sub-header to uniquely indicate that this MAC CE is for activation / deactivation of SP LTM CSI reporting on PUCCH. For example, an LCID value different from the LCID used for legacy SP CSI reporting on PUCCH may indicate that this MAC CE is for LTM CSI reporting. Therefore, the UE may read the (e)LCID field of the MAC CE to determine whether the activation or deactivation of the reporting configuration (or any other information provided by the MAC CE) is for serving nested CSI reporting or for LTM CSI reporting.

[0067] Alternatively, a field in a downlink control message (e.g., DCI / MAC CE), such as the bit field shown in FIG. 3 , may be used (e.g., S / L) to distinguish whether the MAC CE is for legacy SP CSI reporting or for LTM SP CSI reporting. If the field indicates S (or indicates a first value or indicates a value for serving cell beam management), enablement / disablement may be used for serving cell beam management (e.g., for intra-cell / inter-cell beam management or / and CSI acquisition). Alternatively, if the field indicates L (or indicates a second value or indicates a value for LTM), enablement / disablement may be used for LTM CSI reporting. S may be represented by 0 (e.g., the first value), and L may be represented by “1” (e.g., the second value), and vice versa. A field in a downlink control message (eg, DCI or MAC CE message) may include a field indicating whether the information provided by the control message (eg, DCI or MAC CE) is for legacy CSI reporting or LTM CSI reporting.

[0068] At operation 504, the UE 510 may determine the S / L field value indicating the LTM, and may apply the reporting configuration to one or more reporting configurations S 0 . . . S i.

[0069] In certain exemplary embodiments, when the UE 510 determines that a given MAC-CE is an enable / disable MAC-CE command for (SP) LTM CSI reporting on PUCCH, the UE 510 may determine that the Si field indicates the enable / disable state of the SP CSI reporting configuration in the RRC configured reporting configuration list (e.g., ltm-csi-ReportConfigToAddModList) for LTM. S0 may mean a reporting configuration that may include PUCCH resources for SP CSI reporting in the specified BWP and may have the lowest reporting configuration identifier (LTM-CSI-ReportConfigId in the list with type set to semiPersistentOnPUCCH), S1 is set to a reporting configuration that includes PUCCH resources for SP CSI reporting in the specified BWP and has the second lowest reporting configuration identifier (LTM-CSI-ReportConfigId), and so on. If the number of reporting configurations in the list in the specified BWP (type set to semiPersistentOnPUCCH) is less than i + 1, the MAC entity may ignore the Si field. A Si field set to 1 may indicate that the corresponding SP CSI reporting configuration may be enabled. A Si field set to 0 may indicate that the corresponding SP CSI reporting configuration i may be disabled.

[0070] At operation 505, UE 510 may send (L1) measurement reports to source (serving) nest 520, which may be based on one or more report configurations S0...S1.

[0071] 6A-6B illustrate an example of a signaling diagram 600 for SP nest inclusion (activation / deactivation MAC CE with SP). According to some exemplary embodiments, UE 610 may be similar to UE 1020, and source nest 620, CU 630, and target nest 640 may be similar to NE 1010, as shown in FIG. 10.

[0072] In operation 601, CU 630 may send an RRC reconfiguration message to UE 610.

[0073] In operation 602, UE 610 may send an RRC reconfiguration complete message to CU 630.

[0074] Some exemplary embodiments may include signaling configured to control the inclusion of SpCell measurements in the one or more reporting configurations and / or the reporting of SpCell measurements. In some exemplary embodiments, the signaling (i.e., control message) for enabling / disabling, triggering, and / or updating LTM CSI reporting may further include an indication configured to (dynamically) control / change the reporting configuration (i.e., control / change the reported information) for the enabled / triggered reporting. In some exemplary embodiments, this indication may indicate whether to include SpCell measurements for one or more enabled CSI reporting configurations. In various exemplary embodiments, the inclusion of SpCell measurements or SpCell information in the reporting configuration or the control of the inclusion may be indicated by a field in a downlink control message. For example, this field may be present in a MAC CE or in a DCI message. For example, at operation 603, the source nest 620 may transmit a MAC CE for SP to the UE 610 on PUCCH activation for reporting configurations. For example, S 0 may relate to a first LTM reporting configuration and S 1 may relate to a second LTM reporting configuration. A SP field may be set to a value indicating SpCellInclusion. At operation 604, the UE 610 may determine a SP field value indicating SpCellInclusion and may apply reporting configuration S 0 including SpCell measurements. Alternatively, the UE 610 may apply reporting configuration S 0 without SpCell measurements (for example, if an SP field is included). At operation 605, the UE 610 may transmit L1 measurement reports to the source nest 620 according to reporting configurations S 1 and S 2, including SpCell measurements for S 0. For example, a field (eg, an SP field or any field providing functionality) may be present in a downlink control message that changes the RRC configured value or the interpretation of the RRC configured value of at least one parameter related to the inclusion of SpCell in the reporting configuration.

[0075] In various exemplary embodiments, for SP LTM CSI reporting on PUCCH, MAC CE signaling of SP LTM CSI reporting on PUCCH (i.e., SP LTM CSI reporting on PUCCH enable / disable MAC CE) can be used to update the reporting configuration of the enabled SP LTM CSI reporting configuration(s). For example, a field in a MAC CE can be used to update the SpCellInclusion (i.e., SpCell inclusion) configuration of one or more enabled SP reporting configurations, such as the SP field shown in FIG. 4 . In some exemplary embodiments, the SP field (or any field that controls the inclusion of SpCell measurements in one or more reporting configurations) can be referred to as a field of configured inclusion. The field of configured inclusion can be a field that controls the inclusion of SpCell reporting by enabling one or more reporting configurations through the same message that includes the field of configured inclusion. In the RRC configuration, a configuration of SP reporting can be configured with SpCellInclusion. The UE may be expected to report current SpCell measurements in each report associated with the reporting configuration; however, the MAC CE activation associated with the SP reporting may change (e.g., remove or cause the UE to not apply the configuration) the SpCellInclusion. Therefore, the UE 610 may not be expected to report current SpCell measurements in each report associated with the reporting configuration (for which SpCell inclusion is configured to be disabled or not "established"). In an RRC message, the field that configures inclusions may configure the inclusion of SpCell measurements for one or more (or a specific) reporting configuration.

[0076] As shown in FIG. 4 , a field (e.g., a single-bit field) in a MAC CE may be used to toggle the configuration of SpCellInclusion. If the value of the field (i.e., the SP field) is set to a first value (e.g., “1”), the RRC configuration of SpCellInclusion may be toggled between configured and unconfigured. Otherwise, if the value of the field (i.e., the SP field) is set to a second value (e.g., “0”), the RRC configuration of SpCellInclusion may remain the same.

[0077] In some exemplary embodiments, with more than one SP reporting configuration enabled, a field may be interpreted as a common configuration for updating the SpCellInclusion configuration for multiple reporting configurations (e.g., which are enabled). In some exemplary embodiments, a separate field (i.e., bit) may be used for each reporting configuration to independently update the SpCellInclusion configuration. In some exemplary embodiments, there may be at least one field (e.g., Si field) that controls the SpCell inclusion associated with each reporting configuration enable / disable field.

[0078] In some exemplary embodiments, the MAC CE may include a field including a corresponding SP field associated with an enable / disable field (eg, fields S 0 ... S 1 as shown in FIG. 4 ). The indication provided by the SP field may configure the SpCell inclusion for the associated reporting configuration.

[0079] In some exemplary embodiments, the RRC configuration may indicate whether the SpCell inclusion may be changed via a (further) downlink control message (eg, MAC CE or DCI).

[0080] In some exemplary embodiments, a message providing control information (such as MAC or DCI) may control the inclusion of SpCell measurements for a measurement report. If a field is set to a first value (e.g., "0") or indicates that SpCell includes an unassigned value, the UE may not report SpCell measurements in the measurement report. If a field is set to a second value (e.g., "0") or indicates that SpCell includes an assigned value, the UE may report SpCell measurements in the measurement report.

[0081] According to various exemplary embodiments, if the SP field is set to a first value (e.g., "1"), all reporting configurations that are enabled and configured (e.g., configured by RRC) with SpCell inclusion may include SpCell measurements in reports. Alternatively, if the SP field is set to a second value (e.g., "0"), all reporting configurations that are enabled and configured with SpCell inclusion may not include SpCell measurements in reports. Furthermore, deactivation of a reporting configuration may reset any dynamically configured SpCell inclusion parameters.

[0082] In certain exemplary embodiments, for SP LTM CSI reporting on PUSCH, a DCI (e.g., an existing DCI format for scheduling uplink or downlink transmission, or a new CI format including one or more fields for enabling / disabling SP CSI reporting) that enables or disables an SP LTM CSI reporting on PUSCH may be used to update the reporting configuration of the enabled SP LTM CSI reporting configuration(s). For example, a field (e.g., a single-bit field) in the DCI may be used to toggle the RRC configuration of SpCellInclusion.

[0083] In some exemplary embodiments, for aperiodic CSI reporting on PUSCH, a DCI (e.g., a DCI format for enabling an aperiodic CSI reporting trigger state) that enables an aperiodic LTM CSI reporting on PUSCH may be used to update the reporting configuration of the enabled aperiodic LTM CSI reporting configuration(s). For example, a field (e.g., a single-bit field) in the DCI may be used to toggle / modify / change the RRC configuration of SpCellInclusion. The DCI format that provides resource configuration selection / update and / or reporting configuration update may or may not schedule any transmission.

[0084] Some exemplary embodiments may not include SpCell information to be reported. For example, at operation 606, the source nest 620 may transmit a MAC CE SP on PUCCH activation to the UE 610 for a reporting configuration, which may include S 0 for LTM reporting configuration 1 and S 1 for LTM reporting configuration 2. The SP field may be set to a value indicating no SpCell inclusion. At operation 607, the UE 610 may determine the SP field value to indicate no SpCell inclusion, and may apply reporting configurations S 0 and S 1 without including SpCell measurement. At operation 608, the UE 610 may transmit a measurement report to the source nest 620 (L1) according to reporting configurations S 1 and S 2, excluding SpCell measurement.

[0085] In some exemplary embodiments, a field for configuring inclusion (in a control message) may refer to control information included in a control message (provided by the network) that configures the inclusion of SpCell information in a measurement report for one or more reporting configurations (e.g., the inclusion of SpCell measurement results).

[0086] In various exemplary embodiments, the dependency between the servo nest SP reporting on PUCCH and the LTM SP reporting on PUCCH may be captured. Similarly, this dependency may apply to the servo nest (SP) reporting on PUSCH and the LTM (SP) reporting on PUSCH. For example, the activation of at least one SP LTM CSI reporting configuration on PUCCH, where the SP reporting configuration is associated with the reporting of the reference signal assembled for the LTM candidate nest measurement, may trigger the deactivation of at least one or all servo nest SP CSI reporting configurations for the servo nest (e.g., on the same BWP). Similarly, the deactivation of some or all SP LTM CSI reporting configurations on PUCCH (e.g., if at least one was activated), where the SP reporting configuration is associated with the reporting of the reference signal assembled for the LTM candidate nest measurement (i.e., the LTM SP reporting on PUCCH), may trigger the activation of at least one or all legacy SP reporting configurations that were previously assembled for the servo nest (e.g., on the same BWP).

[0087] 7 is an example of a signaling diagram 700 illustrating LTM / legacy dependencies. According to certain exemplary embodiments, UE 710 may be similar to UE 1020, and source nest 720, CU 730, and target nest 740 may be similar to NE 1010, as shown in FIG. 10 .

[0088] At operation 701, CU 730 may send an RRC reconfiguration message to UE 710, which may indicate LTM reporting configuration for SPs on PUCCH on LTM resource configuration and / or indicate servo cell reporting for SPs on PUCCH on a servo cell resource configuration.

[0089] In operation 702, UE 710 may send an RRC reconfiguration complete message to CU 730.

[0090] At operation 703, the source cell 720 may send a MAC CE SP to the UE 710 on a PUCCH activation reporting a configuration serving cell report.

[0091] At operation 704, the UE 710 may send an L1 measurement report to the source cell 720 according to the serving cell report.

[0092] At operation 705, the source cell 720 may send a MAC CE SP on a PUCCH activation of a reporting configuration for LTM reporting configuration 1 to the UE 710.

[0093] At operation 706, UE 710 may determine that SP on PUCCH is enabled for a reporting configuration on RS configured for LTM L1 measurement. For example, UE 710 may determine that service cell reporting configuration 1 is to be disabled / suspended.

[0094] In some exemplary embodiments, the activation of at least one SP reporting configuration on the PUCCH, where the SP reporting configuration is associated with reporting of a reference signal configured for LTM candidate nest measurements, may trigger the suspension of at least one or all serving nest SP CSI reporting configurations for the serving nest (e.g., on the same BWP). The suspension may cause the UE to maintain the previous activation, but to suspend reporting (and measurements associated with the reporting). Whether serving nest SP CSI reporting should be disabled / suspended may be configured by the network. In various exemplary embodiments, the dependency between LTM and serving nest CSI reporting may be configured by the network.

[0095] In various exemplary embodiments, if the activation of at least one SP LTM CSI reporting causes the UE 710 to activate more than a maximum number of SP reporting configurations (e.g., a maximum number of simultaneously active SP reporting configurations, or a maximum number of simultaneous CSI reports per BWP / CC), the UE 710 may determine to disable the servo nest SP reporting configurations on the PUCCH for the servo nest starting from the highest configuration ID until the maximum number is reached.

[0096] In certain exemplary embodiments, SP reporting enablement for LTM may cause the UE to disable serving-nested SP CSI reporting.

[0097] In certain exemplary embodiments, when signaling of SP reporting on PUCCH for LTM is conveyed in a MAC CE (i.e., a field or a header in a MAC CE / DCI indicates whether activation / deactivation of one or more SP reporting configurations applies to LTM configuration or servo nest configuration), in the case where activation indicates for LTM, UE 710 may interpret one or more fields associated with SP reporting on PUCCH configuration for LTM, and UE 710 may assume that the servo nest SP configuration is deactivated (until activated again) or suspended (until LTM SP reporting is deactivated). Otherwise, in the case where the field indicates the servo nest, UE 710 may assume the servo nest SP CSI reporting configuration is activated, indicated by one or more further fields, and deactivate all LTM SPs configured on PUCCH.

[0098] In operation 707, UE 710 may send an L1 measurement report to source cell 720 according to LTM report configuration 1.

[0099] FIG. 8 illustrates an example of a flow chart of a method 800 that may be performed by a UE, such as UE 1020 shown in FIG. 10 , according to various exemplary embodiments.

[0100] In step 801, the method may include receiving, by a user equipment, at least one LTM CSI reporting configuration from a network entity via RRC.

[0101] At step 802, the method may further include receiving, by the user equipment from the network entity, at least one control message configured to enable or disable at least one of the at least one LTM CSI reporting configurations.

[0102] In step 803, the method may further include transmitting, by the user equipment, a layer 1 measurement report to the network entity according to at least one of the at least one control message.

[0103] In some exemplary embodiments, the at least one LTM CSI report configuration may include at least one parameter, the at least one parameter configuring, in the L1 measurement report, inclusion of at least one measurement result in the L1 measurement report according to at least one of the at least one LTM CSI report configurations. In some exemplary embodiments, the at least one control message may include at least one field, the at least one field configuring inclusion of at least one measurement result in the L1 measurement report according to at least one of the at least one LTM CSI report configurations. The at least one included measurement result may include at least one first-level nested measurement.

[0104] In various exemplary embodiments, the at least one control message may include at least one indication of an LTM CSI reporting configuration identifier indicating whether to update at least one LTM CSI or at least one server nested CSI reporting configuration. The at least one indication may include at least one of a server nested / layer 1 or 2 triggered mobility field or a logical channel identifier.

[0105] In some exemplary embodiments, the at least one control message may include at least one of a media access control element or a downlink control information command.

[0106] In some exemplary embodiments, at least one control message is configured to disable the at least one LTM CSI reporting configuration, and the method may further include shelving, by the user equipment, at least one of the at least one server-nested CSI reporting configuration, or disabling, by the user equipment, at least one of the at least one server-nested CSI reporting configuration.

[0107] In various exemplary embodiments, the enabling of at least one LTM CSI reporting configuration further includes determining, by the user equipment, to continue or enable at least one previously suspended or disabled server nest CSI reporting configuration.

[0108] In certain exemplary embodiments, the user equipment may be configured for semi-permanent LTM CSI reporting on the PUCCH, and the LTM CSI reporting configuration identifier may be configured to update and enable the at least one LTM CSI reporting configuration.

[0109] In some exemplary embodiments, the user equipment is configured for SP LTM CSI reporting on PUSCH, and the LTM CSI reporting configuration identifier may be configured to update and enable the at least one LTM CSI reporting configuration.

[0110] In various exemplary embodiments, the method may further include receiving, by the user equipment, from the network entity via RRC, one or more LTM CSI reporting configurations including at least one parameter associated with inclusion of one or more measurement results in measurement reports of the one or more reporting configurations; determining, by the user equipment, based on the indication, to update information regarding the inclusion of the one or more measurement results; and updating, by the user equipment, at least one LTM CSI reporting configuration.

[0111] FIG. 9 illustrates an example of a flow chart of a method 900 that may be performed by a NE, such as the NE 1010 shown in FIG. 10 , according to various exemplary embodiments.

[0112] In step 901, the method may include transmitting, by a network entity, at least one LTM CSI reporting configuration via RRC to a user equipment.

[0113] At step 902, the method may further include transmitting, by the network entity to the user equipment, at least one control message configured to enable or disable at least one of the at least one LTM CSI reporting configurations.

[0114] In step 903, the method may further include receiving, by the network entity, a layer 1 measurement report from the user equipment according to at least one of the at least one control message.

[0115] In some exemplary embodiments, the at least one LTM CSI report configuration may include at least one parameter that configures inclusion of at least one measurement result in the L1 measurement report according to at least one of the at least one LTM CSI report configurations.

[0116] In some exemplary embodiments, the at least one control message includes at least one field that configures inclusion of at least one measurement result in the L1 measurement report according to at least one of the at least one LTM CSI report configurations.

[0117] In various exemplary embodiments, the at least one included nano-measurement comprises at least one first-level nested measurement.

[0118] In some exemplary embodiments, the at least one control message may include at least one indication of an LTM CSI reporting configuration identifier indicating whether to update at least one LTM CSI or at least one server nested CSI reporting configuration.

[0119] In some exemplary embodiments, the at least one indication may include at least one of a server nest / layer 1 or 2 triggered mobility field or a logical channel identifier.

[0120] In various exemplary embodiments, the at least one control message may include at least one of a MAC CE or a DCI command.

[0121] In certain exemplary embodiments, the user equipment may be configured for SP LTM CSI reporting on the PUCCH, and the LTM CSI reporting configuration identifier may be configured to update and enable the at least one LTM CSI reporting configuration.

[0122] In some exemplary embodiments, the user equipment is configured for SP LTM CSI reporting on PUSCH, and the LTM CSI reporting configuration identifier is configured to update and enable the at least one LTM CSI reporting configuration.

[0123] In various exemplary embodiments, the method may further include transmitting, by the network entity, to the user equipment via RRC, one or more LTM CSI reporting configurations including at least one parameter, the at least one parameter configuring inclusion of one or more measurement results in the measurement report of the one or more reporting configurations.

[0124] FIG10 illustrates an example of a system according to some exemplary embodiments. In an exemplary embodiment, a system may include multiple devices, such as NE 1010 and / or UE 1020.

[0125] NE 1010 may be a base station (e.g., 3G UMTS NodeB, 4G LTE evolved NodeB, or 5G NR next generation NodeB), a server gateway, a server, and / or any other access node or combination thereof.

[0126] The NE 1010 may further include at least one gNB centralized unit (CU), which may be associated with at least one gNB distributed unit (DU). The at least one gNB-CU and the at least one gNB-DU may communicate via at least one F1 interface, at least one XnC interface, and / or at least one NG interface of a 5th generation core (5GC).

[0127] UE 1020 may include one or more of a mobile device such as a cell phone, a smart phone, a personal digital assistant (PDA), a tablet, or a portable media player, a digital camera, a camcorder, a video game console, a navigation unit such as a global positioning system (GPS) device, a desktop or laptop computer, a single location device such as a sensor or a smart meter, or any combination thereof. Furthermore, NE 1010 and / or UE 1020 may be one or more of a citizen broadband radio service device (CBSD).

[0128] NE 1010 and / or UE 1020 may include at least one processor, respectively 1011 and 1021. Processors 1011 and 1021 may be implemented by any computing or data processing device, such as a central processing unit (CPU), an application specific integrated circuit (ASIC), or an equivalent device. The processors may be implemented as a single controller, or multiple controllers or processors.

[0129] At least one memory may be disposed in one or more of the devices, as indicated by 1012 and 1022. The memory may be fixed or removable. The memory may include computer program instructions or computer code contained therein. The memory 1012 and 1022 may independently be any suitable storage device, such as a non-transitory computer readable medium. The term "non-transitory" as used herein may correspond to a limitation of the medium itself (i.e., tangible, not a signal), as opposed to a limitation on data storage persistence (e.g., random access memory (RAM) versus read-only memory (ROM)). A hard disk drive (HDD), random access memory (RAM), flash memory, or other suitable memory may be used. The memories may be combined with a processor on a single integrated circuit, or may be separate from the one or more processors. Furthermore, the computer program instructions stored in the memory and processed by the processor may be computer program codes in any suitable form, such as a compiled or interpreted computer program written in any suitable programming language.

[0130] Processors 1011 and 1021, memories 1012 and 1022, and any subset thereof may be configured to provide components corresponding to the various blocks of FIGS. 5 to 9. Although not shown, the device may also include positioning hardware, such as GPS or micro-electromechanical system (MEMS) hardware, which may be used to determine a location of the device. Other sensors may also be configured to determine location, altitude, speed, orientation, etc., such as a barometer, compass, etc.

[0131] As shown in FIG. 10 , transceivers 1013 and 1023 may be provided, and one or more devices may also include at least one antenna, illustrated as 1014 and 1024, respectively. The device may have multiple antennas, such as an antenna array configured for multiple-input multiple-output (MIMO) communication, or multiple antennas for multiple RATs. For example, other configurations of these devices may be provided. Transceivers 1013 and 1023 may be a transmitter, a receiver, or both a transmitter and a receiver, or a unit or device that may be configured for both transmission and reception.

[0132] The memory and computer program instructions may be combined with a processor for a particular device to cause a hardware device, such as a UE, to perform any of the above processes (i.e., Figures 5 to 9). Therefore, in some exemplary embodiments, a non-transitory computer readable medium may be encoded with computer instructions that, when executed in hardware, perform a process such as one of the processes described herein. Alternatively, some exemplary embodiments may be performed entirely in hardware.

[0133] In certain exemplary embodiments, a device may include circuitry configured to perform any of the processes or functions shown in FIGS. 5 to 9. The term "circuitry" as used in this application may mean one or more or all of the following: (a) hardware circuitry implementations only (such as implementations in analog and / or digital circuitry only), (b) combinations of hardware circuitry and software, such as, as applicable: (i) a combination of analog and / or digital hardware circuitry and software / firmware, and (ii) any portion of hardware processor(s) with software (including digital signal processor(s), software, and memory(s) that work together to enable a device such as a mobile phone or server to perform various functions), and (c) hardware circuitry and / or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), which requires software (e.g., firmware) for operation, but the software may not be present when not required for operation. The definition of "circuitry" applies to all uses of the term in this application, including all uses of the term in any claim of the claims. By way of further example, the term "circuitry," when used in this application, also covers an implementation of only a hardware circuit or processor (or multiple processors), or a portion of a hardware circuit or processor, and its accompanying software and / or firmware. The term "circuitry," by way of example and if applicable to the particular claimed element, also covers a baseband integrated circuit or processor integrated circuit used in a mobile device, or a similar integrated circuit in a server, a cellular network device, or other computing or networking device.

[0134] FIG. 11 illustrates an example of a 5G network and system architecture according to certain exemplary embodiments. Various network functions are shown, which may be implemented as software operating as part of a network device or dedicated hardware, as a network device itself or dedicated hardware, or as a virtual function operating as a network device or dedicated hardware. The NE and UE shown in FIG. 11 may be similar to NE 1010 and UE 1020, respectively. The user plane function (UPF) may provide services such as intra-RAT and inter-RAT mobility, routing and forwarding of data packets, packet inspection, user plane quality of service (QoS) processing, buffering of downlink packets, and / or triggering of downlink data notifications. The application function (AF) may primarily interface with the core network to facilitate application use of traffic routing and interact with the policy framework.

[0135] According to some exemplary embodiments, processors 1011 and 1021, and memories 1012 and 1022 may be included in a processing circuit system or a control circuit system, or may form a part of the processing circuit system or the control circuit system. In addition, in some exemplary embodiments, transceivers 1013 and 1023 may be included in a transceiver circuit system, or may form a part of the transceiver circuit system.

[0136] In some exemplary embodiments, a device (e.g., NE 1010 and / or UE 1020) may include components for performing a method, a process, or any variation discussed herein. Examples of such components may include one or more processors, memories, controllers, transmitters, receivers, and / or computer program codes for causing the execution of such operations.

[0137] In various exemplary embodiments, the device 1020 may be controlled by the memory 1022 and the processor 1021 to receive at least one LTM CSI report configuration from a network entity via RRC; receive at least one control message configured to enable or disable at least one of the at least one LTM CSI report configuration from the network entity; and transmit an L1 measurement report to the network entity according to at least one of the at least one control message.

[0138] Certain exemplary embodiments may be directed to an apparatus comprising means for performing any of the methods described herein, including, for example, means for receiving at least one LTM CSI reporting configuration from a network entity via RRC; means for receiving at least one control message configured to enable or disable at least one of the at least one LTM CSI reporting configuration from the network entity; and means for transmitting an L1 measurement report to the network entity based on at least one of the at least one control message.

[0139] In various exemplary embodiments, the device 1010 may be controlled by the memory 1012 and the processor 1011 to transmit at least one LTM CSI reporting configuration to a user equipment via RRC; transmit at least one control message configured to enable or disable at least one of the at least one LTM CSI reporting configuration to the user equipment; and receive an L1 measurement report from the user equipment according to at least one of the at least one control message.

[0140] Certain exemplary embodiments may be directed to an apparatus comprising means for performing any of the methods described herein, including, for example, means for transmitting at least one LTM CSI reporting configuration to a user equipment via RRC; means for transmitting at least one control message configured to enable or disable at least one of the at least one LTM CSI reporting configuration to the user equipment; and means for receiving L1 measurement reports from the user equipment based on at least one of the at least one control message.

[0141] In this specification, the features, structures or characteristics of the exemplary embodiments described may be combined in any suitable manner in one or more exemplary embodiments. For example, in this specification, the use of the words "various embodiments", "certain embodiments", "some embodiments" or other similar terms means that at least one exemplary embodiment may include a particular feature, structure or characteristic described in conjunction with an exemplary embodiment. Therefore, in this specification, the words "in various embodiments", "certain embodiments", "in some embodiments" or other similar terms do not necessarily all mean the same group of exemplary embodiments, and the features, structures or characteristics may be combined in any suitable manner in one or more exemplary embodiments.

[0142] When "at least one of the following: " and "at least one of " and similar expressions are used in this document, where the list of two or more elements is linked by "and" or "or", it means at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.

[0143] In addition, the different functions or procedures discussed above may be performed in a different order and / or simultaneously as desired. Furthermore, one or more of the functions or procedures may be optional or may be combined as desired. Thus, the above description should be considered to illustrate the principles and teachings of certain exemplary embodiments, rather than to limit them.

[0144] It will be readily understood by those skilled in the art that the exemplary embodiments described above may be practiced using procedures in a different order and / or using hardware components in a configuration different from that disclosed. Therefore, although some embodiments have been described based on these exemplary embodiments, it will be apparent to those skilled in the art that certain modifications, variations, and alternative configurations will still be apparent and remain within the spirit and scope of the exemplary embodiments.

[0145] Partial Vocabulary

[0146] 3GPP Third Generation Partnership Project

[0147] 5G Fifth Generation

[0148] 5GC Fifth Generation Core

[0149] 6G Sixth Generation

[0150] ACK

[0151] AF Application Function

[0152] AM Confirmation Mode

[0153] AMF access and mobility management function

[0154] ASIC Application Specific Integrated Circuit

[0155] BM Beam Management

[0156] BWP Bandwidth Part

[0157] CBSD Citizen Broadband Radio Service Device

[0158] CC Component Carrier

[0159] CE control components

[0160] CFRA Contention-Free Random Access

[0161] CPU Central Processing Unit

[0162] CQI Channel Quality Indicator

[0163] CRI Channel Status Information Reference Signal Resource Indicator

[0164] C-RNTI Nested Radio Network Temporary Identifier

[0165] CSI channel status information

[0166] CU Centralized Unit

[0167] dB decibel

[0168] dBm decibel milliwatt

[0169] DRB Data Radio Bearer

[0170] DU Decentralized Unit

[0171] eMBB Enhanced Mobile Broadband

[0172] eNB Evolved Node B

[0173] gNB Next Generation Node B

[0174] GPS Global Positioning System

[0175] HARQ Hybrid Automatic Repeat Request

[0176] HDD Hard Disk Drive

[0177] ID Identifier

[0178] IE Information Elements

[0179] IoT

[0180] L1 Layer 1

[0181] L2 Layer 2

[0182] LCID Logical Channel Identifier

[0183] LI layer indicator

[0184] LTE Long Term Evolution

[0185] LTE-A Long Term Evolution Advanced

[0186] LTM Layer 1 or 2 Triggered Mobility

[0187] MAC Media Access Control

[0188] MEMS Micro-Electro-Mechanical Systems

[0189] MIMO Multiple Input Multiple Output

[0190] mMTC massive machine type communication

[0191] NE Network Entity

[0192] NG Next Generation

[0193] NG-eNB Next Generation Evolved Node B

[0194] NG-RAN Next Generation Radio Access Network

[0195] NR New Radio

[0196] PBCH Physical Broadcast Channel

[0197] PCell Level 1 Nest

[0198] PCI Entity Nest Identity

[0199] PDA Personal Digital Assistant

[0200] PDCCH Physical Downlink Control Channel

[0201] PDCP Packet Data Convergence Protocol

[0202] PDSCH Physical Downlink Shared Channel

[0203] PMI Precoding matrix indicator

[0204] PSCell primary and secondary nesting

[0205] PUCCH Physical Uplink Control Channel

[0206] PUSCH Physical Uplink Shared Channel

[0207] QoS Quality of Service

[0208] RACH Radio Access Channel

[0209] RAM Random Access Memory

[0210] RAN Radio Access Network

[0211] RAR Random Access Response

[0212] RAT Radio Access Technology

[0213] RF

[0214] RI Rating Indicator

[0215] ROM Read Only Memory

[0216] RRC Radio Resource Control

[0217] RSRP Reference signal received power

[0218] SCS Subcarrier Spacing

[0219] SINR Signal to Interference and Noise Ratio

[0220] S / L Servo Nest / LTM

[0221] SP Semi-Persistence

[0222] SpCell Special Cells

[0223] SS Sync Signal

[0224] SSB Synchronous Signal Block

[0225] SSBRI Synchronization Signal Broadcast Channel Resource Indicator

[0226] TA Timing Advance

[0227] TCI Transmission Configuration Indicator

[0228] UE User Equipment

[0229] UL Uplink

[0230] UMTS Universal Mobile Telecommunications System

[0231] UPF User Plane Function

[0232] URLLC Ultra-Reliable Low Latency Communications

[0233] UTRAN Universal Mobile Telecommunications System Terrestrial Radio Access Network

[0234] 1: Steps 2: Steps 3: Steps 4a: Step 4b: Step 5: Steps 6: Steps 7: Steps 8: Steps 500:Signaling diagram 501: Operation 502: Operation 503: Operation 504: Operation 505: Operation 510:UE 520: Source Nest; Nest 530:CU 540: Target nest 600: Signaling diagram 601: Operation 602: Operation 603: Operation 604: Operation 605: Operation 606: Operation 607: Operation 608: Operation 610:UE 620: Source Nest 630:CU 640: Target nest 700: Signaling diagram 701: Operation 702: Operation 703: Operation 704: Operation 705: Operation 706: Operation 707: Operation 710:UE 720: Source Nest 730:CU 740: Target Nest 800: Method 801: Steps 802: Steps 803: Steps 900: Method 901: Steps 902: Steps 903: Steps 1410:NE 1011: Processor 1012: Memory 1013: Transceiver 1014: Antenna 1020:UE;Equipment 1021: Processor 1022: Memory 1023: Transceiver 1024: Antenna

Claims

1. An apparatus for communication, comprising: means for receiving at least one Layer 1 / 2 Triggered Mobility (LTM) Channel Status Information (CSI) report configuration and at least one servo cell CSI report configuration from a network entity via Radio Resource Control (RRC) signaling; means for receiving at least one control message from the network entity, the at least one control message being configured to enable or disable at least one of the at least one LTM CSI report configuration or at least one of the at least one servo cell CSI report configuration, wherein the at least one control message includes a bit field for indicating whether the at least one control message is for an LTM CSI report or for a servo cell CSI report; and means for transmitting a Layer 1 measurement report to the network entity based on the bit field indicating that the at least one control message is for the LTM CSI report, according to the at least one of the at least one LTM CSI report configuration.

2. The equipment as requested in item 1, wherein, The at least one LTM CSI report configuration includes at least one parameter, which is configured according to at least one of the at least one LTM CSI report configurations to include at least one measurement result in the L1 measurement report.

3. The equipment as requested in item 1, wherein, The at least one control message includes at least one field that is configured to include at least one measurement result in the L1 measurement report according to at least one of the at least one LTM CSI report configuration.

4. The equipment as requested in item 2, wherein, The at least one nanometer measurement result includes at least one first-level nesting measurement.

5. The equipment as requested in item 1, wherein, The at least one control message includes at least one indication of an LTM CSI report configuration identifier indicating whether to update at least one LTM CSI or at least one servo nest CSI report configuration.

6. The equipment as requested in item 5, wherein, The at least one indication includes at least one of a servo nest / layer 1 / 2 triggered mobility field or a logical channel identifier.

7. The equipment as requested in item 1, wherein, The at least one control message includes at least one of a media access control element or a downlink control information command.

8. The device as requested in item 1, wherein, At least one control message is configured to disable the at least one LTM CSI report configuration, and the device further includes at least one of the following: a component for suspending at least one servo nest CSI report configuration; or a component for disabling at least one servo nest CSI report configuration.

9. The equipment as requested in item 1, wherein, Enabling at least one LTM CSI report configuration further includes: a component for deciding whether to continue or enable at least one previously shelved or disabled servo nest CSI report configuration.

10. The device as requested in item 1, wherein, The device is configured for semi-perpetual LTM CSI reporting on the physical uplink control channel, and the LTM CSI reporting configuration identifier is configured to update and enable the at least one LTM CSI reporting configuration.

11. The device as requested in item 1, wherein, The device is configured for semi-perpetual (SP) LTM CSI reporting on a physical uplink shared channel (PUSCH), and the LTM CSI reporting configuration identifier is configured to update and enable the at least one LTM CSI reporting configuration.

12. The apparatus of claim 5, further comprising: means for receiving from the network entity one or more LTM CSI report configurations via radio resource configurations, the at least one parameter being associated with the inclusion of one or more measurement results in the measurement report of the one or more report configurations; means for determining, based on the at least one instruction, to update information regarding the inclusion of the one or more measurement results; and means for updating at least one LTM CSI report configuration.

13. An apparatus for communication, comprising: a component for transmitting at least one Layer 1 / 2 Triggered Mobility (LTM) Channel Status Information (CSI) report configuration and at least one servo cell CSI report configuration to a user equipment via Radio Resource Control (RRC) signaling; a component for transmitting at least one control message to the user equipment, the at least one control message being configured to enable or disable at least one of the at least one LTM CSI report configuration or at least one of the at least one servo cell CSI report configuration, wherein the at least one control message includes a bit field for indicating whether the at least one control message is for an LTM CSI report or for a servo cell CSI report; and a component for receiving a Layer 1 measurement report from the user equipment and based on the bit field indicating that the at least one control message is for the LTM CSI report, according to the at least one of the at least one LTM CSI report configuration.

14. The equipment as requested in item 13, wherein, The at least one LTM CSI report configuration includes at least one parameter, which is configured according to at least one of the at least one LTM CSI report configurations to include at least one measurement result in the L1 measurement report.

15. The equipment as requested in item 13, wherein, The at least one control message includes at least one field that is configured to include at least one measurement result in the L1 measurement report according to at least one of the at least one LTM CSI report configuration.

16. The equipment as requested in item 14, wherein, The at least one nanometer measurement result includes at least one first-level nesting measurement.

17. The equipment as requested in item 13, wherein, The at least one control message includes at least one indication of an LTM CSI report configuration identifier indicating whether to update at least one LTM CSI or at least one servo nest CSI report configuration.

18. The equipment as requested in item 17, wherein, The at least one indication includes at least one of a servo nest / layer 1 / 2 triggered mobility field or a logical channel identifier.

19. The equipment as requested in item 13, wherein, The at least one control message includes at least one of a media access control element or a downlink control information command.

20. The equipment as requested in item 13, wherein, The user equipment is configured for semi-perpetual LTM CSI reporting on the physical uplink control channel, and the LTM CSI reporting configuration identifier is configured to update and enable the at least one LTM CSI reporting configuration.

21. The equipment as requested in item 13, wherein, The user equipment is configured for semi-perpetual LTM CSI reporting on a physical uplink shared channel, and the LTM CSI reporting configuration identifier is configured to update and enable the at least one LTM CSI reporting configuration.

22. The device of claim 13, further comprising: a component for transmitting to the user equipment one or more LTM CSI report configurations via radio resource configurations, including at least one parameter, the at least one parameter being incorporated into the measurement report of the one or more report configurations.

Images