Reducing energy consumption in wireless communication systems

Abstract

Aspects of the present disclosure relate to reducing energy consumption in a wireless communication system. For example, a network entity may perform operations to determine a state of a UE associated with the network entity, and reduce or modify DL transmissions to a UE, such as a UE in an RRC idle state, based on a response received from the UE. A UE may assist a network entity by evaluating a geographic area associated with the network entity and providing information about UEs in the area.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Patent Application No. 63 / 376,921, filed on September 23, 2022, entitled “REDUCING ENERGY CONSUMPTION FOR AWIRELESS COMMUNICATIONS SYSTEM,” the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present disclosure relates to wireless communications and, more particularly, to reducing energy consumption of components that facilitate wireless communications. Background Art

[0004] A wireless communication system may include one or more network communication devices (such as base stations), which may be referred to as eNodeB (eNB), next generation NodeB (gNB) or other suitable terms. Each network communication device (such as a base station) may support wireless communication of one or more user communication devices, which may also be referred to as user equipment (UE) or other suitable terms. A wireless communication system may support wireless communication with one or more user communication devices by utilizing resources of a wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)). In addition, a wireless communication system may support wireless communication across various radio access technologies, including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, and other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)).

[0005] While the adoption of 5G and technologies beyond 5G enables wireless communication systems to provide enhanced services at high data rates, these enhanced services generally rely on denser networks, such as networks with an increasing number of cell sites and / or antennas, greater bandwidth, additional frequency bands, etc. In addition, as the number of devices and services increases, the potential environmental impact and operating costs due to device emissions and energy consumption may also increase, as well as other unexpected disadvantages. Summary of the invention

[0006] The present disclosure relates to methods, apparatus and systems that support reducing energy consumption in a wireless communication system by selectively reducing or modifying transmissions from network entities (eg, base stations or cells) and UEs served by the network entities.

[0007] Some implementations of the methods and apparatus described herein may also include a UE having a processor and a memory coupled to the processor, the processor being configured to receive a query message from a network entity; determine, in response to the query message, whether one or more neighboring network entities are available to provide normal services to the UE; and send a message to the network entity when no neighboring network entity is available to provide normal services to the UE.

[0008] In some implementations of the methods and apparatus described herein, the UE receives the query message via a short message on a physical downlink control channel (PDCCH) using a paging radio network temporary identifier (P-RNTI).

[0009] In some implementations of the methods and apparatus described herein, the UE receives the query message via a radio resource control (RRC) paging message.

[0010] In some implementations of the methods and apparatus described herein, the UE operates in an RRC idle state.

[0011] In some implementations of the methods and apparatus described herein, the UE operates in an RRC inactive state.

[0012] In some implementations of the methods and apparatus described herein, a UE determines whether one or more neighboring network entities are available to provide normal service to the UE by: performing intra-frequency measurements or inter-frequency measurements on the one or more neighboring network entities; and determining whether the intra-frequency measurements or inter-frequency measurements satisfy one or more cell reselection criteria.

[0013] In some implementations of the methods and apparatus described herein, a UE determines whether one or more neighboring network entities meet: the S criteria, new radio (NR) inter-frequency and inter-RAT (radio access technology) cell reselection criteria, or intra-frequency and equal-priority inter-frequency cell reselection criteria based on intra-frequency measurements or inter-frequency measurements.

[0014] In some implementations of the methods and apparatus described herein, when the UE determines that the network entity is the UE's sole serving cell based on measurements performed indicating that none of the one or more neighboring network entities meets cell reselection criteria for the UE, the UE sends a message to the network entity.

[0015] In some implementations of the methods and apparatus described herein, the UE sends a message to the network entity when the UE determines that the network entity is the only available serving cell for the UE based on determining that none of the one or more neighboring network entities is a suitable serving cell for the UE.

[0016] Some implementations of the methods and apparatus described herein may also include a method performed by a UE, the method comprising: receiving a query message from a network entity; determining, in response to the query message, whether one or more neighboring network entities are available to provide normal services to the UE; and sending a message to the network entity when no neighboring network entity is available to provide normal services to the UE.

[0017] Some implementations of the methods and apparatus described herein may also include a network entity having a processor and a memory coupled to the processor, the processor being configured to send a query message to one or more UEs; receive a response message from the one or more UEs, the response message indicating for each UE whether the UE can select a neighboring network entity as a serving cell; and modify downlink (DL) transmission to the one or more UEs based on the number of response messages received from the one or more UEs.

[0018] In some implementations of the methods and apparatus described herein, the network entity sends the query message via a short message on the PDCCH using the P-RNTI.

[0019] In some implementations of the methods and apparatus described herein, the network entity sends the query message via an RRC paging message.

[0020] In some implementations of the methods and apparatus described herein, a network entity sends a query message to at least one UE operating in an RRC idle state.

[0021] In some implementations of the methods and apparatus described herein, a network entity sends a query message to at least one UE operating in an RRC inactive state.

[0022] In some implementations of the methods and apparatus described herein, a network entity modifies DL transmissions by reducing synchronization signal block (SSB), master information block (MIB) transmissions, or system information transmissions.

[0023] In some implementations of the methods and apparatus described herein, a network entity modifies the periodicity of uplink (UL) reception from one or more UEs.

[0024] In some implementations of the methods and apparatus described herein, prior to modifying the DL transmission, the network entity sends an idle mobility command to one or more UEs, the idle mobility command requesting any UE in an RRC idle state to perform an RRC idle state mobility procedure.

[0025] In some implementations of the methods and apparatus described herein, the network entity modifies the DL transmission by selecting a DL transmission modification type based on a number of response messages received from one or more UEs being within a number range associated with the DL transmission modification type.

[0026] In some implementations of the methods and apparatus described herein, a network entity modifies a DL transmission by: not performing DL transmission when the number of response messages received from one or more UEs is zero; performing sparse DL transmission when the number of response messages received from one or more UEs is within a first number range; performing reduced DL transmission when the number of response messages received from one or more UEs is within a second number range; and / or performing peak DL transmission when the number of response messages received from one or more UEs is higher than a peak service response number.

[0027] Some implementations of the methods and apparatus described herein may also include a method performed by a network entity, the method comprising sending a query message to one or more user equipment (UE); receiving a response message from the one or more UEs, the response message indicating, for each UE, whether the UE can select a neighboring network entity as a serving cell; and modifying downlink (DL) transmission to the one or more UEs based on a number of response messages received from the one or more UEs. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Figure 1 An example of a wireless communication system that supports reducing energy consumption during wireless communication in accordance with aspects of the present disclosure is illustrated.

[0029] Figure 2 An example of a diagram is illustrated that supports messaging between a network entity and one or more UEs in accordance with aspects of the present disclosure.

[0030] Figure 3 An example of a graph supporting selection of communication periodicity according to aspects of the present disclosure is illustrated.

[0031] Figure 4 An example of a map that supports provisioning of neighboring cells into energy saving slots according to aspects of the present disclosure is illustrated.

[0032] Figure 5 An example of a block diagram of a device supporting reduced energy consumption during wireless communications in accordance with aspects of the present disclosure is illustrated.

[0033] Figure 6 A flow chart is illustrated of a method for a support network entity to determine an RRC state of a UE in a coverage area according to aspects of the present disclosure.

[0034] Figure 7 A flow chart of a method for supporting a UE to evaluate a coverage area of ​​a network entity according to aspects of the present disclosure is illustrated. DETAILED DESCRIPTION

[0035] Network communication systems such as those providing 5G or other enhanced radio access technologies may inadvertently impact geographic areas due to the number of devices providing enhanced services (e.g., services with high data rates) and / or the amount of network bandwidth used when providing such services. For example, while the use of additional devices and higher data rates may result in a more energy-efficient network, the emissions associated with providing these enhanced services may adversely affect the geographic areas served.

[0036] To mitigate such disadvantages, a network communication system may implement and / or follow a network energy consumption model that seeks to optimize the operation of different components of the network (such as base stations and other network entities). Such a model can balance the deployment of equipment and the reduction of energy consumption by modifying equipment operation in a targeted and selective manner.

[0037] For example, a geographic area is usually in a low load or medium load situation, where the number of UEs served by a network entity (e.g., a cell) is relatively small compared to peak times. In addition, a network cell may be associated with many UEs at a given time, but the number of UEs in a connected state (e.g., an RRC connected state) is relatively small compared to other UE RRC states (e.g., an RRC idle and / or an RRC inactive state).

[0038] Therefore, the network may perform operations based on the RRC state of the UE associated with the cell to save or reduce energy consumption of the cell or other network entities. For example, the network may reduce certain access channel transmissions and other DL transmissions of UEs in the RRC connected state, and / or perform handover operations to move these UEs to other cells, such as when there are no longer UEs served by the cell in the RRC connected state.

[0039] The network entity may perform operations to determine the state of a UE associated with the network entity to reduce DL transmissions to the UE, such as a UE in an RRC idle state. The UE may assist the network entity by evaluating a geographic area associated with the network entity and providing information about UEs in the area.

[0040] Thus, by providing state information of associated UEs to network entities, the network can minimize or prevent service interruption to UEs in RRC idle state, while also reducing DL transmissions to these UEs in idle and / or inactive states (e.g., not in connected state). In doing so, the network can reduce energy consumed by continuous and / or unnecessary transmissions between devices (e.g., between a cell and its associated UEs) with no or minimal impact on the services provided to the UEs, among other benefits.

[0041] Aspects of the present disclosure are described in the context of a wireless communication system. Aspects of the present disclosure are further illustrated and described with reference to device diagrams and flow charts.

[0042] Figure 1 An example of a wireless communication system 100 that supports reducing energy consumption during wireless communication according to various aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 102, one or more UEs 104, a core network 106, and a packet data network 108. The wireless communication system 100 may support various radio access technologies. In some implementations, the wireless communication system 100 may be a 4G network, such as an LTE network or an advanced LTE (LTE-A) network. In some other implementations, the wireless communication system 100 may be a 5G network, such as an NR network. In other implementations, the wireless communication system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technologies, including the Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communication system 100 may support radio access technologies other than 5G. In addition, the wireless communication system 100 may support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).

[0043] One or more network entities 102 may be dispersed throughout a geographic area to form a wireless communication system 100. One or more of the network entities 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a radio access network (RAN), a base transceiver station, an access point, a NodeB, an eNodeB (eNB), a next generation NodeB (gNB), or other suitable terms. The network entity 102 and the UE 104 may communicate via a communication link 110, which may be a wireless or wired connection. For example, the network entity 102 and the UE 104 may perform wireless communication (e.g., receive signaling, send signaling) over a Uu interface.

[0044] The network entity 102 may provide a geographic coverage area 112 for which the network entity 102 supports services (e.g., voice, video, packet data, messaging, broadcast, etc.) for one or more UEs 104 within the geographic coverage area 112. For example, the network entity 102 and the UE 104 may support wireless communications of signals associated with services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or more radio access technologies. In some implementations, the network entity 102 may be mobile, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but different geographic coverage areas 112 may be associated with different network entities 102. The information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0045] One or more UEs 104 may be dispersed throughout the geographic area of ​​the wireless communication system 100. UE 104 may include or may be referred to as a mobile device, a wireless device, a remote device, a remote unit, a handheld device, a subscriber device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, a station, a terminal, or a client, etc. Additionally or alternatively, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc. In some implementations, UE 104 may be stationary in the wireless communication system 100. In some other implementations, UE 104 may be mobile in the wireless communication system 100.

[0046] One or more UEs 104 may be devices of different forms or with different capabilities. Figure 1 Some examples of UE 104 are illustrated in FIG. Figure 1 As shown, UE 104 can communicate with various types of devices, such as network entity 102, other UEs 104, or network devices (e.g., core network 106, packet data network 108, relay device, integrated access and backhaul (IAB) node, or another network device), such as Figure 1 Additionally or alternatively, the UE 104 can support communications with other network entities 102 or UEs 104 that can act as relays in the wireless communication system 100.

[0047] The UE 104 may also be capable of supporting wireless communications directly with other UEs 104 via a communication link 114. For example, the UE 104 may support wireless communications directly with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular V2X deployments, the communication link 114 may be referred to as a sidelink. For example, the UE 104 may support wireless communications directly with another UE 104 via a PC5 interface.

[0048] The network entity 102 may support communication with the core network 106 or with another network entity 102 or both. For example, the network entity 102 may interface with the core network 106 via one or more backhaul links 116 (e.g., via S1, N2, N2 or another network interface). The network entities 102 may communicate with each other via the backhaul links 116 (e.g., via X2, Xn or another network interface). In some implementations, the network entities 102 may communicate directly with each other (e.g., between the network entities 102). In some other implementations, the network entities 102 may communicate with each other or indirectly (e.g., via the core network 106). In some implementations, one or more network entities 102 may include subcomponents, such as access network entities, which may be examples of access node controllers (ANCs). The ANC may communicate with one or more UEs 104 via one or more other access network transport entities (which may be referred to as radio heads, smart radio heads, or transport reception points (TRPs)).

[0049] In some implementations, the network entity 102 may be configured in a decomposed architecture that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 102, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 102 may include one or more of a central unit (CU), a distributed unit (DU), a radio unit (RU), a RAN intelligent controller (RIC) (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) system, or any combination thereof.

[0050] The RU may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmission reception point (TRP). In a decomposed RAN architecture, one or more components of the network entity 102 may be collocated, or one or more components of the network entity 102 may be located at distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0051] The functional split between CU, DU and RU can be flexible, and different functions can be supported according to the functions performed at the CU, DU or RU (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions and any combination thereof). For example, a functional split of a protocol stack can be adopted between the CU and the DU so that the CU can support one or more layers of the protocol stack and the DU can support one or more different layers of the protocol stack. In some implementations, the CU can host upper protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functions and signaling (e.g., Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU can be connected to one or more DUs or RUs, and one or more DUs or RUs can host lower protocol layers, such as Layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, media access control (MAC) layer) functions and signaling, and each can be at least partially controlled by the CU 160.

[0052] Additionally or alternatively, a functional split of the protocol stack may be employed between the DU and the RU such that the DU may support one or more layers of the protocol stack and the RU may support one or more different layers of the protocol stack. The DU may support one or more different cells (e.g., via one or more RUs). In some implementations, the functional split between the CU and the DU or between the DU and the RU may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of the CU, DU, or RU, while other functions of the protocol layer may be performed by different ones of the CU, DU, or RU).

[0053] The CU may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU may be connected to one or more DUs via a medium-range communication link (e.g., F1, F1-c, F1-u), and the DU may be connected to one or more RUs via a fronthaul communication link (e.g., an open fronthaul (FH) interface). In some implementations, the medium-range communication link or the fronthaul communication link may be implemented based on interfaces (e.g., channels) between layers of a protocol stack supported by a corresponding network entity 102 communicating via such a communication link.

[0054] The core network 106 may support user authentication, access authorization, tracking, connection, and other access, routing, or mobility functions. The core network 106 may be an evolved packet core (EPC) or a 5G core (5GC), which may include control plane entities that manage access and mobility (e.g., mobility management entity (MME), access and mobility management function (AMF)), and user plane entities that route packets or interconnections to external networks (e.g., serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)). In some implementations, the control plane entities may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) of one or more UEs 104 served by one or more network entities 102 associated with the core network 106.

[0055] The core network 106 may communicate with the packet data network 108 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). The packet data network 108 may include an application server 118. In some implementations, one or more UEs 104 may communicate with the application server 118. The UE 104 may establish a session (e.g., a protocol data unit (PDU) session, etc.) with the core network 106 via the network entity 102. The core network 106 may use the established session (e.g., the established PDU session) to route traffic (e.g., control information, data, etc.) between the UE 104 and the application server 118. The PDU session may be an example of a logical connection between the UE 104 and the core network 106 (e.g., one or more network functions of the core network 106).

[0056] In the wireless communication system 100, the network entity 102 and the UE 104 may use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some implementations, the network entity 102 and the UE 104 may support different resource structures. For example, the network entity 102 and the UE 104 may support different frame structures. In some implementations, such as in 4G, the network entity 102 and the UE 104 may support a single frame structure. In some other implementations, such as in 5G and other suitable radio access technologies, the network entity 102 and the UE 104 may support various frame structures (i.e., multiple frame structures). The network entity 102 and the UE 104 may support various frame structures based on one or more digital technologies.

[0057] One or more digital technologies may be supported in the wireless communication system 100, and the digital technologies may include subcarrier spacing and cyclic prefixes. A first digital technology (e.g., μ = 0) may be associated with a first subcarrier spacing (e.g., 15kHz) and a normal cyclic prefix. In some implementations, a first digital technology (e.g., μ = 0) associated with a first subcarrier spacing (e.g., 15kHz) may utilize one slot per subframe. A second digital technology (e.g., μ = 1) may be associated with a second subcarrier spacing (e.g., 30kHz) and a normal cyclic prefix. A third digital technology (e.g., μ = 2) may be associated with a third subcarrier spacing (e.g., 60kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth digital technology (e.g., μ = 3) may be associated with a fourth subcarrier spacing (e.g., 120kHz) and a normal cyclic prefix. A fifth digital technology (e.g., μ = 4) may be associated with a fifth subcarrier spacing (e.g., 240kHz) and a normal cyclic prefix.

[0058] The time intervals of resources (e.g., communication resources) can be organized according to frames (also referred to as radio frames). Each frame can have a duration, for example, a duration of 10 milliseconds (ms). In some implementations, each frame can include multiple subframes. For example, each frame can include 10 subframes, and each subframe can have a duration, for example, a duration of 1 ms. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.

[0059] Additionally or alternatively, the time interval of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may include a certain number (e.g., quantity) of time slots. The number of time slots in each subframe may also depend on one or more digital technologies supported in the wireless communication system 100. For example, a first digital technology, a second digital technology, a third digital technology, a fourth digital technology, and a fifth digital technology (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with corresponding subcarrier spacings of 15kHz, 30kHz, 60kHz, 120kHz, and 240kHz may utilize one time slot per subframe, two time slots per subframe, four time slots per subframe, eight time slots per subframe, and 16 time slots per subframe, respectively. Each time slot may include a certain number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of time slots of a subframe may depend on the digital technology. For a normal cyclic prefix, a time slot may include 14 symbols. For an extended cyclic prefix (e.g., for a 60 kHz subcarrier spacing), a slot may include 12 symbols. For a normal cyclic prefix and an extended cyclic prefix, the relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame may depend on the digital technology. It should be understood that references to a first digital technology (e.g., μ=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0060] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, frequency channels, etc. based on frequency or wavelength. For example, the wireless communication system 100 can support one or more operating frequency bands, such as frequency range names FR1 (410 MHz-7.125 GHz), FR2 (24.25 GHz-52.6 GHz), FR3 (7.125 GHz-24.25 GHz), FR4 (52.6 GHz-114.25 GHz), FR4a or FR4-1 (52.6 GHz-71 GHz), and FR5 (114.25 GHz-300 GHz). In some implementations, the network entity 102 and the UE 104 can perform wireless communications on the one or more operating frequency bands. In some implementations, FR1 can be used by the network entity 102 and the UE 104 and other devices or apparatuses for cellular communication services (e.g., control information, data). In some implementations, FR2 can be used by the network entity 102 and the UE 104 and other devices or apparatuses for short-range, high data rate capabilities.

[0061] FR1 may be associated with one or more digital technologies (e.g., at least three digital technologies). For example, FR1 may be associated with a first digital technology (e.g., μ=0) including a subcarrier spacing of 15 kHz; a second digital technology (e.g., μ=1) including a subcarrier spacing of 30 kHz; a third digital technology (e.g., μ=2) including a subcarrier spacing of 60 kHz. FR2 may be associated with one or more digital technologies (e.g., at least 2 digital technologies). For example, FR2 may be associated with a third digital technology (e.g., μ=2) including a subcarrier spacing of 60 kHz; a fourth digital technology (e.g., μ=3) including a subcarrier spacing of 120 kHz.

[0062] As described herein, a network can reduce energy consumption, such as energy consumption of base station 102, by identifying the RRC state of any UE 104 associated with base station 102 and reducing transmissions (e.g., reducing the periodicity of transmissions) between the base station and certain UEs (such as UEs in an RRC idle or inactive state).

[0063] UE 104 may be in one RRC state (within a 5G network) at any given time. RRC states include an RRC connected state (e.g., NR RRC_Connected), an RRC inactive state (e.g., NR RRC_Inactive), and an RRC idle state (e.g., NR RRC_Idle). In some cases, when there is an established RRC connection, UE 104 may be in an RRC connected or RRC inactive state, and when there is no RRC connection, UE 104 may be in an RRC idle state.

[0064] In some embodiments, the base station 102 or other network entity sends a message to the UE 104 to determine the RRC state of the UE 104 and to modify transmissions, such as DL transmissions, based on the discovered or determined UE RRC state. For example, the network may reduce certain transmissions (e.g., synchronization signal blocks (SSBs), master information blocks (MIBs) transmissions, and / or system information transmissions) based on the number of UEs in the RRC idle state and / or the number of UEs transitioning between states (e.g., from RRC idle to RRC connected state).

[0065] Figure 2 An example of a diagram 200 supporting messaging between a network entity and one or more UEs according to aspects of the present disclosure is illustrated. A network entity 220 (e.g., a gNB in ​​a 5G network) sends a query message 230 to a UE 210 (such as a UE in an RRC idle state). The query message 230 may be a DL common signaling message (e.g., a new paging message) that addresses the UE 210 in the RRC idle state.

[0066] The query message 210 queries the UE to provide information about the availability of other cells (or other network entities) as suitable or acceptable serving cells for the UE 210. For example, a cell may be a suitable or acceptable serving cell when the cell has sufficient radio quality to support an emergency call placed by the UE 210. Thus, the query message 220 enables the UE 210 to determine whether the UE 210 is able to select (or reselect) a different cell as a suitable or acceptable cell.

[0067] In some cases, the query message 210 may request from the UE 210 to evaluate one or more cell selection criteria S or S alternative criteria at different radio thresholds.

[0068] The network entity 220 may send the query message 230 in different ways. As a first example, the query may be part of an RRC paging message and may optionally include different radio thresholds. The following is an example RRC paging message including a query for the UE 210:

[0069]

[0070] As a second example, the network entity may utilize a short message to add a new code point to signal the query to UE 210. The network entity may send a short message via PDCCH using the P-RNTI (using the short message field in DCI format 1_0 to associate or not associate a paging message).

[0071] Table 1 presents an example implementation where bit 5 signals to the UE 210 that the message is a query message:

[0072]

[0073] Table 1: Short message extended to include queries to UE 210

[0074] As indicated, when the network initiates a capacity saving or reduction process, a query message (e.g., Query-v1800-IEs) is included in SIB1 (or in a different SIB), which is then notified to UE 210 using a newly defined queryMessage in a short message in PDCCH using systemInfoModification or using P-RNTI, as described herein. Alternatively, UE 210 can check whether SIB1 (or a different SIB including the query therein) is updated periodically based on a SIB1 periodicity of 160 ms.

[0075] In response, after evaluating the service area by performing various measurements, UE 210 sends a response message 235 to network entity 220. For example, UE 210 may perform measurements even if network entity 220 (e.g., current serving cell) satisfies the following conditions:

[0076] Srxlev>S IntraSearchP And Squal>S IntraSearchQ , for performing intra-frequency measurements; or

[0077] Srxlev>S nonIntraSearchP And Squal>S nonIntraSearchQ , between NR frequencies with equal or lower reselection priority,

[0078] Where S IntraSearchP Specifies the Srxlev (cell selection RX level) threshold (in dB) for intra-frequency measurements, S IntraSearchQ Specifies the Squal (cell selection quality value) threshold (in dB) for intra-frequency measurements. nonIntraSearch Specifies the Srxlev threshold (in dB) for NR inter-frequency and inter-RAT measurements, S nonIntraSearchQ Specifies the Squal threshold (in dB) for NR inter-frequency and inter-RAT measurements.

[0079] After performing the measurements, the UE 210 evaluates whether one or more radio criteria are met. For example, the UE 210 may determine, among other selection criteria, that the S criteria (or S alternative criteria) are met, that the NR inter-frequency and inter-RAT cell reselection criteria are met, and / or that the intra-frequency and equal-priority inter-frequency cell reselection criteria are met.

[0080] In some cases, when no selection criteria are met, UE 210 sends response message 235. For example, response message 235 may indicate that the current serving cell (eg, network entity 220) is the only suitable cell available to UE 210. Otherwise, UE 210 may not send response message 235.

[0081] In other cases, when UE 210 determines that zero neighboring cells are acceptable or suitable serving cells, UE 210 sends response message 235. Therefore, response message 235 indicates that the current serving cell (e.g., network entity 220) is the only suitable cell available to UE 210. Otherwise, UE 210 may not send response message 235.

[0082] When the network entity 220 receives zero or less than a threshold number of responses from the various queried UEs 210, such as within a certain period of time or window after sending the query message 230, the network entity 220 reduces or stops DL transmissions. For example, the network entity 220 may turn off certain transmissions (e.g., SSB, MIB, and / or system information) and / or UL reception.

[0083] In some embodiments, network entity 220 may optionally send an idle mobility command (or other DL signaling message) 240 to UE 210. Command 240 may request an RRC idle UE (e.g., UE 210) to perform an RRC idle state mobility operation (e.g., a selection or reselection procedure). In some cases, command 240 may indicate the time or duration at which network entity 220 turns on a transmit / receive operation.

[0084] For example, network entity 220 may continue to send SSBs using the current broadcast configuration or with a reduced periodicity (e.g., as identified in command 240 and / or the messaging configuration described herein) and listen to UL RACH opportunities in the idle state for messages from the UE.

[0085] In some embodiments, the network entity 220 determines or identifies a specific number of UEs 210 that have sent response messages 235 in response to a query message 230 sent by the network entity 220. Using the specific number N, the network entity 220 may follow a step-by-step process to determine the frequency or periodicity at which DL signaling is performed. Table 2 maps the number N of response messages to the DL transmission periodicity for a given area.

[0086] Number of UEs that sent responses <N1 No DL transmission N1< send the response number of the UE <N2 Sparse DL transmission N2< send response to UE's number <N3 DL transmission with slightly reduced periodicity N3 < Number of UEs sending responses DL transmission under peak traffic conditions

[0087] Table 2

[0088] Therefore, certain types of DL signaling or transmissions (eg, SSB, MIB, SIB1, and / or other system information) are mapped to the number of UEs 210 that send responses to the network entity 220 .

[0089] For example, given a certain coverage area, the network entity may estimate or determine the number of UEs in the RRC idle state (relative to the UEs in the RRC connected state), which may be expressed as a ratio of RRC idle UEs to RRC connected UEs. In some cases, the ratio may increase from peak periods to non-peak periods, where the ratio increases from 10:1 to 50:1. In this case, N in Table 2 may represent the actual number of UEs that send response messages, or the ratio of RRC idle UEs to RRC connected UEs. Therefore, according to Table 2, the DL transmission periodicity varies with the number of UEs that send response messages.

[0090] Therefore, the network can adjust the DL transmission periodicity based on various conditions, such as when there are no (or minimal) idle UEs in the cell (e.g., in sparsely populated areas and / or when the average number of UEs transitioning from RRC Idle state to RRC Connected state is low (e.g., during non-peak hours in the coverage area). Figure 3 An example of a graph 300 supporting selection of communication periodicity in accordance with aspects of the present disclosure is illustrated.

[0091] As shown, the network entity 220 determines the number N of response messages 310 received after sending the query message 230. Based on the number N, the network entity 220 performs no DL transmission 320, performs sparse or a small number of DL transmissions 330, performs a reduced number of DL transmissions 340, or performs at a peak level (e.g., non-reduced) at a periodicity 350.

[0092] The thresholds N1, N2, N3, and N4 may vary based on coverage area, time of day, etc. For example, the thresholds may be based on absolute numbers, where N1=1, and the other thresholds increase in a linear fashion. As another example, the thresholds may increase exponentially (e.g., N1=3, N2=9, N3=27, N4=81). Furthermore, a network may include fewer or more thresholds to modify the granularity of the step-by-step process based on the network and / or its characteristics.

[0093] In some embodiments, such as when the network entity 220 reduces the periodicity of DL transmissions, the UE 210 may monitor the radio quality within the coverage area during a specific energy saving period (e.g., when DL transmissions are reduced). When monitoring the coverage area, the UE 210 may:

[0094] When the quality meets a threshold (e.g., S standard, alternative S standard, etc.), unconditionally or conditionally reporting the measured serving cell quality, which may be a new threshold, indicating that the serving cell has fallen below the new threshold;

[0095] Reporting when at least one neighboring cell meets one or more quality thresholds;

[0096] Any generated reports are logged, and when the network entity 220 returns to the original DL transmission periodicity, the reports are provided to the network entity 220; and so on.

[0097] In some cases, the UE 210 considers the newly announced DL transmission configuration to determine the cell quality. For example, the UE 210 may apply L1 and / or L3 filtering to evaluate the cell radio quality, utilizing the new configuration of the DL transmission to avoid erroneously determining that the cell is a weak radio cell. Thus, among other things, the UE may avoid erroneous determination of a cell temporarily power saving by reducing (multiple) DL transmissions as a weak cell.

[0098] In some embodiments, the network entity 220 may communicate with other entities (other cells) to prevent or avoid many neighboring cells from reducing DL transmission or entering sleep mode. For example, before sending the query message 230 to the UE 210, the network entity 210 may poll the neighboring cells to determine whether the neighboring cells are or will remain active and available for any UE served by these cells.

[0099] In some cases, neighboring cells may communicate with each other to determine which cells can move to energy saving mode (eg, reduce DL transmissions). Based on the response, the cells may introduce a TDM (time division multiplexing) mode and place different cells in different time slots.

[0100] Figure 4 An example of a diagram 400 that supports provisioning of neighboring cells into energy-saving time slots in accordance with aspects of the present disclosure is illustrated. Cells 410 are positioned or inserted on a timeline 420 at different time periods (e.g., t0 to t1, t4 to t5, etc.). In each time period, a certain cell 410 may perform a DL transmission reduction or modification as described herein. However, when DL transmission is not possible when the query message 230 is sent, the cell 410 may notify the next cell in the timeline 420, which may initiate its DL reduction process before the start of its associated time slot.

[0101] For example, when cell 3 attempts to sleep or otherwise reduce DL transmissions when timeline reaches t2, the cell receives too many response messages 235 and cannot modify operation. Cell 3 then notifies cell 4, which sends query message 230 before t3, which is the normally allocated time for cells to perform energy saving operations, because cell 3 cannot use its insertion time to perform energy saving.

[0102] Figure 5 An example of a block diagram 500 of a device 502 supporting reduced energy consumption during wireless communications in accordance with aspects of the present disclosure is illustrated. The device 502 may be an example of a network entity 102 as described herein. The device 502 may support wireless communications with one or more network entities 102, UEs 104, or any combination thereof. The device 502 may include components for bidirectional communication, including components for sending and receiving communications (such as a processor 504, a memory 506, a transceiver 508, and an I / O controller 510). These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., a bus).

[0103] The processor 504, the memory 506, the transceiver 508, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of the present disclosure described herein. For example, the processor 504, the memory 506, the transceiver 508, or various combinations thereof, or components thereof may support methods for performing one or more of the operations described herein.

[0104] In some implementations, the processor 504, memory 506, transceiver 508, or various combinations or components thereof may be implemented in hardware (e.g., in a communications management circuit system). The hardware may include a processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to or otherwise support means for performing the functions described in the present disclosure. In some implementations, the processor 504 and the memory 506 coupled to the processor 504 may be configured to perform one or more functions described herein (e.g., by executing instructions stored in the memory 506 by the processor 504).

[0105] For example, according to examples disclosed herein, the processor 504 may support wireless communications at the device 502. The processor 504 may be configured to or otherwise support a component for: sending a query message to one or more UEs; receiving a response message from the one or more UEs, the response message indicating, for each UE, whether the UE can select a neighboring network entity as a serving cell; and modifying DL transmission to the one or more UEs based on the number of response messages received from the one or more UEs.

[0106] The processor 504 may include an intelligent hardware device (e.g., a general purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some implementations, the processor 504 may be configured to operate a memory array using a memory controller. In some other implementations, the memory controller may be integrated into the processor 504. The processor 504 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 506) to cause the device 502 to perform various functions of the present disclosure.

[0107] The memory 506 may include random access memory (RAM) and read-only memory (ROM). The memory 506 may store computer-readable computer executable code, which includes instructions that, when executed by the processor 504, cause the device 502 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as a system memory or another type of memory. In some implementations, the code may not be directly executable by the processor 504, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, the memory 506 may include a basic I / O system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0108] I / O controller 510 can manage input and output signals of device 502. I / O controller 510 can also manage peripheral devices that are not integrated into device 502. In some implementations, I / O controller 510 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 510 can utilize an operating system, such as Or another known operating system. In some implementations, I / O controller 510 can be implemented as part of a processor such as processor M06. In some implementations, a user can interact with device 502 via I / O controller 510 or via hardware components controlled by I / O controller 510.

[0109] In some implementations, the device 502 may include a single antenna 512. However, in some other implementations, the device 502 may have more than one antenna 512 (i.e., multiple antennas), including multiple antenna panels or antenna arrays, which are capable of concurrently sending or receiving multiple wireless transmissions. The transceiver 508 can communicate bidirectionally via one or more antennas 512, wired or wireless links, as described herein. For example, the transceiver 508 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. The transceiver 508 may also include a modem for modulating packets, providing the modulated packets to one or more antennas 512 for transmission, and demodulating packets received from one or more antennas 512.

[0110] Figure 6 A flow chart of a method 600 for supporting a network entity to determine an RRC state of a UE in a coverage area according to various aspects of the present disclosure is illustrated. The operations of the method 600 may be implemented by an apparatus or component thereof as described herein. For example, the operations of the method 600 may be implemented by a device as described in reference to Figures 1 to 5The network entity 102 or the network entity 220 described above may be used to perform. In some implementations, the device may execute a set of instructions to control the functional elements of the device to perform the described functions. Additionally or alternatively, the device may use dedicated hardware to perform various aspects of the described functions.

[0111] At 605, the method may include sending a query message to one or more UEs. The operations of 605 may be performed according to the examples described herein. In some implementations, aspects of the operations of 605 may be described by reference to Figure 1 The device is used to perform the above.

[0112] At 610, the method may include receiving a response message from one or more UEs, the response message indicating, for each UE, whether the UE is able to select a neighboring network entity as a serving cell. The operations of 610 may be performed according to examples described herein. In some implementations, aspects of the operations of 610 may be implemented by reference to Figure 1 The device is used to perform the above.

[0113] At 615, the method may include modifying DL transmissions to one or more UEs based on the number of response messages received from the one or more UEs. The operations of 615 may be performed according to the examples described herein. In some implementations, aspects of the operations of 615 may be described by reference to Figure 1 The device is used to perform the above.

[0114] Figure 7 A flowchart of a method 700 for supporting a UE to evaluate a coverage area of ​​a network entity according to various aspects of the present disclosure is illustrated. The operations of the method 700 may be implemented by a device or component thereof as described herein. For example, the operations of the method 700 may be implemented by a device or component thereof as described in reference to Figures 1 to 5 The network entity 102 or the network entity 220 described above may be used to perform. In some implementations, the device may execute a set of instructions to control the functional elements of the device to perform the described functions. Additionally or alternatively, the device may use dedicated hardware to perform various aspects of the described functions.

[0115] At 705, the method may include receiving a query message from a network entity. The operations of 705 may be performed according to examples described herein. In some implementations, aspects of the operations of 616 may be implemented by reference to Figure 1 The device is used to perform the above.

[0116] At 710, the method may include determining, in response to the query message, whether one or more neighboring network entities are available to provide normal service to the UE. The operations of 710 may be performed according to the examples described herein. In some implementations, aspects of the operations of 710 may be described by reference to Figure 1 The device is used to perform the above.

[0117] At 715, the method may include: when no neighboring network entity is available to provide normal service to the UE, sending a message to the network entity. The operation of 715 may be performed according to the examples described herein. In some implementations, aspects of the operation of 715 may be described by reference to Figure 1 The device is used to perform the above.

[0118] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified, and other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0119] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or executed with a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in combination with a DSP core, or any other such configuration).

[0120] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or sent via a computer-readable medium as one or more instructions or codes. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or any combination of these. Features that implement the functions may also be physically located in various locations, including being distributed so that portions of the functions are implemented in different physical locations.

[0121] Computer-readable media include both non-transient computer storage media and communication media, and communication media include any medium that facilitates the transmission of computer programs from one place to another. Non-transient storage media can be any available medium that can be accessed by a general or special-purpose computer. As an example and not limitation, non-transient computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, disk storage or other magnetic storage devices, or can be used to carry or store desired program code devices in the form of instructions or data structures and can be accessed by a general or special-purpose computer, or any other non-transient medium of a general or special-purpose processor.

[0122] Any connection may be appropriately referred to as a computer-readable medium. For example, if the software is sent from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technology (such as infrared, radio, and microwave), the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology (such as infrared, radio, and microwave) is included in the definition of computer-readable medium. Disks and optical disks as used herein include CDs, laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks, wherein disks typically reproduce data magnetically, and optical disks reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0123] As used herein, including in the claims, "or" used in a list of items (e.g., a list of items beginning with a phrase such as "at least one of" or "one or more of" or "one or both of") means an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (e.g., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" may be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on." In addition, as used herein, including in the claims, a "set" may include one or more elements.

[0124] When referring to a network entity, the terms "send," "receive," or "transmit" may refer to any part of a network entity of a RAN (e.g., base station, CU, DU, RU) that communicates with another device (e.g., directly or via one or more other network entities).

[0125] The descriptions described herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "better than other examples." The detailed description includes specific details to facilitate understanding of the described techniques. However, these techniques may be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid confusing the concepts of the described examples.

[0126] The description herein is provided to enable one of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure will be clear to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but should conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE), comprising: processor; as well as a memory coupled to the processor, the processor being configured to: receiving a query message from a network entity; In response to the query message, determining whether one or more neighboring network entities are available to provide normal services to the UE; as well as When no neighboring network entity is available to provide normal service to the UE, a message is sent to the network entity. 2 . The UE of claim 1 , wherein the UE receives the query message via a short message on a physical downlink control channel (PDCCH) using a paging radio network temporary identifier (P-RNTI). 3 . The UE of claim 1 , wherein the UE receives the query message via a radio resource control (RRC) paging message. 4 . The UE of claim 1 , wherein the UE operates in a radio resource control (RRC) idle state.

5. The UE of claim 1, wherein the UE operates in a radio resource control (RRC) inactive state.

6. The UE according to claim 1, wherein the UE determines whether the one or more neighboring network entities are available to provide normal services to the UE by: performing intra-frequency measurements or inter-frequency measurements on the one or more neighboring network entities; and It is determined whether the intra-frequency measurement or the inter-frequency measurement satisfies one or more cell reselection criteria.

7. The UE according to claim 1, wherein the UE determines whether the one or more neighboring network entities satisfy the following conditions based on intra-frequency measurement or inter-frequency measurement: S standard, New Radio (NR) inter-frequency and inter-RAT (Radio Access Technology) cell reselection criteria, or Intra-frequency and equal-priority inter-frequency cell reselection criteria.

8. The UE of claim 1, wherein the UE sends the message to the network entity when the UE determines that the network entity is a separate serving cell for the UE based on measurements performed indicating that none of the one or more neighboring network entities meets a cell reselection criterion for the UE.

9. The UE of claim 1, wherein when the UE determines that the network entity is the only available serving cell for the UE based on determining that none of the one or more neighboring network entities is a suitable serving cell for the UE, the UE sends the message to the network entity.

10. A method performed by a user equipment (UE), the method comprising: receiving a query message from a network entity; In response to the query message, determining whether one or more neighboring network entities are available to provide normal services to the UE; as well as When no neighboring network entity is available to provide normal service to the UE, a message is sent to the network entity.

11. The method of claim 10, wherein the UE receives the query message via a short message on a physical downlink control channel (PDCCH) using a paging radio network temporary identifier (P-RNTI).

12. The method of claim 10, wherein the UE receives the query message via a radio resource control (RRC) paging message.

13. A network entity, comprising: processor; as well as a memory coupled to the processor, the processor being configured to: Sending a query message to one or more user equipments (UEs); receiving a response message from the one or more UEs, the response message indicating, for each UE, whether the UE can select a neighboring network entity as a serving cell; as well as Downlink (DL) transmissions to the one or more UEs are modified based on a number of response messages received from the one or more UEs.

14. The network entity of claim 13, wherein the network entity sends the query message via a short message on a physical downlink control channel (PDCCH) using a paging radio network temporary identifier (P-RNTI).

15. The network entity of claim 13, wherein the network entity sends the query message via a radio resource control (RRC) paging message.

16. The network entity of claim 13, wherein the network entity sends the query message to at least one UE operating in a radio resource control (RRC) idle state.

17. The network entity of claim 13, wherein the network entity sends the query message to at least one UE operating in a radio resource control (RRC) inactive state.

18. The network entity of claim 13, wherein the network entity modifies the DL transmission by reducing synchronization signal block (SSB), master information block (MIB) transmission, or system information transmission.

19. The network entity of claim 13, wherein the network entity modifies a periodicity of uplink reception from the one or more UEs.

20. A processor for wireless communication, comprising: at least one controller coupled to at least one memory and configured to cause the processor to: receiving a query message from a network entity; In response to the query message, determining whether one or more neighboring network entities are available to provide normal services to the processor; as well as When no neighboring network entity is available to provide normal service to the processor, a message is sent to the network entity.

Images