Monitoring system information change indication

Abstract

An apparatus, a method, and a computer program product for monitoring system information changes are provided. An example method may include receiving, from a network entity, a configuration for an initial downlink (DL) bandwidth portion (BWP) associated with a small data transmission (SDT) process, wherein a synchronization signal block (SSB) is configured to be transmitted in the initial DL BWP associated with the SDT process. The example method may also include receiving, from the network entity, a paging advance indication (PEI) indicating that a paging physical downlink control channel (PDCCH) is not scheduled for the first paging occasion (PO) or the first PO group. The example method may also include skipping monitoring of the system information change indication in the first PO or the first PO group in response to receiving the PEI.

Description

Cross-reference to related applications

[0001] This application claims the benefit and priority of U.S. Provisional Application Serial No. 63 / 503,878, filed May 23, 2023, entitled “MONITORING system informationchange indication,” and U.S. Non-Provisional Patent Application Serial No. 18 / 628,520, filed April 5, 2024, entitled “MONITORING SYSTEM INFORMATION CHANGE INDICATION,” which are expressly incorporated herein by reference in their entirety. Technical Field

[0002] This disclosure relates in general to communication systems, and more specifically to wireless communication systems having system information (SI) change indications. Background Technology

[0003] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such 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, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0004] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the city, national, regional, and even global levels. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the Continuous Evolution of Mobile Broadband (CEM) program issued by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT),) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR can be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. Furthermore, these improvements can also be applied to other multiple access technologies and telecommunications standards that adopt these technologies. Summary of the Invention

[0005] The following is a simplified summary of one or more aspects to provide a basic understanding of these aspects. This summary is not a comprehensive overview of all conceived aspects. It neither identifies key or essential elements of all aspects nor describes the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed descriptions that follow.

[0006] In one aspect of this disclosure, a method, computer-readable medium, and apparatus at a user equipment (UE) are provided. The apparatus may include at least one memory and at least one processor coupled to the at least one memory. Based at least in part on stored information stored in the at least one memory, the at least one processor is configured to cause the apparatus to receive from a network entity a configuration for an initial downlink (DL) bandwidth portion (BWP) associated with a small data transmission (SDT) procedure, wherein a synchronization signal block (SSB) is configured to be transmitted in the initial DL BWP associated with the SDT procedure. Based at least in part on stored information stored in the at least one memory, the at least one processor is configured to cause the apparatus to receive from a network entity a paging advance indication (PEI) indicating that there is no scheduled paging physical downlink control channel (PDCCH) for a first paging timing (PO) or a first PO group. Based at least in part on stored information stored in the at least one memory, the at least one processor is configured to cause the apparatus to skip monitoring of system information change indications in the first PO or the first PO group in response to receiving a PEI.

[0007] In another aspect of this disclosure, a method, computer-readable medium, and apparatus at a UE are provided. The apparatus may include at least one memory and at least one processor coupled to the at least one memory. Based at least in part on stored information stored in the at least one memory, the at least one processor is configured to cause the apparatus to receive from a network entity a configuration for an initial DL BWP associated with an SDT procedure, wherein an SSB is configured to be transmitted in the initial DL BWP associated with the SDT procedure. Based at least in part on the stored information stored in the at least one memory, the at least one processor is configured to cause the apparatus to: monitor for system information change indications in a PO or PO group based on a lack of support for receiving an associated PEI or the absence of PEI resources in the configuration for the initial DL BWP.

[0008] To achieve the foregoing and related objectives, one or more aspects include the features fully described below and specifically pointed out in the claims. The following description and drawings set forth some exemplary features of one or more aspects in detail. However, these features indicate only a few of the various ways in which the principles of the various aspects may be employed. Attached Figure Description

[0009] Figure 1 This is a diagram illustrating an example of a wireless communication system and an access network.

[0010] Figure 2A This is an illustration of an example of the first frame according to various aspects of this disclosure.

[0011] Figure 2B This is a diagram illustrating examples of downlink (DL) channels within a subframe according to various aspects of this disclosure.

[0012] Figure 2C This is an illustration of an example of a second frame according to various aspects of this disclosure.

[0013] Figure 2D This is a diagram illustrating examples of uplink (UL) channels within a subframe according to various aspects of this disclosure.

[0014] Figure 3 This is a diagram illustrating examples of base stations and user equipment (UEs) in an access network according to various aspects of this disclosure.

[0015] Figure 4A This is a diagram illustrating examples of power-saving gains and the number of UE subgroups for paging according to various aspects of this disclosure.

[0016] Figure 4B An example of communication based on bandwidth portion (BWP) is shown.

[0017] Figure 5 These are illustrations illustrating examples of SSB, PEI, and PO according to various aspects of this disclosure.

[0018] Figure 6A This is a diagram illustrating examples of SI modifications in the SDT process according to various aspects of this disclosure.

[0019] Figure 6B This is a diagram illustrating examples of BWPs for the SDT process according to various aspects of this disclosure.

[0020] Figure 7A This is a diagram illustrating examples of SI modifications in the SDT process according to various aspects of this disclosure.

[0021] Figure 7B This is a diagram illustrating examples of SI modifications in the SDT process according to various aspects of this disclosure.

[0022] Figure 8A This is a diagram illustrating example communication between a network entity and a UE according to various aspects of this disclosure.

[0023] Figure 8BThis is a diagram illustrating example communication between a network entity and a UE according to various aspects of this disclosure.

[0024] Figure 9 This is a flowchart of a wireless communication method according to various aspects of this disclosure.

[0025] Figure 10 This is a flowchart of a wireless communication method according to various aspects of this disclosure.

[0026] Figure 11 This is a flowchart of a wireless communication method according to various aspects of this disclosure.

[0027] Figure 12 These are illustrations illustrating examples of hardware implementations of example devices and / or network entities according to various aspects of this disclosure. Detailed Implementation

[0028] The UE monitors System Information (SI) updates from the network. The UE can monitor SI updates based on its RRC state. For example, a UE in an RRC idle or inactive state can monitor for SI change indications in the UE paging opportunity (PO) every DRX cycle. A UE in an RRC idle or inactive state during an SDT procedure can monitor for SI change indications in any PO at least once per modification cycle. The aspects presented herein enable the UE to achieve significant power savings by skipping monitoring for SI change indications in the PO in response to receiving an indication that no PEI is scheduled for paging PDCCH for the PO or the first PO group. The aspects presented herein provide monitoring of System Information Change Indicators in the PO or PO group for UEs that do not support receiving associated PEIs or when the UE does not have PEI resources configured in the initial DL BWP.

[0029] The detailed descriptions following, illustrated with reference to the accompanying drawings, describe various configurations and do not represent the only configurations in which the concepts described herein can be practiced. To provide a thorough understanding of the various concepts, the detailed descriptions include specific details. However, these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0030] Various apparatuses and methods are presented with reference to several aspects of a telecommunications system. These apparatuses and methods are described in detail below and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively, “elements”). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0031] As an example, an element, any part of an element, or any combination of elements may be implemented as a "processing system" including one or more processors. When multiple processors are implemented, the multiple processors may perform functions individually or in combination. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in a processing system may execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, or any combination thereof.

[0032] Therefore, in one or more example aspects, specific implementations, and / or use cases, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media. Storage media can be any available medium that can be accessed by a computer. By way of example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disc storage devices, magnetic disk storage devices, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures accessible by a computer.

[0033] While aspects, implementations, and / or use cases are described herein by way of example, additional or different aspects, implementations, and / or use cases may arise in many different arrangements and scenarios. The aspects, implementations, and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, aspects, implementations, and / or use cases may arise via integrated chip implementations and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specific to a use case or application, the described examples may exhibit broad applicability. Aspects, implementations, and / or use cases can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the technologies described herein. In some practical settings, devices incorporating the described aspects and features may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily involve multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or decomposed components, end-user equipment, etc., of various sizes, shapes, and configurations.

[0034] Communication systems, such as 5G NR systems, can be deployed in various ways with a variety of components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, radio access network (RAN) nodes, core network nodes, network elements or network equipment (such as base stations (BS)) or one or more units (or components) performing base station functions can be implemented in aggregated or decomposed architectures. For example, BSs (such as Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit / receive point (TRP), or cell, etc.) can be implemented as aggregated base stations (also known as standalone BS or monolithic BS) or decomposed base stations.

[0035] Aggregated base stations can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. Decentralized base stations can be configured to utilize a protocol stack that is physically or logically distributed across two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some respects, the CU may be implemented within a RAN node, and one or more DUs may co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. DUs may be implemented to communicate with one or more RUs. Each of the CUs, DUs, and RUs may be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0036] Base station operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be utilized in Integrated Access Backhaul (IAB) networks, Open Radio Access Networks (O-RAN (such as network configurations initiated by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)). Decomposition can include distributing functionality across two or more units in various physical locations, as well as virtually distributing the functionality of at least one unit, which enables flexibility in network design. The various units of a decomposed base station or decomposed RAN architecture can be configured to communicate wirelessly with at least one other unit.

[0037] Figure 1 Figure 100 illustrates an example of a wireless communication system and access network. The illustrated wireless communication system includes a decomposed base station architecture. The decomposed base station architecture may include one or more CUs 110, which may communicate directly with the core network 120 via a backhaul link, or indirectly with the core network 120 via one or more decomposed base station units, such as a near real-time (near-RT) RAN Intelligent Controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a Service Management and Orchestration (SMO) framework 105, or both. CUs 110 may communicate with one or more DUs 130 via a corresponding midhaul link (such as an F1 interface). DUs 130 may communicate with one or more RUs 140 via a corresponding fronthaul link. RUs 140 may communicate with a corresponding UE 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

[0038] Each unit in the cells (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO frame 105) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each unit in the cells, or an associated processor or controller providing instructions to the communication interfaces of these units, may be configured to communicate with one or more other units via transmission media. For example, these units may include wired interfaces configured to receive signals or transmit signals to one or more other units via wired transmission media. Additionally, these units may include wireless interfaces that may include receivers, transmitters, or transceivers (such as RF transceivers) configured to receive signals via wireless transmission media or transmit signals to one or more other units, or both.

[0039] In some aspects, the CU 110 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Serving Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by the CU 110. The CU 110 can be configured to handle user plane functionality (i.e., Central Unit-User Plane (CU-UP)), control plane functionality (i.e., Central Unit-Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 110 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 110 can be implemented to communicate with the DU 130 for network control and signaling, as needed.

[0040] DU 130 may correspond to a logic unit that includes one or more base station functions for controlling the operation of one or more RU 140s. In some aspects, DU 130 may at least partially host one or more of the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) according to functional splits (such as those defined by 3GPP). In some aspects, DU 130 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signaling with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

[0041] Lower-layer functionality can be implemented by one or more RU 140s. In some deployments, an RU140 controlled by a DU 130 can correspond to a logical node that hosts RF processing functions or low-PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, or both, based at least in part on functional decomposition (such as lower-layer functional decomposition). In this architecture, the RU 140 can be implemented to handle over-the-air (OTA) communications with one or more UE 104s. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 140 can be controlled by the corresponding DU 130. In some scenarios, this configuration enables the implementation of the DU 130 and CU 110 in cloud-based RAN architectures such as vRAN architectures.

[0042] SMO framework 105 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 105 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, SMO framework 105 can be configured to interact with a cloud computing platform such as Open Cloud (O-Cloud) 190 to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface such as the O2 interface. Such virtualized network elements may include, but are not limited to, CU 110, DU 130, RU 140, and near-RT RIC 125. In some implementations, SMO framework 105 can communicate with the hardware aspects of the 4G RAN (such as Open eNB (O-eNB) 111) via the O1 interface. Additionally, in some implementations, SMO framework 105 can communicate directly with one or more RU 140s via the O1 interface. SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of SMO framework 105.

[0043] The non-RT RIC 115 can be configured to include logical functions enabling non-real-time control and optimization of RAN elements and resources, including artificial intelligence (AI) / machine learning (ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 125. The non-RT RIC 115 can be coupled to or communicate with the near-RT RIC 125, such as via an A1 interface. The near-RT RIC 125 can be configured to include logical functions enabling near real-time control and optimization of RAN elements and resources via an interface, such as an E2 interface, that connects one or more CU 110s, one or more DU 130s, or both, and O-eNBs to the near-RT RIC 125.

[0044] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 125, the non-RT RIC 115 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 125 and can be received from non-network data sources or network functions at the SMO framework 105 or the non-RT RIC 115. In some examples, the non-RT RIC 115 or the near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 may monitor long-term trends and patterns in performance and employ AI / ML models to perform corrective actions via the SMO framework 105 (such as reconfiguration via O1) or by creating RAN management policies (such as A1 policies).

[0045] At least one of CU 110, DU 130, and RU 140 may be referred to as base station 102. Therefore, base station 102 may include one or more of CU 110, DU 130, and RU 140 (each component is indicated by a dashed line to indicate that each component may or may not be included in base station 102). Base station 102 provides UE 104 with an access point to core network 120. Base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Small cells include femtocells, picocells, and microcells. A network that includes both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include an evolved home node B (eNB) (HeNB), which can provide service to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) transmission (also known as reverse link) from UE 104 to RU 140 and / or downlink (DL) transmission (also known as forward link) transmission from RU 140 to UE 104. The communication link may utilize multiple-input multiple-output (MIMO) antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may use one or more carriers. For each direction, the total number of carriers used for transmission can be up to [number missing]. Yx MHz ( x For each carrier allocated in carrier aggregation (of component carriers), base station 102 / UE 104 can use up to [number] carriers. Y A spectrum with a bandwidth of MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.). Carriers may be adjacent to each other or may not be adjacent to each other. Carrier allocation may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier may be referred to as the primary cell (PCell) and the secondary component carrier may be referred to as the secondary cell (SCell).

[0046] Some UEs 104 can communicate with each other using device-to-device (D2D) communication link 158. D2D communication link 158 can use DL / UL wireless wide area network (WWAN) spectrum. D2D communication link 158 can use one or more sidelink channels, such as Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Shared Channel (PSSCH), and Physical Sidelink Control Channel (PSCCH). D2D communication can be performed through various wireless D2D communication systems, such as Bluetooth. ™ (Bluetooth is a trademark of the Bluetooth Special Interest Group (SIG), and is based on the IEEE 802.11 standard for Wi-Fi.)™ (Wi-Fi is a trademark of the Wi-Fi Alliance), LTE, or NR.

[0047] The wireless communication system may also include a Wi-Fi AP 150, which communicates with the UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, for example, in an unlicensed spectrum such as 5 GHz. When communicating in unlicensed spectrum, the UE 104 / AP 150 may perform a free channel assessment (CCA) to determine whether a channel is available before communication.

[0048] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz to 7.125GHz) and FR2 (24.25GHz to 52.6GHz). Although a portion of FR1 is greater than 6GHz, FR1 is generally (interchangeably) referred to as the "sub-6GHz" band in various documents and articles. Similar naming issues sometimes occur with FR2, which is generally (interchangeably) referred to as the "millimeter wave" band in documents and articles, although this is distinct from the Extremely High Frequency (EHF) band (30GHz to 300GHz) designated as "millimeter wave" by the International Telecommunication Union (ITU).

[0049] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR studies have identified the operating bands used for these mid-band frequencies as the frequency range designation FR3 (7.125 GHz to 24.25 GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 to mid-band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating frequency bands have been identified as the frequency range designations FR2-2 (52.6 GHz to 71 GHz), FR4 (71 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0050] In view of the above, unless otherwise specified, the term "below 6 GHz" as used herein can broadly refer to frequencies less than 6 GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise specified, the term "millimeter wave" as used herein can broadly refer to frequencies that can include intermediate frequency band frequencies, within FR2, FR4, FR2-2 and / or FR5, or within the EHF band.

[0051] Base station 102 and UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. Base station 102 may transmit beamformed signals 182 to UE 104 in one or more transmit directions. UE 104 may receive beamformed signals from base station 102 in one or more receive directions. UE 104 may also transmit beamformed signals 184 to base station 102 in one or more transmit directions. Base station 102 may receive beamformed signals from UE 104 in one or more receive directions. Base station 102 / UE 104 may perform beamforming training to determine the optimal receive and transmit directions for each of base station 102 / UE 104. The transmit and receive directions of base station 102 may be the same or different. The transmit and receive directions of UE 104 may be the same or different.

[0052] Base station 102 may include and / or be referred to as gNB, Node B, eNB, access point, transceiver base station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), TRP, network node, network entity, network equipment, or some other suitable terminology. Base station 102 may be implemented as an integrated access and backhaul (IAB) node, relay node, sidelink node, aggregated (monolithic) base station with baseband units (BBU) (including CU and DU) and RU, or may be implemented as a decomposed base station including one or more of CU, DU, and / or RU. A collection of base stations that may include decomposed base stations and / or aggregated base stations may be referred to as Next Generation (NG) RAN (NG-RAN).

[0053] The core network 120 may include Access and Mobility Management Function (AMF) 161, Session Management Function (SMF) 162, User Plane Function (UPF) 163, Unified Data Management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is the control node that handles signaling between UE 104 and the core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports authentication and key agreement (AKA) credential generation, user identity processing, access authorization, and subscription management. One or more location servers 168 are exemplified as including a Gateway Mobile Location Center (GMLC) 165 and a Location Management Function (LMF) 166. However, generally, one or more location servers 168 may include one or more location / positioning servers, which may include one or more of GMLC 165, LMF 166, Position Determination Entity (PDE), Serving Mobile Location Center (SMLC), Mobile Location Center (MPC), etc. GMLC 165 and LMF 166 support UE location services. GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE location information. LMF 166 receives measurement and auxiliary information from NG-RAN and UE 104 via AMF 161 to calculate the location of UE 104. NG-RAN may use one or more positioning methods to determine the location of UE 104. Positioning UE 104 may involve signal measurement, location estimation, and optional rate calculation based on these measurements. Signal measurement may be performed by UE 104 and / or base station 102 serving UE 104. The measured signals may be based on one or more of the following: Satellite Positioning System (SPS) 170 (e.g., one or more of Global Navigation Satellite System (GNSS), Global Positioning System (GPS), Non-Terrestrial Network (NTN) or other satellite positioning / location systems), LTE signals, Wireless Local Area Network (WLAN) signals, Bluetooth signals, Terrestrial Beacon System (TBS), sensor-based information (e.g., barometric pressure sensor, motion sensor), NR Enhanced Cell ID (NR E-CID) method, NR signals (e.g., multiple round-trip time (multiple RTT), DL departure angle (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning) and / or other systems / signals / sensors.

[0054] Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, GPS devices, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional device. Some UEs in UE 104 may be referred to as IoT devices (e.g., parking meters, air pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, mobile phone, user agent, mobile client, client, or some other suitable terminology. In some scenarios, the term UE may also be applied to one or more companion devices, such as in a device constellation arrangement. One or more of these devices may access the network together and / or individually.

[0055] Refer again Figure 1 In some aspects, UE 104 may include SI component 198. In some aspects, SI component 198 may be configured to receive from a network entity configuration for an initial DL BWP associated with an SDT procedure, wherein an SSB is configured to be sent in the initial DL BWP associated with the SDT procedure. In some aspects, SI component 198 may be further configured to receive from a network entity a PEI indicating that no PDCCH paging is scheduled for the first PO or the first PO group. In some aspects, SI component 198 may be further configured to skip monitoring of system information change indications in the first PO or the first PO group in response to receiving a PEI.

[0056] In some aspects, SI component 198 can be configured to receive configuration from a network entity for the initial DL BWP associated with the SDT procedure, wherein the SSB is configured to be transmitted in the initial DL BWP associated with the SDT procedure. In some aspects, SI component 198 can be further configured to monitor system information change indications in PO or PO group based on the lack of support for receiving associated PEI or the absence of PEI resources in the configuration for the initial DLBWP.

[0057] While the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0058] As described herein, a node (which may be referred to as a node, network node, network entity, or wireless node) may include, may be included in, or may be a component of: a base station (e.g., any base station described herein), a UE (e.g., any UE described herein), a network controller, apparatus, device, computing system, integrated access and backhaul (IAB) node, distributed unit (DU), central unit (CU), remote / radio unit (RU) (which may also be referred to as a remote radio unit (RRU)), and / or another processing entity configured to perform any of the techniques described herein. For example, a network node may be a UE. As another example, a network node may be a base station or a network entity. As yet another example, a first network node may be configured to communicate with a second or third network node. In one aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a UE. In another aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a base station. In still other aspects of this example, the first network node, the second network node, and the third network node may be different from these examples. Similarly, references to UE, base station, device, equipment, computing system, etc., may include disclosures of UE, base station, device, equipment, computing system, etc., as network nodes. For example, a disclosure of a UE being configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with this disclosure, once a particular example is extended according to this disclosure (e.g., a disclosure of a UE being configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node), a broader example of a narrower example may be interpreted in reverse, but in a broad, open-ended manner. In the above example where a UE is configured to receive information from a base station and a first network node is configured to receive information from a second network node, the first network node may refer to a first UE, a first base station, a first device, a first equipment, a first computing system, a first set of one or more components, or a first processing entity, etc., configured to receive information; and the second network node may refer to a second UE, a second base station, a second device, a second equipment, a second computing system, a second set of one or more components, or a second processing entity, etc.

[0059] As described herein, different terms may be used in various contexts to describe the transmission of information (e.g., any information, signal, etc.). Disclosure of one communication term includes disclosure of other communication terms. For example, a first network node may be described as being configured to send information to a second network node. In this example and consistent with this disclosure, disclosure regarding a first network node being configured to send information to a second network node includes disclosure regarding a first network node being configured to provide, transmit, output, communicate, or send information to a second network node. Similarly, in this example and consistent with this disclosure, disclosure regarding a first network node being configured to send information to a second network node includes disclosure regarding a second network node being configured to receive, obtain, or decode information provided, transmitted, output, communicate, or sent by the first network node.

[0060] Figure 2A Figure 200 illustrates an example of the first subframe within a 5G NR frame structure. Figure 2B Figure 230 illustrates an example of a DL channel within a 5G NR subframe. Figure 2C Figure 250 is an example of a second subframe within a 5G NR frame structure. Figure 2D Figure 280 illustrates an example of a UL channel within a 5G NR subframe. The 5G NR frame structure can be Frequency Division Duplex (FDD) (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to either DL or UL) or Time Division Duplex (TDD) (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to both DL and UL). Figure 2A , Figure 2C In the provided example, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible and can be used between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28 respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are both DL and UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The UE is configured using the slot format via the received Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-statically / statically configured via Radio Resource Control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0061] Figures 2A to 2DThe frame structure is illustrated, and aspects of this disclosure are applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10 ms) can be divided into 10 equal-sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include micro-time slots, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each time slot may include 14 symbols, and for extended CP, each time slot may include 12 symbols. Symbols on the DL may be CP Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. Symbols on the UL may be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Extended OFDM (DFT-s-OFDM) symbols (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and parameter set. The parameter set defines the subcarrier spacing (SCS) (see Table 1). The symbol length / duration can be scaled with 1 / SCS.

[0062] Table 1: Parameter Set, SCS, and CP For a normal CP (14 symbols / slot), different parameter sets µ 0 through 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For an extended CP, parameter set 2 allows 4 slots per subframe. Therefore, for a normal CP and parameter set µ, there are 14 symbols / slot and 2... µ One time slot / subframe. The subcarrier spacing can be equal to 2. µ * 15kHz, of which The parameter sets are 0 to 4. Therefore, the subcarrier spacing for parameter set µ=0 is 15kHz, and the subcarrier spacing for parameter set µ=4 is 240kHz. The symbol length / duration is negatively correlated with the subcarrier spacing. Figures 2A to 2D Examples of a normal frequency division multiplexing (CP) with 14 symbols per time slot and a parameter set of µ=2 with 4 time slots per subframe are provided. The time slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within the frame set, there may be one or more distinct bandwidth portions (BWPs) of frequency division multiplexing (see [link to relevant documentation]). Figure 2B Each BWP can have a specific set of parameters and CP (normal or extended).

[0063] A resource grid can be used to represent the frame structure. Each time slot consists of a resource block (RB) extending for 12 consecutive subcarriers (also known as a physical RB (PRB)). The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0064] like Figure 2A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. RS may include demodulation RS (DM-RS) (indicated as R for a particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE. RS may also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

[0065] Figure 2B Examples of various DL channels within a subframe of a frame are illustrated. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE comprising six RE Groups (REGs), each REG comprising 12 consecutive REs in the OFDM symbol of the RB. A PDCCH within a BWP can be referred to as a Control Resource Set (CORESET). The UE is configured to monitor PDCCH candidates in the PDCCH search space (e.g., the common search space, the UE-specific search space) during PDCCH monitoring timing on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. The Primary Synchronization Signal (PSS) may be located within symbol 2 of a specific subframe of the frame. The PSS is used by the UE 104 to determine subframe / symbol timing and physical layer identification. The Secondary Synchronization Signal (SSS) may be located within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the Physical Layer Cell Identifier Group Number and radio frame timing. Based on the Physical Layer Identifier and the Physical Layer Cell Identifier Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The Physical Broadcast Channel (PBCH), carrying the Master Information Block (MIB), can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block (also known as an SS block (SSB)). The MIB provides the System Frame Number (SFN) and the number of Restricted Frames (RBs) in the system bandwidth. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (such as System Information Blocks (SIBs)), and paging messages.

[0066] like Figure 2CAs illustrated, some REs in the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS can be transmitted in the first or first two symbols of the PUSCH. Depending on whether a short or long PUCCH is transmitted and depending on the specific PUCCH format used, the PUCCH DM-RS can be transmitted in different configurations. The UE can transmit a Sounding Reference Signal (SRS). The SRS can be transmitted in the last symbol of a subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of the comb teeth. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

[0067] Figure 2D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at the position indicated in some aspects. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), pre-decoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUCCH carries data and may additionally be used to carry buffer status reports (BSR), power clearance reports (PHR), and / or UCIs.

[0068] Figure 3This is a block diagram illustrating communication between base station 310 and UE 350 in the access network. In the DL, Internet Protocol (IP) packets can be provided to controller / processor 375. Controller / processor 375 implements Layer 3 and Layer 2 functionality. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the delivery of upper-layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority ordering.

[0069] Transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) decoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. TX processor 316 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to OFDM subcarriers, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and then combined using inverse fast Fourier transform (IFFT) to produce a physical channel carrying a stream of time-domain OFDM symbols. The OFDM stream undergoes spatial pre-decoding to generate multiple spatial streams. A channel estimate from channel estimator 374 can be used to determine the decoding and modulation scheme, as well as for spatial processing. This channel estimate can be derived from a reference signal transmitted by UE 350 and / or channel condition feedback. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx can utilize the corresponding spatial stream to modulate a radio frequency (RF) carrier for transmission.

[0070] At UE 350, each receiver 354Rx receives signals via its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides that information to the receive (RX) processor 356. The TX processor 368 and RX processor 356 implement Layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for UE 350. If multiple spatial streams are destined for UE 350, the RX processor 356 can combine them into a single OFDM symbol stream. The RX processor 356 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal consists of a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, along with a reference signal, are recovered and demodulated by determining the most probable signal constellation point transmitted by base station 310. These soft decisions can be based on a channel estimate calculated by channel estimator 358. The soft decision is then decoded and deinterleaved to recover the data and control signals originally transmitted by base station 310 on the physical channel. The data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functionality.

[0071] The controller / processor 359 may be associated with at least one memory 360 storing program code and data. The at least one memory 360 may be referred to as a computer-readable medium. In the UL, the controller / processor 359 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels to recover IP packets. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0072] Similar to the functionality described in conjunction with DL transmission performed by base station 310, controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connectivity, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with upper-layer PDU delivery, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority ordering.

[0073] The TX processor 368 can use the reference signal transmitted from the base station 310 or the channel estimate derived from feedback by the channel estimator 358 to select an appropriate decoding and modulation scheme and facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via individual transmitters 354Tx. Each transmitter 354Tx can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0074] UL transmission is processed at base station 310 in a manner similar to that described in conjunction with the receiver function at UE 350. Each receiver 318Rx receives signals via its corresponding antenna 320. Each receiver 318Rx recovers the information modulated onto the RF carrier and provides that information to RX processor 370.

[0075] The controller / processor 375 may be associated with at least one memory 376 storing program code and data. The at least one memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels to recover IP packets. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0076] At least one of the TX processor 368, RX processor 356, and controller / processor 359 can be configured to combine Figure 1 SI component 198 is used to perform various aspects.

[0077] In some wireless communication systems, the RRC protocol can be used on the air interface. The functions of the RRC protocol can include connection establishment and release, broadcasting system information, radio bearer establishment, reconfiguration and release, RRC connection mobility procedures, paging notification and release, and outer loop power control, etc. The RRC protocol can configure the user plane and control plane according to network conditions and can allow the implementation of radio resource management policies. Some example services and functions of the RRC layer / sublayer can include broadcasting system information related to the access stratum (AS) or non-access stratum (NAS), paging, establishment and release of RRC connections between the UE and the radio access network (RAN), establishment and release of signaling radio bearers (SRB) or data radio bearers (DRB), mobility functions, etc. RRC operation can be based on the specific state that the UE may be in. In some wireless communication systems, the UE may be in an RRC idle state, an RRC inactive state, or an RRC active state.

[0078] The UE can enter the RRC idle state after power-on and before establishing an RRC connection. The UE can also enter the RRC idle state in either the RRC connected state or the RRC inactive state after a connection failure or RRC release. In the RRC idle state, the UE can perform or process Public Land Mobile Network (PLMN) selection, System Information (SI) broadcasting, cell reselection mobility, paging for Mobile Station Called (MT) data, or Discontinuous Reception (DRX) for Core Network Paging (CN) configured by NAS. In the RRC inactive state, the UE can perform or process SI broadcasting, cell reselection mobility, RAN paging, RAN-based Notification Area (RNA), DRX for RAN paging, RAN connections in the control plane or user plane, etc. In the RRC inactive state, the UE's AS context can be stored in the RAN, and the UE and RAN can know the RNA to which the UE belongs. In RRC connected mode, in addition to performing or processing RAN connections, the UE can also send or receive unicast data from the RAN and can also process or perform network control-related mobility, including measurements.

[0079] In the RRC inactive state, a UE can identify a small amount of UL data to be transmitted (e.g., data related to instant messaging services, push notifications, or wearable devices), which may be infrequent or undesirable. To transmit UL data, the UE can perform a Random Access Channel (RACH) procedure and establish an RRC connection with the network, entering the RRC connected state. However, considering the significant signaling overhead compared to the small amount of data to be transmitted, performing the RACH procedure and establishing an RRC connection for a small amount of data can be inefficient. Therefore, in some wireless communication systems, a UE in the RRC inactive state can use the SDT procedure to transmit less than a threshold amount of data without transitioning to or entering the RRC connected state, for example, while remaining in the RRC inactive state.

[0080] Based on the SDT procedure, the network can allow the UE to transmit (MO) uplink small data in an RRC inactive state without switching from the RRC inactive state to the RRC connected state. The SDT procedure can be RACH-based or configuration-granted (CG). A RACH-based SDT procedure (also known as RA-SDT) enables UL small data transmission for RACH-based schemes such as 2-step and 4-step RACH. A CG-based SDT procedure (also known as CG-SDT) enables UL data transmission on configured PUSCH resources (e.g., by reusing configuration-granted type 1). A network node can schedule a type 1 CG by sending an RRC to the UE, which schedules the UE to transmit PUSCH without first receiving a lower-layer trigger (e.g., DCI trigger) from the network node. This PUSCH can also be referred to as a type 1 CG. A network node can schedule a Type 2 CG by sending an RRC to the UE, which in turn schedules the UE to send a PUSCH in response to receiving a simple DCI without PUSCH scheduling (e.g., a Configuration Scheduling (CS) Radio Network Temporary Identifier (CS-RNTI)). In response to receiving a DCI, for example, with a CS-RNTI, the UE can send a PUSCH as scheduled by the RRC. Such a PUSCH can also be referred to as a Type 2 CG.

[0081] For the SDT procedure, subsequent transmission and state transition decisions for small data in the UL and DL can be under network control. In some respects, Non-Access Stratum (NAS) message delivery can be implemented within the SDT procedure. For example, SRB1 and SRB2 can be configured for small data transmission in the RRC inactive state, and NAS message transmission via SRB2 can be implemented.

[0082] Improving the paging process to reduce unnecessary UE paging reception can be advantageous. One technique for reducing erroneous (e.g., unnecessary) paging reception could be to group UEs within a paging opportunity (PO). A PO could be a paging PDCCH monitoring opportunity, where the paging PDCCH is sent in a Type 2 PDCCH CSS set, and the cyclic redundancy check (CRC) of the paging PDCCH is scrambled by a paging random network temporary identifier (P-RNTI). Without grouping, even if paging is directed to a single UE, all UEs within the PO can wake up during the PO to receive and decode the paging message. These groups (which may also be referred to as subgroups) can be referred to herein as UE groups (or UE subgroups). Therefore, by utilizing UE grouping, when the network sends a paging indication to UEs in the PO, it can indicate the UE group to which paging is intended, so that UEs in the PO but not being paged do not waste power while receiving and decoding paging messages.

[0083] UEs in a PO can be grouped in various ways. To reduce power consumption associated with paging reception, UE attributes that may affect power can be considered in UE grouping. Examples of UE attributes that may affect power include UE paging probability (i.e., how likely is it that a UE will be paging), UE power state (e.g., external power supply vs. battery power supply), etc. Because different types of UEs may exist in a cell, finding a single UE attribute for grouping UEs that works well for all possible scenarios can be challenging. The UE attribute used for UE grouping can be called a UE paging attribute or simply a paging attribute. Depending on various aspects, a UE can provide its UE paging attributes to the network, and the network can determine how to group UEs based on the UE paging attributes provided by the UE.

[0084] In some aspects, the network may announce a set of attributes that it can use to group UEs in a PO. This set of attributes may include one or more of the following: UE paging probability (e.g., the probability or likelihood that a UE can be paging), UE power profile (e.g., a battery-powered UE may be power-sensitive compared to an externally powered UE which may be less or insensitive to power consumption), UE RRC state (e.g., RRC inactive or RRC idle), or UE mobility (e.g., fixed or mobile). The network may use additional information about the UE that it may have (e.g., UE capabilities, such as the number of antennas, since a UE with fewer antennas may be associated with more duplication) or information received from other network entities (e.g., expected UE behavior information from application function "AF") in UE grouping decisions.

[0085] In some respects, the UE can provide the network with information (e.g., indications) about a selected set of advertised UE paging attributes. In some respects, the UE can provide indications of UE paging attributes to the core network (in a specific example, to the AMF) via NAS signaling. In some respects, the UE can provide indications of UE paging attributes to the RAN (in a specific example, to the base station) in a UE Auxiliary Information (UAI) message.

[0086] In some respects, when or whether (if needed) paging attributes are provided to the UE, or which attributes are provided, can be determined on a UE-specific basis. In some respects, the UE can provide its paging attributes to the network when it is in an RRC connected state. For example, when the UE enters an RRC connected state due to data transfer, registration, or tracking area updates, it can provide its paging attributes to the network. In some respects, the UE can initiate an RRC connection to update its paging attributes. This can be useful when the UE paging attributes have changed significantly (e.g., when the UE's power supply has changed from external power to battery power or the expected paging rate has increased). This can also be useful when the set of UE paging attributes announced by the network has changed. In some respects, the network can configure a timer to control the frequency at which the UE can report or update its paging attributes. The timer can be started or reset when the UE submits a UE paging attribute report to the network. As long as the timer is still running (i.e., before the timer expires), it is possible to prevent or disable the UE from submitting another UE paging attribute report, thus avoiding excessive UE paging attribute reports.

[0087] A PEI can be sent to the UE before an upcoming PO to indicate whether the UE can handle (e.g., monitor) the upcoming PO. The PEI can indicate the UE subgroup being paged in the upcoming PO. If the PEI and SSB are aligned in time, UE power savings can be achieved. One or more SSBs associated with the PO can exist between the PEI and the PO for the UE to further update the tracking loop used for paging PDCCH decoding.

[0088] Figure 4A Figure 400 illustrates examples of power-saving gains for paging and increases in the number of UE subgroups according to various aspects of this disclosure. Figure 4A As illustrated, the power saving gain increases with the number of UE subgroups (so that each subgroup can include fewer UEs). Figure 4A The example in the example can be based on a 10% paging rate and a 20ms SSB periodicity.

[0089] The UE can be configured with multiple BWPs. Figure 4BExample 450 illustrates three BWPs (e.g., BWP1, BWP2, and BWP3), each spanning a set of frequency resources (e.g., a set of PRBs). A BWP can be activated for the UE from a configured set of BWPs. It may not be expected that the UE will receive PDSCH, PDCCH, CSI-RS, TRS, etc., outside of an active downlink BWP. The UE may not send PUSCH or PUCCH outside of an active uplink BWP. The UE can receive from the network an indication to switch from a first active BWP to a second active BWP, both from a configured set of BWPs. Figure 4B As illustrated, each downlink BWP may include a control resource set (CORESET) corresponding to a configurable set of physical resources in time and frequency, which the UE uses to monitor the PDCCH / DCI when the corresponding BWP is activated. For example, if the UE receives an indication to switch to BWP 1, the UE may monitor control signaling in the corresponding CORESET in BWP 1. If the UE receives an indication to switch to BWP 2, the UE may monitor control signaling in the CORESET in BWP 2. The UE may receive configuration for an initial BWP (e.g., an initial DL BWP and / or an initial UL BWP). The UE may, for example, receive indications for an active DL BWP and / or an active UL BWP to be used for communication with the network in the initial DL BWP.

[0090] Figure 5 Figure 500 is an illustration of examples of SSB 502, PEI 504, and PO 506 according to various aspects of this disclosure. As... Figure 5 As illustrated, PEI 504 may include a UE subgroup indication (e.g., for indicating which UE subgroup can be monitored) associated with PO 506. SSB 502 may be associated with PO 506.

[0091] UEs can use different SI acquisition procedures in different RRC states to acquire or reacquire Access Stratum (AS), NAS, and location data. UEs in inactive / idle states can have valid versions of MIB, SIB1, SIB2, SIB3, SIB4, and SIB5. SIB1 can be carried by the PDSCH and can carry all information used by the UE to perform the initial attach procedure at least until resource establishment, and can also carry scheduling information for other SIBs. SIBs other than SIB1 can be sent via the PDSCH and through periodic broadcasts. SIB2 can carry cell reselection information common to intra-frequency, inter-frequency, or other types of cell reselection. SIB3 can carry an intra-frequency neighboring cell list and reselection criteria. SIB4 can carry an inter-frequency neighboring cell list and reselection criteria. SIB5 can carry other types of neighboring cell lists and reselection criteria. Based on UE capabilities and network configuration, UEs in inactive / idle states can have valid versions of other SIBs (including the location SIB). As an example, the UE can delete the stored version of the SIB after a certain period of time (such as 3 hours) from the moment the SIB is successfully confirmed as valid. The network can update the SI message by broadcasting it during the SI modification period following the SI change indication. The boundaries of the SI modification period are determined by... SFN mod m =0 or ( H-SFN*1024+SFN ) mod m =0 specifies that m represents the periodicity of SI modification. The UE uses a short message sent via DCI along with P-RNTI to receive indications of SI modification and / or PWS notifications. The short message may be a paging PDCCH indicating that the SI will be changed by NW in the next SI modification period (in time). The short message may be based on DCI format 1_0. The repetition of the SI change indication may occur within the previous SI modification period or within the previous discontinuous reception (DRX) acquisition period.

[0092] DCI format 0_0 can be a fallback format that can provide scheduling for PUSCH in a cell. DCI format 0_1 ​​can be a non-fallback format that can provide scheduling for PUSCH in a cell. DCI format 1_0 can be a fallback DCI format for allocating downlink resources for PDSCH. DCI format 1_1 can be a non-fallback DCI format for allocating downlink resources for PDSCH. DCI format 2_0 can be used to notify slot format information (to dynamically change slot formats). DCI format 2_1 can be used to notify where the UE can assume there are no PRB and OFDM symbols intended for transmission to the UE. DCI format 2_2 can be used to send transmit power control (TPC) commands for PUCCH and PUSCH. DCI format 2_3 can be used to send a set of TPC commands for SRS transmission for one or more UEs. DCI format 2_4 can be used (e.g., dedicated to) to provide cancellation of UL transmission.

[0093] In some wireless communication systems, if the initial downlink BWP on which an SDT procedure is being performed is associated with a CD-SSB, a UE that is in an RRC idle or RRC inactive state when the SDT procedure is not in progress can monitor for SI change indications during its own paging opportunity in each DRX cycle, and a UE that is in an RRC inactive state when the SDT procedure is in progress can monitor for SI change indications at least once in any paging opportunity in each modification cycle. However, this monitoring may be inconsistent with PEI. For example, a UE (such as a RedCap UE that supports PEI based on PDCCH (or low-power wake-up signal)) may not process (e.g., not monitor) an upcoming PO based on PEI. Based on PEI, it is permissible for a UE to skip monitoring one or more POs (including short messages indicating SI changes) on all DRX cycles when the SDT procedure is not in progress, or to skip monitoring one or more POs in all SI modification cycles when the SDT procedure is in progress. However, if the initial downlink BWP on which the SDT procedure is being performed is associated with a CD-SSB, this procedure may conflict with a configuration where the UE can monitor the SI change indication at its own paging time in each DRX cycle and at least once in any paging time in each modification cycle. Additionally, in some respects, the RedCap-specific initial DL BWP on which the SDT procedure is being performed may include a CD-SSB, but not the entire CORESET#0 associated with the PO (e.g., a type 2-PDCCH CSS set, where the PDCCH common search space set is configured by the pagingSearchSpace in PDCCH-ConfigCommon for a DCI format with CRC scrambled by P-RNTI on the primary cell).

[0094] In some respects, one or more PEI monitoring events (PEI-O) or POs associated with a short message can overlap with the CG-PUSCH event of the SDT. Resources for PEI-O (based on PDCCH or similar LP-WUS sequences) can be configured in the initial DL BWP for the SDT. In some respects, the start time and maximum duration of the SDT are configured separately from the time offset and periodicity of the PO. For example, if the SDT is in PO... n Then begin and in PO n+1 If the process ends earlier, the UE may not need to monitor the PO used for SI change indication while the SDT process is in progress. This document addresses the following aspects: enabling a more efficient SDT process by providing a mechanism to resolve inconsistencies between the PEI and SDT processes; providing conflict resolution rules for the SDT process where one or more PEI monitoring events (PEI-O) or POs associated with a short message can overlap with the CG-PUSCH event of the SDT; allowing the UE to skip monitoring of the PO while the SDT is in progress; and providing a solution for RedCap-specific initial DL BWPs on which the SDT process is being performed, which may include CD-SSBs but not the entire CORESET#0 associated with the PO.

[0095] As used herein, the term "SDT procedure" may refer to the SDT procedure configured with the initial DL BWP, and may be MO-SDT (e.g., RA-SDT or CG-SDT), MT-SDT, or a combination of MO-SDT or MT-SDT. The SSB in the initial DL BWP may be a cell-defined SSB (CD-SSB) or a non-cell-defined SSB (NCD-SSB).

[0096] Figure 6A Figure 600 illustrates examples of SI modifications in the SDT process according to various aspects of this disclosure. For example... Figure 6AAs illustrated, within the time interval 602 used for the SDT process, there may be a first SI modification period 604A, a second SI modification period 604B, a third SI modification period 604C, and a fourth SI modification period 604D that overlap with the time interval 602. The first SI modification period 604A may overlap with PEI-O 606A and the associated PO or PO group 608A; the second SI modification period 604B may overlap with PEI-O 606B and the associated PO or PO group 608B; the third SI modification period 604C may overlap with PEI-O 606C and the associated PO or PO group 608C; and the fourth SI modification period 604D may overlap with PEI-O 606D and the associated PO or PO group 608D. During each of the first SI modification period 604A, the second SI modification period 604B, the third SI modification period 604C, and the fourth SI modification period 604D, an SI change may or may not occur. In some wireless communication systems, the UE can monitor (e.g., in a short message) the SI change indication during each of the first SI modification period 604A, the second SI modification period 604B, the third SI modification period 604C, and the fourth SI modification period 604D, which may conflict with PEI monitoring.

[0097] Figure 6B Figure 650 illustrates examples of SI modifications in the SDT process according to various aspects of this disclosure. For example... Figure 6B As illustrated, for a given UE, there may be a RedCap-specific initial DL BWP 652 configured for SDT but not for PO, and there may be a separate initial DL BWP 654 configured by the CD-SSB's MIB that includes CORESET #0 656 for paging and SI. When the SI change does not occur and the initial DL BWP configured for SDT does not include the entire CORESET (e.g., CORESET #0) associated with the PO (e.g., a Type 2 PDCCH CSS set), BWP handover / RF retuning can be performed for such redundant PO monitoring, which further increases UE complexity, latency, and downtime.

[0098] Figure 7A Figure 700 illustrates examples of SI modifications in the SDT process according to various aspects of this disclosure. For example... Figure 7AAs illustrated, within the time interval 702 used for the SDT process, there may be a first SI modification period 704A, a second SI modification period 704B, and a third SI modification period 704C that overlap with the time interval 702. The first SI modification period 704A may overlap with PEI-O 706A and the associated PO or PO group 708A, the second SI modification period 704B may overlap with PEI-O 706B and the associated PO or PO group 708B, and the third SI modification period 704C may overlap with PEI-O 706C and the associated PO or PO group 708C. The CG-PUSCH timing 710A (e.g., the PUSCH transmission timing associated with configuration grant) may overlap with PEI-O 706A. Therefore, monitoring PEI-O 706A may conflict with the CG-PUSCH timing 710A. CG-PUSCH timing 710B (e.g., a PUSCH transmission timing associated with configuration permission) may not overlap with PEI-O 706A or the associated PO or PO group 708A. Therefore, monitoring PEI-O 706B may not cause a conflict. CG-PUSCH timing 710C (e.g., a PUSCH transmission timing associated with configuration permission) may overlap with PO or PO group 708C. Therefore, monitoring PO or PO group 708C may conflict with CG-PUSCH timing 710C. Each of CG-PUSCH timing 710A, CG-PUSCH timing 710B, and CG-PUSCH timing 710C may span one or more time slots.

[0099] Figure 7B Figure 750 illustrates examples of SI modifications in the SDT process according to various aspects of this disclosure. For example... Figure 7B As illustrated, the time interval 752 of the UE's SDT procedure may overlap with PEI-O 756, but not with the associated PO or PO group 758. PEI-O 756 and PO or PO group 758 may overlap with the SI modification period 754. When the SDT procedure is in progress, monitoring the PO for SI change indication based on the received PEI-O 756 may be inefficient because the PO or PO group 758 does not overlap with the time interval 752 of the SDT procedure.

[0100] Based on the examples provided herein, if the UE's initial DL BWP includes an SSB and is configured for the SDT procedure, and the UE receives a PEI indicating that paging PDCCH is not scheduled on the next PO / PO group, the UE may not monitor (e.g., in short messages) SI change indications during one or more SI modification periods associated with the skipped PO / PO group. For example, refer to [reference]. Figure 6AIf a received PEI associated with PEI-O 606A indicates that the paging PDCCH is not scheduled on the next PO / PO group, the UE can skip monitoring of the SI change indication (e.g., in a short message) during the SI modification period 604A. A PEI indicating that the paging PDCCH is not scheduled on the next PO / PO group can be referred to as indicating "monitoring skip". As another example, refer to the reference. Figure 6A If the received PEI indicating paging PDCCH associated with PEI-O 606A is not scheduled on the next two PO / PO groups, the UE can skip monitoring of the SI change indication (e.g., in a short message) in SI modification period 604A and SI modification period 604B. Based on the example aspects provided herein, if the UE's initial DL BWP includes an SSB and is configured for the SDT procedure, and the UE does not receive a PEI indicating PO monitoring to be skipped, the UE can monitor the SI change indication at least once in any valid PO during each SI modification period while the SDT procedure is in progress. As an example, refer back to the reference. Figure 6A If no PEI is received within PEI-O 606C, the UE can monitor for an SI change indication (e.g., in a short message) during the SI modification period 604C. As another example, refer back to the reference. Figure 6A If a PEI is received within PEI-O 606C, but the PEI does not indicate that the paging PDCCH was not scheduled on the next PO / PO group, the UE can monitor (e.g., in a short message) the SI change indication during the SI modification period 604D.

[0101] In some respects, a valid PO for a SI change indication used for UE monitoring (e.g., in a short message) can satisfy all of the following four conditions (or, in some alternative respects, a subset of the four conditions): (1) it is included in the time interval during which the SDT procedure is in progress; (2) it does not overlap with a DL / UL transmission with higher priority during the SDT (priority handling may be based on a set of rules configured at the UE without network signaling, configured by the NW in the SI or Radio Resource Control (RRC), or dynamically indicated by the Downlink Control Information (DCI), RRC signaling, or MAC Control Element (MAC CE)); (3) if the UE receives a PEI, it is not indicated by the PEI as a monitoring skip; or (4) the UE does not receive a PEI. A UE may not receive a PEI for a variety of reasons. For example, in some respects, the UE may not support PEI. In some respects, the UE may not receive a PEI because the PEI resource was not configured in the initial DL BWP for the SDT procedure for the UE. In some respects, a UE may not receive a PEI because it has not detected a PEI-O associated with a valid PO, due to NW scheduling (between UEs), conflict / priority handling (within UEs), or UE capabilities (e.g., half-duplex HD-FDD for RedCap UEs, simultaneous monitoring of a specific number of RNTIs). In other respects, a UE may not receive a PEI because the presence of a PEI is detected, but the CRC check associated with the PEI fails.

[0102] Return to reference Figure 7A As an example, each of CG-PUSCH timing 710A, CG-PUSCH timing 710B, and CG-PUSCH timing 710C can have a higher priority than PEI-O or the associated PO or PO group. Therefore, in some respects, because the PO or PO group or the associated PEI-O overlaps with the CG-PUSCH timing, the UE may not detect the PO or PO group 708B within SI modification period 704B and may not detect the PO or PO group 708C within SI modification period 704C, thus rendering these POs or PO groups invalid.

[0103] Return to reference Figure 7B As an example, in some respects, since PO or PO group 758 is outside the time interval 752 used for SDT procedures, the UE may not monitor PO or PO group 758.

[0104] Figure 8AFigure 800 illustrates example communication between network entity 804 and UE 802 according to various aspects of this disclosure. Network entity 804 may send configuration 806 of the initial BWP for the SDT procedure to UE 802. During a subsequent SDT procedure and within the first SI modification cycle, PEI 808 may be sent from network entity 804 to UE 802. At 810, if the PO is not a valid PO for the UE to monitor short messages during the SDT, such as if all (or in some alternatives, a subset of) of the following four conditions are not met, the UE 802 may (e.g., may determine) skip monitoring of the PO (associated with PEI 808) for SI change indication (e.g., in short messages): (1) is included in the time interval during which the SDT process is in progress, (2) does not overlap with DL / UL transmissions with higher priority during the SDT (priority handling may be based on a set of rules configured at the UE without network signaling, configured by the NW in the SI or Radio Resource Control (RRC), or dynamically indicated by Downlink Control Information (DCI), RRC signaling, or MAC Control Element (MAC CE)) (as an example, priority may be provided to the UE 802 at 807 via DCI, RRC, or MAC CE), (3) is not indicated by the PEI for monitoring skip if the UE receives the PEI, or (4) the UE does not receive the PEI. For example, if PEI 808 indicates that the paging PDCCH is not scheduled on the next PO / PO group, UE 802 can skip monitoring of the PO (associated with PEI 808) used for SI change indication at 810 (e.g., it can be determined). Therefore, based on the absence of SI change, UE 802 can communicate with network entity 804 at 812 based on the previous SI.

[0105] In some respects, PEI 814 can be sent from network entity 804 to UE 802. At 816, based on the PO being a valid PO for the UE to monitor short messages during SDT, such as based on all (or in some alternative respects, a subset of the four conditions) of the following conditions, UE 802 can (e.g., can determine) monitor the PO (associated with PEI 814) for SI change indication (e.g., in short messages): (1) is included in the time interval during which the SDT process is in progress, (2) does not overlap with DL / UL transmissions with higher priority during SDT (priority handling may be based on a set of rules configured at the UE without network signaling, configured by NW in SI or Radio Resource Control (RRC), or dynamically indicated by Downlink Control Information (DCI), RRC signaling, or MAC Control Element (MAC CE), (3) is not indicated by PEI for monitoring skip if the UE receives PEI, or (4) the UE does not receive PEI. In some respects, UE 802 may receive the associated SI change indication 818 based on monitoring. In other respects, even if UE 802 monitors a PO or PO group, it may not receive the SI change indication 818. During another SI modification cycle, PEI 820 may be sent to UE 802 from network entity 804. At 822, if the PO is not a valid PO for the UE to monitor short messages during the SDT, such as if all (or in some alternatives, a subset of the four conditions) of the following conditions are not met, the UE 802 may (e.g., may determine) skip monitoring of the PO (associated with PEI 820) for SI change indication (e.g., in short messages): (1) is included in the time interval during which the SDT process is in progress, (2) does not overlap with DL / UL transmissions with higher priority during the SDT (priority handling may be based on a set of rules configured at the UE without network signaling, configured by the NW in the SI or Radio Resource Control (RRC), or dynamically indicated by the Downlink Control Information (DCI), RRC signaling, or MAC Control Element (MAC CE), (3) is not indicated by the PEI for monitoring skip if the UE receives the PEI, or (4) the UE does not receive the PEI.

[0106] Figure 8BFigure 850 illustrates example communication between network entity 854 and UE 852 according to various aspects of this disclosure. Network entity 854 may send configuration 856 of the initial BWP for the SDT procedure to UE 852. At 858, based on the fact that the PO is not a valid PO for the UE to monitor short messages during the SDT, such as based on all (or in some alternative aspects, a subset of the four conditions) of the following conditions, the UE 802 may (e.g., may determine) monitor the PO (associated with PEI 814) for SI change indication (e.g., in short messages): (1) is included in the time interval during which the SDT process is in progress, (2) does not overlap with DL / UL transmissions with higher priority during the SDT (priority handling may be based on a set of rules configured at the UE without network signaling, configured by the NW in the SI or Radio Resource Control (RRC), or dynamically indicated by the Downlink Control Information (DCI), RRC signaling, or MAC Control Element (MAC CE), (3) is not indicated by the PEI for monitoring skip if the UE receives the PEI, or (4) the UE does not receive the PEI. Figure 9 This is a flowchart 900 of a wireless communication method. This method can be performed by a UE (e.g., UE 104, UE 802; device 1104). This method can facilitate a more efficient SDT process.

[0107] At 902, the UE can receive configuration from a network entity for the initial DL BWP associated with the SDT procedure, wherein the SSB is configured to be transmitted in the initial DL BWP associated with the SDT procedure. For example, UE 802 can receive configuration for the initial DL BWP associated with the SDT procedure from network entity 804 (e.g., 806), wherein the SSB is configured to be transmitted in the initial DL BWP associated with the SDT procedure. In some aspects, 902 can be performed by SI component 198.

[0108] At 904, the UE can receive a PEI from the network entity indicating that no paging PDCCH is scheduled for the first PO or the first PO group. For example, UE 802 can receive a PEI from network entity 804 indicating that no paging PDCCH is scheduled for the first PO or the first PO group (e.g., 808). In some aspects, 904 can be performed by SI component 198.

[0109] At 906, the UE can skip monitoring of system information change indications in the first PO or the first PO group in response to receiving a PEI. For example, UE 802 can skip monitoring of system information change indications in the first PO or the first PO group in response to receiving a PEI (e.g., at 810). In some aspects, 906 can be performed by SI component 198.

[0110] Figure 10 This is a flowchart 1000 of a wireless communication method. The method can be executed by a UE (e.g., UE 104, UE 802; device 1104).

[0111] At 1002, the UE can receive configuration from a network entity for the initial DL BWP associated with the SDT procedure, wherein the SSB is configured to be sent in the initial DL BWP associated with the SDT procedure. For example, UE 802 can receive configuration for the initial DL BWP associated with the SDT procedure (e.g., 806) from network entity 804, wherein the SSB is configured to be sent in the initial DL BWP associated with the SDT procedure. In some aspects, 1002 can be performed by SI component 198. In some aspects, the SDT procedure is a Mobile Initiated (MO) SDT procedure or a Mobile Termination (MT) SDT procedure. In some aspects, the SSB is a Cell Defined (CD) SSB or a Non-Cell Defined (NCD) SSB. In some aspects, a system information change indication is included in the short message.

[0112] At 1004, the UE can receive a PEI from the network entity indicating that no paging PDCCH is scheduled for the first PO or the first PO group. For example, UE 802 can receive a PEI from network entity 804 indicating that no paging PDCCH is scheduled for the first PO or the first PO group (e.g., 808). In some respects, 1004 can be performed by SI component 198.

[0113] At 1006, the UE may skip the monitoring of system information change indication in the first PO or the first PO group in response to receiving a PEI. For example, UE 802 may skip the monitoring of system information change indication in the first PO or the first PO group in response to receiving a PEI (e.g., at 810). In some aspects, 1006 may be performed by SI component 198.

[0114] At 1010, the UE may determine to skip monitoring of system information change indication in the first PO or the first PO group in response to receiving a PEI. For example, UE 802 may determine to skip monitoring of system information change indication in the first PO or the first PO group in response to receiving a PEI. In some aspects, 1010 may be performed by SI component 198.

[0115] At 1012, the UE can determine, based on the received PEI indicating that no PDCCH was scheduled for the first PO or the first PO group, that there are no system information changes in the subsequent system information modification period associated with the first PO or the first PO group. For example, UE 802 can determine, based on the received PEI indicating that no PDCCH was scheduled for the first PO or the first PO group, that there are no system information changes in the subsequent system information modification period associated with the first PO or the first PO group. In some aspects, 1012 can be performed by SI component 198.

[0116] At 1014, the UE may communicate with a network entity based on previous system information in a subsequent system information modification period associated with the first PO or the first PO group. For example, UE 802 may (e.g., at 812) communicate with network entity 804 based on previous system information in a subsequent system information modification period associated with the first PO or the first PO group. In some aspects, 1014 may be performed by SI component 198.

[0117] At 1022, the UE can monitor for system information change indications in a second PO or second PO group where no associated PEI indicating no paging PDCCH is received for that second PO or second PO group, wherein the second PO or second PO group is within a time interval associated with an SDT procedure, and wherein that time interval does not overlap with DL or UL transmissions having a higher priority than the SDT procedure. For example, UE 802 can (e.g., at 816) monitor for system information change indications in a second PO or second PO group where no associated PEI indicating no paging PDCCH is received for that second PO or second PO group, wherein the second PO or second PO group is within a time interval associated with an SDT procedure, and wherein that time interval does not overlap with DL or UL transmissions having a higher priority than the SDT procedure. In some aspects, 1022 can be performed by SI component 198.

[0118] At 1024, the UE may receive system information changes in a subsequent system information modification period associated with the second PO or the second PO group. For example, UE 802 may receive system information changes in a subsequent system information modification period associated with the second PO or the second PO group (e.g., 818). In some aspects, 1024 may be performed by SI component 198.

[0119] At 1026, the UE can receive information indicating higher priority from a network entity via SI configuration, RRC configuration, DCI, or MAC CE. For example, UE 802 can receive information indicating higher priority from a network entity via SI configuration, RRC configuration, DCI, or MAC CE (e.g., 807). In some aspects, 1026 can be performed by SI component 198.

[0120] At 1028, the UE can detect the presence of an additional PEI associated with the second PO or the second PO group. For example, UE802 can detect the presence of an additional PEI (e.g., 814) associated with the second PO or the second PO group. In some respects, 1028 can be performed by SI component 198.

[0121] At 1030, the UE can monitor the system information change indication in the second PO or the second PO group based on the failure of the cyclic redundancy check (CRC) associated with the PEI. For example, UE 802 can monitor the system information change indication in the second PO or the second PO group based on the failure of the cyclic redundancy check (CRC) associated with the PEI. In some respects, 1030 can be performed by SI component 198.

[0122] At 1032, the UE can skip monitoring of an associated PEI based on scheduling from a network entity, a conflict associated with the associated PEI, or a capability associated with the UE. For example, UE 802 can skip monitoring of an associated PEI based on scheduling from a network entity, a conflict associated with the associated PEI, or a capability associated with the UE. In some respects, 1032 can be performed by SI component 198.

[0123] In some respects, a valid PO or valid PO group used to monitor system information change indications meets at least one of the following conditions: the valid PO or valid PO group is included in the time interval used for the SDT procedure; the valid PO or valid PO group does not overlap with a higher priority downlink transmission or a higher priority uplink transmission; firstly, there is no PEI that skips PO monitoring; secondly, there is no support for receiving PEI associated with a valid PO or valid PO group; and thirdly, there are no PEI resources in the configuration for the initial DL BWP associated with a valid PO or valid PO group; or the monitoring opportunity for PEI associated with a valid PO or valid PO group is skipped.

[0124] In some respects, the UE may skip monitoring of system information change indications in the third PO or third PO group, in which an associated PEI indicating no paging PDCCH is received, wherein the third PO or third PO group is not within the time interval associated with the SDT procedure, or wherein the time interval overlaps with a DL transmission or UL transmission having a higher priority than the SDT procedure.

[0125] Figure 11 This is a flowchart 1100 of a wireless communication method. This method can be performed by a UE (e.g., UE 104, UE 852; device 1104).

[0126] At 1102, the UE can receive configuration from a network entity for the initial DL BWP associated with the SDT procedure, wherein the SSB is configured to be transmitted in the initial DL BWP associated with the SDT procedure. For example, UE 852 can receive configuration for the initial DL BWP associated with the SDT procedure (e.g., 856) from network entity 854, wherein the SSB is configured to be transmitted in the initial DL BWP associated with the SDT procedure. In some aspects, 1102 can be performed by SI component 198.

[0127] At 1104, the UE may monitor the system information change indication in the PO or PO group based on the condition of lack of support for a reception-associated PEI or the absence of PEI resources in the configuration used for the initial DL BWP. For example, UE 852 may (e.g., at 858) monitor the system information change indication in the PO or PO group based on the condition of lack of support for a reception-associated PEI or the absence of PEI resources in the configuration used for the initial DL BWP. In some aspects, 1104 may be performed by SI component 198. In some aspects, the condition is the lack of support for a reception-associated PEI. In some aspects, the condition is the absence of PEI resources in the configuration used for the initial DL BWP. In some aspects, the system information change indication is included in the short message.

[0128] Figure 12Figure 1200 illustrates an example of a hardware implementation for device 1204. Device 1204 may be a UE, a component of a UE, or implement UE functionality. In some aspects, device 1204 may include at least one cellular baseband processor 1224 (also referred to as a modem) coupled to one or more transceivers 1222 (e.g., cellular RF transceivers). Cellular baseband processor 1224 may include at least one on-chip memory 1224'. In some aspects, device 1204 may also include one or more Subscriber Identity Module (SIM) cards 1220 and at least one application processor 1206 coupled to a Secure Digital Card (SD) card 1208 and a screen 1210. Application processor 1206 may include on-chip memory 1206'. In some aspects, device 1204 may also include a Bluetooth module 1212, a WLAN module 1214, an SPS module 1216 (e.g., a GNSS module), one or more sensor modules 1218 (e.g., a barometric pressure sensor / altimeter; motion sensors such as an inertial measurement unit (IMU), gyroscope, and / or accelerometer; light detection and ranging (LIDAR), radio-assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), magnetometer, audio, and / or other technologies for positioning), an additional memory module 1226, a power source 1230, and / or a camera 1232. Bluetooth module 1212, WLAN module 1214, and SPS module 1216 may include on-chip transceivers (TRX) (or in some cases only receivers (RX)). Bluetooth module 1212, WLAN module 1214, and SPS module 1216 may include their own dedicated antennas and / or communicate using antenna 1280. Cellular baseband processor 1224 communicates with UE 104 and / or RU associated with network entity 1202 via transceiver 1222 through one or more antennas 1280. Cellular baseband processor 1224 and application processor 1206 may each include computer-readable media / memory 1224', 1206'. Additional memory module 1226 may also be considered computer-readable media / memory. Each computer-readable media / memory 1224', 1206', 1226 may be non-transitory. Cellular baseband processor 1224 and application processor 1206 are each responsible for general processing, including the execution of software stored on the computer-readable media / memory. When executed by cellular baseband processor 1224 / application processor 1206, the software causes cellular baseband processor 1224 / application processor 1206 to perform the various functions described above. The computer-readable media / memory may also be used to store data manipulated by cellular baseband processor 1224 / application processor 1206 during software execution.Cellular baseband processor 1224 / application processor 1206 may be a component of UE 350 and may include at least one memory 360 and / or at least one of the following: TX processor 368, RX processor 356, and controller / processor 359. In some aspects, device 1204 may be at least one processor chip (modem and / or application) and may only include cellular baseband processor 1224 and / or application processor 1206, and in another configuration, device 1204 may be the entire UE (see, for example). Figure 3 The UE 350 includes an additional module of the device 1204.

[0129] As discussed above, SI component 198 can be configured to receive configuration from a network entity for an initial DL BWP associated with an SDT procedure, wherein an SSB is configured to be transmitted in the initial DL BWP associated with the SDT procedure. In some aspects, SI component 198 can be further configured to receive from a network entity an indication that no PDCCH paging is scheduled for the first PO or the first PO group. In some aspects, SI component 198 can be further configured to skip monitoring of system information change indications in the first PO or the first PO group in response to receiving a PEI. SI component 198 can reside within cellular baseband processor 1224, application processor 1206, or both cellular baseband processor 1224 and application processor 1206. Component 198 can be one or more hardware components specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors can execute the stated process / algorithm individually or in combination. As shown, apparatus 1204 may include various components configured for various functions. In some aspects, apparatus 1204 (and particularly cellular baseband processor 1224 and / or application processor 1206) may include components for receiving from a network entity configuration for an initial DL BWP associated with an SDT procedure, wherein an SSB is configured to be transmitted in the initial DL BWP associated with the SDT procedure. In some aspects, apparatus 1204 may include components for receiving from a network entity an indication that no PEI has been scheduled to paging PDCCH for a first PO or first PO group. In some aspects, apparatus 1204 may include components for skipping monitoring of system information change indications in the first PO or first PO group in response to receiving a PEI. In some aspects, apparatus 1204 may include components for determining to skip monitoring of system information change indications in the first PO or first PO group in response to receiving a PEI. In some aspects, apparatus 1204 may include components for determining, based on a received PEI indicating that no PDCCH was scheduled for the first PO or the first PO group, that there is no system information change in a subsequent system information modification cycle associated with the first PO or the first PO group. In some aspects, apparatus 1204 may include components for communicating with network entities based on previous system information in a subsequent system information modification cycle associated with the first PO or the first PO group.In some aspects, apparatus 1204 may include components for monitoring system information change indications in a second PO or second PO group where no associated PEI indicating no PDCCH paging is received for that second PO or second PO group, wherein the second PO or second PO group is within a time interval associated with an SDT procedure, and wherein that time interval does not overlap with DL transmissions or uplink (UL) transmissions having a higher priority than the SDT procedure. In some aspects, apparatus 1204 may include components for receiving system information changes in subsequent system information modification cycles associated with the second PO or second PO group. In some aspects, apparatus 1204 may include components for receiving information indicating higher priority from a network entity via system information configuration, radio resource control (RRC) configuration, downlink control information (DCI), or media access control (MAC) control element (MAC CE). In some aspects, apparatus 1204 may include components for detecting the presence of additional PEIs associated with the second PO or second PO group. In some aspects, apparatus 1204 may include components for monitoring system information change indications in a second PO or a second PO group based on the failure of a cyclic redundancy check (CRC) associated with the PEI. In some aspects, apparatus 1204 may include components for skipping monitoring of an associated PEI based on scheduling from a network entity, a conflict associated with the associated PEI, or a capability associated with the UE. In some aspects, apparatus 1204 may include components for skipping monitoring of system information change indications in a third PO or a third PO group, in which an associated PEI indicating no PDCCH paging is received, wherein the third PO or third PO group is not within a time interval associated with an SDT procedure, or wherein such time interval overlaps with a DL transmission or uplink (UL) transmission having a higher priority than the SDT procedure.

[0130] In some aspects, apparatus 1204 (and particularly cellular baseband processor 1224 and / or application processor 1206) may include components for receiving configurations from network entities for an initial DL BWP associated with an SDT procedure, wherein an SSB is configured to be transmitted in the initial DL BWP associated with the SDT procedure. In some aspects, apparatus 1204 may include components for monitoring system information change indications in a PO or PO group based on conditions such as a lack of support for receiving an associated PEI or the absence of PEI resources in the configuration for the initial DL BWP.

[0131] The component may be a part 198 of device 1204 configured to perform the functions described therein. As described above, device 1204 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Therefore, in some aspects, the component may be a TX processor 368, an RX processor 356, and / or a controller / processor 359 configured to perform the functions described therein.

[0132] It should be understood that the specific order or hierarchy of the boxes in the disclosed process / flowcharts is merely an example of the exemplary method. It should be understood that the specific order or hierarchy of the boxes in the process / flowcharts may be rearranged based on design preferences. Furthermore, some boxes may be combined or omitted. The appended method claims present the elements of various boxes in a sample order, but are not limited to the given specific order or hierarchy.

[0133] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not limited to the aspects described herein but should be given the full scope consistent with the language of the claims. Unless specifically stated otherwise, references to elements in the singular form do not mean “one and only one” but rather “one or more.” Terms such as “if,” “when,” and “simultaneously” do not imply an immediate temporal relationship or reaction. That is, these phrases, such as “when,” do not imply an immediate action in response to or during the occurrence of an action, but simply suggest that if a condition is met, then the action will occur, but without requiring a specific or immediate temporal constraint on the occurrence of the action. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or superior to other aspects. Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" can be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a collection of elements in which the number of elements is one or more. Therefore, for a set of X, X will include one or more elements. When at least one processor is configured to execute a set of functions, the at least one processor is configured to execute the set of functions individually or in any combination. Therefore, each of the at least one processor can be configured to perform a specific subset of the set of functions, wherein the subset is the complete set, a suitable subset of the set, or an empty subset of the set. If the first device receives data from or sends data to the second device, data can be received / sent directly between the first and second devices, or indirectly between the first and second devices via a set of devices. A device configured to “output” data (such as transmission, signaling, or messaging) can, for example, transmit the data using a transceiver, or can transmit the data to the device that sent the data. A device configured to “receive” data (such as transmission, signaling, or messaging) can, for example, receive the data using a transceiver, or can obtain the data from the device that received the data.Information stored in memory includes instructions and / or data. All structural and functional equivalents of the elements throughout the various aspects described herein that are known to or will later be known to a person skilled in the art are expressly incorporated herein by reference and are covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is expressly recited in the claims. The terms “module,” “mechanism,” “element,” “device,” etc., cannot replace the word “component.” Therefore, no claim element will be construed as a functional component unless the element is expressly recited using the phrase “component for…”.

[0134] As used herein, the phrase “based on” should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase “based on A” (where “A” can be information, conditions, factors, etc.) should be interpreted as “based on at least A”, unless otherwise specified.

[0135] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

[0136] Aspect 1 is a method for wireless communication at a user equipment (UE), the method comprising: receiving from a network entity a configuration for an initial downlink (DL) bandwidth portion (BWP) associated with a small data transmission (SDT) procedure, wherein a synchronization signal block (SSB) is configured to be transmitted in the initial DL BWP associated with the SDT procedure; receiving from the network entity a paging advance indication (PEI) indicating that no paging physical downlink control channel (PDCCH) is scheduled for a first paging opportunity (PO) or a first PO group; and, in response to receiving the PEI, skipping the monitoring of a system information change indication in the first PO or the first PO group.

[0137] Aspect 2 is the method according to aspect 1, the method further comprising: determining, in response to receiving the PEI, to skip the monitoring of the system information change indication in the first PO or the first PO group.

[0138] Aspect 3 is the method according to any one of Aspects 1 to 2, the method further comprising: determining, based on the PEI indicating that no PDCCH is scheduled for the first PO or the first PO group, that there is no system information change in a subsequent system information modification period associated with the first PO or the first PO group; and communicating with the network entity based on previous system information in the subsequent system information modification period associated with the first PO or the first PO group.

[0139] Aspect 4 is the method according to any one of Aspects 1 to 3, the method further comprising: monitoring the system information change indication in a second PO or a second PO group, wherein no associated PEI indicating no paging PDCCH is received for the second PO or the second PO group, wherein the second PO or the second PO group is within a time interval associated with the SDT process, and wherein the time interval does not overlap with a DL transmission or uplink (UL) transmission having a higher priority than the SDT process.

[0140] Aspect 5 is the method according to aspect 4, the method further comprising: receiving system information changes in a subsequent system information modification cycle associated with the second PO or the second PO group.

[0141] Aspect 6 is the method according to any one of Aspects 4 to 5, the method further comprising: receiving information indicating a higher priority from the network entity via System Information (SI) configuration, Radio Resource Control (RRC) configuration, Downlink Control Information (DCI) or Media Access Control (MAC) control element (MAC CE).

[0142] Aspect 7 is the method according to any one of Aspects 4 to 6, wherein the second PO or the second PO group is associated with an additional PEI indicating a paging PDCCH for the UE.

[0143] Aspect 8 is the method according to any one of Aspects 4 to 7, the method further comprising: detecting the presence of an additional PEI associated with the second PO or the second PO group; and monitoring the system information change indication in the second PO or the second PO group based on the failure of the cyclic redundancy check (CRC) associated with the PEI.

[0144] Aspect 9 is the method according to aspect 4, the method further comprising: skipping the monitoring of the associated PEI based on scheduling from the network entity, a conflict associated with the associated PEI, or a capability associated with the UE.

[0145] Aspect 10 is the method according to aspect 9, wherein the capability indicates half-duplex (HD), and the method further includes: skipping monitoring of the associated PEI based on the capability indicating the HD.

[0146] Aspect 11 is the method according to any one of Aspects 1 to 10, wherein a valid PO or valid PO group for monitoring the system information change indication satisfies at least one of the following conditions: the valid PO or the valid PO group is included in the time interval for the SDT process; the valid PO or the valid PO group does not overlap with a higher priority downlink transmission or a higher priority uplink transmission; firstly, there is no PEI that skips PO monitoring; secondly, there is no PEI resource in the configuration for the initial DL BWP associated with the valid PO or the valid PO group; or the monitoring opportunity for the PEI associated with the valid PO or the valid PO group is skipped.

[0147] Aspect 12 is a method according to any one of Aspects 1 to 11, the method further comprising: skipping the monitoring of the system information change indication in a third PO or a third PO group, in which an associated PEI indicating that no PDCCH is being paged is received, wherein the third PO or the third PO group is not within a time interval associated with the SDT procedure, or wherein the time interval overlaps with a DL transmission or uplink (UL) transmission having a higher priority than the SDT procedure.

[0148] Aspect 13 is the method according to any one of aspects 1 to 12, wherein the SDT process is a Mobility Initiation (MO) SDT process or a Mobility Termination (MT) SDT process.

[0149] Aspect 14 is the method according to any one of aspects 1 to 13, wherein the SSB is a cell-defined (CD) SSB or a non-cell-defined (NCD) SSB.

[0150] Aspect 15 is the method according to any one of aspects 1 to 14, wherein the system information change indication is included in the short message.

[0151] Aspect 16 is a method for wireless communication at a user equipment (UE), the method comprising: receiving from a network entity a configuration for an initial downlink (DL) bandwidth portion (BWP) associated with a small data transmission (SDT) procedure, wherein a synchronization signal block (SSB) is configured to be transmitted in the initial DL BWP associated with the SDT procedure; and monitoring for a system information change indication in a paging timing (PO) or PO group based on a lack of support for a reception-associated paging advance indication (PEI) or the absence of PEI resources in the configuration for the initial DL BWP.

[0152] Aspect 17 is the method according to aspect 16, wherein the condition is the lack of support for receiving the associated PEI.

[0153] Aspect 18 is the method according to aspect 16, wherein the condition is that the PEI resource does not exist in the configuration used for the initial DL BWP.

[0154] Aspect 19 is the method according to any one of aspects 16 to 18, wherein the system information change indication is included in a short message.

[0155] Aspect 20 is an apparatus for wireless communication at a device, the apparatus comprising: at least one memory; and at least one processor coupled to the at least one memory and based at least in part on information stored in the at least one memory, the at least one processor being configured individually or in combination to implement any one of aspects 1 to 15.

[0156] Aspect 21 is the apparatus according to aspect 19, the apparatus further comprising one or more transceivers or one or more antennas coupled to the at least one processor.

[0157] Aspect 22 is an apparatus for wireless communication at a device, the apparatus including components for implementing any one of aspects 1 to 15.

[0158] Aspect 23 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer-executable code, wherein the code, when executed by at least one processor, causes the at least one processor to implement any one of aspects 1 to 15.

[0159] Aspect 24 is an apparatus for wireless communication at a device, the apparatus comprising: at least one memory; and at least one processor coupled to the at least one memory and based at least in part on information stored in the at least one memory, the at least one processor being configured individually or in combination to implement any one of aspects 16 to 19.

[0160] Aspect 25 is the apparatus according to aspect 23, the apparatus further comprising one or more transceivers or one or more antennas coupled to the at least one processor.

[0161] Aspect 26 is an apparatus for wireless communication at a device, the apparatus including components for implementing any one of aspects 16 to 19.

[0162] Aspect 27 is a computer-readable medium (e.g., a non-transitory computer-readable medium) that stores computer-executable code, wherein the code, when executed by at least one processor, causes the at least one processor to implement any one of aspects 16 to 19.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: At least one memory; and At least one processor, coupled to the at least one memory, and based at least in part on stored information stored in the at least one memory, the at least one processor being configured individually or in any combination to cause the device to: Receive configuration from network entities for an initial downlink (DL) bandwidth portion (BWP) associated with a small data delivery (SDT) process, wherein a synchronization signal block (SSB) is configured to be transmitted in the initial DL BWP associated with the SDT process; The network entity receives an indication that there is no paging advance indication (PEI) for the first paging opportunity (PO) or the first PO group scheduling the paging physical downlink control channel (PDCCH); and In response to receiving the PEI, the monitoring of system information change indications in the first PO or the first PO group is skipped.

2. The apparatus of claim 1, wherein the at least one processor is configured, individually or in any combination, to cause the apparatus to: In response to receiving the PEI, it is determined to skip the monitoring of the system information change indication in the first PO or the first PO group.

3. The apparatus of claim 1, wherein the at least one processor is configured, individually or in any combination, to cause the apparatus to: Based on the received indication that no PDCCH was scheduled for the first PO or the first PO group, the PEI determines that there are no system information changes in subsequent system information modification periods associated with the first PO or the first PO group; and The network entity is communicated based on previous system information in the subsequent system information modification cycle associated with the first PO or the first PO group.

4. The apparatus of claim 1, wherein the at least one processor is configured, individually or in any combination, to cause the apparatus to: The system information change indication is monitored in the second PO or the second PO group. For the second PO or the second PO group, no associated PEI indicating that no PDCCH is being paged is received, wherein the second PO or the second PO group is within the time interval associated with the SDT process, and wherein the time interval does not overlap with DL transmissions or uplink (UL) transmissions with a higher priority than the SDT process.

5. The apparatus of claim 4, wherein the at least one processor is configured, individually or in any combination, to cause the apparatus to: Information indicating higher priority is received from the network entity via System Information (SI) configuration, Radio Resource Control (RRC) configuration, Downlink Control Information (DCI) or Media Access Control (MAC) control element (MAC CE).

6. The apparatus of claim 4, wherein the at least one processor is configured, individually or in any combination, to cause the apparatus to: Detect the presence of additional PEI associated with the second PO or the second PO group; and The system information change indication is monitored in the second PO or the second PO group based on the failure of the cyclic redundancy check (CRC) associated with the PEI.

7. The apparatus of claim 4, wherein the at least one processor is configured, individually or in any combination, to cause the apparatus to: Monitoring of the associated PEI can be skipped based on scheduling from the network entity, conflicts associated with the associated PEI, or capabilities associated with the UE.

8. The apparatus of claim 7, wherein the capability indicates half-duplex (HD), and wherein the at least one processor is configured individually or in any combination to enable the apparatus to: Based on the aforementioned capability, the HD is instructed to skip monitoring of the associated PEI.

9. The apparatus of claim 4, wherein a valid PO or a group of valid POs for monitoring the system information change indication satisfies at least one of the following conditions: The valid PO or the group of valid POs is included in the time interval used for the SDT process. The valid PO or the group of valid POs does not overlap with higher priority downlink transmissions or higher priority uplink transmissions. Firstly, there is no PEI that skips PO monitoring. There is a lack of support for receiving the PEI associated with the valid PO or the group of valid POs. The second is that there are no PEI resources in the configuration for the initial DL BWP associated with the valid PO or the group of valid POs, or The monitoring of the PEI associated with the valid PO or the group of valid POs is skipped.

10. The apparatus of claim 1, wherein the at least one processor is configured, individually or in any combination, to cause the apparatus to: Skip monitoring of the system information change indication in the third PO or the third PO group, in which an associated PEI indicating no PDCCH paging is received, wherein the third PO or the third PO group is not within the time interval associated with the SDT procedure, or wherein the time interval overlaps with a DL transmission or uplink (UL) transmission with a higher priority than the SDT procedure.

11. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: At least one memory; and At least one processor, coupled to the at least one memory, and based at least in part on stored information stored in the at least one memory, the at least one processor being configured individually or in any combination to cause the device to: Receive configuration from network entities for an initial downlink (DL) bandwidth portion (BWP) associated with a small data delivery (SDT) process, wherein a synchronization signal block (SSB) is configured to be transmitted in the initial DL BWP associated with the SDT process; as well as Based on the lack of support for receive-associated advance paging indication (PEI) or the absence of PEI resources in the configuration used for the initial DL BWP, the system information change indication is monitored in the paging timing (PO) or PO group.

12. A method for conducting wireless communication at a user equipment (UE), the method comprising: Receive configuration from network entities for an initial downlink (DL) bandwidth portion (BWP) associated with a small data delivery (SDT) process, wherein a synchronization signal block (SSB) is configured to be transmitted in the initial DL BWP associated with the SDT process; The network entity receives an indication that there is no paging advance indication (PEI) for the first paging opportunity (PO) or the first PO group scheduling the paging physical downlink control channel (PDCCH); and In response to receiving the PEI, the monitoring of system information change indications in the first PO or the first PO group is skipped.

13. The method according to claim 12, further comprising: In response to receiving the PEI, it is determined to skip the monitoring of the system information change indication in the first PO or the first PO group.

14. The method of claim 12, further comprising: Based on the received indication that no PDCCH was scheduled for the first PO or the first PO group, the PEI determines that there are no system information changes in subsequent system information modification periods associated with the first PO or the first PO group; and The network entity is communicated based on previous system information in the subsequent system information modification cycle associated with the first PO or the first PO group.

15. The method according to claim 12, further comprising: The system information change indication is monitored in the second PO or the second PO group. For the second PO or the second PO group, no associated PEI indicating that no PDCCH is being paged is received, wherein the second PO or the second PO group is within the time interval associated with the SDT process, and wherein the time interval does not overlap with DL transmissions or uplink (UL) transmissions with a higher priority than the SDT process.

16. The method according to claim 15, further comprising: Information indicating higher priority is received from the network entity via System Information (SI) configuration, Radio Resource Control (RRC) configuration, Downlink Control Information (DCI) or Media Access Control (MAC) control element (MAC CE).

17. The method of claim 15, further comprising: Detect the presence of additional PEI associated with the second PO or the second PO group; as well as The system information change indication is monitored in the second PO or the second PO group based on the failure of the cyclic redundancy check (CRC) associated with the PEI.

18. The method according to claim 15, further comprising: Monitoring of the associated PEI can be skipped based on scheduling from the network entity, conflicts associated with the associated PEI, or capabilities associated with the UE.

19. The method of claim 18, wherein the capability indicates half-duplex (HD), the method further comprising: Based on the aforementioned capability, the HD is instructed to skip monitoring of the associated PEI.

20. The method of claim 15, wherein a valid PO or a group of valid POs for monitoring the system information change indication satisfies a condition based on at least one of the following: The valid PO or the group of valid POs is included in the time interval used for the SDT process. The valid PO or the group of valid POs does not overlap with higher priority downlink transmissions or higher priority uplink transmissions. Firstly, there is no PEI that skips PO monitoring. There is a lack of support for receiving the PEI associated with the valid PO or the group of valid POs. The second is that there are no PEI resources in the configuration for the initial DL BWP associated with the valid PO or the group of valid POs, or The monitoring of the PEI associated with the valid PO or the group of valid POs is skipped.

Images