Wireless resource management relaxation

Abstract

Embodiments of the present disclosure relate to radio resource management relaxations. A method is disclosed that includes determining, by a device, a radio resource management relaxation configuration or offset value to be used by the device based on a synchronization signal block (SSB) received from a network device.

Description

Technical Field

[0001] The following example embodiments relate to wireless communication. Background Technology

[0002] Radio Resource Management (RRM) relaxation can be used to reduce power consumption of user equipment. Summary of the Invention

[0003] The scope of protection sought by the various example embodiments is defined by the claims. Example embodiments and features (if any) described in this specification that are not within the scope of the claims are to be interpreted as examples that aid in understanding the various embodiments.

[0004] According to the first aspect, a method is provided, the method comprising:

[0005] The device determines the radio resource management relaxation configuration or offset value to be used based on the synchronization signal block (SSB) received from the network device.

[0006] According to a second aspect, an apparatus is provided that includes components for causing the apparatus to perform at least the method of the first aspect.

[0007] According to a third aspect, an apparatus is provided, the apparatus comprising at least one processor and at least one memory storing instructions, which, when executed by the at least one processor, cause the apparatus to perform at least the method of the first aspect.

[0008] According to a fourth aspect, a non-transitory computer-readable medium is provided, comprising program instructions that, when executed by a device, cause the device to perform at least the method of the first aspect.

[0009] According to the fifth aspect, a method is provided, the method comprising:

[0010] The network device sends a synchronization signal block (SSB) to the user equipment, indicating the wireless resource management relaxation configuration or offset value to be used by the user equipment.

[0011] According to a sixth aspect, an apparatus is provided that includes components for causing the apparatus to perform at least the method of the fifth aspect.

[0012] According to a seventh aspect, an apparatus is provided, the apparatus comprising at least one processor and at least one memory storing instructions, which, when executed by the at least one processor, cause the apparatus to perform at least the method of the fifth aspect.

[0013] According to the eighth aspect, a non-transitory computer-readable medium including program instructions, which, when executed by a device, cause the device to perform at least the method of the fifth aspect. Attached Figure Description

[0014] In the following description, various exemplary embodiments will be described in more detail with reference to the accompanying drawings, in which:

[0015] Figure 1 An example of a wireless communication network is shown;

[0016] Figure 2 This demonstrates network energy saving;

[0017] Figures 3 to 5 A signal flow diagram according to an exemplary embodiment is shown;

[0018] Figures 6 to 8 A flowchart according to an exemplary embodiment is shown; and

[0019] Figure 9 An exemplary device is shown. Detailed Implementation

[0020] The following embodiments are exemplary. Although the specification may refer to "an," "one," or "some" embodiments in several places in the text, this does not necessarily mean that each reference to the same embodiment(s) or a particular feature applies only to a single embodiment. Individual features of different embodiments may also be combined to provide other embodiments within the scope of the claims. Furthermore, the words "comprising" and "including" should be understood as not limiting the described embodiments to consist only of those features already mentioned, and such embodiments may also include features not specifically mentioned. Reference numerals in the specification and / or claims are used to illustrate embodiments with reference to the accompanying drawings, and not to limit the embodiments to these examples.

[0021] Furthermore, it should be understood that, as used herein, the terms “at least one” and “one or more” respectively mean “any one of at least one” or “any one of one or more”. Additionally, as used herein, “at least one of the following: ” and “at least one of ” and similar wording (where the list of two or more elements is connected by “and” or “or”) means at least any one of these elements, or at least any two or more of these elements, or at least all of these elements.

[0022] Some of the example embodiments described herein can be implemented in wireless communication networks, including radio access networks based on one or more of the following radio access technologies (RATs): Global System for Mobile Communications (GSM) or any other second-generation (2G) radio access technology, Universal Mobile Telecommunications System (UMTS, 3G) based on Basic Wideband Code Division Multiple Access (W-CDMA), High-Speed ​​Packet Access (HSPA), Long Term Evolution (LTE), LTE Advanced, fourth-generation (4G), fifth-generation (5G), 5G New Radio (NR), 5G Advanced (i.e., 3GPP NR Rel-18 and later), sixth-generation (6G), or seventh-generation (7G). Some examples of radio access networks include Universal Mobile Telecommunications System (UMTS) Radio Access Network (UTRAN), Evolved Universal Terrestrial Radio Access Network (E-UTRA), or Next Generation Radio Access Network (NG-RAN). The wireless communication network may also include a core network, and some example embodiments can also be applied to the network functions of the core network.

[0023] It should be noted that the embodiments are not limited to the wireless communication network given as an example, and those skilled in the art can apply the solution to other wireless communication networks or systems with the necessary characteristics. For example, some example embodiments can also be applied to communication systems based on the IEEE 802.11 standard or communication systems based on the IEEE 802.15 standard. IEEE is an abbreviation for the Institute of Electrical and Electronics Engineers.

[0024] Figure 1 An example of a simplified wireless communication network is shown, illustrating some physical and logical entities. Figure 1 The connections shown can be physical or logical connections. Those skilled in the art will appreciate that wireless communication networks may also include, in addition to... Figure 1 Other physical and logical entities besides the physical and logical entities shown.

[0025] However, the exemplary embodiments described herein are not limited to the wireless communication networks given as examples, but those skilled in the art can apply the exemplary embodiments described herein to other wireless communication networks with the necessary characteristics.

[0026] Figure 1 The example wireless communication network shown includes a radio access network (RAN) and a core network 110.

[0027] Figure 1 User equipment (UE) 100 and 102 are shown, which are configured to wirelessly connect to access node 104 of a radio access network on one or more communication channels in a radio cell.

[0028] Access node 104 may include a computing device configured to control the radio resources of access node 104 and to wirelessly connect to one or more UEs 100, 102. Access node 104 may also be referred to as a base station, base transceiver station (BTS), access point, cell site, network node, radio access network node, RAN node, or network device.

[0029] For example, access node 104 may be an evolved NodeB (eNB or eNodeB), a next-generation evolved NodeB (ng-eNB), or a next-generation NodeB (gNB or gNodeB) providing a radio cell. Access node 104 may include or be coupled to a transceiver. From the transceiver of access node 104, a connection to an antenna element may be provided, which establishes a bidirectional radio link to one or more UEs 100. The antenna element may include an antenna or antenna element, or multiple antennas or antenna elements.

[0030] The radio connection (e.g., radio link) from UE 100, 102 to access node 104 can be referred to as an uplink (UL) or reverse link, while the radio connection (e.g., radio link) from access node 104 to UE 100, 102 can be referred to as a downlink (DL) or forward link. UE 100 can also communicate directly with another UE 102 via a radio connection commonly referred to as a sidelink (SL), and vice versa. It should be understood that access node 104 or its functionality can be implemented using any node, host, server, access point, or other entity suitable for providing such functionality.

[0031] The wireless access network may include more than one access node 104, in which case the access nodes may also be configured to communicate with each other via wired or wireless links. These links between access nodes may be used to send and / or receive control plane signaling, and may also be used to route data from one access node to another.

[0032] Access node 104 can also connect to core network (CN) 110. Core network 110 may include an evolved packet core (EPC) network and / or a fifth-generation core network (5GC). EPC may include network entities such as a serving gateway (S-GW) for routing and forwarding data packets, a packet data network gateway (P-GW) for providing connectivity to external packet data networks for the UE, and / or a mobility management entity (MME). 5GC may include one or more network functions such as at least one of user plane functions (UPF), access and mobility management functions (AMF), location management functions (LMF), and / or session management functions (SMF).

[0033] The core network 110 can also communicate with or utilize services provided by one or more external networks 113, such as the public switched telephone network or the Internet. For example, in a 5G wireless communication network, the UPF of the core network 110 can be configured to communicate with an external data network via the N6 interface. In an LTE wireless communication network, the P-GW of the core network 110 can be configured to communicate with an external data network.

[0034] It should also be understood that, compared to LTE or 5G, the functional allocation between core network operations and access node operations may differ or even not exist in future wireless communication networks.

[0035] The UEs 100 and 102 shown are a type of device that can be allocated and assigned resources on an air interface. UEs 100 and 102 may also be referred to as wireless communication devices, subscriber units, mobile stations, remote terminals, access terminals, user terminals, terminal equipment, or user equipment, to name just a few. UEs 100 and 102 can be computing devices operating with or without a Subscriber Identity Module (SIM), including but not limited to the following types of computing devices: mobile phones, smartphones, personal digital assistants (PDAs), handheld devices, computing devices including wireless modems (e.g., alarm or measuring devices), laptop computers, desktop computers, tablet computers, game consoles, laptops, multimedia devices, capability reduction (RedCap) devices, wearable devices with wireless components (e.g., watches, headphones, or glasses), home appliances with wireless components, sensors including wireless modems, or computing devices including wireless modems integrated in vehicles or homes.

[0036] Any features of the UE described in this document can also be implemented using corresponding devices, such as relay nodes. An example of such a relay node could be a Layer 3 relay (self-backhaul relay) toward an access node. A self-backhaul relay node can also be called an Integrated Access and Backhaul (IAB) node. An IAB node can include two logical parts: a Mobile Terminal (MT) part, which is responsible for (multiple) backhaul links (i.e., (multiple) links between the IAB node and the donor node (also called the parent node); and a Distributed Unit (DU) part, which is responsible for (multiple) access links (i.e., (multiple) sub-links between the IAB node and (multiple) UEs and / or between the IAB node and other IAB nodes (multiple hop scenarios)).

[0037] Another example of such a relay node could be a Layer 1 relay called a repeater. A repeater can amplify signals received from an access node and forward them to the UE, and / or amplify signals received from a UE and forward them to the access node.

[0038] It should be understood that UEs 100 and 102 can also be almost exclusively uplink-only devices, examples of which could be cameras or camcorders that load images or video clips onto the network. UEs 100 and 102 can also be devices capable of operating in Internet of Things (IoT) networks, which is a scenario in which the ability to transmit data over a network to objects can be provided without human-to-human or human-to-computer interaction.

[0039] Wireless communication networks can also support the use of cloud services. For example, at least a portion of the core network operation can be performed as a cloud service (this is in...). Figure 1 (Depicted by "cloud" 114). UEs 100 and 102 can also utilize cloud 114. In some applications, computations for a given UE can be performed in cloud 114 or in another UE.

[0040] Wireless communication networks can also include a central control entity, such as a Network Management System (NMS). An NMS is a centralized suite of software and hardware used to monitor, control, and manage network infrastructure. The NMS is responsible for a wide range of tasks, including fault management, configuration management, security management, performance management, and accounting management. The NMS enables network operators to efficiently manage and optimize network resources to ensure high performance, reliability, and security.

[0041] The various techniques described in this article can also be applied to cyber-physical systems (CPS) (a system of collaborative computing elements for controlling physical entities). CPS can realize and utilize a large number of interconnected ICT devices (sensors, actuators, processors, microcontrollers, etc.) embedded in physical objects in different locations. Mobile cyber-physical systems are a subcategory of cyber-physical systems where the physical systems under discussion can have inherent mobility. Examples of mobile physical systems include mobile robots and electronic products transported by humans or animals.

[0042] 5G enables the use of multiple-input multiple-output (MIMO) antennas in access nodes 104 and / or UEs 100, 102, far more base stations or access nodes than LTE networks (the so-called small cell concept), including macro sites operating in cooperation with smaller sites, and the use of various wireless technologies depending on service requirements, use cases, and / or available spectrum. 5G wireless communication networks can support a wide range of use cases and related applications, including video streaming, augmented reality, different data sharing methods, and various forms of machine-type applications such as (massive) machine-type communication (mMTC), including vehicle safety, various sensors, and real-time control.

[0043] In 5G wireless communication networks, access nodes and / or UEs can have multiple radio interfaces, such as sub-6 GHz, centimeter wave (cmWave), and millimeter wave (mmWave), and can also be integrated with traditional radio access technologies such as LTE. For example, integration with LTE can be implemented as a system where LTE provides macro coverage, and 5G radio interface access can be aggregated to LTE from small cells. In other words, 5G wireless communication networks can support inter-RAT interoperability (such as interoperability between LTE and 5G) and inter-RI interoperability (interoperability between radio interfaces, such as sub-6 GHz, cmWave, and mmWave).

[0044] 5G wireless communication networks can also apply network slicing, in which multiple independent and dedicated virtual subnets (network instances) can be created within the same physical infrastructure to run services with different requirements for latency, reliability, throughput and mobility.

[0045] 5G enables analytics and knowledge generation at the data source. This approach can involve leveraging resources that may not have continuous network connectivity, such as laptops, smartphones, tablets, and sensors. Multi-access edge computing (MEC) can provide a distributed computing environment for application and service hosting. It can also store and process content near cellular subscribers for faster response times. Edge computing can encompass a wide range of technologies, such as wireless sensor networks, mobile data acquisition, mobile signature analytics, collaborative distributed peer-to-peer self-organizing networks and processing (which can also be categorized as local cloud / fog computing and grid / mesh computing), dew computing, mobile edge computing, cloudlets, distributed data storage and retrieval, autonomous self-healing networks, remote cloud services, augmented and virtual reality, data caching, the Internet of Things (massive connectivity and / or time-critical), and critical communications (autonomous vehicles, traffic safety, real-time analytics, time-critical control, healthcare applications).

[0046] In one embodiment, access node 104 may include: a radio unit (RU) comprising a radio transceiver (TRX), i.e., a transmitter (Tx) and a receiver (Rx); one or more distributed units (DUs) 105, which may be used for so-called Layer 1 (L1) processing and real-time Layer 2 (L2) processing; and a central unit (CU) 108 (also called a centralized unit), which may be used for non-real-time Layer 2 and Layer 3 (L3) processing. CU 108 may be connected to one or more DUs 105, for example, via an F1 interface. Such an embodiment of access node 104 allows for the centralization of CUs relative to cell sites and DUs, while DUs may be more distributed and may even be retained at the cell site. CUs and DUs together may also be referred to as baseband or baseband unit (BBU). CUs and DUs may also be included in a radio access point (RAP).

[0047] CU 108 may be a logical node that hosts the Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), and / or Packet Data Convergence Protocol (PDCP) for the NR protocol stack of access node 104. CU 108 may include a control plane (CU-CP), which may be a logical node that hosts the control plane portions of the RRC and PDCP protocols for the NR protocol stack of access node 104. CU 108 may also include a user plane (CU-UP), which may be a logical node that hosts the user plane portion of the PDCP protocol and the SDAP protocol for the CU of access node 104.

[0048] DU 105 can be a logical node that hosts the Radio Link Control (RLC), Media Access Control (MAC), and / or Physical (PHY) layers of the NR protocol stack of access node 104. The operation of DU 105 can be controlled at least partially by CU 108. It should also be understood that the functional allocation between DU 105 and CU 108 can vary depending on the implementation.

[0049] Cloud computing systems can also be used to provide CU 108 and / or DU 105. CUs provided by cloud computing systems can be referred to as virtualized CUs (vCUs). In addition to vCUs, virtualized DUs (vDUs) provided by cloud computing systems can also exist. Furthermore, there can be a combination where DUs can be implemented on so-called bare-metal solutions, such as application-specific integrated circuits (ASICs) or customer-specific standard product (CSSP) system-on-chips (SoCs).

[0050] By leveraging Network Functions Virtualization (NFV) and Software-Defined Networking (SDN), edge cloud can be introduced into the radio access network. Using edge cloud can represent access node operations that should be performed at least partially in a computing system operatively coupled to the Remote Radio Header (RRH) or Radio Unit (RU) 103 of access node 104. Alternatively, access node operations can be performed on a distributed computing system or cloud computing system located at access node 104. The application of a cloud RAN architecture enables real-time RAN functions to be performed at the radio access network (e.g., in DU 105) and non-real-time functions to be performed in a centralized manner (e.g., in CU 108).

[0051] 5G (or New Radio) wireless communication networks can support multiple hierarchical structures, in which multiple access edge computing (MEC) servers can be placed between the core network 110 and the access node 104. It should be understood that MEC can also be applied to LTE wireless communication networks.

[0052] 5G wireless communication networks (“5G networks”) may also include non-terrestrial communication networks, such as satellite communication networks, to enhance or supplement the coverage of the 5G radio access network. For example, satellite communication can support data transmission between the 5G radio access network and the core network 110, thereby achieving wider network coverage. Possible use cases may include providing service continuity for machine-to-machine (M2M) or Internet of Things (IoT) devices or for passengers on board vehicles, or ensuring the service availability of critical communications and future rail, maritime, or air communications. Satellite communication may utilize geostationary orbit (GEO) satellite systems or low Earth orbit (LEO) satellite systems, such as mega-constellations (i.e., systems in which hundreds of (nano) satellites are deployed). Alternatively, satellites may be airborne equipment, such as unmanned aerial vehicles (UAVs) or high-altitude platform systems (HAPS). A given satellite 106 may provide communication services on Earth via one or more satellite beams. One or more satellite beams create one or more cells over a given service area that can be defined by the field of view of satellite 106.

[0053] It is clear to those skilled in the art that, Figure 1 The access node 104 shown is merely an example of a portion of the radio access network, and in practice, the radio access network may include multiple access nodes 104, UEs 100 and 102 may access multiple radio cells, and the radio access network may also include other devices, such as physical layer relay access nodes or other entities. At least one of the access nodes may be a home eNodeB or a home gNodeB. A home gNodeB or a home eNodeB is an access node that can be used to provide indoor coverage in a home, office, or other indoor environment.

[0054] Furthermore, within the geographical area of ​​the wireless access network, multiple different types of wireless cells and multiple wireless cells can be provided. Wireless cells can be macrocells (or umbrella cells), which can be large areas with diameters of up to tens of kilometers, or smaller cells, such as microcells, femtocells, or picocells. Figure 1 Multiple access nodes 104 can provide any type of these cells. A cellular wireless network can be implemented as a multi-layered access network comprising several types of wireless cells. In a multi-layered access network, one access node can provide one or more wireless cells, and therefore providing such a multi-layered access network may require multiple access nodes.

[0055] To meet the need for improved performance in wireless access networks, the concept of "plug-and-play" access nodes can be introduced. Besides the home eNodeB or home gNodeB, wireless access networks capable of using "plug-and-play" access nodes can also include home node B gateways, HNB-GWs (… Figure 1 (Not shown in the image). An HNB-GW, which can be installed within an operator's radio access network, can aggregate traffic from a large number of home eNodeBs or home gNodeBs back to the operator's core network 110.

[0056] 6G wireless communication networks are expected to employ flexible decentralized and / or distributed computing systems and architectures, along with ubiquitous computing, based on mobile edge computing, artificial intelligence, short packet communication, and blockchain technologies, to achieve local spectrum licensing, spectrum sharing, infrastructure sharing, and intelligent automated management. Key features of 6G may include intelligent interconnected management and control capabilities, programmability, integrated sensing and communication, reduced energy footprint, trusted infrastructure, scalability, and affordability. Furthermore, 6G targets new use cases, including integrating location and sensing capabilities into the system definition to unify the user experience in the physical and digital worlds.

[0057] It is expected that 7G (which will replace 5G and 6G technologies) will be able to meet the requirements of extremely high bandwidth, near-zero latency and universal integration.

[0058] However, the following uses the principles and terminology of 5G wireless access technology to describe some example embodiments, without limiting the example embodiments to 5G wireless access technology.

[0059] In 5G wireless systems, Radio Resource Management (RRM) relaxation can be used to reduce UE power consumption. RRM relaxation can involve less frequent measurements of neighboring cells. Idle / inactive mode UEs can perform relaxation measurements based on specific criteria. These criteria can include low mobility and / or not being at the cell edge. RRM relaxation criteria can be defined for UEs in connected mode and / or (e)RedCap UEs. The network can configure relaxation criteria independently, such as low mobility, not being at the cell edge, or both. If any criterion is met, relaxation measurements with longer intervals can be configured, for example, using a scaling factor. If both criteria are met, the UE can stop measurements for up to 1 hour. In the RRC_Connected state, RRM relaxation may result in handover failure. For neighboring cell RRM relaxation, stationary or inactive UEs can be considered to have higher priority than slightly mobile UEs.

[0060] The first indication received by the UE may be related to the network power saving (NES) mode, and the second indication received by the UE may be related to a correction factor, based on which the UE can evaluate the RRM slack standard. Whenever the network changes the NES state, the UE waits for at least one or two indications: the first indication for the NES state and / or the second indication for the correction factor. Therefore, from a signaling perspective, this can be inefficient.

[0061] The relaxation measurement criteria for low-mobility UEs can be satisfied when the following conditions are met:

[0062] - (Srxlev Ref -Srxlev) SearchDeltaP ,

[0063] in:

[0064] - Srxlev = the current Srxlev value (dB) of the serving cell.

[0065] - Srxlev Ref The reference Srxlev value (dB) for the serving cell is set as follows:

[0066] - After selecting or reselecting a new neighborhood, or

[0067] - If (Srxlev-Srxlev) Ref )>0, or

[0068] - If in T SearchDeltaP The internal relaxation measurement criteria are not met:

[0069] - UE should include Srxlev Ref ​The value is set to the current Srxlev value of the serving cell.

[0070] The relaxation measurement criteria for UEs not located at the cell edge can be satisfied under the following conditions:

[0071] - Srxlev>S SearchThresholdP ,as well as

[0072] - If S SearchThresholdQ If configured, then Squal>S SearchThresholdQ ,

[0073] in:

[0074] - Srxlev = the current Srxlev value (dB) of the serving cell.

[0075] - Squal = the current Squal value (dB) of the serving cell.

[0076] The relaxation measurement criterion for a static (e) RedCap UE is satisfied when the following conditions are met:

[0077] - (Srxlev RefStationary -Srxlev) SearchDeltaP-Stationary ,

[0078] in:

[0079] - Srxlev = the current Srxlev value (dB) of the serving cell.

[0080] - Srxlev RefStationary The reference Srxlev value (dB) for the serving cell is set as follows:

[0081] - After selecting or reselecting a new neighborhood, or

[0082] - If (Srxlev-Srxlev) RefStationary )>0, or

[0083] - If in T SearchDeltaP-Stationary The internal relaxation measurement criteria are not met:

[0084] - UE should include Srxlev RefStationary The value is set to the current Srxlev value of the serving cell.

[0085] The relaxation measurement criteria for stationary (e)RedCap UEs not located at the cell edge can be met under the following conditions:

[0086] - In T SearchDeltaP-Stationary During the specified period, the relaxed measurement criteria in Clause 5.2.4.9.3 were met, and​

[0087] - Srxlev>S SearchThresholdP2 ,and

[0088] - If S SearchThresholdQ2 If configured, then Squal>S SearchThresholdQ2 .

[0089] in:

[0090] - Srxlev = the current Srxlev value (dB) of the serving cell.

[0091] - Squal = the current Squal value (dB) of the serving cell.

[0092] The relaxation measurement criteria for a static (e) RedCap UE can be satisfied under the following conditions:

[0093] - (SS-RSRP RefStationaryConnected -SS-RSRP) SearchDeltaP-StationaryConnected ,

[0094] in:

[0095] - SS-RSRP = Current L3 RSRP measurement (dB) of PCell based on SSB.

[0096] - SS-RSRP RefStationaryConnected The PCell reference SS-RSRP value (dB) should be set as follows:

[0097] - At the end of the RRC reconfiguration process specified in 5.3.5.3, when rrm- MeasRelaxationReportingConfig Included RRCReconfiguration In the message; or

[0098] - When the static standard is configured, spCellConfig Applications in China reconfigurationWithSync Afterwards, after the MAC successfully completes the random access process; or

[0099] - When the static standard is configured, and the low-layer indicator CG handover without RACH or LTM cell handover is successfully completed, or

[0100] - If (SS-RSRP-SS-RSRP) RefStationaryConnected )>0; or

[0101] - If in T SearchDeltaP-StationaryConnected The internal relaxation measurement criteria are not met:

[0102] - The UE should include SS-RSRP RefStationaryConnected ​The value is set to the current SS-RSRP value of the serving cell.

[0103] SS-RSRP represents the received power of the synchronization signal reference signal.

[0104] RRM relaxation can be implemented using both stationary and non-cell edge standards. Due to the dynamic coverage characteristics of NES cells, even stationary UEs may not activate (deactivate) RRM relaxation as expected. From the UE's perspective, this can lead to inefficient relaxation. For example, when the gNB shuts down half of its antenna elements (e.g., using a massive MIMO mute algorithm) or reduces transmit power to enable NES mode, the UE may experience a sudden drop in RSRP (Reference Signal Received Power), thus meeting the traditional RRM relaxation standard, even if the UE is stationary and / or not located at the cell edge.

[0105] When serving cell relaxation is enabled in beam-based communications, the serving beam used for cell quality assessment may change due to NES activation or deactivation when the UE is in a relaxed state. This can lead to beam failure or radio link failure.

[0106] Prolonged slack periods (e.g., up to 1 hour) can negatively impact network performance, particularly for NES cells. This can lead to delayed handover, radio link failures, and ultimately affect UE throughput, potentially negating any network power savings achieved.

[0107] RRM relaxation can involve relaxing RRM measurements for the UE when network configuration conditions are met. The network can configure any relaxation configuration for the UE. A cell can change its "state" from "Non-NES" to "NES" or vice versa, during which the network can send a new RRM relaxation configuration for the UE. Simultaneously, the network can configure new RRM / RLM / BFD relaxation conditions that take into account the "NES state". For 6G, dynamic massive MIMO silence algorithms can make, for example, slot-level decisions to enable / disable specific NES modes. When the network implements such dynamic / frequent decision algorithms, sending a new relaxation configuration at each network decision can become costly, for example, in terms of signaling overhead.

[0108] Figure 2 The paper further illustrates the challenges associated with RRM relaxation and network energy-efficient cells. Figure 2 In the diagram, black rectangles represent active antennas, while white rectangles represent passive antennas.

[0109] In one embodiment, the RRM relaxation standard can be dynamically adjusted. Activation and deactivation of the NES mode can be considered. Therefore, RRM relaxation can be applied at appropriate times to optimize network performance and energy efficiency.

[0110] In one embodiment, the UE can be configured with multiple RRM relaxation standards or offsets. These may include (multiple) NES-aware RRM / RLM / BFD standards or offsets. When the UE receives a legacy synchronization signal block (SSB), it can use the legacy RRM standard. When the UE receives an SSB indicating an NES mode, it can switch to an NES-aware standard for RRM relaxation. The UE can indicate to the network device that the RRM relaxation assessment can be based on a selected NES mode-specific standard. If the network device decides to disable the selected NES state or NES mode, it can reject the RRM relaxation decision and request the UE to reassess after a specific timer expires.

[0111] One embodiment enables the provision of NES-aware RRM relaxation. A network device, such as a gNB, can send one or more RRM relaxation configurations associated with different NES modes to a user equipment (UE). This configuration can be a regular (traditional) relaxation configuration or an NES mode-specific configuration for each NES mode. In one embodiment, one or more offset values ​​to be added to the configurations for different NES modes can be provided by the network device. The network device can send a mapping defining the relationship between SSB transport patterns and corresponding NES modes. The SSB transport patterns can be associated with SSB periodicity, SSB transmission frequency, and / or time resources. The UE can switch between relaxation configurations or use offsets based on the cell's NES mode. The UE can determine which relaxation configuration or offset to use based on the received SSBs. The SSB can explicitly or implicitly indicate the NES mode.

[0112] In one embodiment, the UE can determine the NES mode based on an SSB received from the network device. The SSB can indicate a specific RRM relaxation configuration used by the UE. For example, the SSB can indicate that the NES mode is activated, and based on this indication, the UE can select an appropriate RRM relaxation evaluation criterion corresponding to the aforementioned NES mode. The SSB can explicitly indicate one or more RRM relaxation configurations. The SSB can indicate an index associated with a specific RRM relaxation configuration corresponding to the NES mode.

[0113] In one embodiment, the UE can determine the NES mode based on the SSB transport pattern. Each NES mode can have a NES mode-specific SSB transport pattern. For example, if the SSB is received by the UE periodically at X intervals, this may indicate that the NES mode is not activated, and the UE will use the conventional (traditional) RRM relaxation standard. If the UE observes the SSB periodically changing to Y intervals, this may indicate that the NES mode is activated, and the UE will apply a specific RRM relaxation standard or offset designed for the aforementioned NES mode.

[0114] In one embodiment, the UE may be instructed and / or configured with knowledge of which cells are in NES mode. For example, if the UE is in a connected state, the network device may indicate this to the UE when the NES mode changes. The UE can then determine the RRM slack configuration based on the indicated NES mode.

[0115] In one embodiment, the UE can apply different relaxation configurations or offsets to different cells based on the NES mode, instead of applying the same configuration to different cells.

[0116] In one embodiment, the UE can be configured with multiple RRM relaxation standards, including Network Energy Saving (NES) State Aware RRM, RLM, and / or BFD standards, or be configured with a single standard with an NES-specific offset that can be applied to a legacy RRM relaxation standard. When the UE receives a legacy SSB, it can use the legacy / regular RRM standard. When the UE receives an SSB indicating the NES state, the UE can switch to an NES-aware standard for RRM relaxation.

[0117] In one embodiment, in addition to the conventional RRM relaxation standard, the UE may be configured with one or more NES-aware RRM / RLM / BFD relaxation standards, including multiple different thresholds, offsets, and / or timers, to evaluate RRM relaxation when the cell is in NES mode. The network device may send one or more relaxation configurations to the UE. If a configuration is provided to the UE, one or more offset values ​​for different NES modes may be provided (to be used on top of the configuration values). The network device provides a normal (conventional) relaxation configuration and an NES mode-specific configuration for each NES mode. The network device may also send a mapping in the same message that defines the relationship between the SSB transport pattern and the corresponding NES mode. The SSB transport pattern may be associated with SSB periodicity, SSB transmission frequency, and / or time resources.

[0118] In one embodiment, the RRM relaxation standard can be applied to idle, inactive, and / or connected states. The RLM (Radio Link Management) relaxation standard and / or BFD (Beam Failure Detection) relaxation standard can be applied to connected states. Relaxation configuration can be provided using broadcast (system information) and / or dedicated (e.g., RRC reconfiguration or RRC release messages) signaling.

[0119] If the UE receives a conventional SSB, the UE can perform an SSB measurement. The UE can then determine whether the RRM, RLM, and / or BFD relaxation criteria are met based on the conventional / standard relaxation criteria.

[0120] In one embodiment, the UE may receive an SSB that explicitly or implicitly indicates an active / activated NES mode. The SSB may indicate a specific RRM slack configuration used by the UE. For example, the SSB may indicate that the NES mode is activated, and the UE may select the appropriate RRM slack evaluation criterion corresponding to the NES mode based on this indication. The SSB may also explicitly indicate an RRM slack configuration in one or more RRM slack configurations. The SSB may indicate an index associated with a specific RRM slack configuration corresponding to the active / activated NES mode. Each NES mode may also have a specific SSB transmission pattern, where the NES mode can be determined or indicated based on the SSB transmission pattern. For example, if the SSB arrives periodically at X, this may indicate that the NES mode is not activated, and the UE will use a regular RRM slack criterion. If the UE observes the SSB periodically changing to Y, this may indicate that the NES mode is activated, and the UE will apply a specific RRM slack criterion or offset designed for the NES mode.

[0121] In one embodiment, the UE can perform SSB measurements. The UE can switch between relaxed configurations (or use an offset) based on the received SSB. The UE can determine which configuration (or offset) to use based on the received SSB, as the SSB can explicitly or implicitly indicate an active / activated NES mode.

[0122] In one embodiment, the UE can switch to the NES-aware RRM relaxation standard. The UE can determine that the RRM, RLM, and / or BFD relaxation standards are not met based on the configured NES-aware standard. Then, the UE can continue with NES-aware RRM / RLM / BFD measurements.

[0123] In one embodiment, the UE may receive an SSB that explicitly or implicitly indicates an active / activated NES mode. The UE may then perform an SSB measurement. The UE may change between relaxation configurations based on the received SSB, or use an offset; that is, the UE may determine which configuration (or offset) to use based on the received SSB that explicitly or implicitly indicates the NES mode. The UE may switch to the NES-aware RRM relaxation standard.

[0124] In one embodiment, the UE can determine whether the NES-aware RRM / RLM / BFD relaxation criteria are met. If so, the UE can initiate NES-aware RRM / RLM / BFD relaxation.

[0125] In one embodiment, the UE may optionally report to the network device that the NES-aware RRM / RLM / BFD relaxation criteria have been met. This can be performed on the UE in connected mode. The UE may instruct the network device that the RRM relaxation assessment is based on a specific NES state criterion. If the network device decides to disable that specific NES state, the network device may reject the RRM relaxation decision and request the UE to perform a reassessment after a timer expires. The network device may allow and / or configure NES-aware RRM / RLM / BFD relaxation. The UE can then begin relaxing NES-aware RRM / RLM / BFD measurements.

[0126] In one embodiment, a relaxed NES-aware RRM measurement based on a relaxation criterion may include one or more of the following: RRM / RLM / BFD measurements may be performed entirely. RRM / RLM / BFD measurements may resume when the relaxation criterion is no longer met or the exit condition is met. RRM / RLM / BFD measurements may be relaxed in time and / or frequency until the relaxation criterion is no longer met or the exit condition is met. RRM / RLM / BFD relaxation may be performed according to conventional relaxation.

[0127] In one embodiment, the SSB may include additional bits indicating the NES mode, such as mode 1 (half the antenna can be muted), mode 2 (a quarter antenna can be muted), mode 3 (a 3dB power reduction can be applied), etc. Therefore, an NES-specific SSB configuration can be provided to the UE. For example, if the effect of mode 1 is a 3dB RSRP reduction, the UE can switch to another RRM relaxation standard, or select a 3dB offset within the active relaxation standard, etc.

[0128] In one embodiment, the relaxation measurement criteria configured by the NES cell for a UE with low mobility can be satisfied when the following conditions are met:

[0129] - (Srxlev Ref-NES -Srxlev) SearchDeltaP_NES ,

[0130] in:

[0131] - Srxlev = the current Srxlev value (dB) of the serving cell.

[0132] - Srxlev Ref-NES The reference Srxlev value (dB) for the serving cell is set as follows:

[0133] - After selecting or reselecting a new neighborhood, or

[0134] - If (Srxlev-Srxlev) Ref-NES )>0, or​

[0135] - If in T SearchDeltaP_NES The internal relaxation measurement criteria are not met:

[0136] - UE should include Srxlev Ref-NES The value is set to the current Srxlev value of the serving cell.

[0137] For example, NES cells can provide Srxlev based on the NES model. Ref-NES One or more values. For example, based on NES mode, Srxlev Ref-NES It can be better than traditional Srxlev Ref Small X dB. Reduce S SearchDeltaP_NES The value of may disable RRM relaxation, even if the SSB's received power changes very little. SearchDeltaP_NES The highest value may lead to RRM relaxation activation. In one embodiment, the network device may provide S based on NES mode. SearchDeltaP_NES A set of values. When a network device activates an NES mode that results in the greatest coverage loss, the network device can request the UE to switch to the lowest configuration S. SearchDeltaP_NES Therefore, network devices can enable (multiple) UEs to avoid activating RRM relaxation, thereby reducing the number of HOF, RLF, beam failures, etc. If the network device activates the NES mode with the least impact on coverage, the network device can request UEs to handover to remain in RRM relaxation most of the time, for example, using higher S... SearchDeltaP_NES This saves UE energy. In this case, the network device can be configured with T SearchDeltaP_NES The lower value.

[0138] In one embodiment, the relaxation measurement criterion configured by the NES cell for a UE not located at the cell edge can be satisfied when the following conditions are met:

[0139] - Srxlev>S SearchThresholdP_NES ,as well as

[0140] - If S SearchThresholdQ_NES If configured, then Squal>S SearchThresholdQ_NES ,

[0141] in:

[0142] - Srxlev = the current Srxlev value (dB) of the serving cell.

[0143] - Squal = the current Squal value (dB) of the serving cell.

[0144] For example, NES cells can provide S based on the NES mode. SearchThresholdP_NES or SSearchThresholdQ_NES One or more values ​​of S. Decrease S SearchThresholdP_NES The value of can also lead to the disabling of RRM relaxation, even if the UE is in the middle of the cell. S SearchThresholdP_NES The highest value can also lead to RRM relaxation activation, even if the UE is at the cell edge. In an embodiment, the network device can provide S based on NES mode. SearchThresholdP_NES A set of values. For example, when a network device activates the NES mode that results in the greatest coverage loss, the network device can request the UE to switch to a lower configuration S that takes coverage loss into account. SearchThresholdP_NES That is, the network device can request the UE not to enable RRM relaxation, but instead prioritize measurements to reduce radio link failures (RLF), beam failures (BF), and / or handover failures (HOF). If the network device activates the NES mode with the least impact on coverage, the network device can request the UE to switch to a higher-configured S... SearchThresholdP_NES That is, it remains in a relaxed RRM state most of the time, thereby saving UE energy.

[0145] If a single RRM relaxation configuration is provided, one or more offset values ​​can also be provided for different NES modes. These offset values ​​can be applied on top of the configuration values ​​and can depend on the specific NES state. For example, if NES mode 1 results in a 3dB RSRP degradation, a 3dB offset can be applied to the regular (traditional) relaxation standard. The offset value can be indicated within the SSB, or the UE can determine the offset value based on the SSB periodicity. For example, an SSB periodicity of X can correspond to a 0dB offset, and an SSB periodicity of Y can correspond to a 3dB offset, and so on.

[0146] In one embodiment, the relaxation measurement criterion for low-mobility UEs can be satisfied when the following conditions are met:

[0147] - (Srxlev Ref -Srxlev) SearchDeltaP -offset

[0148] in:

[0149] - Srxlev = the current Srxlev value (dB) of the serving cell.

[0150] - offset = the offset to apply, which depends on the specific NES state.

[0151] - Srxlev Ref The reference Srxlev value (dB) for the serving cell is set as follows:

[0152] - After selecting or reselecting a new neighborhood, or

[0153] ​- If (Srxlev-Srxlev) Ref )>0, or

[0154] - If in T SearchDeltaP The internal relaxation measurement criteria are not met:

[0155] - UE should include Srxlev Ref The value is set to the current Srxlev value of the serving cell.

[0156] In one embodiment, the relaxation measurement criterion for a UE not located at the cell edge can be satisfied when the following conditions are met:

[0157] - Srxlev>S SearchThresholdP -offset,

[0158] - If S SearchThresholdQ If configured, then Squal>S SearchThresholdQ -offset,

[0159] in:

[0160] - Srxlev = the current Srxlev value (dB) of the serving cell.

[0161] - Squal = the current Squal value (dB) of the serving cell.

[0162] - offset = the offset to be applied, which depends on the specific NES state.

[0163] Figure 3 A signal flow diagram according to an example embodiment is shown.

[0164] refer to Figure 3 Network device 104, which can be a RAN node 104 (such as a gNB or base station), can send one or more radio resource management relaxation configuration or offset values ​​to device 100 at 301. Device 100 can be a user device or a user equipment (UE). Device 100 can receive the sent relaxation configuration or offset values. The relaxation configuration or offset values ​​can also be pre-configured to device 100.

[0165] At 302, the network device may send a Synchronization Signal Block (SSB) to device 100, indicating the Radio Resource Management (RRM) slack configuration or offset value used by device 100. At 303, device 100 may receive the SSB. At 303, device 100 may determine the RRM slack configuration or offset value used by device 100 based on the SSB received from network device 104.

[0166] The radio resource management (RRM) relaxation configuration can be specific to either Network Energy Saving (NES) mode or non-NES mode. The RRM relaxation offset value can be an NES mode-specific offset value. The RRM relaxation configuration or offset value can be an NES-aware RRM relaxation configuration or offset value. The RRM relaxation configuration or offset value can be a non-NES-aware RRM relaxation configuration or offset value. The NES-aware RRM relaxation configuration or offset value can be associated with Network Energy Saving (NES) mode.

[0167] In one embodiment, the synchronization signal block may indicate the radio resource management slack configuration or offset value used by the device 100. The device 100 may select the radio resource management slack configuration or offset value indicated by the synchronization signal block.

[0168] In one embodiment, the synchronization signal block may indicate an active or inactive network power-saving mode. The device 100 can select an NES-aware radio resource management slack configuration or offset value corresponding to the active or inactive network power-saving mode.

[0169] In one embodiment, the synchronization signal block may indicate an index associated with a radio resource management slack configuration or offset value used by the device. Device 100 may select a radio resource management slack configuration or offset value based on the index.

[0170] Device 100 can perform a synchronization signal block measurement at 303 to determine the wireless resource management relaxation configuration or offset value used by device 100.

[0171] At 303, device 100 can evaluate the radio resource management relaxation criteria corresponding to the radio resource management relaxation configuration or offset value, determine whether radio resource management relaxation is allowed based on the evaluation, and start radio resource management relaxation when radio resource management relaxation is allowed.

[0172] At point 303, device 100 can evaluate the radio resource management relaxation criterion corresponding to the radio resource management relaxation configuration or offset value. When the radio resource management relaxation criterion is met, device 100 can send an indication to network device 104. Figure 3 (Not shown in the image). Upon receiving a response from network device 104 instructing network device 104 to allow slack in radio resource management ( Figure 3 When (not shown in the image), device 100 can begin wireless resource management relaxation.

[0173] Figure 4 A signal flow diagram according to an example embodiment is shown.

[0174] refer to Figure 4The first network device, gNB1, which can be a gNB or a base station, can send one or more radio resource management relaxation configuration or offset values ​​to device 100 at 401. Device 100 can receive the sent relaxation configuration or offset values. The relaxation configuration or offset values ​​can also be pre-configured to device 100.

[0175] At 402, the first network device can send a first synchronization signal block (SSB) to the device 100, indicating that the device 100 should use a radio resource management slack configuration or offset value for gNB1. A second network device, gNB2, which may be a gNB or a base station, can send a second synchronization signal block (SSB) to the device 100 at 403, indicating that the device 100 should use a second synchronization signal block (SSB) for radio resource management slack configuration or offset value for gNB2. At 303, the device 100 can determine the radio resource management slack configuration or offset value used by the device 100 based on the first and second synchronization signal blocks (SSBs) received from the network device 104. Therefore, the device can apply different slack configurations or offset values ​​to gNB1 and gNB2.

[0176] Figure 5 A signal flow diagram according to an example embodiment is shown.

[0177] In addition to conventional RRM relaxation standards, device 100 may also be configured with one or more NES-aware RRM / RLM / BFD relaxation standards. The relaxation standard may include multiple thresholds, multiple offsets, and multiple timers to evaluate RRM relaxation when the cell is in NES mode. Network device 104 may provide one or more relaxation configuration or offset values ​​to device 100 at 501.

[0178] If a configuration is provided, one or more offset values ​​for different NES modes can be provided (to be used above the configuration value). Alternatively, network device 104 can provide a normal relaxation configuration and an NES mode-specific configuration for each NES mode. Network device 104 can also provide a 501 mapping, which can define the relationship between SSB transport patterns and corresponding NES modes. SSB transport patterns can be associated with SSB periodicity, SSB transmission frequency, and / or time resources.

[0179] At point 502, network device 104 can send an SSB to device 100, which explicitly or implicitly indicates an active / activated NES mode. The device can receive the SSB at 502 and perform an SSB measurement at 503. Furthermore, at 503, device 100 can select an appropriate RRM relaxation evaluation criterion corresponding to the NES mode. At 504, device 100 can determine whether the RRM / RLM / BFD relaxation criteria are met based on the NES-aware relaxation criteria. If the RRM, RLM, and / or BFD relaxation criteria are not met, the device can continue with NES-aware RRM, RL, and / or BF measurements.

[0180] At 505, network device 104 may send an SSB to device 100. Device 100 may receive the SSB at 506. The SSB 505 may indicate a specific RRM slack configuration used by device 100. For example, the SSB may indicate that an NES mode is active, and device 100 may select the appropriate RRM slack evaluation criterion corresponding to the NES mode based on this indication. The SSB may also explicitly indicate one or more RRM slack configurations. The SSB may indicate an index associated with a specific RRM slack configuration corresponding to an active / activated NES mode. Device 100 may also determine the slack configuration or offset used based on the SSB transmission pattern, as each NES mode may have a specific SSB transmission pattern. For example, if an SSB is received at device 100 periodically with an X, this may indicate that the NES mode is not active, and device 100 will use a regular RRM slack criterion. If device 100 observes that SSB periodically changes to Y, this may indicate that NES mode is activated, and device 100 will apply an RRM relaxation criterion or offset specific to the aforementioned NES mode.

[0181] At 506, device 100 can perform an SSB measurement. The device can switch between relaxation configurations (or use an offset) based on the received SSB 505. The device can determine 506 which configuration or offset to use based on the received SSB, which can explicitly or implicitly indicate an active / active mode. The device can switch 506 to the NES-aware RRM relaxation criterion. The device can determine 507 whether the RRM / RLM / BFD relaxation criterion is met based on the NES-aware criterion.

[0182] If the NES-sensing RRM / RLM / BFD relaxation criterion is met at 507, the device 100 can initiate NES-sensing RRM / RLM / BFD relaxation at 510.

[0183] If it is determined at 507 that the NES-aware RRM / RLM / BFD relaxation criteria are met, device 100 may optionally report or indicate to network device 104 at 508 that the NES-aware RRM / RLM / BFD relaxation criteria are met. The device may instruct network device 104 at 508 that the RRM relaxation assessment is based on a specific NES state criterion. If network device 104 decides to disable a specific NES state, network device 104 may reject the RRM relaxation decision and request at 509 that device 100 perform a reassessment after a timer expires. Network device 104 may send a response to device 100 at 509, wherein network device 104 allows and / or configures NES-aware RRM / RLM / BFD relaxation, after which device 100 may begin NES-aware RRM / RLM / BFD relaxation at 510. Steps 508 and 509 may be performed on device 100 in connected mode.

[0184] Figure 6 This is a flowchart illustrating an exemplary method. (Reference) Figure 6 At 601, a device of user equipment 100 may receive a Synchronization Signal Block (SSB) from network device 104. At 602, device 100 may determine the Radio Resource Management (RRM) relaxation configuration or offset value used by device 100 based on the SSB received from network device 104. At 603, the device may determine whether the NES-aware relaxation criterion is met. If the NES-aware relaxation criterion is met, device 100 may begin NES-aware RRM / RLM / BFD relaxation at 605. If the NES-aware relaxation criterion is not met, device 100 may continue SSB measurement at 604.

[0185] Figure 7 This is a flowchart illustrating an exemplary method. (Reference) Figure 7 The device 104, which may be a network device (such as a base station or gNB), may send a synchronization signal block SSB 302 at 701 to the device 100, which may be a user equipment, indicating the radio resource management relaxation configuration or offset value used by the device 100.

[0186] In one embodiment, device 100 may determine, based on the transmission pattern of synchronization signal block SSB 302 received from network device 104, the radio resource management slack configuration or offset value used by device 100, 303, 602. Device 100 may then apply the radio resource management slack configuration or offset value based on this determination, 303.

[0187] In one embodiment, the radio resource management (RRM) slack configuration or offset value may be associated with a network power saving (NES) mode. The RRM slack configuration or offset value may be a non-NES-aware RRM slack configuration or offset value. The transmission pattern of synchronization signal block 302 may be network power saving mode specific.

[0188] In one embodiment, device 100 may select a 303, 602 radio resource management slack configuration or offset value based on periodicity indicated by synchronization signal block 302. Periodicity may indicate an inactive network power-saving mode.

[0189] In one embodiment, device 100 may select a 303, 602 radio resource management slack configuration or offset value based on periodicity indicated by synchronization signal block 302. Periodicity may indicate activation of a network power-saving mode.

[0190] In one embodiment, network device 104 may send synchronization signal blocks SSB 302 with transmission patterns 302, 701 to device 100, the transmission patterns indicating the wireless resource management slack configuration or offset value used by device 100.

[0191] In one embodiment, device 100 may determine, based on information about the network energy-saving NES mode of the cell, 303, 602 the slack configuration or offset value used by the device.

[0192] In one embodiment, the relaxation configuration or offset value may be associated with wireless resource management relaxation, wireless link management relaxation, or beam fault detection relaxation.

[0193] In one embodiment, the offset value can be an RSRP offset, an RSRQ (Reference Signal Received Quality) offset, or an RSSI (Received Signal Strength Indicator) offset. In one embodiment, the offset value can be an integer or a decimal. In one embodiment, the offset value can be represented by + / - dB.

[0194] In one embodiment, information about the network energy-saving mode of the community can be received by device 100 from network device 104 (303, 601).

[0195] In one embodiment, device 100 may receive information 303, 601 regarding the network energy-saving (NES) mode of the cell in the synchronization signal block (SSB), system information (SIBx), and / or dedicated signaling. The dedicated signaling may include an RRC release message for idle / inactive mode and / or an RRC reconfiguration message for connected mode.

[0196] In one embodiment, the device 100 may receive information 303, 601 regarding the network energy-saving NES mode of the cell in the SSB transmission pattern, wherein periodicity may indicate NES mode or non-NES mode.

[0197] In one embodiment, network device 104 may send information 302, 701 about the network energy saving (NES) mode of the cell to device 100.

[0198] Figure 8 This is a flowchart illustrating an exemplary method. (Reference) Figure 8 At point 801, a device of user equipment 100 may maintain or receive information regarding radio resource management relaxation evaluation criteria or offset values. Each radio resource management relaxation evaluation criterion or offset value may be a network power saving NES-aware radio resource management relaxation evaluation criterion or offset value, or it may be a non-NES-aware radio resource management relaxation evaluation criterion or offset value. Each NES-aware radio resource management relaxation evaluation criterion or offset value may be specific to a network power saving NES mode.

[0199] In one embodiment, at 802, device 100 may receive an indication from network device 104 regarding the activation of NES mode. Based on this indication, device 100 may determine, 803, the radio resource management relaxation evaluation criterion or offset value used by device 100, or estimate, 804, the radio resource management relaxation evaluation criterion or offset value used by device 100, or send an 805 request message to network device 104 requesting network device 104 to send a radio resource management relaxation evaluation criterion or offset value for NES mode.

[0200] In one embodiment, when a radio resource management relaxation criterion or offset value specific to the NES mode is not available in the information, device 100 may estimate the radio resource management relaxation criterion for the NES mode.

[0201] In one embodiment, when the NES-specific Radio Resource Management Relaxation Evaluation Criterion or Offset is not available in the information and when the device 100 cannot estimate the NES-specific Radio Resource Management Relaxation Evaluation Criterion or Offset, the device 100 may send an 805 request message to the network device 104, which requests the network device 104 to send the NES-specific Radio Resource Management Relaxation Evaluation Criterion.

[0202] In one embodiment, device 100 may evaluate 806 a radio resource management (RRM) relaxation criterion or offset value, and determine, based on the evaluation, whether RRM relaxation is permitted. If RRM relaxation is permitted, device 100 may initiate RRM relaxation 807. If device 100 determines that the RRM relaxation criterion is not met, the device may decide 808 not to apply the relaxation measurement and continue re-evaluation.

[0203] In one embodiment, network device 104 may send information 302, 701 to user equipment regarding radio resource management (RRM) relaxation evaluation criteria or offset values. Each RRM relaxation evaluation criterion or offset value may be a network energy-saving (NES)-aware RRM relaxation evaluation criterion or offset value, or it may be a non-NES-aware RRM relaxation evaluation criterion or offset value. Each NES-aware RRM relaxation evaluation criterion or offset value may be specific to a network energy-saving (NES) mode.

[0204] In one embodiment, device 100 may receive an evaluation criterion at 801 and look up a table for each NES mode used for NES BS RRM relaxation evaluation. When network device 104 activates an NES mode for serving and / or neighboring base stations, device 100 can determine the NES-aware RRM relaxation criterion at 803 from the lookup table. For example, NES mode 1 may be activated, and device 100 may apply an offset of 3 dB at 806 to the active / activated relaxation criterion. At 806, device 100 may apply the NES-aware RRM relaxation criterion to identify whether to relax RRM measurements. Device 100 may continue (re)evaluating the NES-aware RRM relaxation criterion. If device 100 receives a new NES mode indication at 802, device 100 may restart the evaluation process. If the RRM relaxation criterion specific to the active / activated NES mode is not available in the lookup table, and device 100 is capable of estimating a new evaluation criterion, device 100 can begin estimating the NES-aware offset to be applied (804), for example, using the measured RSRP or the last received path loss estimate relative to the current SSB / WUS (Wake-up Signal). If device 100 cannot estimate the criterion or offset, device 100 can request assistance (805), i.e., request the network device to send the relaxation configuration parameters for the new NES mode. Device 100 can save the received relaxation configuration (801) in a lookup table for future use.

[0205] In one embodiment, a system is provided that includes at least one processor and at least one memory storing instructions, which, when executed by the at least one processor, cause the system to perform any method steps.

[0206] The above has been approved. Figures 2 to 8The described boxes, related functions, and information exchanges (messages) are not in an absolute chronological order, and some of them may occur simultaneously or in a different order than described. Other functions may also be executed between or within them, and other information may be sent, and / or other rules may be applied. Some boxes or portions of boxes, or one or more messages, may also be omitted or replaced with the corresponding boxes or portions of boxes, or one or more messages.

[0207] As used herein, “at least one of the following: ” and “at least one of ” and similar wording (where the list of two or more elements is connected by “and” or “or”) means at least any one of these elements, or at least any two or more of these elements, or at least all of these elements.

[0208] As used herein, the terms “at least one” and “one or more” mean “any one of at least one” or “any one of one or more”, respectively.

[0209] Figure 9 An example of apparatus 9800 is shown, which includes components for causing apparatus 9800 to perform one or more of the example embodiments described above. For example, apparatus 9800 may be an apparatus such as user device 100, terminal device, or user equipment, or an apparatus that includes user device 100, terminal device, or user equipment, or an apparatus included in user device 100, terminal device, or user equipment. For example, apparatus 9800 may be an apparatus such as network device 104 of a wireless access network (such as a network node, access node, gNB, or base station), or an apparatus that includes network device 104 of a wireless access network (such as a network node, access node, gNB, or base station), or an apparatus included in network device 104 of a wireless access network (such as a network node, access node, gNB, or base station).

[0210] Apparatus 9800 may include, for example, a circuit system or chipset suitable for implementing one or more of the example embodiments described above. Apparatus 9800 may be an electronic device including one or more electronic circuit systems. Apparatus 9800 may include a communication control circuit system 9810 (such as at least one processor) and at least one memory 9820 storing instructions 9822, which, when executed by at least one processor, cause apparatus 9800 to perform one or more of the example embodiments described above. For example, such instructions 9822 may include computer program code (software). At least one processor and at least one memory storing instructions may provide components for providing or causing execution of any of the methods and / or blocks described above.

[0211] A processor is coupled to memory 9820. The processor is configured to read data from memory 9820 and write data to memory 9820. Memory 9820 may include one or more memory cells. Memory cells may be volatile or non-volatile. It should be noted that one or more non-volatile memory cells and one or more volatile memory cells may be present, or alternatively, one or more non-volatile memory cells may be present, or alternatively, one or more volatile memory cells may be present. Volatile memory may be, for example, random access memory (RAM), dynamic random access memory (DRAM), or synchronous dynamic random access memory (SDRAM). Non-volatile memory may be, for example, read-only memory (ROM), programmable read-only memory (PROM), electrically erasable programmable read-only memory (EEPROM), flash memory, optical storage device, or magnetic storage device. Generally, memory may be referred to as a non-transitory computer-readable medium. The term "non-transitory" as used herein is a limitation on the medium itself (i.e., tangible, not tactile), rather than a limitation on the persistence of data storage (e.g., RAM and ROM). Memory 9820 stores computer-readable instructions that are executed by the processor. For example, non-volatile memory stores computer-readable instructions, while the processor uses volatile memory that temporarily stores data and / or instructions to execute instructions.

[0212] The computer-readable instructions may have been pre-stored in memory 9820, or alternatively or additionally, they may be received by the device via an electromagnetic carrier signal, and / or copied from a physical entity such as a computer program product. Execution of the computer-readable instructions causes device 9800 to perform one or more of the functions described above.

[0213] The memory 9820 can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and / or removable memory. The memory may include a configuration database for storing configuration data, such as a current list of neighboring cells, and, in some example embodiments, the structure of frames used in detected neighboring cells.

[0214] Device 9800 may also include or be connected to communication interface 9830, such as a wireless unit, which includes hardware and / or software for establishing a communication connection with one or more wireless communication devices according to one or more communication protocols. Communication interface 9830 includes at least one transmitter (Tx) and at least one receiver (Rx), which may be integrated into device 9800 or connected to it. Communication interface 9830 may provide components for performing some of the blocks and / or functions (e.g., transmitting and receiving) of one or more of the above-described example embodiments. Communication interface 9830 may include one or more components controlled by a corresponding control unit, such as a power amplifier, digital front end (DFE), analog-to-digital converter (ADC), digital-to-analog converter (DAC), frequency converter, modulator (demodulator), and / or encoder / decoder circuitry.

[0215] Communication interface 9830 provides the device with wireless communication capabilities to communicate in a wireless communication network. For example, the communication interface may provide a wireless interface to one or more UEs 100, 102, or (multiple) network devices 104. Device 9800 may also include or be connected to another interface toward core network 110, such as a network coordinator device or AMF, and / or include or be connected to other access nodes of the wireless communication network.

[0216] The device 9800 may also include a scheduler 9840 configured to allocate radio resources. The scheduler 9840 may be configured together with the communication control circuitry system 9810 or separately.

[0217] It should be noted that device 9800 may also include Figure 9 Various components are not shown. These various components can be hardware components and / or software components.

[0218] As explained above and repeated below, this disclosure includes, but is not limited to, the following example implementations.

[0219] Clause 1. An apparatus comprising at least one processor and at least one memory storing instructions, the instructions, when executed by the at least one processor, causing the apparatus to at least: determine a radio resource management slack configuration or offset value to be used by the apparatus based on a synchronization signal block (SSB) received from a network device.

[0220] Clause 2. The apparatus according to Clause 1, wherein: the wireless resource management relaxation configuration is a network power saving NES mode or non-NES mode specific configuration.

[0221] Clause 3. The apparatus according to Clause 1, wherein: the radio resource management relaxation offset is an NES mode-specific offset.

[0222] Clause 4. The apparatus according to Clause 1, wherein: the radio resource management relaxation configuration or offset value is an NES-aware radio resource management relaxation configuration or offset value, or the radio resource management relaxation configuration or offset value is a non-NES-aware radio resource management relaxation configuration or offset value.

[0223] Clause 5. The apparatus according to Clause 1, wherein: the NES-aware radio resource management relaxation configuration or offset value is associated with a network power-saving NES mode.

[0224] Clause 6. An apparatus according to any one of the preceding clauses, wherein: the synchronization signal block indicates the radio resource management slack configuration or offset value to be used by the apparatus; wherein the apparatus is configured to: select the radio resource management slack configuration or offset value indicated by the synchronization signal block.

[0225] Clause 7. The apparatus according to any one of the preceding clauses, wherein: the synchronization signal block indicates an active or inactive network power saving mode; wherein the apparatus is configured to: select an NES-aware radio resource management slack configuration or offset value corresponding to the active or inactive network power saving mode.

[0226] Clause 8. The apparatus according to any one of the preceding clauses, wherein: the synchronization signal block indicates an index associated with the radio resource management slack configuration or offset value to be used by the apparatus; wherein the apparatus is configured to select the radio resource management slack configuration or offset value based on the index.

[0227] Clause 9. The apparatus according to any one of the preceding clauses is made to: perform a synchronization signal block measurement to determine the radio resource management slack configuration or offset value to be used by the apparatus.

[0228] Clause 10. The apparatus according to any one of the preceding clauses is configured to: evaluate a radio resource management relaxation criterion corresponding to the radio resource management relaxation configuration or offset value; determine, based on the evaluation, whether radio resource management relaxation is permitted; and, if radio resource management relaxation is permitted, initiate the radio resource management relaxation.

[0229] Clause 11. The apparatus according to any one of the preceding clauses is configured to: evaluate a radio resource management slack criterion corresponding to the radio resource management slack configuration or offset value; and, when the radio resource management slack criterion is satisfied, send an indication to the network device.

[0230] Clause 12. The apparatus according to Clause 11 is configured to: initiate the radio resource management relaxation upon receiving a response from the network device instructing the network device to allow the radio resource management relaxation.

[0231] Clause 13. The device pursuant to any of the preceding clauses, wherein the device is a user equipment.

[0232] Clause 14. A network device comprising at least one processor and at least one memory storing instructions, the instructions, when executed by the at least one processor, causing the network device to at least: send a synchronization signal block (SSB) to a user equipment indicating a radio resource management slack configuration or offset value to be used by the user equipment.

[0233] Clause 15. A method comprising: determining, by means of means, a radio resource management slack configuration or offset value to be used by the means based on a synchronization signal block (SSB) received from a network device.

[0234] Clause 16. A method comprising: sending a synchronization signal block (SSB) from a network device to a user equipment indicating a radio resource management slack configuration or offset value to be used by the user equipment.

[0235] Clause 17. A non-transitory computer-readable medium comprising instructions that, when executed by a means, cause the means to at least: determine a radio resource management slack configuration or offset value to be used by the user equipment based on a synchronization signal block (SSB) received from a network device.

[0236] Clause 18. A non-transitory computer-readable medium comprising instructions that, when executed by a network device, cause the network device to at least: send a synchronization signal block (SSB) to a user equipment indicating a radio resource management slack configuration or offset value to be used by the user equipment.

[0237] As used in this application, the term "circuit system" may refer to one or more or all of the following: a) a purely hardware circuit implementation (such as implementations in analog, digital and / or quantum circuit systems); and b) a combination of (multiple) hardware circuits and software, such as (if applicable): i) a combination of (multiple) analog, digital and / or quantum hardware circuits with software / firmware, and ii) any or all portions of (multiple) hardware processors (including (multiple) digital and / or quantum processors) and (multiple) memories having software, which work together to enable a device (such as a mobile device, computing device or server) to perform various functions; and c) any or all portions of (multiple) hardware circuits, such as (multiple) microprocessors, (multiple) processors and / or (multiple) quantum processors, which require software (e.g., firmware) to operate, but may be absent when not required to operate.

[0238] This definition of circuit system applies to all uses of the term in this application, including in any claim. As another example, as used in this application, the term circuit system also covers only the implementation of hardware circuitry or a processor (or processors) or a portion of hardware circuitry or processing and its accompanying software and / or firmware. For example, if applicable to a particular claim element, the term circuit system also covers baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or network devices.

[0239] The techniques and methods described herein can be implemented in various ways. For example, these techniques can be implemented in hardware (one or more devices), firmware (one or more devices), software (one or more modules), or a combination thereof. For hardware implementation, the apparatus(s) of the example embodiments can be implemented within one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), graphics processing units (GPUs), processors, controllers, microcontrollers, microprocessors, other electronic units designed to perform the functions described herein, or a combination thereof. For firmware or software, implementation can be achieved by modules (e.g., processes, functions, etc.) of at least one chipset that perform the functions described herein. Software code can be stored in memory cells and executed by a processor. Memory cells can be implemented within the processor or external to the processor. In the latter case, as is known in the art, memory cells can be communicatively coupled to the processor in various ways. Furthermore, those skilled in the art will understand that the components of the systems described herein can be rearranged and / or supplemented by additional components to facilitate the implementation of the various aspects described, etc., and they are not limited to the precise configurations illustrated in the given figures.

[0240] Those skilled in the art will understand that, with advancements in technology, the proposed concepts can be implemented in various ways within the scope of the claims. Embodiments are not limited to the exemplary embodiments described above, but can vary within the scope of the claims. Therefore, all words and expressions should be interpreted broadly, and they are intended to illustrate rather than limit the embodiments.

Claims

1. An apparatus for communication, comprising at least one processor and at least one memory storing instructions, wherein the instructions, when executed by said at least one processor, cause the apparatus to at least: Based on the synchronization signal block (SSB) received from the network device, a wireless resource management relaxation configuration or offset value to be used by the device is determined.

2. The apparatus according to claim 1, wherein: The aforementioned relaxed configuration for wireless resource management is a specific configuration for either network energy-saving NES mode or non-NES mode; and The radio resource management relaxation offset value is an NES mode-specific offset value.

3. The apparatus according to claim 1, wherein: The radio resource management relaxation configuration or offset value is an NES-aware radio resource management relaxation configuration or offset value, or The radio resource management relaxation configuration or offset value is a non-NES-aware radio resource management relaxation configuration or offset value.

4. The apparatus according to claim 1, wherein: The NES-aware radio resource management relaxation configuration or offset value is associated with the network power saving NES mode.

5. The apparatus according to any one of claims 1 to 4, wherein: The synchronization signal block indicates the radio resource management slack configuration or offset value to be used by the device, wherein the device is configured to: select the radio resource management slack configuration or offset value indicated by the synchronization signal block; The synchronization signal block indicates an active or inactive network power-saving mode, wherein the device is configured to: select an NES-aware radio resource management slack configuration or offset value corresponding to the active or inactive network power-saving mode; or The synchronization signal block indicates an index associated with the radio resource management slack configuration or offset value to be used by the device, wherein the device is configured to select the radio resource management slack configuration or offset value based on the index.

6. The apparatus according to any one of claims 1 to 4, wherein: Perform synchronization signal block measurements to determine the wireless resource management relaxation configuration or offset value to be used by the device; as well as Evaluate the radio resource management relaxation criteria corresponding to the aforementioned radio resource management relaxation configuration or offset value; The assessment will determine whether wireless resource management slack is permitted. The radio resource management relaxation begins when it is permitted.

7. The apparatus according to any one of claims 1 to 4, wherein: Evaluate the radio resource management relaxation criteria corresponding to the aforementioned radio resource management relaxation configuration or offset value; When the wireless resource management relaxation criterion is met, an indication is sent to the network device; as well as The radio resource management relaxation begins when a response instructing the network device to allow the radio resource management relaxation is received from the network device.

8. A network device comprising at least one processor and at least one memory storing instructions, the instructions, when executed by the at least one processor, causing the network device to at least: Send a synchronization signal block (SSB) to the user equipment indicating the radio resource management relaxation configuration or offset value to be used by the user equipment.

9. A method for communication, comprising: The device determines the wireless resource management slack configuration or offset value to be used by the device based on the synchronization signal block (SSB) received from the network device.

10. A method for communication, comprising: The network device sends a synchronization signal block (SSB) to the user equipment indicating the radio resource management relaxation configuration or offset value to be used by the user equipment.

Images