[go: up one dir, main page]

WO2025020033A1 - Intervalle inactif pour la gestion d'un message de radiomessagerie - Google Patents

Intervalle inactif pour la gestion d'un message de radiomessagerie Download PDF

Info

Publication number
WO2025020033A1
WO2025020033A1 PCT/CN2023/108840 CN2023108840W WO2025020033A1 WO 2025020033 A1 WO2025020033 A1 WO 2025020033A1 CN 2023108840 W CN2023108840 W CN 2023108840W WO 2025020033 A1 WO2025020033 A1 WO 2025020033A1
Authority
WO
WIPO (PCT)
Prior art keywords
grant
inactive interval
paging message
transmission
time
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2023/108840
Other languages
English (en)
Inventor
Dunfa SHI
Sharda RANJAN
Tom Chin
Jingming CHANG
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Qualcomm Inc
Original Assignee
Qualcomm Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qualcomm Inc filed Critical Qualcomm Inc
Priority to PCT/CN2023/108840 priority Critical patent/WO2025020033A1/fr
Publication of WO2025020033A1 publication Critical patent/WO2025020033A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/02—Arrangements for increasing efficiency of notification or paging channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]

Definitions

  • aspects of the present disclosure generally relate to wireless communication and specifically, to techniques and apparatuses for handling a paging message using an inactive interval.
  • Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts.
  • Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (for example, bandwidth or transmit power) .
  • multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and Long Term Evolution (LTE) .
  • LTE/LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP) .
  • UMTS Universal Mobile Telecommunications System
  • New Radio which may be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by the 3GPP.
  • NR is designed to better support mobile broadband internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink, using CP-OFDM or single-carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM) ) on the uplink, as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.
  • OFDM orthogonal frequency division multiplexing
  • SC-FDM single-carrier frequency division multiplexing
  • MIMO multiple-input multiple-output
  • a user equipment may monitor the paging radio network temporary identifier (P-RNTI) over downlink control information (DCI) during a radio resource control (RRC) connected state for only short messages.
  • a network can send a paging message to an RRC connected UE.
  • the network sending the paging message while the UE is in the RRC connected state may indicate that the network and the UE are unsynchronized.
  • the network sending the paging message while the UE is in the RRC connected state may indicate that the network has identified the UE as not being in an RRC connected state (for example, the network has identified the UE as being in an RRC idle state or in an RRC inactive state) .
  • the paging message may prompt the UE to blindly perform a connection release (for example, a local RRC connection release) , move to RRC idle state, and re-try a registration procedure to re-synchronize with network (for example, such that the network identifies the UE as being in an RRC connected state when the UE is in the RRC connected state) .
  • a connection release for example, a local RRC connection release
  • RRC idle state for example, a registration procedure to re-synchronize with network
  • network for example, such that the network identifies the UE as being in an RRC connected state when the UE is in the RRC connected state
  • the paging message sent to the RRC connected UE may have been sent in error.
  • the network may send the paging message even though the network and the UE are synchronized (for example, even though the network has identified the UE as being in an RRC connected state) .
  • the UE may blindly address (for example, process) the paging message by triggering the connection release (for example, a radio link failure (RLF) procedure) .
  • the UE may switch to RRC idle state to re-synchronize with the network via a non-access stratum (NAS) triggering registration request.
  • NAS non-access stratum
  • Performing a connection release in response to a paging message sent in error may interrupt an RRC connection.
  • receiving an erroneous paging message during an active voice over new radio (VoNR) voice call can prompt the UE to blindly release the RRC connection, thereby interrupting the voice call.
  • the connection release may cause intermittent voice breaks, silence during the call, delays, or call drops, among other examples.
  • the UE may include a processing system that includes one or more processors and one or more memories coupled with the one or more processors.
  • the processing system may be configured to cause the UE to receive, while the UE is in a radio resource control (RRC) connected state, a grant for a transmission that is to occur at a grant time.
  • RRC radio resource control
  • the processing system may be configured to cause the UE to receive, while the UE is in the RRC connected state, a paging message.
  • the processing system may be configured to cause the UE to delay, while an inactive interval associated with the UE does not satisfy a configurable inactive interval threshold, release of the RRC connected state.
  • the method may include receiving, while the UE is in an RRC connected state, a grant for a transmission that is to occur at a grant time.
  • the method may include receiving, while the UE is in the RRC connected state, a paging message.
  • the method may include delaying, while an inactive interval associated with the UE does not satisfy a configurable inactive interval threshold, release of the RRC connected state.
  • Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE.
  • the set of instructions when executed by one or more processors of the UE, may cause the UE to receive, while the UE is in an RRC connected state, a grant for a transmission that is to occur at a grant time.
  • the set of instructions when executed by one or more processors of the UE, may cause the UE to receive, while the UE is in the RRC connected state, a paging message.
  • the set of instructions, when executed by one or more processors of the UE may cause the UE to delay, while an inactive interval associated with the UE does not satisfy a configurable inactive interval threshold, release of the RRC connected state.
  • the apparatus may include means for receiving, while the apparatus is in an RRC connected state, a grant for a transmission that is to occur at a grant time.
  • the apparatus may include means for receiving, while the apparatus is in the RRC connected state, a paging message.
  • the apparatus may include means for delaying, while an inactive interval associated with the apparatus does not satisfy a configurable inactive interval threshold, release of the RRC connected state.
  • aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, network node, network entity, wireless communication device, or processing system as substantially described with reference to and as illustrated by the drawings and specification.
  • Figure 1 is a diagram illustrating an example of a wireless network in accordance with the present disclosure.
  • Figure 2 is a diagram illustrating an example network node in communication with a user equipment (UE) in a wireless network in accordance with the present disclosure.
  • UE user equipment
  • Figure 3 is a diagram illustrating an example disaggregated base station architecture in accordance with the present disclosure.
  • Figure 4 is a diagram illustrating an example associated with paging messages in accordance with the present disclosure.
  • Figure 5 is a diagram illustrating an example associated with handling a paging message received during an RRC connected state in accordance with the present disclosure.
  • Figure 6 is a diagram illustrating an example associated with determining how to handle a paging message received during an RRC connected state in accordance with the present disclosure.
  • Figure 7 is a flowchart illustrating an example process performed, for example, by a UE that supports handling a paging message using an inactive interval in accordance with the present disclosure.
  • Figure 8 is a diagram of an example apparatus for wireless communication that supports handling a paging message using an inactive interval in accordance with the present disclosure.
  • Figure 9 is a diagram of an example apparatus for wireless communication that supports handling a paging message using an inactive interval in accordance with the present disclosure.
  • Various aspects relate generally to handling of paging messages. Some aspects more specifically relate to delaying release of a radio resource control (RRC) connection in response to a paging message received by a user equipment (UE) in an RRC connected state.
  • the UE monitors how long the network has been inactive and, after a configurable amount of time, releases the RRC connection.
  • the UE may receive a grant from the network before the configurable amount of time has elapsed, and the UE may ignore the paging message (for example, the UE may determine not to release the RRC connection at any point in response to the paging message) .
  • the UE may not receive a grant from the network before the configurable amount of time has elapsed, and the UE may release the RRC connection.
  • the described techniques can be used to enable the UE to delay release of an RRC connected state in case the paging message was sent in error, thereby preventing interruptions in service.
  • a UE in an RRC connected state may preserve an ongoing voice over Long Term Evolution (VoLTE) call and associated call performance, Long Term Evolution (LTE) data traffic, an ongoing voice over New Radio (VoNR) call and associated call performance, New Radio (NR) data traffic, an ongoing 6G voice call and associated call performance, 6G data traffic, or the like.
  • VoLTE Long Term Evolution
  • LTE Long Term Evolution
  • VoNR New Radio
  • the UE receiving the grant from the network within the configurable amount of time may indicate that the network and the UE are synchronized (for example, the paging message was sent in error) , and, therefore, the UE may maintain the existing RRC connection.
  • the UE not receiving any more grants from the network within the configurable amount of time may indicate that the network and the UE are not synchronized (for example, the connection with the UE may have already been released on the network side due to the UE and the network becoming unsynchronized) , and, therefore, the UE may release the RRC connection and re-register with the network to re-synchronize with the network.
  • the UE may differentiate between, and handle differently, erroneous paging messages and paging message sent because the network and the UE are not synchronized.
  • the configurable amount of time may be configured to enable earlier re-synchronization with the network (for example, by shortening the configurable amount of time) .
  • FIG. 1 is a diagram illustrating an example of a wireless network in accordance with the present disclosure.
  • the wireless network 100 may be or may include elements of a 5G (for example, NR) network or a 4G (for example, LTE) network, among other examples.
  • the wireless network 100 may include one or more network nodes 110 (shown as a network node (NN) 110a, a network node 110b, a network node 110c, and a network node 110d) , a UE 120 or multiple UEs 120 (shown as a UE 120a, a UE 120b, a UE 120c, a UE 120d, and a UE 120e) , or other network entities.
  • NW network node
  • a network node 110 is an entity that communicates with UEs 120. As shown, a network node 110 may include one or more network nodes. For example, a network node 110 may be an aggregated network node, meaning that the aggregated network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (for example, within a single device or unit) .
  • a network node 110 may be a disaggregated network node (sometimes referred to as a disaggregated base station) , meaning that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed among two or more nodes (such as one or more central units (CUs) , one or more distributed units (DUs) , or one or more radio units (RUs) ) .
  • CUs central units
  • DUs distributed units
  • RUs radio units
  • a network node 110 is or includes a network node that communicates with UEs 120 via a radio access link, such as an RU. In some examples, a network node 110 is or includes a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU. In some examples, a network node 110 is or includes a network node that communicates with other network nodes 110 via a midhaul link or a core network via a backhaul link, such as a CU.
  • a network node 110 may include multiple network nodes, such as one or more RUs, one or more CUs, or one or more DUs.
  • a network node 110 may include, for example, an NR network node, an LTE network node, a Node B, an eNB (for example, in 4G) , a gNB (for example, in 5G) , an access point, or a transmission reception point (TRP) , a DU, an RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, and/or a RAN node.
  • the network nodes 110 may be interconnected to one another or to one or more other network nodes 110 in the wireless network 100 through various types of fronthaul, midhaul, or backhaul interfaces, such as a direct physical connection, an air interface, or a virtual network, using any suitable transport network.
  • Each network node 110 may provide communication coverage for a particular geographic area.
  • the term “cell” can refer to a coverage area of a network node 110 or a network node subsystem serving this coverage area, depending on the context in which the term is used.
  • a network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, or another type of cell.
  • a macro cell may cover a relatively large geographic area (for example, several kilometers in radius) and may allow unrestricted access by UEs 120 with service subscriptions.
  • a pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscription.
  • a femto cell may cover a relatively small geographic area (for example, a home) and may allow restricted access by UEs 120 having association with the femto cell (for example, UEs 120 in a closed subscriber group (CSG) ) .
  • CSG closed subscriber group
  • a network node 110 for a macro cell may be referred to as a macro network node.
  • a network node 110 for a pico cell may be referred to as a pico network node.
  • a network node 110 for a femto cell may be referred to as a femto network node or an in-home network node.
  • the wireless network 100 may be a heterogeneous network that includes network nodes 110 of different types, such as macro network nodes, pico network nodes, femto network nodes, or relay network nodes. These different types of network nodes 110 may have different transmit power levels, different coverage areas, or different impacts on interference in the wireless network 100.
  • macro network nodes may have a high transmit power level (for example, 5 to 40 watts) whereas pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (for example, 0.1 to 2 watts) .
  • the network node 110a may be a macro network node for a macro cell 102a
  • the network node 110b may be a pico network node for a pico cell 102b
  • the network node 110c may be a femto network node for a femto cell 102c.
  • a network node may support one or multiple (for example, three) cells.
  • a cell may not necessarily be stationary, and the geographic area of the cell may move in accordance with the location of a network node 110 that is mobile (for example, a mobile network node) .
  • base station or “network node” may refer to an aggregated base station, a disaggregated base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof.
  • base station or “network node” may refer to a CU, a DU, an RU, a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) , and/or a Non-Real Time (Non-RT) RIC.
  • base station or “network node” may refer to one device configured to perform one or more functions, such as those described herein in connection with the network node 110.
  • the terms “base station” or “network node” may refer to a plurality of devices configured to perform the one or more functions. For example, in some distributed systems, each of a quantity of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to duplicate performance of at least a portion of the function, and the terms “base station” or “network node” may refer to any one or more of those different devices.
  • the terms “base station” or “network node” may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device.
  • the terms “base station” or “network node” may refer to one of the base station functions and not another. In this way, a single device may include more than one base station.
  • a network controller 130 may couple to or communicate with a set of network nodes 110 and may provide coordination and control for these network nodes 110.
  • the network controller 130 may communicate with the network nodes 110 via a backhaul communication link.
  • the network nodes 110 may communicate with one another directly or indirectly via a wireless or wireline backhaul communication link.
  • the network controller 130 may be a CU or a core network device, or the network controller 130 may include a CU or a core network device.
  • a cell may not necessarily be stationary, and the geographic area of the cell may move in accordance with the location of a network node 110 that is mobile (for example, a mobile network node) .
  • the network nodes 110 may be interconnected to one another or to one or more other network nodes 110 or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces, such as a direct physical connection or a virtual network, using any suitable transport network.
  • the wireless network 100 may include one or more relay stations.
  • a relay station is an entity that can receive a transmission of data from an upstream station (for example, a network node 110 or a UE 120) and send a transmission of the data to a downstream station (for example, a UE 120 or a network node 110) .
  • a relay station may be a UE 120 that can relay transmissions for other UEs 120.
  • the network node 110d (for example, a relay network node) may communicate with the network node 110a (for example, a macro network node) and the UE 120d in order to facilitate communication between the network node 110a and the UE 120d.
  • a network node 110 that relays communications may be referred to as a relay station, a relay network node, or a relay.
  • the UEs 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile.
  • a UE 120 may include, for example, an access terminal, a terminal, a mobile station, or a subscriber unit.
  • a UE 120 may be a cellular phone (for example, a smart phone) , a personal digital assistant (PDA) , a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (for example, a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (for example, a smart ring or a smart bracelet) ) , an entertainment device (for example, a music device, a video device, or a satellite radio) , a vehicular component or sensor, a smart
  • Some UEs 120 may be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs.
  • An MTC UE or an eMTC UE may include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor, or a location tag, that may communicate with a network node, another device (for example, a remote device) , or some other entity.
  • Some UEs 120 may be considered Internet-of-Things (IoT) devices, or may be implemented as NB-IoT (narrowband IoT) devices.
  • Some UEs 120 may be considered a Customer Premises Equipment.
  • a UE 120 may be included inside a housing that houses components of the UE 120, such as processor components or memory components.
  • the processor components and the memory components may be coupled together.
  • the processor components for example, one or more processors
  • the memory components for example, a memory
  • the processor components and the memory components may be operatively coupled, communicatively coupled, electronically coupled, or electrically coupled.
  • any quantity of wireless networks 100 may be deployed in a given geographic area.
  • Each wireless network 100 may support a particular RAT and may operate on one or more frequencies.
  • a RAT may be referred to as a radio technology or an air interface.
  • a frequency may be referred to as a carrier or a frequency channel.
  • Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs.
  • NR or 5G RAT networks may be deployed.
  • two or more UEs 120 may communicate directly using one or more sidelink channels (for example, without using a network node 110 as an intermediary to communicate with one another) .
  • the UEs 120 may communicate using peer-to-peer (P2P) communications, device-to-device (D2D) communications, a vehicle-to-everything (V2X) protocol (for example, which may include a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, or a vehicle-to-pedestrian (V2P) protocol) , or a mesh network.
  • V2X vehicle-to-everything
  • a UE 120 may perform scheduling operations, resource selection operations, or other operations described elsewhere herein as being performed by the network node 110.
  • Devices of the wireless network 100 may communicate using the electromagnetic spectrum, which may be subdivided by frequency or wavelength into various classes, bands, or channels.
  • devices of the wireless network 100 may communicate using one or more operating bands.
  • two initial operating bands have been identified as frequency range designations FR1 (410 MHz –7.125 GHz) and FR2 (24.25 GHz –52.6 GHz) .
  • FR1 frequency range designations FR1 (410 MHz –7.125 GHz)
  • FR2 24.25 GHz –52.6 GHz)
  • FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in various documents and articles.
  • FR2 which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz – 300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.
  • EHF extremely high frequency
  • ITU International Telecommunications Union
  • FR3 7.125 GHz –24.25 GHz
  • FR3 7.125 GHz –24.25 GHz
  • Frequency bands falling within FR3 may inherit FR1 characteristics or FR2 characteristics, and thus may effectively extend features of FR1 or FR2 into mid-band frequencies.
  • higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz.
  • FR4a or FR4-1 52.6 GHz –71 GHz
  • FR4 52.6 GHz –114.25 GHz
  • FR5 114.25 GHz –300 GHz
  • sub-6 GHz may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies.
  • millimeter wave if used herein, may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-aor FR4-1, or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (for example, FR1, FR2, FR3, FR4, FR4-a, FR4-1, or FR5) may be modified, and techniques described herein are applicable to those modified frequency ranges.
  • the UE 120 may include a communication manager 140.
  • the communication manager 140 may receive, while the UE 120 is in an RRC connected state, a grant for a transmission that is to occur at a grant time; receive, while the UE 120 is in the RRC connected state, a paging message; and delay, while an inactive interval associated with the UE 120 does not satisfy a configurable inactive interval threshold, release of the RRC connected state. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.
  • FIG. 2 is a diagram illustrating an example network node in communication with a UE in a wireless network in accordance with the present disclosure.
  • the network node may correspond to the network node 110 of Figure 1.
  • the UE may correspond to the UE 120 of Figure 1.
  • the network node 110 may be equipped with a set of antennas 234a through 234t, such as T antennas (T ⁇ 1) .
  • the UE 120 may be equipped with a set of antennas 252a through 252r, such as R antennas (R ⁇ 1) .
  • the network node 110 of depicted in Figure 2 includes one or more radio frequency components, such as antennas 234 and a modem 232.
  • a network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include radio frequency components that facilitate direct communication with the UE 120, such as one or more CUs, or one or more DUs.
  • a transmit processor 220 may receive data, from a data source 212, intended for the UE 120 (or a set of UEs 120) .
  • the transmit processor 220 may select one or more modulation and coding schemes (MCSs) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from that UE 120.
  • MCSs modulation and coding schemes
  • CQIs channel quality indicators
  • the network node 110 may process (for example, encode and modulate) the data for the UE 120 based at least in part on the MCS (s) selected for the UE 120 and may provide data symbols for the UE 120.
  • the transmit processor 220 may process system information (for example, for semi-static resource partitioning information (SRPI)) and control information (for example, CQI requests, grants, or upper layer signaling) and provide overhead symbols and control symbols.
  • the transmit processor 220 may generate reference symbols for reference signals (for example, a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS) ) and synchronization signals (for example, a primary synchronization signal (PSS) or a secondary synchronization signal (SSS) ) .
  • reference signals for example, a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS)
  • synchronization signals for example, a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)
  • a transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (for example, precoding) on the data symbols, the control symbols, the overhead symbols, or the reference symbols, if applicable, and may provide a set of output symbol streams (for example, T output symbol streams) to a corresponding set of modems 232 (for example, T modems) , shown as modems 232a through 232t.
  • each output symbol stream may be provided to a modulator component (shown as MOD) of a modem 232.
  • Each modem 232 may use a respective modulator component to process a respective output symbol stream (for example, for OFDM) to obtain an output sample stream.
  • Each modem 232 may further use a respective modulator component to process (for example, convert to analog, amplify, filter, or upconvert) the output sample stream to obtain a downlink signal.
  • the modems 232a through 232t may transmit a set of downlink signals (for example, T downlink signals) via a corresponding set of antennas 234 (for example, T antennas) , shown as antennas 234a through 234t.
  • a set of antennas 252 may receive the downlink signals from the network node 110 or other network nodes 110 and may provide a set of received signals (for example, R received signals) to a set of modems 254 (for example, R modems) , shown as modems 254a through 254r.
  • each received signal may be provided to a demodulator component (shown as DEMOD) of a modem 254.
  • DEMOD demodulator component
  • Each modem 254 may use a respective demodulator component to condition (for example, filter, amplify, downconvert, or digitize) a received signal to obtain input samples.
  • Each modem 254 may use a demodulator component to further process the input samples (for example, for OFDM) to obtain received symbols.
  • a MIMO detector 256 may obtain received symbols from the modems 254, may perform MIMO detection on the received symbols if applicable, and may provide detected symbols.
  • a receive processor 258 may process (for example, demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to a data sink 260, and may provide decoded control information and system information to a controller/processor 280.
  • controller/processor may refer to one or more controllers and/or one or more processors.
  • a channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, or a CQI parameter, among other examples.
  • RSRP reference signal received power
  • RSSI received signal strength indicator
  • RSSRQ reference signal received quality
  • CQI CQI parameter
  • the network controller 130 may include a communication unit 294, a controller/processor 290, and a memory 292.
  • the network controller 130 may include, for example, one or more devices in a core network.
  • the network controller 130 may communicate with the network node 110 via the communication unit 294.
  • One or more antennas may include, or may be included within, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, among other examples.
  • An antenna panel, an antenna group, a set of antenna elements, or an antenna array may include one or more antenna elements (within a single housing or multiple housings) , a set of coplanar antenna elements, a set of non- coplanar antenna elements, or one or more antenna elements coupled to one or more transmission or reception components, such as one or more components of Figure 2.
  • a transmit processor 264 may receive and process data from a data source 262 and control information (for example, for reports that include RSRP, RSSI, RSRQ, or CQI) from the controller/processor 280.
  • the transmit processor 264 may generate reference symbols for one or more reference signals.
  • the symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266 if applicable, further processed by the modems 254 (for example, for DFT-s-OFDM or CP-OFDM) , and transmitted to the network node 110.
  • the modem 254 of the UE 120 may include a modulator and a demodulator.
  • the UE 120 includes a transceiver.
  • the transceiver may include any combination of the antenna (s) 252, the modem (s) 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, or the TX MIMO processor 266.
  • the transceiver may be used by a processor (for example, the controller/processor 280) and the memory 282 to perform aspects of any of the methods described herein.
  • the uplink signals from UE 120 or other UEs may be received by the antennas 234, processed by the modem 232 (for example, a demodulator component, shown as DEMOD, of the modem 232) , detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by the UE 120.
  • the receive processor 238 may provide the decoded data to a data sink 239 and provide the decoded control information to the controller/processor 240.
  • the network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244.
  • the network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink or uplink communications.
  • the modem 232 of the network node 110 may include a modulator and a demodulator.
  • the network node 110 includes a transceiver.
  • the transceiver may include any combination of the antenna (s) 234, the modem (s) 232, the MIMO detector 236, the receive processor 238, the transmit processor 220, or the TX MIMO processor 230.
  • the transceiver may be used by a processor (for example, the controller/processor 240) and the memory 242 to perform aspects of any of the methods described herein.
  • the controller/processor 240 of the network node 110, the controller/processor 280 of the UE 120, or any other component (s) of Figure 2 may perform one or more techniques associated with handling a paging message using an inactive interval, as described in more detail elsewhere herein.
  • the controller/processor 240 of the network node 110, the controller/processor 280 of the UE 120, or any other component (s) of Figure 2 may perform or direct operations of, for example, process 700 of Figure 7 or other processes as described herein.
  • the memory 242 and the memory 282 may store data and program codes for the network node 110 and the UE 120, respectively.
  • the memory 242 or the memory 282 may include a non-transitory computer-readable medium storing one or more instructions (for example, code or program code) for wireless communication.
  • the one or more instructions when executed (for example, directly, or after compiling, converting, or interpreting) by one or more processors of the network node 110 or the UE 120, may cause the one or more processors, the UE 120, or the network node 110 to perform or direct operations of, for example, process 700 of Figure 7 or other processes as described herein.
  • executing instructions may include running the instructions, converting the instructions, compiling the instructions, or interpreting the instructions, among other examples.
  • the UE 120 includes means for receiving, while the UE 120 is in an RRC connected state, a grant for a transmission that is to occur at a grant time; means for receiving, while the UE 120 is in the RRC connected state, a paging message; and/or means for delaying, while an inactive interval associated with the UE 120 does not satisfy a configurable inactive interval threshold, release of the RRC connected state.
  • the means for the UE 120 to perform operations described herein may include, for example, one or more of communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller/processor 280, or memory 282.
  • Deployment of communication systems may be arranged in multiple manners with various components or constituent parts.
  • a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station, or a network equipment may be implemented in an aggregated or disaggregated architecture.
  • a base station such as a Node B (NB) , an evolved NB (eNB) , an NR base station, a 5G NB, an access point (AP) , a TRP, or a cell, among other examples
  • NB Node B
  • eNB evolved NB
  • AP access point
  • TRP TRP
  • a cell a cell
  • a base station such as a Node B (NB) , an evolved NB (eNB) , an NR base station, a 5G NB, an access point (AP) , a TRP, or a cell, among other examples
  • a base station such as a Node B (NB) , an evolved NB (eNB) , an NR base station, a 5G NB, an access point (AP) , a TRP, or a cell, among other examples
  • AP access point
  • TRP TRP
  • a cell a cell, among other examples
  • Network entity or “network node”
  • An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (for example, within a single device or unit) .
  • a disaggregated base station (for example, a disaggregated network node) may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more CUs, one or more DUs, or one or more RUs) .
  • a CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed throughout one or multiple other network nodes.
  • the DUs may be implemented to communicate with one or more RUs.
  • Each of the CU, DU, and RU also can be implemented as virtual units, such as a virtual central unit (VCU) , a virtual distributed unit (VDU) , or a virtual radio unit (VRU) , among other examples.
  • VCU virtual central unit
  • VDU virtual distributed unit
  • VRU virtual radio unit
  • Base station-type operation or network design may consider aggregation characteristics of base station functionality.
  • disaggregated base stations may be utilized in an IAB network, an open radio access network (O-RAN (such as the network configuration sponsored by the O-RAN Alliance) ) , or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN) ) to facilitate scaling of communication systems by separating base station functionality into one or more units that can be individually deployed.
  • a disaggregated base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented for at least one unit virtually, which can enable flexibility in network design.
  • the various units of the disaggregated base station can be configured for wired or wireless communication with at least one other unit of the disaggregated base station.
  • FIG. 3 is a diagram illustrating an example disaggregated base station architecture 300 in accordance with the present disclosure.
  • the disaggregated base station architecture 300 may include a CU 310 that can communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated control units (such as a Near-RT RIC 325 via an E2 link, or a Non-RT RIC 315 associated with a Service Management and Orchestration (SMO) Framework 305, or both) .
  • a CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as through F1 interfaces.
  • Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links.
  • Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links.
  • RF radio frequency
  • Each of the units may include one or more interfaces or be coupled with one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium.
  • Each of the units, or an associated processor or controller providing instructions to one or multiple communication interfaces of the respective unit, can be configured to communicate with one or more of the other units via the transmission medium.
  • each of the units can include a wired interface, configured to receive or transmit signals over a wired transmission medium to one or more of the other units, and a wireless interface, which may include a receiver, a transmitter or transceiver (such as a RF transceiver) , configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.
  • a wireless interface which may include a receiver, a transmitter or transceiver (such as a RF transceiver) , configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.
  • the CU 310 may host one or more higher layer control functions.
  • control functions can include RRC functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, among other examples.
  • Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 310.
  • the CU 310 may be configured to handle user plane functionality (for example, Central Unit –User Plane (CU-UP) functionality) , and/or control plane functionality (for example, Central Unit –Control Plane (CU-CP) functionality) .
  • CU-UP Central Unit –User Plane
  • CU-CP Central Unit –Control Plane
  • the CU 310 can be logically split into one or more CU-UP units and one or more CU-CP units.
  • a CU-UP unit can communicate bidirectionally with a CU-CP unit via an interface, such as the E1 interface when implemented in an O-RAN configuration.
  • the CU 310 can be implemented to communicate with a DU 330, as necessary, for network control and signaling.
  • Each DU 330 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 340.
  • the DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers depending, at least in part, on a functional split, such as a functional split defined by the 3GPP.
  • the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, and modulation and demodulation, among other examples.
  • FEC forward error correction
  • the DU 330 may further host one or more low PHY layers, such as implemented by one or more modules for a fast Fourier transform (FFT) , an inverse FFT (iFFT) , digital beamforming, or physical random access channel (PRACH) extraction and filtering, among other examples.
  • FFT fast Fourier transform
  • iFFT inverse FFT
  • PRACH physical random access channel
  • Each layer (which also may be referred to as a module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 330, or with the control functions hosted by the CU 310.
  • Each RU 340 may implement lower-layer functionality.
  • an RU 340, controlled by a DU 330 may correspond to a logical node that hosts RF processing functions or low-PHY layer functions, such as performing an FFT, performing an iFFT, digital beamforming, or PRACH extraction and filtering, among other examples, based on or otherwise associated with a functional split (for example, a functional split defined by the 3GPP) , such as a lower layer functional split.
  • a functional split for example, a functional split defined by the 3GPP
  • each RU 340 can be operated to handle over the air (OTA) communication with one or more UEs 120.
  • OTA over the air
  • real-time and non-real-time aspects of control and user plane communication with the RU (s) 340 can be controlled by the corresponding DU 330.
  • this configuration can enable each DU 330 and the CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.
  • the SMO Framework 305 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements.
  • the SMO Framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operations and maintenance interface (such as an O1 interface) .
  • the SMO Framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface) .
  • a cloud computing platform such as an open cloud (O-Cloud) platform 390
  • network element life cycle management such as to instantiate virtualized network elements
  • a cloud computing platform interface such as an O2 interface
  • Such virtualized network elements can include, but are not limited to, CUs 310, DUs 330, RUs 340, non-RT RICs 315, and Near-RT RICs 325.
  • the SMO Framework 305 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 311, via an O1 interface. Additionally, in some implementations, the SMO Framework 305 can communicate directly with each of one or more RUs 340 via a respective O1 interface.
  • the SMO Framework 305 also may include a Non-RT RIC 315 configured to support functionality of the SMO Framework 305.
  • the Non-RT RIC 315 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, Artificial Intelligence/Machine Learning (AI/ML) workflows including model training and updates, or policy-based guidance of applications/features in the Near-RT RIC 325.
  • the Non-RT RIC 315 may be coupled to or communicate with (such as via an A1 interface) the Near-RT RIC 325.
  • the Near-RT RIC 325 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 310, one or more DUs 330, or both, as well as an O-eNB, with the Near-RT RIC 325.
  • the Non-RT RIC 315 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 325 and may be received at the SMO Framework 305 or the Non-RT RIC 315 from non-network data sources or from network functions. In some examples, the Non-RT RIC 315 or the Near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 315 may monitor long-term trends and patterns for performance and employ AI/ML models to perform corrective actions through the SMO Framework 305 (such as reconfiguration via an O1 interface) or via creation of RAN management policies (such as A1 interface policies) .
  • Figure 4 is a diagram illustrating an example 400 associated with paging messages in accordance with the present disclosure. As shown in Figure 4, a UE 410 and a network node 420 may communicate with one another.
  • a network node 420 may output, and a UE 410 may receive, a paging message.
  • a purpose of this procedure may be to transmit paging information to a UE (for example, UE 410) in RRC idle state ( “RRC_IDLE” ) or RRC inactive state ( “RRC_INACTIVE” ) .
  • a purpose of this procedure may be to transmit paging information for a Layer 2 (L2) UE-to-network (U2N) remote UE in RRC_IDLE state or RRC_INACTIVE state to a serving L2 U2N relay UE (for example, UE 410) in any RRC state.
  • L2 Layer 2
  • U2N UE-to-network
  • the UE 410 may be in RRC connected state ( “RRC_CONNECTED” ) or in RRC_INACTIVE state. If no RRC connection has been established, then the UE 410 may be in RRC_IDLE state.
  • RRC_CONNECTED state may be characterized as follows.
  • the UE 410 may store access stratum (AS) context.
  • RRC_CONNECTED state may support transfer of unicast data to/from the UE 410 and/or transfer of multicast and broadcast services (MBS) multicast data to the UE 410.
  • the UE 410 may be configured with a UE specific discontinuous reception (DRX) .
  • the UE may be configured with a DRX for point-to-multipoint (PTM) transmission of MBS broadcast and/or a DRX for MBS multicast.
  • PTM point-to-multipoint
  • RRC_CONNECTED state may support use of one or more secondary cells (Scells) , aggregated with a special cell (SpCell) , for increased bandwidth.
  • Scells secondary cells
  • SpCell special cell
  • RRC_CONNECTED state may support use of one secondary cell group (SCG) , aggregated with the main cell group (MCG) , for increased bandwidth.
  • SCG secondary cell group
  • MCG main cell group
  • network-controlled mobility may be available within NR, to/from evolved universal mobile telecommunication system (UMTS) terrestrial radio access (E-UTRA) , and to UMTS terrestrial radio access (UTRA) frequency division duplex (UTRA-FDD) .
  • network-controlled mobility (for example, path switch) may be available between a serving cell and a L2 U2N Relay UE, or vice versa.
  • the UE 410 may monitor control channels associated with the shared data channel to determine if data is scheduled for the UE 410, provide channel quality and feedback information, perform neighboring cell measurements and measurement reporting, acquire system information, perform immediate minimization of drive test (MDT) measurements together with available location reporting, and/or, if configured by upper layers for MBS broadcast reception, acquire MBS control channel (MCCH) change notifications and MBS broadcast control information and data.
  • MDT drive test
  • MCCH MBS control channel
  • the UE 410 may monitor short messages transmitted with P-RNTI over DCI, if configured.
  • a UE may monitor the P-RNTI over DCI during an RRC connected state for only short messages. Therefore, it is unexpected for theUE to receive a paging message scheduled by P-RNTI over DCI in the RRC connected state.
  • a network can send a paging message to an RRC connected UE.
  • the network sending the paging message while the UE is in the RRC connected state may indicate that the network and the UE are unsynchronized.
  • the network sending the paging message while the UE is in the RRC connected state may indicate that the network has identified the UE as not being in an RRC connected state (for example, the network has identified the UE as being in an RRC idle state or in an RRC inactive state) .
  • the paging message may prompt the UE to blindly perform a connection release (for example, a local RRC connection release) , move to RRC idle state, and re-try a registration procedure to re-synchronize with network (for example, such that the network identifies the UE as being in an RRC connected state when the UE is in the RRC connected state) .
  • a connection release for example, a local RRC connection release
  • RRC idle state for example, a registration procedure to re-synchronize with network
  • network for example, such that the network identifies the UE as being in an RRC connected state when the UE is in the RRC connected state
  • the paging message may have been sent in error.
  • the network may send the paging message even though the network and the UE are synchronized (for example, even though the network has identified the UE as being in an RRC connected state) .
  • the UE may blindly address (for example, process) the paging message by triggering the connection release (for example, a radio link failure (RLF) procedure) .
  • the UE may switch to RRC idle state to re-synchronize with the network via a non-access stratum (NAS) triggering registration request.
  • NAS non-access stratum
  • Performing a local RRC connection release in response to a paging message sent in error may interrupt an RRC connection. For example, receiving an erroneous paging message during an active VoNR voice call can prompt the UE to blindly release the RRC connection, thereby interrupting the voice call.
  • the local RRC connection release may cause intermittent voice breaks, silence during the call, delays, or call drops, among other examples. Such interruptions may degrade overall user experience.
  • Various aspects relate generally to handling of paging messages. Some aspects more specifically relate to delaying release of an RRC connection in response to a paging message received by a UE in an RRC connected state.
  • the UE monitors how long the network has been inactive and, after a configurable amount of time, releases the RRC connection.
  • the UE may receive a grant from the network before the configurable amount of time has elapsed, and the UE may ignore the paging message (for example, the UE may determine not to release the RRC connection at any point in response to the paging message) .
  • the UE may not receive a grant from the network before the configurable amount of time has elapsed, and the UE may release the RRC connection.
  • the described techniques can be used to enable the UE to delay release of an RRC connected state in case the paging message was sent in error, thereby preventing interruptions in service.
  • a UE in an RRC connected state may preserve an ongoing voice over VoLTE call and associated call performance, LTE data traffic, an ongoing VoNR call and associated call performance, NR data traffic, an ongoing 6G voice call and associated call performance, 6G data traffic, or the like.
  • the UE receiving the grant from the network within the configurable amount of time may indicate that the network and the UE are synchronized (for example, the paging message was sent in error) , and, therefore, the UE may maintain the existing RRC connection.
  • the UE not receiving any more grants from the network within the configurable amount of time may indicate that the network and the UE are not synchronized (for example, the connection with the UE may have already been released at the network side due to the UE and the network becoming unsynchronized) , and, therefore, the UE may release the RRC connection and re-register with the network to re-synchronize with the network.
  • the UE may differentiate between, and handle differently, erroneous paging messages and paging message sent because the network and the UE are not synchronized.
  • the configurable amount of time may be configured to enable earlier re-synchronization with the network (for example, by shortening the configurable amount of time) .
  • Figure 5 is a diagram illustrating an example 500 associated with handling a paging message received during an RRC connected state in accordance with the present disclosure. As shown in Figure 5, a network node 110 and a UE 120 may communicate with one another.
  • the network node 110 may output, and the UE 120 may receive, while the UE 120 is in an RRC connected state, a grant for a transmission that is to occur at a grant time.
  • the grant may be an uplink grant for an uplink transmission, or the grant may be a downlink grant for a downlink transmission.
  • the grant time may be the time at which the UE 120 is to send the uplink transmission or receive the downlink transmission.
  • the transmission may be associated with one or more of voice traffic (for example, VoNR traffic) or data traffic.
  • the network node 110 may output, and the UE 120 may receive, while the UE 120 is in an RRC connected state, a paging message.
  • the network node 110 may output the paging message because the network node 110 and the UE 120 are not synchronized.
  • the network node 110 may output the paging message erroneously (for example, the network node 110 may output the paging message even though the network node 110 and the UE 120 are synchronized) .
  • the UE 120 may delay, while an inactive interval associated with the UE 120 does not satisfy a configurable inactive interval threshold, release of the RRC connected state.
  • the inactive interval may be a length of time for which the network node 110 is inactive with respect to the UE 120. For example, while the inactive interval is less than the configurable inactive interval threshold, the UE 120 may delay release of the RRC connected state. For example, the UE 120 may refrain from performing a local RRC connection release procedure associated with the paging message.
  • the configurable inactive interval threshold may be any suitable configurable value (e.g., five or ten seconds) .
  • the UE 120 may make a voice or traffic call, cease receiving cell radio network temporary identifier (C-RNTI) DCI grants, and then receive a paging message before the inactive interval reaches the configurable inactive interval threshold. Instead of immediately releasing the connection (and triggering a registration procedure) in response to the paging message, the UE 120 may wait to determine whether to release the connection (and trigger the registration procedure) in response to the paging message. For example, if the UE 120 receives a C-RNTI DCI grant before the inactive interval reaches the configurable inactive interval threshold, then the paging message was sent in error and the UE 120 may continue service without triggering a connection release.
  • C-RNTI cell radio network temporary identifier
  • the UE 120 does not receive a C-RNTI DCI grant before the inactive interval reaches the configurable inactive interval threshold, then the UE 120 and the network node 110 are unsynchronized and the UE 120 may release the connection after the inactive interval reaches the configurable inactive interval threshold and trigger a registration procedure.
  • Delaying release of the RRC connected state while the inactive interval does not satisfy the configurable inactive interval threshold may enable the UE 120 to delay release of the RRC connected state in case the paging message was sent in error, thereby preventing interruptions to the RRC connection.
  • the UE 120 may (for example, at L2 and/or layer 3 (L3) distinguish between, and handle accordingly, MT paging messages in scenarios where the network node 110 outputs the paging message because the network node 110 and the UE 120 are not synchronized (for example, when the inactive interval exceeds the configurable inactive interval threshold) and scenarios where the network node 110 outputs the paging message erroneously (for example, when the inactive interval is smaller than the configurable inactive interval threshold) .
  • L3 layer 3
  • the configurable inactive interval threshold may be configured with any suitable value, such as a smallest value that enables the UE 120 to distinguish between the scenarios discussed above, which may enable the UE 120 to quickly synchronize with the network node 110 by triggering local release procedures in response to the inactive interval exceeding the configurable inactive interval threshold.
  • the timer for example, a length of time for the inactive interval to exceed the configurable inactive interval threshold
  • the UE 120 may help to guarantee that data is forwarded appropriately.
  • the UE 120 may prevent interruptions to a voice call.
  • the UE 120 may prevent interruptions to a traffic call. Refraining from performing the local RRC connection release procedure may enable the UE 120 to delay release of the RRC connected state.
  • the inactive interval is associated with a difference between a current time and the grant time.
  • the UE 120 may determine that the inactive interval extends from the grant time to the current time.
  • the grant time may correspond to the time at which a most recent transmission (for example, uplink transmission or downlink transmission) , associated with a given C-RNTI, was sent by, or received at, the UE 120.
  • inactive interval (current time) – (last uplink or downlink data associated with the C-RNTI) .
  • the UE 120 may monitor the inactive interval as the current time changes (for example, the UE 120 may monitor the inactive interval over time) .
  • Associating the inactive interval with a difference between a current time and the grant time may enable the UE 120 to determine how long the network node 110 (for example, cell) has been inactive for, which may enable the UE 120 to determine whether to ignore the paging message (for example, in case the network node 110 and the UE 120 are synchronized) or to perform the local RRC connection release procedure (for example, in case the network node 110 and the UE 120 are unsynchronized) .
  • the current time may be a time at which the UE 120 receives the paging message.
  • the UE 120 may determine the inactive interval upon receiving the paging message.
  • the UE 120 may determine the inactive interval between the current time (for example, the time at which the paging message was received) and the last C-RNTI DCI grant time. If the inactive interval is less than the configurable inactive interval threshold, then the paging message may have been sent in error and the UE 120 does not immediately release the RRC connection.
  • the UE 120 and the network node 110 may be synchronized (for example, and the paging message may be erroneous and the UE 120 may remain in the RRC connected state) . If the most recent C-RNTI grant was received 76.5 ms before the paging message, then the UE 120 and the network node 110 may or may not be synchronized, depending on the configurable inactive interval threshold.
  • the UE 120 and the network node 110 may not be synchronized (for example, and the paging message may not be erroneous and the UE 120 may not remain in the RRC connected state) .
  • the current time being the time at which the UE 120 receives the paging message may enable the UE 120 to determine, with minimal or no delay from when the paging message is received, whether to ignore the paging message (for example, in case the network node 110 and the UE 120 are synchronized) or to perform the local RRC connection release procedure (for example, in case the network node 110 and the UE 120 are unsynchronized) .
  • performing the local RRC connection release procedure may enable the UE 120 to re-establish an RRC connection with minimal or no delay.
  • the UE 120 may receive, while the inactive interval does not satisfy the configurable inactive interval threshold, another grant for another transmission that is to occur at another grant time.
  • the other grant may be another uplink grant for another uplink transmission, or the other grant may be another downlink grant for another downlink transmission.
  • the other grant time may be a time at which the UE 120 is to send the other uplink transmission or receive the other downlink transmission.
  • the UE 120 may receive the other grant before the inactive interval exceeds the configurable inactive interval threshold. In some examples, the UE 120 may ignore the paging message.
  • the UE 120 may determine that the UE 120 is not, at any time, to perform a local RRC connection release procedure due to the UE 120 receiving the paging message. Thus, if the UE 120 receives any C-RNTI DCI grant before the inactive interval reaches the configurable inactive interval threshold, then the UE 120 and the network node 110 may be synchronized, and the UE 120 may reset the inactive interval and ignore the paging message.
  • the UE 120 receiving the other grant while the inactive interval does not satisfy the configurable inactive interval threshold may indicate that the paging message was sent erroneously (for example, the network node 110 and the UE 120 are synchronized) .
  • the UE 120 ignoring the paging message may enable the UE 120 to delay release of the RRC connected state before the inactive interval reaches the configurable inactive interval threshold, which may reduce interruptions to the RRC connection.
  • the UE 120 may determine that the inactive interval satisfies the configurable inactive interval threshold. For example, the UE 120 may determine that the inactive interval has exceeded the configurable inactive interval threshold. For example, the UE 120 may determine that no other grants have been received since the grant received with reference to operation 510.
  • the UE 120 may perform a local RRC connection release procedure and a follow-up registration procedure. For example, the UE 120 may release the RRC connection and establish another RRC connection with the network node 110. Thus, if the inactive interval reaches the configurable inactive interval threshold, then the UE 120 and the network node 110 may be unsynchronized, and the UE 120 may perform the local RRC connection release and retry registration with the network node 110.
  • the UE 120 determining that the inactive interval satisfies the configurable inactive interval threshold may indicate that the paging message was not sent erroneously (for example, the network node 110 and the UE 120 are not synchronized) .
  • the UE 120 performing the local RRC connection release procedure and the follow-up registration procedure may enable the UE 120 to re-synchronize with the network node 110.
  • Figure 6 is a diagram illustrating an example 600 associated with determining how to handle a paging message received during an RRC connected state in accordance with the present disclosure.
  • a UE may receive a page in a connected mode.
  • the UE may receive a paging message while the UE is in an RRC connected state.
  • the UE may determine an inactive interval as a difference between the current time (for example, a time at which the paging message was received) and a last C-RNTI time (for example, the most recent grant time) .
  • the UE may determine whether the inactive interval exceeds the configurable inactive activity threshold. If the inactive interval exceeds the configurable inactive activity threshold (for example, if the UE and the network node are unsynchronized) , then, in a third operation 630, the UE may perform a local connection release (for example, a local RRC connection release) . The UE may also trigger registration (for example, the UE may re-register with the network node) . In a fourth operation 640, the UE may continue service.
  • a local connection release for example, a local RRC connection release
  • the UE may also trigger registration (for example, the UE may re-register with the network node) .
  • the UE may continue service.
  • the UE may wait for a next slot.
  • the UE may determine whether a C-RNTI has been received. For example, the UE may determine whether a grant has been received in the next slot. If the C-RNTI was received, (for example, if the paging message was sent in error) , then, in a seventh operation 670, the UE may reset the inactive interval and, in the fourth operation 640, the UE may continue service. For example, the UE may continue service without performing the local connection release.
  • the UE may determine whether the inactive interval exceeds the configurable inactive activity threshold. If the inactive interval does not exceed the configurable inactive activity threshold (for example, if the paging message was potentially sent in error) , then, the UE may return to the fifth operation 650 (for example, the UE may wait for a next slot) . If the inactive interval exceeds the configurable inactive activity threshold (for example, if the UE and the network node are unsynchronized) , then, in the third operation 630, the UE may perform the local connection release and trigger registration and, in the fourth operation 640, continue service.
  • FIG. 7 is a flowchart illustrating an example process 700 performed, for example, by a UE that supports handling a paging message using an inactive interval in accordance with the present disclosure.
  • Example process 700 is an example where the UE (for example, UE 120) performs operations associated with an inactive interval for handling of a paging message.
  • process 700 may include receiving, while the UE is in an RRC connected state, a grant for a transmission that is to occur at a grant time (block 710) .
  • the UE (such as by using communication manager 140 or reception component 802, depicted in Figure 8) may receive, while the UE is in an RRC connected state, a grant for a transmission that is to occur at a grant time, as described above.
  • process 700 may include receiving, while the UE is in the RRC connected state, a paging message (block 720) .
  • the UE (such as by using communication manager 140 or reception component 802, depicted in Figure 8) may receive, while the UE is in the RRC connected state, a paging message, as described above.
  • process 700 may include delaying, while an inactive interval associated with the UE does not satisfy a configurable inactive interval threshold, release of the RRC connected state (block 730) .
  • the UE (such as by using communication manager 140 or delaying component 808, depicted in Figure 8) may delay, while an inactive interval associated with the UE does not satisfy a configurable inactive interval threshold, release of the RRC connected state, as described above.
  • Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below or in connection with one or more other processes described elsewhere herein.
  • delaying release of the RRC connected state includes refraining from performing a local RRC connection release procedure associated with the paging message.
  • the inactive interval is associated with a difference between a current time and the grant time.
  • the current time is a time at which the UE receives the paging message.
  • the grant is a first grant
  • the transmission is a first transmission
  • the grant time is a first grant time
  • process 700 further includes receiving, while the inactive interval does not satisfy the configurable inactive interval threshold, a second grant for a second transmission that is to occur at a second grant time, and ignoring the paging message.
  • process 700 includes determining that the inactive interval satisfies the configurable inactive interval threshold, and performing a local RRC connection release procedure and a follow-up registration procedure.
  • the transmission is associated with voice traffic.
  • the transmission is associated with data traffic.
  • process 700 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Figure 7. Additionally or alternatively, two or more of the blocks of process 700 may be performed in parallel.
  • FIG 8 is a diagram of an example apparatus 800 for wireless communication that supports handling a paging message using an inactive interval in accordance with the present disclosure.
  • the apparatus 800 may be a UE, or a UE may include the apparatus 800.
  • the apparatus 800 includes a reception component 802, a transmission component 804, and a communication manager 140, which may be in communication with one another (for example, via one or more buses) .
  • the apparatus 800 may communicate with another apparatus 806 (such as a UE, a network node, or another wireless communication device) using the reception component 802 and the transmission component 804.
  • another apparatus 806 such as a UE, a network node, or another wireless communication device
  • the apparatus 800 may be configured to and/or operable to perform one or more operations described herein in connection with Figures 5-6. Additionally or alternatively, the apparatus 800 may be configured to and/or operable to perform one or more processes described herein, such as process 700 of Figure 7. In some aspects, the apparatus 800 may include one or more components of the UE described above in connection with Figure 2.
  • the reception component 802 may receive communications, such as reference signals, control information, and/or data communications, from the apparatus 806.
  • the reception component 802 may provide received communications to one or more other components of the apparatus 800, such as the communication manager 140.
  • the reception component 802 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples) , and may provide the processed signals to the one or more other components.
  • the reception component 802 may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller/processor, and/or a memory of the UE described above in connection with Figure 2.
  • the transmission component 804 may transmit communications, such as reference signals, control information, and/or data communications, to the apparatus 806.
  • the communication manager 140 may generate communications and may transmit the generated communications to the transmission component 804 for transmission to the apparatus 806.
  • the transmission component 804 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) , and may transmit the processed signals to the apparatus 806.
  • the transmission component 804 may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, and/or a memory of the UE described above in connection with Figure 2. In some aspects, the transmission component 804 may be co-located with the reception component 802 in a transceiver.
  • the communication manager 140 may receive or may cause the reception component 802 to receive, while the UE is in an RRC connected state, a grant for a transmission that is to occur at a grant time.
  • the communication manager 140 may receive or may cause the reception component 802 to receive, while the UE is in the RRC connected state, a paging message.
  • the communication manager 140 may delay, while an inactive interval associated with the UE does not satisfy a configurable inactive interval threshold, release of the RRC connected state.
  • the communication manager 140 may perform one or more operations described elsewhere herein as being performed by one or more components of the communication manager 140.
  • the communication manager 140 may include a controller/processor and/or a memory, of the UE described above in connection with Figure 2.
  • the communication manager 140 includes a set of components, such as delaying component 808, an ignoring component 810, a determination component 812, and/or a performing component 814.
  • the set of components may be separate and distinct from the communication manager 140.
  • one or more components of the set of components may include or may be implemented within a controller/processor and/or a memory of the UE described above in connection with Figure 2.
  • one or more components of the set of components may be implemented at least in part as software stored in a memory.
  • a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component.
  • the reception component 802 may receive, while the UE is in an RRC connected state, a grant for a transmission that is to occur at a grant time.
  • the reception component 802 may receive, while the UE is in the RRC connected state, a paging message.
  • the delaying component 808 may delay, while an inactive interval associated with the UE does not satisfy a configurable inactive interval threshold, release of the RRC connected state.
  • the reception component 802 may receive, while the inactive interval does not satisfy the configurable inactive interval threshold, a second grant for a second transmission that is to occur at a second grant time.
  • the ignoring component 810 may ignore the paging message.
  • the determination component 812 may determine that the inactive interval satisfies the configurable inactive interval threshold.
  • the performing component 814 may perform a local RRC connection release procedure and a follow-up registration procedure.
  • FIG. 8 The quantity and arrangement of components shown in Figure 8 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Figure 8. Furthermore, two or more components shown in Figure 8 may be implemented within a single component, or a single component shown in Figure 8 may be implemented as multiple, distributed components. Additionally or alternatively, a set of (one or more) components shown in Figure 8 may perform one or more functions described as being performed by another set of components shown in Figure 8.
  • FIG 9 is a diagram of an example apparatus 900 for wireless communication that supports handling a paging message using an inactive interval in accordance with the present disclosure.
  • the apparatus 900 may be a network node, or a network node may include the apparatus 900.
  • the apparatus 900 includes a reception component 902, a transmission component 904, and a communication manager 150, which may be in communication with one another (for example, via one or more buses) .
  • the apparatus 900 may communicate with another apparatus 906 (such as a UE, a network node, or another wireless communication device) using the reception component 902 and the transmission component 904.
  • another apparatus 906 such as a UE, a network node, or another wireless communication device
  • the apparatus 900 may be configured to and/or operable to perform one or more operations described herein in connection with Figures 5-6. Additionally or alternatively, the apparatus 900 may be configured to and/or operable to perform one or more processes described herein. In some aspects, the apparatus 900 may include one or more components of the network node described above in connection with Figure 2.
  • the reception component 902 may receive communications, such as reference signals, control information, and/or data communications, from the apparatus 906.
  • the reception component 902 may provide received communications to one or more other components of the apparatus 900, such as the communication manager 150.
  • the reception component 902 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples) , and may provide the processed signals to the one or more other components.
  • the reception component 902 may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller/processor, and/or a memory of the network node described above in connection with Figure 2.
  • the transmission component 904 may transmit communications, such as reference signals, control information, and/or data communications, to the apparatus 906.
  • the communication manager 150 may generate communications and may transmit the generated communications to the transmission component 904 for transmission to the apparatus 906.
  • the transmission component 904 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) , and may transmit the processed signals to the apparatus 906.
  • the transmission component 904 may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, and/or a memory of the network node described above in connection with Figure 2. In some aspects, the transmission component 904 may be co-located with the reception component 902 in a transceiver.
  • the communication manager 150 may transmit or may cause the transmission component 904 to transmit, while a UE is in an RRC connected state, a grant for a transmission that is to occur at a grant time.
  • the communication manager 150 may transmit or may cause the transmission component 904 to transmit, while the UE is in the RRC connected state, a paging message.
  • the UE may delay, while an inactive interval associated with the UE does not satisfy a configurable inactive interval threshold, release of the RRC connected state.
  • the communication manager 150 may perform one or more operations described elsewhere herein as being performed by one or more components of the communication manager 150.
  • the communication manager 150 may include a controller/processor, a memory, a scheduler, and/or a communication unit of the network node described above in connection with Figure 2.
  • FIG. 9 The quantity and arrangement of components shown in Figure 9 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Figure 9. Furthermore, two or more components shown in Figure 9 may be implemented within a single component, or a single component shown in Figure 9 may be implemented as multiple, distributed components. Additionally or alternatively, a set of (one or more) components shown in Figure 9 may perform one or more functions described as being performed by another set of components shown in Figure 9.
  • a method of wireless communication by a UE comprising: receiving, while the UE is in an RRC connected state, a grant for a transmission that is to occur at a grant time; receiving, while the UE is in the RRC connected state, a paging message; and delaying, while an inactive interval associated with the UE does not satisfy a configurable inactive interval threshold, release of the RRC connected state.
  • Aspect 2 The method of Aspect 1, wherein delaying in the RRC connected state includes: refraining from performing a local RRC connection release procedure associated with the paging message.
  • Aspect 3 The method of any of Aspects 1-2, wherein the inactive interval is associated with a difference between a current time and the grant time.
  • Aspect 4 The method of Aspect 3, wherein the current time is a time at which the UE receives the paging message.
  • Aspect 5 The method of any of Aspects 1-4, wherein the grant is a first grant, wherein the transmission is a first transmission, and wherein the grant time is a first grant time, the method further comprising: receiving, while the inactive interval does not satisfy the configurable inactive interval threshold, a second grant for a second transmission that is to occur at a second grant time; and ignoring the paging message.
  • Aspect 6 The method of any of Aspects 1-5, further comprising: determining that the inactive interval satisfies the configurable inactive interval threshold; and performing a local RRC connection release procedure and a follow-up registration procedure.
  • Aspect 7 The method of any of Aspects 1-6, wherein the transmission is associated with voice traffic.
  • Aspect 8 The method of any of Aspects 1-7, wherein the transmission is associated with data traffic.
  • Aspect 9 An apparatus for wireless communication at a device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of Aspects 1-8.
  • Aspect 10 A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of Aspects 1-8.
  • Aspect 11 An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 1-8.
  • Aspect 12 A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of Aspects 1-8.
  • Aspect 13 A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 1-8.
  • the term “component” is intended to be broadly construed as hardware or a combination of hardware and software.
  • “Software” shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
  • a “processor” is implemented in hardware or a combination of hardware and software. It will be apparent that systems or methods described herein may be implemented in different forms of hardware or a combination of hardware and software.
  • satisfying a threshold may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, or not equal to the threshold, among other examples.
  • “at least one of: a, b, or c” is intended to cover a, b, c, a + b, a + c, b + c, and a + b + c, as well as any combination with multiples of the same element (for example, a + a, a + a + a, a + a + b, a + a + c, a +b + b, a + c + c, b + b, b + b + b, b + b + c, c + c, and c + c + c, or any other ordering of a, b, and c) .
  • the terms “has, ” “have, ” “having, ” and similar terms are intended to be open-ended terms that do not limit an element that they modify (for example, an element “having” A may also have B) .
  • the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise.
  • the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and/or, ” unless explicitly stated otherwise (for example, if used in combination with “either” or “only one of” ) .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Selon divers aspects, la présente divulgation porte de manière générale sur le domaine des communications sans fil. Certains aspects concernent plus spécifiquement le retardement de la libération d'une connexion de gestion des ressources radio (RRC) en réponse à un message de radiomessagerie reçu par un équipement utilisateur (UE) dans un état connecté de RRC. Selon certains aspects, l'UE surveille la durée pendant laquelle le réseau a été inactif et, après une durée configurable, libère la connexion RRC. Dans certains exemples, l'UE peut recevoir une autorisation provenant du réseau avant l'écoulement de la durée configurable, et l'UE peut ignorer le message de radiomessagerie. Dans certains exemples, l'UE peut ne pas recevoir une autorisation provenant du réseau avant l'écoulement de la durée configurable, et l'UE peut libérer la connexion RRC.
PCT/CN2023/108840 2023-07-24 2023-07-24 Intervalle inactif pour la gestion d'un message de radiomessagerie Pending WO2025020033A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/108840 WO2025020033A1 (fr) 2023-07-24 2023-07-24 Intervalle inactif pour la gestion d'un message de radiomessagerie

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/108840 WO2025020033A1 (fr) 2023-07-24 2023-07-24 Intervalle inactif pour la gestion d'un message de radiomessagerie

Publications (1)

Publication Number Publication Date
WO2025020033A1 true WO2025020033A1 (fr) 2025-01-30

Family

ID=94373800

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/108840 Pending WO2025020033A1 (fr) 2023-07-24 2023-07-24 Intervalle inactif pour la gestion d'un message de radiomessagerie

Country Status (1)

Country Link
WO (1) WO2025020033A1 (fr)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016191916A1 (fr) * 2015-05-29 2016-12-08 Qualcomm Incorporated Système et procédés de gestion d'un état de commande des ressources radio (rrc) dans un dispositif de communications sans fil prenant en charge simultanément des technologies d'accès radio
US20200100312A1 (en) * 2017-04-24 2020-03-26 Ntt Docomo, Inc. User device, radio base station, and radio communication method
CN111372310A (zh) * 2020-03-16 2020-07-03 展讯通信（上海）有限公司 一种寻呼管理方法及相关产品
CN114830807A (zh) * 2019-12-18 2022-07-29 高通股份有限公司 寻呼响应之后的快速连接释放
US20230018140A1 (en) * 2021-04-13 2023-01-19 Qualcomm Incorporated Service-based paging techniques
CN116170899A (zh) * 2023-03-01 2023-05-26 上海移芯通信科技有限公司 一种防止连接态寻呼响应丢失的方法和系统
CN116438882A (zh) * 2020-08-06 2023-07-14 欧芬诺有限责任公司 无线设备寻呼

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016191916A1 (fr) * 2015-05-29 2016-12-08 Qualcomm Incorporated Système et procédés de gestion d'un état de commande des ressources radio (rrc) dans un dispositif de communications sans fil prenant en charge simultanément des technologies d'accès radio
US20200100312A1 (en) * 2017-04-24 2020-03-26 Ntt Docomo, Inc. User device, radio base station, and radio communication method
CN114830807A (zh) * 2019-12-18 2022-07-29 高通股份有限公司 寻呼响应之后的快速连接释放
CN111372310A (zh) * 2020-03-16 2020-07-03 展讯通信（上海）有限公司 一种寻呼管理方法及相关产品
CN116438882A (zh) * 2020-08-06 2023-07-14 欧芬诺有限责任公司 无线设备寻呼
US20230018140A1 (en) * 2021-04-13 2023-01-19 Qualcomm Incorporated Service-based paging techniques
CN116170899A (zh) * 2023-03-01 2023-05-26 上海移芯通信科技有限公司 一种防止连接态寻呼响应丢失的方法和系统

Similar Documents

Publication Publication Date Title
US12284598B2 (en) Dedicated SIB1 during idle state reselection
US20230362625A1 (en) Updated artificial intelligence or machine learning capabilities reporting
US20250048334A1 (en) Performing a connection setup based at least in part on a paging message
US20240155498A1 (en) Cell wake-up signal for a user equipment operating in an idle or inactive mode
US20250063510A1 (en) Handling of user equipment resource-constrained state
US20240056862A1 (en) Conditional measurement gaps for delay critical traffic
US20230403620A1 (en) Network node migration and tracking area management
US20240121742A1 (en) Tracking area updates based on frequency band conditions
US12207198B2 (en) Wake up signal monitoring occasions
US12395878B2 (en) Access control for network energy savings
US20230284328A1 (en) Energy saving coordination in a network
US20250048156A1 (en) Source layer 2 identifier for path switching
WO2025020033A1 (fr) Intervalle inactif pour la gestion d'un message de radiomessagerie
US20230125531A1 (en) Capability compatibility for paging subgroup
WO2024065361A1 (fr) Améliorations de radiomessagerie pour des configurations de qualité d'expérience de diffusion
US20240089917A1 (en) Paging collision handling
US20240107499A1 (en) Paging messages for forwarding by a network node
US20240381258A1 (en) Power saving for connected devices
US12432753B2 (en) Configuration of multicast reception and mobility for user equipment in an inactive state
US12452862B2 (en) Physical downlink control channel skipping based on an anchor and an indication
US12328630B2 (en) Configuration management for multiple configuration communication scenarios
US20240008088A1 (en) Combined random access response and remaining minimum system information
US20240244549A1 (en) Uplink resource mapping for simplified synchronization signal block cells
US20250106874A1 (en) Suspension and resumption of a multicast/broadcast service
WO2024156071A1 (fr) Gestion de contexte de relais pendant un état inactif

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23946127

Country of ref document: EP

Kind code of ref document: A1