Random access procedure based on physical downlink control channel (PDDCH) commands

By adding the RS_indication_bit field in DCI format 1_0 and determining the referenceSignalPower based on the QCL relationship between CSI-RS and SSB, the inaccuracy problem of UE when calculating PRACH transmission power is solved, and the quality and reliability of the random access channel are improved.

CN119095192APending Publication Date: 2024-12-06APPLE INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411393400.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2018-08-10
Filing Date
2019-08-09
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

During the existing random access process triggered by the physical downlink control channel (PDCCH) command, it is difficult for UE (user equipment) to accurately determine the referenceSignalPower when calculating the PRACH transmission power, resulting in inaccurate PRACH transmission power, affecting the access channel. quality.

Method used

Indicates whether the referenceSignalPower is provided by ss-PBCH-BlockPower or ss-PBCH-BlockPower and powerControlOffsetSS, and determines the path loss estimate of PRACH based on the QCL relationship of CSI-RS and SSB, ensuring PRACH transmission power by determining the PRACH path loss estimate based on the QCL relationship of CSI-RS and SSB. accuracy.

Benefits of technology

It improves the accuracy of PRACH transmission power, enhances the quality and reliability of the random access channel, and solves the uncertainty problem of UE when calculating transmission power.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119095192A_ABST
    Figure CN119095192A_ABST
Patent Text Reader

Abstract

The subject matter of the present disclosure is a random access procedure based on a physical downlink control channel (PDDCH) command. Methods, systems, and storage media for a random access procedure based on physical downlink control channel (PDDCH) command triggering are described. Other embodiments are also described and / or claimed for protection.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application is a divisional application of the invention patent application with international application number PCT / US2019 / 045996, international application date August 9, 2019, application number 201980053713.5, and invention name “Random access process based on physical downlink control channel (PDDCH) command”, which entered the Chinese national stage on February 9, 2021.

[0002] Related Applications

[0003] This patent application claims priority to U.S. Provisional Patent Application No. 62 / 717,547, filed on August 10, 2018, and entitled “Mechanisms on Random Access Triggered by PDCCH Older,” the entire disclosure of which is incorporated by reference in its entirety. Background Art

[0004] Embodiments described herein relate, among other things, to random access procedures triggered based on a physical downlink control channel (PDDCH) order. Embodiments of the present disclosure may be used to help perform random access channel (RACH) transmissions for new radio (NR). BRIEF DESCRIPTION OF THE DRAWINGS

[0005] The embodiment will be more easily understood by the following specific implementation in conjunction with the accompanying drawings. In order to facilitate this description, similar reference numerals represent similar structural elements. In each figure of the accompanying drawings, the embodiment is shown by way of example and not limitation.

[0006] Figure 1 and Figure 2 and Figure 3 An example of an operational flow / algorithm structure according to some embodiments is shown.

[0007] Figure 4A An example of channel state information-reference signal (CSI-RS) usage based on quasi co-site (QCL) information is shown in accordance with some embodiments.

[0008] Figure 4B An example of a measurement model according to some embodiments is shown.

[0009] Figure 5 Depicted is the architecture of a system of networks according to some embodiments.

[0010] Figure 6 Depicted are examples of components of an apparatus according to some embodiments.

[0011] Figure 7Depicted are examples of interfaces for baseband circuitry according to some embodiments.

[0012] Figure 8 A block diagram of components capable of reading instructions from a machine-readable medium or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methods discussed herein is depicted according to some embodiments. DETAILED DESCRIPTION

[0013] Embodiments discussed herein may involve a random access procedure triggered based on a physical downlink control channel (PDDCH) order.Other embodiments are also described and / or claimed.

[0014] The following detailed description refers to the accompanying drawings. The same figure numbers may be used in different drawings to identify the same or similar elements. In the following description, specific details, such as specific structures, architectures, interfaces, technologies, etc., are set forth for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the various aspects protected by the claims. However, it will be apparent to those skilled in the art who benefit from this disclosure that the various aspects of the invention protected by the claims may be practiced in other examples that deviate from these specific details. In some cases, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the invention due to unnecessary details.

[0015] The various aspects of the exemplary embodiments will be described using terms commonly used by those skilled in the art to convey the essence of their work to other persons skilled in the art. However, it will be apparent to those skilled in the art that alternative embodiments may be practiced using only some of the described aspects. For purposes of explanation, many specific quantities, materials, and configurations are set forth in order to provide a thorough understanding of the exemplary embodiments. However, it will be apparent to those skilled in the art that alternative embodiments may be practiced without these specific details. In other cases, well-known features may be omitted or simplified so as not to obscure the exemplary embodiments.

[0016] In addition, various operations will be described as multiple discrete operations in turn in a manner that is most helpful for understanding the exemplary embodiments; however, the order of description should not be understood as implying that these operations are necessarily order-dependent. In particular, these operations do not need to be performed in the order presented.

[0017] The phrases "in various embodiments", "in some embodiments", etc. may refer to the same or different embodiments. Unless the context dictates otherwise, the terms "comprising", "having", and "including" are synonymous. The phrase "A and / or B" means (A), (B), or (A and B). The phrases "A / B" and "A or B" mean (A), (B), or (A and B), similar to the phrase "A and / or B". For the purposes of the present disclosure, the phrase "at least one of A and B" means (A), (B), or (A and B). The description may use the phrases "in one embodiment", "in an embodiment", "in some embodiments", and / or "in various embodiments", which may each refer to one or more of the same or different embodiments. In addition, the terms "comprising", "including", "having", etc. used with the embodiments of the present disclosure are synonymous.

[0018] Examples of embodiments may be described as processes, which are depicted as flow charts, flow diagrams, data flow diagrams, structure diagrams, or block diagrams. Although a flow chart may describe operations as sequential processes, multiple of these operations may be performed in parallel, concurrently, or simultaneously. In addition, the order of the operations may be rearranged. A process may terminate when its operations are completed, but may also have additional steps not included in the accompanying drawings. A process may correspond to a method, function, procedure, subroutine, subprogram, etc. When a process corresponds to a function, its termination may correspond to the function returning to the calling function and / or the main function.

[0019] Examples of embodiments may be described in the general context of computer executable instructions (such as program codes, software modules, and / or functional processes) executed by one or more of the above-mentioned circuits. Program codes, software modules, and / or functional processes may include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific data types. The program codes, software modules, and / or functional processes discussed herein may be implemented using existing hardware in existing communication networks. For example, the program codes, software modules, and / or functional processes discussed herein may be implemented using existing hardware at existing network elements or control nodes.

[0020] Currently, PDCCH commands for triggering random access procedures are supported by defining specific downlink control information (DCI). For example, DCI format 1_0 is used to schedule PDSCH in one DL cell. The following information is transmitted with the help of DCI format 1_0, where the CRC is scrambled by a radio network temporary identifier (RNTI) such as C-RNTI, CS-RNTI or new-RNTI:

[0021] - Identifier of DCI format—1 bit (the value of this bit field is always set to 1, indicating DLDCI format)

[0022] - Frequency Domain Resource Allocation— bits, of which is the size of the active DL bandwidth portion in the case where DCI format 1_0 is monitored in the UE-specific search space, and satisfies: for the file cell, the total number of different DCI sizes monitored per time slot does not exceed 4, and for the cell, the total number of different DCI sizes with C-RNTI monitored per time slot does not exceed 3, otherwise is the size of the initial DL bandwidth portion.

[0023] If the CRC of DCI format 1_0 is scrambled by C-RNTI and the "Frequency Domain Resource Allocation" field is all 1, then DCI format 1_0 is used for random access procedures initiated by a PDCCH order, with all remaining fields set as follows:

[0024] - Random Access Preamble Index—6 bits according to ra-PreambleIndex.

[0025] - Uplink / Supplementary Uplink (UL / SUL) indicator—1 bit. If the value of "Random Access Preamble Index" is not all zeros and if the UE is configured with SUL in the cell, this field indicates which UL carrier in the cell is to transmit PRACH according to Table 7.3.1.1.1-1; otherwise, this field is reserved.

[0026] -SS / PBCH Index—6 bits. If the value of the "Random Access Preamble Index" is not all zeros, this field indicates the SS / PBCH that will be used to determine the RACH opportunity for PRACH transmission; otherwise, this field is reserved.

[0027] -PRACH Mask Index—4 bits. If the value of "Random Access Preamble Index" is not all zeros, this field indicates the RACH opportunity of the PRACH transmission associated with the SS / PBCH indicated by "SS / PBCH Index" according to subclause 5.1.1 of [8, TS38.321];

[0028] Otherwise, keep the field.

[0029] - Reserved bits—10 bits.

[0030] Based on the above, if a user equipment (UE) receives a DCI including the above information, the UE must transmit a random access preamble using the indicated preamble index, the indicated RACH opportunity, and the associated SS / PBCH index indicated by the DCI.

[0031] If the UE receives this PDCCH command, the UE needs to calculate the power used to transmit the corresponding PRACH, and the power equation requires the path loss information between the NR base station (called gNB) and the UE. This path loss information is obtained by measuring some reference signals (RS), and the reference signals to be measured need to be pre-configured. The UE must also know the reference Tx power of the RS in advance to calculate the accurate transmission power of the PRACH. According to 3GPP TS 38.213v.15.2.0, 2018-06-29:

[0032] If the PRACH transmission from the UE is not in response to the UE's detection of a PDCCH order, or in response to the UE's detection of a PDCCH order triggering a contention-based random access procedure, the referenceSignalPower is provided by the ss-PBCH-BlockPower.

[0033] If the PRACH transmission from the UE is in response to the UE's detection of a PDCCH order triggering a non-contention based random access procedure and is based on a DL RS quasi-collocated with the DM-RS of the PDCCH order as described in subclause 10.1, the referenceSignalPower is provided by ss-PBCH-BlockPower, or when the UE is configured for resources for periodic CSI-RS reception, the referenceSignalPower is obtained from the higher layer parameters ss-PBCH-BlockPower and powerControlOffsetSS, where powerControlOffsetSS provides an offset of the CSI-RS transmission power relative to the SS / PBCH block transmission power [6, TS 38.214]. If powerControlOffsetSS is not provided to the UE, the UE assumes an offset of 0 dB.

[0034] According to the above paragraph, referenceSignalPower may be provided by ss-PBCH-BlockPower or ss-PBCH-BlockPower together with powerControlOffsetSS, depending on whether the RACH is associated with SSB or CSI-RS.

[0035] However, 3GPP TS 38.214v.15.2.0, 2018-06-29 states that if the TCI state is activated, the PDCCH will be QCLed together with the CSI-RS. In this case, it is not possible for the ss-PBCH-BlockPower to become the referenceSignalPower of the PRACH that may need to be supported. For example:

[0036] For DM-RS of PDCCH, the UE shall expect the TCI-State to indicate the following quasi co-location type:

[0037] one:

[0038] - "QCL-Type A" has CSI-RS resources in NZP-CSI-RS-ResourceSet configured with higher layer parameter trs-Info and, when applicable,

[0039] "QCL-Type D" has the same CSI-RS resources, or

[0040] - "QCL-Type A" has CSI-RS resources in NZP-CSI-RS-ResourceSet configured with higher layer parameter trs-Info and, when applicable,

[0041] "QCL-Type D" has CSI-RS resources in NZP-CSI-RS-ResourceSet configured with a higher layer parameter repetition, or when "QCL-Type D" is not applicable, - "QCL-Type A" has CSI-RS resources in NZP-CSI-RS-ResourceSet not configured with a higher layer parameter trs-Info and not configured with a higher layer parameter repetition.

[0042] Additionally, there may be multiple CSI-RSs with which the PDCCH is quasi co-located (QCLed). Therefore, it is unclear which CSI-RSs must be considered for the referenceSignalPower of the RACH transmission.

[0043] The embodiments herein provide a mechanism for random access triggered by a PDCCH order.

[0044] For PRACH, the UE determines the transmit power P of the physical random access channel (PRACH) for the active UL BWP b on carrier f based on the current SS / PBCH block for serving cell c at transmission occasion i. PRACH.b.f.c (i) Determined as

[0045] P PRACH.b.f.c (i) = min{P CMAZ.f.c (i),P PRACH.目标..f.c +PL b.f.c}[dBm],

[0046] Where P CMAX.f.c (i) is the UE transmission power configured for carrier f of serving cell c in transmission opportunity i, P PRACH.目标.f.cis the PRACH preamble target received power preamble PREAMBLE_RECEIVED_TARGET_POWER provided by the higher layer for UL BWP b of carrier f serving cell c, and PL b.f.c is the path loss of the UL BWP b for carrier f of the current SS / PBCH block of serving cell c, calculated by the UE in dB as referenceSignalPower—RSRP filtered by higher layers, where RSRP is defined elsewhere and the higher layer filtering configuration is defined elsewhere.

[0047] If the UE has received a higher layer parameter TCI-States PDCCH containing a single TCI state, or if the UE has received a MAC CE activation command for one of the TCI states, the UE assumes that the DM-RS antenna port associated with PDCCH reception is quasi-co-located with one or more DL RS configured by the TCI state.

[0048] However, depending on the TCI state of the UE, the QCL information may be different, and multiple CSI-RS may be used for different QCLs, as shown in Table 4. Here, Type A QCL indicates that the reference signal is QCLed with respect to Doppler shift, Doppler spread, average delay, and delay spread. And Type D QCL indicates that the reference signal is QCLed with respect to spatial Rx parameters.

[0049] In one embodiment, when the UE is configured with resources for periodic CSI-RS reception, and when the CSI-RS for tracking is configured for CQL information 1 and the CSI-RS for beam management is configured for QCL information 2, the referenceSignalPower may be obtained through the higher layer parameters ss-PBCH-BlockPower and powerControlOffsetSS, where powerControlOffsetSS provides an offset of the transmission power of the CSI-RS (TRS) for tracking relative to the SS / PBCH block transmission power. Here, the CSI-RS for tracking may be defined as "CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info", and the CSI-RS for beam management may be defined as "CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with the higher layer parameter repetition".

[0050] In another embodiment, when the UE is configured with resources for periodic CSI-RS reception, and when the CSI-RS for tracking is configured for CQL information 1 and the CSI-RS for beam management is configured for QCL information 2, the referenceSignalPower may be obtained through higher layer parameters ss-PBCH-BlockPower and powerControlOffsetSS, where powerControlOffsetSS provides an offset of the transmission power of the CSI-RS (BMRS) for beam management relative to the SS / PBCH block transmission power. Here, the CSI-RS for tracking may be defined as "CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info", and the CSI-RS for beam management may be defined as "CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with the higher layer parameter repetition".

[0051] In another embodiment, in DCI format 1_0 for a random access procedure initiated by a PDCCH command, an additional bit (RS_indication_bit) may be added to indicate whether referenceSignalPower is provided by ss-PBCH-BlockPower or by both ss-PBCH-BlockPower and powerControlOffsetSS, where powerControlOffsetSS indicates the offset of the CSI-RS transmission power relative to the SS / PBCH block transmission power. The RS_indication_bit enables the NW to associate PRACH with SS / PBCH or CSI-RS even if the UE has received a higher layer parameter TCI-StatesPDCCH containing a single TCI state or if the UE has received a MAC CE activation command for one of the TCI states. If the RS_indication_bit is 0, the referenceSignalPower is provided by ss-PBCH-BlockPower, and the SSB is used for path loss estimation of PRACH transmission. Here, the path loss estimation may be based on the SSB indicated by the DCI for the PDCCH command. If RS_indication_bit is 1, referenceSignalPower is provided by ss-PBCH-BlockPower and powerControlOffsetSS, and CSI-RS is used for path loss estimation for PRACH transmission.

[0052] In another embodiment, referenceSignalPower is provided by ss-PBCH-BlockPower or by both ss-PBCH-BlockPower and powerControlOffsetSS, depending on whether the CSI-RS is QCLed with the SSB. If the CSI-RS is QCLed with the SSB, the UE assumes that the SSB is associated with the PRACH, and referenceSignalPower is provided by ss-PBCH-BlockPower. However, if the CSI-RS is not QCLed with the SSB, the UE assumes that the CSI-RS is associated with the PRACH, and referenceSignalPower is provided by ss-PBCH-BlockPower and powerControlOffsetSS, where powerControlOffsetSS provides an offset of the CSI-RS transmit power relative to the SS / PBCH block transmit power.

[0053] Beam management

[0054] In the NR specific implementation, beam management refers to a set of L1 / L2 processes for acquiring and maintaining a set of transmit / receive points (TRP or TRxP) and / or UE beams that can be used for downlink (DL) and uplink (UL) transmission / reception. Beam management includes various operations or processes, such as beam determination, beam management, beam reporting, and beam scanning operations / processes. Beam determination refers to the ability of a TRxP or UE to select its own transmit (Tx) / receive (Rx) beam. Beam measurement refers to the ability of a TRP or UE to measure the characteristics of a received beamforming signal. Beam reporting refers to the ability of a UE to report information about a beamforming signal based on beam measurements. Beam scanning refers to the operation of transmitting and / or receiving a beam covering a spatial area during a time interval in a predetermined manner.

[0055] The Tx / Rx beam correspondence at the TRxP holds if at least one of the following conditions is satisfied: The TRxP can determine the TRxP Rx beam for uplink reception based on the UE's downlink measurements on one or more Tx beams of the TRxP; and the TRxP can determine the TRxP Tx beam for downlink transmission based on the TRxP's uplink measurements on one or more Rx beams of the TRxP. The Tx / Rx beam correspondence at the UE holds if at least one of the following is satisfied: The UE can determine the UE Tx beam for uplink transmission based on the UE's downlink measurements on one or more Rx beams of the UE; the UE can determine the UE Rx beam for downlink reception based on the indication from the TRxP (based on the UE's uplink measurements on one or more Tx beams of the UE); and an ability indication supporting UE beam-TRxP correspondence related information.

[0056] In some specific embodiments, DL beam management includes process P-1, process P-2, and process P-3. Process P-1 is used to implement UE measurements on different TRxP Tx beams, thereby supporting the selection of the TRxP Tx beam / UE Rx beam. For beamforming at the TRxP, process P-1 generally includes intra-TRxP / inter-TRxP Tx beam scanning from different beam sets. For beamforming at the UE, process P-1 generally includes UE Rx beam scanning from a set of different beams.

[0057] Process P-2 is used to implement UE measurements on different TRxP Tx beams, thereby possibly changing the inter-TRxP / intra-TRxP Tx beams. Process P-2 can be a special case of process P-1, where process P-2 is used for a possibly smaller set of beams for beam refinement than process P-1. Process P-3 is used to implement UE measurements on the same TRxP Tx beam when the UE uses beamforming, thereby changing the UE Rx beam. Processes P-1, P-2, and P-3 can be used for aperiodic beam reporting.

[0058] UE measurements based on the RS (at least CSI-RS) for beam management are composed of K beams (where K is the total number of configured beams), and the UE reports the measurement results of N selected Tx beams (where N may or may not be a fixed number). Processes based on the RS for mobility purposes are not excluded. If N < K, the beam information to be reported includes the measurements of the N beams and the information indicating the N DL Tx beams. Other information or data may be included in or included together with the beam information. When the UE is configured with K' > 1 non-zero power (NZP) CSI-RS resources, the UE may report N' CSI-RS resource indicators (CRIs).

[0059] In some NR implementations, the UE may trigger a mechanism to recover from a beam failure, which is referred to as "beam recovery", "beam failure recovery request procedure", etc. A beam failure event may occur when the link quality of the beam pair of the associated control channel drops below a threshold, or when an associated timer times out. When a beam failure occurs, the beam recovery mechanism is triggered. The network may explicitly configure the UE with resources for UL transmission of signals for recovery purposes. Configuration of resources is supported when the base station (e.g., aTRP, gNB, etc.) listens from all or some directions (e.g., random access areas). The UL transmission / resources used to report beam failures may be in the same time instance as the physical random access channel (PRACH) or resources orthogonal to the PRACH resources, or in a time instance different from the PRACH (configurable for the UE). Transmission of DL signals is supported to allow the UE to monitor beams and thereby identify new potential beams.

[0060] For beam failure recovery, if one, multiple, or all serving PDCCH beams fail, a beam failure may be indicated. If a beam failure is indicated, a beam failure recovery request procedure is initiated. For example, when a beam failure is detected on a serving SSB / CSI-RS, the beam failure recovery request procedure may be used to indicate to the serving gNB (or TRP) of a new SSB or CSI-RS. A beam failure may be detected by lower layers and indicated to the UE's media access control (MAC) entity.

[0061] In some implementations, beam management includes providing or not providing beam-related indications. When beam-related indications are provided, information related to the UE-side beamforming / reception process for CSI-RS-based measurements may be indicated to the UE via QCL. The control channel and the corresponding data channel may be supported to be transmitted using the same or different beams.

[0062] Downlink (DL) beam indication is based on the transmission configuration indication (TCI) state. The TCI state is indicated in a TCI list configured by a radio resource control (RRC) and / or a medium access control (MAC) control element (CE). In some specific implementations, based on a detected PDCCH with downlink control information (DCI) for the UE and a given serving cell, the UE may be configured by higher layer signaling to decode the PDSCH with up to M TCI-States, where M depends on the UE capabilities. Each configured TCI state includes a reference signal (RS) group TCI-RS-SetConfig. Each TCI-RS-SetConfig includes parameters for configuring a quasi-co-location relationship between the RS in the RS group and the demodulation reference signal (DM-RS) port group of the PDSCH. The RS group includes a reference to one or two DL RSs and an associated QCL-type configured for each DL RS by a higher layer parameter quasi-co-location type (QCL-type). For the case of two DL RSs, the QCL type should not be the same regardless of whether the reference is to the same DL RS or to different DL RSs. The quasi co-location type indicated to the UE is based on the higher layer parameter QCL-Type and adopts one of the following types or a combination thereof: QCL-Type A: {Doppler shift, Doppler spread, average delay, delay spread}; QCL-Type B: {Doppler shift, Doppler spread}; QCL-Type C: {average delay, Doppler shift}; QCL-Type D: {spatial Rx parameters}.

[0063] The UE may receive a selection command (e.g., in a MAC CE) for mapping up to 8 TCI states to code points of the DCI field TCI-States. Until the UE receives a higher layer configuration of the TCI state and before receiving an activation command, the UE may assume that the antenna ports of one DM-RS port group of the PDSCH of the serving cell are spatially quasi-co-located with the SSB determined during the initial access process. When the number of TCI states in TCI-States is less than or equal to 8, the DCI field TCI-States directly indicates the TCI state.

[0064] The beam failure recovery request may be delivered via a dedicated PRACH or physical uplink control channel (PUCCH) resource. For example, for a serving cell, the UE may be configured by a higher layer parameter Beam-Failure-Detection-RS-ResourceConfig with a set of periodic CSI-RS resource configuration indices The higher layer parameter Candidate-Beam-RS-List is configured as a set of CSI-RS resource configuration index and / or SS / PBCH block index. For radio link quality measurement of the serving cell. If no configuration is present, beam failure detection may be based on CSI-RS or SSB that is spatially quasi-co-located (QCLed) with the PDCCH demodulation reference signal (DMRS). For example, if the UE is not configured with the higher layer parameter Beam-Failure-Detection-RS-ResourceConfig, the UE determines Includes SS / PBCH blocks and periodic CSI-RS configurations having a value of a higher layer parameter TCI-StatesPDCCH that is the same as the value of a control resource set (CORESET) that the UE is configured to monitor PDCCH.

[0065] The physical layer of the UE is based on the threshold Q out,LR Resource configuration collection To evaluate the quality of the radio link. out,LR Corresponding to the default values ​​of the higher layer parameters RLM-IS-OOS-thresholdConfig and beam-failure-candidate-beam-threshold, respectively. The UE evaluates the radio link quality based only on the quasi-co-located periodic CSI-RS resource configuration or SS / PBCH block, where the DM-RS of the PDCCH reception DM-RS is monitored by the UE. in,LR The threshold is applied to the periodic CSI-RS resource configuration. The UE sets Q after scaling the SS / PBCH block transmission power with the value provided by the higher layer parameter Pc_SS. out,LR The threshold is applied to SS / PBCH blocks.

[0066] In some implementations, if the MAC entity receives a beam failure indication from a lower layer, the MAC entity starts a beam failure recovery timer (beamFailureRecoveryTimer) and initiates a random access procedure. If the beamFailureRecovetyTimer times out, the MAC entity indicates to the upper layer that the beam failure recovery request failed. If a DL assignment or UL grant is received (e.g., on a PDCCH addressed to a cell radio network temporary identifier (C-RNTI)), the MAC entity may stop and reset the beamFailureRecovetyTimer to consider the beam failure recovery request procedure completed successfully.

[0067] Beam Measurement

[0068] In some embodiments, the UE (e.g., in RRC_CONNECTED mode) measures one or more beams of a cell and averages the measurements (power values) to derive cell quality. The UE may be configured to consider a subset of detected beams, such as the N best beams above an absolute threshold. Filtering occurs at two different levels, including at the physical layer (PHY) to derive beam quality and at the RRC level to derive cell quality from multiple beams. Serving cells and non-serving cells may derive cell quality from beam measurements in the same manner. If the gNB configures the UE to do so, the measurement report contains measurements of the X best beams. For the purpose of channel state estimation, the UE may be configured to measure CSI-RS resources and estimate the downlink channel state based on the CSI-RS measurements. The UE feeds back the estimated channel state to the gNB for link adaptation.

[0069] Figure 4B An example of a measurement model is shown. Figure 4B In the example, point A includes measurements internal to the PHY (e.g., beam-specific samples). Layer 1 (L1) filtering includes internal layer 1 filtering circuitry for filtering the input measured at point A. The exact filtering mechanism and how the measurements are actually performed at the PHY may be implementation specific. The measurements (e.g., beam-specific measurements) are reported by the L1 filtering to the PHY at point A. 1 Layer 3 (L3) beam filtering circuit and beam consolidation / selection circuit at.

[0070] The beam consolidation / selection circuit includes circuitry to consolidate beam-specific measurements to derive cell quality. For example, if N>1, otherwise when N=1, the best beam measurement may be selected to derive cell quality. The configuration of the beam is provided by RRC signaling. Then after beam consolidation / selection, the measurement results (e.g., cell quality) derived from the beam-specific measurements are reported to the L3 filtering for cell quality circuit. In some embodiments, the reporting period at point B may be equal to the reporting period at point A. 1 A measurement cycle at .

[0071] The L3 filtering for the cell quality circuit is configured to filter the measurement provided at point B. The configuration of the layer 3 filter is provided by the aforementioned RRC signaling or different / separate RRC signaling. In some embodiments, the filtering reporting period at point C may be equal to one measurement period at point B. The measurement is provided to the evaluation of the reporting criteria circuit at point C after processing in the layer 3 filtering circuit. In some embodiments, the reporting rate may be the same as the reporting rate at point B. The measurement input may be used for one or more evaluations of the reporting criteria.

[0072] The evaluation of the reporting criteria circuit is configured to check whether an actual measurement report is required at point D. The evaluation may be based on more than one measurement stream at reference point C. In one example, the evaluation may involve a comparison between different measurements, such as a measurement provided at point C and a measurement provided at point C. 1 In some embodiments, the UE may at least whenever at point C, at point C 1 The reporting criteria are evaluated when reporting new measurement results at point D. The reporting criteria configuration is provided by the above RRC signaling (UE measurement) or by different / separate RRC signaling. After the evaluation, the measurement report information is sent on the radio interface at point D (e.g., as a message).

[0073] See point A again 1 , will be at point A 1 The measurements provided at point E are provided to L3 beam filtering circuitry, which is configured to perform beam filtering of the provided measurements (e.g., beam-specific measurements). The configuration of the beam filter is provided by the RRC signaling described above or by different / separate RRC signaling. In some embodiments, the filtering reporting period at point E may be equal to the filtering reporting period at point A. 1 The K beams may correspond to measurements on New Radio (NR) synchronization signal (SS) blocks (SSBs) or channel state information reference signal (CSI-RS) resources configured for L3 mobility of the gNB and detected by the UE at L1.

[0074] After processing in the beam filter measurement (e.g., beam specific measurement), the measurement is provided to the beam selection for reporting circuitry at point E. The measurement is used as input to select the X measurements to be reported. In some embodiments, the reporting rate may be the same as at point A. 1 The beam selection for beam reporting circuitry is configured to select X measurements from the measurements provided at point E. The configuration of this module is provided by the aforementioned RRC signaling or different / separate RRC signaling. The beam measurement information included in the measurement report is sent or scheduled for transmission on the radio interface at point F.

[0075] The measurement report includes a measurement identifier of the relevant measurement configuration that triggered the report. The measurement report may also include cell and beam measurement quantities configured by the network (e.g., using RRC signaling) included in the measurement report. The measurement report may also include the number of non-service cells to be reported, which may be limited by network configuration. Cells belonging to a blacklist configured by the network are not used for event evaluation and reporting. Conversely, when the network configures a whitelist, only cells belonging to the whitelist are used for event evaluation and reporting. The beam measurements included in the measurement report are configured by the network, and such measurement report only includes or indicates a beam identifier, including measurement results and a beam identifier, or does not include a beam report.

[0076] Figure 5 The architecture of a system 500 of a network according to some embodiments is shown. System 500 is shown to include user equipment (UE) 501 and UE 502. UE 501 and UE 502 are shown as smart phones (e.g., handheld touch screen mobile computing devices that can connect to one or more cellular networks), but these UEs can also include any mobile or non-mobile computing devices, such as personal data assistants (PDAs), pagers, laptop computers, desktop computers, wireless handheld terminals, or any computing device that includes a wireless communication interface.

[0077] In some embodiments, either UE 501 and UE 502 may include an Internet of Things (IoT) UE, which may include a network access layer designed for low-power IoT applications that utilize short-term UE connections. The IoT UE may utilize technologies such as machine-to-machine (M2M) or machine-type communication (MTC) to exchange data with an MTC server or device via a public land mobile network (PLMN), proximity-based services (ProSe) or device-to-device (D2D) communication, a sensor network, or an IoT network. The M2M or MTC data exchange may be a machine-initiated data exchange. The IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-lived connections. The IoT UE may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network.

[0078] UE 501 and UE 502 may be configured to connect, e.g., be communicatively coupled, to a radio access network (RAN) 510—RAN 510 may be, e.g., an evolved universal mobile telecommunications system (UMTS) terrestrial radio access network (E-UTRAN), a next generation RAN (NG RAN), or some other type of RAN. UE 501 and UE 502 utilize connection 503 and connection 504, respectively, each of which includes a physical communication interface or layer (discussed in further detail below); in this example, connection 503 and connection 504 are shown as air interfaces to achieve communicatively coupling, and may be consistent with a cellular communication protocol, such as a global system for mobile communications (GSM) protocol, a code division multiple access (CDMA) network protocol, a push-to-talk (PTT) protocol, a cellular PTT (POC) protocol, a universal mobile telecommunications system (UMTS) protocol, a 3GPP long term evolution (LTE) protocol, a fifth generation (5G) protocol, a new radio (NR) protocol, etc.

[0079] In this embodiment, UE 501 and UE 502 may also directly exchange communication data via ProSe interface 505. ProSe interface 505 may alternatively be referred to as a sidelink interface including one or more logical channels including, but not limited to, a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), a physical sidelink discovery channel (PSDCH), and a physical sidelink broadcast channel (PSBCH).

[0080] UE 502 is shown configured to access access point (AP) 506 via connection 507. Connection 507 may include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, where AP 506 would include wireless fidelity. In this example, AP 506 is shown connected to the Internet without being connected to the core network of the wireless system (described in further detail below).

[0081] The RAN 510 may include one or more access nodes that enable connection 503 and connection 504. These access nodes (ANs) may be referred to as base stations (BS), NodeBs, evolved NodeBs (eNBs), next generation NodeBs (gNBs), RAN nodes, etc., and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). The RAN 510 may include one or more RAN nodes (e.g., macro RAN nodes 511) for providing macro cells, and one or more RAN nodes (e.g., low power (LP) RAN nodes 512) for providing femto cells or pico cells (e.g., cells with smaller coverage areas, smaller user capacity, or higher bandwidth than macro cells).

[0082] Either of the RAN nodes 511 and 512 may terminate the air interface protocol and may be the first point of contact for the UE 501 and UE 502. In some embodiments, either of the RAN nodes 511 and 512 may fulfill various logical functions of the RAN 510, including but not limited to the functions of a radio network controller (RNC), such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0083] According to some embodiments, UE 501 and UE 502 may be configured to communicate with each other or with any of RAN nodes 511 and 512 through a multi-carrier communication channel using orthogonal frequency division multiplexing (OFDM) communication signals according to various communication techniques, such as, but not limited to, orthogonal frequency division multiple access (OFDMA) communication techniques (e.g., for downlink communications) or single carrier frequency division multiple access (SC-FDMA) communication techniques (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. OFDM signals may include multiple orthogonal subcarriers.

[0084] In some embodiments, a downlink resource grid may be used for downlink transmissions from either of RAN node 511 and RAN node 512 to UE 501 and UE 502, while uplink transmissions may utilize similar techniques. The grid may be a time-frequency grid, referred to as a resource grid or a time-frequency resource grid, which is a physical resource in the downlink in each time slot. For OFDM systems, such a time-frequency plane representation is common practice, which makes wireless resource allocation intuitive. Each column and each row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid includes a plurality of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block includes a set of resource elements; in the frequency domain, this may represent the minimum amount of resources that can currently be allocated. Such resource blocks are used to transmit several different physical downlink channels.

[0085] The physical downlink shared channel (PDSCH) may carry user data and higher layer signaling to UE 501 and UE 502. The physical downlink control channel (PDCCH) may carry information about the transport format and resource allocation related to the PDSCH channel, etc. The PDCCH may also inform UE 501 and UE 502 of the transport format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel. Typically, downlink scheduling (allocation of control and shared channel resource blocks to UE 502 within a cell) may be performed at either RAN node 511 or RAN node 512 based on channel quality information fed back from either UE 501 or UE 502. Downlink resource allocation information may be sent on the PDCCH used for (e.g., allocated to) each of UE 501 and UE 502.

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

[0087] Some embodiments may use the concept of resource allocation for control channel information, which is an extension of the above concept. For example, some embodiments may utilize an enhanced physical downlink control channel (EPDCCH) that uses PDSCH resources for control information transmission. One or more enhanced control channel elements (ECCEs) may be used to transmit EPDCCH. Similar to the above, each ECCE may correspond to four sets of nine physical resource elements, referred to as enhanced resource element groups (EREGs). In some cases, ECCEs may have other numbers of EREGs.

[0088] RAN 510 is shown as being communicatively coupled to a core network (CN) 520 via an S1 interface 513. In an embodiment, CN 520 may be an evolved packet core (EPC) network, a next generation packet core (NPC) network, or some other type of CN. In this embodiment, S1 interface 513 is divided into two parts: S1-U interface 514, which carries traffic data between RAN nodes 511 and 512 and a serving gateway (S-GW) 522; and S1-mobility management entity (MME) interface 515, which is a signaling interface between RAN nodes 511 and 512 and MME 521.

[0089] In this embodiment, CN 520 includes MME 521, S-GW 522, Packet Data Network (PDN) Gateway (P-GW) 523 and Home Subscriber Server (HSS) 524. MME 521 may be similar in function to the control plane of a conventional Serving General Packet Radio Service (GPRS) Support Node (SGSN). MME 521 may manage mobility aspects in access, such as gateway selection and tracking area list management. HSS 524 may include a database for network users, including subscription-related information to support network entities' handling of communication sessions. Depending on the number of mobile subscribers, the capacity of the equipment, the organization of the network, etc., CN 520 may include one or more HSS 524. For example, HSS 524 may provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependencies, etc.

[0090] The S-GW 522 may terminate the S1 interface 513 towards the RAN 510 and route data packets between the RAN 510 and the CN 520. In addition, the S-GW 522 may be a local mobility anchor point for inter-RAN node handovers and may also provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful interception, charging, and enforcement of certain policies.

[0091] The P-GW 523 may terminate the SGi interface toward the PDN. The P-GW 523 may route data packets between the EPC network and an external network such as a network including an application server 530 (alternatively referred to as an application function (AF)) via an Internet Protocol (IP) interface 525. Generally, the application server 530 may be an element that provides an application program that uses IP bearer resources with the core network (e.g., UMTS packet service (PS) domain, LTE PS data service, etc.). In this embodiment, the P-GW 523 is shown as being communicatively coupled to the application server 530 via an IP communication interface 525. The application server 530 may also be configured to support one or more communication services (e.g., Voice over Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UE 501 and UE 502 via the CN 520.

[0092] The P-GW 523 may also be a node for policy enforcement and charging data collection. The Policy and Charging Enforcement Function (PCRF) 526 is a policy and charging control element of the CN 520. In a non-roaming scenario, there may be a single PCRF in the domestic public land mobile network (HPLMN) associated with the UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with local traffic breakout, there may be two PCRFs associated with the UE's IP-CAN session: a domestic PCRF (H-PCRF) in the HPLMN and a visited PCRF (V-PCRF) in the visited public land mobile network (VPLMN). The PCRF 526 may be communicatively coupled to the application server 530 via the P-GW 523. The application server 530 may signal the PCRF 526 to indicate a new service flow and select appropriate quality of service (QoS) and charging parameters. PCRF 526 may configure the rules to a Policy and Charging Enforcement Function (PCEF) (not shown) with the appropriate Communication Flow Template (TFT) and QoS Class Identifier (QCI), which initiates the QoS and charging specified by application server 530 .

[0093] Figure 6 Exemplary components of a device 600 according to some embodiments are shown. In some embodiments, the device 600 may include an application circuit 602, a baseband circuit 604, a radio frequency (RF) circuit 606, a front-end module (FEM) circuit 608, one or more antennas 610, and a power management circuit (PMC) 612 (at least coupled together as shown). The components of the illustrated device 600 may be included in a UE or a RAN node. In some embodiments, the device 600 may include fewer elements (e.g., the RAN node may not utilize the application circuit 602, but include a processor / controller to process IP data received from the EPC). In some embodiments, the device 600 may include additional elements, such as, for example, a memory / storage device, a display, a camera, a sensor, or an input / output (I / O) interface. In other embodiments, the components described below may be included in more than one device (e.g., the circuit may be separately included in more than one device for a specific implementation of a cloud-RAN (C-RAN)).

[0094] The application circuit 602 may include one or more application processors. For example, the application circuit 602 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The processors may include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors, application processors, etc.). These processors may be coupled to or may include memory / storage devices, and may be configured to execute instructions stored in the memory / storage devices to enable various applications or operating systems to run on the device 600. In some embodiments, the processor of the application circuit 602 may process IP data packets received from the EPC.

[0095] The baseband circuit 604 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The baseband circuit 604 may include one or more baseband processors or control logic components to process baseband signals received from the receive signal path of the RF circuit 606 and generate baseband signals for the transmit signal path of the RF circuit 606. The baseband processing circuit 604 may interact with the application circuit 602 to generate and process baseband signals and control the operation of the RF circuit 606. For example, in some embodiments, the baseband circuit 604 may include a third generation (3G) baseband processor 604A, a fourth generation (4G) baseband processor 604B, a fifth generation (5G) baseband processor 604C, or other baseband processors 604D of other existing generations, generations under development or generations to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.). The baseband circuit 604 (e.g., one or more baseband processors of the baseband processors 604A-604D) may handle various radio control functions that enable communication with one or more radio networks via the RF circuit 606. In other embodiments, some or all of the functionality of baseband processors 604A-D may be included in a module stored in memory 604G and executed via central processing unit (CPU) 604E. Radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some embodiments, the modulation / demodulation circuitry of baseband circuitry 604 may include fast Fourier transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuitry of baseband circuitry 604 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functions. The implementation of modulation / demodulation and encoder / decoder functions is not limited to these examples, and may include other suitable functions in other embodiments.

[0096] In some embodiments, the baseband circuit 604 may include one or more audio digital signal processors (DSPs) 604F. The audio DSP 604F may include elements for compression / decompression and echo cancellation, and may include other suitable processing elements in other embodiments. In some embodiments, the components of the baseband circuit may be appropriately combined in a single chip, a single chipset, or disposed on the same circuit board. In some embodiments, some or all of the components of the baseband circuit 604 and the application circuit 602 may be implemented together, such as on a system on a chip (SOC).

[0097] In some embodiments, the baseband circuit 604 may provide communications compatible with one or more radio technologies. For example, in some embodiments, the baseband circuit 604 may support communications with an Evolved Universal Terrestrial Radio Access Network (EUTRAN) or other wireless metropolitan area network (WMAN), wireless local area network (WLAN), wireless personal area network (WPAN). Embodiments in which the baseband circuit 604 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuits.

[0098] RF circuit 606 can communicate with a wireless network through a non-solid medium using modulated electromagnetic radiation. In various embodiments, RF circuit 606 may include switches, filters, amplifiers, etc. to facilitate communication with a wireless network. RF circuit 606 may include a receive signal path, which may include circuits for down-converting RF signals received from FEM circuit 608 and providing baseband signals to baseband circuit 604. RF circuit 606 may also include a transmit signal path, which may include circuits for up-converting baseband signals provided by baseband circuit 604 and providing RF output signals for transmission to FEM circuit 608.

[0099] In some embodiments, the receive signal path of the RF circuit 606 may include a mixer circuit 606a, an amplifier circuit 606b, and a filter circuit 606c. In some embodiments, the transmit signal path of the RF circuit 606 may include a filter circuit 606c and a mixer circuit 606a. The RF circuit 606 may also include a synthesizer circuit 606d for synthesizing the frequency used by the mixer circuit 606a for the receive signal path and the transmit signal path. In some embodiments, the mixer circuit 606a of the receive signal path may be configured to down-convert the RF signal received from the FEM circuit 608 based on the synthesized frequency provided by the synthesizer circuit 606d. The amplifier circuit 606b may be configured to amplify the down-converted signal, and the filter circuit 606c may be a low pass filter (LPF) or a band pass filter (BPF) configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal may be provided to the baseband circuit 604 for further processing. In some embodiments, the output baseband signal may be a zero frequency baseband signal, although this is not required.In some embodiments, the mixer circuit 606a of the receive signal path may include a passive mixer, although the scope of the embodiments is not limited in this respect.

[0100] In some embodiments, mixer circuit 606a of the transmit signal path can be configured to upconvert an input baseband signal based on a synthesized frequency provided by synthesizer circuit 606d to generate an RF output signal for FEM circuit 608. The baseband signal can be provided by baseband circuit 604 and can be filtered by filter circuit 606c.

[0101] In some embodiments, the mixer circuit 606a of the receiving signal path and the mixer circuit 606a of the transmitting signal path may include two or more mixers and may be arranged to be used for orthogonal down-conversion and up-conversion, respectively. In some embodiments, the mixer circuit 606a of the receiving signal path and the mixer circuit 606a of the transmitting signal path may include two or more mixers and may be arranged to be used for image suppression (e.g., Hartley image suppression). In some embodiments, the mixer circuit 606a of the receiving signal path and the mixer circuit 606a of the transmitting signal path may be arranged for direct down-conversion and direct up-conversion, respectively. In some embodiments, the mixer circuit 606a of the receiving signal path and the mixer circuit 606a of the transmitting signal path may be configured for superheterodyne operation.

[0102] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, the RF circuit 606 may include an analog-to-digital converter (ADC) circuit and a digital-to-analog converter (DAC) circuit, and the baseband circuit 604 may include a digital baseband interface to communicate with the RF circuit 606.

[0103] In some dual-mode embodiments, separate radio IC circuits may be provided to process signals for each spectrum, although the scope of the embodiments is not limited in this respect.

[0104] In some embodiments, synthesizer circuit 606d may be a fractional-N synthesizer or a fractional N / N+1 synthesizer, but the scope of the embodiments is not limited in this respect, as other types of frequency synthesizers may also be suitable. For example, synthesizer circuit 606d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0105] Synthesizer circuit 606d may be configured to synthesize an output frequency based on the frequency input and the divider control input for use by mixer circuit 606a of RF circuit 606. In some embodiments, synthesizer circuit 606d may be a fractional-N / N+1 synthesizer.

[0106] In some embodiments, the frequency input may be provided by a voltage controlled oscillator (VCO), although this is not required. The divider control input may be provided by the baseband circuit 604 or the application processor 602 according to the desired output frequency. In some embodiments, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by the application processor 602.

[0107] The synthesizer circuit 606d of the RF circuit 606 may include a frequency divider, a delay locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider may be a dual-mode frequency divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on a carry) to provide a fractional division ratio. In some example embodiments, the DLL may include a cascaded, tunable, delay element, a phase detector, a charge pump, and a set of D-type flip-flops. In these embodiments, the delay element may be configured to divide the VCO cycle into Nd equal phase groups, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0108] In some embodiments, the synthesizer circuit 606d can be configured to generate a carrier frequency as an output frequency, while in other embodiments, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used with a quadrature generator and divider circuit to generate multiple signals with multiple different phases relative to each other at the carrier frequency. In some embodiments, the output frequency can be the LO frequency (fLO). In some embodiments, the RF circuit 606 can include an IQ / polarity converter.

[0109] The FEM circuitry 608 may include a receive signal path that may include circuitry configured to operate on RF signals received from one or more antennas 610, amplify the received signals, and provide an amplified version of the received signals to the RF circuitry 606 for further processing. The FEM circuitry 608 may also include a transmit signal path that may include circuitry configured to amplify transmit signals provided by the RF circuitry 606 for transmission through one or more of the one or more antennas 610. In various embodiments, amplification by either the transmit signal path or the receive signal path may be accomplished only in the RF circuitry 606, only in the FEM 608, or in both the RF circuitry 606 and the FEM 608.

[0110] In some embodiments, the FEM circuit 608 may include a TX / RX switch to switch between transmit mode and receive mode operation. The FEM circuit 608 may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit 608 may include a low noise amplifier (LNA) to amplify the received RF signal and provide the amplified received RF signal as an output (e.g., provided to the RF circuit 606). The transmit signal path of the FEM circuit 608 may include a power amplifier (PA) for amplifying an input RF signal (e.g., provided by the RF circuit 606); and one or more filters for generating an RF signal for subsequent transmission (e.g., through one or more of the one or more antennas 610).

[0111] In some embodiments, PMC 612 can manage the power provided to baseband circuit 604. Specifically, PMC 612 can control power selection, voltage scaling, battery charging, or DC-DC conversion. When device 600 is capable of being powered by a battery, for example, when the device is included in a UE, PMC 612 can generally be included. PMC 612 can improve power conversion efficiency while providing the desired specific implementation size and heat dissipation characteristics.

[0112] Figure 6PMC 612 is shown coupled only to baseband circuit 604. However, in other embodiments, PMC 612 may additionally or alternatively be coupled to other components (such as, but not limited to, application circuit 602, RF circuit 606, or FEM 608) and perform similar power management operations.

[0113] In some embodiments, the PMC 612 may control or otherwise be part of various power saving mechanisms of the device 600. For example, if the device 600 is in the RRC_Connected state, where the device is still connected to the RAN node because it expects to receive traffic immediately, then after a period of inactivity, the device may enter a state known as discontinuous reception mode (DRX). During this state, the device 600 may be powered off for short time intervals, thereby saving power.

[0114] If there is no data traffic activity for an extended period of time, the device 600 may transition to the RRC_Idle state, in which the device is disconnected from the network and does not perform operations such as channel quality feedback, handover, etc. The device 600 enters a very low power state and performs paging, in which the device periodically wakes up again to listen to the network and then powers down again. The device 600 cannot receive data in this state, and in order to receive data, it must transition back to the RRC_Connected state.

[0115] An additional power saving mode can keep a device from using the network for longer than the paging interval (which can range from a few seconds to several hours). During this time, the device is completely unable to connect to the network and can be completely powered down. Any data sent during this time will be significantly delayed, and it is assumed that the delay is acceptable.

[0116] The processor of the application circuit 602 and the processor of the baseband circuit 604 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of the baseband circuit 604 can be used alone or in combination to perform layer 3, layer 2, or layer 1 functions, while the processor of the application circuit 602 can utilize data received from these layers (e.g., packet data) and further perform layer 4 functions (e.g., transport communication protocol (TCP) and user datagram protocol (UDP) layers). As mentioned herein, layer 3 may include a radio resource control (RRC) layer, which will be described in further detail below. As mentioned herein, layer 2 may include a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, which will be described in further detail below. As mentioned herein, layer 1 may include a physical (PHY) layer of a UE / RAN node, which will be described in further detail below.

[0117] Figure 7An exemplary interface of a baseband circuit according to some embodiments is shown. As described above, Figure 6 The baseband circuit 604 may include processors 604A-604E and a memory 604G used by the processors. Each of the processors 604A-604E may include a memory interface 704A-704E for sending / receiving data to / from the memory 604G, respectively.

[0118] The baseband circuit 604 may also include: one or more interfaces to communicatively couple to other circuits / devices, such as a memory interface 712 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 604); an application circuit interface 714 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 604); Figure 6 RF circuit interface 716 (for example, for sending / receiving data to / from the application circuit 602); Figure 6 an interface for sending / receiving data to / from a RF circuit 606); a wireless hardware connection interface 718 (e.g., for sending / receiving data to / from a near field communication (NFC) component, Components (e.g. Low power consumption), components and other communication components to send / receive data); and a power management interface 720 (eg, an interface for sending / receiving power or control signals to / from PMC 612).

[0119] Figure 8 is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and capable of performing any one or more of the methods discussed herein, according to some exemplary embodiments. Specifically, Figure 8 A schematic diagram of hardware resources 800 is shown, including one or more processors (or processor cores) 810, one or more memory / storage devices 820, and one or more communication resources 830, each of which may be communicatively coupled via a bus 840. For embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 802 may be executed to provide an execution environment for one or more network slices / sub-slices to utilize hardware resources 800.

[0120] Processor 810 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) (such as a baseband processor), an application specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, processor 812 and processor 814.

[0121] The memory / storage device 820 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 820 may include, but is not limited to, any type of volatile or non-volatile memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage, etc.

[0122] The communication resources 830 may include an interconnect or network interface component or other suitable device to communicate with one or more peripheral devices 804 or one or more databases 806 via the network 808. For example, the communication resources 830 may include a wired communication component (e.g., for coupling via a universal serial bus (USB)), a cellular communication component, an NFC component, Components (e.g. Low power consumption), components and other communication components.

[0123] The instructions 850 may include software, programs, applications, applet, applications, or other executable code for causing at least any one of the processors 810 to perform any one or more of the methods discussed herein. The instructions 850 may reside completely or partially in at least one of the processors 810 (e.g., in a cache memory of the processor), the memory / storage device 820, or any suitable combination thereof. In addition, any portion of the instructions 850 may be transmitted to the hardware resources 800 from any combination of the peripheral device 804 or the database 806. Therefore, the memory of the processor 810, the memory / storage device 820, the peripheral device 804, and the database 806 are examples of computer-readable media and machine-readable media.

[0124] In various embodiments, Figures 5 to 8 Equipment / components, especially Figure 7 The baseband circuit can be used to practice all or part of Figures 1 to 3 Any of the depicted operational flows / algorithm structures.

[0125] Figure 1An example of an operational flow / algorithm structure that may be performed by a next generation Node B (gNB) according to some embodiments is depicted in . In this example, the operational flow / algorithm structure 100 may include retrieving configuration information from a memory at 105 that a user equipment (UE) will use to perform periodic channel state information-reference signal (CSI-RS) reception, wherein the configuration information includes a synchronization signal-physical broadcast channel (ss-PBCH) block power parameter and a synchronization signal power control offset (powerControlOffsetSS) parameter. The operational flow / algorithm structure 100 may also include generating a message including the configuration information at 110. The operational flow / algorithm structure 100 may also include encoding the message at 115 for transmission to the UE.

[0126] Figure 2 Another example of an operational flow / algorithm structure that may be performed by a UE according to some embodiments is depicted in . In this example, the operational flow / algorithm structure 200 may include receiving a configuration message at 205, the configuration message including a synchronization signal-physical broadcast channel (ss-PBCH) block power parameter and a synchronization signal power control offset (powerControlOffsetSS) parameter. The operational flow / algorithm structure 200 may also include determining a power level for a physical random access channel (PRACH) transmission based on the configuration message at 210. The operational flow / algorithm structure 200 may also include performing a PRACH transmission based on the determined power level at 215.

[0127] Figure 3 Another example of an operational flow / algorithm structure that may be performed by a gNB according to some embodiments is depicted in . In this example, the operational flow / algorithm structure 300 may include generating a configuration message including the following configuration information at 305, the configuration information including: a synchronization signal-physical broadcast channel (ss-PBCH) block power parameter and a synchronization signal power control offset (powerControlOffsetSS) parameter. The operational flow / algorithm structure 300 may also include encoding the configuration message at 310 for transmission to the UE.

[0128] Example 21 may include an apparatus comprising means for performing one or more elements of the methods or processes described herein.

[0129] Embodiment 22 may include one or more non-transitory computer-readable media that include instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of the methods or processes described herein.

[0130] Embodiment 23 may include an apparatus comprising logic components, modules, and / or circuits for performing one or more elements of a method or methods related to any of the methods or processes described herein.

[0131] Embodiment 26 may include a method of communicating in a wireless network as shown and described herein.

[0132] Embodiment 27 may include a system for providing wireless communications as shown and described herein.

[0133] Embodiment 28 may include an apparatus for providing wireless communications as shown and described herein.

[0134] The description of the specific implementations shown herein, including the specific implementations described in the Abstract, is not intended to be exhaustive or to limit the disclosure to the precise form disclosed. Although specific implementations and examples are described herein for illustrative purposes, various alternative or equivalent embodiments or implementations calculated to achieve the same purpose can be made based on the above detailed description without departing from the scope of the present disclosure.

Claims

1. A device, comprising: A memory storing configuration information to be used by a user equipment UE to perform periodic channel state information-reference signal CSI-RS reception, wherein the configuration information includes a block power parameter and a power control offset parameter; as well as A processor is coupled to the memory, the processor being configured to: retrieving the configuration information from the memory; generating a message including the configuration information; as well as encoding the message for transmission to the UE, The configuration information enables the UE to determine the reference signal power referenceSignalPower transmitted through the physical random access channel PRACH based on the block power parameter or based on the block power parameter and the power control offset parameter according to the configuration of the downlink control information DCI or the CSI-RS.

2. The apparatus of claim 1, wherein the power control offset parameter provides an offset of a transmission power of a tracking reference signal (TRS) relative to a synchronization signal / physical broadcast channel (SS) / PBCH block transmission power.

3. The apparatus of claim 1, wherein the TRS is a CSI-RS in a non-zero power NZP CSI-RS resource set configured with a TRS-Info parameter.

4. The apparatus of claim 1, wherein the power control offset parameter provides an offset of a beam management reference signal (BMRS) relative to a synchronization signal / physical broadcast channel (SS) / PBCH block transmission power. 5 . The apparatus according to claim 4 , wherein the BMRS is a CSI-RS in a non-zero power NZP CSI-RS resource set configured with a higher layer parameter repetition.

6. The apparatus according to any one of claims 1 to 5, wherein the CSI-RS is quasi co-located (QLD-ed) with a synchronization signal block (SSB), and wherein the block power parameter indicates the reference signal power.

7. An apparatus according to any one of claims 1 to 5, wherein the CSI-RS is not quasi-co-located (QLD-ed) with a synchronization signal block (SSB), and wherein the power control offset parameter provides an offset of the CSI-RS transmission power relative to the synchronization signal / physical broadcast channel (SS) / PBCH block transmission power indicated by the ss-PBCH block power parameter.

8. A method comprising: Receiving, by a user equipment UE, a configuration message including a block power parameter and a power control offset parameter; Based on the configuration message, determine a power level for physical random access channel PRACH transmission based on the block power parameter or based on the block power parameter and the power control offset parameter according to the configuration of downlink control information DCI or channel state information-reference signal CSI-RS; as well as The PRACH transmission is performed based on the determined power level.

9. The method of claim 8, wherein the UE is configured for periodic CSI-RS reception.

10. The method of claim 8, wherein when the CSI-RS for tracking is configured for quasi-co-site QCL information 1, the power control offset parameter provides an offset of the transmission power of the tracking reference signal TRS relative to the transmission power of the synchronization signal / physical broadcast channel SS / PBCH block. 11 . The method according to claim 10 , wherein the TRS is a CSI-RS in a non-zero power NZP CSI-RS resource set configured with a TRS-Info parameter.

12. The method of claim 8, wherein when the CSI-RS for tracking is configured for quasi-co-site QCL information 2, the power control offset parameter provides an offset of a beam management reference signal BMRS relative to a synchronization signal / physical broadcast channel SS / PBCH block transmission power.

13. The method according to claim 12, wherein the BMRS is a CSI-RS in a non-zero power NZP CSI-RS resource set configured with a higher layer parameter repetition.

14. The method of claim 8, wherein the CSI-RS is quasi co-located (QCL-ed) with a synchronization signal block (SSB), and wherein the block power parameter indicates a reference signal power.

15. The method of claim 8, wherein the CSI-RS is not quasi-co-located (QCL-ed) with a synchronization signal block (SSB), and wherein the power control offset parameter provides an offset of the CSI-RS transmission power relative to a synchronization signal / physical broadcast channel (SS) / PBCH block transmission power indicated by the block power parameter.

16. A method comprising: generating, by the base station, a configuration message including configuration information, the configuration information including: a block power parameter and a power control offset parameter; and encoding the configuration message for transmission to a user equipment UE, The configuration information enables the UE to determine the reference signal power referenceSignalPower transmitted through the physical random access channel PRACH based on the block power parameter or based on the block power parameter and the power control offset parameter according to the configuration of the downlink control information DCI or the channel state information-reference signal CSI-RS.

17. The method of claim 16, wherein the power control offset parameter provides an offset of the transmission power of a tracking reference signal (TRS) relative to the transmission power of a synchronization signal / physical broadcast channel (SS) / PBCH block, and wherein the TRS is a CSI-RS in a non-zero power NZP CSI-RS resource set configured with a TRS-Info parameter.

18. The method of claim 16, wherein the power control offset parameter provides an offset of a beam management reference signal BMRS relative to a synchronization signal / physical broadcast channel SS / PBCH block transmission power, and wherein the BMRS is a CSI-RS in a non-zero power NZP CSI-RS resource set configured with a higher layer parameter repetition.

19. The method of claim 16, wherein the CSI-RS is quasi co-located (QLD-ed) with a synchronization signal block (SSB), and wherein the block power parameter indicates the reference signal power.

20. The method of claim 16, wherein the CSI-RS is not quasi-co-located (QCL-ed) with a synchronization signal block (SSB), and wherein the power control offset parameter provides an offset of the CSI-RS transmission power relative to a synchronization signal / physical broadcast channel (SS) / PBCH block transmission power indicated by the block power parameter.