Apparatus and method for enhancing beam recovery

Abstract

Some embodiments of the present disclosure include systems, devices, methods, and computer-readable media for use in wireless networks to facilitate a beam failure recovery process. Some embodiments relate to a method that includes detecting a beam failure instance. The method also includes initiating a beam failure recovery process by dynamically activating or deactivating a candidate beam for each uplink bandwidth part (BWP) associated with a user equipment (UE). In addition, the method also includes generating a control signal to identify one or more activated or deactivated candidate beams for at least one BWP associated with the UE. The method also includes transmitting the control signal to the UE.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Application No. 62 / 804,000, filed on February 11, 2019, under 35 U.S.C. §119(e), the entire contents of which are incorporated herein by reference. Technical Field

[0003] Various embodiments may generally relate to the field of wireless communications. Summary of the invention

[0004] Certain embodiments of the present disclosure include systems, apparatuses, methods, and computer-readable media for use in a wireless network to configure operation of a base station (BS) and a user equipment (UE).

[0005] Some embodiments relate to a method that includes detecting a beam failure instance. The method also includes initiating a beam failure recovery procedure by activating or deactivating a candidate beam for at least one uplink bandwidth part (BWP) associated with a user equipment (UE). In addition, the method also includes generating a control signal to identify one or more activated or deactivated candidate beams for at least one BWP associated with the UE. The method also includes transmitting the control signal to the UE.

[0006] Some embodiments relate to an apparatus (e.g., a network apparatus, a base station, an eNB, etc.) comprising a radio front-end circuit and a processor circuit coupled to the radio front-end circuit and configured to detect a beam failure instance. The processor circuit may be further configured to initiate a beam failure recovery process by activating or deactivating a candidate beam for at least one uplink bandwidth part (BWP) associated with a user equipment (UE). According to some embodiments, the processor circuit may be further configured to generate a control signal to identify one or more activated or deactivated candidate beams for at least one BWP associated with the UE. The processor circuit may be further configured to transmit the control signal to the UE using the radio front-end circuit.

[0007] Some embodiments relate to a non-transitory computer-readable medium, which includes instructions that, when executed by one or more processors of a device, cause the device to perform one or more operations, including detecting a beam failure instance. The operations also include initiating a beam failure recovery process by activating or deactivating a candidate beam for at least one uplink bandwidth part (BWP) associated with a user equipment (UE). According to some embodiments, the operations also include generating a control signal to identify one or more activated or deactivated candidate beams for at least one BWP associated with the UE. In addition, the operations also include transmitting the control signal to the UE.

[0008] In an embodiment, the control signal may be one of a medium access (MAC) control element (CE) or a physical random access channel (PRACH) information element (IE).

[0009] In an embodiment, when the control signal is a MAC CE, one or more candidate beams for activation or deactivation may be identified in a media access control (MAC) protocol data unit (PDU) subheader with a new logical channel ID (LCID) in the MAC CE.

[0010] In an embodiment, when the control signal is a PRACH IE, the cell-specific candidate beam subset may be identified in the PRACH IE by including an index associated with the candidate beam subset in the cell-specific uplink configuration message. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Figure 1 shows MAC CE activation / deactivation of candidate beams for BFR according to some embodiments;

[0012] Figure 2 shows a measurement model according to some embodiments;

[0013] Figure 3 Describing the architecture of a system of networks according to some embodiments;

[0014] Figure 4 depicts an architecture of a system including a first core network according to some embodiments;

[0015] Figure 5 depicts an architecture of a system including a second core network according to some embodiments;

[0016] Figure 6 depicts examples of infrastructure equipment according to various embodiments;

[0017] Figure 7Depicting exemplary components of a computer platform according to various embodiments;

[0018] Figure 8 depicts exemplary components of baseband circuitry and radio frequency circuitry according to various embodiments;

[0019] Fig. 9 is an illustration of various protocol functions that may be used in various protocol stacks according to various embodiments;

[0020] Fig.10 illustrates components of a core network according to various embodiments;

[0021] Fig.11 A flowchart illustrating a beam failure recovery method according to some embodiments is shown; and

[0022] Fig.12 A flow chart of a beam failure recovery method according to some embodiments is shown. DETAILED DESCRIPTION

[0023] The following specific embodiments relate to the accompanying drawings. The same figure numbers may be used to identify the same or similar elements in different drawings. In the following description, for the purpose of illustration and not limitation, specific details, such as specific structures, architectures, interfaces, technologies, etc., are set forth to provide a thorough understanding of various aspects of various embodiments. However, it will be apparent to those skilled in the art who benefit from the present disclosure that various aspects of various embodiments 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 that the description of various embodiments will not be obscured by unnecessary details. For the purposes of this document, the phrase "A or B" refers to (A), (B), or (A and B).

[0024] Beam Failure Recovery (BFR) is specified in New Radio (NR) Release 15. The main concept is that the UE (e.g. Figure 3 UE 301) detects a next generation Node B (gNB) (e.g., Figure 3The beam at the RAN node 311) and / or the UE has been misaligned, and therefore the network (NW) may not be able to reach the UE. In this case, the UE searches for a new reference signal (RS) in the candidate beams configured by the RRC for the BFR process, which meets a certain criterion (e.g., requiring the RSRP of the new beam to exceed the RSRP threshold signaled). If such an RS is found, the UE uses the RS as a quasi-co-located (QCLed) RS to perform contention-free random access to the cell (via a random access preamble associated with the selected beam reference signal) or contention-based random access. The NW then proceeds to reconfigure the transmission configuration indication (TCI) state of the control channel resource set (CORESET) by transmitting the corresponding MACCE scheduled by the control channel in the configured beam failure recovery search space to the UE, so that the beam failure recovery is completed. This process is also called link recovery.

[0025] While link failure recovery is much faster than RRC re-establishment after a radio link failure, the process may not be extremely fast when the UE moves out of coverage, which will take about 150ms before the UE has completed a successful link recovery. Note that multiple candidate beams are configured by RRC signaling for beam failure recovery. Since this set of candidate beams can only be (re)configured by RRC signaling, if all candidate beams do not provide a good enough link quality, the UE needs to perform a normal contention-based random access followed by an RRC re-establishment procedure. This is naturally a time-consuming process. In order to achieve fast link recovery, it would be beneficial to enable the gNB to update this set of candidate beams more dynamically to always incorporate those strong beams into the candidate set.

[0026] The present disclosure provides an implementation scheme that enables a gNB to dynamically reconfigure a candidate beam set so that whenever a beam failure is detected, the UE can find a candidate beam through which a fast link recovery can be achieved. The first implementation scheme (implementation scheme-1) involves an RRC signaling candidate beam set for BFR for each serving cell. In this implementation scheme, a physical random access channel (PRACH) resource configuration for BFR can be configured based on the serving cell, which is defined as PRACH-ResourceConfigBFR. For each uplink BWP, a cell-specific candidate beam subset can be configured for BFR by including the index of the candidate beam from the candidate beam set in the cell-specific UplinkConfig. The second implementation scheme (implementation scheme-2) involves MAC CE activation / deactivation of candidate beams for BFR for each uplink BWP. In this implementation scheme, MAC CE is proposed to dynamically activate / deactivate candidate beams for BFR for each uplink BWP. According to some implementation schemes, the network can activate / deactivate candidate beams for BFR for UEs in a specific BWP by sending the proposed MAC CE to the UE. The implementation scheme of this paper implements dynamic activation / deactivation of UE's BFR candidate beams based on BWP. In addition, cell-specific BFR PRACH resource configuration can further reduce signaling overhead.

[0027] Implementation 1: RRC signaling candidate beam set for BFR per serving cell

[0028] The BeamFailureRecoveryConfig IE is used to configure RACH resources and candidate beams for the UE for beam failure recovery in case of beam failure detection. Table 1 shows an exemplary BeamFailureRecoveryConfig IE, and Table 2 shows the field description of BeamFailureRecoveryConfig.

[0029] Table 1: BeamFailureRecoveryConfig information elements

[0030]

[0031] Table 2: BeamFailureRecoveryConfig field description

[0032]

[0033]

[0034] In the first implementation, the PRACH resource configuration for BFR may be configured based on the serving cell, which is defined as PRACH-ResourceConfigBFR IE. Table 3 shows an exemplary RRC configuration that may be used to implement this function.

[0035] Table 3

[0036]

[0037] In various embodiments, the set of candidate beams for BFR (i.e., candidateBeamsBFR-ToAddModList) will be included in the UplinkConfig configured by each serving cell ServingCellConfig (see, for example, Tables 5 and 6 below). The parameter maxNrofCandidateBeamsPerServingCell defines the maximum number of candidate beams for BFR per serving cell and can be set to 128 as an example. Invalid candidate beams for BFR to be removed (which are identified by the resourceId of each PRACH-ResourceDedicatedBFR) should be added to the list candidateBeamsBFR-ToReleaseList. The resourceId of PRACH-ResourceDedicatedBFR should be uniquely ordered across the entire serving cell. Therefore, all valid candidate beams for BFR are configured in a serving cell-specific manner. For each uplink BWP, a cell-specific subset of candidate beams can be configured for BFR, as shown in Table 4.

[0038] Table 4

[0039]

[0040] According to some embodiments, the BeamFailureRecoveryConfig is configured according to the uplink BWP. The candidateBeamRSList can be configured to include the index of the candidate beams from the candidate beam set in the cell-specific UplinkConfig, rather than consisting of BFR beam RS resources. This will reduce the signaling overhead.

[0041] According to some embodiments, the ServingCellConfig IE is used to configure (add or modify) a serving cell for the UE, which may be a SpCell or SCell of an MCG or SCG. The parameters herein are primarily UE-specific, but are also partially cell-specific (e.g., in an additionally configured bandwidth portion). Table 5 shows an exemplary ServingCellConfig IE, and Table 6 shows a field description of the ServingCellConfig IE.

[0042] Table 5: ServingCellConfig information elements

[0043]

[0044]

[0045] Table 6: ServingCellConfig field description

[0046]

[0047]

[0048]

[0049]

[0050] Implementation-2: MAC CE activation / deactivation of candidate beams for BFR per uplink BWP

[0051] In this embodiment, the MAC CE is used to dynamically activate / deactivate the candidate beams for BFR for each uplink BWP. An exemplary MAC CE consists of Figure 1 Shown.

[0052] The BFR candidate beam activation / deactivation for BWP-specific MAC CE may be identified by a MAC PDU subheader with a new LCID (e.g., a new LCID index value for UL-SCH and / or DL-SCH). It has a variable size and includes the following fields:

[0053] -Serving Cell ID: This field indicates the identity of the serving cell to which the MAC CE applies. The length of this field is 5 bits;

[0054] -BWP ID: This field indicates the UL BWP to which the MAC CE applies as the code point of the DCI bandwidth partindicator field, as specified below. The length of the BWP ID field is 2 bits;

[0055] -T i : If PRACH-ResourceDedicatedBFR with resourceId i is configured in candidateBeamsBFR-ToAddModList in UplinkConfig, this field indicates the activation / deactivation status of PRACH-ResourceDedicatedBFR with resourceId i. Otherwise, the MAC entity shall ignore this T i Field. i The field is set to '1' to indicate that the PRACH-ResourceDedicatedBFR with resourceId i should be activated. i The field is set to "0" to indicate that the PRACH-ResourceDedicatedBFR with resourceId i should be deactivated. The maximum number of activated PRACH-ResourceDedicatedBFRs can be 16;

[0056] -R: Reserved bit, set to "0".

[0057] In various implementations, the MAC subheader may include some or all of the following fields:

[0058] -LCID: The "Logical Channel ID" field identifies the logical channel instance of the corresponding MAC SDU or the type of the corresponding MAC CE or the padding of DL-SCH and UL-SCH respectively. Each MAC subheader has one LCID field. The LCID field size is 6 bits;

[0059] -L: The "Length" field indicates the length in bytes of the corresponding MAC SDU or variable-size MAC CE. Each MAC subheader has an L field, except for the subheaders corresponding to fixed-size MAC CEs, padding, and MAC SDUs containing UL CCCH. The size of the L field is indicated by the F field;

[0060] -F: This "Format" field indicates the size of the length field. Each MAC subheader has an F field, except for the subheaders corresponding to fixed-size MAC CEs, padding, and MAC SDUs containing UL CCCH. The size of the F field is 1 bit. A value of 0 indicates 8 bits of the length field. A value of 1 indicates 16 bits of the length field;

[0061] -R: Reserved bit, set to "0".

[0062] According to the second implementation, the network can activate / deactivate the candidate beams for the BFR of the UE in a specific BWP by sending the above-mentioned MAC CE to the UE. After the UE sends a HARQ-ACK to the network to confirm the PDSCH carrying the MAC CE, the new activated candidate beam set becomes valid at x time slots.

[0063] According to some embodiments, the BWP ID field indicates the UL BWP to which the MAC CE applies as the code point of the DCI bandwidth partindicator field. The DCI bandwidth part indicator field may be included in DCI format 0_1 ​​or DCI format 1_1. DCI format 0_1 ​​is used to schedule PUSCH in one cell, and DCI format 1_1 is used to schedule PDSCH in one cell. The DCI bandwidth part indicator field included in DCI format 0_1 ​​may be 0, 1, or 2 bits, such as the number of UL BWPs n configured by higher layers. BWP,RRC The DCI bandwidth part indicator field included in DCI format 1_1 may be 0, 1, or 2 bits, such as the number of DLBWPs n configured by the higher layer. BWP,RRC The bit width of this field is determined as follows, excluding the initial DL bandwidth part. In DCI format 0_1 ​​and / or DCI format 1_1, the bit width of this field is determined as bits, where if n BWP,RRC ≤3, then n BWP =n BWP,RRC +1, in which case the bandwidth part indicator is equal to the ascending order of the higher layer parameter BWP-Id; otherwise, n BWP =n BWP,RRC , in which case the bandwidth part indicator is defined in Table 7. If the UE does not support active BWP change via DCI, the UE ignores the bandwidth part indicator field.

[0064] Table 7: Bandwidth fraction indicators

[0065]

[0066]

[0067] Beam management

[0068] Beam management refers to a set of L1 / L2 processes that acquire and maintain a set of transmit / receive points (TRP or TRxP) and / or UE beams that can be used for DL ​​and 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 Tx / 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 an operation covering a spatial area in which beams are transmitted and / or received during time intervals in a predetermined manner.

[0069] If at least one of the following conditions is met, the Tx / Rx beam correspondence at TRxP is established: TRxP can be based on the UE (for example, Figure 3 301) determines the TRxP Rx beam for uplink reception based on downlink measurement of one or more Tx beams of TRxP by UE; and TRxP is capable of determining the TRxP Tx beam for downlink transmission based on uplink measurement of one or more Rx beams of TRxP by TRxP. The Tx / Rx beam correspondence at the UE is established if at least one of the following is satisfied: the UE is capable of determining the UE Tx beam for uplink transmission based on downlink measurement of one or more Rx beams of the UE by UE; the UE is capable of determining the UE Rx beam for downlink reception based on the indication of TRxP (based on uplink measurement on one or more Tx beams of the UE); and the capability indication of the information related to the UE beam correspondence of TRxP is supported.

[0070] In some implementations, 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 TRxP Tx beams / UE Rx beams. For beamforming at TRxP, process P-1 typically includes intra-TRxP / inter-TRxP Tx beam scanning from different beam sets. For beamforming at UE, process P-1 typically includes UE Rx beam scanning from different beam sets.

[0071] Procedure P-2 is used to implement UE measurements on different TRxP Tx beams, which may change the inter-TRxP / intra-TRxP Tx beams. Procedure P-2 can be a special case of Procedure P-1, where Procedure P-2 is used for a potentially smaller set of beams for beam refinement than Procedure P-1. Procedure 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. Procedures P-1, P-2, and P-3 can be used for aperiodic beam reporting.

[0072] UE measurements based on RSs (at least CSI-RS) for beam management consist 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). RS-based procedures 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 with the beam information. When the UE is configured with K' > 1 NZP CSI-RS resources, the UE may report N' CRIs.

[0073] For beam failure detection, the gNB configures a beam failure detection reference signal for the UE, and when the number of beam failure instances indicated from the physical layer reaches the configured threshold within the configured period, the UE declares that a beam failure exists. After detecting a beam failure, the UE triggers beam failure recovery by initiating a "random access" procedure on the Pcell and selects a suitable beam to perform beam failure recovery (if the gNB has provided dedicated "random access" resources for some beams, the UE will prioritize them). When the "random access" procedure is completed, the beam failure recovery is considered complete.

[0074] The mechanism that triggers beam failure recovery is referred to as "beam recovery", "beam failure recovery request procedure", etc. A beam failure event may occur when the quality of the beam pair link of the associated control channel drops below a threshold, when the timeout of the associated timer occurs, etc. When a beam failure occurs, the beam recovery mechanism is triggered. The network can explicitly configure resources for UL transmission of signals for the UE for recovery purposes. The configuration of resources is supported in the case where the base station (e.g., TRP, gNB, etc.) listens from all or some directions (e.g., random access area). The UL transmission / resources for reporting beam failure can 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 (capable of being configured for the UE). The transmission of DL signals is supported to allow the UE to monitor beams for identifying new potential beams.

[0075] If one, multiple or all serving PDCCH beams are faulty, 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 a serving gNB (or TRP) for a new SSB or CSI-RS. A beam failure may be detected by lower layers and indicated to the UE's medium access control (MAC) entity.

[0076] Beam management also 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 the QCL. The same or different beams on the control channel and the corresponding data channel transmissions may be supported. The DL beam indication is based on the transmission configuration indication (TCI) state. The TCI state is indicated in the TCI list configured by the radio resource control (RRC) and / or medium access control (MAC) control element (CE).

[0077] When the collection The radio link quality on all configured RS resources in out_LR When the beam failure instance is poor, the UE's layer 1 shall send a beam failure instance indication for the cell to higher layers. The layer 3 filter shall be applied to the beam failure instance indication. Two consecutive indications from layer 1 should be separated by at least T Indication_interval_BFD When DRX is not used, T Indication_interval_BFD is max(2ms,T BFD-RS,M ), where T BFD-RS,M A collection of access cells The shortest period of all configured RS resources in The RS resource in is SSB, then it corresponds to T SSB , or if the set The RS resource in is CSI-RS, which corresponds to T CSI-RS When using DRX, if DRX cycle_length is less than or equal to 320ms, then T Indication_interval_BFD is max(1.5*DRX_cycle_length,1.5*T BFD-RS,M ), and if DRX cycle_length is greater than 320ms, T Indication_interval It is DRX_cycle_length.

[0078] The beam failure recovery request may be delivered via dedicated PRACH or PUCCH resources. If the random access procedure is initialized for beam failure recovery and if contention-free random access resources and contention-free PRACH opportunities for beam failure recovery requests associated with either SSB and / or CSI-RS are configured, the UE is able to select a random access preamble corresponding to a selected SSB with an SS-RSRP higher than rsrp-ThresholdSSB in the associated SSB or a selected CSI-RS with a CSI-RSRP higher than cfra-csirs-DedicatedRACH-Threshold in the associated CSI-RS, and and be able to transmit a random access preamble on the next available PRACH opportunity, the next available PRACH opportunity being from the PRACH opportunity corresponding to the selected SSB allowed by the restriction given by ra-ssb-OccasionMaskIndex (if configured), or from the PRACH opportunity in the ra-OccasionList corresponding to the selected CSI-RS, and the PRACH opportunity shall be randomly selected with equal probability from the PRACH opportunity associated with the selected SSB or the PRACH opportunity associated with the selected CSI-RS occurring simultaneously but on different subcarriers. If a contention-free random access preamble for a beam failure recovery request is transmitted and if a PDCCH addressed to the UE's C-RNTI is received, the UE may stop monitoring for a random access response.

[0079] Beam Measurement

[0080] A UE in RRC_CONNECTED mode measures one or more beams of a cell and averages the measurements (e.g., power values) to derive cell quality. In doing so, the UE is configured to consider a subset of detected beams, such as the N best beams above an absolute threshold. Filtering occurs at the physical layer to derive beam quality and then at the RRC level to derive cell quality from multiple beams. Cell quality from beam measurements is derived in the same way for serving and non-serving cells. If the UE is configured to do so by the gNB, the measurement report may contain measurements of the X best beams.

[0081] The UE derives cell measurements by measuring one or more beams associated with each cell as configured by the network. For all cell measurements in RRC_CONNECTED mode, the UE applies layer 3 filtering before using the measurement results to evaluate reporting criteria and measurement reports. For cell measurements, the network may configure RSRP, RSRQ, and / or SINR as triggering quantities. The reporting quantity may be the same as the triggering quantity or a combination of quantities (e.g., RSRP and RSRQ; RSRP and SINR; RSRQ and SINR; RSRP, RSRQ, and SINR).

[0082] The network may also configure the UE to report measurement information for each beam, which may be a measurement result for each beam with the corresponding beam identity or just the beam identity. If the beam measurement information is configured to be included in the measurement report, the UE applies layer 3 beam filtering. However, the exact layer 1 filtering of the beam measurements used to derive the cell measurement results depends on the specific implementation.

[0083] If the gNB configures the UE to do so, the measurement report contains the measurement results of the X best beams. For channel state estimation purposes, the UE can be configured to measure the 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.

[0084] Figure 2 An exemplary measurement model is shown. Figure 2 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 filtered by L1 to layer 3 (L3) beam filtering circuitry and beam consolidation / selection circuitry at point A. 1 Report to the Department.

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

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

[0087] 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).

[0088] 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 correspond to measurements on New Radio (NR) Synchronization Signal (SS) Block (SSB) resources or Channel State Information Reference Signal (CSI-RS) resources configured by the gNB for L3 mobility and detected by the UE at L1.

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

[0090] L1 filtering introduces a certain level of measurement averaging. The exact way and time at which the UE performs the required measurements is implementation specific to the point at which the output at B meets the predefined performance requirements. L3 filtering and related parameters for cell quality do not introduce any delay in sample availability between B and C. The measurement at point C 1 is the input used in event evaluation. The L3 beam filtering and related parameters do not introduce any delay in sample availability between E and F.

[0091] The measurement report includes a measurement identifier of the associated measurement configuration that triggered the report; the cell and beam measurement quantities to be included in the measurement report are configured by the network (e.g., using RRC signaling); the number of non-service cells to be reported can be limited by configuration made by the network; cells belonging to a blacklist configured by the network are not used for event evaluation and reporting, and conversely, when a whitelist is configured by the network, only cells belonging to the whitelist are used for event evaluation and reporting (in contrast), when a whitelist is configured by the network, only cells belonging to the whitelist are used for event evaluation and reporting; and the beam measurements to be included in the measurement report are configured by the network (only a beam identifier, measurement results and a beam identifier, or no beam report).

[0092] Intra-frequency neighbor (cell) measurement and inter-frequency neighbor (cell) measurement include SSB-based measurement and CSI-RS-based measurement.

[0093] For SSB-based measurements, one measurement object corresponds to one SSB, and the UE regards different SSBs as different cells. SSB-based intra-frequency measurement is defined as a measurement based on SSB-based intra-frequency measurement, provided that the center frequency of the SSB of the serving cell is the same as the center frequency of the SSB of the neighboring cell, and the subcarrier spacing of the two SSBs is also the same.

[0094] The SSB-based inter-frequency measurement is defined as a measurement based on the SSB, provided that the center frequency of the SSB of the serving cell and the center frequency of the SSB of the adjacent cell are different, or the subcarrier spacings of the two SSBs are different.

[0095] CSI-RS based intra-frequency measurement is defined as a measurement based on CSI-RS intra-frequency measurement, provided that the bandwidth of the CSI-RS resources on the neighboring cell configured for measurement is within the bandwidth of the CSI-RS resources on the serving cell configured for measurement, and the subcarrier spacing of the two CSI-RS resources is the same.

[0096] CSI-RS based inter-frequency measurement is defined as a measurement based on CSI-RS, provided that the bandwidth of the CSI-RS resources on the neighboring cell configured for measurement is not within the bandwidth of the CSI-RS resources on the serving cell configured for measurement, or the subcarrier spacing of the two CSI-RS resources is different.

[0097] Inter-frequency adjacent (cell) measurements include SSB-based inter-frequency measurements and CSI-RS-based inter-frequency measurements. SSB-based inter-frequency measurements are defined as SSB-based inter-frequency measurements, provided that the center frequency of the SSB of the serving cell and the center frequency of the SSB of the adjacent cell are different, or the subcarrier spacing of the two SSBs is different. For SSB-based measurements, one measurement object corresponds to one SSB, and the UE regards different SSBs as different cells. CSI-RS-based inter-frequency measurements are measurements defined as CSI-RS-based inter-frequency measurements, provided that the bandwidth of the CSI-RS resources on the adjacent cell configured for measurement is not within the bandwidth of the CSI-RS resources on the serving cell configured for measurement, or the subcarrier spacing of the two CSI-RS resources is different.

[0098] Whether a measurement is non-gap assisted or gap assisted depends on the capabilities of the UE, the active BWP of the UE and the current operating frequency. In a non-gap assisted scenario, the UE is able to perform such measurements without measurement gaps. In a gap assisted scenario, the UE cannot be assumed to be able to perform such measurements without measurement gaps.

[0099] Antenna port quasi-co-location

[0100] The UE may be configured with a list of up to M TCI-State configurations within the higher layer parameter PDSCH-Config to decode the PDSCH based on the detected PDCCH with DCI for the UE and a given serving cell, where M depends on the UE capabilities. Each TCI-State contains parameters for configuring the quasi-co-location relationship between one or two downlink reference signals of the PDSCH and the DM-RS ports. The quasi-co-location relationship is configured by the higher layer parameters qcl-Type1 for the first DL RS and qcl-Type2 for the second DL RS (if configured). 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 corresponding to each DL RS is given by the high-level parameter qcl-Type in QCL-Info, and can take one of the following values: QCL-TypeA: {Doppler shift, Doppler spread, average delay, average spread}; QCL-TypeB: {Doppler shift, Doppler spread}; QCL-TypeC: {average delay, Doppler shift}; QCL-TypeD: {spatial Rx parameters}.

[0101] The UE receives an activation command for mapping up to 8 TCI states to code points in the DCI field "Transmission Configuration Indication". When a HARQ-ACK corresponding to the PDSCH carrying the activation command is transmitted in time slot n, it shall Initially, the indicated mapping between TCI states and code points of the DCI field "TransmissionConfiguration Indication" applies. After the UE receives the higher-layer configuration of the TCI state and before receiving the activation command, the UE may assume that the DM-RS ports of the PDSCH of the serving cell are quasi-co-located with the SS / PBCH blocks determined during the initial access procedure with respect to "QCL-TypeA" and, when applicable, also with respect to "QCL-TypeD".

[0102] If the UE is configured with the higher layer parameter tci-PresentInDCI set to "enabled" for the CORESET scheduling PDSCH, the UE assumes that the TCI field is present in DCI format 1_1 for PDCCH transmitted on the CORESET. If tci-PresentInDCI is not configured for the CORESET scheduling PDSCH or the PDSCH is scheduled by DCI format 1_0, then for the purpose of determining PDSCH antenna port quasi co-location, the UE assumes that the TCI state of the PDSCH is the same as the TCI state applied to the CORESET for PDCCH transmission.

[0103] If tci-PresentInDCI is set to "enabled", when PDSCH is scheduled by DCI format 1_1, the UE shall use TCI-State according to the value of the "Transmission Configuration Indication" field in the detected PDCCH with DCI for determining PDSCH antenna port quasi co-location. If the time offset between the reception of the DL DCI and the corresponding PDSCH is equal to or greater than a threshold Threshold-Sched-Offset, where the threshold is based on the reported UE capabilities, the UE may assume that the DM-RS ports of the PDSCH of the serving cell are quasi-co-located with the RS in the TCI state relative to the QCL type parameter given by the indicated TCI state.

[0104] For both cases when tci-PresentInDCI is set to "enabled" and when tci-PresentInDCI is not configured, if the offset between the reception of DL DCI and the corresponding PDSCH is less than the threshold Threshold-Sched-Offset, the UE may assume that the DM-RS ports of the PDSCH of the serving cell are quasi-co-located with the RS in the TCI state relative to the QCL parameters indicated by the PDCCH quasi-co-location for the lowest CORESET-ID in the most recent slot in which one or more CORESETs within the active BWP of the serving cell are configured for the UE. If none of the configured TCI states contains "QCL-TypeD", the UE shall obtain other QCL assumptions from the indicated TCI state of its scheduled PDSCH, regardless of the time offset between the reception of DL DCI and the corresponding PDSCH.

[0105] For periodic CSI-RS resources in NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info, the UE shall expect the TCI-State to indicate one of the following quasi co-location types:

[0106] - "QCL-TypeC" with SS / PBCH blocks and, when applicable, "QCL-TypeD" with the same SS / PBCH blocks, or

[0107] - "QCL-TypeC" with SS / PBCH blocks and, when applicable, "QCL-TypeD" with CSI-RS resources in NZP-CSI-RS-ResourceSet configured with the higher layer parameter repetition, or

[0108] For non-periodic CSI-RS resources in NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info, the UE shall expect the TCI-State to indicate "QCL-TypeA" with the periodic CSI-RS resources in NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info, and, when applicable, "QCL-TypeD" with the same periodic CSI-RS resources.

[0109] For CSI-RS resources in NZP-CSI-RS-ResourceSet that are not configured with the higher layer parameter trs-Info and not configured with the higher layer parameter repetition, the UE shall expect the TCI-State to indicate one of the following quasi co-location types:

[0110] - "QCL-TypeA" with CSI-RS resources in NZP-CSI-RS-ResourceSet configured with higher layer parameter trs-Info, and "QCL-TypeD" with SS / PBCH blocks when applicable, or

[0111] - "QCL-TypeA" with CSI-RS resources in NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info, and, when applicable, "QCL-TypeD" with CSI-RS resources in NZP-CSI-RS-ResourceSet configured with the higher layer parameter repetition, or

[0112] - When "QCL-TypeD" is not applicable, "QCL-TypeB" with CSI-RS resources in NZP-CSI-RS-ResourceSet configured with higher layer parameter trs-Info.

[0113] For CSI-RS resources in NZP-CSI-RS-ResourceSet configured with the higher layer parameter repetition, the UE shall expect the TCI-State to indicate one of the following quasi co-location types:

[0114] - "QCL-TypeA" with CSI-RS resources in NZP-CSI-RS-ResourceSet configured with higher layer parameter trs-Info, and, when applicable, "QCL-TypeD" with the same CSI-RS resources, or

[0115] - "QCL-TypeA" with CSI-RS resources in NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info, and, when applicable, "QCL-TypeD" with CSI-RS resources in NZP-CSI-RS-ResourceSet configured with the higher layer parameter repetition, or

[0116] - "QCL-Type C" with SS / PBCH blocks, and when applicable, "QCL-Type D" with the same SS / PBCH blocks.

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

[0118] - "QCL-TypeA" with CSI-RS resources in NZP-CSI-RS-ResourceSet configured with higher layer parameter trs-Info, and, when applicable, "QCL-TypeD" with the same CSI-RS resources, or

[0119] - "QCL-TypeA" with CSI-RS resources in NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info, and, when applicable, "QCL-TypeD" with CSI-RS resources in NZP-CSI-RS-ResourceSet configured with the higher layer parameter repetition, or

[0120] - When "QCL-TypeD" is not applicable, "QCL-TypeA" with CSI-RS resources in NZP-CSI-RS-ResourceSet not configured with the higher layer parameter trs-Info and not configured with the higher layer parameter repetition.

[0121] For DM-RS of PDSCH, the UE shall expect the TCI-State to indicate one of the following quasi co-location types:

[0122] - "QCL-TypeA" with CSI-RS resources in NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info, and, when applicable, "QCL-TypeD" with the same CSI-RS resources, or

[0123] - "QCL-TypeA" with CSI-RS resources in NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info, and, when applicable, "QCL-TypeD" with CSI-RS resources in NZP-CSI-RS-ResourceSet configured with the higher layer parameter repetition, or

[0124] - "QCL-TypeA" with CSI-RS resources in NZP-CSI-RS-ResourceSet not configured with the higher layer parameter trs-Info and not configured with repetition, and when applicable, "QCL-TypeD" with the same CSI-RS resources.

[0125] Beam Failure Recovery Process

[0126] The UE is based on the set specified in this document The reference signals in the RF are used to evaluate the downlink quality of the serving cell in order to detect beam failure instances. The RS resources in the set can be periodic CSI-RS resources and / or SSBs. The UE does not need to perform beam failure detection outside the active DL BWP. On each RS resource in the UE, the UE estimates the radio link quality and compares it with the threshold Q out_LR A comparison is performed in order to access the downlink radio link quality of the serving cell.

[0127] Threshold Q out_LR is defined as the BLER at which the downlink radio level link cannot be reliably received and should correspond to an assumed PDCCH transmission out For SSB-based beam failure detection, Q is derived based on the assumed PDCCH transmission parameters listed in Table B.1-1. out_LR_SSB For CSI-RS based beam failure detection, Q is derived based on the assumed PDCCH transmission parameters listed in Table B.1-2. out_LR_CSI-RS .

[0128] Table B.1-1: PDCCH transmission parameters for beam failure case

[0129]

[0130] Table B.1-2: PDCCH transmission parameters for beam failure case

[0131]

[0132] The UE is based on the set specified in this document The reference signal in is used to perform L1-RSRP measurement in order to detect the candidate beams. The RS resources in the set may be periodic CSI-RS resources and / or SSBs. The UE does not need to perform candidate beam detection outside the active DL BWP. On each RS resource in the UE, the UE performs L1-RSRP measurement and compares it with the threshold Q in_LR The comparison is used to select a new beam for beam failure recovery. in_LR Corresponds to the value of the high-level parameter candidateBeamThreshold.

[0133] As previously implied, for the serving cell, a set of periodic CSI-RS resource configuration indices may be provided to the UE via the higher layer parameter failureDetectionResource. And the high-level parameter candidateBeamRSList for radio link quality measurement on the serving cell provides the UE with a set of periodic CSI-RS resource configuration indices and / or SS / PBCH block indices If the higher-layer parameter failureDetectionResource is not provided to the UE, the UE determines the set Includes periodic CSI-RS resource configuration indices that have the same value as the RS index in the RS set indicated by the higher layer parameter TCI-states of the corresponding control resource set used by the UE to monitor the PDCCH. UE expects the set includes up to two RS indices, and if two RS indices exist in the TCI state, the set The RS index with the QCL-TypeD configuration for the corresponding TCI state is included. The UE expects There is a single port RS in the. Threshold Q out,LR and Q in,LR Corresponding to the out The default value of the higher-level parameter rlmInSyncOutOfSyncThreshold and the value provided by the higher-level parameter rsrp-ThresholdSSB.

[0134] The physical layer in the UE is based on the threshold Q out,LR Resource configuration collection To evaluate the radio link quality. The UE evaluates the radio link quality based only on the periodic CSI-RS resource configuration or SS / PBCH blocks that are quasi-co-located with the DM-RS received by the PDCCH monitored by the UE. in,LRThe threshold is applied to the L1-RSRP measurement obtained from the SS / PBCH block. The UE sets Q in,LR The threshold is applied to the L1-RSRP measurement obtained for the CSI-RS resource.

[0135] When the UE uses the set of The radio link quality ratio threshold Q of all corresponding resource configurations in out,LR When the radio link quality is lower than the threshold Q out,LR When the quality of the radio link is poor, the physical layer notifies the higher layer of the set of The periodicity is determined by the maximum value between the shortest period in the periodic CSI-RS configuration or the SS / PBCH block and 2msec.

[0136] When requested by higher layers, the UE provides the higher layers with The periodic CSI-RS configuration index and / or SS / PBCH block index and the periodic CSI-RS configuration index and / or SS / PBCH block index greater than or equal to Q in,LR The corresponding L1-RSRP measurement of the threshold. When requested by the higher layer, the UE provides the higher layer with The periodic CSI-RS configuration index and / or SS / PBCH block index and the periodic CSI-RS configuration index and / or SS / PBCH block index greater than or equal to Q in,LR The threshold corresponds to the L1-RSRP measurement.

[0137] A control resource set may be provided to the UE via a link to a search space set provided by a higher layer parameter recoverySearchSpaceId for monitoring PDCCH in the control resource set. If the UE is provided with a higher layer parameter recoverySearchSpaceId, the UE does not expect to be provided with another search space set for monitoring PDCCH in the control resource set associated with the search space set provided by recoverySearchSpaceId.

[0138] The UE may receive the configuration for PRACH transmission via the higher layer parameter PRACH-ResourceDedicatedBFR. For PRACH transmission in time slot n and according to the same index q provided by the higher layer newThe associated periodic CSI-RS resource configuration or the antenna port quasi-co-location parameters associated with the SS / PBCH block, the UE monitors the PDCCH in the search space provided by the higher-layer parameter recoverySearchSpaceId for the timeslots within the window configured by the higher-layer parameter BeamFailureRecoveryConfig n+4 Starts detecting DCI formats with CRC scrambled by C-RNTI or MCS-C-RNTI. For PDCCH monitoring and corresponding PDSCH reception, the UE assumes that the same DCI format as the one with the same index q new The associated antenna port quasi-co-location parameters have the same antenna port quasi-co-location parameters until the UE receives activation of the TCI state or any of the parameters TCI-StatesPDCCH-ToAddlist and / or TCI-StatesPDCCH-ToReleaseList through the higher layer. After the UE detects a DCI format with a CRC scrambled by C-RNTI or MCS-C-RNTI in the search space set provided by recoverySearchSpaceId, the UE continues to monitor the PDCCH candidates in the search space set provided by recoverySearchSpaceld until the UE receives a MAC CE activation command for the TCI state or higher layer parameters TCI-StatesPDCCH-ToAddlist and / or TCI-StatesPDCCH-ToReleaseList.

[0139] If the MAC entity receives a beam failure indication from the lower layer, the MAC entity starts the beam failure recovery timer (beamFailureRecoveryTimer) and initiates a random access procedure. If the beamFailureRecoveryTimer expires, the MAC entity indicates to the upper layer that the beam failure recovery request failed. If a DL allocation 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 beamFailureRecoveryTimer and consider the beam failure recovery request procedure to be successfully completed.

[0140] For SSB-based beam failure detection, the UE evaluates the Evaluate_BFD_SSB [ms] The collection of estimates within the period Whether the downlink radio link quality on the configured SSB resources in T Evaluate_BFD_SSB [ms] Threshold Q within period out_LR_SSB Table B.2-1 defines T for FR1. Evaluate_BFD_SSBTable B.2-2 defines T for FR2 with N = 1. Evaluate_BFD_SSB , if the higher layer parameter failureDetectionResource is not provided to the UE and the UE is provided by the higher layer parameter TCI-state for PDCCH SSB with QCL-TypeD, or if the SSB configured for BFD is QCL-TypeD with DM-RS for PDCCH and the QCL association is known to the UE, or if the SSB configured for BFD is QCL-TypeD and is time division multiplexed (TDMed) to a CSI-RS resource configured for L1-RSRP reporting and the QCL association is known to the UE and CSI reporting with L1-RSRP measurement for the SSB configured for BFD has been performed within [TBD] ms.

[0141] For FR1, P = 1 / (1-T SSB / MGRP), in this case, in the monitored cell, there are measurement gaps configured for intra-frequency measurement, inter-frequency measurement or inter-RAT measurement, which overlap with some but not all opportunities of SSB; and P=1, in this case, in the monitored cell, there are no measurement gaps overlapping with any opportunity of SSB.

[0142] For FR2, P = 1 / (1-T SSB / T SMTCperiod ), at which time BFD-RS does not overlap with the measurement gap and BFD-RS partially overlaps with the SMTC opportunity (T SSB <T SMTCperiod ). P is P sharing factor , at this time, BFD-RS does not overlap with the measurement gap and BFD-RS completely overlaps with the SMTC period (T SSB =T SMTCperiod ). P is 1 / (1-T SSB / MGRP-T SSB / T SMTCperiod ), at this time, BFD-RS partially overlaps with the measurement gap and BFD-RS partially overlaps with the SMTC opportunity (T SSB <T SMTCperiod ), and the SMTC opportunity does not overlap with the measurement gap and T SMTCperiod ≠MGRP or T SMTCperiod =MGRP and T SSB <0.5*T SMTCperiod . P is 1 / (1-T SSB / MGRP)*P sharing facto , at this time, BFD-RS partially overlaps with the measurement gap and BFD-RS partially overlaps with the SMTC opportunity (T SSB<T SMTCperiod ), and the SMTC opportunity does not overlap with the measurement gap and T SMTCperiod = MGRP and T SSB = 0.5 * T SMTCperiod。 P is 1 / {1 - T SSB / min(T SMTCperiod , MGRP)}, at this time BFD-RS partially overlaps with the measurement gap (T SSB < MGRP) and BFD-RS partially overlaps with the SMTC opportunity (T SSB < T SMTCperiod ) and the SMTC opportunity partially or fully overlaps with the measurement gap. P is 1 / (1 - T SSB / MGRP) * P sharing factor , at this time BFD-RS partially overlaps with the measurement gap and BFD-RS fully overlaps with the SMTC opportunity (T SSB = T SMTCperiod ) and the SMTC opportunity partially overlaps with the measurement gap (T SMTCperiod < MGRP). P sharing factor = 3.

[0143] If the higher layer signaling of smtc2 is configured, then T SMTCperiod corresponds to the value of the higher layer parameter smtc2; otherwise, T SMTCperiod corresponds to the value of the higher layer parameter smtc1. If the combination of the configured BFD-RS, SMTC opportunity, and measurement gap does not meet the previous conditions, a longer evaluation period is expected.

[0144] Table B.2-1: Evaluation Period TEvaluate_BFD_SSB for FR1

[0145]

[0146] Table B.2-2: Evaluation Period TEvaluate_BFD_out for FR2

[0147]

[0148] For CSI-RS based beam failure detection, the UE evaluates whether the downlink radio link quality on the configured CSI-RS resources in the set estimated within the last T Evaluate_BFD_CSI-RS [ms] period has become worse than the threshold Q within the T Evaluate_BFD_CSI-RS [ms] period. The value of T out_LR_CSI-RS is defined for FR1 in Table B.2-3. The value of T Evaluate_BFD_CSI-RS is defined for FR2 with N = 1 in Table B.2-4. Evaluate_BFD_CSI-RS ​, if the higher layer parameter RadioLinkMonitoringRS is not provided to the UE and the UE is provided by the higher layer parameter TCI-state for PDCCH CSI-RS with QCL-TypeD, or if the CSI-RS configured for BFD is QCL-TypeD with DM-RS for PDCCH and the QCL association is known to the UE, or if the CSI-RS resources configured for BFD are QCL-TypeD and are time-division multiplexed to CSI-RS resources configured for L1-RSRP reporting or SSBs configured for L1-RSRP reporting, all CSI-RS resources configured for BFD are time-division multiplexed with each other and the QCL association is known to the UE and CSI reporting with L1-RSRP measurement for the CSI-RS configured for BFD has been performed within [TBD] ms.

[0149] For FR1, P = 1 / (1-T CSI-RS / MGRP), in which case, in the monitored cell, there are measurement gaps configured for intra-frequency measurement, inter-frequency measurement, or inter-RAT measurement, which overlap with some but not all CSI-RS opportunities; and P=1, in which case, in the monitored cell, there are no measurement gaps overlapping with any CSI-RS opportunities.

[0150] For FR2, P=1. In this case, BFD-RS does not overlap with the measurement gap and does not overlap with the SMTC opportunity. P=1 / (1-T CSI-RS / MGRP), at which time BFD-RS partially overlaps with the measurement gap and BFD-RS does not overlap with the SMTC opportunity (T CSI-RS <MGRP),P=1 / (1-T CSI-RS / T SMTCperiod ), at this time, BFD-RS does not overlap with the measurement gap and BFD-RS partially overlaps with the SMTC opportunity (T CSI-RS <T SMTCperiod ). P is P sharing factor , at this time, BFD-RS does not overlap with the measurement gap and BFD-RS completely overlaps with the SMTC opportunity (T CSI-RS =T SMTCperiod ). P is 1 / (1-T CSI-RS / MGRP-T CSI-RS / T SMTCperiod ), at this time, BFD-RS partially overlaps with the measurement gap, and BFD-RS partially overlaps with the SMTC opportunity (T CSI-RS <T SMTCperiod ), and the SMTC opportunity does not overlap with the measurement gap, and T SMTCperiod ≠MGRP or TSMTCperiod = MGRP and T CSI-RS < 0.5 * T SMTCperiod 。P is 1 / (1 - T CSI-RS / MGRP) * P sharing factor , where BFD-RS partially overlaps with the measurement gap and BFD-RS partially overlaps with the SMTC occasion (T CSI-RS < T SMTCperiod ) and the SMTC occasion does not overlap with the measurement gap and T SMTCperiod = MGRP and T CSI-RS = 0.5 * T SMTCperiod 。P is 1 / {1 - T CSI-RS / min(T SMTCperiod , MGRP)}, where BFD-RS partially overlaps with the measurement gap (T CSI-RS < MGRP) and BFD-RS partially overlaps with the SMTC occasion (T CSI-RS < T SMTCperiod ) and the SMTC occasion partially or fully overlaps with the measurement gap. P is 1 / (1 - T CSI-RS / MGRP) * P sharing factor , where BFD-RS partially overlaps with the measurement gap and BFD-RS fully overlaps with the SMTC occasion (T CSI-RS = Ts MTCperiod ) and the SMTC occasion partially overlaps with the measurement gap (T SMTCperiod < MGRP). P sharing factor is 3.

[0151] If the higher layer signaling of smtc2 is configured, then T SMTCperiod corresponds to the value of the higher layer parameter smtc2; otherwise, T SMTCperiod corresponds to the value of the higher layer parameter smtc1. If the combination of the BFD-RS, SMTC occasion, and measurement gap configurations does not meet the previous conditions, a longer evaluation period is expected. If the CSI-RS resources configured for BFD are transmitted at density = 3, then the M BFD value used in Table B.2-3 and Table B.2-4 is defined as M BFD = 10.

[0152] Table B.2-3: Evaluation Period TEvaluate_BFD_CSI-RS for FR1

[0153]

[0154] Table B.2-4: Evaluation Period TEvaluate_BFD_CSI-RS for FR2

[0155]

[0156] Scheduling restrictions

[0157] In some embodiments, scheduling availability restrictions may apply when the UE is performing beam failure detection. For example, since beam failure detection is performed on an SSB configured as a BFD-RS with the same SCS as the PDSCH / PDCCH in FR1, there is no scheduling restriction. When the UE supports simultaneousRxDataSSB-DiffNumerology, there is no restriction on scheduling availability due to beam failure detection based on the SSB as the BFD-RS. However, when the UE does not support simultaneousRxDataSSB-DiffNumerology, due to beam failure detection based on the SSB configured as the BFD-RS, the following restriction applies: The UE is not expected to transmit PUCCH / PUSCH or receive PDCCH / PDSCH on SSB symbols to be measured for beam failure detection.

[0158] Due to beam failure detection based on CSI-RS as BFD-RS, the following scheduling restrictions apply: UEs are not expected to transmit PUCCH / PUSCH or receive PDCCH / PDSCH on CSI-RS symbols to be measured for beam failure detection. When intra-band carrier aggregation in FR1 is configured, scheduling restrictions apply to all SCells aggregated in the same frequency band as PCell or PSCell. When inter-band carrier aggregation in FR1 is configured, there are no scheduling restrictions on FR1 serving cells configured in other frequency bands than the band in which the PCell or PSCell is configured.

[0159] Due to beam failure detection on FR2 PCell and / or PSCell, the following scheduling restrictions apply: If the higher layer parameter failureDetectionResources is not provided to the UE and the UE is provided by the higher layer parameter TCI-state for PDCCH SSB / CSI-RS with QCL-TypeD, or if the SSB / CSI-RS used for BFD is QCL-TypeD with DM-RS for PDCCH. Since beam failure detection is performed with the same SCS as PDSCH / PDCCH, there are no scheduling restrictions. Otherwise, except for RMSI PDCCH / PDSCH and PDCCH / PDSCH which are not required to be received by RRC_CONNECTED mode UEs, the UE is not expected to transmit PUCCH / PUSCH or receive PDCCH / PDSCH on BFD-RS symbols to be measured for beam failure detection.

[0160] When intra-band carrier aggregation is configured, the following scheduling restrictions apply to all SCells configured in the same frequency band as the PCell and / or PSCell on which beam failure is detected. For the case where no RS is provided for BFD, or the BFD-RS is explicitly configured and quasi-co-located with the active TCI state for PDCCH / PDSCH. Since beam failure detection is performed with the same SCS as PDSCH / PDCCH, there are no scheduling restrictions. When beam failure detection is performed with a different SCS from PDSCH / PDCCH, for UEs supporting simultaneousRxDataSSB-DiffNumerology, there are no restrictions on scheduling availability due to beam failure detection. For UEs that do not support simultaneousRxDataSSB-DiffNumerology, it is not expected that the UE transmits PUCCH / PUSCH or receives PDCCH / PDSCH on SSB symbols to be measured for beam failure detection. For the case where the BFD-RS is explicitly configured and is not quasi-co-located with the active TCI state for PDCCH / PDSCH. The UE is not expected to transmit PUCCH / PUSCH or receive PDCCH / PDSCH on the BFD-RS symbols to be measured for beam failure detection.

[0161] Since beam failure detection is performed on the FR2 serving PCell and / or PSCell, there are no scheduling restrictions on the FR1 serving cell.Since beam failure detection is performed on the FR1 serving PCell and / or PSCell, there are no scheduling restrictions on the FR2 serving cell.

[0162] Radio Link Monitoring (RLM) aspects

[0163] Radio link monitoring (RLM) involves monitoring of the Figure 3 A mechanism used by a UE 301 to monitor the downlink radio link quality of a primary cell in order to indicate the out-of-sync / in-sync status to higher layers. The UE does not need to monitor the downlink radio link quality in DL BWPs other than the active DL BWP on the primary cell.

[0164] If the UE is configured with SCG and the parameter rlf-TimersAndConstants is provided by higher layers and is not set to release, the downlink radio link quality of the PSCell of the SCG is monitored by the UE in order to indicate the out-of-sync / in-sync status to higher layers. The UE does not need to monitor the downlink radio link quality in DL BWPs other than the active DL BWP on the PSCell.

[0165] The UE may be configured with a set of resource indices for each DLBWP of the SpCell via a corresponding set of higher layer parameters RadioLinkMonitoringRS for radio link monitoring by the higher layer parameter failureDetectionResources. The UE is provided with a CSI-RS resource configuration index (provided by the higher layer parameter csi-RS-tndex) or a SS / PBCH block index (provided by the higher layer parameter ssb-lndex) by the higher layer parameter RadioLinkMonitoringRS. The UE may be configured with up to N LR-RLM RadioLinkMonitoringRS is used for link recovery process (as discussed below) and radio link monitoring. LR-RLM Up to N RadioLinkMonitoringRS can be used RLM Up to two RadioLinkMonitoringRS may be used for radio link monitoring (this depends on the maximum number L of candidate SS / PBCH blocks per half-frame), and up to two RadioLinkMonitoringRS may be used for the link recovery process.

[0166] If the higher layer parameter RadioLinkMonitoringRS is not provided to the UE, and the UE is provided with one or more RSs including CSI-RS and / or one or more of the SS / PBCH blocks by the higher layer parameter TCI-state for PDCCH

[0167] - If the active TCI state of the PDCCH includes only one RS, the UE uses the RS provided for the active TCI state of the PDCCH for radio link monitoring

[0168] - If the active TCI state for PDCCH includes two RSs, the UE expects one RS to have QCL-Type D and the UE uses one RS for radio link monitoring; the UE does not expect both RSs to have QCL-Type D

[0169] -UE does not need to use aperiodic RS for radio link monitoring

[0170] When the higher layer parameter RadioLinkMonitoringRS is not provided to the UE, it is not expected that the UE will use more than N RLM A RadioLinkMonitoringRS performs radio link monitoring.

[0171] The N values ​​for different L values ​​are given in Table RLM-1. LR-RLM and N RLM The value of .

[0172] Table RLM-1: N LR-RLM and N RLM As a function of the maximum number L of SS / PBCH blocks per half-frame

[0173] L <![CDATA[N LR-RLM ]]> <![CDATA[N RLM ]]> 4 2 2 8 6 4 64 8 8

[0174] For CSI-RS resource configuration, the higher-level parameter powerControlOffsetSS is not applicable, and the UE expects to be provided: only "No CDM" from the higher-level parameter cdm-Type; only "1" and "3" from the higher-level parameter density; and only "1 port" from the higher-level parameter nrofPorts.

[0175] In non-DRX mode operation, the physical layer in the UE evaluates the radio link quality once per indication period, which is higher than the threshold (Q) configured by the higher layer parameter rlmInSyncOutOfSyncThreshold in the previous time period. out and Q in ) is evaluated. The UE determines the indication period as the maximum value between the shortest periodicity of the radio link monitoring resource and 10 milliseconds.

[0176] In DRX mode operation, the physical layer in the UE evaluates the radio link quality once per indication period, which is higher in the previous time period than the threshold (Q out and Q in ) is evaluated. The UE determines the indication period as the maximum value between the shortest periodicity of the radio link monitoring resource and the DRX cycle.

[0177] When the radio link quality is lower than the threshold Q of all resources in the resource set used for radio link monitoring out When the radio link quality is lower than the threshold Q of any resource in the resource set used for radio link monitoring, the physical layer in the UE indicates that it is out of synchronization with the higher layer in the frame in which the radio link quality is evaluated. in When good, the physical layer in the UE indicates synchronization with the higher layer in the frame in which the radio link quality is evaluated.

[0178] The UE is used to monitor the downlink quality based on the reference signal in the configured RLM-RS resource to detect the downlink radio link quality of the PCell and PSCell. The configured RLM-RS resource can be all SSBs or all CSI-RS or a mixture of SSBs and CSI-RS. The UE does not need to perform RLM outside the active DL BWP. The reference signal (RLM-RS) resource of the RLM is a resource in the resource set configured for RLM by the high-level parameter RLM-RS-List.

[0179] On each RLM-RS resource, the UE estimates the downlink radio link quality and compares it with the threshold Q out and Q in The comparison is performed in order to monitor the downlink radio link quality of the cell.

[0180] Threshold Q out is defined as the level at which the downlink radio link cannot be reliably received and corresponds to the out-of-sync block error rate (BLER) as defined in Table RLM.1-1. out ). For SSB-based radio link monitoring, Q is derived based on the assumed PDCCH transmission parameters listed in Table RLM.2-1. out_SSB For CSI-RS based radio link monitoring, Q is derived based on the assumed PDCCH transmission parameters listed in Table RLM.3-1. out_CSI-RS .

[0181] Threshold Q in is defined as out The level of downlink radio link quality that can be received significantly more reliably than 100 Mbps and corresponds to the synchronization block error rate (BLER) defined in Table RLM.1-1. in ). For SSB-based radio link monitoring, Q is derived based on the assumed PDCCH transmission parameters listed in Table RLM.2-2. in_SSB For CSI-RS based radio link monitoring, Q is derived based on the assumed PDCCH transmission parameters listed in Table RLM.3-2. in_CSI-RS .

[0182] The out-of-sync block error rate (BLER) is determined according to the network configuration via the parameter RLM-IS-OOS-thresholdConfig or lmInSyncOutOfSyncThreshold signaled by higher layers. out ) and synchronization block error rate (BLER in). The network may configure one of the two pairs of out-of-sync block error rate and in-sync block error rate shown in Table RLM.1-1. When the UE is not configured with RLM-IS-OOS-thresholdConfig from the network, the UE determines the out-of-sync block error rate and in-sync block error rate from Configuration #0 in Table RLM.1-1 as default values.

[0183] Table RLM.1-1: Unsynchronized block error rate and synchronized block error rate

[0184] Configuration <![CDATA[BLER out ]]> <![CDATA[BLER in ]]> 0 10％ 2％ 1 TBD TBD

[0185] The UE can monitor up to X signals of the same or different types within each corresponding carrier frequency range. RLM-RS RLM-RS resources, of which X RLM-RS Specified in Table RLM.1-2 and meet the requirements as specified below.

[0186] Table RLM.1-2: Maximum number of RLM-RS resources XRLM-RS

[0187] <![CDATA[Maximum number of RLM-RS resources, X RLM-RS > Carrier frequency range of PCell / PSCell 2 FR1,≤3GHz 4 FR1, >3GHz 8 FR2

[0188] Requirements for SSB-based radio link monitoring

[0189] Each SSB-based RLM-RS resource is configured for PCell and / or PSCell, provided that the SSB configured for RLM is actually transmitted within the UE active DL BWP during the entire evaluation period specified below.

[0190] Table RLM.2-1: PDCCH transmission parameters for asynchronous

[0191]

[0192]

[0193] Table RLM.2-2: PDCCH transmission parameters for synchronization

[0194]

[0195] Requirements for CSI-RS based radio link monitoring

[0196] Each CSI-RS based RLM-RS resource is configured for PCell and / or PSCell, provided that the CSI-RS configured for RLM is actually transmitted within the UE active DL BWP during the entire evaluation period specified below.

[0197] Table RLM.3-1: PDCCH transmission parameters for asynchronous

[0198]

[0199]

[0200] Table RLM.3-2: PDCCH transmission parameters for synchronization

[0201]

[0202] When the CSI-RS is quasi-co-located with multiple CORESETs, the CORESET is used as a reference. In some embodiments, when the CSI-RS is not quasi-co-located with any CORESET, the UE shall perform RLM and, if so, which CORESET to use as a reference.

[0203] Minimum requirements for transition

[0204] When the UE transitions between DRX and non-DRX or when the DRX cycle changes periodically, for each RLM-RS resource, the UE shall use an evaluation period that is not less than the minimum of the evaluation periods corresponding to the first mode and the second mode for a duration equal to the evaluation period corresponding to the second mode after the transition occurs. After this duration, the UE shall use the evaluation period corresponding to the second mode for each RLM-RS resource. This requirement shall apply to both asynchronous and synchronous evaluations of the monitored cells.

[0205] When a UE transitions from a first configuration of RLM-RS resources to a second configuration of RLM-RS resources that is different from the first configuration, for each RLM-RS resource present in the second configuration, the UE shall use an evaluation period that is not less than the minimum of the evaluation periods corresponding to the first configuration and the second configuration for a duration equal to the evaluation period corresponding to the second configuration after the transition occurs. After this duration, the UE shall use the evaluation period corresponding to the second configuration for each RLM-RS resource present in the second configuration. This requirement shall apply to both asynchronous and synchronous evaluations of monitored cells.

[0206] Minimum requirements for UE to turn off transmitter

[0207] The transmitter power of the UE in the monitored cell should be turned off within 40ms after the T310 timer expires.

[0208] Minimum requirements for L1 indication

[0209] When the downlink radio link quality on all configured RLM-RS resources is better than Q out When the cell is out of sync, the UE's layer 1 sends an out-of-sync indication to the upper layer. The layer 3 filter will be applied to the out-of-sync indication.

[0210] When the downlink radio link quality on at least one of the configured RLM-RS resources is higher than Q in When the synchronization is good, the UE's layer 1 sends the cell's synchronization indication to the upper layer. The layer 3 filter will be applied to the synchronization indication.

[0211] Both asynchronous and synchronous evaluations will be performed for the configured RLM-RS resources. Two consecutive indications from Layer 1 will be separated by at least T Indication_interval .

[0212] When DRX is not used, T Indication_interval is the maximum max(10ms,T RLM-RS,M ),in

[0213] T RLM,M is the shortest periodicity of all configured RLM-RS resources of the monitored cell. If the RLM-RS resource is SSB, it corresponds to T SSB , or if the RLM-RS resource is a CSI-RS, it corresponds to T CSI-RS .

[0214] In case of DRX, if DRX cycle_length is less than or equal to 320ms, T Indication_interval is max(10ms,1.5*DRX_cycle_length,1.5*T RLM-RS,M ), and if DRX cycle_length is greater than 320ms, T Indication_interval When the T310 timer as specified in TS 38.331 [2] is started, the UE shall monitor the configured RLM-RS resources for recovery using the evaluation period and the Layer 1 indication interval corresponding to non-DRX mode until the T310 timer expires or is stopped.

[0215] Scheduling UE availability during radio link monitoring

[0216] When the reference signal to be measured for RLM has a different subcarrier spacing than PDSCH / PDCCH and is on frequency range FR2, there are restrictions on scheduling availability as described below. Scheduling availability for UE to perform radio link monitoring with the same subcarrier spacing as PDSCH / PDCCH on FR1

[0217] Since radio link monitoring is performed with the same subcarrier spacing as PDSCH / PDCCH on FR1, there is no scheduling restriction.

[0218] Scheduling availability for UE to perform radio link monitoring with different subcarrier spacing than PDSCH / PDCCH on FR1

[0219] For UEs supporting simultaneousRxDataSSB-DiffNumerology

[14] , there is no restriction on scheduling availability due to radio link monitoring based on SSB as RLM-RS. For UEs not supporting simultaneousRxDataSSB-DiffNumerology

[14] , the following restrictions apply due to radio link monitoring based on SSB as RLM-RS. The UE is not expected to transmit PUCCH / PUSCH or receive PDCCH / PDSCH on SSB symbols to be measured for radio link monitoring.

[0220] When performing intra-band carrier aggregation, scheduling restrictions apply to all serving cells on the frequency band due to radio link monitoring performed in the same frequency band on the FR1 serving PCell or PSCell. When performing inter-band carrier aggregation within FR1, there are no scheduling restrictions on the FR1 serving cells in the frequency band due to radio link monitoring performed in different frequency bands on the FR1 serving PCell or PSCell.

[0221] Scheduling availability for UE to perform radio link monitoring in FR2

[0222] Due to radio link monitoring on the FR2 serving PCell and / or PSCell, the following scheduling restrictions apply.

[0223] If the higher layer parameter RadioLinkMonitoringRS is not provided to the UE and the UE is provided by the higher layer parameter TCI-state for PDCCH SSB / CSI-RS with QCL-TypeD, or if the SSB / CSI-RS configured for RLM is QCL-TypeD with DM-RS for PDCCH. Since radio link monitoring is performed with the same subcarrier spacing as PDSCH / PDCCH, there are no scheduling restrictions. Otherwise, except for RMSIPDCCH / PDSCH and PDCCH / PDSCH that do not need to be received by RRC_CONNECTED mode UEs, the UE is not expected to transmit PUCCH / PUSCH or receive PDCCH / PDSCH on RLM-RS symbols to be measured for radio link monitoring.

[0224] When intra-band carrier aggregation is performed, for other serving cells on the band other than the FR2 serving PCell or PSCell in the same band, the following scheduling restrictions apply due to radio link monitoring on the FR2 serving PCell and / or PSCell. If the RLM-RS is type-D quasi-co-located with the active TCI state for PDCCH / PDSCH, and N=1 applies to the RLM-RS, as specified in section 8.1.2.2, if the RLM-RS is SSB, if the RLM-RS is CSI-RS. Since radio link monitoring is performed with the same subcarrier spacing as PDSCH / PDCCH, there are no scheduling restrictions. When radio link monitoring is performed with a different subcarrier spacing than PDSCH / PDCCH, for UEs supporting simultaneousRxDataSSB-DiffNumerology, there are no restrictions on scheduling availability due to radio link monitoring. For UEs that do not support simultaneousRxDataSSB-DiffNumerology, it is not expected that the UE transmits PUCCH / PUSCH or receives PDCCH / PDSCH on SSB symbols to be measured for radio link monitoring. Otherwise, it is not expected that the UE transmits PUCCH / PUSCH or receives PDCCH / PDSCH on RLM-RS symbols to be measured for radio link monitoring.

[0225] Scheduling availability for UE to perform radio link monitoring on FR1 or FR2 in case of FR1-FR2 inter-band CA

[0226] Due to the radio link monitoring performed on the FR2 serving PCell and / or PSCell, there are no scheduling restrictions on the FR1 serving cell.

[0227] Due to the radio link monitoring performed on the FR1 serving PCell and / or PSCell, there are no scheduling restrictions on the FR2 serving cell.

[0228] Link recovery process

[0229] UE-based collection The reference signals in the RF are used to evaluate the downlink quality of the serving cell in order to detect beam failure instances. The RS resources in the set can be periodic CSI-RS resources and / or SSBs. The UE does not need to perform beam failure detection outside the active DL BWP. On each RS resource in the UE, the UE shall estimate the radio link quality and compare it with the threshold Q out_LR A comparison is performed in order to access the downlink radio link quality of the serving cell.

[0230] Threshold Q out_LR is defined as the BLER at which the downlink radio level link cannot be reliably received and should correspond to an assumed PDCCH transmission out For SSB-based beam failure detection, Q is derived based on the assumed PDCCH transmission parameters listed elsewhere. out_LR_SSB For CSI-RS based beam failure detection, Q is derived based on the assumed PDCCH transmission parameters listed elsewhere out_LR_CSI-RS .

[0231] UE-based collection The reference signal in is used to perform L1-RSRP measurement in order to detect the candidate beams. The RS resources in may be periodic CSI-RS resources and / or SSBs. The UE does not need to perform candidate beam detection outside of the active DL BWP.

[0232] In the collection On each RS resource in the UE, the UE shall perform L1-RSRP measurement and compare it with the threshold Q in_LR The comparison is used to select a new beam for beam failure recovery. in_LR Corresponds to the value of the high-level parameter candidateBeamThreshold.

[0233] In some embodiments, the set of periodic CSI-RS resource configuration indices Indicated by the high-level parameter failureDetectionResources, where the set of periodic CSI-RS resource configuration index and / or SS / PBCH block index Indicated by the higher layer parameter candidateBeamRSList for radio link quality measurement on the serving cell. If the UE is not provided with the higher layer parameter failureDetectionResources, the UE determines the set Includes SS / PBCH block index and periodic CSI-RS resource configuration index, which have the same value as the RS index in the RS set indicated by the TCI state that the UE uses to monitor the corresponding control resource set of PDCCH. UE expects the set Includes up to two RS indices, and if there are two RS indices, the set Only RS indices with QCL-TypeD configuration for the corresponding TCI state are included. The UE expects There is a single port RS in it.

[0234] Threshold Qout,LR They correspond respectively to the default value of the higher-layer parameter rlmInSyncOutOfSyncThreshold and the value provided by the higher-layer parameter rsrp-ThresholdSSB.

[0235] The physical layer in Ue is based on the threshold Q out,LR Resource configuration set To evaluate the radio link quality. The UE evaluates the radio link quality only based on the periodic CSI-RS resource configuration or SS / PBCH blocks that are quasi-co-located with the DM-RS received by the PDCCH monitored by the UE, as described. in,LR The threshold is applied to the L1-RSRP measurement obtained from the SS / PBCH block. The UE sets Q in,LR The threshold is applied to the L1-RSRP measurement obtained for the CSI-RS resource.

[0236] When the UE uses the set used to evaluate the quality of the radio link The radio link quality ratio threshold Q of all corresponding resource configurations in out,LR When the radio link quality is lower than the threshold Q out,LR When the quality of the radio link is poor, the physical layer notifies the higher layer of the set of The periodicity is determined by the maximum value between the periodic CSI-RS configuration in or the shortest period of the SS / PBCH block and 2msec.

[0237] Based on the request of higher layers, the UE provides the higher layers with The periodic CSI-RS configuration index and / or SS / PBCH block index and the corresponding L1-RSRP measurement greater than or equal to the corresponding threshold.

[0238] The CORESET may be provided to the UE via a link to the search space set provided by the higher layer parameter recoverySearchSpaceId for monitoring PDCCH in the control resource set. If the UE is provided with the higher layer parameter recoverySearchSpaceId, the UE does not expect to be provided with another search space set for monitoring PDCCH in the control resource set associated with the search space set provided by recoverySearchSpaceId.

[0239] The UE may receive the configuration for PRACH transmission via the higher layer parameter PRACH-ResourceDedicatedBFR. For PRACH transmission in time slot n and according to the PRACH with index q provided by higher layers new The UE monitors the PDCCH in the search space provided by the higher-layer parameter recoverySearchSpaceId for detecting DCI formats with CRC scrambled by C-RNTI starting from slot n+4 within the window configured by the higher-layer parameter BeamFailureRecoveryConfig. For PDCCH monitoring and corresponding PDSCH reception, the UE assumes a PDCCH with index q new The antenna port quasi-co-location parameters are the same until the UE receives activation of the TCI state or any of the parameters TCI-StatesPDCCH-ToAddlist and / or TCI-StatesPDCCH-ToReleaseList through the higher layer. After the UE detects a DCI format with a CRC scrambled by C-RNTI in the search space provided by recoverySearchSpaceId, the UE monitors the PDCCH candidates in the search space provided by recoverySearchSpaceId until the UE receives a MAC CE activation command for the TCI state or higher layer parameters TTCI-StatesPDCCH-ToAddlist and / or TCI-StatesPDCCH-ToReleaseList.

[0240] If the UE is not provided with a set of control resources for the search space set provided by recoverySearchSpaceId, or if the UE is not provided with recoverySearchSpaceId, the UE does not expect to receive a PDCCH order triggering a PRACH transmission.

[0241] System and implementation

[0242] Figure 3 An exemplary architecture of a system 300 of a network according to various embodiments is shown. The following description is provided for an example system 300 operating in conjunction with LTE system standards and 5G or NR system standards provided by 3GPP technical specifications. However, the exemplary embodiments are not limited in this regard, and the embodiments may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems (e.g., sixth generation (6G)) systems, IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), and the like.

[0243] like Figure 3 As shown, system 300 includes UE 301a and UE 301b (collectively referred to as "UE 301"). In this example, multiple UE 301 are shown as smart phones (e.g., handheld touch screen mobile computing devices capable of connecting to one or more cellular networks), but may also include any mobile or non-mobile computing devices, such as consumer electronic devices, mobile phones, smart phones, feature phones, tablet computers, wearable computer devices, personal digital assistants (PDAs), pagers, wireless handheld devices, desktop computers, laptop computers, in-vehicle infotainment (IVI), in-vehicle entertainment (ICE) devices, instrument panels (ICs), head-up display (HUD) devices, on-board diagnostic (OBD) devices, dashtop mobile equipment (DME), mobile data terminals (MDTs), electronic engine management systems (EEMS), electronic / engine electronic control units (ECUs), electronic / engine electronic control modules (ECMs), embedded systems, microcontrollers, control modules, engine management systems (EMS), networked or "smart" appliances, MTC devices, M2M, IoT devices, etc.

[0244] In some embodiments, any of the UEs 301 may be an 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 M2M or MTC to exchange data with an MTC server or device via PLMN, ProSe or D2D communications, sensor networks, or IoT networks. M2M or MTC data exchanges may be machine-initiated data exchanges. 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.

[0245] UE 301 may be configured to connect, e.g., be communicatively coupled, to RAN 310. In an embodiment, RAN 310 may be an NG RAN or 5G RAN, an E-UTRAN, or a legacy RAN, such as UTRAN or GERAN. As used herein, the term "NG RAN" or the like may refer to RAN 310 operating in an NR or 5G system 300, while the term "E-UTRAN" or the like may refer to RAN 310 operating in an LTE or 4G system 300. UE 301 utilizes connections (or channels) 303 and 304, respectively, each of which includes a physical communication interface or layer (discussed in further detail below).

[0246] In this example, connections 303 and 304 are shown as air interfaces to achieve communication coupling, and may be consistent with a cellular communication protocol, such as a GSM protocol, a CDMA network protocol, a PTT protocol, a POC protocol, a UMTS protocol, a 3GPP LTE protocol, a 5G protocol, a NR protocol, and / or any other communication protocol discussed herein. In an embodiment, UE 301 may directly exchange communication data via a ProSe interface 305. ProSe interface 305 may alternatively be referred to as a SL interface 305, and may include one or more logical channels, including but not limited to PSCCH, PSSCH, PSDCH, and PSBCH.

[0247] UE 301b is shown as being configured to access AP 306 (also referred to as "WLAN node 306", "WLAN 306", "WLAN terminal 306", "WT 306", etc.) via connection 307. Connection 307 may include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein AP 306 will include Wireless Fidelity. Router. In this example, the AP 306 shown is connected to the Internet without being connected to the core network of the wireless system (described in further detail below). In various embodiments, the UE 301b, the RAN 310, and the AP 306 can be configured to utilize LWA operation and / or LWIP operation. The LWA operation can involve the UE 301b in the RRC_CONNECTED state being configured by the RAN nodes 311a-b to utilize the radio resources of LTE and WLAN. The LWIP operation can involve the UE 301b using the WLAN radio resources (e.g., connection 307) via an IPsec protocol tunnel to authenticate and encrypt packets (e.g., IP packets) sent through the connection 307. IPsec tunneling can include encapsulating the entire original IP packet and adding a new packet header, thereby protecting the original header of the IP packet.

[0248] The RAN 310 may include one or more AN nodes or RAN nodes 311a and 311b (collectively referred to as "RAN node 311" or "RAN node 311") that enable connections 303 and 304. As used herein, the terms "access node", "access point", etc. may describe equipment that provides radio baseband functions for data and / or voice connections between a network and one or more users. These access nodes may be referred to as BS, gNB, RAN node, eNB, NodeB, RSU, TRxP or TRP, etc., and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). As used herein, the terms "NG RAN node" and the like may refer to a RAN node 311 (e.g., a gNB) operating in an NR or 5G system 300, while the terms "E-UTRAN node" and the like may refer to a RAN node 311 (e.g., an eNB) operating in an LTE or 4G system 300. According to various embodiments, the RAN node 311 may be implemented as one or more of a dedicated physical device such as a macrocell base station and / or a low power (LP) base station for providing a femtocell, picocell or other similar cell with a smaller coverage area, smaller user capacity or higher bandwidth than a macrocell.

[0249] In some embodiments, all or part of the multiple RAN nodes 311 may be implemented as one or more software entities running on a server computer as part of a virtual network that may be referred to as a CRAN and / or a virtual baseband unit pool (vBBUP). In these embodiments, the CRAN or vBBUP may implement RAN functional splits, such as PDCP splits, where the RRC and PDCP layers are operated by the CRAN / vBBUP, while other L2 protocol entities are operated by individual RAN nodes 311; MAC / PHY splits, where the RRC, PDCP, RLC, and MAC layers are operated by the CRAN / vBBUP, and the PHY layer is operated by individual RAN nodes 311; or "lower PHY" splits, where the RRC, PDCP, RLC, MAC layers, and upper portions of the PHY layers are operated by the CRAN / vBBUP, while the lower portions of the PHY layers are operated by individual RAN nodes 311. This virtualization framework allows idle processor cores of the RAN nodes 311 to execute other virtualized applications. In some specific implementations, individual RAN nodes 311 may represent a plurality of RAN nodes 311 that are connected to the RAN via individual F1 interfaces ( Figure 3 In these embodiments, the gNB-DU may include one or more remote radio heads or RFEMs (see, e.g., Figure 6), and the gNB-CU may be operated by a server (not shown) located in the RAN 310 or by a server pool in a manner similar to the CRAN / vBBUP. In addition or alternatively, one or more of the RAN nodes 311 may be a next generation eNB (ng-eNB), which is a next generation eNB that provides E-UTRA user plane and control plane protocol terminals to the UE 301 and is connected to the 5GC (e.g., Figure 5 CN 520) RAN node.

[0250] In a V2X scenario, one or more of the RAN nodes 311 may be an RSU or act as an RSU. The term "roadside unit" or "RSU" may refer to any traffic infrastructure entity used for V2X communication. The RSU may be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, wherein an RSU implemented in or by a UE may be referred to as a "UE-type RSU", an RSU implemented in or by an eNB may be referred to as an "eNB-type RSU", an RSU implemented in or by a gNB may be referred to as a "gNB-type RSU", and so on. In one example, the RSU is a computing device coupled to a radio frequency circuit located on the road side that provides connectivity support to a passing vehicle UE 301 (vUE 301). The RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicle and pedestrian traffic. The RSU may operate on the 5.9 GHz Direct Short Range Communication (DSRC) band to provide extremely low latency communications required for high-speed events, such as collision avoidance, traffic warnings, etc. In addition or alternatively, the RSU may operate on the cellular V2X band to provide the aforementioned low latency communications as well as other cellular communication services. In addition or alternatively, the RSU may operate as a Wi-Fi hotspot (2.4 GHz band) and / or provide connectivity to one or more cellular networks to provide uplink and downlink communications. Some or all of the computing device and the RSU's RF circuitry may be packaged in a weather-resistant enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller and / or backhaul network.

[0251] Any of the RAN nodes 311 may terminate the air interface protocol and may be the first point of contact for the UE 301. In some embodiments, any of the RAN nodes 311 may fulfill various logical functions of the RAN 310, 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.

[0252] In an embodiment, multiple UEs 301 may be configured to communicate with each other or with any of multiple RAN nodes 311 on a multi-carrier communication channel using OFDM communication signals according to various communication techniques, such as but not limited to OFDMA communication techniques (e.g., for downlink communication) or SC-FDMA communication techniques (e.g., for uplink and ProSe or sidelink communication), although the scope of the embodiments is not limited in this respect. The OFDM signal may include multiple orthogonal subcarriers.

[0253] In some embodiments, a downlink resource grid may be used for downlink transmissions from any of the RAN nodes 311 to the UE 301, 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 a 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.

[0254] According to various embodiments, UE 301 and RAN node 311 communicate data (e.g., transmit data and receive data) through a licensed medium (also referred to as "licensed spectrum" and / or "licensed frequency band") and an unlicensed shared medium (also referred to as "unlicensed spectrum" and / or "unlicensed frequency band"). The licensed spectrum may include channels operating in a frequency range of approximately 400 MHz to approximately 3.8 GHz, and the unlicensed spectrum may include a 5 GHz frequency band.

[0255] To operate in the unlicensed spectrum, the UE 301 and the RAN node 311 may operate using LAA, eLAA, and / or feLAA mechanisms. In these implementations, the UE 301 and the RAN node 311 may perform one or more known medium sensing operations and / or carrier sensing operations to determine whether one or more channels in the unlicensed spectrum are unavailable or otherwise occupied before transmitting in the unlicensed spectrum. The medium / carrier sensing operations may be performed according to a listen-before-talk (LBT) protocol.

[0256] LBT is a mechanism for equipment (e.g., UE 301, RAN node 311, etc.) to sense a medium (e.g., a channel or carrier frequency) and transmit when the medium is sensed to be idle (or when a particular channel in the medium is sensed to be unoccupied). The medium sensing operation may include CCA, which utilizes at least ED to determine whether other signals are present on the channel in order to determine whether the channel is occupied or idle. The LBT mechanism allows cellular / LAA networks to coexist with existing systems in unlicensed spectrum and with other LAA networks. ED may include sensing RF energy over a period of time on an expected transmission band, and comparing the sensed RF energy to a predefined or configured threshold.

[0257] Typically, existing systems in the 5 GHz band are WLANs based on IEEE 802.11 technology. WLANs use a contention-based channel access mechanism called CSMA / CA. Here, when a WLAN node (e.g., a mobile station (MS) such as UE 301, AP 306, etc.) intends to transmit, the WLAN node may first perform CCA before transmission. In addition, in the case where more than one WLAN node senses the channel as idle and transmits at the same time, a backoff mechanism is used to avoid conflicts. The backoff mechanism may be a counter randomly introduced within the CWS that increases exponentially when a conflict occurs and is reset to a minimum value when the transmission is successful. The LBT mechanism designed for LAA is somewhat similar to the CSMA / CA of WLAN. In some specific implementations, the LBT process for a DL or UL transmission burst (including PDSCH or PUSCH transmission) may have a LAA contention window of variable length between X and Y ECCA slots, where X and Y are the minimum and maximum values ​​of the CWS of LAA. In one example, the minimum CWS for LAA transmissions may be 9 microseconds (μs); however, the size of the CWS and MCOT (eg, transmission burst) may be based on government regulatory requirements.

[0258] The LAA mechanism is built on the CA technology of the LTE-Advanced system. In CA, each aggregated carrier is called a CC. A CC can have a bandwidth of 1.4, 3, 5, 10, 15, or 20 MHz, and up to five CCs can be aggregated, so the maximum aggregated bandwidth is 100 MHz. In an FDD system, the number of aggregated carriers can be different for DL ​​and UL, where the number of UL CCs is equal to or lower than the number of DL component carriers. In some cases, each CC may have a different bandwidth from other CCs. In a TDD system, the number of CCs and the bandwidth of each CC are typically the same for DL ​​and UL.

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

[0260] The PDSCH carries user data and higher layer signaling to the UE 301. The PDCCH carries, among other information, information about the transport format and resource allocation related to the PDSCH channel. It can also inform the UE 301 about the transport format, resource allocation, and HARQ information related to the uplink shared channel. Typically, downlink scheduling (allocation of control and shared channel resource blocks to UE 301b within a cell) can be performed on any of the multiple RAN nodes 311 based on channel quality information fed back from any of the multiple UEs 301. Downlink resource allocation information can be sent on the PDCCH for (e.g., allocated to) each of the UEs 301.

[0261] PDCCH uses 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 nine sets of four physical resource elements, respectively, called REGs. Four quadrature phase shift keying (QPSK) symbols can be mapped to each REG. Depending on the size of the 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).

[0262] 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 EPDCCH that uses PDSCH resources for control information transmission. One or more ECCEs may be used to transmit EPDCCH. Similar to the above, each ECCE may correspond to nine sets of four physical resource elements, referred to as EREG. In some cases, ECCE may have other numbers of EREGs.

[0263] RAN nodes 311 may be configured to communicate with each other via interface 312. In embodiments where system 300 is an LTE system (eg, when CN 320 is a Figure 4 420 in the EPC 420), the interface 312 may be an X2 interface 312. The X2 interface may be defined between two or more RAN nodes 311 (e.g., two or more eNBs, etc.) connected to the EPC 320, and / or between two eNBs connected to the EPC 320. In some specific implementations, the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). The X2-U may provide a flow control mechanism for user packets transmitted over the X2 interface, and may be used to transmit information about the delivery of user data between eNBs. For example, the X2-U may provide specific sequence number information about user data transmitted from the MeNB to the SeNB; information about the successful in-sequence delivery of PDCP PDUs from the SeNB to the UE 301 for user data; information about PDCP PDUs that were not delivered to the UE 301; information about the current minimum expected buffer size at the SeNB for transmitting user data to the UE; and the like. X2-C can provide intra-LTE access mobility functions, including context transfer from source eNB to target eNB, user plane transmission control, etc.; load management functions; and inter-cell interference coordination functions.

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

[0265] RAN 310 is shown as being communicatively coupled to a core network—in this embodiment, a core network (CN) 320. CN 320 may include a plurality of network elements 322 configured to provide various data and telecommunication services to customers / subscribers (e.g., users of UE 301) connected to CN 320 via RAN 310. The components of CN 320 may be implemented in one physical node or in separate physical nodes, including components for reading and executing instructions from a machine-readable medium or a computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some embodiments, NFV may be used to virtualize any or all of the above-mentioned network node functions via executable instructions stored in one or more computer-readable storage media (described in further detail below). A logical instance of CN 320 may be referred to as a network slice, and a logical instance of a portion of CN 320 may be referred to as a network sub-slice. NFV architecture and infrastructure may be used to virtualize one or more network functions onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches (alternatively performed by proprietary hardware). In other words, the NFV system may be used to perform a virtual or reconfigurable implementation of one or more EPC components / functions.

[0266] Generally speaking, the application server 330 may be an element that provides applications that use IP bearer resources with the core network (e.g., UMTS PS domain, LTE PS data services, etc.). The application server 330 may also be configured to support one or more communication services for the UE 301 via the EPC 320 (e.g., VoIP sessions, PTT sessions, group communication sessions, social network services, etc.).

[0267] In an embodiment, CN 320 may be a 5GC (referred to as "5GC 320" or the like), and RAN 310 may be connected to CN 320 via an NG interface 313. In an embodiment, NG interface 313 may be divided into two parts: an NG user plane (NG-U) interface 314, which carries traffic data between RAN node 311 and UPF; and an S1 control plane (NG-C) interface 315, which is a signaling interface between RAN node 311 and AMF. Figure 5 CN 320 is an implementation of 5GC 320 discussed in more detail.

[0268] In an embodiment, CN 320 may be a 5G CN (referred to as "5GC 320", etc.), while in other embodiments, CN 320 may be an EPC. In the case where CN 320 is an EPC (referred to as "EPC 320", etc.), RAN 310 may be connected to CN 320 via an S1 interface 313. In an embodiment, S1 interface 313 may be divided into two parts: an S1 user plane (S1-U) interface 314, which carries traffic data between RAN node 311 and S-GW; and an S1-MME interface 315, which is a signaling interface between RAN node 311 and MME. Figure 4 An exemplary architecture is shown in which CN 320 is an EPC 320 .

[0269] Figure 4 FIG. 4 shows an exemplary architecture of a system 400 including a first CN 420 according to various embodiments. In this example, the system 400 may implement the LTE standard, wherein the CN 420 is a Figure 3 The EPC 420 corresponding to the CN 320. In addition, the UE 401 can communicate with Figure 3 UE 301 is the same as or similar to UE 301, and E-UTRAN 410 may be Figure 3 The CN 420 may be a RAN that is the same as or similar to the RAN 310 of the mobile network, and may include the RAN node 311 discussed previously. The CN 420 may include an MME 421, an S-GW 422, a P-GW 423, an HSS 424, and an SGSN 425.

[0270] The MME 421 may be similar in function to the control plane of a conventional SGSN, and may implement MM functions to keep track of the current location of the UE 401. The MME 421 may perform various MM procedures to manage mobility aspects in access, such as gateway selection and tracking area list management. MM (also referred to as "EPS MM" or "EMM" in an E-UTRAN system) may refer to all applicable procedures, methods, data storage, etc. for maintaining knowledge of the current location of the UE 401, providing user identity confidentiality to users / subscribers, and / or performing other similar services. Each UE 401 and the MME 421 may include an MM or EMM sublayer, and an MM context may be established in the UE 401 and the MME 421 when the attach procedure is successfully completed. The MM context may be a data structure or database object that stores MM-related information of the UE 401. The MME 421 may be coupled to the HSS 424 via an S6a reference point, to the SGSN 425 via an S3 reference point, and to the S-GW 422 via an S11 reference point.

[0271] SGSN 425 may be a node that serves UE 401 by tracking the location of individual UE 401 and performing security functions. In addition, SGSN 425 may perform inter-EPC node signaling for mobility between 2G / 3G and E-UTRAN 3GPP access networks; PDN and S-GW selection as specified by MME 421; handling of UE 401 time zone capabilities as specified by MME 421; and MME selection for handover to E-UTRAN 3GPP access network. The S3 reference point between MME 421 and SGSN 425 may enable user and bearer information exchange for inter-3GPP access network mobility in an idle state and / or an active state.

[0272] The HSS 424 may include a database for network users, which includes subscription-related information for supporting network entities in handling communication sessions. The EPC 420 may include one or several HSSs 424, depending on the number of mobile subscribers, the capacity of the equipment, the organization of the network, etc. For example, the HSS 424 may provide support for routing / roaming, authentication, authorization, naming / addressing solutions, location dependencies, etc. The S6a reference point between the HSS 424 and the MME 421 may enable the transfer of subscription and authentication data for authenticating / authorizing users to access the EPC 420 between the HSS 424 and the MME 421.

[0273] The S-GW 422 may terminate the S1 interface 313 ( Figure 4 The S-GW 422 may be a local mobility anchor 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. The S11 reference point between the S-GW 422 and the MME 421 may provide a control plane between the MME 421 and the S-GW 422. The S-GW 422 may be coupled to the P-GW 423 via the S5 reference point.

[0274] The P-GW 423 may terminate the SGi interface toward the PDN 430. The P-GW 423 may communicate with the PDN 430 via the IP interface 325 (see, e.g., Figure 3 ) routes data packets between EPC 420 and an external network, such as a network including an application server 330 (alternatively referred to as an "AF"). In an embodiment, P-GW 423 may communicate with the EPC 420 via an IP communication interface 325 (see, e.g., Figure 3 ) is communicatively coupled to an application server ( Figure 3 Application server 330 or Figure 4The S5 reference point between the P-GW 423 and the S-GW 422 can provide user plane tunneling and tunnel management between the P-GW 423 and the S-GW 422. Due to the mobility of the UE 401 and whether the S-GW 422 needs to be connected to a non-colocated P-GW 423 for the required PDN connectivity, the S5 reference point can also be used for S-GW 422 relocation. The P-GW 423 can also include nodes for policy implementation and charging data collection (e.g., PCEF (not shown)). In addition, the SGi reference point between the P-GW 423 and the packet data network (PDN) 430 can be an operator-external public, private PDN, or an internal operator packet data network, for example, to provide IMS services. The P-GW 423 can be coupled to the PCRF 426 via the Gx reference point.

[0275] PCRF 426 is a policy and charging control element of EPC 420. In a non-roaming scenario, there may be a single PCRF 426 in a domestic public land mobile network (HPLMN) associated with an Internet Protocol Connectivity Access Network (IP-CAN) session of UE 401. In a roaming scenario with local traffic breakout, there may be two PCRFs associated with the IP-CAN session of UE 401: a domestic PCRF (H-PCRF) in the HPLMN and a visited PCRF (V-PCRF) in a visited public land mobile network (VPLMN). PCRF 426 may be communicatively coupled to application server 430 via P-GW 423. Application server 430 may signal PCRF 426 to indicate a new service flow and select appropriate QoS and charging parameters. PCRF 426 may configure the rule to a PCEF (not shown) with the appropriate TFT and QCI, which function starts QoS and charging as specified by application server 430. The Gx reference point between PCRF 426 and P-GW 423 may allow for the transfer of QoS policies and charging rules from PCRF 426 to PCEF in P-GW 423. The Rx reference point may reside between PDN 430 (or "AF 430") and PCRF 426.

[0276] Figure 5The architecture of a system 500 including a second CN 520 according to various embodiments is shown. The system 500 is shown to include a UE 501, which may be the same or similar to the previously discussed UE 301 and UE 401; an (R) AN 510, which may be the same or similar to the previously discussed RAN 310 and RAN 410, and which may include the previously discussed RAN node 311; and a DN 503, which may be, for example, an operator service, Internet access, or a 3rd party service; and a 5GC 520. The 5GC 520 may include an AUSF 522; an AMF 521; an SMF 524; an NEF 523; a PCF 526; an NRF 525; an UDM 527; an AF 528; an UPF 502; and an NSSF 529.

[0277] UPF 502 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point interconnected with DN 503, and a branch point supporting multi-host PDU sessions. UPF 502 may also perform packet routing and forwarding, perform packet inspection, perform the user plane portion of policy rules, lawful interception of packets (UP collection), perform traffic usage reporting, perform QoS processing (e.g., packet filtering, gating, UL / DL rate enforcement) on the user plane, perform uplink traffic verification (e.g., SDF to QoS flow mapping), transport level packet marking in uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF 502 may include an uplink classifier to support routing traffic flows to data networks. DN 503 may represent various network operator services, Internet access, or third-party services. DN 503 may include or be similar to the application server 330 discussed previously. UPF 502 may interact with SMF 524 via the N4 reference point between SMF 524 and UPF 502.

[0278] The AUSF 522 may store data for authentication of the UE 501 and handle authentication-related functions. The AUSF 522 may facilitate a common authentication framework for various access types. The AUSF 522 may communicate with the AMF 521 via the N12 reference point between the AMF 521 and the AUSF 522; and may communicate with the UDM 527 via the N13 reference point between the UDM 527 and the AUSF 522. In addition, the AUSF 522 may present an interface based on the Nausf service.

[0279] AMF 521 may be responsible for registration management (e.g., responsible for registering UE 501, etc.), connection management, reachability management, mobility management, and lawful interception of AMF-related events, as well as access authentication and authorization. AMF 521 may be the termination point of the N11 reference point between AMF 521 and SMF 524. AMF 521 may provide transport for SM messages between UE 501 and SMF 524, and act as a transparent proxy for routing SM messages. AMF 521 may also provide a communication channel between UE 501 and SMSF ( Figure 5 The AMF 521 may provide transport for SMS messages between the (R)AN 510 and the AMF 521 (not shown). The AMF 521 may act as a SEAF, which may include interaction with the AUSF 522 and the UE 501, receiving intermediate keys established as a result of the UE 501 authentication process. In the case of using USIM-based authentication, the AMF 521 may retrieve security material from the AUSF 522. The AMF 521 may also include an SCM function that receives keys from the SEA for deriving access network-specific keys. In addition, the AMF 521 may be a termination point for the RAN CP interface, which may include or be an N2 reference point between the (R)AN 510 and the AMF 521; and the AMF 521 may be a termination point for NAS (N1) signaling, and perform NAS encryption and integrity protection.

[0280] The AMF 521 may also support NAS signaling with the UE 501 over the N3 IWF interface. The N3 IWF may be used to provide access to untrusted entities. The N3 IWF may be the termination point for the N2 interface between the (R) AN 510 and the AMF 521 for the control plane, and may be the termination point for the N3 reference point between the (R) AN 510 and the UPF 502 for the user plane. Thus, the AMF 521 may process N2 signaling for PDU sessions and QoS from the SMF 524 and the AMF 521, encapsulate / decapsulate packets for IPSec and N3 tunnels, mark N3 user plane packets in the uplink, and perform QoS corresponding to N3 packet markings, taking into account QoS requirements associated with such markings received over N2. N3IWF may also relay uplink and downlink control plane NAS signaling between UE 501 and AMF 521 via the N1 reference point between UE 501 and AMF 521, and relay uplink and downlink user plane packets between UE 501 and UPF 502. N3IWF also provides a mechanism for IPsec tunnel establishment with UE 501. AMF 521 may present an interface based on Namf services, and may be an N14 reference point between two AMF 521 and an N14 reference point between AMF 521 and 5G-EIR ( Figure 5 The termination point of the N17 reference point between the two (not shown).

[0281] UE 501 may need to register with AMF 521 in order to receive network services. RM is used to register UE 501 with the network (e.g., AMF 521) or deregister UE 501, and establish a UE context in the network (e.g., AMF 521). UE 501 may operate in the RM-REGISTERED state or the RM-DEREGISTERED state. In the RM-DEREGISTERED state, UE 501 is not registered with the network, and the UE context in AMF 521 does not maintain the valid location or routing information of UE 501, so AMF 521 cannot reach UE 501. In the RM-REGISTERED state, UE 501 is registered with the network, and the UE context in AMF 521 may maintain the valid location or routing information of UE 501, so AMF 521 can reach UE 501. In the RM-REGISTERED state, UE 501 may perform a mobility registration update procedure, perform a periodic registration update procedure triggered by the expiration of a periodic update timer (e.g., to notify the network that UE 501 is still active), and perform a registration update procedure to update UE capability information or renegotiate protocol parameters with the network, etc.

[0282] AMF 521 may store one or more RM contexts for UE 501, each RM context being associated with a specific access to the network. An RM context may be a data structure, a database object, or the like, which indicates or stores, among other things, a registration status and a periodic update timer for each access type. AMF 521 may also store a 5GC MM context which may be the same or similar to the (E)MM context discussed previously. In various embodiments, AMF 521 may store CE mode B restriction parameters for UE 501 in an associated MM context or RM context. AMF 521 may also derive the value from the UE's usage setting parameters already stored in the UE context (and / or MM / RM context) when necessary.

[0283] The CM may be used to establish and release a signaling connection between the UE 501 and the AMF 521 through the N1 interface. The signaling connection is used to enable NAS signaling exchange between the UE 501 and the CN 520, and includes a signaling connection between the UE and the AN (e.g., an RRC connection or a UE-N3IWF connection for non-3GPP access) and an N2 connection of the UE 501 between the AN (e.g., the RAN 510) and the AMF 521. The UE 501 may operate in one of two CM states (CM-IDLE mode or CM-CONNECTED mode). When the UE 501 operates in the CM-IDLE state / mode, the UE 501 may not have a NAS signaling connection established with the AMF 521 through the N1 interface, and there may be a (R) AN 510 signaling connection (e.g., N2 and / or N3 connection) for the UE 501. When UE 501 operates in the CM-CONNECTED state / mode, UE 501 may have a NAS signaling connection established with AMF 521 through an N1 interface, and there may be a (R) AN 510 signaling connection (e.g., N2 and / or N3 connection) for UE 501. Establishing an N2 connection between (R) AN 510 and AMF 521 may cause UE 501 to transition from CM-IDLE mode to CM-CONNECTED mode, and when the N2 signaling between (R) AN 510 and AMF 521 is released, UE 501 may transition from CM-CONNECTED mode to CM-IDLE mode.

[0284] SMF 524 may be responsible for SM (e.g., session establishment, modification, and release, including tunnel maintenance between UPF and AN nodes); UE IP address allocation and management (including optional authorization); selection and control of UP functions; configuring traffic steering of UPF to route traffic to the correct destination; terminating the interface toward the policy control function; control portion of policy enforcement and QoS; lawful interception (for SM events and interface with LI system); terminating the SM portion of NAS messages; downlink data notification; initiating AN-specific SM information sent to AN via AMF over N2; and determining the SSC mode of the session. SM may refer to the management of a PDU session, and a PDU session or "session" may refer to a PDU connectivity service that provides or enables the exchange of PDUs between a UE 501 and a data network (DN) 503 identified by a data network name (DNN). The PDU session may be established upon request by UE 501, modified upon request by UE 501 and 5GC 520, and released upon request by UE 501 and 5GC 520 using NAS SM signaling exchanged between UE 501 and SMF 524 over the N1 reference point. Upon request from an application server, 5GC 520 may trigger a specific application in UE 501. In response to receiving a trigger message, UE 501 may deliver the trigger message (or relevant parts / information of the trigger message) to one or more identified applications in UE 501. The identified applications in UE 501 may establish a PDU session to a specific DNN. SMF 524 may check whether the UE 501 request complies with user subscription information associated with UE 501. In this regard, SMF 524 may retrieve and / or request to receive update notifications about SMF 524 level subscription data from UDM 527.

[0285] SMF 524 may include the following roaming functions: handling local execution to apply QoS SLA (VPLMN); charging data collection and charging interface (VPLMN); lawful interception (for SM events and interface with LI system, in VPLMN); and support interaction with external DN to transmit signaling for PDU session authorization / authentication through external DN. An N16 reference point between two SMFs 524 may be included in the system 500, which may be located between another SMF 524 in the visited network and the SMF 524 in the home network in a roaming scenario. In addition, SMF 524 may present an interface based on Nsmf services.

[0286] NEF 523 may provide a device for securely exposing services and capabilities provided by 3GPP network functions for third parties, internal exposure / re-exposure, application functions (e.g., AF 528), edge computing or fog computing systems, etc. In such embodiments, NEF 523 may authenticate, authorize and / or restrict AF. NEF 523 may also convert information exchanged with AF 528 and information exchanged with internal network functions. For example, NEF 523 may convert between AF service identifiers and internal 5GC information. NEF 523 may also receive information from other network functions based on the exposure capabilities of other network functions (NFs). The information may be stored at NEF 523 as structured data, or stored at a data storage NF using a standardized interface. The stored information may then be re-exposed to other NFs and AFs by NEF 523, and / or used for other purposes such as analysis. In addition, NEF 523 may present an interface based on Nnef services.

[0287] NRF 525 may support service discovery functionality, receive NF discovery requests from NF instances, and provide information about discovered NF instances to NF instances. NRF 525 also maintains information about available NF instances and services supported by these instances. As used herein, the term "instantiation" and the like may refer to the creation of an instance, and "instance" may refer to the specific occurrence of an object, which may occur, for example, during the execution of a program code. In addition, NRF 525 may present an interface based on Nnrf services.

[0288] PCF 526 may provide policy rules to the control plane functions to execute them, and may also support a unified policy framework for managing network behavior. PCF 526 may also implement FE to access subscription information related to policy decisions in the UDR of UDM 527. PCF 526 may communicate with AMF 521 via the N15 reference point between PCF 526 and AMF 521, which may include PCF 526 and AMF 521 in the visited network in the case of roaming scenarios. PCF 526 may communicate with AF 528 via the N5 reference point between PCF 526 and AF 528; and communicate with SMF 524 via the N7 reference point between PCF 526 and SMF 524. System 500 and / or CN 520 may also include an N24 reference point between PCF 526 (in the home network) and PCF 526 in the visited network. In addition, PCF 526 may present an interface based on Npcf services.

[0289] UDM 527 may process subscription-related information to support the handling of communication sessions by network entities, and may store subscription data of UE 501. For example, subscription data may be transmitted between UDM 527 and AMF via an N8 reference point between UDM 527 and AMF 521. UDM 527 may include two parts: application FE and UDR ( Figure 5 FE and UDR are not shown). UDR can store subscription data and policy data of UDM 527 and PCF 526, and / or structured data for exposure and application data of NEF 523 (including PFD for application detection, application request information of multiple UE 501). Nudr service-based interface can be presented by UDR 221 to allow UDM527, PCF 526 and NEF 523 to access specific sets of stored data, as well as read, update (e.g., add, modify), delete and subscribe to notifications of related data changes in UDR. UDM may include UDM-FE, which is responsible for handling credentials, location management, subscription management, etc. In different transactions, several different front ends can serve the same user. UDM-FE accesses subscription information stored in UDR, and performs authentication credential processing, user identification processing, access authorization, registration / mobility management and subscription management. UDR can interact with SMF 524 via the N10 reference point between UDM 527 and SMF 524. UDM 527 may also support SMS management, where SMS-FE implements similar application logic discussed previously. In addition, UDM 527 may present an interface based on Nudm services.

[0290] AF 528 can provide the influence of applications on traffic routing, provide access to NCE, and interact with the policy framework for policy control. NCE can be a mechanism that allows 5GC 520 and AF528 to provide information to each other via NEF 523, which can be used for edge computing implementation. In such implementations, network operators and third-party services can be hosted near the UE 501 access point of the attachment to achieve effective service delivery through reduced end-to-end delay and load on the transmission network. For edge computing implementation, 5GC can select UPF 502 near UE 501 and perform traffic steering from UPF 502 to DN 503 via N6 interface. This can be based on UE subscription data, UE location and information provided by AF 528. In this way, AF 528 can affect UPF (re) selection and traffic routing. Based on operator deployment, when AF 528 is considered a trusted entity, the network operator can allow AF 528 to interact directly with the relevant NF. In addition, AF 528 can present an interface based on Naf services.

[0291] NSSF 529 may select a set of network slice instances to serve UE 501. If necessary, NSSF 529 may also determine the allowed NSSAI and the mapping to the subscribed S-NSSAI. NSSF 529 may also determine the AMF set, or a list of candidate AMFs 521, to serve UE 501 based on appropriate configuration and possibly by querying NRF 525. The selection of a set of network slice instances for UE 501 may be triggered by AMF 521, where UE 501 registers by interacting with NSSF 529, which may result in changes to AMF 521. NSSF 529 may interact with AMF 521 via the N22 reference point between AMF 521 and NSSF 529; and may communicate with AMF 521 via the N31 reference point ( Figure 5 The NSSF 529 may communicate with another NSSF 529 in the visited network (not shown). In addition, the NSSF 529 may present an interface based on the Nnssf service.

[0292] As previously discussed, CN 520 may include SMSF, which may be responsible for SMS subscription checking and verification, and relaying SM messages to / from UE 501 to / from other entities, such as SMS-GMSC / IWMSC / SMS routers. SMS may also interact with AMF 521 and UDM 527 for notification procedures that UE 501 is available for SMS transmission (e.g., setting an unreachable flag for the UE and notifying UDM 527 when UE 501 is available for SMS).

[0293] CN 120 may also include Figure 5 Other elements not shown, such as data storage system / architecture, 5G-EIR, SEPP, etc. The data storage system may include SDSF, UDSF, etc. Any NF can communicate with UDSF ( Figure 5 The N18 reference point between the NF and the NF (not shown) stores or retrieves unstructured data in or from the UDSF (e.g., UE context). Individual NFs may share a UDSF for storing their respective unstructured data, or individual NFs may each have their own UDSF located at or near a single NF. In addition, the UDSF may present an interface based on the Nudsf service ( Figure 5 (not shown). The 5G-EIR may be a NF that checks the status of the PEI to determine whether to blacklist a specific equipment / entity from the network; and the SEPP may be a non-transparent proxy that performs topology hiding, message filtering, and policing on the inter-PLMN control plane interface.

[0294] Additionally, there may be more reference points and / or service-based interfaces between NF services in a NF; however, for clarity, Figure 5These interfaces and reference points are omitted. In one example, CN 520 may include an Nx interface, which is an inter-CN interface between an MME (e.g., MME 421) and an AMF 521, so as to enable interworking between CN 520 and CN 420. Other example interfaces / reference points may include an interface based on N5g-EIR services presented by 5G-EIR, an N27 reference point between an NRF in a visited network and an NRF in a home network; and an N31 reference point between an NSSF in a visited network and an NSSF in a home network.

[0295] Figure 6 An example of infrastructure equipment 600 according to various embodiments is shown. Infrastructure equipment 600 (or "system 600") can be implemented as a base station, a radio head, a RAN node (such as the RAN node 311 and / or AP 306 shown and described previously), an application server 330, and / or any other element / device discussed herein. In other examples, system 600 can be implemented in or by a UE.

[0296] System 600 includes application circuit 605, baseband circuit 610, one or more radio front end modules (RFEM) 615, memory circuit 620, power management integrated circuit (PMIC) 625, power tee circuit 630, network controller circuit 635, network interface connector 640, satellite positioning circuit 645 and user interface 650. In some embodiments, device 600 may include additional elements such as, for example, memory / storage, display, camera, sensor, or input / output (I / O) interface. In other embodiments, the following components may be included in more than one device. For example, the circuit may be included separately in more than one device for CRAN, vBBU or other similar implementations.

[0297] The application circuit 605 includes the following circuits such as, but not limited to: one or more processors (processor cores), cache memory, and one or more of the following: a low dropout regulator (LDO), an interrupt controller, a serial interface such as SPI, I 2C or general programmable serial interface module, real-time clock (RTC), timer-counter including interval timer and watchdog timer, general input / output (I / O or IO), memory card controller such as secure digital (SD) multimedia card (MMC) or similar products, universal serial bus (USB) interface, mobile industry processor interface (MIPI) interface and joint test access group (JTAG) test access port. The processor (or core) of application circuit 605 can be coupled with memory / storage element or can include memory / storage element, and can be configured to execute instructions stored in memory / storage device to enable various applications or operating systems to run on system 600. In some embodiments, the memory / storage element can be an on-chip memory circuit, which can include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory and / or any other type of memory device technology, such as those discussed herein.

[0298] The processor of the application circuit 605 may include, for example, one or more processor cores (CPUs), one or more application processors, one or more graphics processing units (GPUs), one or more reduced instruction set computing (RISC) processors, one or more Acorn RISC Machine (ARM) processors, one or more complex instruction set computing (CISC) processors, one or more digital signal processors (DSPs), one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, or any suitable combination thereof. In some embodiments, the application circuit 605 may include or may be a dedicated processor / controller for operating according to various embodiments herein. As an example, the processor of the application circuit 605 may include one or more Intel or Processor: Advanced Micro Devices (AMD) Processor, Accelerated Processing Unit (APU) or Processor; ARM-based processors licensed by ARM Holdings, Ltd., such as the ARM Cortex-A series processors provided by Cavium (TM), Inc. and MIPS-based designs from MIPS Technologies, Inc., such as the MIPS Warrior P-class processor; etc. In some embodiments, the system 600 may not utilize application circuit 605, and instead may include a dedicated processor / controller to process IP data received, for example, from an EPC or 5GC.

[0299] In some implementations, the application circuit 605 may include one or more hardware accelerators, which may be microprocessors, programmable processing devices, etc. The one or more hardware accelerators may include, for example, computer vision (CV) and / or deep learning (DL) accelerators. For example, the programmable processing device may be one or more field programmable devices (FPDs), such as field programmable gate arrays (FPGAs), etc.; programmable logic devices (PLDs), such as complex PLDs (CPLDs), high capacity PLDs (HCPLDs), etc.; ASICs, such as structured ASICs, etc.; programmable SoCs (PSoCs); etc. In such implementations, the circuits of the application circuit 605 may include logic blocks or logic architectures, as well as other interconnected resources that may be programmed to perform various functions, such as the processes, methods, functions, etc. of the various embodiments discussed herein. In such an embodiment, the circuitry of the application circuit 605 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), anti-fuse, etc.)) for storing logic blocks, logic architectures, data, etc. in a lookup table (LUT), etc.

[0300] Baseband circuit 610 may be implemented, for example, as a solder-in substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits. Figure X T discusses the various hardware electronic components of baseband circuit 610.

[0301] The user interface circuit 650 may include one or more user interfaces designed to enable a user to interact with the system 600 or peripheral component interfaces designed to enable peripheral components to interact with the system 600. The user interface may include, but is not limited to, one or more physical or virtual buttons (e.g., a reset button), one or more indicators (e.g., light emitting diodes (LEDs)), a physical keyboard or keypad, a mouse, a touch pad, a touch screen, a speaker or other audio transmitting device, a microphone, a printer, a scanner, a headset, a display screen or display device, etc. The peripheral component interface may include, but is not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, a power interface, etc.

[0302] The radio front end module (RFEM) 615 may include a millimeter wave (mmWave) RFEM and one or more sub-mmWave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-mmWave RFICs may be physically separated from the mmWave RFEM. The RFIC may include connections to one or more antennas or antenna arrays (see, e.g., below). Figure 8 Antenna array 811), and RFEM can be connected to multiple antennas. In an alternative implementation, both millimeter wave and sub-millimeter wave radio functions can be implemented in the same physical RFEM615 that combines both millimeter wave antennas and sub-millimeter waves.

[0303] The memory circuit 620 may include one or more of the following: a volatile memory including a dynamic random access memory (DRAM) and / or a synchronous dynamic random access memory (SDRAM), a non-volatile memory (NVM) including a high-speed electrically erasable memory (commonly referred to as a "flash memory"), a phase change random access memory (PRAM), a magnetoresistive random access memory (MRAM), etc., and may be combined with and The memory circuit 620 may be implemented as one or more of: a solder-in package integrated circuit, a socket memory module, and a plug-in memory card.

[0304] The PMIC 625 may include a voltage regulator, a surge protector, a power alarm detection circuit, and one or more backup power sources, such as a battery or capacitor. The power alarm detection circuit may detect one or more of a brownout (undervoltage) and a surge (overvoltage) condition. The power tee circuit 630 may provide power extracted from a network cable to provide both power and data connections for the infrastructure equipment 600 using a single cable.

[0305] The network controller circuit 635 may provide connectivity to the network using a standard network interface protocol such as Ethernet, Ethernet based on a GRE tunnel, Ethernet based on a multi-protocol label switching (MPLS), or some other suitable protocol. A physical connection may be used to provide a network connection to / from the infrastructure equipment 600 via a network interface connector 640, which may be an electrical connection (commonly referred to as a "copper interconnect"), an optical connection, or a wireless connection. The network controller circuit 635 may include one or more dedicated processors and / or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the network controller circuit 635 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0306] The positioning circuit 645 includes a circuit for receiving and decoding signals transmitted / broadcasted by a positioning network of a global satellite navigation system (GNSS). Examples of navigation satellite constellations (or GNSS) include the United States' Global Positioning System (GPS), Russia's Global Navigation System (GLONASS), the European Union's Galileo system, China's Beidou Navigation Satellite System, regional navigation systems or GNSS augmentation systems (e.g., using the Indian constellation (NAVIC), Japan's Quasi-Zenith Satellite System (QZSS), France's Doppler Orbit Chart and Satellite Integrated Radio Positioning (DORIS), etc. for navigation), etc. The positioning circuit 645 includes various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, etc. for facilitating OTA communications) to communicate with components of the positioning network such as navigation satellite constellation nodes. In some embodiments, the positioning circuit 645 may include a micro technology (micro PNT) IC for positioning, navigation, and timing that uses a master timing clock to perform position tracking / estimation without GNSS assistance. The positioning circuit 645 may also be part of or interact with the baseband circuit 610 and / or RFEM 615 to communicate with nodes and components of the positioning network. The positioning circuit 645 may also provide location data and / or time data to the application circuit 605, which may use the data to synchronize operations with various infrastructures (e.g., RAN node 311, etc.), etc.

[0307] Figure 6 The components shown may communicate with each other using interface circuitry that may include any number of bus and / or interconnect (IX) technologies, such as Industry Standard Architecture (ISA), Extended ISA (EISA), Peripheral Component Interconnect (PCI), Peripheral Component Interconnect Extended (PCIx), PCI express (PCIe), or any number of other technologies. The bus / IX may be a proprietary bus, such as used in SoC-based systems. Other bus / IX systems may be included, such as I 2 C interface, SPI interface, point-to-point interface and power bus, etc.

[0308] Figure 7 An example of a platform 700 (or "device 700") according to various embodiments is shown. In an embodiment, the computer platform 700 may be suitable for use as a UE 301, a UE 401, a UE 502, an application server 330, and / or any other element / device discussed herein. The platform 700 may include any combination of components shown in the example. The components of the platform 700 may be implemented as an integrated circuit (IC), a portion thereof, a discrete electronic device, or other modules, logic, hardware, software, firmware, or a combination thereof suitable for use in the computer platform 700, or implemented as components otherwise incorporated within a chassis of a larger system. Figure 7The block diagram is intended to show a high-level view of the components of computer platform 700. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other implementations.

[0309] Application circuit 705 includes circuits such as, but not limited to, one or more processors (or processor cores), cache memory, and LDO, interrupt controller, serial interface (such as SPI), I 2 The processor (or core) of the application circuit 705 may be coupled to or may include a memory / storage element and may be configured to execute instructions stored in the memory / storage element to enable various applications or operating systems to run on the system 700. In some embodiments, the memory / storage element may be an on-chip memory circuit that may include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory, and / or any other type of memory device technology, such as those discussed herein.

[0310] The processor of the application circuit 605 may include, for example, one or more processor cores, one or more application processors, one or more GPUs, one or more RISC processors, one or more ARM processors, one or more CISC processors, one or more DSPs, one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, multi-threaded processors, ultra-low voltage processors, embedded processors, some other known processing elements, or any suitable combination thereof. In some embodiments, the application circuit 605 may include or may be a dedicated processor / controller for operating according to various embodiments herein.

[0311] As an example, the processor of the application circuit 705 may include a processor based on Architecture Core TM Processors such as Quark TM 、Atom TM , i3, i5, i7 or MCU class processors, or available from Santa Clara, CA The processor of application circuit 705 may also be one or more of the following: Advanced Micro Devices (AMD) Processor or Accelerated Processing Unit (APU); from Inc.'s A5-A9 processors, Snapdragon by Technologies, Inc. TM Processor, Texas Instruments, Open Multimedia Applications Platform(OMAP) TM processors; MIPS-based designs from MIPS Technologies, Inc., such as the MIPS Warrior M-class, Warrior I-class, and Warrior P-class processors; ARM-based designs licensed from ARM Holdings, Ltd., such as the ARM Cortex-A, Cortex-R, and Cortex-M series processors; etc. In some specific implementations, the application circuit 705 can be part of a system on a chip (SoC), in which the application circuit 705 and other components are formed as a single integrated circuit or a single package, such as company( Edison Corporation TM or Galileo TM SoC board.

[0312] Additionally or alternatively, the application circuit 705 may include circuits such as, but not limited to, one or more field programmable devices (FPDs) such as FPGAs, etc.; programmable logic devices (PLDs) such as complex PLDs (CPLDs), high capacity PLDs (HCPLDs), etc.; ASICs such as structured ASICs, etc.; programmable SoCs (PSoCs); etc. In such embodiments, the circuits of the application circuit 705 may include logic blocks or logic structures, and other interconnected resources that can be programmed to perform various functions such as the processes, methods, functions, etc. of the various embodiments discussed herein. In such embodiments, the circuits of the application circuit 705 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), anti-fuse, etc.)) for storing logic blocks, logic structures, data, etc. in lookup tables (LUTs), etc.

[0313] Baseband circuit 710 may be implemented, for example, as a solder-in substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits. Figure 8 Various hardware electronic components of baseband circuit 710 are discussed.

[0314] The RFEM 715 may include a millimeter wave (mmWave) RFEM and one or more sub-millimeter wave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-millimeter wave RFICs may be physically separated from the mmWave RFEM. The RFIC may include connections to one or more antennas or antenna arrays (see, e.g., below). Figure 8 Antenna array 811), and the RFEM can be connected to multiple antennas. In an alternative implementation, both millimeter wave and sub-millimeter wave radio functions can be implemented in the same physical RFEM 715 that combines both millimeter wave antennas and sub-millimeter waves.

[0315] The memory circuit 720 may include any number and type of memory devices for providing a fixed amount of system memory. For example, the memory circuit 720 may include one or more of the following: volatile memory, including random access memory (RAM), dynamic RAM (DRAM) and / or synchronous dynamic RAM (SDRAM); and non-volatile memory, including high-speed electrically erasable memory (commonly referred to as flash memory), phase change random access memory (PRAM), magnetoresistive random access memory (MRAM), etc. The memory circuit 720 may be developed according to the Joint Electron Device Engineering Council (JEDEC) based low power double data rate (LPDDR) design such as LPDDR2, LPDDR3, LPDDR4, etc. The memory circuit 720 may be implemented as one or more of the following: a solder-in package integrated circuit, a single die package (SDP), a dual die package (DDP) or a quad die package (Q17P), a socketed memory module, a dual in-line memory module (DIMM) including a micro DIMM or a mini DIMM, and / or soldered to a motherboard via a ball grid array (BGA). In a low-power implementation, the memory circuit 720 may be an on-chip memory or register associated with the application circuit 705. To provide persistent storage of information such as data, applications, operating systems, etc., the memory circuit 720 may include one or more mass storage devices, which may include, among others, a solid-state disk drive (SSDD), a hard disk drive (HDD), a micro HDD, a resistive change memory, a phase change memory, a holographic memory, or a chemical memory. For example, the computer platform 700 may be combined with and Three-dimensional (3D) cross-point (XPOINT) memory.

[0316] Removable memory circuitry 723 may include devices, circuitry, housings / casings, ports or receptacles, etc., for coupling portable data storage devices to platform 700. These portable data storage devices may be used for mass storage, and may include, for example, flash memory cards (e.g., Secure Digital (SD) cards, micro SD cards, xD picture cards, etc.), as well as USB flash drives, optical disks, external HDDs, etc.

[0317] The platform 700 may further include an interface circuit (not shown) for connecting external devices to the platform 700. External devices connected to the platform 700 via the interface circuit include a sensor circuit 721 and an electromechanical component (EMC) 722, and a removable memory device coupled to a removable memory circuit 723.

[0318] Sensor circuitry 721 comprises a device, module, or subsystem that is intended to detect events or changes in its environment, and to send information about the detected events (sensor data) to some other device, module, subsystem, etc. Examples of such sensors include, among others: an inertial measurement unit (IMU) including an accelerometer, a gyroscope, and / or a magnetometer; a microelectromechanical system (MEMS) or a nanoelectromechanical system (NEMS) including a three-axis accelerometer, a three-axis gyroscope, and / or a magnetometer; a level sensor; a flow sensor; a temperature sensor (e.g., a thermistor); a pressure sensor; a barometric pressure sensor; a gravity meter; an altimeter; an image capture device (e.g., a camera or a lensless aperture); a light detection and ranging (LiDAR) sensor; a proximity sensor (e.g., an infrared radiation detector, etc.), a depth sensor, an ambient light sensor, an ultrasonic transceiver; a microphone or other similar audio capture device; etc.

[0319] EMC 722 includes devices, modules or subsystems that are intended to enable platform 700 to change its state, position and / or orientation or to move or control mechanisms or (sub) systems. In addition, EMC 722 can be configured to generate messages / signaling and send messages / signaling to other components of platform 700 to indicate the current state of EMC 722. Examples of EMC 722 include one or more power switches, relays (including electromechanical relays (EMR) and / or solid-state relays (SSR)), actuators (e.g., valve actuators, etc.), audible sound generators, visual warning devices, motors (e.g., DC motors, stepper motors, etc.), wheels, thrusters, propellers, claws, clamps, hooks and / or other similar electromechanical components. In an embodiment, platform 700 is configured to operate one or more EMC 722 based on one or more capture events and / or instructions or control signals received from service providers and / or various clients.

[0320] In some specific implementations, the interface circuit may connect the platform 700 to the positioning circuit 745. The positioning circuit 745 includes a circuit for receiving and decoding signals transmitted / broadcasted by the positioning network of the GNSS. Examples of navigation satellite constellations (or GNSS) may include the GPS of the United States, the GLONASS of Russia, the Galileo system of the European Union, the Beidou navigation satellite system of China, regional navigation systems or GNSS augmentation systems (e.g., NAVIC, QZSS of Japan, DORIS of France, etc.), etc. The positioning circuit 745 may include various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, etc. for facilitating OTA communication) to communicate with components of the positioning network such as navigation satellite constellation nodes. In some embodiments, the positioning circuit 745 may include a micro PNT IC that uses a master timing clock to perform position tracking / estimation without GNSS assistance. The positioning circuit 745 may also be part of the baseband circuit 610 and / or the RFEM 715 or interact with it to communicate with nodes and components of the positioning network. Positioning circuitry 745 may also provide position data and / or time data to application circuitry 705, which may use the data to synchronize operations with various infrastructure (e.g., radio base stations) for use in turn-by-turn navigation applications, etc.

[0321] In some implementations, the interface circuit may connect the platform 700 with a near field communication (NFC) circuit 740. The NFC circuit 740 is configured to provide contactless short-range communication based on the radio frequency identification (RFID) standard, where a magnetic field is sensed to enable communication between the NFC circuit 740 and an NFC-enabled device (e.g., an "NFC touch point") external to the platform 700. The NFC circuit 740 includes an NFC controller coupled to an antenna element and a processor coupled to the NFC controller. The NFC controller may be a chip / IC that provides NFC functionality to the NFC circuit 740 by executing an NFC controller firmware and an NFC stack. The NFC stack may be executed by the processor to control the NFC controller, and the NFC controller firmware may be executed by the NFC controller to control the antenna element to transmit a short-range RF signal. The RF signal may power a passive NFC tag (e.g., a microchip embedded in a sticker or wristband) to transfer stored data to the NFC circuit 740, or initiate data transfer between the NFC circuit 740 and another active NFC device (e.g., a smartphone or an NFC-enabled POS terminal) close to the platform 700.

[0322] The driver circuit 746 may include software and hardware elements for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to the platform 700. The driver circuit 746 may include various drivers to allow other components of the platform 700 to interact with or control various input / output (I / O) devices that may be present in or connected to the platform 700. For example, the driver circuit 746 may include: a display driver for controlling and allowing access to a display device, a touch screen driver for controlling and allowing access to a touch screen interface of the platform 700, a sensor driver for obtaining sensor readings of the sensor circuit 721 and controlling and allowing access to the sensor circuit 721, an EMC driver for obtaining an actuator position of the EMC 722 and / or controlling and allowing access to the EMC 722, a camera driver for controlling and allowing access to an embedded image capture device, and an audio driver for controlling and allowing access to one or more audio devices.

[0323] A power management integrated circuit (PMIC) 725 (also referred to as “power management circuit 725”) may manage power provided to various components of the platform 700. Specifically, the PMIC 725 may control power selection, voltage scaling, battery charging, or DC-DC conversion relative to the baseband circuit 710. When the platform 700 is capable of being powered by a battery 730, for example, when the device is included in UE 301, UE 401, UE 502, the PMIC 725 may be generally included.

[0324] In some embodiments, the PMIC 725 may control or otherwise be part of various power saving mechanisms of the platform 700. For example, if the platform 700 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 platform 700 may be powered off for short time intervals, thereby saving power. If there is no data traffic activity for an extended period of time, the platform 700 may transition to the RRC_Idle state, where the device is disconnected from the network and no operations such as channel quality feedback, handover, etc. are performed. The platform 700 enters a very low power state and performs paging, where the device wakes up periodically again to listen to the network and then powers off again. The platform 700 may not receive data in this state; in order to receive data, the platform must transition back to the RRC_Connected state. Additional power saving modes may prevent the device from using the network for longer than the paging interval (ranging from a few seconds to a few hours). During this time, the device is completely unable to connect to the network and can be completely powered off. Any data sent during this time will be significantly delayed, and it is assumed that the delay is acceptable.

[0325] The battery 730 can power the platform 700, but in some examples, the platform 700 can be mounted in a fixed location and can have a power source coupled to a power grid. The battery 730 can be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some implementations, such as in V2X applications, the battery 730 can be a typical lead-acid car battery.

[0326] In some implementations, the battery 730 may be a "smart battery" that includes or is coupled to a battery management system (BMS) or a battery monitoring integrated circuit. The BMS may be included in the platform 700 to track the state of charge (SoCh) of the battery 730. The BMS may be used to monitor other parameters of the battery 730, such as the state of health (SoH) and state of function (SoF) of the battery 730 to provide fault prediction. The BMS may transmit information about the battery 730 to the application circuit 705 or other components of the platform 700. The BMS may also include an analog-to-digital (ADC) converter that allows the application circuit 705 to directly monitor the voltage of the battery 730 or the current from the battery 730. The battery parameters may be used to determine actions that the platform 700 may perform, such as transmission frequency, network operation, sensing frequency, etc.

[0327] A power block or other power source coupled to the grid can be coupled to the BMS to charge the battery 730. In some examples, the power block 725 can be replaced with a wireless power receiver to obtain power wirelessly, for example, through a loop antenna in the computer platform 700. In these examples, a wireless battery charging circuit can be included in the BMS. The specific charging circuit selected can depend on the size of the battery 730 and therefore the required current. Charging can be performed using the aviation fuel standard published by the Aviation Fuel Alliance, the Qi wireless charging standard published by the Wireless Power Alliance, or the Rezence charging standard published by the Wireless Power Alliance.

[0328] The user interface circuit 750 includes various input / output (I / O) devices present in or connected to the platform 700, and includes one or more user interfaces designed to enable user interaction with the platform 700 and / or a peripheral component interface designed to enable peripheral components to interact with the platform 700. The user interface circuit 750 includes input device circuits and output device circuits. The input device circuit includes any physical or virtual means for accepting input, including, in particular, one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touch screen, a microphone, a scanner, a headset, etc. The output device circuit includes any physical or virtual means for displaying information or otherwise conveying information (such as sensor readings, actuator positions, or other similar information). The output device circuitry may include any number and / or combination of audio or visual displays, including, in particular, one or more simple visual outputs / indicators (e.g., binary status indicators (e.g., light emitting diodes (LEDs)) and multi-character visual outputs, or more complex outputs, such as display devices or touch screens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, projectors, etc.), where outputs of characters, graphics, multimedia objects, etc. are generated or produced by the operation of the platform 700. The output device circuitry may also include speakers or other audio emitting devices, printers, etc. In some embodiments, the sensor circuitry 721 may be used as an input device circuitry (e.g., an image capture device, a motion capture device, etc.) and one or more EMCs may be used as output device circuitry (e.g., an actuator for providing tactile feedback, etc.). In another example, an NFC circuit may be included to read an electronic tag and / or connect to another NFC-enabled device, the NFC circuitry including an NFC controller and a processing device coupled to an antenna element. The peripheral component interface may include, but is not limited to, a non-volatile memory port, a USB port, an audio jack, a power interface, etc.

[0329] Although not shown, the components of platform 700 may communicate with each other using a suitable bus or interconnect (IX) technology, which may include any number of technologies, including ISA, EISA, PCI, PCIx, PCIe, a time-triggered protocol (TTP) system, a FlexRay system, or any number of other technologies. The bus / IX may be a proprietary bus / IX, such as used in SoC-based systems. Other bus / IX systems, such as I 2 C interface, SPI interface, point-to-point interface and power bus, etc.

[0330] Figure 8 8 and 815. Exemplary components of a baseband circuit 810 and a radio front end module (RFEM) 815 are shown according to various embodiments. The baseband circuit 810 corresponds to Figure 6 The baseband circuit 610 and Figure 7 Baseband circuit 710. RFEM 815 respectively correspond to Figure 6 RFEM 615 and Figure 7 RFEM 715. As shown, RFEM 815 may include radio frequency (RF) circuitry 806, front end module (FEM) circuitry 808, and an antenna array 811 coupled together at least as shown.

[0331] The baseband circuit 810 includes circuits and / or control logic components that are configured to execute various radio / network protocols and radio control functions that enable communication with one or more radio networks via the RF circuit 806. The 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 circuit of the baseband circuit 810 may include fast Fourier transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuit of the baseband circuit 810 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functions. The implementation of the modulation / demodulation and encoder / decoder functions is not limited to these examples, and may include other suitable functions in other embodiments. The baseband circuit 810 is configured to process baseband signals received from the receive signal path of the RF circuit 806 and generate baseband signals for the transmit signal path of the RF circuit 806. The baseband circuit 810 is configured to communicate with the application circuit 605 / 705 (see Figure 6 and Figure 7 ) to generate and process baseband signals and control the operation of RF circuit 806. Baseband circuit 810 may handle various radio control functions.

[0332] The aforementioned circuits and / or control logic components of the baseband circuit 810 may include one or more single-core or multi-core processors. For example, the one or more processors may include a 3G baseband processor 804A, a 4G / LTE baseband processor 804B, a 5G / NR baseband processor 804C, or some other baseband processors 804D for other existing generations, generations under development or generations to be developed in the future (e.g., the sixth generation (6G), etc.). In other embodiments, some or all of the functions of the baseband processors 804A-804D may be included in a module stored in the memory 804G and executed via a central processing unit (CPU) 804E. In other embodiments, some or all of the functions of the baseband processors 804A to 804D may be provided as a hardware accelerator (e.g., FPGA, ASIC, etc.) loaded with an appropriate bitstream or logic block stored in a corresponding memory unit. In various embodiments, the memory 804G may store program code of a real-time OS (RTOS), which, when executed by the CPU 804E (or other baseband processor), will enable the CPU 804E (or other baseband processor) to manage resources of the baseband circuit 810, schedule tasks, etc. Examples of RTOS may include: Operating System Embedded (OSE) provided TM , by Mentor Nucleus RTOS provided TM , by Mentor Versatile Real-Time Executive (VRTX) provided by Express Provided by ThreadX TM ,Depend on FreeRTOS and REX OS provided by OpenKernel (OK) OKL4 provided, or any other suitable RTOS, such as those discussed herein. In addition, the baseband circuit 810 includes one or more audio digital signal processors (DSPs) 804F. The audio DSP 804F includes elements for compression / decompression and echo cancellation, and may include other suitable processing elements in other embodiments.

[0333] In some embodiments, each of processors 804A-804E includes a corresponding memory interface to send data to / receive data from memory 804G. Baseband circuit 810 may also include one or more interfaces for communicatively coupling to other circuits / devices, such as an interface for sending data to / receiving data from a memory external to baseband circuit 810; an interface for sending data to / receiving data from a memory external to the baseband circuit; Figures 6 to XApplication circuit interface for sending data to / receiving data from the application circuit 605 / 705 of T; Figure X RF circuit interface for sending data to / receiving data from the RF circuit 806 of T; for receiving data from one or more wireless hardware elements (e.g., near field communication (NFC) components, Low power consumption components, components, etc.) to send data / receive data from these wireless hardware elements; and a power management interface for sending power or control signals to / receiving power or control signals from the PMIC 725.

[0334] In an alternative embodiment (which can be combined with the above embodiment), the baseband circuit 810 includes one or more digital baseband systems, which are coupled to each other and to the CPU subsystem, the audio subsystem and the interface subsystem via an interconnection subsystem. The digital baseband subsystem can also be coupled to the digital baseband interface and the mixed signal baseband subsystem via another interconnection subsystem. Each of the interconnection subsystems may include a bus system, a point-to-point connector, a network on chip (NOC) structure and / or some other suitable bus or interconnection technology, such as those discussed herein. The audio subsystem may include a DSP circuit, a buffer memory, a program memory, a voice processing accelerator circuit, a data converter circuit such as an analog-to-digital converter circuit and a digital-to-analog converter circuit, an analog circuit including one or more of an amplifier and a filter, and / or other similar components. In one aspect of the present disclosure, the baseband circuit 810 may include a protocol processing circuit with one or more control circuit instances (not shown) to provide control functions for the digital baseband circuit and / or the radio frequency circuit (e.g., the radio front end module 815).

[0335] although Figure 8Not shown, but in some embodiments, the baseband circuit 810 includes various processing devices (e.g., a "multi-protocol baseband processor" or "protocol processing circuit") for operating one or more wireless communication protocols and various processing devices for implementing PHY layer functions. In these embodiments, the PHY layer functions include the aforementioned radio control functions. In these embodiments, the protocol processing circuit operates or implements various protocol layers / entities of one or more wireless communication protocols. In a first example, when the baseband circuit 810 and / or the RF circuit 806 are part of a millimeter wave communication circuit or some other suitable cellular communication circuit, the protocol processing circuit may operate LTE protocol entities and / or 5G / NR protocol entities. In the first example, the protocol processing circuit will operate MAC, RLC, PDCP, SDAP, RRC, and NAS functions. In a second example, when the baseband circuit 810 and / or the RF circuit 806 are part of a Wi-Fi communication system, the protocol processing circuit may operate one or more IEEE-based protocols. In the second example, the protocol processing circuit will operate Wi-Fi MAC and logical link control (LLC) functions. The protocol processing circuit may include one or more memory structures (e.g., 804G) for storing program code and data for operating protocol functions, and one or more processing cores for executing program code and performing various operations using data. The baseband circuit 810 may also support radio communications of more than one wireless protocol.

[0336] The various hardware elements of the baseband circuit 810 discussed herein may be implemented as, for example, a solder-in substrate including one or more integrated circuits (ICs), a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more ICs. In one example, the components of the baseband circuit 810 may be appropriately combined in a single chip or a single chipset, or disposed on the same circuit board. In another example, some or all of the components of the baseband circuit 810 and the RF circuit 806 may be implemented together, such as, for example, a system on a chip (SoC) or a system-level package (SiP). In another example, some or all of the components of the baseband circuit 810 may be implemented as a separate SoC communicatively coupled to the RF circuit 806 (or multiple instances of the RF circuit 806). In yet another example, some or all of the components of the baseband circuit 810 and the application circuit 605 / 705 may be implemented together as a separate SoC (e.g., a "multi-chip package") mounted to the same circuit board.

[0337] In some embodiments, the baseband circuit 810 may provide communications compatible with one or more radio technologies. For example, in some embodiments, the baseband circuit 810 may support communications with E-UTRAN or other WMANs, WLANs, WPANs. Embodiments in which the baseband circuit 810 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuits.

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

[0339] In some embodiments, the receive signal path of the RF circuit 806 may include a mixer circuit 806a, an amplifier circuit 806b, and a filter circuit 806c. In some embodiments, the transmit signal path of the RF circuit 806 may include a filter circuit 806c and a mixer circuit 806a. The RF circuit 806 may also include a synthesizer circuit 806d for synthesizing the frequencies used by the mixer circuit 806a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuit 806a of the receive signal path may be configured to down-convert the RF signal received from the FEM circuit 808 based on the synthesized frequency provided by the synthesizer circuit 806d. The amplifier circuit 806b may be configured to amplify the down-converted signal, and the filter circuit 806c 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 810 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 806a of the receive signal path may include a passive mixer, although the scope of the embodiments is not limited in this respect.

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

[0341] In some embodiments, the mixer circuit 806a of the receive signal path and the mixer circuit 806a of the transmit signal path may include two or more mixers and may be arranged for quadrature down-conversion and quadrature up-conversion, respectively. In some embodiments, the mixer circuit 806a of the receive signal path and the mixer circuit 806a of the transmit signal path may include two or more mixers and may be arranged for image suppression (e.g., Hartley image suppression). In some embodiments, the mixer circuit 806a of the receive signal path and the mixer circuit 806a of the transmit signal path may be arranged for direct down-conversion and direct up-conversion, respectively. In some embodiments, the mixer circuit 806a of the receive signal path and the mixer circuit 806a of the transmit signal path may be configured for superheterodyne operation.

[0342] 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 806 may include an analog-to-digital converter (ADC) and a digital-to-analog converter (DAC) circuit, and the baseband circuit 810 may include a digital baseband interface to communicate with the RF circuit 806.

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

[0344] In some embodiments, synthesizer circuit 806d 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 806d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

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

[0346] 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 810 or the application circuit 605 / 705 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 circuit 605 / 705.

[0347] The synthesizer circuit 806d of the RF circuit 806 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.

[0348] In some embodiments, the synthesizer circuit 806d 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 806 can include an IQ / polarity converter.

[0349] The FEM circuitry 808 may include a receive signal path that may include circuitry configured to operate on RF signals received from the antenna array 811, amplify the received signals, and provide an amplified version of the received signals to the RF circuitry 806 for further processing. The FEM circuitry 808 may also include a transmit signal path that may include circuitry configured to amplify transmit signals provided by the RF circuitry 806 for transmission by one or more antenna elements in the antenna array 811. In various embodiments, amplification by the transmit or receive signal path may be accomplished only in the RF circuitry 806, only in the FEM circuitry 808, or in both the RF circuitry 806 and the FEM circuitry 808.

[0350] In some embodiments, the FEM circuit 808 may include a TX / RX switch to switch between transmit mode and receive mode operation. The FEM circuit 808 may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit 808 may include an LNA to amplify the received RF signal and provide the amplified received RF signal as an output (e.g., to the RF circuit 806). The transmit signal path of the FEM circuit 808 may include a power amplifier (PA) for amplifying an input RF signal (e.g., provided by the RF circuit 806), and one or more filters for generating an RF signal for subsequent transmission by one or more antenna elements of the antenna array 811.

[0351] The antenna array 811 includes one or more antenna elements, each of which is configured to convert an electrical signal into a radio wave to travel through the air and convert the received radio wave into an electrical signal. For example, a digital baseband signal provided by the baseband circuit 810 is converted into an analog RF signal (e.g., a modulated waveform), which is amplified and transmitted via the antenna elements of the antenna array 811 including one or more antenna elements (not shown). The antenna elements may be omnidirectional, directional, or a combination thereof. The antenna elements may be formed into a variety of arrangements as known and / or discussed herein. The antenna array 811 may include a microstrip antenna or a printed antenna fabricated on the surface of one or more printed circuit boards. The antenna array 811 may be formed as a patch of metal foil of various shapes (e.g., a patch antenna) and may be coupled to the RF circuit 806 and / or the FEM circuit 808 using a metal transmission line or the like.

[0352] The processor of the application circuit 605 / 705 and the processor of the baseband circuit 810 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of the baseband circuit 810 can be used alone or in combination to perform layer 3, layer 2, or layer 1 functions, while the processor of the application circuit 605 / 705 can utilize data received from these layers (e.g., packet data) and further perform layer 4 functions (e.g., TCP and UDP layers). As mentioned herein, layer 3 may include an RRC layer, which will be described in further detail below. As mentioned herein, layer 2 may include a MAC layer, an RLC layer, and a PDCP layer, which will be described in further detail below. As mentioned herein, layer 1 may include a PHY layer of a UE / RAN node, which will be described in further detail below.

[0353] Fig. 9 Various protocol functions that can be implemented in a wireless communication device according to various embodiments are shown. Specifically, Fig. 9 An arrangement 900 is included that shows the interconnection between various protocol layers / entities. Various protocol layers / entities operating in conjunction with 5G / NR system standards and LTE system standards are provided. Fig. 9 The following description, but Fig. 9 Some or all aspects of the invention may also be applicable to other wireless communication network systems.

[0354] In addition to other higher layer functions not shown, the protocol layers of arrangement 900 may also include one or more of PHY 910, MAC 920, RLC 930, PDCP 940, SDAP 947, RRC 955, and NAS layer 957. These protocol layers may include one or more service access points (e.g., Fig. 9 Items 959, 956, 950, 949, 945, 935, 925 and 915).

[0355] PHY 910 can send and receive physical layer signals 905, which can be received from or sent to one or more other communication devices. Physical layer signals 905 may include one or more physical channels, such as those discussed herein. PHY 910 may also perform link adaptation or adaptive modulation and coding (AMC), power control, cell search (e.g., for initial synchronization and switching purposes) and other measurements used by higher layers (e.g., RRC 955). PHY 910 may also further perform error detection on transmission channels, forward error correction (FEC) encoding / decoding of transmission channels, modulation / demodulation of physical channels, interleaving, rate matching, mapping to physical channels, and MIMO antenna processing. In an embodiment, an instance of PHY 910 may process a request from an instance of MAC 920 via one or more PHY-SAP 915 and provide an indication thereto. According to some embodiments, the request and indication transmitted via PHY-SAP 915 may include one or more transmission channels.

[0356] An instance of MAC 920 may process requests from and provide indications to an instance of RLC 930 via one or more MAC-SAPs 925. These requests and indications transmitted via MAC-SAP 925 may include one or more logical channels. MAC 920 performs mapping between logical channels and transport channels, multiplexes MAC SDUs from one or more logical channels onto TBs to be delivered to PHY 910 via transport channels, demultiplexes MAC SDUs from TBs delivered from PHY 910 via transport channels to one or more logical channels, multiplexes MAC SDUs onto TBs, schedules information reporting, performs error correction via HARQ, and performs logical channel prioritization.

[0357] The MAC 920 handles the following transport channels:

[0358] - Broadcast Channel (BCH);

[0359] - Downlink Shared Channel (DL-SCH);

[0360] - Paging Channel (PCH);

[0361] - Uplink Shared Channel (UL-SCH);

[0362] - Random Access Channel (RACH).

[0363] When the UE 301 is configured with an SCG, two MAC 920 entities are configured to the UE 301: one for the MCG and one for the SCG. Unless otherwise specified, the functions of the different MAC 920 entities in the UE 301 operate independently. Unless otherwise specified, the timers and parameters used in each MAC 920 entity are configured independently. Unless otherwise specified, the service cell, C-RNTI, radio bearer, logical channel, upper and lower layer entities, LCG and HARQ entity considered by each MAC entity refer to those corresponding components mapped to the MAC entity. If the MAC 920 entity is configured with one or more SCells, each MAC entity has multiple DL-SCHs and may have multiple UL-SCHs and multiple RACHs; there is one DL-SCH, one UL-SCH and one RACH on the SpCell, and each SCell has one DL-SCH, zero or one UL-SCH and zero or one RACH. If the MAC 920 entity is not configured with any SCell, each MAC MAC 920 entity has one DL-SCH, one UL-SCH and one RACH.

[0364] According to various embodiments, a MAC CE is used to dynamically activate / deactivate candidate beams for BFR per uplink BWP. In these embodiments, the BFR candidate beam activation / deactivation for a BWP-specific MAC CE is identified by a MAC PDU subheader with a new LCID. Such a MAC CE may have fields as discussed above and may have fields as discussed above. Figure 1 The network can activate / deactivate the candidate beams for the BFR of UE 301 in a specific BWP by sending the above MAC CE to UE 301. After UE 301 sends HARQ-ACK to the network to acknowledge the PDSCH carrying the MAC CE, the new activated candidate beam set becomes valid at x time slots.

[0365] Semi-persistent scheduling (SPS) is configured by RRC 955 for each serving cell and each BWP. Activation and deactivation of DL SPS is independent between serving cells. For DL ​​SPS, DL allocations are provided by PDCCH and are stored or cleared based on L1 signaling indicating SPS activation or deactivation. When SPS is configured, RRC 955 configures the following parameters:

[0366] -cs-RNTI: CS-RNTI used for activation, deactivation and retransmission;

[0367] -nrofHARQ-Processes: number of configured HARQ processes for SPS;

[0368] - periodicity: The periodicity of the configured downlink allocation for SPS.

[0369] When SPS is released by upper layers, all corresponding configurations are released. After a downlink allocation is configured for SPS, the MAC entity shall sequentially consider the Nth downlink allocation to occur in a timeslot, for which:

[0370] (number of slots per frame × SFN + number of slots in a frame) = [(number of slots per frame × SFN 开始时间 +Time Slot 开始时间 )+N×periodicity×number of time slots per frame / 10] modulo (1024×number of time slots per frame)

[0371] SFN 开始时间 and time slot 开始时间 are the SFN and timeslot, respectively, of the first transmission of the PDSCH when (re)initializing the configured downlink assignment.

[0372] There are two types of transmissions without dynamic grants: configured grant type 1, in which the uplink grant is provided by RRC and stored as a configured uplink grant; and configured grant type 2, in which the uplink grant is provided by PDCCH and is stored or cleared as a configured uplink grant based on L1 signaling indicating activation or deactivation of the configured uplink grant.

[0373] Type 1 and Type 2 are configured by RRC 955 for each serving cell and each BWP. Multiple configurations can only be active simultaneously on different serving cells. For Type 2, activation and deactivation are independent between serving cells. For the same serving cell, the MAC 920 entity is configured with either Type 1 or Type 2. When configuring a configured grant Type 1, RRC 955 configures the following parameters:

[0374] -cs-RNTI: CS-RNTI used for retransmission;

[0375] - periodicity: the configured periodicity of grant type 1;

[0376] -timeDomainOffse (time domain offset): the time domain offset of the resource relative to SFN=0;

[0377] - timeDomainAllocation (time domain allocation): the allocation of configured uplink grants in the time domain containing startSymbolAndLength (i.e. SLIV in TS38.214);

[0378] -nrofHARQ-Processes: Number of HARQ processes used for configured grants.

[0379] When configured grant type 2, RRC 920 configures the following parameters:

[0380] -cs-RNTI: CS-RNTI used for activation, deactivation and retransmission;

[0381] - periodicity: the configured periodicity of grant type 2;

[0382] -nrofHARQ-Processes: Number of HARQ processes used for configured grants.

[0383] When the upper layers configure the serving cell with a configured grant type 1, the MAC 920 entity is used to:

[0384] 1>Store the uplink grant provided by the upper layer as the configured uplink grant for the indicated serving cell;

[0385] 1> Initialize or reinitialize the configured uplink grant to start in symbols according to timeDomainOffset and S (derived from SLIV as specified in TS 38.214 [7]), and reoccur periodically.

[0386] After an uplink grant is configured for a configured grant type 1, the MAC 920 entity considers the uplink grant to be associated with each symbol recurring, for each symbol:

[0387] [(SFN×number of time slots per frame×number of symbols per time slot)+(number of time slots in frame×number of symbols per time slot)+number of symbols in time slot]=(time domain offset×number of symbols per time slot+S+N×periodicity) modulo (1024×number of time slots per frame×number of symbols per time slot), all N>=0.

[0388] After an uplink grant is configured for a configured grant type 2, the MAC entity shall consider the uplink grant to be associated with each symbol recurring, for each symbol:

[0389] [(SFN × number of slots per frame × number of symbols per slot) + (number of slots in a frame × number of symbols per slot) + number of symbols in a slot] = [(SFN 开始时间 ×Number of slots per frame ×Number of symbols per slot + slot 开始时间 ×Number of symbols per time slot + symbol 开始时间 )+N×periodicity] modulo (1024×number of slots per frame×number of symbols per slot), all N>=0. Where SFN 开始时间 , Time Slot 开始时间 and Symbol 开始时间 These are respectively the SFN, timeslot and symbol of the first transmission opportunity of PUSCH when (re)initializing the configured uplink grant.

[0390] When the upper layer releases a configured uplink grant, all corresponding configurations shall be released and all corresponding uplink grants shall be cleared. The MAC 920 entity is used to:

[0391] 1> if the configured uplink grant confirmation has been triggered and not cancelled; and

[0392] 1> If the MAC entity allocates UL resources for new transmission, then:

[0393] 2> Instruct the multiplexing and assembly process to generate the configured authorization confirmation MAC CE;

[0394] 2>Cancel the triggered configured uplink grant confirmation.

[0395] For configured grant type 2, the MAC 920 entity clears the configured uplink grant immediately after the first transmission of the configured grant confirmation MAC CE triggered by the configured uplink grant deactivation. Retransmissions other than repetitions of the configured uplink grant shall use the uplink grant addressed to the CS-RNTI.

[0396] If the MAC 920 entity is configured with one or more SCells, the network can activate and deactivate the configured SCells. When the SCell is configured, the SCell is deactivated. The configured SCell is activated and deactivated by: receiving the SCell activation / deactivation MAC CE; and configuring the sCellDeactivationTimer timer according to the configured SCell (except the SCell configured with PUCCH (if any)): the associated SCell is deactivated when it expires. For each configured SCell, the MAC 920 entity is used to:

[0397] 1> If SCell activation / deactivation MAC CE is received, activate SCell:

[0398] 2> Activate the SCell according to the timing defined in TS 38.213; that is, apply normal SCell operation, including:

[0399] 3>SRS transmission on SCell;

[0400] 3> CSI report for SCell;

[0401] 3>PDCCH monitoring on SCell;

[0402] 3>PDCCH monitoring for SCell;

[0403] 3>PUCCH transmission on SCell (if configured).

[0404] 2> If the SCell is deactivated before receiving the SCell activation / deactivation MAC CE, then:

[0405] 3> Activate the DL BWP and ULBWP indicated by firstActiveDownlinkBWP-Id and firstActiveUplinkBWP-Id respectively;

[0406] 2> Start or restart the sCellDeactivationTimer associated with the SCell according to the timing defined in TS 38.213;

[0407] 2> (re)initialize any suspended configured uplink grants of configured grant type 1 associated with this SCell according to the stored configuration (if any), and start in symbol;

[0408] 2>Trigger Power Headroom (PHR).

[0409] 1> Otherwise, if SCell activation / deactivation MAC CE is received, deactivate SCell;

[0410] or

[0411] 1> If the sCellDeactivationTimer associated with the activated SCell expires,

[0412] but:

[0413] 2> Deactivate SCell according to the timing defined in TS 38.213;

[0414] 2> Stop the sCellDeactivationTimer associated with SCell;

[0415] 2>Stop the bwp-InactivityTimer associated with SCell;

[0416] 2> Deactivate any active BWP associated with SCell;

[0417] 2> Clear any configured downlink allocation and any configured uplink grant type 2 associated with the SCell respectively;

[0418] 2> Clear any PUSCH resources used for semi-persistent CSI reporting associated with the SCell;

[0419] 2>Suspend any configured uplink grant type 1 associated with the SCell;

[0420] 2>Flush all HARQ buffers associated with the SCell.

[0421] 1> If the PDCCH on the activated SCell indicates an uplink grant or a downlink allocation; or

[0422] 1> If the PDCCH on the serving cell scheduling the activated SCell indicates an uplink grant or downlink allocation for the activated SCell; or

[0423] 1> If a MAC PDU is transmitted in a configured uplink grant or is received in a configured downlink allocation, then:

[0424] 2>Restart the sCellDeactivationTimer associated with the SCell.

[0425] 1> If SCell is deactivated, then:

[0426] 2> Do not transmit SRS on SCell;

[0427] 2> Do not report CSI for SCell;

[0428] 2> Not transmitted on the UL-SCH on the SCell;

[0429] 2> Not transmitted on RACH on SCell;

[0430] 2>Do not monitor the PDCCH on the SCell;

[0431] 2>Do not monitor the PDCCH for SCell;

[0432] 2> PUCCH on SCell is not transmitted.

[0433] The HARQ feedback of the MAC PDU containing the SCell activation / deactivation MAC CE is not affected by the PCell, PSCell and PUCCH SCell interruption caused by SCell activation / deactivation in TS 38.133. When the SCell is deactivated, the ongoing random access procedure (if any) on the SCell is aborted.

[0434] A serving cell may be configured with one or more BWPs, and the maximum number of BWPs per serving cell is specified in TS38.213. BWP switching of a serving cell is used to simultaneously activate inactive BWPs and deactivate active BWPs. BWP switching is controlled by a PDCCH indicating a downlink allocation or uplink grant, by a bwp-InactivityTimer, by RRC 920 signaling, or by the MAC 920 entity itself when a random access procedure is initiated. Upon RRC (re)configuration of firstActiveDownlinkBWP-Id and / or firstActiveUplinkBWP-Id for a SpCell or activation of an SCell, the DLBWP and / or UL BWP (as specified in TS38.331) indicated by firstActiveDownlinkBWP-Id and / or firstActiveUplinkBWP-Id, respectively, is active without receiving a PDCCH indicating a downlink allocation or uplink grant. The active BWP for a serving cell is indicated by RRC 955 or PDCCH (as specified in TS 38.213). For unpaired spectrum, the DL BWP is paired with the UL BWP, and BWP switching is common for both UL and DL. For each activated serving cell configured with a BWP, the MAC 920 entity is used to:

[0435] 1> If BWP is activated, then:

[0436] 2> Transmit on UL-SCH on BWP;

[0437] 2> If PRACH timing is configured, it is transmitted on RACH on BWP;

[0438] 2> Monitor PDCCH on BWP;

[0439] 2> Transmit PUCCH on BWP (if configured);

[0440] 2> Report CSI for BWP;

[0441] 2> Transmit SRS on BWP (if configured);

[0442] 2> Receive DL-SCH on BWP;

[0443] 2> (Re)initialize any suspended configured uplink grants of configured grant type 1 on the active BWP according to the stored configuration (if any) and start in symbol.

[0444] 1> If BWP is deactivated, then:

[0445] 2> Not transmitting on UL-SCH on BWP;

[0446] 2> Not transmitting on RACH on BWP;

[0447] 2>Do not monitor PDCCH on BWP;

[0448] 2> PUCCH on BWP is not transmitted;

[0449] 2> Do not report CSI for BWP;

[0450] 2> Do not transmit SRS on BWP;

[0451] 2> Do not receive DL-SCH on BWP;

[0452] 2> Clear any configured downlink allocations and configured uplink grants of configured grant type 2 on the BWP;

[0453] 2> Suspend any configured uplink grants of configured grant type 1 on the inactive BWP.

[0454] When a random access procedure is initiated on a serving cell, after selecting a carrier for performing the random access procedure, for the selected carrier of the serving cell, the MAC 920 entity is used to:

[0455] 1> If the PRACH opportunity is not configured for an active UL BWP, then:

[0456] 2> Switch the active UL BWP to the BWP indicated by initialUplinkBWP;

[0457] 2> If the serving cell is SpCell, then:

[0458] 3> Switch the active DL BWP to the BWP indicated by initialDownlinkBWP.

[0459] 1> Otherwise:

[0460] 2> If the serving cell is SpCell, then:

[0461] 3> If the active DL BWP does not have the same bwp-Id as the active UL BWP, then:

[0462] 4> Switch the active DL BWP to a DL BWP with the same bwp-Id as the active UL BWP.

[0463] 1> If running, stop the bwp-InactivityTimer associated with the active DL BWP of the serving cell.

[0464] 1> If the serving cell is SCell, then:

[0465] 2> Stop the bwp-InactivityTimer associated with the active DL BWP of the SpCell if it is running.

[0466] 1> Perform a random access procedure on the active DL BWP of the SpCell and the active UL BWP of the serving cell.

[0467] If the MAC 920 entity receives a PDCCH for BWP switching of a serving cell, the MAC 920 entity is configured to:

[0468] 1> if there is no ongoing random access procedure associated with the serving cell; or

[0469] 1> If, upon receipt of the PDCCH addressed to the C-RNTI, an ongoing random access procedure associated with the serving cell is successfully completed, then:

[0470] 2> Perform BWP switching to the BWP indicated by PDCCH.

[0471] If the MAC 920 entity receives a PDCCH for BWP switching of a serving cell while a random access procedure associated with the serving cell is being performed in the MAC entity, it is up to the UE 301 to implement whether to switch the BWP or ignore the PDCCH for BWP switching, except for the PDCCH reception for BWP switching addressed to the C-RNTI to successfully complete the random access procedure (in this case, the UE 301 will perform a BWP switch to the BWP indicated by the PDCCH). Upon receiving a PDCCH for BWP switching other than a successful contention solution, if the MAC 920 entity decides to perform a BWP switch, the MAC 920 entity will stop the ongoing random access procedure and initiate a random access procedure after performing the BWP switch; if the MAC 920 decides to ignore the PDCCH for BWP switching, the MAC 920 entity will continue the ongoing random access procedure on the serving cell.

[0472] When an RRC (re)configuration for BWP switching of a serving cell is received while a random access procedure associated with the serving cell is ongoing in the MAC 920 entity, the MAC 920 entity shall stop the ongoing random access procedure and initiate a random access procedure after performing BWP switching.

[0473] For each activated serving cell configured with bwp-InactivityTimer, the MAC 920 entity is used to:

[0474] 1> If defaultDownlinkBWP-Id is configured and the active DL BWP is not the BWP indicated by defaultDownlinkBWP-Id; or

[0475] 1> If defaultDownlinkBWP-Id is not configured and the active DL BWP is not initialDownlinkBWP, then:

[0476] 2> if a PDCCH addressed to the C-RNTI or CS-RNTI indicating a downlink allocation or uplink grant is received on the active BWP; or

[0477] 2> If a PDCCH addressed to the C-RNTI or CS-RNTI indicating a downlink allocation or uplink grant is received for the active BWP; or

[0478] 2> If a MAC PDU is transmitted in a configured uplink grant or received in a configured downlink allocation, then:

[0479] 3> If there is no ongoing random access procedure associated with the serving cell; or

[0480] 3> If, upon receipt of the PDCCH addressed to the C-RNTI, an ongoing random access procedure associated with the serving cell is successfully completed, then:

[0481] 4> Start or restart the bwp-InactivityTimer associated with the active DL BWP.

[0482] 2> If the bwp-InactivityTimer associated with an active DL BWP expires, then:

[0483] 3> If defaultDownlinkBWP-Id is configured, then:

[0484] 4> Perform a BWP switch to the BWP indicated by defaultDownlinkBWP-Id.

[0485] 3> Otherwise:

[0486] 4>Execute BWP switch to initialDownlinkBWP.

[0487] If a random access procedure is initiated on an SCell, both the SCell and the SpCell are associated with the random access procedure.

[0488] 1> If PDCCH for BWP switching is received and the MAC entity switches the active DL BWP, then:

[0489] 2> If defaultDownlinkBWP-Id is configured and the MAC entity switches to a DL BWP not indicated by defaultDownlinkBWP-Id; or

[0490] 2> If defaultDownlinkBWP-Id is not configured and the MAC entity switches to a DL BWP that is not initialDownlinkBWP, then:

[0491] 3> Start or restart the bwp-InactivityTimer associated with the active DL BWP.

[0492] MAC 920 includes a HARQ entity for each serving cell with a configured uplink (including the case where supplementaryUplink is configured), which maintains multiple parallel HARQ processes. Each HARQ process supports one TB. Each HARQ process is associated with a HARQ process identifier. For UL transmissions with UL grants in RA responses, HARQ process identifier 0 is used. When the MAC 920 entity is configured with pusch-AggregationFactor>1, the parameter pusch-AggregationFactor provides the number of transmissions of the TB within a bundle of dynamic grants. After the initial transmission, pusch-AggregationFactor-1 HARQ retransmissions follow within the bundle. When the MAC 920 entity is configured with repK>1, the parameter repK provides the number of transmissions of the TB within a bundle of configured uplink grants. After the initial transmission, HARQ retransmissions follow within the bundle. For both dynamic grants and configured uplink grants, bundling operations rely on the HARQ entity to call the same HARQ process for each transmission that is part of the same bundle. Within a bundle, HARQ retransmissions are triggered without waiting for feedback from previous transmissions according to the pusch-AggregationFactor for dynamic grants and repK for configured uplink grants, respectively. After the initial uplink grant within the bundle is delivered to the HARQ entity, each transmission within the bundle is a separate uplink grant. Each HARQ process is associated with a HARQ buffer. New transmissions are performed on the resource and with the MCS indicated on the PDCCH, random access response or RRC. Retransmissions are performed on the resource and with the MCS indicated on the PDCCH or on the same resource if provided and with the same MCS as used for the last transmission attempt within the bundle.

[0493] An instance of RLC 930 may process requests from an instance of PDCP 940 and provide indications thereto via one or more radio link control service access points (RLC-SAPs) 935. These requests and indications transmitted via RLC-SAPs 935 may include one or more RLC channels. RLC 930 may operate in a variety of operating modes, including: transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM). RLC 930 may perform transmission of upper layer protocol data units (PDUs), error correction through automatic repeat request (ARQ) for AM data transmission, and concatenation, segmentation, and reassembly of RLC SDUs for UM and AM data transmission. RLC 930 may also perform resegmentation of RLC data PDUs for AM data transmission, reorder RLC data PDUs for UM and AM data transmission, detect duplicate data for UM and AM data transmission, discard RLC SDUs for UM and AM data transmission, detect protocol errors for AM data transmission, and perform RLC re-establishment.

[0494] An instance of PDCP 940 may process requests from an instance of RRC 955 and / or an instance of SDAP 947 via one or more Packet Data Convergence Protocol Service Points (PDCP-SAP) 945 and provide indications thereto. These requests and indications transmitted via PDCP-SAP 945 may include one or more radio bearers. PDCP 940 may perform header compression and decompression of IP data, maintain PDCP sequence numbers (SNs), perform in-order delivery of upper layer PDUs when lower layers are reestablished, eliminate duplication of lower layer SDUs when lower layers are reestablished for radio bearers mapped on RLC AM, encrypt and decrypt control plane data, perform integrity protection and integrity verification on control plane data, control timer-based data discard, and perform security operations (e.g., encryption, decryption, integrity protection, integrity verification, etc.).

[0495] An instance of SDAP 947 may process requests from one or more higher layer protocol entities via one or more SDAP-SAP 949 and provide instructions thereto. These requests and instructions transmitted via SDAP-SAP 949 may include one or more QoS flows. SDAP 947 may map QoS flows to DRBs and vice versa, and may also mark QFIs in DL packets and UL packets. A single SDAP entity 947 may be configured for a separate PDU session. In the UL direction, NG-RAN 310 may control the mapping of QoS flows to DRBs in two different ways (reflective mapping or explicit mapping). For reflective mapping, SDAP 947 of UE 301 may monitor the QFI of the DL packets of each DRB, and may apply the same mapping to packets flowing in the UL direction. For DRBs, SDAP 947 of UE 301 may map UL packets belonging to a QoS flow corresponding to the QoS flow ID and PDU session observed in the DL packets of the DRB. To enable reflective mapping, the NG-RAN 510 may mark the DL packets with a QoS flow ID over the Uu interface. The explicit mapping may involve the RRC 955 configuring the SDAP 947 with explicit mapping rules for QoS flows to DRBs, which may be stored and followed by the SDAP 947. In an embodiment, the SDAP 947 may be used only in NR implementations and may not be used in LTE implementations.

[0496] The RRC 955 may configure aspects of one or more protocol layers, which may include one or more instances of PHY 910, MAC 920, RLC 930, PDCP 940, and SDAP 947, via one or more Management Service Access Points (M-SAPs). In an embodiment, an instance of the RRC 955 may process requests from one or more NAS entities 957 and provide instructions thereto via one or more RRC-SAPs 956. The main services and functions of the RRC 955 may include broadcasting of system information (e.g., included in a MIB or SIB related to NAS), broadcasting of system information related to the access stratum (AS), paging, establishment, maintenance, and release of an RRC connection between the UE 301 and the RAN 310 (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), establishment, configuration, maintenance, and release of point-to-point radio bearers, security functions including key management, inter-RAT mobility, and measurement configuration for UE measurement reporting. These MIBs and SIBs may include one or more IEs, each of which may include a separate data field or data structure.

[0497] NAS 957 may form the highest layer of the control plane between UE 301 and AMF 521. NAS 957 may support the mobility and session management procedures of UE 301 to establish and maintain an IP connection between UE 301 and P-GW in the LTE system.

[0498] According to various embodiments, one or more protocol entities of the arrangement 900 may be implemented in the UE 301, the RAN node 311, the AMF 521 in the NR implementation or the MME 421 in the LTE implementation, the UPF 502 in the NR implementation or the S-GW 422 and the P-GW 423 in the LTE implementation, etc., for control plane or user plane communication protocol stacks between the aforementioned devices. In such embodiments, one or more protocol entities that may be implemented in one or more of the UE 301, the gNB 311, the AMF 521, etc. may communicate with corresponding peer protocol entities that may be implemented in or on another device (using the services of corresponding lower layer protocol entities to perform such communication). In some embodiments, the gNB-CU of gNB 311 may host the RRC 955, SDAP 947, and PDCP 940 of the gNB that control the operation of one or more gNB-DUs, and the gNB-DUs of gNB 311 may each host the RLC 930, MAC 920, and PHY 910 of gNB 311.

[0499] In a first example, the control plane protocol stack may include, in order from the highest layer to the lowest layer, NAS 957, RRC 955, PDCP 940, RLC 930, MAC 920, and PHY 910. In this example, an upper layer 960 may be built on top of NAS 957, the upper layer including an IP layer 961, SCTP 962, and an application layer signaling protocol (AP) 963.

[0500] In a NR specific implementation, AP 963 can be an NG application protocol layer (NGAP or NG-AP) 963 for the NG interface 313 defined between the NG-RAN node 311 and the AMF 521, or AP 963 can be an Xn application protocol layer (XnAP or Xn-AP) 963 for the Xn interface 312 defined between two or more RAN nodes 311.

[0501] The NG-AP 963 may support the functionality of the NG interface 313 and may include an elementary procedure (EP). The NG-AP EP may be an interaction unit between the NG-RAN node 311 and the AMF 521. The NG-AP 963 services may include two groups: UE-associated services (e.g., services related to the UE 301) and non-UE-associated services (e.g., services related to the entire NG interface instance between the NG-RAN node 311 and the AMF 521). These services may include functions including, but not limited to: a paging function for sending a paging request to the NG-RAN node 311 involved in a specific paging area; a UE context management function for allowing the AMF 521 to establish, modify and / or release the UE context in the AMF 521 and the NG-RAN node 311; a mobility function for the UE 301 in ECM-CONNECTED mode, for intra-system HO to support mobility within the NG-RAN, and for inter-system HO to support mobility from / to the EPS system; a NAS signaling transport function for transmitting or rerouting NAS messages between the UE 301 and the AMF 521; a NAS node selection function for determining the association between the AMF 521 and the UE 301; an NG interface management function for setting up the NG interface and monitoring errors through the NG interface; a warning message sending function for providing a means to transmit a warning message via the NG interface or to cancel an ongoing warning message broadcast; a NAS signaling transport function for transmitting or rerouting NAS messages between the UE 301 and the AMF 521; a NAS node selection function for determining the association between the AMF 521 and the UE 301; a ... via the CN 320 is a configuration transmission function for requesting and transmitting RAN configuration information (eg, SON information, performance measurement (PM) data, etc.) between two RAN nodes 311; and / or other similar functions.

[0502] The XnAP 963 may support the functionality of the Xn interface 312 and may include XnAP basic mobility procedures and XnAP global procedures. The XnAP basic mobility procedures may include procedures for handling UE mobility within the NG RAN 311 (or E-UTRAN 410), such as handover preparation and cancellation procedures, SN state transfer procedures, UE context retrieval and UE context release procedures, RAN paging procedures, procedures related to dual connectivity, etc. The XnAP global procedures may include procedures that are not related to a specific UE 301, such as Xn interface setup and reset procedures, NG-RAN update procedures, cell activation procedures, etc.

[0503] In an LTE specific implementation, the AP 963 may be an S1 application protocol layer (S1-AP) 963 for the S1 interface 313 defined between the E-UTRAN node 311 and the MME, or the AP 963 may be an X2 application protocol layer (X2AP or X2-AP) 963 for the X2 interface 312 defined between two or more E-UTRAN nodes 311.

[0504] The S1 application protocol layer (S1-AP) 963 may support the functionality of the S1 interface, and similar to the NG-AP discussed previously, the S1-AP may include an S1-AP EP. The S1-AP EP may be an interaction unit between the E-UTRAN node 311 and the MME 421 within the LTE CN 320. The S1-AP 963 services may include two groups: UE-associated services and non-UE-associated services. The functions performed by these services include, but are not limited to: E-UTRAN Radio Access Bearer (E-RAB) management, UE capability indication, mobility, NAS signaling transmission, RAN Information Management (RIM), and configuration transmission.

[0505] The X2AP 963 may support the functions of the X2 interface 312 and may include an X2AP basic mobility procedure and an X2AP global procedure. The X2AP basic mobility procedure may include a procedure for handling UE mobility within the E-UTRAN 320, such as a handover preparation and cancellation procedure, an SN state transfer procedure, a UE context retrieval and a UE context release procedure, a RAN paging procedure, a procedure related to dual connectivity, etc. The X2AP global procedure may include a procedure that is not related to a specific UE 301, such as an X2 interface setup and reset procedure, a load indication procedure, an error indication procedure, a cell activation procedure, etc.

[0506] The SCTP layer (alternatively referred to as the SCTP / IP layer) 962 can provide guaranteed delivery of application layer messages (e.g., NGAP or XnAP messages in NR implementations, or S1-AP or X2AP messages in LTE implementations). The SCTP 962 can ensure reliable delivery of signaling messages between the RAN node 311 and the AMF 521 / MME 421 based in part on the IP protocol supported by the IP 961. The Internet Protocol layer (IP) 961 can be used to perform packet addressing and routing functions. In some implementations, the IP layer 961 can deliver and transmit PDUs using point-to-point transport. In this regard, the RAN node 311 can include L2 and L1 layer communication links (e.g., wired or wireless) with the MME / AMF to exchange information.

[0507] In a second example, the user plane protocol stack may include SDAP 947, PDCP 940, RLC 930, MAC 920, and PHY 910 in order from the highest layer to the lowest layer. The user plane protocol stack may be used for communication between UE 301, RAN node 311, and UPF 502 in NR implementation, or communication between S-GW 422 and P-GW 423 in LTE implementation. In this example, the upper layer 951 may be built on top of SDAP 947 and may include a user datagram protocol (UDP) and IP security layer (UDP / IP) 952, a general packet radio service (GPRS) tunneling protocol (GTP-U) 953 for the user plane layer, and a user plane PDU layer (UP PDU) 963.

[0508] The transport network layer 954 (also referred to as the "transport layer") may be built on top of an IP transport, and GTP-U 953 may be used on top of a UDP / IP layer 952 (including a UDP layer and an IP layer) to carry user plane PDUs (UP-PDUs). The IP layer (also referred to as the "Internet layer") may be used to perform packet addressing and routing functions. The IP layer may assign IP addresses to user data packets, for example, in any of the IPv4, IPv6, or PPP formats.

[0509] GTP-U 953 can be used to carry user data within the GPRS core network and between the radio access network and the core network. For example, the transmitted user data can be a packet in any of the IPv4, IPv6 or PPP formats. UDP / IP 952 can provide a checksum for data integrity, a port number for addressing different functions at the source and destination, and encryption and authentication of the selected data stream. The RAN node 311 and the S-GW 422 can exchange user plane data via a protocol stack including an L1 layer (e.g., PHY 910), an L2 layer (e.g., MAC 920, RLC 930, PDCP 940 and / or SDAP 947), a UDP / IP layer 952, and a GTP-U 953 using an S1-U interface. The S-GW 422 and the P-GW 423 can exchange user plane data via a protocol stack including an L1 layer, an L2 layer, a UDP / IP layer 952, and a GTP-U 953 using an S5 / S8a interface. As previously discussed, the NAS protocol may support mobility and session management procedures of the UE 301 to establish and maintain an IP connection between the UE 301 and the P-GW 423 .

[0510] In addition, despite Fig. 9Not shown, but an application layer may exist above the AP 963 and / or transport network layer 954. The application layer may be a layer where a user of the UE 301, RAN node 311, or other network element interacts with a software application, for example, executed by the application circuitry 605 or the application circuitry 705, respectively. The application layer may also provide one or more interfaces for the software application to interact with the communication system (such as the baseband circuitry 810) of the UE 301 or RAN node 311. In some implementations, the IP layer and / or the application layer may provide the same or similar functionality as layers 5 to 7 of the Open Systems Interconnection (OSI) model, or portions thereof (e.g., OSI layer 7—application layer, OSI layer 6—presentation layer, and OSI layer 5—session layer).

[0511] Fig.10 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, Fig.10 A schematic diagram of hardware resources 1000 is shown, including one or more processors (or processor cores) 1010, one or more memory / storage devices 1020, and one or more communication resources 1030, each of which may be communicatively coupled via a bus 1040. For embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 1002 may be executed to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resources 1000.

[0512] Processor 1010 may include, for example, processor 1012 and processor 1014. Processor 1010 may be, for example, 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 DSP such as a baseband processor, an ASIC, an FPGA, a radio frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

[0513] The memory / storage device 1020 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 1020 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.

[0514] The communication resources 1030 may include an interconnect or network interface component or other suitable device to communicate with one or more peripheral devices 1004 or one or more databases 1006 via the network 1008. For example, the communication resources 1030 may include a wired communication component (e.g., for coupling via USB), a cellular communication component, an NFC component, (or Low power consumption) components, components and other communication components.

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

[0516] Fig.11 A method 1100 for beam failure recovery (BFR) that may be performed by a base station or access point is shown. According to some embodiments, the method 1100 may include detecting a beam failure instance, as shown in step 1102. According to some aspects, the method 1100 may also include initiating a beam failure recovery process by dynamically activating or deactivating a candidate beam for each uplink bandwidth part (BWP) associated with a user equipment (UE), as shown in step 1104.

[0517] According to some embodiments, method 1100 may further include generating a control signal to identify candidate beams for one or more activation or deactivation of at least one BWP associated with the UE, as shown in step 1106. Method 1100 may further include transmitting the control signal to the UE, as shown in step 1108.

[0518] according to Fig.11 In other embodiments not shown in FIG. 1 , method 1100 may further include identifying a media access control (MAC) protocol data unit (PDU) subheader having a new logical channel ID (LCID). In addition, method 1100 may further include a control signal as a media access (MAC) control element (CE).

[0519] According to some aspects, the method 1100 may further include identifying, to the UE, a serving cell identity within the MAC CE to which the MAC CE applies. In addition, according to some embodiments, the method 1100 may further include identifying, to the UE, a BWP ID indicating an uplink (UL) BWP to which the MAC CE applies. According to some aspects, the method 1100 may further include verifying the activated candidate beam set at a predetermined time slot in response to receiving a HARQ-ACK from the UE confirming the PDSCH carrying the MAC CE.

[0520] According to some embodiments, the control signal is a physical random access channel (PRACH) information element (IE).Thus, in some aspects, method 1100 may further include configuring a cell-specific subset of candidate beams for each uplink BWP by including an index of a candidate beam from a set of available candidate beams in a cell-specific uplink configuration message.

[0521] Fig.12 A method 1200 for beam failure recovery (BFR) that may be performed by a UE is shown. According to some embodiments, the method 1200 may include detecting a beam failure instance, as shown in step 1202. According to some aspects, the method 1200 may also include receiving a control signal that identifies one or more candidate beams for activation or deactivation of at least one BWP associated with the UE, as shown in step 1204. The method 1200 may also include selecting one or more candidate beams from the candidate beams for beam failure recovery in step 1206. The method 1200 may also include transmitting an ACK indicating the selection of the one or more candidate beams to a base station in step 1208. The method may also include implementing a beam failure recovery (BFR) process based on the selection of the one or more candidate beams in step 1210.

[0522] Figure 11 to Figure 12 The steps and / or functions in may be performed at least in part by one or more of the application circuit 605 or 705, the baseband circuit 610 or 710, and / or the processor 1014.

[0523] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes and / or methods described in the following example section. For example, the baseband circuit described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the following embodiments. For another example, the circuits associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the embodiments shown in the example section below.

[0524] Example

[0525] Example 1 includes a PRACH resource configuration for BFR (PRACH-ResourceConfigBFR) that may be configured based on a serving cell.

[0526] Example 2 includes the PRACH configuration of Example 1 and / or some other examples herein, wherein the RRC configuration is as follows:

[0527]

[0528] Example 3 includes the PRACH configuration of Example 2 and / or some other examples herein, wherein the candidate beam set for BFR (ie, candidateBeamsBFR-ToAddModList) should be included in the UplinkConfig configured by each serving cell ServingCellConfig.

[0529] Example 4 includes the PRACH configuration of Example 2 and / or some other examples herein, wherein the parameter maxNrofCandidateBeamsPerServingCell defines the maximum number of candidate beams for BFR per serving cell, for example, which can be set to 128.

[0530] Example 5 includes the PRACH configuration of Example 2 and / or some other examples herein, wherein invalid candidate beams for BFR to be removed (identified by resourceId of each PRACH-ResourceDedicatedBFR) should be added to the list candidateBeamsBFR-ToReleaseList.

[0531] Example 6 includes the PRACH configuration of Example 2 and / or some other examples herein, wherein the resourceId of the PRACH-ResourceDedicatedBFR should be uniquely ordered across the entire serving cell.

[0532] Example 7 includes the PRACH configuration of Examples 1 to 6 and / or some other examples herein, wherein all valid candidate beams for BFR are configured in a serving cell-specific manner, wherein for each uplink BWP, a cell-specific subset of candidate beams is configured for BFR as follows:

[0533]

[0534] Example 8 includes the PRACH configuration of Example 7 and / or some other examples herein, wherein BeamFailureRecoveryConfig is configured according to the uplink BWP; candidateBeamRSList is configured to include indices of candidate beams from a candidate beam set in a cell-specific UplinkConfig, rather than consisting of BFR beam RS resources.

[0535] Example 9 includes a MAC CE for dynamically activating and / or deactivating candidate beams for BFR per uplink BWP.

[0536] Example 10 includes the MAC CE of Example 9 and / or some other examples herein, wherein the BFR candidate beam activation / deactivation for the BWP-specific MAC CE is identified by a MAC PDU subheader with a new LCID.

[0537] Example 11 includes the MAC CE of Examples 9-10 and / or some other examples herein, wherein the MAC CE comprises a variable size including one or more fields from:

[0538] A serving cell ID field, which is used to indicate the identity of the serving cell to which the MAC CE applies, wherein the length of this field is 5 bits;

[0539] A BWP ID field, which is used to indicate the DL BWP of the code point of the DCI bandwidth partindicator field applicable to the MAC CE, wherein the length of the BWP ID field is 2 bits;

[0540] T i field, the T i The T field is used to indicate whether the PRACH-ResourceDedicatedBFR with resourceId i is configured in the candidateBeamsBFR-ToAddModList in UplinkConfig. This field indicates the activation / deactivation status of the PRACH-ResourceDedicatedBFR with resourceId i. Otherwise, the MAC entity shall ignore this T field. i Field, where T i The field is set to "1" to indicate that the PRACH-ResourceDedicatedBFR with resourceId i should be activated, where T iThe field is set to '0' to indicate that the PRACH-ResourceDedicatedBFR with resourceId i should be deactivated, and wherein the maximum number of activated PRACH-ResourceDedicatedBFRs may be 16; and

[0541] An R field, which includes one or more reserved bits to be set to "0".

[0542] Example 12 includes the MAC CE of Examples 9 to 11 and / or some other examples herein, wherein the network element may activate / deactivate candidate beams for the BFR of a UE in a specific BWP by sending the above-mentioned MAC CE to the UE, wherein the new activated candidate beam set becomes valid at x time slots after the UE sends a HARQ-ACK back to the network to confirm the PDSCH carrying the MAC CE.

[0543] Example 13 includes a method comprising:

[0544] An RRC message is received, where the RRC message includes a PRACH resource configuration for BFR (PRACH-ResourceConfigBFR), where the PRACH-ResourceConfigBFR is to be configured based on a serving cell.

[0545] Example 14 includes the method of Example 13 and / or some other examples herein, wherein PRACH-ResourceConfigBFR includes a resource identifier parameter (resourceId) to include a value for a maximum number of candidate beams based on each serving cell, and a beam resource BFR parameter (beamResourceBFR) indicates one of a BFR SSB resource or a BFR CSI-RS resource.

[0546] Example 15 includes the method of Examples 13 to 14 and / or some other examples in the present document, wherein the method includes identifying or causing identification of a candidate beam set for BFR in a candidateBeamsBFR-ToAddModList IE in an RRC message, wherein the candidateBeamsBFR-ToAddModList IE is included in an UplinkConfig IE of an RRC message configured by each serving cell, wherein each serving cell is configured via a ServingCellConfig IE in the RRC message.

[0547] Example 16 includes the method of Examples 13 to 15 and / or some other examples herein, wherein the RRC message includes a maximum number of candidate beams per serving cell parameter (maxNrofCandidateBeamsPerServingCell), wherein the maxNrofCandidateBeamsPerServingCell defines the maximum number of candidate beams for BFR per serving cell.

[0548] Example 17 includes the method of Example 16 and / or some other examples herein, wherein maxNrofCandidateBeamsPerServingCell can be set to a number from 1 to 128.

[0549] Example 18 includes the method of Examples 13 to 17 and / or some other examples herein, wherein the method includes identifying or causing identification in an RRC message of a set of invalid candidate beams for BFR to be removed in a candidateBeamsBFR-ToReleaseList IE, wherein the candidateBeamsBFR-ToReleaseList IE will include the resourceId of each PRACH-ResourceDedicatedBFR to be removed.

[0550] Example 19 includes the methods of Examples 13 to 18 and / or some other examples herein, wherein the resourceId of the PRACH-ResourceDedicatedBFR is uniquely ordered across the serving cell.

[0551] Example 20 includes the method of Examples 13 to 19 and / or some other examples in the present document, wherein all valid candidate beams for BFR are configured in a serving cell-specific manner in an RRC message via a beam failure recovery configuration (BeamFailureRecoveryConfig) IE, and wherein the method includes: for each uplink BWP, identifying or causing identification of a subset of cell-specific candidate beams in a candidate beam RS list (CandateBeamRSList) IE in the RRC message, wherein the candidateBeamRSList IE includes a value based on maxNrofCandidateBeamsPerServingCell.

[0552] Example 21 includes the method of Example 20 and / or some other examples herein, wherein the number of uplink BWPs is indicated by a maximum number of candidate beam parameters (maxNrofCandidateBeams) in an RRC message.

[0553] Example 22 includes the PRACH configuration of Examples 20 to 21 and / or some other examples herein, wherein BeamFailureRecoveryConfig is configured according to the uplink BWP and candidateBeamRSList is configured to include indices of candidate beams from a candidate beam set in a cell-specific UplinkConfig.

[0554] Example 23 includes the method of Examples 13 to 22 and / or some other examples in this document, wherein the method includes: receiving "BFR candidate beam activation / deactivation for BWP-specific MAC CE" via PDSCH, wherein the BFR candidate beam activation / deactivation for BWP-specific MAC CE is used to dynamically activate and / or deactivate candidate beams for BFR for each uplink BWP.

[0555] Example 24 includes the method of Example 23 and / or some other examples in the present document, wherein the method includes: determining or causing a determination that the received MAC CE is a BFR candidate beam activation / deactivation for a BWP-specific MAC CE based on an LCID value in an LCID field of a MAC PDU subheader in the received MAC CE.

[0556] Example 25 includes the method of Examples 23 to 24 and / or some other examples herein, wherein the BFR candidate beam activation / deactivation for the BWP-specific MACCE has a variable size and includes one or more fields, the one or more fields including:

[0557] A serving cell ID field, which is used to indicate the identity of the serving cell to which the MAC CE applies, wherein the length of this field is 5 bits;

[0558] A BWP ID field, which is used to indicate the DL BWP of the code point of the DCI bandwidth partindicator field applicable to the MAC CE, wherein the length of the BWP ID field is 2 bits;

[0559] T i field, the T i The T field is used to indicate whether the PRACH-ResourceDedicatedBFR with resourceId i is configured in the candidateBeamsBFR-ToAddModList in UplinkConfig, where this field indicates the activation / deactivation status of the PRACH-ResourceDedicatedBFR with resourceId i. Otherwise, the MAC entity shall ignore this T field. iField, where T i The field is set to "1" to indicate that the PRACH-ResourceDedicatedBFR with resourceId i is to be activated, where T i The PRACH-ResourceDedicatedBFR field is set to '0' to indicate that the PRACH-ResourceDedicatedBFR with resourceId i is to be deactivated; and

[0560] An R field, which includes one or more reserved bits to be set to "0".

[0561] Example 26 includes the method of Example 25 and / or some other examples herein, wherein the maximum number of activated PRACH-ResourceDedicatedBFRs is 16.

[0562] Example 27 includes the method of Examples 23 to 26 and / or some other examples herein, wherein the method includes transmitting or causing transmission of HARQ-ACK feedback based on proper reception and / or decoding of a received MAC CE, and wherein the new activated candidate beam set indicated by the received MAC CE becomes valid at X time slots after transmission of the HARQ-ACK feedback.

[0563] Example 28 includes the method of Examples 13 to 27 and / or some other examples herein, wherein the method is to be performed by a user equipment (UE) or a radio access network (RAN) node.

[0564] Example 29 may include an apparatus comprising means for performing one or more elements of a method described in or related to any of Examples 1-28, or any other method or process described herein.

[0565] Example 30 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 a method described or related to any of Examples 1-28 or any other method or process described herein.

[0566] Example 31 may include an apparatus comprising logic components, modules, or circuits for performing one or more elements of the method described in or related to any of Examples 1 to 28, or any other method or process described herein.

[0567] Example 32 may include a method, technique, or process described in or related to any of Examples 1-28, or a portion or component thereof.

[0568] Example 33 may include a device comprising: one or more processors and one or more computer-readable media, the one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process, or portion thereof, described in or related to any one of Examples 1 to 28.

[0569] Example 34 may include a signal as described or related to any of Examples 1 to 28, or a portion or component thereof.

[0570] Example 35 may include a frame, datagram, packet, PDU and / or SDU, or a portion or component thereof, as described or associated with any of Examples 1 to 28.

[0571] Example 36 may include a method of communicating in a wireless network as shown and described herein.

[0572] Example 37 may include a system for providing wireless communications as shown and described herein.

[0573] Example 38 may include an apparatus for providing wireless communications as shown and described herein.

[0574] Unless explicitly stated otherwise, any of the above examples may be combined with any other example (or combination of examples). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. Modifications and variations are possible in view of the above teachings or may be obtained from the practice of the various embodiments.

[0575] abbreviation

[0576] For the purposes of this document, the following abbreviations may be applied to the examples and implementations discussed herein but are not intended to be limiting.

[0577] 3GPP Third Generation Partnership Project

[0578] 4G Fourth Generation

[0579] 5G Fifth Generation

[0580] 5GC 5G Core Network

[0581] ACK

[0582] AF Application Function

[0583] AM Confirmation Mode

[0584] AMBR Aggregate Maximum Bit Rate

[0585] AMF Access and Mobility Management Function

[0586] AN Access Network

[0587] ANR Automatic Neighbor Relation

[0588] AP application protocol, antenna port, access point

[0589] API Application Programming Interface

[0590] APN Access Point Name

[0591] ARP Assignment Retention Priority

[0592] ARQ Automatic Repeat Request

[0593] AS Access Layer

[0594] ASN.1 Abstract Syntax Notation

[0595] AUSF authentication server function

[0596] AWGN Additive White Gaussian Noise

[0597] BCH Broadcast Channel

[0598] BER Bit Error Rate

[0599] BLER Block Error Rate

[0600] BPSK Binary Phase Shift Keying

[0601] BRAS Broadband Remote Access Server

[0602] BSS Business Support System

[0603] BS Base Station

[0604] BSR Buffer Status Report

[0605] BW Bandwidth

[0606] BWP Bandwidth Part

[0607] C-RNTI Cell Radio Network Temporary Identifier

[0608] CA Carrier Aggregation, Certification Authority

[0609] CAPEX Capital Expenditure

[0610] CBRA Contention-based random access

[0611] CC component carrier, country code, encryption checksum

[0612] CCA Clear Channel Assessment

[0613] CCE Control Channel Element

[0614] CCCH Common Control Channel

[0615] CE Coverage Enhancement

[0616] CDM Content Delivery Network

[0617] CDMA Code Division Multiple Access

[0618] CFRA Contention-free random access

[0619] CG Cell Group

[0620] CI Cell ID

[0621] CID Cell ID (eg, positioning method)

[0622] CIM Common Information Model

[0623] CIR Carrier to Interference Ratio

[0624] CK Cryptographic Key

[0625] CM Connection Management, Conditionally Mandatory

[0626] CMAS Commercial Mobile Alert Service

[0627] CMD command

[0628] CMS Cloud Management System

[0629] CO Conditional optional

[0630] CoMP Coordinated Multipoint

[0631] CORESET Control Resource Set

[0632] COTS Commercial Off-the-Shelf

[0633] CP Control Plane, Cyclic Prefix, Attachment Point

[0634] CPD Connection Point Descriptor

[0635] CPE user terminal equipment

[0636] CPICH Common Pilot Channel

[0637] CQI Channel Quality Indicator

[0638] CPU CSI processing unit, central processing unit

[0639] C / R Command / Response field bit

[0640] CRAN Cloud Radio Access Network, Cloud RAN

[0641] CRB Common Resource Block

[0642] CRC Cyclic Redundancy Check

[0643] CRI Channel State Information Resource Indicator, CSI-RS Resource Indicator

[0644] C-RNTI Cell RNTI

[0645] CS Circuit Switched

[0646] CSAR Cloud Service Archive

[0647] CSI Channel State Information

[0648] CSI-IM CSI interference measurement

[0649] CSI-RS CSI reference signal

[0650] CSI-RSRP CSI reference signal received power

[0651] CSI-RSRQ CSI reference signal reception quality

[0652] CSI-SINR CSI signal to interference plus noise ratio

[0653] CSMA Carrier Sense Multiple Access

[0654] CSMA / CA CSMA with collision avoidance

[0655] CSS Common Search Space, Cell Specific Search Space

[0656] CTS Clear to Send

[0657] CW codeword

[0658] CWS Contention Window Size

[0659] D2D Device to Device

[0660] DC Dual Connection, Direct Current

[0661] DCI Downlink Control Information

[0662] DF deployment preferences

[0663] DL Downlink

[0664] DMTF Distributed Management Task Force

[0665] DPDK Data Plane Development Kit

[0666] DM-RS, DMRS Demodulation Reference Signal

[0667] DN Data Network

[0668] DRB Data Radio Bearer

[0669] DRS Discovery Reference Signal

[0670] DRX Discontinuous Reception

[0671] DSL Domain Specific Language, Digital Subscriber Line

[0672] DSLAM DSL Access Multiplexer

[0673] DwPTS Downlink Pilot Time Slot

[0674] E-LAN ​​Ethernet Local Area Network

[0675] E2E End-to-End

[0676] ECCA Extended Clear Channel Assessment, Extended CCA

[0677] ECCE Enhanced Control Channel Element, Enhanced CCE

[0678] ED Energy Detection

[0679] EDGE Enhanced Data Rates for GSM Evolution (GSM Evolution)

[0680] EGMF exposes governance management functions

[0681] EGPRS Enhanced GPRS

[0682] EIR Equipment Identity Register

[0683] eLAA Enhanced License Assisted Access, enhanced LAA

[0684] EM Component Manager

[0685] eMBB Enhanced Mobile Broadband

[0686] eMBMS Evolved MBMS

[0687] EMS Component Management System

[0688] eNB Evolved Node B, E-UTRAN Node B

[0689] EN-DC E-UTRA-NR Dual Connectivity

[0690] EPC Evolved Packet Core

[0691] EPDCCH Enhanced PDCCH, Enhanced Physical Downlink Control Channel

[0692] EPRE Energy per resource element

[0693] EPS Evolved Packet System

[0694] EREG Enhanced REG, enhanced resource element group

[0695] ETSI European Telecommunications Standards Institute

[0696] ETWS Earthquake and Tsunami Warning System

[0697] eUICC embedded UICC, embedded universal integrated circuit card

[0698] E-UTRA Evolved UTRA

[0699] E-UTRAN Evolved UTRAN

[0700] F1AP F1 Application Protocol

[0701] F1-C F1 control plane interface

[0702] F1-U F1 User Plane Interface

[0703] FACCH Fast Associated Control Channel

[0704] FACCH / F Fast Associated Control Channel / Full Rate

[0705] FACCH / H Fast Associated Control Channel / Half Rate

[0706] FACH Forward Access Channel

[0707] FAUSCH Fast Uplink Signalling Channel

[0708] FB Function Block

[0709] FBI Feedback

[0710] FCC Federal Communications Commission

[0711] FCCH Frequency Correction Channel

[0712] FDD Frequency Division Duplex

[0713] FDM Frequency Division Multiplexing

[0714] FDMA Frequency Division Multiple Access

[0715] FE Front End

[0716] FEC Forward Error Correction

[0717] FFS for further study

[0718] FFT Fast Fourier Transform

[0719] feLAA Further Enhanced License Assisted Access, further enhanced LAA

[0720] FN Frame Number

[0721] FPGA Field Programmable Gate Array

[0722] FR Frequency Range

[0723] G-RNTI GERAN Radio Network Temporary Identity

[0724] GERAN GSM EDGE RAN, GSM EDGE Radio Access Network

[0725] GGSN Gateway GPRS Support Node

[0726] GLONASS GLObal'naya NAvigatsionnaya Sputnikovaya Sistema (Chinese: Global Navigation Satellite System)

[0727] gNB Next Generation Node B

[0728] gNB-CU gNB centralized unit, next generation Node B centralized unit

[0729] gNB-DU gNB distributed unit, next generation Node B distributed unit

[0730] GNSS Global Navigation Satellite System

[0731] GPRS General Packet Radio Service

[0732] GSM Global System for Mobile Communications, Mobile Experts Group

[0733] GTP GPRS Tunneling Protocol

[0734] GTP-U GPRS Tunneling Protocol for the User Plane

[0735] GUMMEI Globally Unique MME Identifier

[0736] GUTI Globally Unique Temporary UE Identifier

[0737] HARQ Hybrid ARQ, Hybrid Automatic Repeat Request

[0738] HANDO,HO switch

[0739] HFN Superframe Number

[0740] HHO Hard Handover

[0741] HLR Home Location Register

[0742] HN Home Network

[0743] HPLMN Home Public Land Mobile Network

[0744] HSDPA High Speed ​​Downlink Packet Access

[0745] HSN Hopping Sequence Number

[0746] HSPA High Speed ​​Packet Access

[0747] HSS Home Subscriber Server

[0748] HSUPA High Speed ​​Uplink Packet Access

[0749] HTTP Hypertext Transfer Protocol

[0750] HTTPS Hypertext Transfer Protocol Secure (https is http / 1.1 over SSL (i.e. port 443))

[0751] I-Block Information Block

[0752] ICCID Integrated Circuit Card Identifier

[0753] ICIC Inter-cell Interference Coordination

[0754] ID

[0755] IDFT Inverse Discrete Fourier Transform

[0756] IE Information Elements

[0757] IEEE Institute of Electrical and Electronics Engineers

[0758] IEI Information Element Identifier

[0759] IEIDL Information Element Identifier Data Length

[0760] IETF Internet Engineering Task Force

[0761] IF Infrastructure

[0762] IM Interference Measurement, Intermodulation, IP Multimedia

[0763] IMC IMS credentials

[0764] IMEI International Mobile Equipment Identity

[0765] IMGI International Mobile Group Identity

[0766] IMPI IP Multimedia Privacy Identity

[0767] IMPU IP Multimedia Public Identity

[0768] IMS IP Multimedia Subsystem

[0769] IMSI International Mobile Subscriber Identity

[0770] IoT

[0771] IP Internet Protocol

[0772] IPsec IP security, Internet Protocol security

[0773] IP-CAN IP connection access network

[0774] IP-M IP Multicast

[0775] IPv4 Internet Protocol version 4

[0776] IPv6 Internet Protocol version 6

[0777] IR

[0778] IRP Integration Reference Point

[0779] ISDN Integrated Services Digital Network

[0780] ISIM IM Service Identity Module

[0781] ISO International Organization for Standardization

[0782] ISP Internet Service Provider

[0783] IWF interworking function

[0784] I-WLAN Intercommunication WLAN

[0785] K is the constraint length of the convolutional code, USIM individual key

[0786] kB kilobyte (1000 bytes)

[0787] kbps kilobits per second

[0788] Kc Cryptographic key

[0789] Ki Individual user authentication key

[0790] KPI Key Performance Indicator

[0791] KQI Key Quality Indicator

[0792] KSI Key Set Identifier

[0793] ksps kilosymbols per second

[0794] KVM Kernel Virtual Machine

[0795] L1 Layer 1 (physical layer)

[0796] L1-RSRP Layer 1 reference signal received power

[0797] L2 Layer 2 (Data Link Layer)

[0798] L3 Layer 3 (Network Layer)

[0799] LAA License Assisted Access

[0800] LAN Local Area Network

[0801] LBT Listen before you speak

[0802] LCM Lifecycle Management

[0803] LCR Low Chip Rate

[0804] LCS Location Services

[0805] LI layer indicator

[0806] LLC Logical Link Control, Low Layer Compatibility

[0807] LPLMN Local PLMN

[0808] LPP LTE Positioning Protocol

[0809] LSB Least Significant Bit

[0810] LTE Long Term Evolution

[0811] LWA LTE-WLAN Aggregation

[0812] LWIP LTE / WLAN radio level integration with IPsec tunneling

[0813] LTE Long Term Evolution

[0814] M2M Machine to Machine

[0815] MAC Medium Access Control (Protocol Layer Context)

[0816] MAC Message Authentication Code (Security / Cryptography Context)

[0817] MAC-A MAC for authentication and key agreement (TSG T WG3 context)

[0818] MAC-I MAC for data integrity of signalling messages (TSG T WG3 context)

[0819] MANO Management and Orchestration

[0820] MBMS Multimedia Broadcast Multicast Service

[0821] MBSFN Multimedia Broadcast Multicast Service Single Frequency Network

[0822] MCC Mobile Country Code

[0823] MCG Master Cell Group

[0824] MCOT Maximum Channel Occupancy Time

[0825] MCS Modulation and Coding Scheme

[0826] MDAF Management Data Analysis Function

[0827] MDAS Management Data Analysis Service

[0828] Minimization of MDT-driven testing

[0829] ME Mobile Equipment

[0830] MeNB Master eNB

[0831] MER message error rate

[0832] MGL Measurement Gap Length

[0833] MGRP measurement gap repetition period

[0834] MIB Master Information Block, Management Information Base

[0835] MIMO Multiple Input Multiple Output

[0836] MLC Mobile Location Center

[0837] MM Mobility Management

[0838] MME Mobility Management Entity

[0839] MN Master Node

[0840] MO measurement object, mobile station calling

[0841] MPBCH MTC Physical Broadcast Channel

[0842] MPDCCH MTC Physical Downlink Control Channel

[0843] MPDSCH MTC Physical Downlink Shared Channel

[0844] MPRACH MTC Physical Random Access Channel

[0845] MPUSCH MTC Physical Uplink Shared Channel

[0846] MPLS Multi-Protocol Label Switching

[0847] MS Mobile Station

[0848] MSB Most Significant Bit

[0849] MSC Mobile Switching Center

[0850] MSI minimum system information, MCH scheduling information

[0851] MSID Mobile Station Identifier

[0852] MSIN Mobile Station Identification Number

[0853] MSISDN Mobile Subscriber ISDN Number

[0854] MT mobile station called, mobile terminal

[0855] MTC Machine Type Communication

[0856] mMTC Massive MTC, massive machine type communication

[0857] MU-MIMO Multi-User MIMO

[0858] MWUS MTC wake-up signal, MTC WUS

[0859] NACK Negative Acknowledgement

[0860] NAI Network Access Identifier

[0861] NAS Non-Access Stratum, Non-Access Stratum

[0862] NCT Network Connection Topology

[0863] NEC network capabilities exposed

[0864] NE-DC NR-E-UTRA dual connectivity

[0865] NEF Network Exposure Function

[0866] NF Network Function

[0867] NFP Network Forwarding Path

[0868] NFPD Network Forwarding Path Descriptor

[0869] NFV Network Function Virtualization

[0870] NFVI NFV Infrastructure

[0871] NFVO NFV Orchestrator

[0872] NG Next generation, next generation

[0873] NGEN-DC NG-RAN E-UTRA-NR Dual Connectivity

[0874] NM Network Manager

[0875] NMS Network Management System

[0876] N-PoP Network Point of Presence

[0877] NMIB, N-MIB Narrowband MIB

[0878] NPBCH Narrowband Physical Broadcast Channel

[0879] NPDCCH Narrowband Physical Downlink Control Channel

[0880] NPDSCH Narrowband Physical Downlink Shared Channel

[0881] NPRACH Narrowband Physical Random Access Channel

[0882] NPUSCH Narrowband Physical Uplink Shared Channel

[0883] NPSS Narrowband Primary Synchronization Signal

[0884] NSSS Narrowband Secondary Synchronization Signal

[0885] NR New air interface, neighbor relationship

[0886] NRF NF Repository Functionality

[0887] NRS Narrowband Reference Signal

[0888] NS Network Services

[0889] NSA Non-standalone operation mode

[0890] NSD Network Service Descriptor

[0891] NSR Network Service Record

[0892] NSSAI Network Slice Selection Assistance Information

[0893] S-NNSAI Single NSSAI

[0894] NSSF network slice selection function

[0895] NW Network

[0896] NWUS Narrowband wake-up signal, narrowband WUS

[0897] NZP Non Zero Power

[0898] O&M Operation and Maintenance

[0899] ODU2 Optical Channel Data Unit - Type 2

[0900] OFDM Orthogonal Frequency Division Multiplexing

[0901] OFDMA Orthogonal Frequency Division Multiple Access

[0902] OOB Out of Band

[0903] OPEX Operational Expenses

[0904] OSI Other System Information

[0905] OSS Operation Support System

[0906] OTA

[0907] PAPR Peak to Average Power Ratio

[0908] PAR Peak to Average Ratio

[0909] PBCH Physical Broadcast Channel

[0910] PC Power Control, Personal Computer

[0911] PCC primary component carrier, primary CC

[0912] PCell Primary Cell

[0913] PCI Physical Cell ID, Physical Cell Identity

[0914] PCEF Policy and Charging Enforcement Function

[0915] PCF Policy Control Function

[0916] PCRF Policy Control and Charging Rules Function

[0917] PDCP Packet Data Convergence Protocol, Packet Data Convergence Protocol Layer

[0918] PDCCH Physical Downlink Control Channel

[0919] PDCP Packet Data Convergence Protocol

[0920] PDN Packet Data Network, Public Data Network

[0921] PDSCH Physical Downlink Shared Channel

[0922] PDU Protocol Data Unit

[0923] PEI Permanent Equipment Identifier

[0924] PFD Packet Flow Description

[0925] P-GW PDN Gateway

[0926] PHICH Physical Hybrid ARQ Indicator Channel

[0927] PHY Physical Layer

[0928] PLMN Public Land Mobile Network

[0929] PIN Personal Identification Number

[0930] PM performance measurement

[0931] PMI Precoding matrix indicator

[0932] PNF Physical Network Function

[0933] PNFD Physical Network Functional Descriptor

[0934] PNFR Physical Network Function Record

[0935] POC PTT over Cellular

[0936] PP,PTP Point to Point

[0937] PPP Point-to-Point Protocol

[0938] PRACH Physical RACH

[0939] PRB Physical Resource Block

[0940] PRG Physical Resource Group

[0941] ProSe Proximity-based Services

[0942] PRS Positioning Reference Signal

[0943] PS Packet Service

[0944] PSBCH Physical Sidelink Broadcast Channel

[0945] PSDCH Physical Sidelink Downlink Channel

[0946] PSCCH Physical Sidelink Control Channel

[0947] PSSCH Physical Sidelink Shared Channel

[0948] PSCell Primary SCell

[0949] PSS Primary Synchronization Signal

[0950] PSTN Public Switched Telephone Network

[0951] PT-RS Phase Tracking Reference Signal

[0952] PTT Push to Talk

[0953] PUCCH Physical Uplink Control Channel

[0954] PUSCH Physical Uplink Shared Channel

[0955] QAM Quadrature Amplitude Modulation

[0956] QCI QoS Class Identifier

[0957] QCL Quasi-Co-sited

[0958] QFI QoS flow ID, QoS flow identifier

[0959] QoS Quality of Service

[0960] QPSK Quadrature (Quaternary) Phase Shift Keying

[0961] QZSS Quasi-Zenith Satellite System

[0962] RA-RNTI Random Access RNTI

[0963] RAB Radio Access Bearer, Random Access Burst

[0964] RACH Random Access Channel

[0965] RADIUS Remote Authentication Dial-In User Service

[0966] RAN Radio Access Network

[0967] RAND random number (for authentication)

[0968] RAR Random Access Response

[0969] RAT Radio Access Technology

[0970] RAU Routing Area Update

[0971] RB Resource Block, Radio Bearer

[0972] RBG Resource Block Group

[0973] REG Resource Element Group

[0974] Rel Release

[0975] REQ Request

[0976] RF

[0977] RI Rank Indicator

[0978] RIV Resource Indicator Value

[0979] RL Radio Link

[0980] RLC Radio Link Control, Radio Link Control Layer

[0981] RLF Radio Link Failure

[0982] RLM Radio Link Monitoring

[0983] RLM-RS Reference signal for RLM

[0984] RM Registration Management

[0985] RMC Reference Measurement Channel

[0986] RMSI Remaining MSI, Remaining Minimum System Information

[0987] RN Relay Node

[0988] RNC Radio Network Controller

[0989] RNL Radio Network Layer

[0990] RNTI Radio Network Temporary Identifier

[0991] ROHC Robust Header Compression

[0992] RRC Radio Resource Control, Radio Resource Control Layer

[0993] RRM Radio Resource Management

[0994] RS reference signal

[0995] RSRP Reference Signal Received Power

[0996] RSRQ Reference Signal Received Quality

[0997] RSSI Received Signal Strength Indicator

[0998] RSU Road Side Unit

[0999] RSTD Reference Signal Time Difference

[1000] RTP Real Time Protocol

[1001] RTS Ready to Send

[1002] RTT Round Trip Time

[1003] Rx receive, receive, receiver

[1004] S1AP S1 Application Protocol

[1005] S1-MME is used for S1 control plane

[1006] S1-U S1 for user plane

[1007] S-GW Service Gateway

[1008] S-RNTI SRNC Radio Network Temporary Identifier

[1009] S-TMSI SAE temporary mobile station identifier

[1010] SA Standalone Operation Mode

[1011] SAE system architecture evolution

[1012] SAP Service Access Point

[1013] SAPD Service Access Point Descriptor

[1014] SAPI Service Access Point Identifier

[1015] SCC Secondary Component Carrier, Secondary CC

[1016] SCell Secondary Cell

[1017] SC-FDMA Single Carrier Frequency Division Multiple Access

[1018] SCG Secondary Cell Group

[1019] SCM Security Context Management

[1020] SCS Subcarrier Spacing

[1021] SCTP Stream Control Transmission Protocol

[1022] SDAP Service Data Adaptation Protocol, Service Data Adaptation Protocol Layer

[1023] SDL Supplemental Downlink

[1024] SDNF Structured Data Storage Network Function

[1025] SDP Service Discovery Protocol (Bluetooth related)

[1026] SDSF structured data storage function

[1027] SDU Service Data Unit

[1028] SEAF Security Anchoring Function

[1029] SeNB Assisted eNB

[1030] SEPP Security Edge Protection Proxy

[1031] SFI Slot Format Indicator

[1032] SFTD Space Frequency Time Diversity, SFN and Frame Timing Difference

[1033] SFN System Frame Number

[1034] SgNB

[1035] SGSN Serving GPRS Support Node

[1036] S-GW Service Gateway

[1037] SI System Information

[1038] SI-RNTI System Information RNTI

[1039] SIB System Information Block

[1040] SIM Subscriber Identity Module

[1041] SIP Session Initiation Protocol

[1042] SiP System in Package

[1043] SL Side Link

[1044] SLA Service Level Agreement

[1045] SM Session Management

[1046] SMF session management functions

[1047] SMS Short Message Service

[1048] SMSF SMS Function

[1049] SMTC SSB-based measurement timing configuration

[1050] SN Secondary node, serial number

[1051] SoC System on Chip

[1052] SON Self-Organizing Network

[1053] SpCell Special Cell

[1054] SP-CSI-RNTI Semi-persistent CSI RNTI

[1055] SPS Semi-persistent Scheduling

[1056] SQN Serial Number

[1057] SR Scheduling Request

[1058] SRB Signalling Radio Bearer

[1059] SRS Sounding Reference Signal

[1060] SS Sync Signal

[1061] SSB Synchronization Signal Block, SS / PBCH Block

[1062] SSBRI SS / PBCH block resource indicator, synchronization signal block resource indicator

[1063] SSC Session and Service Continuity

[1064] SS-RSRP Reference signal received power based on synchronization signal

[1065] SS-RSRQ Reference signal reception quality based on synchronization signal

[1066] SS-SINR Signal to Interference and Noise Ratio based on synchronization signal

[1067] SSS Secondary synchronization signal

[1068] SST Slice / Service Type

[1069] SU-MIMO Single User MIMO

[1070] SUL Supplementary Uplink

[1071] TA timing advance, tracking area

[1072] TAC Tracking Area Code

[1073] TAG Timing Advance Group

[1074] TAU Tracking Area Updates

[1075] TB Transfer Block

[1076] TBS Transport Block Size

[1077] TBD To be defined

[1078] TCI Transmission Configuration Indicator

[1079] TCP transport communication protocol

[1080] TDD Time Division Duplex

[1081] TDM Time Division Multiplexing

[1082] TDMA Time Division Multiple Access

[1083] TE Terminal Equipment

[1084] TEID Tunnel Endpoint Identifier

[1085] TFT Business Flow Template

[1086] TMSI Temporary Mobile Subscriber Identity

[1087] TNL Transport Network Layer

[1088] TPC Transmit Power Control

[1089] TPMI Transmitted Precoding Matrix Indicator

[1090] TR Technical Report

[1091] TRP,TRxP Transmission Receive Point

[1092] TRS Tracking Reference Signal

[1093] TRx Transceiver

[1094] TS Technical Specification, Technical Standard

[1095] TTI Transmission Time Interval

[1096] Tx transmission, transmission, transmitter

[1097] U-RNTI UTRAN Radio Network Temporary Identity

[1098] UART Universal Asynchronous Receiver and Transmitter

[1099] UCI Uplink Control Information

[1100] UE User Equipment

[1101] UDM Unified Data Management

[1102] UDP User Datagram Protocol

[1103] UDSF Unstructured Data Storage Network Function

[1104] UICC Universal Integrated Circuit Card

[1105] UL Uplink

[1106] UM Unconfirmed Mode

[1107] UML Unified Modeling Language

[1108] UMTS Universal Mobile Telecommunications System

[1109] UP User Plane

[1110] UPF User Plane Function

[1111] URI Uniform Resource Identifier

[1112] URL Uniform Resource Locator

[1113] URLLC Ultra-Reliable Low Latency

[1114] USB Universal Serial Bus

[1115] USIM Universal Subscriber Identity Module

[1116] USS UE-specific search space

[1117] UTRA UMTS Terrestrial Radio Access

[1118] UTRAN Universal Terrestrial Radio Access Network

[1119] UwPTS Uplink Pilot Time Slot

[1120] V2I Vehicle to Infrastructure

[1121] V2P Vehicle to Pedestrian

[1122] V2V Vehicle to Vehicle

[1123] V2X: Vehicle-to-Everything

[1124] VIM Virtualization Infrastructure Manager

[1125] VL Virtual Link

[1126] VLAN virtual LAN, virtual local area network

[1127] VM Virtual Machine

[1128] VNF Virtualized Network Function

[1129] VNFFG VNF forwarding graph

[1130] VNFFGD VNF Forwarding Graph Descriptor

[1131] VNFM VNF Manager

[1132] VoIP Voice over IP, Voice over Internet Protocol

[1133] VPLMN Visited Public Land Mobile Network

[1134] VPN Virtual Private Network

[1135] VRB Virtual Resource Block

[1136] WiMAX Worldwide Interoperability for Microwave Access

[1137] WLAN Wireless Local Area Network

[1138] WMAN Wireless Metropolitan Area Network

[1139] WPAN Wireless Personal Area Network

[1140] X2-C X2 control plane

[1141] X2-U X2 user plane

[1142] XML Extensible Markup Language

[1143] XRES Expected User Response

[1144] XOR

[1145] ZC Zadoff-Chu

[1146] ZP Zero Power

[1147] the term

[1148] For the purposes of this document, the following terms and definitions apply to the examples and embodiments discussed herein but are not intended to be limiting.

[1149] As used herein, the term "circuit" refers to, is part of, or includes a hardware component such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and / or a memory (shared, dedicated, or group) configured to provide the described functions, an application specific integrated circuit (ASIC), a field programmable device (FPD) (e.g., a field programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), a digital signal processor (DSP), etc. In some embodiments, the circuit may execute one or more software or firmware programs to provide at least some of the described functions. The term "circuit" may also refer to a combination of one or more hardware elements and a program code for performing the functions of the program code (or a combination of circuits used in an electrical or electronic system). In these embodiments, the combination of hardware elements and program code may be referred to as a specific type of circuit.

[1150] As used herein, the term "processor circuit" refers to, is part of, or includes a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, and / or transmitting digital data. The term "processor circuit" may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and / or any other device capable of executing or otherwise operating computer-executable instructions (such as program code, software modules, and / or functional processes). The terms "application circuit" and / or "baseband circuit" may be considered synonymous with "processor circuit" and may be referred to as "processor circuit".

[1151] As used herein, the term "interface circuit" refers to a circuit that enables, is a part of, or includes information exchange between two or more components or devices. The term "interface circuit" may refer to one or more hardware interfaces, such as a bus, an I / O interface, a peripheral component interface, a network interface card, etc.

[1152] As used herein, the term "user equipment" or "UE" refers to a device that has radio communication capabilities and can describe a remote user of network resources in a communication network. In addition, the terms "user equipment" or "UE" may be considered synonymous and may be referred to as a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. In addition, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device that includes a wireless communication interface.

[1153] As used herein, the term "network element" refers to physical or virtualized equipment and / or infrastructure for providing wired or wireless communication network services. The term "network element" may be considered synonymous with and / or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN equipment, RAN node, gateway, server, virtualized VNF, NFVI, etc.

[1154] As used herein, the term "computer system" refers to any type of interconnected electronic devices, computer devices, or components thereof. Additionally, the terms "computer system" and / or "system" may refer to various components of a computer that are communicatively coupled to one another. Furthermore, the terms "computer system" and / or "system" may refer to multiple computer devices and / or multiple computing systems that are communicatively coupled to one another and configured to share computing and / or networking resources.

[1155] As used herein, the terms "appliance", "computer appliance", etc. refer to a computer device or computer system with program code (e.g., software or firmware) that is specifically designed to provide specific computing resources. A "virtual appliance" is a virtual machine image to be implemented by a device equipped with a hypervisor that virtualizes or emulates a computer appliance or is otherwise dedicated to providing specific computing resources.

[1156] As used herein, the term "resource" refers to a physical or virtual device, a physical or virtual component within a computing environment, and / or a physical or virtual component within a specific device, such as a computer device, a mechanical device, a memory space, a processor / CPU time and / or a processor / CPU usage rate, a processor and accelerator load, a hardware time or usage rate, a power supply, an input / output operation, a port or a network socket, a channel / link allocation, throughput, memory usage rate, storage, a network, a database and an application, a unit of work, etc. "Hardware resources" may refer to computing, storage and / or network resources provided by physical hardware elements. "Virtualized resources" may refer to computing, storage and / or network resources provided by a virtualized infrastructure to an application, a device, a system, etc. The term "network resources" or "communication resources" may refer to resources that a computer device / system can access via a communication network. The term "system resources" may refer to any kind of shared entity that provides a service, and may include computing resources and / or network resources. System resources may be considered as a set of coherent functions, network data objects or services that can be accessed through a server, wherein such system resources reside on a single host or multiple hosts and can be clearly identified.

[1157] As used herein, the term "channel" refers to any tangible or intangible transmission medium for transmitting data or data streams. The term "channel" may be synonymous and / or equivalent to "communication channel", "data communication channel", "transmission channel", "data transmission channel", "access channel", "data access channel", "link", "data link", "carrier", "radio frequency carrier" and / or any other similar terms representing a path or medium through which data is transmitted. In addition, the term "link" as used herein refers to a connection between two devices for transmitting and receiving information over a RAT.

[1158] As used herein, the terms "instantiate," "instantiate," and the like refer to the creation of an instance. "Instance" also refers to a specific occurrence of an object, which may occur, for example, during the execution of program code.

[1159] The terms "coupled," "communicatively coupled," and their derivatives are used herein. The term "coupled" may mean that two or more elements are in direct physical or electrical contact with each other, may mean that two or more elements are in indirect contact with each other but still cooperate or interact with each other, and / or may mean that one or more other elements are coupled or connected between the elements said to be coupled to each other. The term "directly coupled" may mean that two or more elements are in direct contact with each other. The term "communicatively coupled" may mean that two or more elements may be in contact with each other by means of communication, including through a wire or other interconnect connection, through a wireless communication channel or link, etc.

[1160] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual contents of an information element, or a data element that contains the contents.

[1161] The term "SMTC" refers to the SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration.

[1162] The term "SSB" refers to SS / PBCH block.

[1163] The term "primary cell" refers to an MCG cell operating on a primary frequency, where the UE either performs an initial connection establishment procedure or initiates a connection re-establishment procedure.

[1164] The term "primary SCG cell" refers to an SCG cell in which a UE performs random access when reconfiguration is performed using a synchronization procedure for DC operation.

[1165] The term "secondary cell" refers to a cell that provides additional radio resources on top of a special cell for a UE configured with CA.

[1166] The term "secondary cell group" refers to a subset of serving cells including a PSCell for a UE configured with DC and zero or more secondary cells.

[1167] The term "serving cell" refers to a primary cell for a UE in RRC_CONNECTED that is not configured with CA / DC, where there is only one serving cell including the primary cell. The term "serving cell" refers to a cell group including a special cell for a UE configured with CA and in RRC_CONNECTED and all secondary cells.

[1168] The term "special cell" refers to the PCell of the MCG or the PSCell of the SCG for DC operation; otherwise, the term "special cell" refers to the Pcell.

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

[1170] The present disclosure envisions that entities responsible for collecting, analyzing, disclosing, transmitting, storing or otherwise using such personal information data will comply with established privacy policies and / or privacy practices. Specifically, such entities should implement and adhere to privacy policies and practices that are recognized as meeting or exceeding industry or government requirements for maintaining the privacy and security of personal information data. Such policies should be easily accessible to users and should be updated as the collection and / or use of data changes. Personal information from users should be collected for the legitimate and reasonable purposes of the entity and not shared or sold outside of these legitimate uses. In addition, such collection / sharing should only be done after receiving the user's informed consent. In addition, such entities should consider taking any necessary steps to defend and safeguard access to such personal information data and ensure that others who have access to personal information data comply with their privacy policies and processes. In addition, such entities may subject themselves to third-party assessments to demonstrate their compliance with widely accepted privacy policies and practices. In addition, policies and practices should be adjusted to specific types of personal information data collected and / or accessed, and to applicable laws and standards that include specific considerations of jurisdiction. For example, in the United States, the collection or access of certain health data may be governed by federal and / or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA), while health data in other countries may be subject to other regulations and policies and should be handled accordingly. Therefore, different privacy practices should be maintained in each country for different types of personal data.

[1171] Regardless of the foregoing, the present disclosure also contemplates implementation schemes in which users selectively block the use or access of personal information data. That is, the present disclosure contemplates providing hardware elements and / or software elements to prevent or block access to such personal information data. For example, the present technology may be configured to allow users to selectively participate in "opt-in" or "opt-out" of collecting personal information data at any time during (for example) registration for a service or thereafter. In addition to providing "opt-in" and "opt-out" options, the present disclosure contemplates providing notifications related to access or use of personal information. For example, a user may be notified that their personal information data will be accessed when downloading an application, and then reminded again just before the personal information data is accessed by the application.

[1172] In addition, it is an object of the present disclosure that personal information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use. Risks can be minimized by limiting data collection and deleting data once it is no longer needed. In addition, and when applicable, including in certain health-related applications, data de-identification can be used to protect the privacy of users. De-identification can be facilitated by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of stored data (e.g., collecting location data at the city level rather than at the address level), controlling how data is stored (e.g., aggregating data between users), and / or other methods when appropriate.

[1173] Thus, while the present disclosure may broadly cover the use of personal information data to implement one or more of the various disclosed embodiments, the present disclosure also contemplates that various embodiments may also be implemented without access to such personal information data. That is, various embodiments of the present technology will not fail to function properly due to the lack of all or part of such personal information data.

Claims

1. A method for beam failure recovery (BFR), the method being performed by a network device, the method comprising: Detect beam failure instances; initiating a beam failure recovery procedure by activating or deactivating a candidate beam for at least one uplink bandwidth part BWP associated with a user equipment UE; generating a control signal to identify the one or more candidate beams for activation or deactivation of the at least one uplink BWP associated with the UE; as well as transmitting the control signal to the UE, The control signal is a medium access MAC control element CE, and the method further comprises: A set of activated candidate beams is verified at a predetermined time slot in response to receiving a HARQ-ACK from the UE acknowledging a physical downlink shared channel (PDSCH) signal carrying the MAC CE.

2. The method of claim 1, wherein the one or more candidate beams for activation or deactivation are identified in a medium access control MAC protocol data unit (PDU) subheader with a new logical channel ID (LCID) in the MAC CE.

3. The method according to claim 1, further comprising: The serving cell identifier to which the MAC CE in the MAC CE is applicable is identified to the UE.

4. The method according to claim 1, further comprising: A BWP ID indicating the at least one uplink BWP to which the MAC CE applies is identified to the UE.

5. A network device for beam failure recovery BFR, the network device comprising: Radio front-end circuits; and a processor circuit coupled to the radio front end circuit and configured to: Detect beam failure instances, initiating a beam failure recovery procedure by activating or deactivating a candidate beam for at least one uplink bandwidth part BWP associated with a user equipment UE, generating a control signal to identify the one or more candidate beams for activation or deactivation of the at least one uplink BWP associated with the UE, and transmitting the control signal to the UE using the radio front end circuit, wherein the control signal is a medium access MAC control element CE, and wherein the processor circuit is further configured to: A set of activated candidate beams is verified at a predetermined time slot in response to receiving a HARQ-ACK from the UE acknowledging a physical downlink shared channel (PDSCH) signal carrying the MAC CE.

6. The network device of claim 5, wherein the processor circuit is further configured to: The one or more candidate beams for activation or deactivation are identified in a medium access control MAC protocol data unit (PDU) subheader with a new logical channel ID LCID in the MAC CE.

7. The network device of claim 5, wherein the processor circuit is further configured to: The serving cell identifier to which the MAC CE in the MAC CE is applicable is identified to the UE.

8. The network device of claim 5, wherein the processor circuit is further configured to: A BWP ID indicating the at least one uplink BWP to which the MAC CE applies is identified to the UE.

9. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors of a network device, cause the network device to perform one or more operations comprising: Detect beam failure instances; initiating a beam failure recovery procedure by activating or deactivating a candidate beam for at least one uplink bandwidth part BWP associated with a user equipment UE; generating a control signal to identify the one or more candidate beams for activation or deactivation of the at least one uplink BWP associated with the UE; as well as transmitting the control signal to the UE, The control signal is a medium access MAC control element CE, and the operation further comprises: A set of activated candidate beams is verified at a predetermined time slot in response to receiving a HARQ-ACK from the UE acknowledging a physical downlink shared channel (PDSCH) signal carrying the MAC CE.

10. The non-transitory computer readable medium of claim 9, the operations further comprising: The one or more candidate beams are identified in a medium access control MAC protocol data unit (PDU) subheader with a new logical channel ID LCID in the MAC CE.

11. The non-transitory computer readable medium of claim 9, the operations further comprising: The serving cell identifier to which the MAC CE in the MAC CE is applicable is identified to the UE.

Images