Radio resource management relaxation for radio resource control connection mode

Abstract

A user equipment (UE) is configured to: receive a measurement configuration from a serving cell, wherein the measurement configuration includes an event configuration associated with radio resource management (RRM) slack; perform a measurement of the serving cell; send a measurement report to the serving cell; and receive from the serving cell an indication to enable RRM slack for radio resource control (RRC) connection mode at the UE.

Description

Technical Field

[0001] This application generally relates to wireless communication systems, and particularly to radio resource management relaxation for radio resource control connection modes. Background Technology

[0002] New Radio (NR) networks can support redcap user equipment (UEs). It has been confirmed that implementing Radio Resource Management (RRM) relaxation may be beneficial for redcap UEs operating in Radio Resource Control (RRC) connection mode. Those skilled in the art will understand that RRM relaxation refers to a 3GPP concept where a UE complies with relaxed RRM requirements under certain conditions. Techniques need to be configured to facilitate the implementation of RRM relaxation for redcap UEs in RRC connection mode. Summary of the Invention

[0003] Some exemplary embodiments relate to a processor of a user equipment (UE) configured to perform operations. These operations include: receiving a measurement configuration from a serving cell, wherein the measurement configuration includes an event configuration associated with radio resource management (RRM) slack; performing a measurement of the serving cell; sending a measurement report to the serving cell; and receiving from the serving cell an indication to enable RRM slack for radio resource control (RRC) connection mode at the UE.

[0004] Other exemplary embodiments relate to a user equipment (UE) having: a transceiver configured to communicate with a serving cell; and a processor communicatively coupled to the transceiver and configured to perform operations. These operations include: receiving a measurement configuration from the serving cell, wherein the measurement configuration includes an event configuration associated with radio resource management (RRM) slack; performing a measurement of the serving cell; sending a measurement report to the serving cell; and receiving from the serving cell an indication to enable RRM slack for a radio resource control (RRC) connection mode at the UE. Attached Figure Description

[0005] Figure 1 Exemplary network arrangements according to various exemplary implementations are shown.

[0006] Figure 2 Exemplary user equipment (UE) according to various exemplary embodiments are shown.

[0007] Figure 3 An exemplary base station according to various exemplary embodiments is shown.

[0008] Figure 4Signaling diagrams for enabling and disabling Radio Resource Management (RRM) slack according to various exemplary embodiments are shown.

[0009] Figure 5 An exemplary abstract syntax representation of event configuration information is shown (ASN.1) according to various exemplary implementations.

[0010] Figure 6 Methods for implementing RRM relaxation according to various exemplary embodiments are shown. Detailed Implementation

[0011] Exemplary embodiments can be further understood with reference to the following description and related figures, wherein similar elements have the same reference numerals. Exemplary embodiments relate to Radio Resource Management (RRM) relaxation. Those skilled in the art will understand that the term "RRM relaxation" generally refers to a 3GPP concept in which user equipment (UE) complies with relaxed RRM requirements under certain conditions. To provide an example, when RRM relaxation is enabled, the UE can be configured to perform measurements and / or monitor reference signals at a lower frequency compared to other RRM measurement configurations.

[0012] In one aspect, exemplary embodiments introduce techniques for implementing RRM relaxation schemes for RRC connected modes. Those skilled in the art will understand that “RRC” refers to the Radio Resource Control Protocol, and that a UE can be configured to be in one of several different types of RRC operating modes (or states), such as RRC idle mode, RRC inactive mode, RRC connected mode, etc. In RRC connected mode, the UE and the network can exchange information (e.g., control information) and / or data. The exchange of information and / or data allows the UE to perform various available functionalities via the network connection. In RRC idle mode, the UE typically does not exchange data with the network, and radio resources are not allocated to the UE within the network. In RRC inactive mode, the UE maintains the RRC connection while minimizing signaling and power consumption. However, when the UE is in RRC idle mode or RRC inactive mode, the UE can still monitor information and / or data transmitted by the network. Throughout this specification, these terms are generally used to describe the modes or states that the UE can be in when connected to any network and the modes or states exhibiting the aforementioned characteristics of RRC idle mode, RRC connected mode, and RRC inactive mode.

[0013] In RRC connection mode, the UE can be configured with a measurement gap. As will be described in more detail below, exemplary embodiments introduce techniques that facilitate RRM relaxation in RRC connection modes with or without measurement gaps.

[0014] Those skilled in the art will understand that the term "measurement gap" generally refers to a time period during which the UE can collect measurement data corresponding to cells other than the currently configured serving cell. For example, during pre-occupancy, the UE may be configured with a measurement gap, during which the UE can tune away from the serving cell and scan for signals broadcast by other cells. The UE can collect measurement data based on signals received during the measurement gap. The measurement data collected by the UE can then be used by the UE and / or the network for a variety of different purposes, including but not limited to RRM.

[0015] During operation, the UE can be configured with a measurement gap mode. For example, consider a scenario where the measurement gap mode is configured with a measurement gap length of (Y) seconds and a repetition period of (X) seconds. First, a first measurement gap is triggered. The UE may tune its transceiver to one or more frequencies to scan for signals broadcast by surrounding cells for (Y) seconds. After the measurement gap expires, the UE may tune back to its serving cell. A second measurement gap may be triggered (X) seconds after the first measurement gap. The UE may again tune its transceiver to one or more frequencies to scan for signals broadcast by surrounding cells for (Y) seconds. The above example is provided merely as a general example of a measurement gap mode and is not intended to limit the exemplary implementation in any way. The exemplary implementation introduces techniques that facilitate RRM relaxation in RRC connection modes with (or without) measurement gaps.

[0016] In RRC connected mode, the UE can be configured with connected discontinuous reception (cDRX) functionality. As will be described in more detail below, exemplary embodiments introduce techniques that facilitate RRM relaxation in RRC connected mode with (or without) cDRX.

[0017] Those skilled in the art will understand that cDRX is a power-saving mechanism that can be implemented by a UE in RRC connection mode. A cDRX cycle may include the UE being scheduled to monitor the on duration of the Physical Downlink Control Channel (PDCCH) during its operation. Outside of the on duration, the UE may have the opportunity to utilize an inactive sleep mode and conserve power. Throughout this specification, references to power-saving modes or inactive sleep modes do not necessarily imply that the UE's processor, transmitter, and receiver are put to sleep, hibernate, or disabled. For example, the processor (e.g., baseband and / or applications) may continue to execute other applications or processes. An inactive sleep mode involves conserving power by interrupting continuous processing functions associated with operations that enable the UE to receive data that can be transmitted to the UE and transmit data to the network.

[0018] The cDRX cycle can have a predetermined duration (N), such as 100 milliseconds (ms), 50 ms, 40 ms, 20 ms, etc. For example, at time 0, there can be an on-duration active mode during which processing can be used. Subsequently, at the end of the on-duration, the UE has the opportunity to utilize an inactive sleep mode. Then at time N, there can be another on-duration. The sleep mode can then be used until time 2N. This process can continue until the cDRX cycle is no longer configured at the UE. The mention of a cDRX cycle configured in milliseconds is merely illustrative; exemplary embodiments may utilize cDRX cycles based on subframes or any other suitable time unit. The exemplary embodiments introduce techniques that facilitate RRM relaxation in RRC connection modes with (or without) cDRX.

[0019] On the other hand, an exemplary embodiment introduces techniques for enabling and disabling RRM relaxation in RRC connected mode. As will be described in more detail below, the network can control when to enable / disable RRM relaxation at the UE. However, the network can decide to enable / disable RRM relaxation based at least in part on measurement data reported by the UE. For example, at a first time, the UE can be configured to perform RRM operation according to a default configuration. The UE can then collect measurement data corresponding to its serving cell and report the measurement data to the network. In response, at a second time, the network can enable RRM relaxation at the UE. The UE can then collect measurement data corresponding to its serving cell and report the measurement data to the network. In response, at a third time, the network can disable RRM relaxation at the UE. Then, according to the default configuration, the UE can return to performing RRM.

[0020] The examples above are not intended to limit the exemplary implementation in any way. Rather, they are provided to demonstrate that when the UE is in RRC connected mode, there are multiple different RRM measurement configurations that the network can enable / disable. In real-world scenarios, there may be multiple different types of RRM relaxation schemes and multiple different types of other RRM measurement schemes. Throughout this specification, the term "RRM measurement scheme" can refer to any RRM measurement configuration that cannot be characterized as an RRM relaxation scheme.

[0021] Exemplary implementations are described with reference to a redcap UE. The term "redcap UE" generally refers to a 3GPP concept of a New Radio (NR) device with lower cost and / or complexity compared to other NR devices. In some cases, a redcap UE can be characterized as a device with lower-end capabilities relative to version 16 Enhanced Mobile Broadband (eMBB) devices and Ultra Reliable Low Latency Communication (URLLC) devices. To provide some concrete examples, a redcap UE can be associated with use cases such as, but not limited to, industrial wireless sensors, video surveillance, and wearable devices.

[0022] Exemplary implementations are described with reference to "events" associated with the UE's mobility state (e.g., stationary, not at the cell edge, etc.). Those skilled in the art will understand that an "event" refers to a predefined type of measurement report triggered in response to the fulfillment of certain conditions. As described above, these measurement reports can provide the network with a basis for enabling or disabling RRM relaxation at the UE. These events can leverage the relatively stationary deployment of redcap UEs to provide additional power savings to redcap UEs via RRM relaxation.

[0023] While exemplary embodiments can provide various beneficial effects to a redcap UE, they are not limited to redcap device types and can provide beneficial effects to any device configured with measurement reporting events similar to those described herein. Exemplary embodiments can be used with any electronic components configured with hardware, software, and / or firmware for exchanging information (e.g., control information) and / or data with the network. Therefore, the UE described herein is intended to represent any suitable electronic device.

[0024] The following provides detailed examples of exemplary techniques for implementing RRM relaxation and specific examples of techniques for enabling / disabling RRM relaxation schemes at the UE. These exemplary techniques can be used in conjunction with currently implemented RRM relaxation techniques and processes, future implementations of RRM relaxation techniques and processes, or independently of other RRM relaxation techniques and processes.

[0025] Figure 1An exemplary network arrangement 100 according to various exemplary embodiments is illustrated. The exemplary network arrangement 100 includes a UE 110. Those skilled in the art will understand that the UE 110 can be any type of electronic component configured to communicate via a network, such as a mobile phone, tablet computer, desktop computer, smartphone, phablet, embedded device, Internet of Things (IoT) device, wearable device (e.g., medical device, augmented reality goggles, virtual reality goggles, smartwatch, etc.), industrial wireless sensor, food monitoring device, etc. It should also be understood that a practical network arrangement can include any number of UEs used by any number of users. Therefore, for illustrative purposes, only an example of a single UE 110 is provided.

[0026] UE 110 can be configured to communicate with one or more networks. In the example of network configuration 100, the network with which UE 110 can wirelessly communicate is the 5G NR radio access network (RAN) 120. However, UE 110 can also communicate with other types of networks (e.g., 5G cloud RAN, next-generation RAN (NG-RAN), LTE RAN, legacy cellular networks, WLAN, etc.), and UE 110 can also communicate with the network via a wired connection. Regarding an exemplary implementation, UE 110 can establish a connection with 5G NR RAN 120. Therefore, UE 110 may have a 5G NR chipset to communicate with 5G NR RAN 120.

[0027] The 5G NR RAN 120 can be part of a cellular network that can be deployed by network operators (e.g., Verizon, AT&T, T-Mobile, etc.). The 5G NR RAN 120 may include, for example, nodes, cells, or base stations (e.g., Node B, eNodeB, HeNB, eNBS, gNB, gNodeB, macrocell base station, microcell base station, small cell base station, femtocell base station, etc.) configured to send and receive communication services from UEs equipped with appropriate cellular chipsets.

[0028] Those skilled in the art will understand that any relevant procedures can be performed for UE 110 to connect to 5G NR-RAN 120. For example, as described above, 5G NR-RAN 120 can be associated with a specific cellular provider, where UE 110 and / or its user have protocol and credential information (e.g., stored on a SIM card). Upon detecting the presence of 5G NR-RAN 120, UE 110 can transmit the corresponding credential information to associate with 5G NR-RAN 120. More specifically, UE 110 can be associated with a specific base station (e.g., Next Generation Node B (gNB) 120A).

[0029] Network deployment 100 also includes a cellular core network 130, an Internet 140, an IP Multimedia Subsystem (IMS) 150, and a network services backbone 160. The cellular core network 130 can be viewed as an interconnected set of components that manage the operation and communication traffic of the cellular network. It may include an evolved packet core (EPC) and / or a fifth-generation core (5GC). The cellular core network 130 also manages the communication traffic flowing between the cellular network and the Internet 140. The IMS 150 can generally be described as an architecture for delivering multimedia services to the UE 110 using IP protocols. The IMS 150 can communicate with the cellular core network 130 and the Internet 140 to provide multimedia services to the UE 110. The network services backbone 160 communicates directly or indirectly with the Internet 140 and the cellular core network 130. The network services backbone 160 can generally be described as a set of components (e.g., servers, network storage deployments, etc.) that implement a set of services that can be used to extend the functionality of the UE 110 to communicate with various networks.

[0030] Figure 2 An exemplary UE 110 according to various exemplary embodiments is shown. Reference will be made to... Figure 1 The network layout 100 is used to describe UE 110. UE 110 may include a processor 205, a memory layout 210, a display device 215, an input / output (I / O) device 220, a transceiver 225, and other components 230. Other components 230 may include, for example, audio input devices, audio output devices, power sources, data acquisition devices, ports for electrically connecting UE 110 to other electronic devices, etc.

[0031] Processor 205 can be configured to execute multiple engines of UE 110. For example, engines may include measurement reporting engine 235 and RRM relaxation engine 240. Measurement reporting engine 235 can perform various operations related to collecting and reporting measurement data to the network. As described above, measurement reporting can at least partially provide the network with the basis for enabling / disabling RRM relaxation at UE 110. RRM relaxation engine 240 can perform various operations related to RRM relaxation, such as, but not limited to, configuring RRM relaxation schemes in RRC connection mode.

[0032] The engines 235 and 240 described above, each as an application (e.g., a program) executed by processor 205, are provided for illustrative purposes only. The functionality associated with engines 235 and 240 may also be represented as separate integrated components of UE 110, or as modular components coupled to UE 110, such as integrated circuits with or without firmware. For example, the integrated circuit may include input circuitry for receiving signals and processing circuitry for processing signals and other information. An engine may also be embodied as a single application or multiple independent applications. Furthermore, in some UEs, the functionality described for processor 205 is split among two or more processors, such as a baseband processor and an application processor. Exemplary implementations can be implemented according to any of these or other configurations of the UE.

[0033] Memory arrangement 210 may be a hardware component configured to store data related to operations performed by UE 110. Display device 215 may be a hardware component configured to display data to a user, while I / O device 220 may be a hardware component enabling user input. Display device 215 and I / O device 220 may be separate components or may be integrated together (such as a touchscreen). Transceiver 225 may be a hardware component configured to establish connections with 5G NR-RAN 120, LTE-RAN (not shown), legacy RAN (not shown), WLAN (not shown), etc. Therefore, transceiver 225 may operate on multiple different frequencies or channels (e.g., a set of consecutive frequencies).

[0034] Figure 3 An exemplary base station 300 according to various exemplary embodiments is shown. Base station 300 may represent a gNB 120A or any other access node that UE 110 can use to establish connections and manage network operations.

[0035] Base station 300 may include processor 305, memory arrangement 310, input / output (I / O) devices 315, transceiver 320, and other components 325. These other components 325 may include, for example, audio input devices, audio output devices, batteries, data acquisition devices, ports for electrically connecting base station 300 to other electronic devices, etc.

[0036] The processor 305 may be configured to execute multiple engines of the base station 300. For example, these engines may include an RRM relaxation engine 330. The RRM relaxation engine 330 may perform various operations related to configuring, enabling, and disabling RRM relaxation schemes at the UE 110.

[0037] The engine 330 described above, as an application (e.g., a program) executed by the processor 305, is merely exemplary. Functions associated with the engine 330 may also be represented as separate components of the base station 300, or as modular components coupled to the base station 300, such as integrated circuits with or without firmware. For example, the integrated circuit may include input circuitry for receiving signals and processing circuitry for processing signals and other information. Furthermore, in some base stations, the functions described for the processor 305 are distributed among multiple processors (e.g., a baseband processor, an application processor, etc.). Exemplary implementations can be implemented according to any of these or other configurations of the base station.

[0038] Memory 310 may be a hardware component configured to store data related to operations performed by base station 300. I / O device 315 may be a hardware component or port enabling a user to interact with base station 300. Transceiver 320 may be a hardware component configured to exchange data with UE 110 and any other UE in system 100. Transceiver 320 may operate on a variety of different frequencies or channels (e.g., a set of consecutive frequencies). Therefore, transceiver 320 may include one or more components (e.g., radio components) to enable data exchange with various networks and UEs.

[0039] Exemplary implementations are described with reference to different types of "events". As described above, those skilled in the art will understand that an "event" refers to a set of one or more conditions configured to trigger UE 110 to transmit a measurement report to the network. In some networks, the measurement report type and event type may be referred to by the same name (e.g., X1, X2, X3, etc.). Events that trigger measurement reports can be used for a variety of different mechanisms. However, in the example described herein, the network may use the measurement report to determine whether to enable / disable RRM slack at UE 110.

[0040] An exemplary event may correspond to a stationary criterion. Throughout this specification, this event may be referred to as "Event X1". A stationary criterion may indicate that the UE is deployed in a fixed location, is stationary, or exhibits low mobility. For example, a stationary criterion may include a time window during which changes in the Reference Signal Received Power (RSRP) of the target serving cell will remain within a specific threshold. Event X1 may be analogous to the low mobility criterion defined in 3GPP Technical Specification (TS) 38.304. In other words, the lack of RSRP changes may indicate that UE 110 is deployed in a relatively stationary manner. When UE 110 is relatively stationary, connection parameters are unlikely to change. Therefore, when UE 110 is deployed in a relatively stationary manner, the power savings from RRM relaxation may outweigh the usefulness of performing certain RRM operations.

[0041] Another exemplary event may correspond to the "not at the cell edge" criterion. Throughout this specification, this event may be referred to as "Event X2". The "not at the cell edge" criterion may indicate that UE 110 is not deployed at the edge of the coverage area of ​​the target serving cell. For example, the "not at the cell edge" criterion may include one or more serving cell parameters (e.g., RSRP, Reference Signal Received Quality (RSRQ), etc.) exceeding a corresponding threshold. The Event X2 criterion may be similar to the "not at the cell edge" criterion defined in 3GPP TS 38.304. When UE 110 is not deployed at the edge of the coverage area of ​​the target serving cell, the measurement data corresponding to the serving cell may be more reliable, and neighboring cells are unlikely to provide better connection quality. Therefore, when UE 110 is not deployed at the edge of the coverage area of ​​the target cell, the power-saving benefits of RRM relaxation may outweigh the usefulness of performing certain RRM operations.

[0042] Additionally, another exemplary event may correspond to both the stationary criterion and the not-at-the-cell-edge criterion mentioned above. Throughout this specification, this event may be referred to as "Event X3". References will follow below. Figure 4 Signaling diagram 400 and Figure 5 Abstract Syntax Notation 1 (ASN.1) provides additional details about events X1, X2, and X3.

[0043] Exemplary implementations are not limited to the exemplary events described herein (e.g., events X1, X2, and X3), and can be applied to any measurement report triggering event including any type of standard that may be beneficial in indicating whether or not to enable or disable RRM relaxation. Furthermore, those skilled in the art will understand that in 3GPP networks, event types are typically identified using letters and numbers (e.g., A1, A2, A3, B1, C1, etc.). In actual network deployments, the event types used to enable / disable RRM relaxation in RRC connectivity mode may not actually be referred to using "X1," "X2," or "X3." Different networks may use different combinations of numbers and letters or any other appropriate IDs to characterize measurement report event types for RRM relaxation in RRC connectivity mode.

[0044] Figure 4 Signaling diagram 400 for enabling and disabling RRM relaxation according to various exemplary embodiments is shown. Signaling diagram 400 includes UE 110 and gNB 120A. However, signaling diagram 400 is not intended to limit the exemplary embodiments in any way. Rather, signaling diagram 400 provides exemplary signaling exchanges that can be used to enable and disable RRM relaxation at UE 110. Specific examples of implementing RRM relaxation schemes will be provided after describing signaling diagram 400.

[0045] In step 405, gNB 120A transmits event configuration information to UE 110. The event configuration information may include one or more conditions that will trigger UE 110 to transmit network measurement reports. In this example, there are three different events (e.g., event X1, event X2, event X3) for enabling / disabling RRM relaxation. However, references to these events are provided for illustrative purposes only. Exemplary implementations can be applied to any number of events for enabling / disabling RRM relaxation.

[0046] As will be described in more detail below, measurement reports triggered by these events can indicate to the network that RRM relaxation configuration can be enabled at UE110. Additionally, once RRM relaxation is enabled, UE110 can continue monitoring events X1-X3, and / or the network can configure different events for the purpose of triggering measurement reports that can indicate to the network that RRM relaxation configuration at UE110 can be released or disabled.

[0047] In some implementations, event configuration information for enabling / disabling RRM slack can be provided to the UE 110 in one or more RRC messages. Figure 5 Example ASN.1 500 for event configuration information is shown. In this example, event X1 includes a “StationaryStatus-threshold” parameter representing a serving cell quality change threshold (e.g., RSRP change) and a time parameter “X1Period”. Event X1 occurs when the serving cell quality change is within the StationaryStatus-threshold for the duration of the X1Period time parameter.

[0048] In ASN.1 500, event X2 includes a “NotAtCellEdge-threshold” parameter representing a serving cell quality threshold (e.g., RSRP, RSRQ, etc.) and a time parameter “X2Period”. Event X2 occurs when the serving cell quality parameter exceeds NotAtCellEdge-threshold for the duration of the X2Period time parameter.

[0049] In ASN.1 500, event X3 includes the StationaryStatus-threshold parameter, the NotAtCellEdge-threshold parameter, and the time parameter "X3Period". Event X3 occurs when the serving cell quality change is within the StationaryStatus-threshold for the duration of the X3Period time parameter, and the serving cell quality parameter exceeds the NotAtCellEdge-threshold for the duration of the X3Period time parameter.

[0050] Returning to signaling diagram 400, in 410, UE 110 is in RRC connection mode. In some implementations, the event configuration information in 405 can be provided to UE 110 during RRC connection establishment. However, exemplary implementations are not limited to this example, and the event configuration information can be provided to UE 110 at any appropriate time.

[0051] In 415, UE 110 is configured to monitor events that enable RRM relaxation. For example, UE 110 may collect measurement data, such as, but not limited to, RSRP and RSRQ, based on reference signals transmitted by the serving cell (e.g., gNB 120A).

[0052] In 420, UE 110 determines that an event criterion is met. For example, UE 110 may identify the duration for which the serving cell RSRP is within the StationaryStatus-threshold for an event parameter of X1Period (e.g., event X1). To provide another example, UE 110 may identify the duration for which the serving cell RSRP or RSRQ exceeds the NotAtCellEdge-threshold for a time parameter of X2Period (e.g., event X2). In another example, UE 110 may identify the duration for which the serving cell RSRP is within the StationaryStatus-threshold for a time parameter of X3Period, and the duration for which the serving cell RSRP or RSRQ exceeds the NotAtCellEdge-threshold for a time parameter of X2Period (e.g., event X3).

[0053] In 425, UE 110 transmits a measurement report to gNB 120A. As described above, the transmission of the measurement report can be triggered by one of the events that enable RRM slack (e.g., event X1, event X2, event X3, etc.).

[0054] The measurement report may include information such as, but not limited to, event IDs (e.g., X1, X2, X3), measurement data (e.g., RSRP, RSRQ), stationary status, non-cell-edge status, and indications that RRM relaxation can be enabled. To provide some examples of event X1, the measurement report may include an event ID (e.g., X1) with or without measurement data (e.g., RSRP, RSRQ). Therefore, the network can determine whether RRM relaxation will be enabled at UE 110 based on the association between the event ID and the RRM relaxation scheme. In another example, the measurement report may include an indication of the stationary mobility state of UE 110 with or without measurement data. Therefore, the network can determine whether RRM relaxation will be enabled at UE 110 based on the association between the stationary mobility state and the RRM relaxation scheme. In yet another example, the measurement report may include an indication of a specific type of RRM relaxation scheme (e.g., an RRM relaxation scheme specific to event X1).

[0055] To provide some examples of event X2, the measurement report may include an event ID (e.g., X2), with or without measurement data (e.g., RSRP, RSRQ). Therefore, the network can determine whether to enable RRM relaxation at UE 110 based on the association between the event ID and the RRM relaxation scheme. In another example, the measurement report may include an indication that UE 110 is not in a cell-edge state, with or without measurement data. Therefore, the network can determine whether to enable RRM relaxation at UE 110 based on the association between not being in a cell-edge state and the RRM relaxation scheme. In yet another example, the measurement report may include an indication of a specific type of RRM relaxation scheme (e.g., an RRM relaxation scheme specific to event X1).

[0056] To provide some examples of event X3, the measurement report may include an event ID (e.g., X3) with or without measurement data (e.g., RSRP, RSRQ). Therefore, the network can determine whether to enable RRM relaxation at UE 110 based on the association between the event ID and the RRM relaxation scheme. In another example, the measurement report may include an indication of the UE 110's stationary mobility state and non-cell-edge state, with or without measurement data. Therefore, the network can determine whether to enable RRM relaxation at UE 110 based on the association between the combined stationary mobility state and non-cell-edge state and the RRM relaxation scheme. In yet another example, the measurement report may include an indication of a specific type of RRM relaxation scheme (e.g., an RRM relaxation scheme specific to event X3).

[0057] In step 430, the network transmits an instruction to enable RRM relaxation at UE 110. In some embodiments, the network may instruct the activation of one of several different types of RRM relaxation schemes. Therefore, the network can explicitly identify which RRM relaxation scheme to utilize. In other embodiments, the network may utilize a single bit flag to enable RRM relaxation. UE 110 can then determine, based on the bit flag and any other appropriate conditions (e.g., event type, measurement data, cDRX parameters, measurement gap parameters, etc.), which type of RRM relaxation scheme will be utilized. In other embodiments, if UE 110 is configured with cDRX or measurement gap mode, the network transmits reconfiguration information for cDRX cycling and / or measurement gap mode to relax RRM measurement operations at UE 110.

[0058] In 435, RRM relaxation is enabled. Following the description of signaling diagram 400, a specific example of an RRM relaxation scheme is provided below.

[0059] In configuration 440, UE 110 monitors events configured to disable (or release) RRM relaxation. Because RRM relaxation is enabled, UE 110 can perform measurements on the serving cell less frequently. However, UE 110 can still collect serving cell measurement data to monitor release events. For example, UE 110 can collect measurement data based on reference signals transmitted by the serving cell (e.g., gNB 120A), such as, but not limited to, RSRP and RSRQ. UE 110 can compare this measurement data with the same criteria used to enable RRM relaxation (e.g., StationaryStatus-threshold, NotAtCellEdge-threshold, X1period, X2period, X2period, etc.). In other embodiments, different criteria may be specifically configured to release RRM relaxation configurations. Throughout this specification, in order to distinguish between triggering events and release events, “Event Y1” can represent the release criterion used for the RRM relaxation of event X1, “Event Y2” can represent the release criterion used for the RRM relaxation of event X2, and “Event Y3” can represent the release criterion used for the RRM relaxation of event X3.

[0060] In 445, UE 110 determines that the RRM relaxation release criteria are met. For example, UE 110 may identify that the serving cell RSRP is not within the StationaryStatus-threshold (e.g., event Y1). To provide another example, UE 110 may identify that the serving cell RSRP or RSRQ does not exceed the NotAtCellEdge-threshold (e.g., event Y2). In another example, UE 110 may identify that the serving cell RSRP is not within the StationaryStatus-threshold or the RSRQ does not exceed the NotAtCellEdge-threshold (e.g., event Y3).

[0061] In 450, UE 110 transmits a measurement report to gNB 120A. As described above, the transmission of the measurement report can be triggered by one of the events used to disable RRM slack (e.g., event Y1, event Y2, event Y3, etc.).

[0062] The measurement report may include information such as, but not limited to, event ID, measurement data (e.g., RSRP, RSRQ), departure from a stationary state, departure from a non-cell-edge state, and an indication that RRM relaxation can be released. To provide some examples of event Y1, the measurement report may include an event ID (e.g., Y1) with or without measurement data (e.g., RSRP, RSRQ). Therefore, the network can determine that RRM relaxation will be disabled at UE 110 based on the association between the event ID and the RRM relaxation scheme. In another example, the measurement report may include an indication of UE 110's departure from a stationary mobility state, with or without measurement data. Therefore, the network can determine that RRM relaxation will be disabled at UE 110 based on the association between the stationary mobility state and the RRM relaxation scheme. In yet another example, the measurement report may include an indication to release a specific type of RRM relaxation scheme (e.g., an RRM relaxation scheme specific to event X1).

[0063] To provide some examples of event Y2, the measurement report may include an event ID (e.g., Y2) with or without measurement data (e.g., RSRP, RSRQ). Therefore, the network can determine to disable RRM relaxation at UE 110 based on the association between the event ID and the RRM relaxation scheme. In another example, the measurement report may include an indication of UE 110's "out-of-cell-edge" state, with or without measurement data. Therefore, the network can determine to disable RRM relaxation at UE 110 based on the association between the "out-of-cell-edge" state and the RRM relaxation scheme. In yet another example, the measurement report may include an indication to release a specific type of RRM relaxation scheme (e.g., an RRM relaxation scheme specific to event X2).

[0064] To provide some examples of event Y3, the measurement report may include an event ID (e.g., Y3) with or without measurement data (e.g., RSRP, RSRQ). Therefore, the network can determine to disable RRM relaxation at UE 110 based on the association between the event ID and the RRM relaxation scheme. In another example, the measurement report may include an indication of UE 110's departure from stationary mobility state and / or departure from not at cell edge state, with or without measurement data. Therefore, the network can determine to disable RRM relaxation at UE 110 based on the association between the combined departure from stationary mobility state or departure from not at cell edge state and the RRM relaxation scheme. In yet another example, the measurement report may include an indication to release a specific type of RRM relaxation scheme (e.g., an RRM relaxation scheme specific to event X3).

[0065] In step 455, the network transmits an instruction to disable RRM relaxation at UE 110. In some implementations, the network may explicitly identify the RRM relaxation scheme to be released. In another implementation, the network may utilize a single bit flag to disable RRM relaxation. UE 110 can then determine the RRM relaxation scheme to be released based on the bit flag and any other appropriate conditions (e.g., event type, measurement data, cDRX parameters, measurement gap parameters, etc.). In other implementations, if UE 110 is configured with cDRX or measurement gap mode, the network transmits reconfiguration information for cDRX cycling and / or measurement gap mode to restore RRM measurement operation at UE 110. In step 460, RRM relaxation is disabled.

[0066] Exemplary embodiments are described with reference to two different RRM relaxation schemes (e.g., RRM relaxation scheme 1 and RRM relaxation scheme 2). However, the exemplary embodiments are not limited to two RRM relaxation schemes, and the network can implement any suitable number of RRM relaxation schemes (e.g., one or more). Each of the RRM relaxation techniques described below in the context of RRM relaxation scheme 1 and RRM relaxation scheme 2 can be implemented in combination with any current RRM relaxation technique for RRC connectivity mode, future implementations of RRM relaxation techniques for RRC connectivity mode, or independently of other RRM relaxation techniques.

[0067] Figure 6 A method 600 for implementing RRM relaxation according to various exemplary embodiments is shown. The method 600 is described from the perspective of UE 110.

[0068] Initially, we assume a scenario where UE 110 is pre-occupied on the serving cell in RRC connection mode. In step 605, UE 110 receives RRM relaxation scheme configuration information. As will be described in more detail below, the RRM relaxation scheme configuration information may include, for example, but not limited to, information for the detection time of the primary synchronization signal (PSS) and secondary synchronization signal (SSS), the measurement time of the synchronization signal block (SSB), and the scaling factor for the cDRX cyclic periodicity.

[0069] In some implementations, RRM relaxation scheme configuration information can be provided to UE 110 via the serving cell. For example, in the context of signaling diagram 400, the RRM relaxation scheme configuration information may be provided to UE 110 in one or more RRC messages (such as the event configuration information in 405), during the RRC connection establishment process, or together with the indication in 430 to enable RRM relaxation at UE 110. To provide another example, the RRM relaxation scheme configuration information may be hardcoded in accordance with 3GPP standards. However, the above examples are provided for illustrative purposes only. RRM relaxation configuration scheme information may be provided to UE 110 in any suitable manner.

[0070] In 610, RRM relaxation is enabled at UE 110. For example, UE 110 may receive an instruction to enable one of several different types of RRM relaxation schemes (e.g., RRM relaxation scheme 1, RRM relaxation scheme 2, etc.).

[0071] In step 615, UE 110 determines whether cDRX is configured. If cDRX is not configured, method 600 continues to step 620. In step 620, UE 110 determines whether a measurement gap is configured. If a measurement gap is not configured, method 600 continues to step 625. In step 625, UE 110 applies one or more scaling factors to the RRM configuration. For example, in RRM scheme 1, when neither cDRX nor a measurement gap is configured, PSS / SSS detection and time indexing can be extended by a scaling factor (M). In this example, M = 3; however, the exemplary implementation is not limited to scaling factor M = 3 and can be applied to cases where the scaling factor M is any suitable value.

[0072] Those skilled in the art will understand that PSS / SSS detection time refers to the time period during which UE 110 identifies the target cell and synchronizes with it by using PSS / SSS sequence detection and correlation. Additionally, those skilled in the art will understand that time index detection time refers to the time period during which UE 110 reads the SSB index of the target cell by identifying the PBCH demodulation reference signal (DMRS) sequence and / or decoding the PBCH payload.

[0073] The scaling factor M can be applied to the detection time period and / or the lower boundary of the detection time for PSS / SSS detection. For example, the PSS / SSS detection time within frequency range 1 (FR1) can be determined as follows: max(600ms*M, ceil(5*k)). p )*SMTCperiod*M). Here, SMTC period represents the periodicity of the synchronization signal (SS) / physical broadcast channel (PBCH) block, k p This represents the resource sharing factor when a measurement opportunity without a measurement gap conflicts with a measurement gap, and the carrier-specific scaling factor (CSSF) is equal to 1. p It can be hardcoded in 3GPP standards or provided to UE 110 in any other appropriate manner.

[0074] The PSS / SSS detection time within frequency range 2 (FR2) can be determined as follows: max(600ms*M, ceil(M) pss.sss_sync_w / o_gaps *k p *Klayer1_measurement)*SMTCperiod*M). Here, SMTC period represents the periodicity of the synchronization signal (SS) / physical broadcast channel (PBCH) block, k p M represents the resource sharing coefficient when a measurement opportunity without a measurement gap conflicts with a measurement gap. pss.sss_sync_w / o_gapsThis indicates the PSS / SSS detection time without measurement gaps. `Klayer1_measurement` represents the measurement resource coordination factor between layer 1 (L1) and layer 3 (L3) measurements, and the carrier-specific scaling factor (CSSF) is equal to 1. Similar to k... p M pss.sss_sync_w / o-gaps Klayer1_measurement can be hardcoded according to 3GPP standards or provided to UE 110 in any other appropriate manner.

[0075] The time index detection time within the FR1 frequency range can be determined as follows: max(120ms*M, ceil(3*k) p )*SMTCperiod*M). Here, SMTC period represents the periodicity of the synchronization signal (SS) / physical broadcast channel (PBCH) block, k p This represents the resource sharing factor when a measurement opportunity without a measurement gap conflicts with a measurement gap, and the carrier-specific scaling factor (CSSF) is equal to 1.

[0076] Additionally, for RRM relaxation scheme 1, when neither cDRX nor measurement interval is configured, the measurement interval can be extended by a scaling factor M. Those skilled in the art will understand that the measurement interval refers to the time interval between two consecutive physical layer measurement sampling points for SSBs with the same index of the target cell. The scaling factor can be applied to the measurement time period and / or the lower boundary of the measurement time. For example, the SSB measurement time within the FR1 frequency can be determined by: max(200ms*M, ceil(5*k)). p )*SMTCperiod*M). Here, SMTC period represents the periodicity of the synchronization signal (SS) / physical broadcast channel (PBCH) block, k p This represents the resource sharing factor when a measurement opportunity without a measurement gap conflicts with a measurement gap, and the carrier-specific scaling factor (CSSF) is equal to 1.

[0077] The measurement time for SSB within the FR2 frequency range can be determined as follows: max(400ms*M, ceil(M) meas_period_w / o_gaps *k p *Klayer1_measurement)*SMTCperiod*M). Here, SMTC period represents the periodicity of the synchronization signal (SS) / physical broadcast channel (PBCH) block, k p M represents the resource sharing coefficient when a measurement opportunity without a measurement gap conflicts with a measurement gap. meas_period_w / o_apsKlayer1_measurement represents the cell measurement time period without measurement gaps. Klayer1_measurement represents the measurement resource coordination factor between L1 and L3 measurements, and the carrier-specific scaling factor (CSSF) is equal to 1.

[0078] In RRM relaxation scheme 2, when neither cDRX nor measurement gap is configured, a scaling factor (M_2) greater than the scaling factor (M) can be used. Therefore, in the equations provided above, the scaling factor M can be replaced by the scaling factor M_2. In other implementations, RRM relaxation scheme 2 can utilize a fixed detection and measurement interval (S).

[0079] Returning to 615, if cDRX is configured, method 600 continues to 630. In 630, UE 110 determines whether a measurement gap is configured. If a measurement gap is not configured, method 600 continues to 635. Therefore, in 635, cDRX is configured and a measurement gap is not configured.

[0080] In 635, UE 110 applies one or more scaling factors to the RRM configuration. In some implementations, for RRM relaxation scheme 1, UE 110 may apply a scaling factor M. As described above with reference to 625, the PSS / SSS detection and time index detection times can be extended by the scaling factor M. Therefore, the scaling factor M can be applied to the detection time period and / or the lower boundary of the detection time. Additionally, the measurement interval can be extended by the scaling factor M. Therefore, the scaling factor M can be applied to the measurement time period and / or the lower boundary of the measurement time.

[0081] In other implementations, for RRM relaxation scheme 1, UE 110 can extend the cDRX cycle periodicity by a scaling factor (D). In this example, D = 3. However, the exemplary implementation is not limited to a scaling factor D = 3 and any suitable value can be used.

[0082] To provide an example, the PSS / SSS detection time within the FR1 frequency when the cDRX cycle duration is less than or equal to 320 milliseconds (ms) can be determined as follows: max(600ms*D, ceil(M2*5*k) p )*max(SMTCperiod, cDRX cycle*D). Here, SMTC period represents the periodicity of the synchronization signal (SS) / physical broadcast channel (PBCH) block, k p M2 represents the resource sharing coefficient when a measurement opportunity without a measurement gap conflicts with a measurement gap. M2 represents the DRX relaxation coefficient when the DRX cycle is less than 320ms, and the carrier-specific scaling factor (CSSF) is equal to 1. M2 can be hardcoded in 3GPP standard or provided to UE 110 in any other suitable manner.

[0083] When the cDRX cycle duration is greater than 320 milliseconds (ms), the PSS / SSS detection time within the FR1 frequency can be determined as follows: ceil(5*k p )*cDRX cycle*D. Here, k p This represents the resource sharing factor when a measurement opportunity without a measurement gap conflicts with the measurement gap, and the carrier-specific scaling factor (CSSF) is equal to 1.

[0084] When the cDRX cycle duration is less than or equal to 320 milliseconds (ms), the PSS / SSS detection time within the FR2 frequency can be determined as follows: max(600ms, ceil(1.5*M) pss.sss_syncw / o_gaps *k p *Klayer1_measurement)*max(SMTCperiod, cDRX cycle*D). Here, SMTC period represents the periodicity of the synchronization signal (SS) / physical broadcast channel (PBCH) block, k p M represents the resource sharing coefficient when a measurement opportunity without a measurement gap conflicts with a measurement gap. pss.sss_sync_w / o_gaps This indicates the PSS / SSS detection time without measurement gaps. Klayer1_measurement represents the measurement resource coordination factor between L1 and L3 measurements, and the carrier-specific scaling factor (CSSF) is equal to 1.

[0085] When the cDRX cycle duration is greater than 320 milliseconds (ms), the PSS / SSS detection time within the FR2 frequency can be determined as follows: ceil(M pss.sss_sync_w / o_gaps *k p *Klayer1_measurement)*max(SMTCperiod, cDRXcycle*D). Here, SMTC period represents the periodicity of the synchronization signal (SS) / physical broadcast channel (PBCH) block, k p M represents the resource sharing coefficient when a measurement opportunity without a measurement gap conflicts with a measurement gap. pss.sss_sync_w / o_gaps This indicates the PSS / SSS detection time without measurement gaps. Klayer1_measurement represents the resource coordination factor between L1 and L3 measurements, and the carrier-specific scaling factor (CSSF) is equal to 1.

[0086] When the cDRX loop duration is less than or equal to 320 milliseconds (ms), the FR1 frequency-interval time index detection time can be determined as follows: max(120ms*D, ceil(M2*3*k) p)*max(SMTCperiod, cDRX cycle*D). Here, SMTC period represents the periodicity of the synchronization signal (SS) / physical broadcast channel (PBCH) block, k p M1 represents the resource sharing coefficient when the measurement timing without a measurement gap conflicts with the measurement gap, and M2 represents the DRX relaxation coefficient when the DRX cycle is less than 320ms, and the carrier-specific scaling factor (CSSF) is equal to 1.

[0087] When the cDRX loop duration is greater than milliseconds (ms), the FR1 frequency-interval time index detection time can be determined as follows: ceil(3*k p )*cDRX cycle*D). Here, k p This represents the resource sharing factor when a measurement opportunity without a measurement gap conflicts with the measurement gap, and the carrier-specific scaling factor (CSSF) is equal to 1.

[0088] The measurement time of SSB based on FR1 frequency when the cDRX cycle duration is less than or equal to 320 milliseconds (ms) can be determined by the following: max(200ms*D, ceil(1.5*5*k) p )*max(SMTCperiod, cDRX cycle*D). Here, SMTC period represents the periodicity of the synchronization signal (SS) / physical broadcast channel (PBCH) block, k p This represents the resource sharing factor when a measurement opportunity without a measurement gap conflicts with a measurement gap, and the carrier-specific scaling factor (CSSF) is equal to 1.

[0089] When the cDRX cycle duration is greater than 320 milliseconds (ms), the measurement time of SSB based on FR1 frequency can be determined by the following: ceil(5*k p )*cDRX cycle*D). Here, k p This represents the resource sharing factor when a measurement opportunity without a measurement gap conflicts with the measurement gap, and the carrier-specific scaling factor (CSSF) is equal to 1.

[0090] The measurement time of SSB based on FR2 frequency when the cDRX cycle duration is less than or equal to 320 milliseconds (ms) can be determined as follows: Here, SMTC period represents the periodicity of the synchronization signal (SS) / physical broadcast channel (PBCH) block, k p M represents the resource sharing coefficient when a measurement opportunity without a measurement gap conflicts with a measurement gap. meas_period_w / o_gapsKlayer1_measurement represents the cell measurement time period without measurement gaps. Klayer1_measurement represents the resource coordination factor between L1 and L3 measurements, and the carrier-specific scaling factor (CSSF) is equal to 1.

[0091] When the cDRX cycle duration is greater than 320 milliseconds (ms), the measurement time of SSB based on the FR2 frequency can be determined as follows: Here, k p M represents the resource sharing coefficient when a measurement opportunity without a measurement gap conflicts with a measurement gap. meas_period_w / o_gaps The cell measurement time period without measurement gaps is represented by Klayer1-measurement, which represents the resource coordination factor between L1 and L3 measurements, and the carrier-specific scaling factor (CSSF) is equal to 1.

[0092] In RRM relaxation scheme 2, when cDRX is configured and no measurement gap is configured, a scaling factor (M_2) greater than the scaling factor (M) can be used. Therefore, in the equation provided above, the scaling factor M can be replaced by the scaling factor M_2. In other embodiments, when cDRX is configured and no measurement gap is configured, a scaling factor (D_2) greater than the scaling factor (D) can be used. Therefore, in the equation provided above, the scaling factor D_2 can be replaced by the scaling factor D. In other embodiments, when cDRX is configured and no measurement gap is configured, RRM relaxation scheme 2 can utilize a fixed detection and measurement interval (S).

[0093] Returning to 615 in signaling diagram 600, if cDRX is not configured, the method continues to 620. In 620, UE 110 determines whether a measurement gap is configured. If a measurement gap is configured, method 600 continues to 640. In 640, UE 110 applies one or more scaling factors to the RRM configuration. In some implementations, for RRM relaxation scheme 1, UE 110 may apply a scaling factor M. As described above with reference to 625 and 635, the PSS / SSS detection and time index detection times can be extended by the scaling factor M. Therefore, the scaling factor M can be applied to the detection time period and / or the lower boundary of the detection time. Additionally, the measurement interval can be extended by the scaling factor M. Therefore, the scaling factor M can be applied to the measurement time period and / or the lower boundary of the measurement time. This scaling factor can be applied to both measurement gaps for intra-frequency measurements and measurement gaps for inter-frequency measurements.

[0094] In other embodiments, for RRM relaxation scheme 1, the measurement gap repetitive periodicity (MGRP) can be extended by a scaling factor (G). This scaling factor can be applied to all detection and measurement time periods, as long as MGRP and / or its applicable lower boundary for the detection or measurement time is used. Furthermore, this scaling factor applies to both measurement gaps for intra-frequency measurements and measurement gaps for inter-frequency measurements. In this example, G = 3. However, the exemplary embodiments are not limited to a scaling factor G = 3 and any suitable value can be used.

[0095] For example, the inter-frequency PSS / SSS detection time of FR1 can be determined as follows: max(600ms*G, 8*max(MGRP*G, SMTCperiod)*CSSF). Here, SMTC period represents the periodicity of the synchronization signal (SS) / physical broadcast channel (PBCH) block, and CSSF represents the carrier-specific scaling factor.

[0096] The PSS / SSS detection time between FR2 frequencies can be determined as follows: max(600ms*G, M) pss.sss.sync.inter *max(MGRP*G, SMTCPeriod)*CSSF. Here, SMTC period represents the periodicity of the synchronization signal (SS) / physical broadcast channel (PBCH) block, k p M represents the resource sharing coefficient when a measurement opportunity without a measurement gap conflicts with a measurement gap. pss.sss.sync.inter It represents the PSS / SSS detection time of the target cell between frequencies, and CSSF represents the carrier-specific scaling factor (CSSF).

[0097] In RRM relaxation scheme 2, when cDRX is not configured and the measurement gap is configured, a scaling factor (M_2) greater than the scaling factor (M) can be used. Therefore, in the equation provided above, the scaling factor M can be replaced by the scaling factor M_2. In other embodiments, when cDRX is not configured and the measurement gap is configured, a scaling factor (G_2) greater than the scaling factor (G) can be used. Therefore, in the equation provided above, the scaling factor G_2 can be replaced by the scaling factor G. In other embodiments, when cDRX is not configured and the measurement gap is configured, RRM relaxation scheme 2 can utilize a fixed detection and measurement interval (S).

[0098] Returning to 615 of signaling diagram 600. If UE 110 is configured with cDRX, method 600 continues to 630. In 630, UE 110 determines whether a measurement gap is configured. If a measurement gap is configured, method 400 continues to 645. In 645, UE 110 applies one or more scaling factors to the RRM configuration. In some embodiments, for RRM relaxation scheme 1, UE 110 may apply a scaling factor M. As described above with reference to 625, 635, and 640, the PSS / SSS detection and time index detection times can be extended by the scaling factor M. Therefore, the scaling factor M can be applied to the detection time period and / or the lower boundary of the detection time. Additionally, the measurement interval can be extended by the scaling factor M. Therefore, the scaling factor M can be applied to the measurement time period and / or the lower boundary of the measurement time. This scaling factor can be applied to both the measurement gap for intra-frequency measurements and the measurement gap for inter-frequency measurements. In other embodiments, a scaling factor D can be used, a scaling factor G can be used, or a combination of scaling factors D and G can be used.

[0099] In RRM relaxation scheme 2, when cDRX is configured and the measurement gap is configured, a scaling factor (M_2) greater than the scaling factor (M) can be used. Therefore, in the equation provided above, the scaling factor M can be replaced by the scaling factor M_2. In other embodiments, when cDRX is configured and the measurement gap is configured, a scaling factor (G_2) greater than the scaling factor (G) can be used. Therefore, in the equation provided above, the scaling factor G_2 can be replaced by the scaling factor G. In other embodiments, when cDRX is configured and the measurement gap is configured, a scaling factor (D_2) greater than the scaling factor (D) can be used. Therefore, in the equation provided above, the scaling factor D_2 can be replaced by the scaling factor D. In other embodiments, when cDRX is not configured and the measurement gap is configured, RRM relaxation scheme 2 can utilize a fixed detection and measurement interval (S).

[0100] In some implementations, when the RRM relaxation scheme is enabled, the UE 110 can ignore the RRM relaxation scheme for the candidate beam detection (CBD) procedure and / or beam fault recovery (BFR) procedure.

[0101] Those skilled in the art will understand that the exemplary embodiments described above can be implemented with any suitable software or hardware configuration or combination thereof. Exemplary hardware platforms for implementing the exemplary embodiments may include, for example, Intel x86-based platforms with compatible operating systems, Windows OS, Mac platforms and MAC OS, and mobile devices with operating systems such as iOS, Android, etc. Exemplary embodiments of the methods described above may be embodied as programs comprising lines of code stored on a non-transitory computer-readable storage medium, which, at compile time, can be executed on a processor or microprocessor.

[0102] Although this patent application describes various combinations of various embodiments, each with different features, those skilled in the art will understand that any feature of an embodiment can be combined with features of other embodiments or features that are not functionally or logically inconsistent with the operation or function of the device of the disclosed embodiment of the invention in any manner not explicitly denied.

[0103] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0104] It will be apparent to those skilled in the art that various modifications can be made to this disclosure without departing from its spirit or scope. Therefore, this disclosure is intended to cover all modifications and variations thereof, provided that such modifications and variations are within the scope of the appended claims and their equivalents.

Claims

1. A processor for a reduced-capacity user equipment (UE) redcap, the processor being configured to perform operations including: Receive measurement configuration from the serving cell, wherein the measurement configuration includes event configuration associated with radio resource management (RRM) relaxation for radio resource control (RRC) connection mode; Perform measurements on the serving cell; Based on the measurements, determine whether the event configuration associated with RRM relaxation for RRC connection mode has been met; When the event configuration associated with RRM relaxation for RRC connection mode has been met, a measurement report is sent to the serving cell, the measurement report indicating to the serving cell at least that RRM relaxation can be enabled at the redcap UE; as well as Receive an instruction from the serving cell to enable RRM relaxation for RRC connection mode at the redcap UE. The measurement report also includes an event ID associated with RRM slack for RRC connection mode.

2. The processor of claim 1, wherein the measurement report further includes one or more of the redcap UE’s stationary mobility state and the redcap UE’s non-cell edge state.

3. The processor of claim 1, wherein the measurement report further includes the type of RRM relaxation scheme to be implemented at the redcap UE.

4. The processor according to claim 1, wherein the operation further comprises: After enabling RRM relaxation for RRC connection mode, a second measurement report is sent to the serving cell, wherein the second measurement report includes an event ID associated with disabling RRM relaxation for RRC connection mode.

5. The processor according to claim 1, wherein the operation further comprises: After enabling RRM relaxation for RRC connection mode, a second measurement report is sent to the serving cell, wherein the second measurement report includes one or more of the redcap UE’s out-of-station mobility state and the redcap UE’s out-of-cell-edge state.

6. The processor according to claim 1, wherein the operation further comprises: After enabling RRM relaxation for RRC connection mode, a second measurement report is sent to the serving cell, wherein the second measurement report includes the type of RRM relaxation scheme to be disabled at the redcap UE.

7. The processor of claim 1, wherein the RRM relaxation for the RRC connection mode includes applying a scaling factor to one or more of the following: primary synchronization signal (PSS) / secondary synchronization signal SSS detection time configuration, synchronization signal block SSB measurement time configuration, or time index detection configuration.

8. The processor of claim 7, wherein during RRM relaxation for RRC connection mode, discontinuous reception DRX is not configured and the redcap UE does not use measurement gaps.

9. The processor of claim 7, wherein during RRM relaxation for RRC connection mode, discontinuous DRX reception is configured at the UE and measurement gaps are not used at the redcap UE.

10. The processor of claim 7, wherein during RRM relaxation for RRC connection mode, discontinuous reception DRX is not configured at the redcap UE and a measurement gap is used at the redcap UE.

11. The processor of claim 7, wherein during RRM relaxation for RRC connection mode, discontinuous DRX reception is configured at the redcap UE and a measurement gap is configured at the redcap UE.

12. The processor of claim 1, wherein the RRM relaxation for the RRC connection mode includes applying a scaling factor to the discontinuous reception DRX cyclic periodicity.

13. The processor of claim 1, wherein RRM relaxation for RRC connection mode includes applying a scaling factor to the measurement gap repetition period MGRP.

14. The processor of claim 1, wherein RRM relaxation for RRC connection mode includes implementing a fixed detection time or measurement time.

15. A capability-reduced user equipment (UE) with redcap, the redcap UE comprising: A transceiver configured to communicate with the serving cell; as well as A processor, communicatively coupled to the transceiver and configured to perform operations including: Receive measurement configuration from the serving cell, wherein the measurement configuration includes an event configuration associated with radio resource management (RRM) relaxation for radio resource control (RRC) connection mode; Perform measurements on the serving cell; Based on the measurements, determine whether the event configuration associated with RRM relaxation for RRC connection mode has been met; When the event configuration associated with RRM relaxation for RRC connection mode has been met, a measurement report is sent to the serving cell, the measurement report indicating to the serving cell at least that RRM relaxation can be enabled at the redcap UE; as well as Receive an instruction from the serving cell to enable RRM relaxation for RRC connection mode at the redcap UE. The measurement report also includes an event ID associated with RRM slack for RRC connection mode.

16. The redcap UE of claim 15, wherein the measurement report further includes one or more of the redcap UE’s stationary mobility state and the redcap UE’s non-cell edge state.

17. The redcap UE of claim 15, wherein the measurement report further includes the type of RRM relaxation scheme to be implemented at the redcap UE.

18. The redcap UE of claim 15, further comprising: After enabling RRM relaxation for RRC connection mode, a second measurement report is sent to the serving cell, wherein the second measurement report includes an event ID associated with disabling RRM relaxation for RRC connection mode.

19. The redcap UE of claim 15, further comprising: After enabling RRM relaxation for RRC connection mode, a second measurement report is sent to the serving cell, wherein the second measurement report includes one or more of the redcap UE’s out-of-station mobility state and the redcap UE’s out-of-cell-edge state.

20. The redcap UE of claim 15, further comprising: After enabling RRM relaxation for RRC connection mode, a second measurement report is sent to the serving cell, wherein the second measurement report includes the type of RRM relaxation scheme to be disabled at the redcap UE.

21. The redcap UE of claim 15, wherein the RRM relaxation for the RRC connection mode includes applying a scaling factor to one or more of the following: primary synchronization signal PSS / secondary synchronization signal SSS detection time configuration, synchronization signal block SSB measurement time configuration, or time index detection configuration.

22. The redcap UE of claim 21, wherein during RRM relaxation for RRC connection mode, discontinuous reception DRX is not configured and the UE does not use measurement gaps.

23. The redcap UE of claim 21, wherein during RRM relaxation for RRC connection mode, discontinuous reception DRX is configured at the redcap UE and no measurement gap is used at the redcap UE.

24. The redcap UE of claim 21, wherein during RRM relaxation for RRC connection mode, discontinuous reception DRX is not configured at the UE and a measurement gap is used at the UE.

25. The redcap UE of claim 21, wherein during RRM relaxation for RRC connection mode, discontinuous reception DRX is configured at the redcap UE and a measurement gap is configured at the redcap UE.

26. The redcap UE of claim 15, wherein RRM relaxation for RRC connection mode includes applying a scaling factor to discontinuous reception DRX cyclic periodicity.

27. The redcap UE of claim 15, wherein RRM relaxation for RRC connection mode includes applying a scaling factor to the measurement gap repetition period MGRP.

28. The UE of claim 15, wherein RRM relaxation for RRC connection mode includes implementing a fixed detection time or measurement time.

Images