SINR measurement technology for power saving

Abstract

An apparatus and system for power saving in a user equipment (UE) is described. The UE uses a signal-to-interference-plus-noise (SINR) of a radio link monitoring (RLM) signal to determine whether to enter or exit an easing state in which the frequency of measurements of the RLM signal is reduced, as well as feedback to a base station. The RLM easing state depends on the average SINR of the RLM signal over a predefined time window. Alternatively, the RLM easing state depends on a SINR threshold that includes a SINR fluctuation range derived from a cumulative distribution function (CDF) curve of the SINR using a SINR threshold for RLM synchronization or using a predefined maximum SINR fluctuation.

Description

Technical Field

[0001] Priority Claim This application claims the benefit of priority to U.S. Provisional Patent Application No. 63 / 166,815, filed Mar. 26, 2021, and U.S. Provisional Patent Application No. 63 / 166,821, filed Mar. 26, 2021, each of which is hereby incorporated by reference in its entirety.

[0002] Embodiments relate to new radio (NR) wireless communication. Some embodiments relate to Radio Link Monitoring (RLM) in an NR wireless communication network. In particular, some embodiments relate to UE power saving based on RLM.

Background Art

[0003] The use and complexity of NR wireless systems, including fifth-generation (5G) networks and especially beginning to include sixth-generation (6G) networks, are increasing due to both an increasing variety of device UEs using network resources and the amount of data and bandwidth used by various applications such as video streaming operating on these UEs. With the significant increase in the number and diversity of communication devices, the corresponding network environment, including routers, switches, bridges, gateways, firewalls, and load balancers, is becoming increasingly complex. As expected, there are many problems with the emergence of new technologies.

Brief Description of the Drawings

[0004] In the drawings, the figures are not necessarily drawn to scale, and like numerals may represent like components in different figures. Like numerals with different letter suffixes may represent different instances of like components. The figures generally illustrate, by way of example and not limitation, the various embodiments discussed in this document.

[0005] [Figure 1A]Several network architectures are shown.

[0006] [Figure 1B] This document describes several non-roaming 5G system architectures.

[0007] [Figure 1C] This document describes several non-roaming 5G system architectures.

[0008] [Figure 2] Block diagrams of communication devices according to several embodiments are shown.

[0009] [Figure 3] The simulated signal-to-interference-plus-noise (SINR)-to-time plots are shown in several aspects.

[0010] [Figure 4] The following plots show the cumulative distribution function (CDF) versus SINR variation in several different ways.

[0011] [Figure 5] The following plots of SINR versus time with relaxation are shown in several forms. [Modes for carrying out the invention]

[0012] The following description and drawings fully illustrate specific embodiments that will enable those skilled in the art to carry them out. Other embodiments may incorporate structural, logical, electrical, process, and other modifications. Parts and features of some embodiments may be included in or replaced by parts and features of other embodiments. The embodiments described in the claims encompass all available equivalents of these claims.

[0013] Figure 1A shows several embodiments of the network architecture. Network 140A includes NG network functionality that can be extended to 3GPP® LTE / 4G and 6G functionality. Therefore, although it is called 5G, it should be understood as being extendable to the structure, system and functionality of 6G. Network functionality can be implemented as individual network elements on dedicated hardware, as software instances running on dedicated hardware, and / or as virtualized functionality instantiated on an appropriate platform, such as dedicated hardware or cloud infrastructure.

[0014] Network 140A is shown to include user equipment (UE) 101 and UE102. UE101 and 102 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices capable of connecting to one or more cellular networks), but may include any mobile or non-mobile computing devices such as portable (laptop) or desktop computers, wireless handsets, drones, or any other computing devices including wired and / or wireless communication interfaces. UE101 and 102 may be collectively referred to as UE101 in this specification, and UE101 can be used to perform one or more of the technologies disclosed herein.

[0015] Any of the radio links described herein (e.g., as used in network 140A or other illustrated networks) may operate in accordance with any exemplary radio communication techniques and / or standards. Any spectrum management scheme may include, for example, dedicated licensed spectra, unlicensed spectra, and (licensed) shared spectra (e.g., Licensed Shared Access (LSA) for 2.3–2.4 GHz, 3.4–3.6 GHz, 3.6–3.8 GHz, and other frequencies, and Spectrum Access System (SAS) for 3.55–3.7 GHz and other frequencies). Different single-carrier orthogonal frequency domain multiplexing (OFDM) modes (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier (FBMC), OFDM, etc.), particularly 3GPP NR, may be used by assigning OFDM carrier data bit vectors to corresponding symbolic resources.

[0016] In some embodiments, either UE101 or 102 may include an Internet of Things (IoT) UE or a Cellular IoT (CIoT) UE, which may include a network access layer designed for low-power IoT applications that utilize short-lived UE connections. In some embodiments, either UE101 or 102 may include a narrowband (NB) IoT UE (e.g., an enhanced NB-IoT (eNB-IoT) UE and a further enhanced (FeNB-IoT) UE). IoT UEs may utilize technologies such as public land mobile networks (PLMN), proximity-based services (ProSe), or device-to-device (D2D) communication, sensor networks, or machine-to-machine (M2M) or machine-type communication (MTC) to exchange data with MTC servers or devices over IoT networks. M2M or MTC data exchange may be machine-initiated data exchange. The IoT network includes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections. The IoT UE may run background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network. In some embodiments, either UE101 or 102 may include an extended MTC (eMTC) UE or a further extended MTC (FeMTC) UE.

[0017] UE101 and 102 may be configured to communicate with, for example, a radio access network (RAN) 110. RAN 110 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) terrestrial radio access network (E-UTRAN), a next-generation RAN (NG RAN), or another type of RAN.

[0018] UEs 101 and 102 each utilize connections 103 and 104, respectively, each of which includes a physical communication interface or layer (to be described in more detail below). In this example, connections 103 and 104 are illustrated as air interfaces for enabling communicable couplings and can be compatible with cellular communication protocols such as the Global System for Mobile Communications (GSM) protocol, Code Division Multiple Access (CDMA) network protocol, Push-to-Talk (PTT) protocol, Push-to-Talk over Cellular (POC) protocol, Universal Mobile Telecommunications System (UMTS) protocol, 3GPP Long-Term Evolution (LTE) protocol, 5G protocol, 6G protocol, etc.

[0019] In one aspect, UEs 101 and 102 may further directly exchange communication data via ProSe interface 105. ProSe interface 105 may alternatively be referred to as a sidelink (SL) interface that includes one or more logical channels, including but not limited to, the Physical Sidelink Control Channel (PSCCH), Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Broadcast Channel (PSBCH), and Physical Sidelink Feedback Channel (PSFCH).

[0020] UE 102 is shown to be configured to access access point (AP) 106 via connection 107. Connection 107 can include, for example, a local wireless connection such as a connection compatible with any IEEE 802.11 protocol, and accordingly, AP 106 can include a Wireless Fidelity (WiFi (registered trademark)) router. In this example, AP 106 is shown to be connected to the Internet without being connected to the core network of the wireless system (to be described in more detail below).

[0021] RAN 110 may include one or more access nodes that enable connections 103 and 104. These access nodes (ANs) can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), next-generation (5th or 6th generation) NodeBs (gNBs), RAN nodes, etc., and can include terrestrial stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographical area (e.g., a cell). In some aspects, communication nodes 111 and 112 can be transmission / reception points (TRPs). When communication nodes 111 and 112 are NodeBs (e.g., eNBs or gNBs), one or more TRPs can function within the communication cell of the NodeB. RAN 110 can include one or more RAN nodes for providing a macrocell, e.g., macro RAN node 111, and one or more RAN nodes for providing a femtocell or picocell (e.g., a cell with a smaller coverage area, smaller user capacity, or larger bandwidth compared to a macrocell), e.g., low-power (LP) RAN node 112.

[0022] Either of RAN nodes 111 and 112 can terminate the air interface protocol and can be the first point of contact for UEs 101 and 102. In some aspects, either of RAN nodes 111 and 112 can perform various logical functions for RAN 110, including, but not limited to, radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management, such as radio network controller (RNC) functions. In one example, either of nodes 111 and / or 112 can be a gNB, an eNB, or another type of RAN node.

[0023] It is shown that RAN 110 is communicably coupled to the core network (CN) 120 via the S1 interface 113. In this embodiment, CN 120 may be an evolved packet core (EPC) network, a next-generation packet core (NPC) network, or another type of CN (as illustrated, for example, with reference to Figure 1B-1C). In this embodiment, the S1 interface 113 is divided into two parts: the S1-U interface 114, which transmits traffic data between RAN nodes 111 and 112 and the serving gateway (S-GW) 122, and the S1 mobility management entity (MME) interface 115, which is a signaling interface between RAN nodes 111 and 112 and the MME 121.

[0024] In this embodiment, CN120 includes MME121, S-GW122, Packet Data Network (PDN) Gateway (P-GW)123, and Home Subscriber Server (HSS)124. The MME121 is functionally similar to the control plane of a conventional Serving General Packet Radio Service (GPRS) Support Node (SGSN). The MME121 can manage mobility aspects of access, such as gateway selection and tracking area list management. The HSS124 may include a database for network users, containing subscriber-related information to support the processing of communication sessions of network entities. Depending on the number of mobile subscribers, equipment capacity, network organization, etc., CN120 may include one or more HSS124s. For example, the HSS124 can provide support for routing / roaming, authentication, authorization, naming / address resolution, location dependency, etc.

[0025] S-GW122 can terminate the S1 interface 113 to RAN110 and route data packets between RAN110 and CN120. Furthermore, S-GW122 can serve as a local mobility anchor point for RAN node handovers and can also provide an anchor for 3GPP inter-node mobility. Other responsibilities of S-GW122 include lawful interception, charging, and certain policy enforcement.

[0026] The P-GW123 may terminate the SGi interface to the PDN. The P-GW123 may route data packets to and from external networks, such as the network containing the CN120 and the application server 184 (alternatively referred to as the Application Function (AF)), via the Internet Protocol (IP) interface 125. The P-GW123 can also communicate data to other external networks 131A, which may include the Internet, IP Multimedia Subsystem (IPS) networks, and other networks. Generally, the application server 184 may be an element providing applications that use IP bearer resources in the core network (e.g., UMTS Packet Service (PS) domain, LTE PS data service, etc.). In this embodiment, the P-GW123 is shown to be communicably coupled to the application server 184 via the IP interface 125. The application server 184 may also be configured to support one or more communication services for UE101 and 102 via the CN120 (e.g., Voice over Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.).

[0027] P-GW123 may further be a node for policy enforcement and billing data collection. The Policy and Billing Rule Function (PCRF)126 is the policy and billing control element of CN120. In non-roaming scenarios, in some embodiments, there may be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with the UE's Internet Protocol Connected Access Network (IP-CAN) session. In roaming scenarios with local breakout of traffic, there may be two PCRFs associated with the UE's IP-CAN session: a Home PCRF (H-PCRF) in the HPLMN and a Visit PCRF (V-PCRF) in the Visited Public Land Mobile Network (VPLMN). PCRF126 may be communicably coupled to the application server 184 via P-GW123.

[0028] In some aspects, communication network 140A may be an IoT network or a 5G or 6G network, including a new 5G radio network using communications in licensed (5G NR) and unlicensed (5G NR-U) spectrums. One of the current enablers of IoT is narrowband IoT (NB-IoT). Operation in the unlicensed spectrum may include dual-connected (DC) operation and standalone LTE systems in the unlicensed spectrum, where LTE-based technology operates only in the unlicensed spectrum without using an "anchor" in the licensed spectrum called MultiFire. Further extended operation of LTE systems in both licensed and unlicensed spectrum is expected in future releases and 5G systems. Such extended operation may include technologies for sidelink resource allocation and UE processing operations for NR sidelink V2X communications.

[0029] The NG system architecture (or 6G system architecture) may include a RAN 110 and a 5G core network (5GC) 120. The NG-RAN 110 may include multiple nodes such as gNBs and NG-eNBs. The CN 120 (e.g., 5G core network / 5GC) may include access and mobility functions (AMF) and / or user plane functions (UPF). The AMF and UPF can be communicatively coupled to the gNB and NG-eNB via the NG interface. More specifically, in some embodiments, the gNB and NG-eNB may be connected to the AMF by the NG-C interface and to the UPF by the NG-U interface. The gNB and NG-eNB may be coupled to each other via the Xn interface.

[0030] In some embodiments, the NG system architecture can use reference points between various nodes. In some embodiments, each of the gNB and NG-eNB can be implemented as a base station, mobile edge server, small cell, home eNB, etc. In some embodiments, the gNB can be a master node (MN), and the NG-eNB can be a secondary node (SN) in a 5G architecture.

[0031] Figure 1B shows a non-roaming 5G system architecture in several embodiments. In particular, Figure 1B shows a 5G system architecture 140B in reference point representation, which can be extended to a 6G system architecture. More specifically, UE 102 can communicate with RAN 110 as well as one or more other 5GC network entities. The 5G system architecture 140B includes multiple network functions (NFs), such as AMF 132, Session Management Function (SMF) 136, Policy Control Function (PCF) 148, Application Function (AF) 150, UPF 134, Network Slice Selection Function (NSSF) 142, Authentication Server Function (AUSF) 144, and Unified Data Management (UDM) / Home Subscriber Server (HSS) 146.

[0032] UPF134 can provide connectivity to the data network (DN) 152, which may include, for example, operator services, internet access, or third-party services. AMF132 can be used to manage access control and mobility and may include network slice selection functionality. AMF132 may provide UE-based authentication, authorization, mobility management, etc., and may be independent of access technology. SMF136 can be configured to set up and manage various sessions according to network policies. Thus, SMF136 may be responsible for session management and assigning IP addresses to UEs. SMF136 may also select and control UPF134 for data transfer. SMF136 can be associated with a single session of UE101 or multiple sessions of UE101. That is, UE101 may have multiple 5G sessions. A different SMF may be assigned to each session. The use of different SMFs may allow each session to be managed individually. As a result, the functionality of each session may be independent of each other.

[0033] The UPF134 can be deployed in one or more configurations according to the desired service type and can be connected to a data network. The PCF148 can be configured to provide a policy framework using network slicing, mobility management, and roaming (similar to PCRF in 4G communication systems). The UDM can be configured to store subscriber profiles and data (similar to HSS in 4G communication systems).

[0034] AF150 may provide packet flow information to PCF148, which is responsible for policy control, in order to support the desired QoS. PCF148 may set mobility and session management policies for UE101. For this purpose, PCF148 may use packet flow information to determine appropriate policies for the proper operation of AMF132 and SMF136. AUSF144 may store data for UE authentication.

[0035] In some embodiments, the 5G system architecture 140B includes not only the IP Multimedia Subsystem (IMS) 168B but also several IP Multimedia Core Network Subsystem Entities such as Call Session Control Functions (CSCFs). More specifically, the IMS 168B includes CSCFs that can operate as a Proxy CSCF (P-CSCF) 162BE, a Serving CSCF (S-CSCF) 164B, an Emergency CSCF (E-CSCF) (not shown in Figure 1B), or a Query CSCF (I-CSCF) 166B. The P-CSCF 162B can be configured to be the first contact point for UE 102 within the IM Subsystem (IMS) 168B. The S-CSCF 164B can be configured to handle session state within the network, and the E-CSCF can be configured to handle specific aspects of emergency sessions, such as routing emergency requests to the appropriate emergency center or PSAP. The I-CSCF166B can be configured to function as a contact point within the operator's network for all IMS connections destined for the network operator's subscribers or roaming subscribers currently located within the network operator's service area. In some embodiments, the I-CSCF166B can connect to another IP multimedia network 170E, for example, an IMS operated by another network operator.

[0036] In some embodiments, the UDM / HSS146 can be coupled to an application server 160E which may include a telephony application server (TAS) or another application server (AS). The AS160B can be coupled to the IMS168B via the S-CSCF164B or I-CSCF166B.

[0037] Reference point representations indicate that interactions can exist between corresponding NF services. For example, Figure 1B shows the following reference points: N1 (between UE102 and AMF132), N2 (between RAN110 and AMF132), N3 (between RAN110 and UPF134), N4 (between SMF136 and UPF134), N5 (between PCF148 and AF150, not shown), N6 (between UPF134 and DN152), N7 (between SMF136 and PCF148, not shown), N8 (between UDM146 and AMF132, not shown), N9 (between two UPF134s, not shown), N10 (between UDM146 and SMF136) N11 (between AMF132 and SMF136, not shown), N12 (between AUSF144 and AMF132, not shown), N13 (between AUSF144 and UDM146, not shown), N14 (between two AMF132s, not shown), N15 (between PCF148 and AMF132 in non-roaming scenarios, between PCF148, the visited network and AMF132 in roaming scenarios, not shown), N16 (between two SMFs, not shown), and N22 (between AMF132 and NSSF142, not shown). Other reference point representations not shown in Figure 1B can also be used.

[0038] Figure 1C shows a 5G system architecture 140C and a service-based representation. In addition to the network entities shown in Figure 1B, the system architecture 140C may also include a network exposure function (NEF) 154 and a network repository function (NRF) 156. In some embodiments, the 5G system architecture can be service-based, and the interactions between network functions can be represented as corresponding point-to-point reference points Ni or service-based interfaces.

[0039] In some embodiments, as shown in Figure 1C, a service-based representation can be used to represent a network function in the control plane that allows other authorized network functions to access that service. In this regard, the 5G system architecture 140C may include the following service-based interfaces: NamF158H (a service-based interface represented by AMF132), NsmF158I (a service-based interface represented by SMF136), NneF158B (a service-based interface represented by NEF154), NpcF158D (a service-based interface represented by PCF148), NudM158E (a service-based interface represented by UDM146), NaF158F (a service-based interface represented by AF150), NnrF158C (a service-based interface represented by NRF156), NnssF158A (a service-based interface represented by NSSF142), and NausF158G (a service-based interface represented by AUSF144). Other service-based interfaces not shown in Figure 1C (e.g., Nudr, N5G-eir, and Nudsf) can also be used.

[0040] The NR-V2X architecture can support highly reliable, low-latency sidelink communications with various traffic patterns, including periodic and aperiodic communications with random packet arrival times and sizes. The technologies disclosed herein can be used to support high reliability in distributed communications systems with dynamic topologies, including sidelink NR V2X communications systems.

[0041] Figure 2 shows block diagrams of communication devices according to several embodiments. The communication device 200 may be a dedicated computer, a personal or laptop computer (PC), a UE such as a tablet PC or smartphone, a dedicated network device such as an eNB, a server running software that configures the server to operate as a network device, a virtual device, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be performed by that machine. For example, the communication device 200 may be implemented as one or more of the devices shown in Figures 1A to 1C. It should be noted that the communications described herein may be encoded for reception by a receiving entity (e.g., gNB, UE) before transmission by a transmitting entity (e.g., UE, gNB) and decoded after reception by the receiving entity.

[0042] As described herein, examples may include or operate on logic or several components, modules, or mechanisms. Modules and components are tangible entities (e.g., hardware) capable of performing specific operations and may be configured or arranged in specific ways. In one example, a circuit may be arranged in a specific way as a module (e.g., internally or to external entities such as other circuits). In one example, one or more computer systems (e.g., standalone, client, or server computer systems) or one or more hardware processors, in whole or in part, may be configured by firmware or software (e.g., instructions, application parts, or applications) as modules that operate to perform specific operations. In one example, the software may reside on a machine-readable medium. In one example, the software, when executed by the underlying hardware of the module, causes the hardware to perform a specified operation.

[0043] Therefore, the terms “module” (and “component”) are understood to include tangible entities that are physically constructed, specifically configured (e.g., wired), or temporarily configured (e.g., programmed) to operate in a specified manner or to perform some or all of the operations described herein. Considering an example where a module is temporarily configured, each module does not need to be instantiated at any given time. For example, if a module includes a general-purpose hardware processor configured using software, the general-purpose hardware processor may be configured as different modules at different times. Thus, software may configure a hardware processor to, for example, configure a particular module at one time and different modules at different times.

[0044] The communication device 200 includes a hardware processor (or equivalent processing circuit) 202 (e.g., a central processing unit (CPU), GPU, hardware processor core, or any combination thereof), main memory 204, and static memory 206, some or all of which may communicate with each other via an interlink (e.g., a bus) 208. The main memory 204 may include any or all of removable and non-removable storage devices, volatile memory, or non-volatile memory. The communication device 200 may further include a display unit 210 such as a video display, an alphanumeric input device 212 (e.g., a keyboard), and a user interface (UI) navigation device 214 (e.g., a mouse). In one example, the display unit 210, the input device 212, and the UI navigation device 214 may be touchscreen displays. The communication device 200 may further include a storage device (e.g., a drive unit) 216, a signal generating device 218 (e.g., a speaker), a network interface device 220, and one or more sensors such as a Global Positioning System (GPS) sensor, a compass, an accelerometer, or other sensors. The communication device 200 may further include an output controller such as a serial (e.g., Universal Serial Bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near-field communication (NFC), etc.) connection) for communicating with or controlling one or more peripheral devices (e.g., a printer, a card reader, etc.).

[0045] The storage device 216 may include a non-temporary machine-readable medium 222 (hereinafter simply referred to as "machine-readable medium") on which one or more sets of data structures or instructions 224 (e.g., software) that embody or utilize one or more of the technologies or functions described herein are stored. The instructions 224 may also reside, all or at least partially, in the main memory 204, static memory 206, and / or hardware processor 202 while the instructions are being executed by the communication device 200. Although the machine-readable medium 222 is illustrated as a single medium, the term "machine-readable medium" may include one or more mediums (e.g., centralized or distributed databases, and / or associated caches and servers) configured to store one or more instructions 224.

[0046] The term “machine-readable medium” may include any medium capable of storing, encoding, or transmitting instructions to be executed by the communication device 200, causing the communication device 200 to execute one or more of the technologies of this disclosure, or storing, encoding, or transmitting data structures used by or associated with such instructions. Non-limiting examples of machine-readable mediums may include solid memory, and optical and magnetic media. Specific examples of machine-readable mediums may include: non-volatile memory such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), electrically programmable read-only memory (EEPROM)) and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; random access memory (RAM); and CD-ROM and DVD-ROM disks.

[0047] Instruction 224 may also be transmitted and received over a communication network using a transmission medium 226 via a network interface device 220 that utilizes one of several wireless local area network (WLAN) transport protocols (e.g., Frame Relay, Internet Protocol (IP), Transmission Control Protocol (TCP), User Datagram Protocol (UDP), Hypertext Transfer Protocol (HTTP), etc.). Illustrative communication networks may include local area networks (LANs), wide area networks (WANs), packet data networks (e.g., the Internet), mobile phone networks (e.g., cellular networks), conventional ordinary telephone (POTS) networks, and wireless data networks. Communication over the network may include one or more different protocols, such as the IEEE 802.11 family of standards known as Wi-Fi®, the IEEE 802.16 family of standards known as WiMAX, the IEEE 802.15.4 family of standards, the Long-Term Evolution (LTE) family of standards, the Universal Mobile Communications System (UMTS) family of standards, peer-to-peer (P2P) networks, and next-generation (NG) / fifth-generation (5G) standards. For example, the network interface device 220 may include one or more physical jacks (such as Ethernet, coaxial, or telephone jacks) or one or more antennas for connecting to the transmission medium 226.

[0048] It should be noted that the term “circuit” as used herein refers to, is a part of, or includes, hardware components configured to provide the described functions, such as electronic circuits, logic circuits, processors (shared, dedicated, or grouped) and / or memory (shared, dedicated, or grouped), application-specific integrated circuits (ASICs), field-programmable devices (FPDs) (e.g., field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), composite PLDs (CPLDs), high-capacity PLDs (HCPLDs), structured ASICs, or programmable SoCs), and digital signal processors (DSPs). In some embodiments, a circuit may run one or more software or firmware programs to provide at least some of the described functions. The term “circuit” may also refer to a combination of one or more hardware elements (or combinations of circuits used in an electrical or electronic system) and program code used to perform the functions of that program code. In these embodiments, a combination of hardware elements and program code may be referred to as a particular type of circuit.

[0049] Accordingly, as used herein, the terms “processor circuit” or “processor” refer to, or are part of, or include, a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations, or recording, storing, and / or transferring digital data. The terms “processor circuit” or “processor” may refer to one or more application processors, one or more baseband processors, physical central processing units (CPUs), single-core or multi-core processors, and / or other devices capable of executing or otherwise manipulating computer executable instructions such as program code, software modules, and / or functional processes.

[0050] The radio links described herein may operate in accordance with one or more of the following radio communication technologies and / or standards, which include Global System for Mobile Communications (GSM) radio communication technologies, General-Purpose Packet Radio Services (GPRS) radio communication technologies, Enhanced Data Rate for GSM Evolution (EDGE) radio communication technologies, and / or Third Generation Partnership Project (3GPP) radio communication technologies, such as Universal Mobile Communications System (UMTS), Freedom of Multimedia Access (FOMA), 3GPP Long-Term Evolution (LTE), 3GPP Long-Term Evolution Advanced (LTE Advanced), and Code Division Multiple Access 2000 (CDMA). 2000), Cellular Digital Packet Data (CDPD), Mobitex, Third Generation (3G), Circuit Switched Data (CSD), High-Speed ​​Circuit Switched Data (HSCSD), Universal Mobile Communications System (Third Generation) (UMTS(3G)), Broadband Code Division Multiple Access (Universal Mobile Communications System) (W-CDMA(UMTS)), High-Speed ​​Packet Access (HSPA), High-Speed ​​Downlink Packet Access (HSDPA), High-Speed ​​Uplink Packet Access (HSUPA), High-Speed ​​Packet Access Plus (HSPA+), Universal Mobile Communications System - Time Division Duplex (UMTS-TDD), Time Division Code Division Multiple Access (TD-CDMA), Time Division Synchronous Code Division Multiple Access (TD-CDMA), Third Generation Partnership Project Release 8 (Pre-4th Generation) (3GPP Rel.8(Pre-4G)), 3GPP Rel.9 (Third Generation Partnership Project Release 9), 3GPP Rel.10 (Third Generation Partnership Project Release 10), 3GPP Rel.11 (Third Generation Partnership Project Release 11), 3GPP Rel.12 (Third Generation Partnership Project Release 12), 3GPP Rel.13 (Third Generation Partnership Project Release 13), 3GPP Rel.14 (Third Generation Partnership Project Release 14), 3GPP Rel.15 (Third Generation Partnership Project Release 15), 3GPP Rel.16 (Third Generation Partnership Project Release 16), 3GPP Rel.17 (Third Generation Partnership Project Release 17) and subsequent releases (Rel. 18, Rel.19, etc.), 3GPP 5G, 5G, 5G New Radio (5G NR), 3GPP 5G New Radio, 3GPP LTE Extra, LTE Advanced Pro, LTE License-Assisted Access (LAA), MuLTEfire, UMTS Terrestrial Radio Access (UTRA), Advanced UMTS Terrestrial Radio Access (E-UTRA), Long-Term Evolution Advanced (4th Generation) (LTE Advanced (4G)), cdmaOne (2G), Code Division Multiple Access 2000 (3rd Generation) (CDMA2000 (3G)), Evolutionary Data Optimized or Evolutionary Data Only (EV-DO), Advanced Mobile Phone Systems (1st Generation) (AMPS (1G)), Total Access Communication Systems / Extended Total Access Communication Systems (TACS / ETACS), Digital AMPS (2nd Generation) (D-AMPS (2G)), Push-to-Talk (PTT), Mobile Communications System (MTS), Improved Mobile Communications System (IMTS), Advanced Mobile Communications System (AMTS), OLT (Offentilating Landmobile) Telefoni (Norwegian for public land mobile telephone), MTD (Swedish abbreviation for Mobiltelefonisystem D, or mobile phone system D), Public Automated Land Mobile) (Autotel / PALM), ARP (Autoradiopuhelin in Finnish, "car radio phone"), NMT (Nordic mobile phone), NTT's high-capacity version (Nippon Telegraph and Telephone) (Hicap), Cellular Digital Packet Data (CDPD), Mobitex, DataTAC, Integrated Digital Expansion Network (iDEN), Personal Digital Cellular (PDC), Circuit Switched Data (CSD), Personal Handyphone System (PHS), Broadband Integrated Digital Expansion Network (WiDEN), iBurst, Unlicensed Mobile Access (UMA), 3GPP General Purpose Access Network (also known as GAN standard), Zigbee, Bluetooth®, Wireless Gigabit Alliance (WiGig) standard, Millimeter Wave standards in general (WiGig, IEEE 802.11ad, IEEE 802.Wireless systems operating at 10-300GHz or higher, such as 11ay; technologies operating in the 300GHz and THz bands and above; vehicle-to-vehicle (V2V), vehicle-to-X (V2X), vehicle-to-infrastructure (V2I), and infrastructure-to-vehicle (I2V) communication technologies (3GPP LTE-based, IEEE 802.11p, or IEEE 802.11bd, and others); DSRC (dedicated narrow-band communication) communication systems such as 3GPP cellular V2X and intelligent road traffic systems (typically operating at 5850MHz-5925MHz or higher (CEPT) This includes, but is not limited to, IEEE 802.11p-based DSRC systems (including, but not limited to, European ITS-G5 systems, i.e., European ITS-G5A (i.e., ITS-G5 operation in the European ITS frequency band dedicated to ITS for safety-related applications in the frequency range of 5,875 GHz to 5,905 GHz), ITS-G5B (i.e., European ITS frequency band dedicated to non-safety applications in the frequency range of 5,855 GHz to 5,875 GHz), and ITS-G5C (i.e., European-style IEEE 802.11p-based DSRC, i.e., ITS-G5C operation in the frequency range of 5,470 GHz to 5,725 GHz), as well as DSRC in the 700 MHz band (including 715 MHz to 725 MHz), and IEEE 802.11bd-based systems, in accordance with the proposed changes in Report 71.

[0051] The embodiments described herein can be used in the context of any spectrum management scheme, including dedicated licensed spectra, unlicensed spectra, license-exempt spectra, and (licensed) shared spectra (e.g., LSA = 2.3–2.4 GHz, 3.4–3.6 GHz, 3.6–3.8 GHz and above frequencies, SAS = Spectrum Access System / CBRS = Citizens Broadband Radio System for 3.55–3.7 GHz and above frequencies).The applicable spectral bands include the IMT (International Mobile Communications) spectrum and other types of spectrum / bands, such as those with national allocations (including 450-470MHz, 902-928MHz (Note: e.g., allocated in the United States (FCC Part 15))) and 863-868.6MHz (Note: e.g., allocated in the European Union (ETSI EN300)). 220) allocated), 915.9-929.7MHz (Note: For example, allocated in Japan), 917-923.5MHz (Note: For example, allocated in South Korea), 755-779MHz and 779-787MHz (Note: For example, allocated in China), 790-960MHz, 1710-2025MHz, 2110-2200MHz, 2300-2400MHz, 2.4-2.4835GHz (Note: Globally available ISM band, used by Wi-Fi® technology family (11b / g / n / ax) and Bluetooth®), 2500-2690MHz, 698-790MHz, 610-790MHz, 3400-3600MHz, 3400-3800MHz, 3800-4200MHz, 3.55-3.7GHz (Note: For example, allocated to citizen broadband wireless services in the United States), 5.15-5.25GHz, 5.25-5.35GHz, 5.47-5.725GHz, and 5.725-5.85GHz bands (Note: For example, allocated in the United States (FCC Part 15), consisting of four U-NII bands totaling 500MHz spectrum), 5.725-5.875GHz (Note: For example, allocated in the EU (ETSI EN301 893)), 5.47-5.65GHz (Note: For example, allocated in South Korea), 5925-7125MHz, and 5925-6425MHz bands (Note: Under consideration in the United States and the EU, respectively. Next-generation Wi-Fi systems are expected to include the 6GHz spectrum as an operating band, but it should be noted that as of December 2017, Wi-Fi systems are not yet permitted in this band.)Regulations are expected to be completed between 2019 and 2020), IMT Advanced Spectra, IMT-2020 Spectra (expected to include 3600-3800MHz, 3800-4200MHz, 3.5GHz band, 700MHz band, bands in the 24.25-86GHz range, etc.), and Spectra that have become available under the FCC's "Spectrum Frontier" 5G initiative (including 27.5-28.35GHz, 29.1-29.25GHz, 31-31.3GHz, 37-38.6GHz, 38.6-40GHz, 42-42.5GHz, 57-64GHz, 71-76GHz, 81-86GHz and 92-94GHz, etc.). , the ITS (Intelligent Transportation Systems) bands of 5.9GHz (usually 5.85-5.925GHz) and 63-64GHz, WiGig band 1 (57.24-59.40GHz), WiGig band 2 (59.40-61.56GHz), WiGig band 3 (61.56-63.72GHz), and WiGig band 4 (63.72-65.88GHz), which are currently allocated to WiGig, and 57-64 / 66GHz (Note: This band is almost globally designated for Multi-Gigabit Wireless Systems (MGWS) / WiGig. In the US (FCC Part 15), a total of 14GHz of spectrum is allocated, but in the EU (ETSI) EN302 567 and ETSI EN301 217-2 (for fixed P2P) allocate a total of 9 GHz of spectrum, including the 70.2 GHz–71 GHz band, any band between 65.88 GHz–71 GHz, bands currently allocated to automotive radar applications such as 76–81 GHz, and future bands including 94–300 GHz and above. Furthermore, this scheme can be secondarily used in bands such as the TV white space band (usually below 790 MHz), where the 400 MHz and 700 MHz bands are particularly promising candidates. In addition to mobile phone applications, specific applications for vertical markets such as PMSE (Programming and Special Events), medical, health, surgery, automotive, low latency, and drones can be addressed.

[0052] The embodiments described herein can also implement hierarchical applications of the scheme by introducing hierarchical prioritization of use for different types of users (e.g., low / medium / high priority) based on, for example, prioritized access to the spectrum, with, for example, the highest priority given to Tier 1 users, then Tier 2 users, then Tier 3 users, and so on.

[0053] The embodiments described herein can also be applied to different single-carrier or OFDM flavors (CP-OFDM, SC-FDMA, SC-OFDM, Filter Bank-Based Multicarrier (FBMC), OFDMA, etc.) and in particular to 3GPP NR (New Radio) by assigning OFDM carrier data bit vectors to the corresponding symbolic resources.

[0054] Some functions are defined for the network side, such as AP, eNB, NR, or gNB. Note that these terms are typically used in the context of 3GPP 5G and 6G communication systems. Nevertheless, the UE can assume this role and function as an AP, eNB, or gNB. In other words, some or all of the functions defined for network equipment can be implemented by the UE.

[0055] As mentioned above, one of the issues is improving cell reselection. Power saving can be designed for idle-mode cell reselection where Reference Signal Received Power (RSRP) is used as the metric. An idle-mode UE does not have a radio resource control (RRC) connection with the gNB and can move to RRC connected mode using an initial connection procedure or a connection establishment procedure.

[0056] Once the RRC connection is established, the UE performs Radio Link Monitoring (RLM), continuously measuring reference signals from the serving gNB (or cell) to determine the radio link quality and provide feedback to the serving gNB. The 5G reference signals measured include the Signaling System Block (SSB) signal or the Channel Status Information Reference Signal (CSI-RS). These measurements can be used to determine if a Radio Link Failure (RLF) has occurred and to trigger the RRC re-establishment procedure.

[0057] However, continuous measurement and feedback can consume a significant amount of power by the UE. Therefore, power saving by the UE can be facilitated by relaxing RLM measurements, in which case the UE is allowed to reduce the frequency of RLM measurements when certain criteria are met (i.e., the UE is in a relaxed state). Specifically, in a typical RLM procedure, the UE measures the SINR of the measured 5G reference signal. The UE then compares the SINR to threshold Qin (the level at which the downlink radio link can be reliably received) and threshold Qout (the level at which the downlink radio link cannot be reliably received) to indicate whether the serving cell quality is sufficient to sustain data traffic. Since RLM relies on SINR estimation, relaxation criteria may take SINR into account. The absolute SINR value can be used not only for RLM but also as a metric for serving cell quality for criteria to relax RLM measurements.

[0058] Furthermore, SINR levels change more rapidly than RSRP. Figure 3 shows a plot of simulated SINR versus time in several aspects. As shown in Figure 3, the estimated SINR value changes over time and reflects only instantaneous channel quality. If a fixed SINR value is used as the relaxation threshold, the estimated SNR value may frequently exceed the threshold. For example, if the current channel's average SINR = 4 dB, due to variability, the SINR range may instantaneously vary from 0 dB to 8 dB depending on several conditions.

[0059] If the instantaneous SINR is greater than the threshold SINR, the UE may decide that mitigation is appropriate (i.e., enter a mitigated state). However, whether to initiate mitigation when the determined SINR is below the threshold but still above the out-of-service (OOS) threshold remains questionable, particularly in determining whether the mitigation scheme is stable (and therefore whether to exit the mitigated state).

[0060] Therefore, in order to provide a more robust relaxation scheme and reduce SINR variability, in some embodiments, the SINR is measured and processed during a time window to determine whether the relaxation criteria are met, and thus whether it is appropriate to enter or exit a relaxation state (also referred to as relaxation state on and relaxation state off, respectively). In some embodiments, a method for evaluating the SINR and processing the SINR value during the relaxation RLM is described.

[0061] The effect of the measurement period on reducing SINR variation is described here. Different evaluation times are simulated for the low-speed case. Figure 4 shows plots of CDF vs. SINR variation in several embodiments. The UE velocity in Figure 4 was simulated as 3 km / h. SINR estimation error due to the UE was not considered. The evaluation time was for a predetermined number of samples: 1, 5, 10, or 15 samples. The CSI-RS period was 5 ms. Therefore, the window length was 1 / 5 / 10 / 15 × 5 ms. The X-axis in Figure 4 is the SINR variation range. During the evaluation time, the instantaneous SINR values ​​were averaged to obtain a single filtered SINR value.

[0062] The simulation results in Figure 4 show that SINR variation decreases with more mean samples. As can be seen from the CDF in Figure 4, with 10 samples as the evaluation time, the maximum SINR variation range is less than 1.3 dB in the 95% case. However, when only one sample is used, the maximum SINR variation range increases to 4.5 dB in the 95% case. Therefore, the SINR measurement window for reducing SINR variation for RLM relaxation is N*T CSI-RS / SSB It can be set as follows, where N is the number of SSB / CSI-RS samples, and T CSI-RS / SSB This is the period of SSB / CSI-RS transmission from the gNB. The window period depends on the UE speed; it decreases as the speed increases and increases as the speed decreases.

[0063] The method for handling SINR within a window is also discussed as follows. Both methods for obtaining SINR values ​​and handling SINR within a window are described. Instantaneous SINR values ​​may be obtained first, and then these instantaneous SINR values ​​may be filtered.

[0064] In the first embodiment, the instantaneous SINR value can be derived from the SSB / CSI-RS measurement (i.e., directly from the RLM signal itself). In the second embodiment, the instantaneous SINR value can be derived from a block error rate (BLER)-SINR mapping table provided by the UE via the gNB or preloaded into the UE. In the second embodiment, the UE first calculates the BLER and then converts the BLER value to SINR based on the mapping table.

[0065] After the UE determines several instantaneous SINR values, the SINR values ​​can be processed within a measurement window. To process the SINR values, in a first method, the SINR is averaged over N instantaneous SINR values, where N is the number of samples in the window. In a second embodiment, the signal level and noise level are averaged over N samples, respectively. The averaged signal power is then divided by the averaged noise power to obtain the averaged SINR. The averaged SINR obtained by either embodiment can be used for RLM / beam fault detection (BFD) relaxation evaluation.

[0066] The low mobility of Rel-16 reflects the low variability of the filtered RSRP. In Rel-17, the low mobility criterion used in Rel-16 is not suitable for reuse because RLM / BFD relies on SINR estimation. RSRP primarily focuses on useful signal power, while SINR also takes noise and interference power into account. In Rel-17, "low SINR variability," which is more directly related to RLM / BFD performance, may be considered. RLM / BFD relaxation schemes may be used in low SINR variability scenarios.

[0067] In some embodiments, in a first operation of the measurement method to reflect low SINR variability, the UE calculates ΔSINR (SINR determined between adjacent measurement sets) between adjacent SINR levels. In a second operation, ΔSINR is compared to a threshold. If ΔSINR is less than the threshold for a certain period of time, the current scenario can be assumed to be stable and in a "low SINR variability" state.

[0068] In some embodiments of the RLM relaxation criterion, the SINR calculated by the UE may be compared to a fixed SINR threshold to determine whether the relaxation criterion is met. For example, the fixed threshold is X=Q out +Z dB, Q outis the SINR threshold for RLM / BFD OOS, and Z dB is an extra margin to ensure the channel is in good condition.

[0069] Since SINR fluctuates over time, the SINR fluctuation range can be added to a fixed SINR threshold to ensure that in most cases the SINR exceeds the 95% threshold. For example, if the SINR threshold is X dB and the SINR fluctuation range is Y dB, the final SINR threshold will be X + Y dB. The SINR fluctuation range can be determined from the CDF curve of the SINR, and the maximum SINR fluctuation (5%, 95%) is selected as Y dB. In other embodiments, the threshold may be other than 95%.

[0070] BFD is designed to help UEs determine low beam quality and trigger beam fault recovery without causing radio link failure. When SINR is used as a relaxation criterion, similar to RLM, the SINR variation range can be further added to the SINR threshold. Q of BFD out is RLM's Q out Because it is 4dB higher, the BFD criterion becomes stricter when the same margin is considered in the relaxation criteria. In other words, the SINR relaxation threshold for BFD is higher than that for RLM.

[0071] On the other hand, the criterion for in-sync synchronization in beam management is the threshold Q indicated by the higher layer parameter rsrp-ThresholdSSB, where the measured layer 1 (L1)-RSRP is equal to the measured layer 1 (L1)-RSRP. in_LR The above conditions were met. Unlike RLM, BM synchronization also considers RSRP. Therefore, RSRP can also be considered as a relaxation criterion for BFD. For example, UE may relax the BFD measurement if the measured RSRP is higher than the RSRP threshold.

[0072] In some embodiments, the criteria for entering a relaxation criterion and returning to normal RLM operation should be aligned. In some embodiments, the UE performs relaxed RLM; when it detects a predetermined number of out-of-sync indications, triggers timer 310 (T310), or in response to observed link quality degradation or movement state change, the UE may return to normal RLM operation (i.e., without relaxation). T310 is triggered by the detection of a problem in the serving cell's physical layer, and when it expires, the UE enters the RRC_Idle state or initiates the connection re-establishment procedure. Thus, in various embodiments, the UE may return to normal RLM operation when the relaxation criterion is not met, when N310 starts counting (i.e., one out-of-sync indication is received), when T310 is running (i.e., an out-of-sync indication is received in N310), when link quality degradation is observed, or when movement state change is observed.

[0073] When a high SINR is considered a criterion for entering the relaxation criterion and an exit criterion for desynchronization, the SINR gap is relatively large and can potentially lead to problems. Figure 5 shows plots of SINR versus relaxation time in several embodiments.

[0074] The problem is illustrated in Figure 5: At time A, the SINR is higher than the SINR criterion that initiates relaxation, and the RLM begins to relax. Starting from point B, the SINR is below the relaxation threshold but still higher than the OOS threshold, and the UE does not return to normal mode. However, the relaxation criterion is not met from time B to C. Therefore, the relaxation criterion and the return criterion can be designed together to avoid such cases. Assuming a fixed SINR threshold of X dB and a SINR fluctuation range of Y dB, the final SINR threshold may be X+Y dB, and the return threshold may then be set to XY dB. In some embodiments, the final SINR threshold may be X+Y dB, but the return threshold may be set to XZ dB. Alternatively, or additionally, the return threshold may be Qin, where Qin is the SINR threshold for RLM synchronization, or the final SINR threshold may be Qout. In various embodiments, Y may be, for example, 2 dB, 4 dB, etc.

[0075] Regarding returning to BFD, RSRP can also be considered as a relaxation criterion, so the return criterion can also consider RSRP. The thresholds for BFD and RLM can be set independently. As mentioned above, both thresholds can be based on SINR information.

[0076] While embodiments are described with reference to specific exemplary embodiments, it will be apparent that various modifications and changes can be made to these embodiments without departing from the broader scope of this disclosure. Therefore, the specification and drawings should be considered illustrative rather than restrictive. The accompanying drawings, which constitute part of this disclosure, illustrate, not restrictively, specific embodiments that can carry out the subject matter. The illustrated embodiments are described in sufficient detail to enable those skilled in the art to carry out the teachings disclosed herein. Other embodiments can be utilized and derived therefrom, so as to be structural and logical substitutions and modifications without departing from the scope of this disclosure. Therefore, this detailed description should not be construed restrictively, and the scope of the various embodiments is defined solely by the accompanying claims and the entire scope of equivalents to which such claims are entitled.

[0077] In this specification, subject matter may be referred to individually and / or collectively by the term “embodiments” for convenience only, and is not intended to spontaneously limit the scope of this application to any single inventive concept when multiple inventive concepts are actually disclosed. Therefore, it should be understood that any configuration calculated to achieve the same objective, where a particular embodiment is illustrated and described herein, may be substituted for the particular embodiment illustrated. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the embodiments described above and other embodiments not specifically described herein will be apparent to those skilled in the art upon consideration of the above description.

[0078] In this specification, the term “one ("a" or “an")” is used to include one or more, independently of any other examples or uses of “at least one” or “one or more,” as is common in patent literature. In this specification, the term “or” is used to refer to non-exclusive or, unless otherwise indicated, such that “A or B” includes “A but not B,” “B but not A,” and “A and B.” In this specification, the terms “including” and “whereine” are used as plain English equivalents of the terms “having” and “whereine,” respectively. Furthermore, in the following claims, the terms “including” and “having” are open-ended, meaning that a system, UE, article, composition, formulation or process containing elements in addition to those listed after such terms in the claims is still considered to be within the scope of the claims. Furthermore, in the following claims, the terms "first," "second," and "third," etc., are used merely as labels and are not intended to impose numerical requirements on the subject matter.

[0079] The disclosure summary is provided in accordance with 37 C. FR Section 1.72(b), which requires a summary that allows readers to quickly confirm the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. Furthermore, it will be seen in the detailed description above that, for the purpose of streamlining the disclosure, various features have been grouped into a single embodiment. This method of disclosure should not be construed as reflecting an intention that the embodiments described in the claims require more features than expressly described in each claim. Rather, as reflected in the following claims, the subject matter of the invention is less than all the features of a single disclosed embodiment. Accordingly, the following claims are incorporated herein by reference, and each claim stands alone as an independent embodiment.

Claims

1. A device for user equipment (UE), wherein the device is: The aforementioned UE: Receive the Radio Link Measurement (RLM) signal from the 5th generation NodeB (gNB); In order to determine the signal-to-interference-plus-noise (SINR) of the RLM signal, the RLM signal is measured; Based on the SINR of the RLM signal, it is determined whether the UE enters or exits the RLM relaxation state based on a predetermined RLM relaxation threshold; The frequency of measuring the RLM signal from the gNB is adjusted depending on whether the RLM relaxation state is entered or exited. A processing circuit configured as follows: A memory configured to store the RLM relaxation state; The processing circuit is configured to use the UE as a value obtained by adding the SINR threshold and the SINR variation range for entering the RLM relaxation state, and a value obtained by subtracting the SINR variation range from the SINR threshold for exiting the RLM relaxation state, wherein the SINR variation range includes the SINR threshold for RLM synchronization. Device.

2. The processing circuit is configured to determine whether the UE has met relaxation criteria to enter or exit the RLM relaxation state, based on measurements of the RLM signal over a predetermined time window. The apparatus according to claim 1.

3. The processing circuit is configured to adjust the UE based on the variation in the SINR of the RLM signal over time. The apparatus according to claim 2.

4. The RLM signal includes a signaling system block (SSB) signal or a channel status information reference signal (CSI-RS). The apparatus according to claim 2.

5. The predetermined time window is obtained by multiplying the number of integers in the RLM signal by the period of the RLM signal. The apparatus according to claim 2.

6. The processing circuit is configured to derive the UE directly from each of the RLM signals, The apparatus according to any one of claims 1 to 5.

7. The processing circuit uses the UE as follows: The block error rate (BLER) is calculated from each of the aforementioned RLM signals; A BLER-SINR mapping table is used to derive the instantaneous SINR value for each of the RLM signals; Configure it as follows: The apparatus according to any one of claims 1 to 5.

8. The processing circuit uses the UE as follows: The instantaneous SINR value is derived from each of the aforementioned RLM signals; The instantaneous SINR values ​​are averaged to determine whether to change the RLM relaxation state of the UE; Configure it as follows: The apparatus according to any one of claims 1 to 5.

9. The processing circuit uses the UE as follows: To obtain an average signal level, the signal levels of each of the RLM signals are averaged; To obtain an average noise level, the noise levels of each of the RLM signals are averaged; To obtain the average SINR, the average signal level and the average noise level are used; The mean SINR is used to determine whether to change the RLM relaxation state of the UE; Configure it as follows: The apparatus according to any one of claims 1 to 5.

10. The processing circuit uses the UE as follows: The change in SINR of the RLM signal is determined; The change in SINR is compared with the SINR threshold; Based on the comparison of the change in SINR with the SINR threshold, it is determined whether the SINR of the RLM signal is in a low-fluctuation state; The decision to change the RLM relaxation state of the UE is limited to when the SINR of the RLM signal is in a low-variability state; Configure it as follows: The apparatus according to any one of claims 1 to 9.

11. The processing circuit is configured to compare the UE with the SINR of the RLM signal to a fixed threshold in order to determine whether to enter or remain in the RLM relaxation state, wherein the fixed threshold includes a SINR threshold for RLM out-of-sync and a SINR variation range derived from a cumulative distribution function (CDF) curve of SINR using a predetermined maximum SINR variation range. The apparatus according to any one of claims 1 to 10.

12. The processing circuit is configured to use different criteria for entering and exiting the UE for RLM and beam fault detection (BFD). The apparatus according to any one of claims 1 to 11.

13. A non-temporary computer-readable storage medium for storing instructions for execution by one or more processors of a user device (UE), wherein the one or more processors execute the UE when the instructions are executed: Receive a radio link measurement (RLM) signal from a 5th generation NodeB (gNB); In order to determine the signal-to-interference-plus-noise (SINR) of the RLM signal, the RLM signal is measured; Based on the SINR of the RLM signal, it is determined whether to enter or exit the RLM relaxation state based on a predetermined RLM relaxation threshold; The frequency of measuring the RLM signal from the gNB is adjusted depending on whether the RLM relaxation state is entered or exited. Configured in this way, The one or more processors are configured to use, when the instruction is executed, the UE using a value obtained by adding the SINR threshold for entering the RLM relaxation state and the SINR variation range, and a value obtained by subtracting the SINR variation range from the SINR threshold for exiting the RLM relaxation state, wherein the SINR variation range includes the SINR threshold for RLM synchronization. Non-temporary computer-readable storage medium.

14. The one or more processors are configured to determine, when the instruction is executed, whether the UE enters the RLM relaxation state or whether relaxation criteria are met for the UE to remain in the RLM relaxation state, based on measurements of the RLM signal over a predetermined time window. The RLM signal includes a signaling system block (SSB) or a channel status information reference signal (CSI-RS). The non-temporary computer-readable storage medium according to claim 13.

15. The one or more processors are configured to use different criteria for entering and exiting RLM and beam fault detection (BFD) when the instruction is executed. A non-temporary computer-readable storage medium according to claim 13 or 14.

16. The one or more processors are configured to compare the UE with a fixed threshold to determine whether to enter or remain in the RLM relaxation state when the instruction is executed, the fixed threshold includes a SINR threshold for RLM desynchronization and a SINR variation range derived from a cumulative distribution function (CDF) curve of SINR using a predetermined maximum SINR variation range. A non-temporary computer-readable storage medium according to any one of claims 13 to 15.

Images