Wireless Link Monitoring and Radio Resource Management Measurement Procedures for NR-U

Abstract

To provide a device, a method, and a computer readable storage medium that implement a radio link monitoring or a radio link failure process.SOLUTION: In a communication system, a user terminal includes executes monitoring an in-sync or out-of-sync indication, monitoring a number of faulty Radio Link Monitoring Reference Signal (RLM-RS) transmission opportunities (TXOPs), and detecting a Radio Link Failure (RLF) on the basis of the monitored in-sync or out-of-sync indication combined with the monitored number of faulty RLM-RS TXOPs.SELECTED DRAWING: Figure 7

Description

Technical Field

[0001] (Cross - Reference to Related Applications) This application claims the benefit of U.S. Provisional Patent Application No. 62 / 716,020, filed on Aug. 8, 2018 entitled “RLM and RRM Measurement Procedures for NR - U”, the content of which is hereby incorporated by reference herein.

Background Art

[0002] The 3rd Generation Partnership Project (3GPP) is developing technical standards for cellular telecommunication network technologies, including radio access, core transport networks, and service capabilities (including those affecting channel decoding, security, and quality of service). Recent radio access technology (RAT) standards include WCDMA (registered trademark) (commonly referred to as 3 G), LTE (commonly referred to as 4G), and LTE - Advanced standards . 3GPP has started working on the standardization of a new radio (NR), also referred to as “5G”. Next - generation cellular technology.

Summary of the Invention

[0003] In New Radio Unlicensed (NR - U), an NR NodeB (e.g., gNB) cannot acquire a channel and transmits a downlink reference signal (DL - RS) during a Transmission Opportunity (TXOP). ​There may be cases where it cannot be transmitted. When a User Equipment (UE) attempts to measure DL-RS during a blocked TXOP, since the DL-RS is not being transmitted by the gNB, the UE measurement may be calculated incorrectly. As a result, there are cases where the Radio Link Monitoring (RLM) measurement quantity becomes incorrect, and even when the gNB can acquire the channel and transmit the reference signal for measurement, and the link quality may be good, the UE may declare that it is out-of-sync. Also, this causes the calculated Radio Resource Management (RRM) measurement quantity to be incorrect, and may also cause errors in detecting measurement events or malfunctions. Therefore, an extension of the RLM and RRM measurement procedures for NR-U to handle blocked DL-RS TXOPs, etc. is required. If the UE attempts to measure DL-RS during a blocked TXOP, since the DL-RS is not being transmitted by the gNB, the UE measurement may be calculated incorrectly. As a result, there are cases where the Radio Link Monitoring (RLM) measurement quantity becomes incorrect, and even when the gNB can acquire the channel and transmit the reference signal for measurement, and the link quality may be good, the UE may declare that it is out-of-sync. Also, this causes the calculated Radio Resource Management (RRM) measurement quantity to be incorrect, and may also cause errors in detecting measurement events or malfunctions. Therefore, an extension of the RLM and RRM measurement procedures for NR-U to handle blocked DL-RS TXOPs, etc. is required. In one aspect, a method for performing RRM measurements for NR-U is disclosed herein, which is based on a measurement model that can adapt the measurement function implemented by Radio Resource Control (RRC) by providing a defective RS TXOP indicator to the upper layer when a defective RS TXOP is detected. In another aspect, a method for performing RLM for NR-U is disclosed herein based on an in-sync or out-of-sync indication based on the estimated radio link quality combined with a defective RLM-RS TXOP. As a result, there are cases where the Radio Link Monitoring (RLM) measurement quantity becomes incorrect, and even when the gNB can acquire the channel and transmit the reference signal for measurement, and the link quality may be good, the UE may declare that it is out-of-sync. Also, this causes the calculated Radio Resource Management (RRM) measurement quantity to be incorrect, and may also cause errors in detecting measurement events or malfunctions. Therefore, an extension of the RLM and RRM measurement procedures for NR-U to handle blocked DL-RS TXOPs, etc. is required. In one aspect, a method for performing RRM measurements for NR-U is disclosed herein, which is based on a measurement model that can adapt the measurement function implemented by Radio Resource Control (RRC) by providing a defective RS TXOP indicator to the upper layer when a defective RS TXOP is detected.

[0004] In one aspect, a method for performing RRM measurements for NR-U is disclosed herein, which is based on a measurement model that can adapt the measurement function implemented by Radio Resource Control (RRC) by providing a defective RS TXOP indicator to the upper layer when a defective RS TXOP is detected. However, this is based on a measurement model that can adapt the measurement function implemented by Radio Resource Control (RRC) by providing a defective RS TXOP indicator to the upper layer when a defective RS TXOP is detected. When a defective RS TXOP is detected, a defective RS TXOP indicator is provided to the upper layer, and the measurement function implemented by Radio Resource Control (RRC) can be adapted based on this measurement model. In another aspect, a method for performing RLM for NR-U is disclosed herein based on an in-sync or out-of-sync indication based on the estimated radio link quality combined with a defective RLM-RS TXOP.

[0005] In another aspect, a method for performing RLM for NR-U is disclosed herein based on an in-sync or out-of-sync indication based on the estimated radio link quality combined with a defective RLM-RS TXOP. Based on an in-sync or out-of-sync indication based on the estimated radio link quality combined with a defective RLM-RS TXOP. A method for performing RLM for NR-U is disclosed herein.

[0006] This Summary is provided in a simplified form to provide an overview of the detailed description of the invention, which is further described below. This Summary is provided to introduce a selection of key features or aspects of the claimed subject matter. shall not be used to specify qualitative characteristics or to limit the scope of the claimed subject matter. Moreover, claimed subject matter is not intended to be a substitute for any part of this disclosure. The present invention is not limited to the above-mentioned limitations, nor is it limited to the limitations that address any or all of the disadvantages.

[0007] BRIEF DESCRIPTION OF THE DRAWINGS A more detailed understanding may be had from the following description, given by way of example in conjunction with the accompanying drawings, in which: It is possible. [Brief description of the drawings]

[0008]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9A

Figure 9B

Figure 9C

Figure 9D

Figure 9E

Figure 9F

Figure 9G

[0009] With respect to LTE Licensed-Assisted Access, carrier aggregation using at least one SCell operating in an unlicensed frequency band is also referred to as Licensed-Assisted Access (LAA). Thus, in LAA, the set of serving cells configured for a UE always includes at least one SCell operating in an unlicensed frequency band according to frame structure type 3, also referred to as an LAA SCell. Unless otherwise indicated, the LAA SCell operates as a standard SCell. In LAA, the set of serving cells configured for a UE always includes at least one SCell operating in an unlicensed frequency band according to frame structure type 3, also referred to as an LAA SCell. Unless otherwise indicated, the LAA SCell operates as a standard SCell. SCell operating in an unlicensed frequency band according to frame structure type 3, also referred to as an LAA SCell. Unless otherwise indicated, the LAA SCell operates as a standard SCell. SCell operating in an unlicensed frequency band according to frame structure type 3, also referred to as an LAA SCell. Unless otherwise indicated, the LAA SCell operates as a standard SCell.

[0010] The LAA eNB and UE perform Listen-Before-Talk (LBT) before transmitting on the LAA SCell. When LBT is performed, the transmitter listens / detects the channel to determine whether the channel is free or busy. If the channel is determined to be free, the transmitter may perform the transmission. The LAA eNB and UE perform Listen-Before-Talk (LBT) before transmitting on the LAA SCell. When LBT is performed, the transmitter listens / detects the channel to determine whether the channel is free or busy. If the channel is determined to be free, the transmitter may perform the transmission. The LAA eNB and UE perform Listen-Before-Talk (LBT) before transmitting on the LAA SCell. When LBT is performed, the transmitter listens / detects the channel to determine whether the channel is free or busy. If the channel is determined to be free, the transmitter may perform the transmission. The LAA eNB and UE perform Listen-Before-Talk (LBT) before transmitting on the LAA SCell. When LBT is performed, the transmitter listens / detects the channel to determine whether the channel is free or busy. If the channel is determined to be free, the transmitter may perform the transmission. Otherwise, transmission is not performed. When the LAA eNB uses the channel access signals of other technologies for the purpose of LAA channel access, it must continue to meet the LAA maximum energy detection threshold requirements. [1] See 3GPP TS 36.300, (E-UTRAN); Overall description; Stage 2 (Release 15), V15.0.0.

[0011] Frame structure type 3 is applicable to the LAA secondary cell operation with only the normal cyclic prefix. Each radio frame has the length of Equation 1 below and is composed of 20 slots with the length of Equation 2 below numbered from 0 to 19. A subframe is defined by two consecutive slots, where subframe i is composed of slots i and 2i + 1. [2] See 3GPP TS 36.211, Physical channels and modulation (Rel ease 15). ease 15).

[0012]

Number

[0013]

Number

[0014] Ten subframes within a radio frame are available for downlink or uplink transmission. As defined in Table 10.2-1 of 3GPP TS 36.211, Physical channels and modulation (Release 15), downlink transmission is one or more consecutive ​​​​​occupies a subframe, starts within any of the subframes, and ends by completely occupying the last subframe or following one of the DwPTS time periods. Uplink transmission occupies one or more consecutive subframes. For NR measurement, in RRC_CONNECTED, the UE measures multiple beams of (at least one) cell and derives the cell quality by averaging the measurement results (power values). To do so, the UE is configured to take into account a subset of the detected beams. Filtering is performed at two levels: the physical layer level for deriving beam quality and the RRC level for deriving cell quality from multiple beams. The cell quality by beam measurement is derived in the same way for both the serving cell and the non-serving cell.

[0015] The measurement report may include the measurement results of X best beams if the UE is configured to measure the best beams by the gNB. The NR measurement model is shown in Figure 1. This model is an excerpt from 3GPP TS 38.300, NR; NR and NG-RAN Overall Description; Stage 2 (Release 15), V15.2.0[3]3GPP TS 38.300, NR; NR and NG-RAN Overall Description; Stage 2 (Release 15), V15.2.0. In NR, the network may configure the UE to perform measurements based on the SS / PBCH block (SS / PBCH Block: SSB) or the CSI-RS (Channel State Information Reference Signal). In this case, the measurement quantity is the received power of the reference signal (Reference Signal Recei

[0016] ​​​​​​​​​​​​ Received Power: RSRP), Received Quality of Reference Signal (Reference Signal Received Quality : RSRQ), or Signal-to-Noise and Interference Ratio : SINR). Physical layer measurements for NR are defined in [5] 3GPP TS 38.215, N R; Physical layer measurements (Release 15), V15.2.0.

[0017] Regarding NR radio link failure, in RRC_CONNECTED, (1) expiration of a timer started after notification of a radio problem from the physical layer (if the radio problem is resolved before the timer expires, the UE stops the timer), (2) random access procedure failure, (3) R LC failure criteria, when one of them is met, the UE declares a radio link failure (RLF).

[0018] After RLF is declared, the UE 1) stays in RRC_CONNECTED, 2) selects a suitable cell and starts RRC re-establishment, 3) if no suitable cell is found within a certain time after RLF is declared, enters RRC_IDLE.

[0019] As shown in Figure 2, the operations associated with radio link failure are controlled in two phases.

[0020] The first phase starts at 1) radio problem detection, 2) leads to radio link failure detection, 3) is not UE-based mobility, 4) is based on a timer or other (count) criteria (T 1 ) and continues.

[0021] ​​​​​The second phase is 1) initiated upon detection of a radio link failure or a handover failure, 2) leads to RR C_IDLE, 3) is UE-based mobility, and 4) is based on a timer (T 2 ). .

[0022] By using bandwidth adaptation (BA) in NR, the receive and transmission bandwidths of the UE do not have to be the same size as the cell bandwidth and can be adjusted , for example, the width may be instructed to change (e.g., reduced during a low-activity period to save power), the position can be moved in the frequency domain (e.g., to increase scheduling flexibility), and the subcarrier spacing may be specified to change (e.g., to enable different services). A subset of the total cell bandwidth of the cell is called a bandwidth part (BWP), and BA is realized by configuring the UE with BWPs and informing the UE which configured BWP is currently active.

[0023] Figure 3 shows a scenario where three different BWPs are configured: 1) BWP1 with a width of 40 MHz and a subcarrier spacing of 15 kHz, 2) BWP2 with a width of 10 M Hz and a subcarrier spacing of 15 kHz, and 3) BWP3 with a width of 20 MHz and a subcarrier spacing of 60 kHz.

[0024] The serving cell may be configured with up to four BWPs, and in an active serving cell, one active BWP always exists at any given time. The serving BWP switching in the serving cell is used to simultaneously activate a non-active BWP and deactivate an active BWP, and is controlled by a PDCCH indicating a downlink allocation or an uplink grant. Depending on the addition of a SpCell (special cell) or the activation of an SCell, one BWP is first activated without receiving a PDCCH indicating a downlink allocation or an uplink grant. The active BWP of the serving cell is indicated by the RRC or the PDCCH. In an unpaired frequency band, the DL BWP is paired with the UL BWP, and the BWP switching is common to both the UL and the DL. See [5] and [7] 3GPP TS 38.321, NR; Medium Access Control (MAC) Protocol Specification (Release 15), V15.2.0.

[0025] Returning now to radio link monitoring (RLM) and radio resource management (RRM), in new radio unlicensed (NR-U), the NR NodeB (e.g., gNB) may not be able to acquire a channel and transmit a downlink reference signal (DL-RS) during a transmission opportunity (TXOP). If a user equipment (UE) attempts to measure the DL-RS during a blocked TXOP, the UE measurement may be incorrectly calculated because the DL-RS is not transmitted by the gNB. As a result, the measurement quantity of the radio link monitoring (RLM) may be incorrect, and even if the gNB can acquire a channel and transmit a reference signal for and may cause the UE to declare. Also, this may result in incorrect RRM measurement quantities and may cause incorrect detection of measurement events or malfunctions. Therefore, for NR-U, an RLM and an extension of the RRM measurement procedure to handle blocked DL-RS TXOPs are required. In one example, being blocked may refer to a situation where the gNB cannot acquire a channel, thereby preventing the transmission of DL-RS during the TXOP.

[0026] In one aspect, a method for performing RRM measurements for NR-U is disclosed herein which is based on a measurement model that adapts the measurement function performed by RRC when a defective RS TXOP is detected and a defective RS TXOP indicator is provided to the upper layer.

[0027] In another aspect, a method for performing RLM for NR-U is disclosed herein based on a synchronization in / synchronization out indication based on the estimated radio link quality combined with a defective RLM-RS TXOP.

[0028] (Method for performing RLM for NR-U) A method for performing RLM for NR-U is disclosed below. The UE may monitor the downlink link quality based on the reference signals of the configured RLM-RS resources to detect the downlink radio link quality of the PCell and the PSCell. In addition to monitoring the downlink link quality, the UE may monitor the number of defective RLM-RS TXOPs. Regarding monitoring the downlink quality, the UE determines the DL link quality for the purpose of ​ Measurements of the reference signal configured by may be performed, and whether the measurement value is greater than or less than the configured threshold is used to determine whether the radio link is in synchronization or out of synchronization. This is good. The count of the number of defective RLM-RS TXOPs may be combined with the downlink link quality estimate to detect RLF. The configured RLM-RS resources may be all SSBs, or all CSI-RSs, or a combination of SSB and CSI-RS. Figure 4 is a diagram of an exemplary NR-U RLM / RLF model.

[0029] (Detection of Defective RLM-RS TXOP) Monitoring for defective RLM-RS TXOPs may be based on the detection of a discovery reference signal (DRS), a channel access indication (CAI) signal, or any other signal transmitted by the gNB that may be used by the UE to confirm whether the gNB has acquired the channel. The characteristics of the channel usage signal may be such that it can be reliably detected during a single TXOP, for example, it does not need to be combined over multiple TXOPs. The "channel usage" signal may be multiplexed with multiple RLM-RSs using frequency division multiplexing (FDM) or time division multiplexing (TDM) techniques. The detection of CAI may be explicit or implicit. Whether the UE uses the SSB

[0030] Channel Occupancy Time (COT) configured for CSIRS for receiving PDSCH, the UE implicitly understands that the RS is available in some cases.

[0031] In the case of explicit signaling, when the gNB acquires the channel for COT, signals such as PSS / SSS may be transmitted by the gNB. The UE monitors this signal and identifies that its transmission is from the gNB. By doing so, the UE recognizes that the RS is available during COT .

[0032] Alternatively, in a configuration where the licensed band downlink is also available, the gNB indicates whether an unlicensed channel has been acquired during the R LM-RS TXOP by transmitting Downlink Control Information (DCI) on the licensed band downlink . For example, DCI Format _2_X configured with the information shown in Table 1 and scrambled with C-RNT I, common RNTI, or group RNTI may be used to indicate a defective TXOP for a specific RLM-RS on a specific carrier .

[0033]

Table 1

[0034] Furthermore, in yet another alternative, the detection of a defective RLM-RS TXOP may be threshold-based . For example, if the value of the RLM-RS RSRP measurement is less than the threshold , the UE considers that there is a defect in the RLM-RS TXOP. The value of the threshold is determined by the upper layer (e.g., It may be signaled to the UE by RRC signaling). For example, the threshold may be signaled as the parameter rlmDetectionThreshold included in the SpCellConfig information element (IE) shown in Table 2.

[0035]

Table 2

[0036] As another alternative, in order to detect the absence of RLM-RS, RLM-RS may be transmitted only when it is associated with other successfully transmitted or scheduled downlink transmission bursts (e.g., overlapping ). In other words, RLM-RS and the associated DL transmission burst are always within the same COT. For example, if RLM-RS is associated with a specific SSB and the UE fails to detect this SSB, the UE may assume that the gNB cannot acquire the channel normally and regard this as a RLM-RS TXO P problem. As another example, if RLM-RS is associated with a specific control resource set ( Control Resource Set: CORESET) and the UE fails to decode the PDCCH within this CORE SET, the UE may assume that the gNB cannot acquire the channel normally and regard this as a RLM-RS TXOP problem

[0037] The transmission burst associated with RLM-RS may be signaled to the UE by a higher layer (e.g., RRC signaling ). For example, SSBID, CORESETID, etc. ​​​​​​​Which value may the RLM - AssociatedBurst IE take and be signaled to the UE? be signaled

[0038] (RLF Detection (Alternative 1)) As discussed herein, the detection of RLF for NR - U may be based on the estimated radio link quality combined with the defective RLM - RS TXOP and the synchronization or out - of - synchronization indication based on the estimated radio link quality combined with the defective RLM - RS TXOP and the synchronization or out - of - synchronization indication At each RLM - RS resource, the UE estimates the downlink radio link quality and compares it with the thresholds Q and Q out and Q in for the purpose of monitoring the downlink radio link quality of the cell. The threshold Q out is a level at which the downlink radio link cannot be reliably received, for example, an out - of - sync Block Error Rate (BLER) of 10% ER out and may be defined as such. The threshold Q in is a level at which the downlink radio link quality can be received with a much higher certainty than Q out for example, an in - sync Block Error Rate (BLER) of 2% and may be defined as such. The BLER and BL in ER out and BL ER in can also be other values, which may be determined by the gNB based on measurements (e.g., channel occupancy) performed by the gNB or reported to the gNB, and signaled to the UE via upper layers, e.g., SI broadcast or dedicated signaling can also be other values, which may be determined by the gNB based on measurements (e.g., channel occupancy) performed by the gNB or reported to the gNB, and signaled to the UE via upper layers, e.g., SI broadcast or dedicated signaling At all resources within the set of resources configured for radio link monitoring, the RLM - RS be signaled

[0039] At all resources within the set of resources configured for radio link monitoring, the RLM - RS When the UE detects a problem with the TXOP, the physical layer of the UE evaluates the link quality in the frame indicating the defective RLM-RS TXOP. The UE evaluates whether the number of defective RLM-RS TXOPs during the previous T period is greater than the threshold N. Monitoring the number of defective RLM-RS TXOPs may be based on the timing at which N is received during the T period. The values of the parameters T and N may be signaled to the UE by the upper layer (e.g., RRC signaling). For example, T and N may be signaled as T312 and N312, respectively, via the RLF-TimersAndConstants IE shown in Table 3. The NR-U RLF timers and constants may be defined as presented in Tables 4 and 5, respectively. The timer may be started when a defective RLM-RS TXOP is detected. See Tables 4 and 6. in the frame where the link quality was evaluated, indicating the defective RLM-RS TXOP. The UE Evaluate _missed_TXOP evaluates whether the number of defective RLM-RS TXOPs during the previous T period is greater than the threshold Missed_TXOP N. Monitoring the number of defective RLM-RS Evaluate_missed_TXOP TXOPs may be based on the timing at which N Missed_TXOP is received during the T Evaluate_missed_TXOP period. The values of the parameters Missed_TXOP T and N may be signaled to the UE by the upper layer (e.g., RRC signaling). For example Evaluate_missed_TXOP T Missed_TXOP and N may be signaled as T312 and N312, respectively, via the RLF-TimersAndConstants IE shown in Table 3. The NR-U RLF timers and constants may be defined as presented in Tables 4 and 5, respectively. The timer may be started when a defective RLM-RS TXOP is detected. See Tables 4 and 6. Please refer to Tables 4 and 6.

[0040]

Table 3

[0041]

Table 4

[0042]

Table 5

[0043] ​ (RRC's RLF-related operations (Alternative 1)) For NR-U, RLF detection may be performed by RRC. As an example of RLF-related operations performed by RRC is shown in Table 6, Table 7, or Table 8.

[0044]

Table 6

[0045]

Table 7

[0046]

Table 8

[0047] (RLF Detection (Alternative 2)) In Alternative 2, for NR-U, RLF detection is based on defective RLM-RS TXOP combined with estimated radio link quality during synchronization or out-of-synchronization indication. Monitoring and detection of RLF based on downlink link quality are as described in Alternative 1 . The method of detecting RLF based on defective RLM-RS TXOP is different from Alternative 1 . In Alternative 2, monitoring and detection of RLF based on "defective" RLM-RS TXOP use a different method. In this different method, as shown in Figure 5, when the UE detects a "defective" RL M-RS TXOP and when the UE detects that an RLM-RS has been transmitted during the RLM-RS TXOP, an indication is provided to the upper layer . In Figure 4, an indication of defective RLM-RS TXOP is provided to the upper layer . In Figure 5, an indication of defective and detected RLM-RS TXOP is provided to the upper layer . . is provided to the layer. The detected RLM-RS TXOP may be used to stop timer T312 .

[0048] Upon detection of N312 consecutive failed RLM-RS TXOPs, the UE starts timer T312 . During N313 consecutive RLM-RS TXOPs, if an RLM-RS is detected, the timer is stopped. More generally, the timer may be stopped when a reference signal is detected between consecutive reference signal TXOP thresholds (e.g., N de tected_TXOP ). The thresholds may be pre-configured by RRC. RLF is declared upon expiration of timer T312 . The values of timer T312 and constants N312 and N313 may be signaled to the UE by the upper layer (e.g., R RC signaling) via the RLF-TimersAndConstants IE as shown in Table 9 . The NR-U RLF timers and constants used in Alternative 2 may be defined as presented in Table 10 and Table 11 respectively .

[0049]

Table 9

[0050]

Table 10

[0051]

Table 11

[0052] (RLF-related operations of RRC (Alternative 2)) ​​For NR-U, RLF detection may be performed by RRC. As an alternative 2, RRC An exemplary description of the RLF-related operations performed by is shown in Tables 12, 13, and 14 .

[0053]

Table 12

[0054]

Table 13

[0055]

Table 14

[0056] (RLF Detection (Alternative 3)) In a configuration where a wideband carrier is used, a scenario is conceivable where a part of the channel is occupied by other users, e.g., , Wi-Fi users, while the remaining part may not be occupied . To optimize the channel utilization rate, it is proposed that the gNB perform sub band LBT when accessing the channel for some downlink transmissions, e.g., for the transmission of RLM-RS . This document discusses models of multiple subbands, each having its own set of RLM resources in different BWP configurations .

[0057] In one example, the gNB transmits RLM-RS in all of the DL-BWPs configured for a given UE according to the results of the subband LBT performed in each corresponding DL-BWP . When the UE detects a physical layer problem on the active DL-BWP, the UE performs a BWP switch . It may be possible to perform pinging. If the UE does not recover from the physical layer problem after the BWP switching is performed, additional BWP switching may be performed before declaring RLF. The values of timer T310 and constants N312 and N313 may be signaled to the UE by the upper layer (e.g., RRC signaling) via the RLF-Time rsAndConstants IE. The NR-U RLF timer and constants used in alternative 3 are defined in Table 16 and Table 17, respectively. If the UE does not recover from the physical layer problem after the BWP switching is performed, additional BWP switching may be performed before declaring RLF. The values of timer T310 and constants N312 and N313 may be signaled to the UE by the upper layer (e.g., RRC signaling) via the RLF-Time rsAndConstants IE. The NR-U RLF timer and constants used in alternative 3 are defined in Table 16 and Table 17, respectively. If the UE does not recover from the physical layer problem after the BWP switching is performed, additional BWP switching may be performed before declaring RLF. The values of timer T310 and constants N312 and N313 may be signaled to the UE by the upper layer (e.g., RRC signaling) via the RLF-Time rsAndConstants IE. The NR-U RLF timer and constants used in alternative 3 are defined in Table 16 and Table 17, respectively. If the UE does not recover from the physical layer problem after the BWP switching is performed, additional BWP switching may be performed before declaring RLF. The values of timer T310 and constants N312 and N313 may be signaled to the UE by the upper layer (e.g., RRC signaling) via the RLF-Time rsAndConstants IE. The NR-U RLF timer and constants used in alternative 3 are defined in Table 16 and Table 17, respectively. If the UE does not recover from the physical layer problem after the BWP switching is performed, additional BWP switching may be performed before declaring RLF. The values of timer T310 and constants N312 and N313 may be signaled to the UE by the upper layer (e.g., RRC signaling) via the RLF-Time rsAndConstants IE. The NR-U RLF timer and constants used in alternative 3 are defined in Table 16 and Table 17, respectively. If the UE does not recover from the physical layer problem after the BWP switching is performed, additional BWP switching may be performed before declaring RLF. The values of timer T310 and constants N312 and N313 may be signaled to the UE by the upper layer (e.g., RRC signaling) via the RLF-Time rsAndConstants IE. The NR-U RLF timer and constants used in alternative 3 are defined in Table 16 and Table 17, respectively.

[0058]

Table 15

[0059]

Table 16

[0060]

Table 17

[0061] (RRC RLF-related operations (Alternative 3)) For NR-U, RLF detection may be performed by RRC. Exemplary descriptions of RLF-related operations performed by RRC as alternative 3 are shown in Table 18, Table 19, and Table 20. For NR-U, RLF detection may be performed by RRC. Exemplary descriptions of RLF-related operations performed by RRC as alternative 3 are shown in Table 18, Table 19, and Table 20. For NR-U, RLF detection may be performed by RRC. Exemplary descriptions of RLF-related operations performed by RRC as alternative 3 are shown in Table 18, Table 19, and Table 20.

[0062]

Table 18

[0063]

Table 19

[0064]

Table 20

[0065] An alternative to triggering BWP switching by RRC is to perform detection of physical layer problems at the MAC layer and trigger BWP switching when the MAC detects a physical layer problem which may also be good. In this alternative, the operations performed by RRC for the detection of physical layer problems are shown in Table 21. The remaining RRC operations for the recovery of physical layer problems and the detection of RLF are shown in Tables 19 and 20. The operations performed by the MAC for the detection of physical layer problems are shown in Table 22.

[0066]

Table 21

[0067]

Table 22

[0068] In this alternative, the synchronization deviation indication received by the MAC layer may be based on the estimated radio link quality. Alternatively, the synchronization deviation indication may be based on the estimated radio link quality combined with the defective RLM -RS TXOP. Further alternatively, the detection of physical layer problems by the MAC layer may be based only on the reception of defective RLM-RS TXOP, for example,

[0069] defaultDownlinkBWP or initialDownlinkBWP As an alternative to switching to, the UE may autonomously switch to any other configured DL BW ​​It may also be switched to P. For example, the UE may increment the BWP-ID of the activated BWP by 1 as a rule for the number of configured BWPs. After repeating through all the configured BWPs, if the UE does not recover from the physical layer problem, the UE may switch to the defaultDownlinkBWP or the initialDownlinkBWP.

[0070] (Detection of RLF (Alternative 4)) In Alternative 4, the detection of RLF for NR-U may be based on the reception of N310 consecutive synchronization loss indications. The timer-based recovery period may not be defined. For example, when an N310 consecutive synchronization loss indication is detected, RLF is declared. In one example, the synchronization loss indication may be generated when a defective RLM-RS TXOP is detected. When the upper layer receives a synchronization loss indication, it may increment the counter N310 and declare RLF when the maximum value is reached. The counter N310 is reset when an N311 consecutive "in-sync" indication is received.

[0071] In an alternative example, the in-sync or synchronization loss indication may be generated within a frame where the UE detects a defect in the RLM-RS TXOP for all resources within a set of resources configured for radio link monitoring when the link quality is evaluated. When the upper layer receives a synchronization loss indication, it may increment the counter N310 and declare RLF when the maximum value is reached. The counter N310 may be reset when an N311 consecutive "in-sync" indication is received. N310 and N31 The counter value of 1 may not be updated during the frame in which the malfunction RLM-RS TXOP is detected. There may be cases where it is not.

[0072] In yet another example, the PHY layer provides an indication of an instance where the UE fails to detect the RL M reference signal to the upper layer due to the failure of LBT at the gNB. These instances may be referred to herein as malfunction RLM-RS TXOPs. When the UE upper layer receives a malfunction RLM-RS TXOP, it may not reset the counters N310 and N311. The reception of the malfunction RLM-RS TXOP indication by the upper layer may not affect the count of the received continuous In-Sync (IS) indication or the received continuous Out-Of-Sync (OOS) indication. Upon detection of a radio link problem, the timer (e.g., timer T310) used to control the declaration of a radio link failure is adjusted to represent the malfunction RLM-RS TXOP. For example, timer T310 may be stopped upon reception of a malfunction RLM-RS-TXOP and restarted upon reception of an IS indication or upon reception of an OOS indication. As soon as a radio link problem is detected, the timer (e.g., timer T310) used to control the declaration of a radio link failure is adjusted to represent the malfunction RLM-RS TXOP. For example, timer T310 may be stopped upon reception of a malfunction RLM-RS-TXOP and restarted upon reception of an IS indication or upon reception of an OOS indication. timer T310 may be stopped upon reception of a malfunction RLM-RS-TXOP and restarted upon reception of an IS indication or upon reception of an OOS indication. Upon reception of a malfunction RLM-RS-TXOP, it may be stopped and restarted upon reception of an IS indication or upon reception of an OOS indication. It may be restarted upon reception of an IS indication or upon reception of an OOS indication.

[0073] (Method for performing RRM measurements for NR-U) FIG. 6 is an exemplary NR-U measurement model in which when a malfunction RS TXOP is detected, a malfunction RS TXOP indication is provided to the upper layer to adapt the measurement function performed by RRC. Further explanation regarding measurement or filtering will be disclosed below. Explanation regarding measurement or filtering will be disclosed below. will be disclosed below. -A: Measurements inside the physical layer (beam-specific samples). - Layer 1 Filtering: Inner layer 1 filtering of the input measured at point A. Accurate filtering depends on the implementation form. Depending on the implementation form (input A and layer 1 filtering), therefore, how the measurement is actually performed at the physical layer is not forced by the standard. - A 1 : After layer 1 filtering, the measurement value reported by layer 1 to layer 3 (for example, beam-specific measurement value). When a defective RS TXOP is detected, L1 may discard the measurement samples that would have changed in response to the "defective" input. For example, layer 1 does not report that measurement value to layer 3. As a result, the rate of measurement samples at A may vary. 1 Alternatively, layer 1 reports all measurement values to layer 3, and layer 3 may discard the measurement samples associated with the defective RS TXOP. The discarding of measurement samples by layer 3 is based on a clear indication received from layer 1 (for example, a defective RX TXOP indicator, a measurement sample with a preliminary value, etc.), or layer 3 may apply a threshold test to determine whether the measurement samples should be discarded (for example, if the measurement value is less than the configured threshold, it is discarded). - Beam integration or selection: The beam-specific measurement values may be integrated to derive the cell quality. The operation of beam integration or selection is standardized, and the configuration of this module is provided by RRC signaling. The reporting period of B is equal to one measurement period of A. - B: The measurement value (for example, cell quality) derived from the beam-specific measurement values reported to layer 3 after beam integration or selection. The cell quality measurement value may not be derived for reporting during the period when the RS TXOP is defective for all beams. 1 -Layer 3 filtering of cell quality: Filtering is performed based on the provided measurement values, and the filtering may be an evaluation of the reporting criteria. It is checked whether the actual measurement report is required at point D. The evaluation may be based on, for example, two or more flows of measurement values at reference point C to compare different measurement values with each other. This is based on inputs C and C and what is shown . The evaluation may also be based on the detection of a malfunction RS TXOP. The UE may evaluate the reporting criteria at least each time, and new measurement results are reported when point C, C 1 or a malfunction RX TXOP is detected. The reporting criteria are standardized, and the configuration is provided by RRC signaling (UE measurement values). 1 -D: Measurement report information (message) transmitted on the radio interface. -L3 beam filtering: Filtering performed based on the measurement values provided at point A (e.g., beam-specific measurement values). The operation of the beam filter is standardized, and the configuration of this beam filter is provided by RRC signaling. The layer 3 filtering is adapted so that the time characteristics of the filter are retained when measurement samples are discarded. The filtering reporting period at E is equal to one measurement period at A . 1 -E: Measurement values (e.g., beam-specific measurement values) after being processed by the beam filter. The reporting rate may be the same as the reporting rate at point A . These measurement values may be used as inputs for selecting X measurement values to be reported . -Beam selection in beam reporting: Select X measurement values from the measurement values provided at point E 1 . 1 ​​​​​It is done. The operation of beam selection may be standardized, and the configuration of this module is provided by RRC signaling. -F: Beam measurement value information included in measurement reports (transmission) on the radio interface.

[0074] Regarding an alternative where L1 discards measurement samples that would have changed in response to a "fault" input , the operation of the beam integration or selection function, as described in section 5.5.3.3 of 3GPP TS 38.331, Radio Resource Control (RRC) protocol specification ( Release 15), V15.2.1, is disclosed herein. Regarding an alternative where the discarding of measurement samples that would have changed in response to a "fault" input is performed by layer 3, when at least one beam measurement corresponds to an RS TXOP without faults, the beam integration or selection function is proposed to generate cell measurement quantities. If a faulty RS TXOP is indicated for all beam measurements, the cell measurement quantities may not be generated. An exemplary description of this alternative beam integration or selection function is described in Table 23.

[0075]

Table 23

[0076] The L3 cell quality filtering function may output new measurement samples in response to receiving cell quality samples from the beam integration or selection function. Similarly, the L3 beam filtering function may output new measurement samples in response to receiving beam measurement values filtered at L1. A faulty RS TXOP indicator is provided as an input to these functions. Provided that these functions can determine when the measurement sample was discarded That's fine.

[0077] In one example, the layer 3 filter does not generate new power during the reporting period when the measurement sample is discarded. After one or more reporting periods in which the measurement sample was discarded, when the measurement sample is provided to the layer 3 filter as an input, the layer 3 filtering is adapted so that the time characteristics of the filter are maintained. For example, assume that a valid measurement value was provided during measurement reporting periods n and (n - x), but that valid measurement value was discarded during all other measurement reporting periods in between. Then the output of the layer 3 filter for sample n is calculated as follows.

[0078]

[0079]

Equation

[0080] An exemplary description of this alternative layer 3 filtering function is described in Table 24.

[0081]

Table 24

[0082] Alternatively, the layer 3 filter calculates a new output during the measurement period in which the sample was discarded. When the calculation is performed, the layer 3 filter may use a type of sample M that is scaled with respect to the value of sample M (e.g., M n = c * M , where 0 n-1 ≤ c ≤ 1). The value of c is defined according to the standard or signaled via a higher layer, e.g., RRC signaling. The same layer 3 filter may be used for the L3 beam filtering function, but it may also be configured to use different filter coefficients. n n-1 In addition to the measurement events defined for NR, it is proposed to define new events for NR-U based on the detection of defective RS TXOP, e.g., event Ax (defective RS TXOP detected in the serving cell), event Ay (defective RS TXOP detected in the neighboring cell). The start condition of such an event may be based on the number of defective RS TXOP detected exceeding a configured threshold during a predetermined time period, and the departure condition may be based on no defective RS TXOP being detected during a predetermined timer period. At this time, the parameters used for event configuration in the UE may be provided via higher layer signaling (e.g., RRC signaling) or defined according to the standard. Exemplary definitions of the proposed events are shown in Tables 25 and 26.

[0083]

[0084]

Table 25

[0085]

Table 26

[0086] The UE may be configured to include beam measurement information in the measurement report. During a reporting period in which measurement samples are discarded for a given beam, the L3 filter may not generate a new output or, if a new output is calculated, the new output may be based on old samples. In either case, the measurement results may be inaccurate. As disclosed, to notify the gNB of this situation, it may be effective to include a field in the beam measurement report indicating whether the accuracy of the beam measurement may have been affected by the discarding of measurement samples. For example, as shown in Table 27, the MeasQuantityR esults IE may be extended to include an enabling flag indicating whether the measurement accuracy may have been affected by the discarding of measurement samples. Alternatively the UE may exclude such beam measurement values from the measurement report.

[0087]

[0088]

Table 27

[0088] The measurement configuration may include a parameter that controls the timing at which the UE is required to perform neighbor cell measurements. This parameter may sometimes be referred to as S-measure . S-measure may correspond to a SpCell quality threshold against which the derived cell quality of the SpCell is compared. If the derived SpCell quality is below S-measure

[0088] When rotating, the UE may be required to perform neighbor cell measurements. The derived SpCe ll quality may be based on the SSB or CSI-RS reference signal.

[0089] For NR-U, reference values other than the derived SpCell quality may be used to control the timing at which the UE is required to perform neighbor cell measurements. For example, the UE may trigger neighbor cell measurements when the number of defective RS TXOPs detected during a configured time interval exceeds a threshold. In another example, channel occupancy measurements performed at the RSSI or the serving cell frequency may be compared with a threshold to control the timing at which the UE is required to perform neighbor cell measurements. The thresholds used in the proposed examples may be signaled to the UE via higher layers, e.g., RRC signaling. Another example, to control the timing at which the UE is required to perform neighbor cell measurements, such reference may be used in combination with the derived SpCell or by itself to control the timing at which the UE is required to perform neighbor cell measurements. For example, the UE may be configured to perform neighbor cell measurements when the SpCell quality is below a threshold, or when a defective RS TXOP is detected, there is a possibility that the RSSI exceeds a threshold, there is a possibility that the channel occupancy exceeds a threshold, etc.

[0090] Such criteria may be used in combination with the derived SpCell or by itself to control the timing at which the UE is required to perform neighbor cell measurements. For example, the UE may be configured to perform neighbor cell measurements when the SpCell quality is below a threshold, or when a defective RS TXOP is detected, there is a possibility that the RSSI exceeds a threshold, there is a possibility that the channel occupancy exceeds a threshold, etc.

[0091] An exemplary MeasConfig IE including the proposed parameters is shown in Figure 27.

[0092]

Table 28

[0093] FIG. 7 shows an exemplary method of implementing the disclosed subject matter. At step 221, monitoring of in-sync indication or out-of-sync indication may be performed. The in-sync indication or out-of-sync indication may be based on radio link quality. At step 222, monitoring of the number of defective RLM-RS TXOPs may be performed. At step 223 based on the monitored in-sync indication or out-of-sync indication combined with the monitored number of defective RLM-RS TXOPs, the user equipment may detect a radio link failure. Monitoring the number of defective RLM-RS TXOPs may be based on a discovery reference signal, a channel access indication, or another signal. One or more of the out-of-sync indications may be generated when there is a possibility that at least one of the defective RLM-RS TXOPs is detected. A timer T is set to an initial value and then may be counted down . Expiration of the timer may correspond to the timer reaching a zero value. Future changes to this method flow Evalu ate_missed_TXOP may be based on Tables 1 through 28 and the corresponding descriptions. Table 29 presents exemplary acronyms that may appear in this specification. Unless otherwise indicated, the acronyms used in this specification refer to the corresponding terms described in Table 29.

[0094]

[0095]

[0096] ​​​​ In particular, the entity that implements the steps shown herein, such as from Table 1 to Table 28, or from Figure 4 to Figure 7, should be understood to potentially be a logical entity. These steps may be stored in the memory of a user terminal, server, or computer system, and executed by their processors, as shown in Figure 9C or Figure 9D. Omissions, combinations, or additions of steps are contemplated among the exemplary methods disclosed herein. Figure 8 shows an exemplary display (e.g., a graphical user interface) that may be created based on the methods, systems, and devices for wireless link monitoring and radio resource management measurement procedures for NR-U, as discussed herein. The display interface 901 (e.g., a touch screen display) may display text related to the wireless link monitoring and radio resource management measurement procedures for NR-U, such as method flows and RRC-related parameters, in block 902. The progress of any of the steps discussed herein (e.g., message transmission or step success) may also be displayed within block 902. Additionally, a graphical output 902 may be displayed on the display interface 901. The graphical output 903 may be, for example, a graphical output of the topology of the device implementing the methods, systems, and devices for wireless link monitoring and radio resource management measurement procedures for NR-U, or the progress of any method or system discussed herein. should be understood to potentially be a logical entity. These steps may be stored in the memory of a user terminal, server, or computer system, and executed by their processors, as shown in Figure 9C or Figure 9D. Omissions, combinations, or additions of steps are contemplated among the exemplary methods disclosed herein. Figure 8 shows an exemplary display (e.g., a graphical user interface) that may be created based on the methods, systems, and devices for wireless link monitoring and radio resource management measurement procedures for NR-U, as discussed herein. The display interface 901 (e.g., a touch screen display) may display text related to the wireless link monitoring and radio resource management measurement procedures for NR-U, such as method flows and RRC-related parameters, in block 902. The progress of any of the steps discussed herein (e.g., message transmission or step success) may also be displayed within block 902. Additionally, a graphical output 902 may be displayed on the display interface 901. The graphical output 903 may be, for example, a graphical output of the topology of the device implementing the methods, systems, and devices for wireless link monitoring and radio resource management measurement procedures for NR-U, or the progress of any method or system discussed herein.

[0097] Figure 8 shows an exemplary display (e.g., a graphical user interface) that may be created based on the methods, systems, and devices for wireless link monitoring and radio resource management measurement procedures for NR-U, as discussed herein. The display interface 901 (e.g., a touch screen display) may display text related to the wireless link monitoring and radio resource management measurement procedures for NR-U, such as method flows and RRC-related parameters, in block 902. The progress of any of the steps discussed herein (e.g., message transmission or step success) may also be displayed within block 902. Additionally, a graphical output 902 may be displayed on the display interface 901. The graphical output 903 may be, for example, a graphical output of the topology of the device implementing the methods, systems, and devices for wireless link monitoring and radio resource management measurement procedures for NR-U, or the progress of any method or system discussed herein. Figure 8 shows an exemplary display (e.g., a graphical user interface) that may be created based on the methods, systems, and devices for wireless link monitoring and radio resource management measurement procedures for NR-U, as discussed herein. The display interface 901 (e.g., a touch screen display) may display text related to the wireless link monitoring and radio resource management measurement procedures for NR-U, such as method flows and RRC-related parameters, in block 902. The progress of any of the steps discussed herein (e.g., message transmission or step success) may also be displayed within block 902. Additionally, a graphical output 902 may be displayed on the display interface 901. The graphical output 903 may be, for example, a graphical output of the topology of the device implementing the methods, systems, and devices for wireless link monitoring and radio resource management measurement procedures for NR-U, or the progress of any method or system discussed herein. Figure 8 shows an exemplary display (e.g., a graphical user interface) that may be created based on the methods, systems, and devices for wireless link monitoring and radio resource management measurement procedures for NR-U, as discussed herein. The display interface 901 (e.g., a touch screen display) may display text related to the wireless link monitoring and radio resource management measurement procedures for NR-U, such as method flows and RRC-related parameters, in block 902. The progress of any of the steps discussed herein (e.g., message transmission or step success) may also be displayed within block 902. Additionally, a graphical output 902 may be displayed on the display interface 901. The graphical output 903 may be, for example, a graphical output of the topology of the device implementing the methods, systems, and devices for wireless link monitoring and radio resource management measurement procedures for NR-U, or the progress of any method or system discussed herein. Figure 8 shows an exemplary display (e.g., a graphical user interface) that may be created based on the methods, systems, and devices for wireless link monitoring and radio resource management measurement procedures for NR-U, as discussed herein. The display interface 901 (e.g., a touch screen display) may display text related to the wireless link monitoring and radio resource management measurement procedures for NR-U, such as method flows and RRC-related parameters, in block 902. The progress of any of the steps discussed herein (e.g., message transmission or step success) may also be displayed within block 902. Additionally, a graphical output 902 may be displayed on the display interface 901. The graphical output 903 may be, for example, a graphical output of the topology of the device implementing the methods, systems, and devices for wireless link monitoring and radio resource management measurement procedures for NR-U, or the progress of any method or system discussed herein. Figure 8 shows an exemplary display (e.g., a graphical user interface) that may be created based on the methods, systems, and devices for wireless link monitoring and radio resource management measurement procedures for NR-U, as discussed herein. The display interface 901 (e.g., a touch screen display) may display text related to the wireless link monitoring and radio resource management measurement procedures for NR-U, such as method flows and RRC-related parameters, in block 902. The progress of any of the steps discussed herein (e.g., message transmission or step success) may also be displayed within block 902. Additionally, a graphical output 902 may be displayed on the display interface 901. The graphical output 903 may be, for example, a graphical output of the topology of the device implementing the methods, systems, and devices for wireless link monitoring and radio resource management measurement procedures for NR-U, or the progress of any method or system discussed herein. Figure 8 shows an exemplary display (e.g., a graphical user interface) that may be created based on the methods, systems, and devices for wireless link monitoring and radio resource management measurement procedures for NR-U, as discussed herein. The display interface 901 (e.g., a touch screen display) may display text related to the wireless link monitoring and radio resource management measurement procedures for NR-U, such as method flows and RRC-related parameters, in block 902. The progress of any of the steps discussed herein (e.g., message transmission or step success) may also be displayed within block 902. Additionally, a graphical output 902 may be displayed on the display interface 901. The graphical output 903 may be, for example, a graphical output of the topology of the device implementing the methods, systems, and devices for wireless link monitoring and radio resource management measurement procedures for NR-U, or the progress of any method or system discussed herein. Figure 8 shows an exemplary display (e.g., a graphical user interface) that may be created based on the methods, systems, and devices for wireless link monitoring and radio resource management measurement procedures for NR-U, as discussed herein. The display interface 901 (e.g., a touch screen display) may display text related to the wireless link monitoring and radio resource management measurement procedures for NR-U, such as method flows and RRC-related parameters, in block 902. The progress of any of the steps discussed herein (e.g., message transmission or step success) may also be displayed within block 902. Additionally, a graphical output 902 may be displayed on the display interface 901. The graphical output 903 may be, for example, a graphical output of the topology of the device implementing the methods, systems, and devices for wireless link monitoring and radio resource management measurement procedures for NR-U, or the progress of any method or system discussed herein. Figure 8 shows an exemplary display (e.g., a graphical user interface) that may be created based on the methods, systems, and devices for wireless link monitoring and radio resource management measurement procedures for NR-U, as discussed herein. The display interface 901 (e.g., a touch screen display) may display text related to the wireless link monitoring and radio resource management measurement procedures for NR-U, such as method flows and RRC-related parameters, in block 902. The progress of any of the steps discussed herein (e.g., message transmission or step success) may also be displayed within block 902. Additionally, a graphical output 902 may be displayed on the display interface 901. The graphical output 903 may be, for example, a graphical output of the topology of the device implementing the methods, systems, and devices for wireless link monitoring and radio resource management measurement procedures for NR-U, or the progress of any method or system discussed herein. Figure 8 shows an exemplary display (e.g., a graphical user interface) that may be created based on the methods, systems, and devices for wireless link monitoring and radio resource management measurement procedures for NR-U, as discussed herein. The display interface 901 (e.g., a touch screen display) may display text related to the wireless link monitoring and radio resource management measurement procedures for NR-U, such as method flows and RRC-related parameters, in block 902. The progress of any of the steps discussed herein (e.g., message transmission or step success) may also be displayed within block 902. Additionally, a graphical output 902 may be displayed on the display interface 901. The graphical output 903 may be, for example, a graphical output of the topology of the device implementing the methods, systems, and devices for wireless link monitoring and radio resource management measurement procedures for NR-U, or the progress of any method or system discussed herein. Figure 8 shows an exemplary display (e.g., a graphical user interface) that may be created based on the methods, systems, and devices for wireless link monitoring and radio resource management measurement procedures for NR-U, as discussed herein. The display interface 901 (e.g., a touch screen display) may display text related to the wireless link monitoring and radio resource management measurement procedures for NR-U, such as method flows and RRC-related parameters, in block 902. The progress of any of the steps discussed herein (e.g., message transmission or step success) may also be displayed within block 902. Additionally, a graphical output 902 may be displayed on the display interface 901. The graphical output 903 may be, for example, a graphical output of the topology of the device implementing the methods, systems, and devices for wireless link monitoring and radio resource management measurement procedures for NR-U, or the progress of any method or system discussed herein. Figure 8 shows an exemplary display (e.g., a graphical user interface) that may be created based on the methods, systems, and devices for wireless link monitoring and radio resource management measurement procedures for NR-U, as discussed herein. The display interface 901 (e.g., a touch screen display) may display text related to the wireless link monitoring and radio resource management measurement procedures for NR-U, such as method flows and RRC-related parameters, in block 902. The progress of any of the steps discussed herein (e.g., message transmission or step success) may also be displayed within block 902. Additionally, a graphical output 902 may be displayed on the display interface 901. The graphical output 903 may be, for example, a graphical output of the topology of the device implementing the methods, systems, and devices for wireless link monitoring and radio resource management measurement procedures for NR-U, or the progress of any method or system discussed herein. Figure 8 shows an exemplary display (e.g., a graphical user interface) that may be created based on the methods, systems, and devices for wireless link monitoring and radio resource management measurement procedures for NR-U, as discussed herein. The display interface 901 (e.g., a touch screen display) may display text related to the wireless link monitoring and radio resource management measurement procedures for NR-U, such as method flows and RRC-related parameters, in block 902. The progress of any of the steps discussed herein (e.g., message transmission or step success) may also be displayed within block 902. Additionally, a graphical output 902 may be displayed on the display interface 901. The graphical output 903 may be, for example, a graphical output of the topology of the device implementing the methods, systems, and devices for wireless link monitoring and radio resource management measurement procedures for NR-U, or the progress of any method or system discussed herein.

[0098] The 3rd Generation Partnership Project (3GPP) is developing technical specifications for cellular telecommunication network technologies, including radio access, core transport networks, and service capabilities (including those that act on decoding, security, and quality of service). Recent radio access technology (RAT) specifications include WCDMA (commonly referred to as 3G), LTE (commonly referred to as 4G), LTE-Advanced specifications, and New Radio (NR), also referred to as "5G". 3GPP NR specification development is ongoing and is expected to include definitions of next-generation radio access technologies (new RATs), which are expected to include provisions for new flexible radio access below 7 GHz and new ultra-mobile broadband radio access above 7 GHz. Flexible radio access is expected to consist of new non-backward compatible radio access in new frequency bands below 6 GHz and is also expected to be multiplexed together in the same frequency band to include different operating modes that may address a wide set of 3GPP NR use cases with diverse requirements. Ultra-mobile broadband is expected to include centimeter and millimeter wave frequency bands that provide opportunities for ultra-mobile broadband access, for example, for indoor use and hotspots. In particular, ultra-mobile broadband with centimeter and millimeter wave design optimizations is expected to share a common design framework with flexible radio access below 7 GHz.

[0099] 3GPP has identified various user experience requirements for data rate, latency, and mobility and the various use cases expected to be supported by NR. The use cases include common categories, namely enhanced mobile broadband (eMBB), ultra-reliable and low-latency communication (URLLC), massive machine type communication (mMTC), network operations (e.g., network slicing, routing, migration, and interworking, energy saving), and enhanced vehicle-to-everything (eV2X) communication including any of vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-network (V2N), vehicle-to-pedestrian (V2P), and vehicle communication with other entities. Specific services and applications in these categories include, for example, some examples are monitoring and sensor networks, device remote control, two-way remote control, personal cloud computing, video streaming, wireless cloud -based office, emergency responder connectivity, automotive e-call, disaster warning, real -time gaming, multi-party video call, autonomous driving, augmented reality, tactile Internet, virtual reality, home automation, robotics, and aerial drones. All of these use cases and others are considered herein.

[0100] FIG. 9A shows an example of a communication system 100 in which the systems and methods described and claimed herein with reference to FIGS. 4-6 for wireless link monitoring and radio resource management measurement procedures for NR-U may be used. The communication system 100 may include one or more wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, 102e, 102f, or 102g (collectively or generically referred to as (one or more) WTRUs). The communication system 100 may also include a radio access network (RAN) 103 / 104 / 105 / 103b / 104b / 105b, a core network 106 / 107 / 109, a public switched telephone network (PSTN) 108, the Internet 110, other networks 112, and network services 113. Network services 113 may include, for example, a V2X server, V2X functionality, a ProSe server, ProSe functionality, an IoT service, video streaming, or edge computing. It should be understood that the concepts disclosed herein may be used with any number of WTRUs, base stations, networks, or network elements. Each of the WTRUs 102a, 102b, 102c, 102d, 102e, 102f, or 102g may be any type of device or apparatus configured to operate or communicate in a wireless environment. The WTRUs 102a, 102b, 102c, 102d, 102e, 102f, or 102g may be any type of device or apparatus configured to operate or communicate in a wireless environment. The WTRUs 102a, 102b, 102c, 102d, 102e, 102f, or 102g may be any type of device or apparatus configured to operate or communicate in a wireless environment. The WTRUs 102a, 102b, 102c, 102d, 102e, 102f, or 102g may be any type of device or apparatus configured to operate or communicate in a wireless environment. The WTRUs 102a, 102b, 102c, 102d, 102e, 102f, or 102g may be any type of device or apparatus configured to operate or communicate in a wireless environment. The WTRUs 102a, 102b, 102c, 102d, 102e, 102f, or 102g may be any type of device or apparatus configured to operate or communicate in a wireless environment. The WTRUs 102a, 102b, 102c, 102d, 102e, 102f, or 102g may be any type of device or apparatus configured to operate or communicate in a wireless environment. The WTRUs 102a, 102b, 102c, 102d, 102e, 102f, or 102g

[0101] It should be understood that the concepts disclosed herein may be used with any number of WTRUs, base stations, networks, or network elements. Each of the WTRUs 102a, 102b, 102c, 102d, 102e, 102f, or 102g may be any type of device or apparatus configured to operate or communicate in a wireless environment. The WTRUs 102a, 102b, 102c, 102d, 102e, 102f, or 102g each may be any type of device or apparatus configured to operate or communicate in a wireless environment. Each of the WTRUs 102a, 102b, 102c, 102d, 102e, 102f, or 102g may be any type of device or apparatus configured to operate or communicate in a wireless environment. Each of the WTRUs 102a, 102b, 102c, 102d, 102e, 102f, or 102g each may be any type of device or apparatus configured to operate or communicate in a wireless environment. Each of the WTRUs 102a, 102b, 102c, 102d, 102e, 102f, or 102g ​​Each of g may refer to the hand-held wireless communication device in FIGS. 9A, 9B, 9C, 9D, 9E, or 9F, but in various use cases contemplated for 5G wireless communication, each WTRU is, by way of example only, a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a pager, a cellular phone, a Personal Digital Assistant: PDA), a smartphone, a laptop, a tablet, a netbook, a notebook computer, a personal computer, a wireless sensor, a mass consumer electronic product, a wearable device such as a smartwatch or smart clothing, a medical or e- health device, a robot, an industrial device, a drone, for example, a vehicle such as a car, a bus, a truck, a train, or an airplane, or any type of device or apparatus configured to transmit or receive wireless signals, or may be embodied by them, should be understood.

[0102] Communication system 100 may also include base stations 114a and 114b. In the example of FIG. 9A, each base station 114a and 114b is shown as a single element. In reality, base stations 114a and 114b may include any number of interconnected base stations or network elements. Base station 114a wirelessly interfaces with at least one of WTRUs 102a, 102 b, and 102c and facilitates access to one or more communication networks such as core network 106 / 107 / 109, Internet 110, network services 113, or other network 112. Similarly, a base station may be any type of device configured to 114b interfaces, either wired or wirelessly, with at least one of Remote Radio Heads (RRHs) 118a, 118b, Transmission / Reception Points (TRPs) 119a, 119b, or Roadside Units (RSUs) 120a and 120b, and is any type of device configured to facilitate access to one or more communication networks such as core network 106 / 107 / 109, Internet 110, other network 112, or network service 113. RRHs 118a, 118b interface wirelessly with at least one of WTRUs 102, e.g., WTRU 102c, and are any type of device configured to facilitate access to one or more communication networks such as core network 106 / 107 / 109, Internet 110, network service 113, or other network 112. TRPs 119a, 119b interface wirelessly with at least one of WTRUs 102d and are any type of device configured to facilitate access to one or more communication networks such as core network 106 / 107 / 109, Internet 110, network service 113, or other network 112. RSUs 120a and 120b interface wirelessly with at least one of WTRUs 102e or 102f and are any type of device configured to facilitate access to one or more communication networks such as core network 106 / 107 / 109, Internet 110, other network 112, or network service 113.

[0103] To facilitate access to one or more communication networks such as Service 113 It may be any type of device configured as such. By way of example, base stations 114a, 114 b may be a Base Transceiver Station (BTS), Node-B, eNode B, Home NodeB, Home eNodeB, next-generation Node-B (gNode B), satellite, site controller, Access Point (AP), wireless router, etc. It may be, for example.

[0104] Base station 114a may be part of RANs 103 / 104 / 105, and those RANs may also include other base stations or network elements (not shown), such as a Base Station Controller (BSC), a Radio Network Controller (RNC), a relay node, etc. Similarly, base station 114b may be part of RANs 103b / 104b / 105b, and those RANs may also include other base stations or network elements (not shown), such as a BSC 、RNC、relay node, etc. Base station 114a may be configured to transmit or receive wireless signals within a specific geographical area, which may also be called a cell (not shown). Similarly, base station 114b may be configured to transmit or receive wired or wireless signals within a specific geographical area, which may be called a cell (not shown) related to the method, system, and device for wireless link monitoring and radio resource management measurement procedures for NR-U as disclosed in this specification. Similarly, base station 114b may be within a specific geographical area may also include other base stations or network elements (not shown), such as a BSC 、RNC、relay node, etc. Base station 114a may be configured to transmit or receive wireless signals within a specific geographical area, which may also be called a cell (not shown). Similarly, base station 114b may be configured to transmit or receive wired or wireless signals within a specific geographical area, which may be called a cell (not shown) related to the method, system, and device for wireless link monitoring and radio resource management measurement procedures for NR-U as disclosed in this specification. Similarly, base station 114b may be within a specific geographical area may also include other base stations or network elements (not shown), such as a BSC 、RNC、relay node, etc. Base station 114a may be configured to transmit or receive wireless signals within a specific geographical area, which may also be called a cell (not shown). Similarly, base station 114b may be configured to transmit or receive wired or wireless signals within a specific geographical area, which may be called a cell (not shown) related to the method, system, and device for wireless link monitoring and radio resource management measurement procedures for NR-U as disclosed in this specification. Similarly, base station 114b may be within a specific geographical area may also include other base stations or network elements (not shown), such as a BSC 、RNC、relay node, etc. Base station 114a may be configured to transmit or receive wireless signals within a specific geographical area, which may also be called a cell (not shown). Similarly, base station 114b may be configured to transmit or receive wired or wireless signals within a specific geographical area, which may be called a cell (not shown) related to the method, system, and device for wireless link monitoring and radio resource management measurement procedures for NR-U as disclosed in this specification. Similarly, base station 114b may be within a specific geographical area may also include other base stations or network elements (not shown), such as a BSC 、RNC、relay node, etc. Base station 114a may be configured to transmit or receive wireless signals within a specific geographical area, which may also be called a cell (not shown). Similarly, base station 114b may be configured to transmit or receive wired or wireless signals within a specific geographical area, which may be called a cell (not shown) related to the method, system, and device for wireless link monitoring and radio resource management measurement procedures for NR-U as disclosed in this specification. Similarly, base station 114b may be within a specific geographical It may be configured to transmit or receive wired or wireless signals within a geographical area, which geographical area may also be referred to as a cell (not shown). A cell may be further divided into cell sectors. For example, the cell associated with base station 114a may be divided into three sectors. Thus, in one example, base station 114a may include, for example, one of three transceivers for each sector of the cell. In one example, base station 114a may employ multiple-input multiple-output (MIMO) technology and thus may utilize multiple transceivers for each sector of the cell. There may be. For example, the cell associated with base station 114a may be divided into three sectors. For example, the cell associated with base station 114a may be divided into three sectors. Thus, in one example, base station 114a may include, for example, one of three transceivers for each sector of the cell. In one example, base station 114a may employ multiple-input multiple-output (MIMO) technology and thus may utilize multiple transceivers for each sector of the cell. (Multiple-Input Multiple Output: MIMO) technology, and thus may utilize multiple transceivers for each sector of the cell. (Multiple-Input Multiple Output: MIMO) technology, and thus may utilize multiple transceivers for each sector of the cell.

[0105] Base station 114a may communicate with one or more of WTRUs 102a, 102b, 102c, or 102g via an air interface 115 / 116 / 117, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.). The air interface 115 / 116 / 117 may be established using any suitable radio access technology (RAT). : RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.). The air interface 115 / 116 / 117 may be established using any suitable radio access technology (RAT). : RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.). The air interface 115 / 116 / 117 may be established using any suitable radio access technology (RAT). Base station 114a may communicate with one or more of WTRUs 102a, 102b, 102c, or 102g via an air interface 115 / 116 / 117, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.). The air interface 115 / 116 / 117 may be established using any suitable radio access technology (RAT). Base station 114a may communicate with one or more of WTRUs 102a, 102b, 102c, or 102g via an air interface 115 / 116 / 117, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.). The air interface 115 / 116 / 117 may be established using any suitable radio access technology (RAT). Base station 114a may communicate with one or more of WTRUs 102a, 102b, 102c, or 102g via an air interface 115 / 116 / 117, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.). The air interface 115 / 116 / 117 may be established using any suitable radio access technology (RAT).

[0106] Base station 114b may communicate with one or more of RRHs 118a, 118b, TRPs 119a, 119b, or RSUs 120a, 120b via a wired or air interface 115b / 116b / 117b, which may be any suitable wired (e.g., cable, fiber optic, etc.) or wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.). Base station 114b may communicate with one or more of RRHs 118a, 118b, TRPs 119a, 119b, or RSUs 120a, 120b via a wired or air interface 115b / 116b / 117b, which may be any suitable wired (e.g., cable, fiber optic, etc.) or wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.). Base station 114b may communicate with one or more of RRHs 118a, 118b, TRPs 119a, 119b, or RSUs 120a, 120b via a wired or air interface 115b / 116b / 117b, which may be any suitable wired (e.g., cable, fiber optic, etc.) or wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.). Base station 114b may communicate with one or more of RRHs 118a, 118b, TRPs 119a, 119b, or RSUs 120a, 120b via a wired or air interface 115b / 116b / 117b, which may be any suitable wired (e.g., cable, fiber optic, etc.) or wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.). Base station 114b may communicate with one or more of RRHs 118a, 118b, TRPs 119a, 119b, or RSUs 120a, 120b via a wired or air interface 115b / 116b / 117b, which may be any suitable wired (e.g., cable, fiber optic, etc.) or wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.). The air interfaces 115b / 116b / 117b may be established using any suitable radio access technology (RAT).

[0107] RRH 118a, 118b, TRP 119a, 119b or RSU 120a, 120 b may communicate with one or more of WTRU 102c, 102d, 10 2e, 102f via an air interface 115c / 116c / 117c which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared ( IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.). The air interface 1 15c / 116c / 117c may be established using any suitable radio access technology (RAT).

[0108] WTRU 102a, 102b, 102c, 102d, 102e or 102f may communicate with each other via a side link communication air interface 115d / 116d / 117d which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet ( UV), visible light, centimeter wave, millimeter wave, etc.). The air interface 115d / 116d / 117d may be established using any suitable radio access technology (RAT).

[0109] The communication system 100 may be a multiple access system and may employ one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, SC - FDMA, etc. For example, the base stations 1 within RAN 103 / 104 / 105 14a and WTRU102a, 102b, 102c, or RAN103b / 104 RRH118a, 118b, TRP119a, 119b and RSU1 within b / 105b 20a, 120b and WTRU102c, 102d, 102e, 102f are universal mobile telecommunications systems (Universal Mobile Telecommunications System: UM TS), terrestrial radio access (Universal Terrestrial Radio Access: UTRA), etc. of radio technologies may be implemented, whereby wideband CDMA (Wideband CDMA: WCDMA ) can be used to establish air interfaces 115 / 116 / 117 or 115c / 116c / 117c respectively. WCDMA may include communication protocols such as high-speed packet access (Hi gh-Speed Packet Access: HSPA) or evolved HSPA (Evolved HSPA: HSP A+). HSPA may include high-speed downlink packet access (High-Speed Downlink Packet Access: HSDPA) or high-speed uplink packet access (High-Speed Uplink Packet Access: HSUPA).

[0110] In one example, base station 114a and WTRU102a, 102b, 102c, or R RRH118a, 118b, TRP119a, 1 within RAN103b / 104b / 105b 19b or RSU120a, 120b and WTRU102c, 102d are evolved UM TS terrestrial radio access (Evolved UMTS Terrestrial Radio Access: E-UTRA) ​​may implement wireless technologies such as Long-Term Evolution (LTE) or LTE-Advanced (LTE-A) to establish air interfaces 115 / 116 / 117 or 115c / 116c / 117c, respectively In the future, air interfaces 115 / 116 / 117 or 115c / 116c / 117c may implement 3GPP NR technology. LTE and LTE-A technologies may include LTE D2D and V2X technologies (such as sidelink communication) and interfaces -A technologies may include LTE D2D and V2X technologies (such as sidelink communication) and interfaces Similarly, 3GPP NR technology may include NR V2X technologies (such as sidelink communication) and interfaces

[0111] The base station 114a within RAN103 / 104 / 105 and the WTRUs 102a, 102b, 102c, and 102g, or the remote radio heads (RRHs) 118a, 118b, transmit receive points (TRPs) 119a, 119b or roadside units (RSUs) 120a, 120b within RAN103b / 104b / 105 and the WTRUs 102c, 102d, 102e, 102f may communicate via IEEE802.16 (e.g., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000 CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile Communications (GSM) (IS-856), Global System for Mobile Communications (GSM) Communications: GSM (registered trademark), Enhanced Data Rates For GSM Evolution (EDGE), GSM EDGE (GERAN), etc. Wireless technologies such as these may be implemented.

[0112] The base station 114c in FIG. 9A may be a wireless router, a Home Node B, a Home eNode B, or an access point, and for NR-U as discussed herein, To implement wireless link monitoring and radio resource management measurement procedures, methods, systems, and devices For example, to facilitate wireless connectivity within a local area such as an office, home, vehicle, train, aircraft, satellite, manufacturing plant, campus, etc., any suitable RAT May be utilized. In one example, the base station 114c and the WTRU 102, e.g., the WTRU 102e, may implement a wireless technology such as IEEE 802.11 to establish a Wireless Local Area Network (WLAN). Similarly, The base station 114c and the WTRU 102, e.g., the WTRU 102d, may implement a wireless technology such as IEEE 802.1 5 to establish a Wireless Personal Area Network (WPAN). In yet another example, the base station 114c and The WTRU 102, e.g., the WTRU 102e, may utilize a cellular-based RAT (e.g., W CDMA, CDMA2000, GSM, LTE, LTE-A, NR, etc.) to establish a picocell or femtocell. As shown in FIG. 9A, the base station 114c may Have a direct connection to the Internet 110. Thus, the base station 114c , in order to access the Internet 110, it may not be necessary to go through the core network 106 / 107 / 10 9.

[0113] RAN 103 / 104 / 105 or RAN 103b / 104b / 105b may communicate with the core net work 106 / 107 / 109, and that core network may provide voice, data, message transmission, authorization and authentication, applications, or Voice Over Internet Protocol (VoIP) services to one or more of WTRUs 102a, 102b, 102c, 102d. Any type of network configured to do so may be used. For example, the core net work 106 / 107 / 109 may provide call control, billing services, mobile location-based services, prepaid calls, Internet connectivity, packet data network connectivity, Ethernet connectivity, video distribution, etc., or may perform high-level security functions such as user authentication. Although not shown in FIG. 9A, it should be understood that RAN 103 / 104 / 105 or RAN 103b / 104b / 105b or the core network 106 / 107 / 109 may communicate directly or indirectly with other RANs that employ the same or a different Radio Access Technology (RAT). For example, in addition to being connected to RAN 103 / 104 / 105 or RAN 103b / 104b / 105b that may utilize E-UTRA radio technology, the core network 106 / 107 / 109

[0114] Although not shown in FIG. 9A, it should be understood that RAN 103 / 104 / 105 or RAN 103b / 104b / 105b or the core network 106 / 107 / 109 may communicate directly or indirectly with other RANs that employ the same or a different RAT. For example, in addition to being connected to RAN 103 / 104 / 105 or RAN 103b / 104b / 105b that may utilize E-UTRA radio technology, the core network 106 / 107 / 109 may communicate directly or indirectly with other RANs that employ the same or a different RAT. For example, in addition to being connected to RAN 103 / 104 / 105 or RAN 103b / 104b / 105b that may utilize E-UTRA radio technology, the core network 106 / 107 / 109 may communicate directly or indirectly with other RANs that employ the same or a different RAT. For example, in addition to being connected to RAN 103 / 104 / 105 or RAN 103b / 104b / 105b that may utilize E-UTRA radio technology, the core network 106 / 107 / 109 may communicate directly or indirectly with other RANs that employ the same or a different RAT. For example, in addition to being connected to RAN 103 / 104 / 105 or RAN 103b / 104b / 105b that may utilize E-UTRA radio technology, the core network 106 / 107 / 109 may also communicate with another RAN (not shown) that employs GSM or NR radio technology. It may communicate.

[0115] The core network 106 / 107 / 109 may also function as a gateway for WTRUs 102a, 102b, 10 2c, 102d, 102e to access the PSTN 108, the Internet 110, or other network works 112. The PSTN 108 may include a circuit-switched telephone network that provides Plain Old Telephone Service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols such as the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and the Internet Protocol (IP) of the TCP / IP Internet protocol suite. r Datagram Protocol:UDP), and the TCP / IP Internet protocol suite's Internet Protocol (IP). The network 112 may include a wired or wireless communication network that is owned or operated by another service provider. For example, the network 112 may be any type of packet data network (e.g., an IEEE802.3 Ethernet (registered trademark) network), or another core network that is connected to one or more RANs that may employ the same RAT or a different RAT as the RANs 103 / 104 / 105 or RANs 103b / 104b / 105b. The network 112 may include a wired or wireless communication network that is owned or operated by another service provider. For example, the network 112 may be any type of packet data network (e.g., an IEEE802.3 Ethernet (registered trademark) network), or another core network that is connected to one or more RANs that may employ the same RAT or a different RAT as the RANs 103 / 104 / 105 or RANs 103b / 104b / 105b.

[0116] Some or all of the WTRUs 102a, 102b, 102c, 102d, 102e and 102f within the communication system 100 may have multi-mode capabilities, e.g., the W TRUs 102a, 102b, 102c, 102d, 102e and 102f may include multiple transceivers for communicating with different wireless networks over different wireless links to implement the wireless link monitoring and radio resource management measurement procedures, systems, and devices disclosed herein. For example, the WTRU 102g shown in FIG. 9A may be configured to communicate with a base station 114a that may employ cellular-based wireless technology and a base station 114c that may employ IEEE 802 wireless technology. Although not shown in FIG. 9A, it will be appreciated that a user terminal may make a wired connection to a gateway. The gateway may be a Residential Gateway (RG). The RG may provide connectivity to the core network 106 / 107 / 109. Many of the concepts included herein may similarly apply to UEs that are WTRUs and UEs that use a wired connection to connect to a network. For example, the concepts applied to the wireless interfaces 115, 116, 117 and 115c / 116c / 117c may similarly apply to a wired connection. FIG. 9B may illustrate a RAN 103 that may implement the methods, systems, and devices for the wireless link monitoring and radio resource management measurement procedures for NR-U disclosed herein. Although not shown in FIG. 9A, it will be appreciated that a user terminal may make a wired connection to a gateway. The gateway may be a Residential Gateway (RG). The RG may provide connectivity to the core network 106 / 107 / 109. Many of the concepts included herein may similarly apply to UEs that are WTRUs and UEs that use a wired connection to connect to a network. For example, the concepts applied to the wireless interfaces 115, 116, 117 and 115c / 116c / 117c may similarly apply to a wired connection. Although not shown in FIG. 9A, it will be appreciated that a user terminal may make a wired connection to a gateway. The gateway may be a Residential Gateway (RG). The RG may provide connectivity to the core network 106 / 107 / 109. Many of the concepts included herein may similarly apply to UEs that are WTRUs and UEs that use a wired connection to connect to a network. For example, the concepts applied to the wireless interfaces 115, 116, 117 and 115c / 116c / 117c may similarly apply to a wired connection. Although not shown in FIG. 9A, it will be appreciated that a user terminal may make a wired connection to a gateway. The gateway may be a Residential Gateway (RG). The RG may provide connectivity to the core network 106 / 107 / 109. Many of the concepts included herein may similarly apply to UEs that are WTRUs and UEs that use a wired connection to connect to a network. For example, the concepts applied to the wireless interfaces 115, 116, 117 and 115c / 116c / 117c may similarly apply to a wired connection.

[0117] Although not shown in FIG. 9A, it will be appreciated that a user terminal may make a wired connection to a gateway. The gateway may be a Residential Gateway (RG). The RG may provide connectivity to the core network 106 / 107 / 109. Many of the concepts included herein may similarly apply to UEs that are WTRUs and UEs that use a wired connection to connect to a network. For example, the concepts applied to the wireless interfaces 115, 116, 117 and 115c / 116c / 117c may similarly apply to a wired connection. Although not shown in FIG. 9A, it will be appreciated that a user terminal may make a wired connection to a gateway. The gateway may be a Residential Gateway (RG). The RG may provide connectivity to the core network 106 / 107 / 109. Many of the concepts included herein may similarly apply to UEs that are WTRUs and UEs that use a wired connection to connect to a network. For example, the concepts applied to the wireless interfaces 115, 116, 117 and 115c / 116c / 117c may similarly apply to a wired connection. Although not shown in FIG. 9A, it will be appreciated that a user terminal may make a wired connection to a gateway. The gateway may be a Residential Gateway (RG). The RG may provide connectivity to the core network 106 / 107 / 109. Many of the concepts included herein may similarly apply to UEs that are WTRUs and UEs that use a wired connection to connect to a network. For example, the concepts applied to the wireless interfaces 115, 116, 117 and 115c / 116c / 117c may similarly apply to a wired connection. Although not shown in FIG. 9A, it will be appreciated that a user terminal may make a wired connection to a gateway. The gateway may be a Residential Gateway (RG). The RG may provide connectivity to the core network 106 / 107 / 109. Many of the concepts included herein may similarly apply to UEs that are WTRUs and UEs that use a wired connection to connect to a network. For example, the concepts applied to the wireless interfaces 115, 116, 117 and 115c / 116c / 117c may similarly apply to a wired connection. Although not shown in FIG. 9A, it will be appreciated that a user terminal may make a wired connection to a gateway. The gateway may be a Residential Gateway (RG). The RG may provide connectivity to the core network 106 / 107 / 109. Many of the concepts included herein may similarly apply to UEs that are WTRUs and UEs that use a wired connection to connect to a network. For example, the concepts applied to the wireless interfaces 115, 116, 117 and 115c / 116c / 117c may similarly apply to a wired connection. Although not shown in FIG. 9A, it will be appreciated that a user terminal may make a wired connection to a gateway. The gateway may be a Residential Gateway (RG). The RG may provide connectivity to the core network 106 / 107 / 109. Many of the concepts included herein may similarly apply to UEs that are WTRUs and UEs that use a wired connection to connect to a network. For example, the concepts applied to the wireless interfaces 115, 116, 117 and 115c / 116c / 117c may similarly apply to a wired connection. Although not shown in FIG. 9A, it will be appreciated that a user terminal may make a wired connection to a gateway. The gateway may be a Residential Gateway (RG). The RG may provide connectivity to the core network 106 / 107 / 109. Many of the concepts included herein may similarly apply to UEs that are WTRUs and UEs that use a wired connection to connect to a network. For example, the concepts applied to the wireless interfaces 115, 116, 117 and 115c / 116c / 117c may similarly apply to a wired connection. Although not shown in FIG. 9A, it will be appreciated that a user terminal may make a wired connection to a gateway. The gateway may be a Residential Gateway (RG). The RG may provide connectivity to the core network 106 / 107 / 109. Many of the concepts included herein may similarly apply to UEs that are WTRUs and UEs that use a wired connection to connect to a network. For example, the concepts applied to the wireless interfaces 115, 116, 117 and 115c / 116c / 117c may similarly apply to a wired connection.

[0118] FIG. 9B may illustrate a RAN 103 that may implement the methods, systems, and devices for the wireless link monitoring and radio resource management measurement procedures for NR-U disclosed herein. Although not shown in FIG. 9A, it will be appreciated that a user terminal may make a wired connection to a gateway. The gateway may be a Residential Gateway (RG). The RG may provide connectivity to the core network 106 / 107 / 109. Many of the concepts included herein may similarly apply to UEs that are WTRUs and UEs that use a wired connection to connect to a network. For example, the concepts applied to the wireless interfaces 115, 116, 117 and 115c / 116c / 117c may similarly apply to a wired connection. And it is a system diagram of an example of the core network 106. As described above, RAN 103 may adopt UTRA radio technology and communicate with WTRUs 102a , 102b, and 102c through the air interface 115. RAN 103 may also communicate with the core network 10 6. As shown in FIG. 9B, RAN 103 may include one or more transceivers each for communicating with WTRUs 102a, 102b, and 102c through the air interface 11 5, such as Node-Bs 140a, 140b, and 1 40c. Node-Bs 140a, 140b, and 140c may each be associated with a specific cell (not shown) within RAN 103. RAN 103 may also include RNCs 142a, 142b. It will be understood that RAN 103 may include any number of Node-Bs and radio network controllers (RNCs).

[0119] As shown in FIG. 9B, Node-Bs 140a, 140b may communicate with RNC 142a . Additionally, Node-B 140c may communicate with RNC 142b. Node-Bs 140a, 140b, and 140c may communicate with the corresponding RNCs 142a and 142b via the Iub interface . RNCs 142a and 142 b may communicate with each other via the Iur interface. Each of RNCs 142a and 142b may be configured to control the respective connected Node-Bs 140a, 140b, and 140c. Additionally, each of RNCs 142a, 142b may perform outer loop power control, load control, admission control, packet scheduling, handover control, etc. Other functions such as handover control, macro diversity, security functions, data encryption, etc. may be configured to execute or support.

[0120] The core network 106 shown in FIG. 9B includes a media gateway (Media Gateway : MGW) 144, a mobile switching center (Mobile Switching Center: MSC) 146, a serving GPRS support node (Serving GPRS Support Node: SGSN) 148, or may include a gateway GPRS support node (Gateway GPRS Support Node: GGSN ) 150. Each of the above-described elements is represented as part of the core network 106, but it should be understood that any one of these elements may be owned or operated by an entity other than the core network operator.

[0121] The RNC 142a within the RAN 103 may be connected to the MSC 146 within the core network 106 via the IuCS interface. The MSC 146 may be connected to the MGW 144. The MSC 146 and the MGW 144 provide access to a circuit-switched network such as the PSTN 108 to the WTRUs 102a, 102b, and 1 02c, and may facilitate communication between the WTRUs 102a, 102b, and 102c and conventional terrestrial communication devices.

[0122] The RNC 142a within the RAN 103 may also be connected to the SGSN 148 within the core network 106 via the IuPS interface. The SGSN 148 may be connected to the GGSN 1 50. The SGSN 148 and the GGSN 150 provide access to a packet-switched network such as the Internet to the WTRUs 102a, 1 02b and 102c may provide access to a packet switched network such as the Internet 110 and facilitate communication between the WTRUs 102a, 102b and 102c and IP-enabled devices.

[0123] The core network 106 may also be connected to other networks 112 that may include other wired or wireless networks owned or operated by other service providers.

[0124] Figure 9C is a system diagram of an example of a RAN 104 and core network 107 that may implement the methods, systems, and devices for wireless link monitoring and radio resource management measurement procedures for NR-U disclosed herein. As described above, the RAN 104 may employ E-UTRA radio technology and communicate with the WTRUs 10 2a, 102b and 102c through the air interface 116. The RAN 104 may also communicate with the core network 107.

[0125] The RAN 104 may include eNode-Bs 160a, 160b and 160c but it will be understood that the RAN 104 may include any number of eNode-Bs. The eNode-Bs 160a, 160b and 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b and 102c through the air interface 116. For example, the eNode-Bs 160a, 160b and 160c may implement MIMO technology. Thus, the eNode-B 160a may transmit a radio signal to, for example, the WTRU 102a and receive a radio signal from the WTRU 102a Multiple antennas may be used to receive it.

[0126] Each of eNode-Bs 160a, 160b, and 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, user scheduling in the uplink or downlink, etc. As shown in Figure 9C, eNode-Bs 160a, 160b, and 160c may communicate with each other through an X2 interface. As shown in Figure 9C, eNode-Bs 160a, 160b, and 160c may communicate with each other through an X2 interface.

[0127] The core network 107 shown in Figure 9C may include a Mobility Management Gateway (MME) 162, a Serving Gateway 164, and a Packet Data Network (PDN) Gateway 166. Although each of the above-described elements is represented as part of the core network 107, it will be understood that any one of these elements may be owned or operated by an entity other than the core network operator. Although each of the above-described elements is represented as part of the core network 107, it will be understood that any one of these elements may be owned or operated by an entity other than the core network operator. Although each of the above-described elements is represented as part of the core network 107, it will be understood that any one of these elements may be owned or operated by an entity other than the core network operator. Although each of the above-described elements is represented as part of the core network 107, it will be understood that any one of these elements may be owned or operated by an entity other than the core network operator.

[0128] The MME 162 may be connected to each of eNode-Bs 160a, 160b, and 160c within the RAN 104 via an S1 interface and may function as a control node. For example, the MME 162 may authenticate users of WTRUs 102a, 102b, and 102c, activate / deactivate bearers, select a particular serving gateway during the initial connection of WTRUs 102a, 102b, and 102c, etc. For example, the MME 162 may authenticate users of WTRUs 102a, 102b, and 102c, activate / deactivate bearers, select a particular serving gateway during the initial connection of WTRUs 102a, 102b, and 102c, etc. For example, the MME 162 may authenticate users of WTRUs 102a, 102b, and 102c, activate / deactivate bearers, select a particular serving gateway during the initial connection of WTRUs 102a, 102b, and 102c, etc. For example, the MME 162 may authenticate users of WTRUs 102a, 102b, and 102c, activate / deactivate bearers, select a particular serving gateway during the initial connection of WTRUs 102a, 102b, and 102c, etc. The MME 162 may also communicate with the RAN 104 and GSM or WCDMA networks. A control plane function may be provided to switch between the RAN (not shown) employing any other radio technology and another RAN. This may provide a handover function.

[0129] The serving gateway 164 may be connected to each of the eNode-Bs 160a, 160b, and 160c within the RAN 104 via the S1 interface. The serving gateway 164 may generally route and transfer user data packets to / from the WTRUs 102a, 102b, and 102c. The serving gateway 164 may also perform other functions such as being the anchor of the user plane during eNodeB handover, triggering paging when downlink data is available to the WTRUs 102a, 102b, and 102c, and managing and storing the contexts of the WTRUs 102a, 102b, and 102c. The serving gateway 164 may also provide access to the WTRUs 102a, 102b, and 102c to a packet switched network such as the Internet 110 and may facilitate communication between the WTRUs 102a, 102b, and 102c and IP-enabled devices. The serving gateway 164 may be connected to a PDN gateway 166 which may facilitate communication between the WTRUs 102a,

[0130] The serving gateway 164 may also provide the WTRUs 102a, 102b, and 102c with access to a packet switched network such as the Internet 110 and may facilitate communication between the WTRUs 102a, 102b, and 102c and IP-enabled devices. The serving gateway 164 may be connected to a PDN gateway 166 which may facilitate communication between the WTRUs 102a, 102b, and 102c and IP-enabled devices.

[0131] The core network 107 may facilitate communication with other networks. For example, the core network 107 may provide the WTRUs 102a, 102b, and 102c with access to a circuit switched network such as the PSTN 108 and may facilitate communication between the WTRUs 102a, 102b, and 102c and conventional land communication devices. For example, the core network 107 may provide the WTRUs 102a, 102b, and 102c with access to a circuit switched network such as the 07 functions as an interface between the core network 107 and the PSTN 108 and may include, or communicate with, an IP gateway (e.g., an IP Multimedia Subsystem: IMS server). In addition, the core network 107 may provide access to the network 112 that may include other wired or wireless networks owned or operated by other service providers to the WTRUs 102a, 102b, and 102c.

[0132] Figure 9D is a system diagram of an example of a RAN 105 and a core network 109 that may implement the methods, systems, and devices for wireless link monitoring and radio resource management for NR-U disclosed herein. The RAN 105 may employ NR radio technology and communicate with the WTRUs 102a and 102b through an air interface 117 . The RAN 105 may also communicate with the core network 109. A Non-3GPP Interworking Function (N3IWF) 199 may employ Non-3GPP radio technology and communicate with the WTRU 102c through an air interface 198 . The N3IWF 199 may also communicate with the core network 109. .

[0133] The RAN 105 may include gNode-Bs 180a and 180b. It will be understood that the RAN 105 may include any number of gNode-Bs . The gNode-Bs 180a and 180b each communicate with the WTRU 10 through the air interface 117 ​2a and 102b. When integrated access and backhaul connections are used, the same air interface , a WTRU and a core network 109 via one or more gNBs. The gNode-Bs 180a and 180b may be used between the gNode-Bs 180a and 180b. MIMO, MU-MIMO, or digital beamforming techniques may be implemented. Thus, the gNode-B 180a may transmit a wireless signal to the WTRU 102a, for example. and using multiple antennas to receive wireless signals from the WTRU 102a. The RAN 105 may employ other types of base stations, such as eNode-B. It should be understood that the RAN 105 may employ more than one type of base station. For example, the RAN may include an eNode-B and a gNode-B. B may be adopted.

[0134] The N3IWF 199 may include a non-3GPP access point 180c. It is understood that WF199 may include any number of non-3GPP access points. The non-3GPP access point 180c communicates with the wireless LAN through the air interface 198. It may include one or more transceivers for communicating with the TRU 102c. The access point 180c communicates over the air interface using the 802.11 protocol. The WTRU 102c may communicate with the WTRU 102c via a hub 198.

[0135] Each of the gNode-Bs 180a and 180b is associated with a particular cell (not shown). and radio resource management decisions, handover decisions, uplink or downlink It may be configured to handle user scheduling in a link, etc. Figure 9D As shown in, gNode-Bs 180a and 180b may communicate with each other, for example, through the Xn interface s.

[0136] The core network 109 shown in Figure 9D may be a 5G core network (5G Core Netw ork: 5GC). The core network 109 may provide a very large number of communication services to customers interconnected by a radio access network . The core network 109 includes several entities that implement the functions of the core network. As used herein, the term "core network entity" or "network function" means any entity that implements one or more functions of the core network. A core network entity may be a logical entity stored in the memory of a device configured for wireless or network communication, or for a computer system such as the system 90 shown in Figure 9G, and implemented in the form of computer-executable instructions (software ware) executable by a processor of the device, and it is understood that it may also be in this form.

[0137] In the example of Figure 9D, the 5G core network 109 includes an Access and Mobility Management Function (AMF) 172, a Session Management Function (SMF) 174, User Plane Functions (UPF) 176a and 176b, a User Data Management Function (User Data Managem ction: UPF) 176a and 176b, a User Data Management Function (User Data Managem Entity Function: UDM) 197. Authentication Server Function : AUSF) 190. Network Exposure Function n: NEF) 196. Policy Control Function: PCF) 184 Non-3GPP Interworking Function (N3IWF) 199. User Data Repository (UDR) 178 may be included. Each of the above elements is represented as part of the 5G core network 109, but any one of these elements may be owned or operated by an entity other than the core network operator. It should be understood that the 5G core network may not be composed of all of these elements, may be composed of additional elements, and may be composed of multiple instances of each of these elements. Each network function is shown in FIG. 9D to be directly connected to each other, but it should be understood that they may communicate via a routing agent such as a Diameter routing agent or a message bus. er Data Repository: UDR) 178 may be included. Each of the above elements is represented as part of the 5G core network 109, but any one of these elements may be owned or operated by an entity other than the core network operator. It should be understood that the 5G core network may not be composed of all of these elements, may be composed of additional elements, and may be composed of multiple instances of each of these elements. Each network function is shown in FIG. 9D to be directly connected to each other, but it should be understood that they may communicate via a routing agent such as a Diameter routing agent or a message bus. G core network 109, but any one of these elements may be owned or operated by an entity other than the core network operator. It should be understood that the 5G core network may not be composed of all of these elements, may be composed of additional elements, and may be composed of multiple instances of each of these elements. Each network function is shown in FIG. 9D to be directly connected to each other, but it should be understood that they may communicate via a routing agent such as a Diameter routing agent or a message bus. One of them may be owned or operated by an entity other than the core network operator. It should be understood that the 5G core network may not be composed of all of these elements, may be composed of additional elements, and may be composed of multiple instances of each of these elements. Each network function is shown in FIG. 9D to be directly connected to each other, but it should be understood that they may communicate via a routing agent such as a Diameter routing agent or a message bus. 5G core network may not be composed of all of these elements, may be composed of additional elements, and may be composed of multiple instances of each of these elements. Each network function is shown in FIG. 9D to be directly connected to each other, but it should be understood that they may communicate via a routing agent such as a Diameter routing agent or a message bus. It should be understood that the 5G core network may not be composed of all of these elements, may be composed of additional elements, and may be composed of multiple instances of each of these elements. Each network function is shown in FIG. 9D to be directly connected to each other, but it should be understood that they may communicate via a routing agent such as a Diameter routing agent or a message bus. Each network function is shown in FIG. 9D to be directly connected to each other, but it should be understood that they may communicate via a routing agent such as a Diameter routing agent or a message bus. FIG. 9D, the connectivity between network functions is realized through a set of interfaces or reference points. It should be understood that network functions may be modeled, described, or implemented as being initiated or called by other network functions or services, or as a set of services. The initiation of network function services may involve direct connections between network functions, message exchanges on a message bus, It should be understood that network functions may be modeled, described, or implemented as being initiated or called by other network functions or services, or as a set of services. The initiation of network function services may involve direct connections between network functions, message exchanges on a message bus, or other means.

[0138] In the example of FIG. 9D, the connectivity between network functions is realized through a set of interfaces or reference points. It should be understood that network functions may be modeled, described, or implemented as being initiated or called by other network functions or services, or as a set of services. The initiation of network function services may involve direct connections between network functions, message exchanges on a message bus, In the example of FIG. 9D, the connectivity between network functions is realized through a set of interfaces or reference points. It should be understood that network functions may be modeled, described, or implemented as being initiated or called by other network functions or services, or as a set of services. The initiation of network function services may involve direct connections between network functions, message exchanges on a message bus, or other means. It should be understood that network functions may be modeled, described, or implemented as being initiated or called by other network functions or services, or as a set of services. The initiation of network function services may involve direct connections between network functions, message exchanges on a message bus, or other means. or other means. The initiation of network function services may involve direct connections between network functions, message exchanges on a message bus, It can be realized through the call of software functions.

[0139] AMF172 may be connected to RAN105 via the N2 interface and function as a control node. For example, AMF172 may play roles in registration management, connection management, reachability management, access authentication, and access authorization. AMF may be responsible for delivering user plane tunnel configuration information to RAN105 via the N2 interface . AMF172 may receive user plane tunnel configuration information from SMF via the N11 interface. AMF172 generally routes and transfers NAS packets to / from WTRU102a, 102b, and 102c via the N1 interface . The N1 interface is not shown in FIG. 9D.

[0140] SMF174 may be connected to AMF172 via the N11 interface. Similarly, SMF may be connected to PCF184 via the N7 interface and to UPF176a and 176b via the N4 interface . SMF174 may function as a control node. For example, SMF174 may play roles in session management, IP address assignment for WTRU102a, 102b, and 102c, management and configuration of rules for guiding traffic in UPF176a and UPF176b, and generation of downlink data notifications to AMF172 .

[0141] UPF176a and UPF176b provide access for WTRU102a, 102b, and 102c to a packet data network (PDN) such as the Internet 110 . Facilitate communication between WTRU102a, 102b, and 102c and other devices This may be done. UPF176a and UPF176b may also provide WTRU102a, 102b and 102c with access to other types of packet data networks. For example, the other network 112 may be an Ethernet network or any type of network that exchanges data packets. UPF176a and UPF176b may receive rules that direct traffic from SMF174 via the N4 interface. UPF176a and UPF176b may provide access to the packet data network by connecting to the packet data network using the N6 interface or by connecting to each other and other UPFs using the N9 interface. In addition to providing access to the packet data network, UPF176 may also perform functions such as packet routing and forwarding, policy rule enforcement, quality of service management for user plane traffic, and buffering of downlink packets.

[0142] AMF172 may also be connected to N3IWF199, for example, via the N2 interface. The N3IWF facilitates the connection between WTRU102c and the 5G core network 109 via a radio interface technology that is not defined by 3GPP, for example. AMF may interact with N3IWF199 in the same or a similar way as it interacts with RAN105.

[0143] PCF184 may be connected to SMF174 via the N7 interface and N1 ​​​​It may also be connected to the AMF 172 via the 5 interface and to the Application Function (AF) 188 via the N5 interface and may also be connected to the Application Function (AF) 188 via the N15 and N5 interfaces are not shown in Figure 9D. The PCF 184 may provide policy rules to control plane nodes such as the AMF 172 and the SMF 174 so that each control plane node can enforce these rules. The PCF 18 4 may send policies for the WTRUs 102a, 102b, and 102c to the AMF 172 and as a result, the AMF may distribute the policies to the WTRUs 102a , 102b, and 102c via the N1 interface. Next, the policies may be enforced or applied at the WTR Us 102a, 102b, and 102c.

[0144] The UDR 178 functions as a repository for authentication certificates and subscription information The UDR may be connected to network functions and as a result, the network functions may add to, read from, and modify data in the repository. For example, the UDR 178 may be connected to the PCF 184 via the N36 interface Similarly, the UDR 178 may be connected to the NEF 196 via the N37 interface and may be connected to the UDM 197 via the N35 interface.

[0145] The UDM 197 may function as an interface between the UDR 178 and other network functions The UDM 197 may grant network functions permission to access the UDR 178 For example, the UDM 197 may be connected to the N8 interface Connect to AMF172 via [interface name] and connect to SMF174 via the N10 interface This may be the case. Similarly, UDM197 may be connected to AUSF190 via the N13 interface UDR178 and UDM197 may be closely integrated .

[0146] AUSF190 performs authentication-related operations and connects to UDM178 via the N13 interface and to AMF172 via the N12 interface .

[0147] NEF196 exposes the capabilities and services within the 5G core network 109 to the application function (AF) 188. The exposure may occur over the N33 API interface . NEF may be connected to AF188 via the N33 interface and may also be connected to other network functions to expose the capabilities and services of the 5G core network 109 . The application function 188 may interact with the network functions within the 5G core network 109. The interaction between the application function 188 and the network functions may occur directly via an interface or via NEF196 .

[0148] The application function 188 may be considered part of the 5G core network 109 or may be external to the 5G core network 109 and may be deployed by an enterprise having a business relationship with the mobile network operator . .

[0149] ​​​​Network slicing is the process of integrating one or more With mobile network operators supporting multiple "virtual" core networks This is a mechanism that may be used to The core network is being scaled to support different service types operating across multiple Network Slicing allows operators to determine the various requirements for functionality, performance, and separation, e.g. Build customized networks and optimize solutions for different market scenarios This enables us to provide solutions.

[0150] 3GPP is upgrading the 5G core network to support network slicing Network slicing is a technology that allows network operators to A diverse set of 5G use cases that are often demanding (e.g. Supports large-scale IoT, critical communications, V2X, and advanced mobile broadband Each use case is a good tool that can be used to improve performance, scalability, and Network slicing has its own set of requirements, scalability, and availability. Without the use of network technologies, network architectures cannot efficiently meet the needs of a wide range of use cases. may not be flexible and scalable enough to efficiently support new The deployment of network services must be made more efficient.

[0151] Referring again to FIG. 9D, in a network slicing scenario, the WTRU 102a, When 102b or 102c is connected to the AMF 172 via the N1 interface exists. The AMF may logically be part of one or more slices. The AMF is connected to or communicates with the WTRU 102a, 102b or 102c and one or more UPFs 176a and 176b, the SMF 174, and other network functions to coordinate the connection or communication. Each of the UPFs 176a and 176b, the SMF 174, and other network functions may be part of the same slice or different slices . If they are part of different slices, they may be separated from each other in that they may use different computing resources , security certificates, etc. .

[0152] The core network 109 may facilitate communication with other networks. For example , the core network 109 may include or communicate with an IP gateway such as an IP Multimedia Subsystem (IMS) server that functions as an interface between the 5G core network 109 and the PSTN 108 . For example, the core network 109 may include or communicate with a Short Message Service (SMS) service center that facilitates communication via the Short Message Service . For example, the 5G core network 109 may facilitate the exchange of non-IP data packets between the WTRUs 102a , 102b and 102c and a server or application function 188. In addition, the core network 109 may provide the WTRUs 102a , 102b and 102c with services owned or operated by other service providers . 102b and 102c and a server or application function 188 to facilitate the exchange of non-IP data packets. In addition, the core network 109 may provide the WTRUs 102a , 102b and 102c with services owned or operated by other service providers . access to network 112, which may include other wired or wireless networks that are made may be provided.

[0153] The core network entities described herein and illustrated in FIGS. 9A, 9C, 9D, 9E are identified by the names given to those entities in certain existing 3GPP specifications, but in the future, those entities and functions may be identified by other names, and certain entities or functions may be combined in future specifications published by 3GPP, including 3GPP NR specifications. Therefore, it should be understood that the specific network entities and functions described and illustrated in FIGS. 9A, 9B, 9C, 9D or 9E are provided only as examples, and the subject matter disclosed and claimed herein may be implemented or realized in any similar communication system, whether currently defined or defined in the future.

[0154] FIG. 9E shows an example of a communication system 111 in which a system, method, apparatus for implementing wireless link monitoring and radio resource management measurement procedures for NR-U described herein may be used. The communication system 111 may include wireless transmit / receive units (WTRUs) A, B, C, D, E, F, a base station gNB121, a V2X server 124, and roadside units (RSUs) 123a and 123b. In practice, the concepts presented herein may be applied ​may be applied to the network elements. One or some or all of the WTRUs A, B, C, D, E, and F may be outside the scope of the access network coverage 131 In the case of WTRUs A, B, and C in the V2X group, WTRU A leads the group and WTRUs B and C are group members.

[0155] When WTRUs A, B, C, D, E, and F are within the access network coverage 131, they may communicate with each other via the Uu interface 129 through gNB121 In the example of FIG. 9E, WTRUs B and F are shown within the access network coverage 131. WTRUs A, B, C, D, E, and F may communicate directly with each other via a sidelink interface (e.g., interface 125a, 125b, or 128 such as, for example, PC5 or NR PC5), regardless of whether they are below the access network coverage 131 or outside the access network coverage 131. For example, in the example of FIG. 9E, WTRU D, which is outside the access network coverage 131, communicates with WTRU F, which is within the coverage 131.

[0156] WTRUs A, B, C, D, E, and F may communicate with RSU123a and 1 23b via the vehicle-to-network (V2N) 133 or the sidelink interface 125b. WTRUs A, B, C, D, E, and F may communicate with the V2X server 1 via the vehicle-to-infrastructure (V2I) interface 127. ​​​​It may communicate with 24. WTRU A, B, C, D, E, and F may communicate with another UE via a vehicle-to-person (V2P) interface 128 . .

[0157] FIG. 9F is a block diagram of an example of a device or apparatus WTRU 102, such as that described herein, that may be configured for wireless communication and operation in accordance with the wireless link monitoring and radio resource management measurement procedures for NR-U, as shown in FIGS. 9A, 9B, 9C, 9D, or 9E, or FIGS. 4 through 6 . As shown in FIG. 9F, an exemplary WTRU 102 may comprise a processor 118, a transceiver 120, a transmission / reception element 122, a speaker / microphone 124, a keypad 126 , a display / touchpad / indicator 128, a non-removable memory 130, a removable memory 132, a power source 134, a Global Positioning System (GPS) chipset 136 , and other peripheral devices 138. It is to be understood that the WTRU 102 may comprise any sub-combination of the above-described elements . By way of non-limiting example, among others, base stations 11 such as transceiver base stations (BTSs), Node-Bs, site controllers, access points (APs), home Node-Bs, evolved home Node-Bs (eNodeBs), home evolved Node-Bs (HeNBs), home evolved Node-B gateways, next generation Node-Bs (gNode-Bs), and proxy nodes . . . . . . . . . . Nodes 4a and 114b, which may refer to base stations 114a and 114b. may comprise some or all of the elements depicted in FIG. 9F and may be any of the components described herein. For radio link monitoring and radio resource management measurement procedures for NR-U, The present invention may be an example implementation for implementing the above-described systems and methods.

[0158] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital Digital Signal Processor (DSP), multiple microprocessors one or more microprocessors associated with the DSP cores; a controller; Microcontrollers, Application Specific Integrated Circuits ircuit:ASIC, Field Programmable Gate Array FPGA (Field Programmable Gauge) circuits, any other type of Integrated Circuit (Integrated Circuit C), a state machine, etc. The processor 118 may be a signal coding, a data processing processing, power control, input / output processing, or otherwise enabling the WTRU 102 to operate within a wireless environment. The processor 118 may also implement any other functionality that enables the transmit / receive element 12 to perform the 2, which may be coupled to a transceiver 120. In FIG. 9F, Although a processor 118 and a transceiver 120 are shown as components, 18 and transceiver 120 may be integrated together in an electronic package or chip. Please understand this.

[0159] The UE's transmit / receive element 122 communicates over the air interface 115 / 116 / 117. 9A), or the air interface 115d / Transmitting signals to or receiving signals from other UEs via 116d / 117d For example, the transmit / receive element 122 may be configured to transmit or receive an RF signal. The transmit / receive element 122 may be, for example, an antenna configured to receive An emitter / detector configured to transmit or receive IR, UV, or visible light signals The transmit / receive element 122 may be configured to transmit and receive both RF and optical signals. The transmit / receive element 122 may be configured to transmit any combination of wireless or wired signals. It will be appreciated that the device may be configured to transmit or receive matching information.

[0160] In addition, the transmit / receive element 122, although depicted in FIG. 9F as a single element, may be The RU 102 may include any number of transmit / receive elements 122. More specifically, the WT The RU 102 may employ MIMO technology. To transmit and receive radio signals through interfaces 115 / 116 / 117, It may include two or more transmit / receive elements 122 (eg, multiple antennas).

[0161] The transceiver 120 modulates the signal to be transmitted by the transmit / receive element 122. , and may be configured to demodulate signals received by the transmit / receive element 122. As mentioned above, the WTRU 102 may have multi-mode capabilities. The transceiver 120 may be configured to support multiple RATs, such as NR and IEEE802. 2.11, or communicate via NR and E-UTRA, or different RRHs, T Enable communication with the same RAT via multiple beams to an RP, RSU, or node To this end, it may include multiple transceivers.

[0162] The processor 118 of the WTRU 102 is connected to the speaker / microphone 124, keypad 1 26, or the display / touchpad / indicator 128 (e.g., a liquid crystal display (Liquid Crystal Display: LCD) display device or an organic light-emitting diode (Organic Light-Emitting Diode: OLED) display device) and may receive user input data therefrom. The processor 118 may also output user data to the speaker / microphone 124, keypad 126, or display / touchpad / indicator 128. Additionally, the processor 118 may access information from any suitable type of memory, such as the non-removable memory 130 or removable memory 132, and store data therein. Examples of the non-removable memory 130 include random-access memory (Random-Access Memory: RAM), read-only memory (Read-Only Memory: ROM), hard disk, or any other type of memory storage device. Examples of the removable memory 132 include subscriber identity module (Subscriber Identity Module: SIM) card, memory stick, secure digital From which user input data may be received. The processor 118 may also output user data to the speaker / microphone 124, keypad 126, or display / touchpad / indicator 128. Additionally, the processor 118 may access information from any suitable type of memory, such as the non-removable memory 130 or removable memory 132, and store data therein. - card 126, or the display / touchpad / indicator 128 and may output user data thereto. In addition, the processor 118 may access information from any suitable type of memory, such as the non-removable memory 130 or removable memory 132, and store data therein. The non-removable memory 130 may include random-access memory (Random-Access Memory: RAM), read-only memory (Read-Only Memory: ROM), hard disk, or any other type of memory storage device. The removable memory 132 may include subscriber identity module (Subscriber Identity Module: SIM) card, memory stick, secure digital (Secure Digital: SD) memory card, etc. The processor 118 may be a server hosted on a cloud or edge computing platform, or Access information from any suitable type of memory, such as non-removable memory 130 or removable memory 132, and store data therein. Examples of non-removable memory 130 include random-access memory (Random-Access Memory: RAM), read-only memory (Read-Only Memory: ROM), hard disk, or any other type of memory storage device. Examples of removable memory 132 include subscriber identity module (Subscriber Identity Module: SIM) card, memory stick, secure digital (Secure Digital: SD) memory card, etc. The processor 118 may be a server hosted on a cloud or edge computing platform, or Subscriber Identity Module: SIM) card, memory stick, secure digital (Secure Digital: SD) memory card, etc. The processor 118 may be a server hosted on a cloud or edge computing platform, or Subscriber Identity Module: SIM) card, memory stick, secure digital (Secure Digital: SD) memory card, etc. The processor 118 may be a server hosted on a cloud or edge computing platform, or (Secure Digital: SD) memory card, etc. The processor 118 may be a server hosted on a cloud or edge computing platform, or A server hosted on a cloud or edge computing platform, or It may access information in a memory that is not physically installed on the WTRU102, such as within a home computer (not shown), and store data therein. The processor 118, in some of the examples described in this specification, controls the lighting pattern, image, or color on the display or indicator 128, or is configured to indicate the status of the NR-U radio link monitoring and radio resource management measurement procedures and related components, depending on whether the setup of the NR-U radio link monitoring and radio resource management measurement procedures has succeeded or failed. The control of the lighting pattern, image, or color of the display or indicator 128 reflects the method flow or the status of any of the components shown or discussed in each figure in this specification (e.g., FIGS. 4 to 6, etc.). Messages and procedures for the NR-U radio link monitoring and radio resource management measurement procedures are disclosed in this specification. The user may request, configure, or query for radio link monitoring and radio resource management measurement procedure-related information for NR-U, which may be displayed on the display 128, via an input source (e.g., a speaker / microphone 124, a keypad 126, or a display / touchpad / indicator 128). The messages and procedures may be extended to provide an interface / API. It may access information in a memory that is not physically installed on the WTRU102, such as within a home computer (not shown), and store data therein. In some of the examples described in this specification, for NR-U radio link monitoring and radio resource management measurement procedures, depending on whether the setup has succeeded or failed, the processor 118 controls the lighting pattern, image, or color on the display or indicator 128, or is configured to indicate the status of the NR-U radio link monitoring and radio resource management measurement procedures and related components. The control of the lighting pattern, image, or color of the display or indicator 128 reflects the method flow or the status of any of the components shown or discussed in each figure in this specification (e.g., FIGS. 4 to 6, etc.). Messages and procedures for the NR-U radio link monitoring and radio resource management measurement procedures are disclosed in this specification. The user may request, configure, or query for radio link monitoring and radio resource management measurement procedure-related information for NR-U, which may be displayed on the display 128, via an input source (e.g., a speaker / microphone 124, a keypad 126, or a display / touchpad / indicator 128). The messages and procedures may be extended to provide an interface / API. when the method flow or the status of any of the components shown or discussed in each figure in this specification (e.g., FIGS. 4 to 6, etc.) is reflected Messages for the NR-U radio link monitoring and radio resource management measurement procedures are disclosed in this specification. The user may request, configure, or query for radio link monitoring and radio resource management measurement procedure-related information for NR-U, which may be displayed on the display 128, via an input source (e.g., a speaker / microphone 124, a keypad 126, or a display / touchpad / indicator 128). Messages and procedures may be extended to provide an interface / API for the user to request, configure, or query for radio link monitoring and radio resource management measurement procedure-related information for NR-U, which may be displayed on the display 128, via an input source (e.g., a speaker / microphone 124, a keypad 126, or a display / touchpad / indicator 128). In particular, when the radio link monitoring and radio resource management measurement procedure-related information for NR-U is displayed on the display 128, the messages and procedures may be extended to provide an interface / API for the user to request, configure, or query for such information via an input source (e.g., a speaker / microphone 124, a keypad 126, or a display / touchpad / indicator 128). The processor 118 may obtain power from the power supply 134 and may be configured to distribute or control power to other components within the WTRU102. The power supply 134 may be a WTRU... The processor 118 may obtain power from the power supply 134 and may be configured to distribute or control power to other components within the WTRU102. The power supply 134 may be a WTRU...

[0163] The processor 118 may obtain power from the power supply 134 and may be configured to distribute or control power to other components within the WTRU102. The power supply 134 may be a WTRU... It may be any suitable device for powering the WTRU102. For example, the power supply 134 may include one or more dry batteries, solar cells, fuel cells, etc.

[0164] The processor 118 may also be coupled to a GPS chipset 136 configured to provide location information regarding the current location of the WTRU102 (e.g., longitude and latitude). In addition to, or instead of, the information from the GPS chipset 136, the WTR U102 may receive location information from a base station (e.g., base stations 114a, 114b) through the air interface 115 / 116 / 117, or may determine its location based on the timing of signals received from two or more neighboring base stations. It will be understood that the WTRU10 2 may obtain location information by any suitable location determination method.

[0165] The processor 118 may further be coupled to other peripheral devices 138 that include one or more software or hardware modules that provide additional features, functionality, or wired or wireless connectivity capabilities. For example, the peripheral device 138 may include various sensors such as an accelerometer , a biometric (e.g., fingerprint) sensor, an e-compass, a satellite transceiver , a digital camera (for photos or videos), a Universal Serial Bus (USB) port or other interconnect interface, a vibration device , a television transceiver, a hands-free headset, a Bluetooth® module , a Frequency Modulated (FM) radio unit, a digital music player ​​​​​​including a media player, a video game player module, an Internet browser, etc. It may also include.

[0166] WTRU102 may be included in other devices or apparatuses such as sensors, consumer electronics products, smart watches or smart clothing wearable devices such as, medical or e-health devices, robots, industrial equipment, drones vehicles such as cars, trucks, trains, or airplanes, etc. WTRU102 may be included in other components, modules, or systems of such devices or apparatuses It may be provided with one of the peripheral devices 138. It may be connected to other components, modules, or systems of such devices or apparatuses via one or more interconnect interfaces such as an interconnect interface It may be connected to other components, modules, or systems of such devices or apparatuses via one or more interconnect interfaces such as an interconnect interface It may be connected to other components, modules, or systems of such devices or apparatuses via one or more interconnect interfaces such as an interconnect interface It may also be connected.

[0167] FIG. 9G is a block diagram of an exemplary computing system 90. In this system within, one or more devices of the communication networks exemplified in FIGS. 9A, 9C, FIG. 9D, and FIG. 9E, such as certain nodes or functional entities within RAN103 / 104 / 105, core network 106 / 107 / 109, PS TN108, Internet 110, other network 112, or other network service 113, etc., and one or more devices of the communication networks exemplified in FIGS. 9A, 9C, and, the systems and methods shown in FIGS. 4 to 6 discussed and claimed herein, etc., N radio link monitoring and radio resource management measurement procedures for NR-U may be implemented It may be. The computing system 90 includes a computer or a server and may be mainly controlled by computer-readable instructions, which may be in the form of software It may be in the form of software, and the place where such software is stored or accessed may also be It may be in the form of software, and the place where such software is stored or accessed may also be The means can be any kind. Such computer-readable instructions may be executed within the processor 91 so as to operate the computing system 90. The processor 91 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 91 may perform signal coding, data processing, power control, input / output processing, or any other functionality that enables the computing system 90 to operate within a communication network. The coprocessor 81 is an optional processor that is distinct from the main processor 91 and may perform additional functions or assist the processor 91. The processor 91 or the coprocessor 81 may receive, generate, and process data related to the methods and apparatuses disclosed herein for wireless link monitoring and radio resource management measurement procedures for NR-U, such as monitoring of signals or frames. The processor 91, during operation, fetches, decodes, and executes instructions, and transfers information to and from other resources via the system bus 80, which is the main data transfer path of the computing system. Such a system bus may be a computer bus, a PCI bus, a HyperTransport bus, or any other type of bus known in the art. The computing system 90 may also include a memory 92 for storing data and instructions. The memory 92 may be a random access memory (RAM), a read-only memory (ROM), a flash memory, a hard disk drive, or any other type of memory known in the art. The memory 92 may store the computer-readable instructions for operating the computing system 90, as well as data processed by the processor 91. The computing system 90 may further include an input / output (I / O) interface 93 for communicating with external devices. The I / O interface 93 may be a USB interface, an Ethernet interface, a Wi-Fi interface, or any other type of interface known in the art. The I / O interface 93 may receive data from external devices and transfer it to the processor 91 for processing, or transfer data processed by the processor 91 to external devices. The computing system 90 may also include a communication interface 94 for communicating with other computing systems or devices over a network. The communication interface 94 may be a wired communication interface, such as an Ethernet interface, or a wireless communication interface, such as a Wi-Fi interface or a cellular communication interface. The communication interface 94 may transmit and receive data over the network according to a communication protocol, such as TCP / IP, HTTP, or Bluetooth. The computing system 90 may further include a power supply 95 for providing power to the various components of the computing system. The power supply 95 may be a battery, a power adapter, or any other type of power supply known in the art.

[0168] The processor 91, during operation, fetches, decodes, and executes instructions, and transfers information to and from other resources via the system bus 80, which is the main data transfer path of the computing system. The processor 91 may be coupled to the system bus 80 through a bus interface unit (BIU). The BIU may perform functions such as address decoding, bus arbitration, and data buffering. The system bus 80 may be a computer bus, a PCI bus, a HyperTransport bus, or any other type of bus known in the art. Connect components within the wing system 90 and define a medium for data exchange to do. The system bus 80 typically includes data lines for transmitting data, address lines for transmitting addresses, and control lines for transmitting interrupts and operating the system bus . An example of such a system bus 80 is a PCI (Peripheral Component Interconnect) bus .

[0169] The memory connected to the system bus 80 includes a random access memory (RAM) 82 and a read-only memory (ROM) 93 . Such a memory includes a circuit that enables storage and reading of information . The ROM 93 generally contains stored data that cannot be easily modified . The data stored in the RAM 82 may be read or modified by the processor 91 or other hardware devices. Access to the RAM 82 or ROM 93 may be controlled by a memory controller 92 . The memory controller 92 may provide an address translation function that converts virtual addresses to physical addresses when instructions are executed . The memory controller 92 may also provide a memory protection function that isolates processes within the system and isolates system processes from user processes . Thus, a program launched in the first mode may access only the memory mapped by its own process virtual address space and cannot access the memory within the virtual address space of another process unless memory sharing between processes is set . .

[0170] ​​In addition, computing system 90 may include a peripheral device controller 83 that communicates instructions from processor 91 to peripheral devices such as printer 94, keyboard 84, mouse 95, and disk drive 85.

[0171] A display 86 controlled by a display controller 96 is used to display visual output generated by computing system 90. Such visual output may include text, graphics, video graphics, and video. The visual output may be provided in the form of a graphical user interface (GUI). Display 86 may be a CRT-based video display, an LCD-based flat panel display, a gas plasma-based flat panel display, or may be implemented as a touch panel. Display controller 96 includes the electronic components necessary to generate the video signals sent to display 86.

[0172] Furthermore, computing system 90 is used to connect computing system 90 to an external communication network or device such as RAN103 / 104 / 105, core network 106 / 107 / 109, PSTN108, Internet 110, WTRU102, or other network 112 of FIGS. 9A, 9B, 9C, 25D, or 25E so that computing system 90 can communicate with other nodes or functional entities of those networks, for example, via a wireless or wired network. It may include a communication circuit such as communication adapter 97. The communication circuit may be used alone or in combination with processor 91 to perform the transmission and reception steps of certain devices, nodes, or functional entities described herein.

[0173] Any or all of the devices, systems, methods, and processes described herein may be embodied in the form of computer-executable instructions (e.g., program code) stored on a computer-readable storage medium, and when executed by a processor such as processor 118 or 91, cause the processor to implement or implement the systems, methods, and processes described herein. Specifically, any step, operation, or function described herein may be implemented in the form of such computer-executable instructions and executed by a processor of a device or computing system configured for wireless or wired network communication. The computer-readable storage medium may be implemented using any non-transitory (e.g., tangible or physical) method or technology for storing information, including volatile and non-volatile media, removable and non-removable media, but does not include signals. Examples of computer-readable storage media include RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disk (DVD) or other optical disk storage devices, magnetic cassettes, magnetic tapes, magnetic disk storage devices or other magnetic storage devices, or may be used to store desired information. , and any other tangible or physical medium that may be accessed by a computer system, including, but not limited to, those.

[0174] As shown in each figure, for the subject matter of the present disclosure, wireless link monitoring and radio resource management measurements for NR-U When describing a preferred method, system or apparatus for the subject matter of the procedure, specific terms are used for the purpose of clarity. However, the claimed subject matter is not intended to be limited to such selected specific terms, and it should be understood that each specific element includes all technical equivalents that operate in a similar manner to achieve a similar purpose.

[0175] The various techniques described herein may be implemented in conjunction with hardware, firmware, software, or, where appropriate, combinations thereof. Such hardware, firmware, and software may reside in devices disposed at various nodes of a communication network. To implement the methods described herein, the devices may operate independently or in cooperation with each other. The terms "apparatus", "network device", "node", "device", "network node", etc. used herein may be used interchangeably. In addition, the word "or" is used generally herein in an inclusive sense, unless otherwise specified.

[0176] This specification uses each example to disclose the invention, including the best mode, and to enable a person skilled in the art to make and use any device or system and to practice the invention, including performing any incorporated method. The patentable scope of the invention is defined by the claims. ​​​​​​​Defined by the scope of the claim and other examples that can be recalled by those skilled in the art (e.g., omitting steps, combining steps, or adding steps among each exemplary method disclosed herein). Such other examples are intended to be within the scope of the claims if they have structural elements that do not differ from the literal words of the claims, or if they include equivalent structural elements with only a slight difference from the literal words of the claims. It may be included. When such other examples have structural elements that are not different from the literal words of the claims, or when they include equivalent structural elements with only a very slight difference from the literal words of the claims, they are intended to be within the scope of the claims. It is intended to be within the scope of the claims. It is intended to be within the scope of the claims. It is intended to be within the scope of the claims.

[0177] The methods, systems, and apparatuses described herein can provide means for wireless link monitoring and radio resource management measurement procedures, particularly for NR-U. The method, system, computer-readable storage medium, or apparatus can monitor the downlink quality based on one or more configured wireless link monitoring reference signals (RLM-RS) of the resource, monitor the number of defective wireless link monitoring reference signal (RLM-RS) transmission opportunities (TXOP) (e.g., count), and determine (e.g., detect) a radio link failure (RLF) based on the monitored downlink quality combined with the monitored number of defective RLM-RS TXOP. When an RLF is detected, the UE may initiate an RRC connection re-establishment procedure. The downlink quality may be based on one or more RLM reference signals. The downlink wireless link quality may be measured for a specific reference signal. The UE may perform RLM only for the DL. The UE may evaluate the downlink wireless link quality for the purpose of monitoring the downlink wireless link quality of the cell. The method, system, computer-readable storage medium, or apparatus can monitor the downlink quality based on one or more configured wireless link monitoring reference signals (RLM-RS) of the resource, monitor the number of defective wireless link monitoring reference signal (RLM-RS) transmission opportunities (TXOP) (e.g., count), and determine (e.g., detect) a radio link failure (RLF) based on the monitored downlink quality combined with the monitored number of defective RLM-RS TXOP. When an RLF is detected, the UE may initiate an RRC connection re-establishment procedure. The downlink quality may be based on one or more RLM reference signals. The downlink wireless link quality may be measured for a specific reference signal. The UE may perform RLM only for the DL. The UE may evaluate the downlink wireless link quality for the purpose of monitoring the downlink wireless link quality of the cell. Radio Link Monitoring Reference Signal (RLM-RS) Based on the reference signal of one or more configured wireless link monitoring reference signals (RLM-RS) of the resource, monitor the downlink quality, monitor the number of defective wireless link monitoring reference signal (RLM-RS) transmission opportunities (TXOP) (e.g., count), and determine (e.g., detect) a radio link failure (RLF) based on the monitored downlink quality combined with the monitored number of defective RLM-RS TXOP. When an RLF is detected, the UE may initiate an RRC connection re-establishment procedure. The downlink quality may be based on one or more RLM reference signals. The downlink wireless link quality may be measured for a specific reference signal. The UE may perform RLM only for the DL. The UE may evaluate the downlink wireless link quality for the purpose of monitoring the downlink wireless link quality of the cell. (e.g., count) Based on the monitored downlink quality combined with the monitored number of defective RLM-RS TXOP, determine (e.g., detect) a radio link failure (RLF). When an RLF is detected, the UE may initiate an RRC connection re-establishment procedure. The downlink quality may be based on one or more RLM reference signals. The downlink wireless link quality may be measured for a specific reference signal. The UE may perform RLM only for the DL. The UE may evaluate the downlink wireless link quality for the purpose of monitoring the downlink wireless link quality of the cell. The UE may initiate an RRC connection re-establishment procedure. The downlink quality may be based on one or more RLM reference signals. The downlink wireless link quality may be measured for a specific reference signal. The UE may perform RLM only for the DL. The UE may evaluate the downlink wireless link quality for the purpose of monitoring the downlink wireless link quality of the cell. The downlink quality may be based on one or more RLM reference signals. The downlink wireless link quality may be measured for a specific reference signal. The UE may perform RLM only for the DL. The UE may evaluate the downlink wireless link quality for the purpose of monitoring the downlink wireless link quality of the cell. The downlink wireless link quality may be measured for a specific reference signal. The UE may perform RLM only for the DL. The UE may evaluate the downlink wireless link quality for the purpose of monitoring the downlink wireless link quality of the cell. The UE may evaluate the downlink wireless link quality for the purpose of monitoring the downlink wireless link quality of the cell. It may be compared with threshold values Qout (e.g., out-of-sync) and Qin (in-sync). In one example Qin is a threshold value above which in-sync is declared, and Qout is a threshold value below which out-of-sync is declared. The gNB may use other reference signals (e.g., SRS or DMRS for determining UL quality). The quality measurement may correspond to RSRP or RSRQ measurements as defined according to 3GPP specifications. All combinations (including omission or addition of steps) in this paragraph and the following paragraphs are considered to be means consistent with other parts of the form for carrying out the invention.

[0178] A method, system, computer-readable storage medium, or apparatus is to monitor an in-sync indication or an out-of-sync indication, where the in-sync indication or the out-of-sync indication is based on radio link quality, and to monitor the number of defective radio link monitoring reference signal (RLM-RS) transmission opportunities (TXOPs), and to determine (e.g., detect) a radio link failure (RLF) based on the monitored in-sync indication or out-of-sync indication combined with the monitored number of defective RLM-RS TXOPs. Monitoring the number of defective RLM-RS TXOPs may be based on a discovery reference signal, a channel access indication, or another signal. A method, system, computer-readable storage medium, or apparatus, when there is an available licensed band downlink, based on downlink control information (DCI) obtained on the licensed band downlink, during RLM-RS TXOPs unlicensed... ... ​​It has means for detecting whether an access channel has been acquired. Defect R Monitoring the number of LM-RS TXOPs may be based on the frame of the physical layer where the radio link quality is evaluated. Defect RLM-RS TXOPs may be monitored based on the physical layer frame where the radio link quality is evaluated. Monitoring the number of RLM-RS TXOPs may be based on the timing at which NMissed_TXOP is received during the TEval uate_missed_TXOP period. A method, system, computer-readable storage medium, or device has means for providing an indication to a higher layer that there is a defect in an RLM-RS TXOP when there is a defect in the RLM-RS TXOP or when the RLM-RS is detected to have been transmitted during the RLM-RS TXOP. RRC is an example of a higher layer. Signaling between peer RRC entities within a UE or gNB may be regarded as RRC signaling. A method, system, computer-readable storage medium, or device operates (e.g., starts) a timer TEvaluate_missed_TXOP based on detecting NMissed_TXOP consecutive defective RLM-RS TXOPs, and stops the timer TEvaluate_missed_TXOP based on detecting an RLM-RS during Ndetected_TXOP consecutive RLM-RS TXO Ps, and has means for determining that there is a radio link failure when the timer TEvaluate_missed_TXOP is not stopped and the timer TEvaluate_missed_TXOP expires. TEvaluate_ missed_TXOP, NMissed_TXOP, or Ndetected_TX OP may be signaled by RRC signaling or by another higher layer. (e.g., start) the timer TEvaluate_missed_TXOP based on detecting NMissed_TXOP consecutive defective RLM-RS TXOPs, and stop the timer TEvaluate_missed_TXOP based on detecting an RLM-RS during Ndetected_TXOP consecutive RLM-RS TXO Ps, and has means for determining that there is a radio link failure when the timer TEvaluate_missed_TXOP is not stopped and the timer TEvaluate_missed_TXOP expires. TEvaluate_ missed_TXOP, NMissed_TXOP, or Ndetected_TX OP may be signaled by RRC signaling or by another higher layer. OP may be signaled by RRC signaling or by another higher layer. missed_TXOP, NMissed_TXOP, or Ndetected_TX OP may be signaled by RRC signaling or by another higher layer. One or more of the out-of-sync indications may be generated if at least one of the RLM-RS TX OPs is detected. Timer T 312 may be set to an initial value and then counted down. Expiration of the timer may correspond to the timer reaching a zero value. Detecting a radio link failure may further be based on receiving N310 consecutive out-of-sync indications. A method, system, computer-readable storage medium, or apparatus may detect an RLM-RS TXOP failure while timer T Evaluate_miss ed_TXOP is not running, and based on this, start timer T and, during N Evaluate_missed_TXOP consecutive RLM-RS TXOPs, stop timer T d etected_TXOP based on detecting an RLM-RS, and when timer T is not stopped and timer T Evaluate_missed_TXOP expires, determine that there is a radio link failure, and has means for doing so. Detecting a radio link failure may further be based on receiving the maximum number of consecutive out-of-sync indications regarding the PCell from the lower layer Timer T Evaluate_missed_TXOP is not stopped, and when timer T Eval uate_missed_TXOP expires, determine that there is a radio link failure and. Detecting a radio link failure may further be based on receiving the maximum number of consecutive out-of-sync indications regarding the PCell from the lower layer A method, system, computer-readable storage medium, or apparatus may increment count timer N310 based on receiving at least one of the out-of-sync indications using the upper layer, detect a radio link failure based on reaching the maximum value, and when receiving an N311 consecutive in-sync indication and, when receiving an N311 consecutive in-sync indication increment count timer N310 based on receiving at least one of the out-of-sync indications using the upper layer, detect a radio link failure based on reaching the maximum value, and when receiving an N311 consecutive in-sync indication detect a radio link failure based on reaching the maximum value, and when receiving an N311 consecutive in-sync indication It has means for resetting counter N310. A method, system, computer-readable storage medium, or device provides an indication that there is a problem with the RLM-RS TXOP to the upper layer when there is a problem with the RLM-RS TXOP. A computer-readable storage medium, or device has means for providing an indication that there is a problem with the RLM-RS TXOP to the upper layer when there is a problem with the RLM-RS TXOP. The detected indication of the RLM-RS TXOP may be provided to the upper layer. When T expires, RLF may be detected. T may be started upon receipt of N consecutive problem RLM-RS TXOP indications from the lower layer, and may be stopped upon receipt of an indication of detection of RLM-RS during N consecutive RLM-RS TXOPs. Evaluate_missed_TXOP When T expires, RLF may be detected. T may be started upon receipt of N consecutive problem RLM-RS TXOP indications from the lower layer, and may be stopped upon receipt of an indication of detection of RLM-RS during N consecutive RLM-RS TXOPs. Evaluate_missed_TXOP T is from the lower layer N Mi ssed_TXOP It may be started upon receipt of consecutive problem RLM-RS TXOP indications, and may be stopped upon receipt of an indication of detection of RLM-RS during N consecutive RLM-RS TXOPs from the lower layer. It may be started upon receipt of N consecutive problem RLM-RS TXOP indications from the lower layer, and may be stopped upon receipt of an indication of detection of RLM-RS during N consecutive RLM-RS TXOPs. detected_TXOP Consecutive RLM-RS TX OP may be stopped upon receipt of an indication of detection of RLM-RS during N consecutive RLM-RS TXOPs. Eva luate_missed_TXOP The number of problem RLM-RS TXOPs received within the period is N Even if it is smaller than, monitoring may be performed. Missed_TXOP The maximum value may correspond to the maximum count of the out-of-sync indication. Counter N3 10 may be incremented or reset based on whether an out-of-sync or in-sync indication is received. When the maximum count is reached, RLF may be declared. A method, system, computer-readable storage medium, or device starts timer T based on detecting a problem RLM-RS TXOP while timer T is not operating, and timer T is based on detecting RLM-RS during N consecutive RLM-RS TXOPs. 10 may be incremented or reset based on whether an out-of-sync or in-sync indication is received. When the maximum count is reached, RLF may be declared. A method, system, computer-readable storage medium, or device starts timer T based on detecting a problem RLM-RS TXOP while timer T is not operating, and timer T is based on detecting RLM-RS during N consecutive RLM-RS TXOPs. When the maximum count is reached, RLF may be declared. A method, system, computer-readable storage medium, or device starts timer T based on detecting a problem RLM-RS TXOP while timer T is not operating, and timer T is based on detecting RLM-RS during N consecutive RLM-RS TXOPs. When the maximum count is reached, RLF may be declared. A method, system, computer-readable storage medium, or device starts timer T based on detecting a problem RLM-RS TXOP while timer T is not operating, and timer T is based on detecting RLM-RS during N consecutive RLM-RS TXOPs. E valuate_missed_TXOP While timer T is not operating, based on detecting a problem RLM-RS TXOP, timer T TXOP is detected, and based on detecting RLM-RS during N consecutive RLM-RS TXOPs, timer T Evaluate_missed_TXO P Starts timer T based on detecting a problem RLM-RS TXOP while timer T is not operating, and timer T is based on detecting RLM-RS during N consecutive RLM-RS TXOPs. detected_TXOP During N consecutive RLM-RS TXOPs Based on detecting RLM-RS, timer TEvaluate_missed_ TXOP to stop, and timer T Evaluate_missed_TXOP is operating when it is, N from the lower layer Missed_TXOP Continuous fault RLM-RS TX to receive an OP indication and determine that there is a radio link failure, and means for performing has. All combinations of this paragraph (including omission or addition of steps) are considered to be means that coincide with other parts of the form for carrying out the invention.

Claims

1. A wireless transmit / receive unit (WTRU) for performing a radio link monitoring or radio link failure process, comprising: A processor; a memory coupled to the processor; The memory itself contains executable instructions; The executable instructions, when executed by the processor, cause the processor to: monitoring an unlicensed channel for an in-sync or out-of-sync indication, the in-sync or out-of-sync indication being based on a radio link quality; Monitoring a number of failure Radio Link Monitoring Reference Signal (RLM-RS) Transmission Opportunities (TXOPs) on the unlicensed channel, detecting whether an unlicensed channel has been acquired during the RLM-RS TXOP based on a Channel Access Indication (CAI) signal, the CAI signal indicating to the WTRU that the unlicensed channel has been acquired for a particular carrier based on Downlink Control Information (DCI) acquired in a downlink; determining a Radio Link Failure (RLF) based on the monitored in-sync or out-of-sync indications combined with the monitored number of the failed RLM-RS TXOPs; monitoring a number of the failed RLM-RS TXOPs, The WTRU performs an operation including:

2. 2. The WTRU of claim 1, wherein monitoring the number of failed RLM-RS TXOPs is based on a signal transmitted by a base station, the base station being a gNB.

3. The WTRU of claim 1 , wherein monitoring the number of failed RLM-RS TXOPs is based on a discovery reference signal.

4. The WTRU of claim 1 , wherein monitoring the number of failed RLM-RS TXOPs is based on a physical layer frame in which a radio link quality is evaluated.

5. The WTRU of claim 1, wherein monitoring the number of failed RLM-RS TXOPs is based on detecting NMissed_TXOP failed RLM-RS TXOPs during a TEvaluate_missed_TXOP period.

6. The WTRU of claim 1, wherein the operations further include, if an RLM-RS TXOP is faulty, providing an indication to higher layers that the RLM-RS TXOP has failed.

7. The operation is starting a timer TEvaluate_missed_TXOP based on detecting a failed RLM-RS TXOP while the timer TEvaluate_missed_TXOP is not running; stopping a timer TEvaluate_missed_TXOP based on detecting an RLM-RS during Ndetected_TXOP consecutive RLM-RS TXOPs, where Ndetected_TXOP is a predetermined threshold for detected RLM-RS TXOPs; receiving NMissed_TXOP consecutive failed RLM-RS TXOP indications from a lower layer when a timer TEvaluate_missed_TXOP is running, where NMissed_TXOP is a predefined threshold of failed RLM-RS TXOPs; and determining that there is a radio link failure; The WTRU of claim 1 further comprising:

8. The WTRU of claim 7, wherein the TEvaluate_missed_TXOP, the NMissed_TXOP, or the Ndetected_TXOP is signaled by RRC signaling.

9. The operation is starting a timer TEvaluate_missed_TXOP based on receiving NMissed_TXOP consecutive failed RLM-RS TXOP indications from a lower layer, where NMissed_TXOP is a predetermined threshold of failed RLM-RS TXOPs; stopping a timer TEvaluate_missed_TXOP based on detecting an RLM-RS during Ndetected_TXOP consecutive RLM-RS TXOPs from a lower layer, where Ndetected_TXOP is a predetermined threshold number of detected RLM-RS TXOPs; a timer TEvaluate_missed_TXOP is not stopped and determining that there is a radio link failure when the timer TEvaluate_missed_TXOP expires; The WTRU of claim 1 further comprising:

10. The WTRU of claim 1 , wherein determining the radio link failure is further based on receiving a maximum number of consecutive out-of-sync indications for a PCell from a lower layer.

11. A method of operating a wireless transmit / receive unit (WTRU) to perform a radio link monitoring or radio link failure process, comprising: monitoring an unlicensed channel for an in-sync or out-of-sync indication, the in-sync or out-of-sync indication being based on a radio link quality; monitoring a number of failure Radio Link Monitoring Reference Signal (RLM-RS) transmission opportunities (TXOPs) on the unlicensed channel; detecting whether an unlicensed channel has been acquired during the RLM-RS TXOP based on a Channel Access Indication (CAI) signal, the CAI signal indicating to the WTRU that the unlicensed channel has been acquired for a particular carrier based on Downlink Control Information (DCI) acquired in a downlink; determining a radio link failure (RLF) based on the monitored in-sync or out-of-sync indications combined with the monitored number of the failed RLM-RS TXOPs; monitoring a number of the failed RLM-RS TXOPs, The method includes:

12. starting a timer TEvaluate_missed_TXOP based on detecting a failed RLM-RS TXOP while the timer TEvaluate_missed_TXOP is not running; stopping a timer TEvaluate_missed_TXOP based on detecting an RLM-RS during Ndetected_TXOP consecutive RLM-RS TXOPs, where Ndetected_TXOP is a predetermined threshold for detected RLM-RS TXOPs; a timer TEvaluate_missed_TXOP is not stopped and determining that there is a radio link failure when the timer TEvaluate_missed_TXOP expires; The method of claim 11 further comprising:

13. The method of claim 11, wherein monitoring the number of failed RLM-RS TXOPs is based on a signal transmitted by a base station, the base station being a gNB.

14. The method of claim 11, wherein monitoring the number of failed RLM-RS TXOPs is based on a physical layer frame in which a radio link quality is evaluated.

15. The method of claim 11, further comprising, if an RLM-RS TXOP fails, providing an indication to upper layers that the RLM-RS TXOP has failed.

Images