Method and apparatus for system information block type 1 (SIB1) request operation

Abstract

A method performed by a User Equipment (UE) for performing a System Information Block Type 1 (SIB1) request operation is provided. The method receives, from a first cell, a Wake-Up Signal (WUS) configuration. The method transmits, to a Network Energy Saving (NES) cell, an Uplink (UL) WUS based on the WUS configuration to request an On-Demand (OD)-SIB1. Upon determining that a Physical Downlink Control Channel (PDCCH) has been successfully decoded with a first Radio Network Temporary Identifier (RNTI), the method receives the OD-SIB1 based on the PDCCH scrambled by the first RNTI. Upon determining that the PDCCH has been unsuccessfully decoded with the first RNTI, the method attempts to decode the PDCCH with a second RNTI. Upon determining that the PDCCH has been successfully decoded with the second RNTI, the method receives a Random Access Response (RAR) based on the PDCCH scrambled by the second RNTI.　

Description

METHOD AND APPARATUS FOR SYSTEM INFORMATION BLOCK TYPE 1 (SIB1) REQUEST OPERATION

[0001] The present disclosure is related to wireless communication and, more specifically, to a User Equipment (UE), Base Station (BS), and method for Network Energy Saving (NES) in the wireless communication networks.

[0002] Various efforts have been made to improve different aspects of wireless communication for the cellular wireless communication systems, such as the 5thGeneration (5G) New Radio (NR), by improving data rate, latency, reliability, and mobility. The 5G NR system is designed to provide flexibility and configurability to optimize network services and types, accommodating various use cases, such as enhanced Mobile Broadband (eMBB), massive Machine-Type Communication (mMTC), and Ultra-Reliable and Low-Latency Communication (URLLC). As the demand for radio access continues to grow, however, there exists a need for further improvements in the next-generation wireless communication systems, such as improvements in network energy saving.

[0003] The present disclosure is related to a UE, a BS, and a method for a SIB1 request operation in the wireless communication networks.

[0004] In a first aspect of the present disclosure, a UE for performing a SIB1 request operation is provided. The UE includes at least one processor and at least one non-transitory computer-readable medium that is coupled to the at least one processor and that stores one or more computer-executable instructions. The computer-executable instructions, when executed by the at least one processor, cause the UE to: receive, from a first cell , a Wake-Up Signal (WUS) configuration; transmit, to a Network Energy Saving (NES) cell, an Uplink (UL) WUS based on the WUS configuration to request an On-Demand (OD)-SIB1; monitor a Physical Downlink Control Channel (PDCCH) in the NES cell; attempt to decode the PDCCH with a first Radio Network Temporary Identifier (RNTI); in response to determining that the PDCCH has been successfully decoded with the first RNTI, receive the OD-SIB1 based on the PDCCH scrambled by the first RNTI; in response to determining that the PDCCH has been unsuccessfully decoded with the first RNTI, attempt to decode the PDCCH with a second RNTI ; and in response to determining that the PDCCH has been successfully decoded with the second RNTI, receive a Random Access Response (RAR) based on the PDCCH scrambled by the second RNTI.

[0005] In some implementations of the first aspect, monitoring the PDCCH in the NES cell includes monitoring the PDCCH in the NES cell based on a search space zero and a Control Resource Set (CORESET) zero in a case that the UE is not provided with a Random Access (RA) search space in the WUS configuration.

[0006] In some implementations of the first aspect, monitoring the PDCCH in the NES cell includes monitoring the PDCCH in the NES cell based on an RA search space provided in the WUS configuration.

[0007] In some implementations of the first aspect, the first RNTI includes a System Information (SI)-RNTI

[0008] In some implementations of the first aspect, the second RNTI includes an RA-RNTI.

[0009] In a second aspect of the present application, a BS for supporting a SIB1 request operation is provided. The BS includes at least one processor and at least one non-transitory computer-readable medium that is coupled to the at least one processor and that stores one or more computer-executable instructions. The computer-executable instructions, when executed by the at least one processor, cause the BS to: receive, from a UE via an NES cell, an UL WUS requesting an OD-SIB1, the UL WUS being based on a WUS configuration provided by a first cell; scramble a PDCCH with either a first RNTI or a second RNTI; transmit the OD-SIB1 to the UE in response to scrambling the PDCCH with the first RNTI; and transmit an RAR to the UE in response to scrambling the PDCCH with the second RNTI.

[0010] In some implementations of the second aspect, the UE monitors the PDCCH in the NES cell based on a search space zero and a CORESET zero in a case that the UE is not provided with an RA search space in the WUS configuration.

[0011] In some implementations of the second aspect, the UE monitors the PDCCH in the NES cell based on an RA search space provided in the WUS configuration.

[0012] In some implementations of the second aspect, the first RNTI includes an SI-RNTI.

[0013] In some implementations of the second aspect, the second RNTI includes an RA-RNTI.

[0014] In a third aspect of the present application, a method performed by a UE for performing a SIB1 request operation is provided. The method includes: receiving, from a first cell, a WUS configuration; transmitting, to an NES cell, an UL WUS based on the WUS configuration to request an OD-SIB1; monitoring a PDCCH in the NES cell; attempting to decode the PDCCH with a first RNTI; in response to determining that the PDCCH has been successfully decoded with the first RNTI, receiving the OD-SIB1 based on the PDCCH scrambled by the first RNTI; in response to determining that the PDCCH has been unsuccessfully decoded with the first RNTI, attempting to decode the PDCCH with a second RNTI; and in response to determining that the PDCCH has been successfully decoded with the second RNTI, receiving an RAR based on the PDCCH scrambled by the second RNTI.

[0015] Aspects of the present disclosure are best understood from the following detailed disclosure when read with the accompanying drawings. Various features are not drawn to scale. Dimensions of various features may be arbitrarily increased or reduced for clarity of discussion.

[0016] FIG. 1 is a flowchart illustrating a method / process performed by a UE for performing a SIB1 request operation, according to an example implementation of the present disclosure.

[0017] FIG. 2 is a flowchart illustrating a method / process performed by a BS for supporting a SIB1 request operation, according to an example implementation of the present disclosure.

[0018] FIG. 3 is a block diagram illustrating a node for wireless communication, according to an example implementation of the present disclosure.

[0019] The following contains specific information related to implementations of the present disclosure. The drawings and their accompanying detailed disclosure are merely directed to implementations. However, the present disclosure is not limited to these implementations. Other variations and implementations of the present disclosure will be obvious to those skilled in the art.

[0020] Unless noted otherwise, like or corresponding elements among the drawings may be indicated by like or corresponding reference numerals. Moreover, the drawings and illustrations in the present disclosure are generally not to scale and are not intended to correspond to actual relative dimensions.

[0021] For the purposes of consistency and ease of understanding, like features may be identified (although, in some examples, not illustrated) by the same numerals in the drawings. However, the features in different implementations may be different in other respects and may not be narrowly confined to what is illustrated in the drawings.

[0022] References to “one implementation,” “an implementation,” “example implementation,” “various implementations,” “some implementations,” “implementations of the present application,” etc., may indicate that the implementation(s) of the present application so described may include a particular feature, structure, or characteristic, but not every possible implementation of the present application necessarily includes the particular feature, structure, or characteristic. Further, repeated use of the phrase “In some implementations,” or “in an example implementation,” “an implementation,” do not necessarily refer to the same implementation, although they may. Moreover, any use of phrases like “implementations” in connection with “the present application” are never meant to characterize that all implementations of the present application must include the particular feature, structure, or characteristic, and should instead be understood to mean “at least some implementations of the present application” includes the stated particular feature, structure, or characteristic. The term “coupled” is defined as connected, whether directly or indirectly through intervening components, and is not necessarily limited to physical connections. The term “comprising,” when utilized, means “including, but not necessarily limited to”; it specifically indicates open-ended inclusion or membership in the so-described combination, group, series, and the equivalent.

[0023] The expression “at least one of A, B and C” or “at least one of the following: A, B and C” means “only A, or only B, or only C, or any combination of A, B and C.” The terms “system” and “network” may be used interchangeably. The term “and / or” is only an association relationship for describing associated objects and represents that three relationships may exist such that A and / or B may indicate that A exists alone, A and B exist at the same time, or B exists alone. The character “ / ” generally represents that the associated objects are in an “or” relationship.

[0024] For the purposes of explanation and non-limitation, specific details, such as functional entities, techniques, protocols, and standards, are set forth for providing an understanding of the disclosed technology. In other examples, detailed disclosure of well-known methods, technologies, systems, and architectures are omitted so as not to obscure the present disclosure with unnecessary details.

[0025] Persons skilled in the art will immediately recognize that any network function(s) or algorithm(s) disclosed may be implemented by hardware, software, or a combination of software and hardware. Disclosed functions may correspond to modules which may be software, hardware, firmware, or any combination thereof.

[0026] A software implementation may include computer-executable instructions and / or Artificial Intelligence (AI) / Machine Learning (ML) module(s) stored on a computer-readable medium, such as memory or other type of storage devices. One or more microprocessors or general-purpose computers with communication processing capability may be programmed with corresponding computer-executable instructions and perform the disclosed network function(s), AI / ML module(s), or algorithm(s). The AI / ML module(s) may be implemented with a supervised learning approach, a semi-supervised learning approach, an unsupervised learning approach (e.g., Transductive approach and Inductive approach), a federated learning approach, or a reinforcement learning (RL) approach, but the present disclosure is not limited thereto. The computer-executable instructions associated with the AI module(s) and / or the ML module(s) may include but are not limited to, data management instructions (e.g., collection instructions, validation instructions…etc.), model monitoring and management instructions (e.g., network key performance indicators (KPIs) monitoring, model input / output monitoring, model selection / switching / update / upload / download, model (de)activation, model identification, functionality selection…etc.), and / or pre-process input instructions.

[0027] The microprocessors or general-purpose computers may include Application-Specific Integrated Circuits (ASICs), programmable logic arrays, Central Processing Units (CPUs), Tensor Processing Units (TPUs), Graphics Processing Units (GPUs), General-purpose computing on GPUs (GPGPU, or less often GPGP), and / or using one or more Digital Signal Processors (DSPs). Although some of the disclosed implementations are oriented to software installed and executing on computer hardware, alternative implementations implemented as firmware, as hardware, or as a combination of hardware and software are well within the scope of the present disclosure. The computer-readable medium may include, but is not limited to, Random Access Memory (RAM), Dynamic Random Access Memory (DRAM), High Bandwidth Memory (HBM), Magnetoresistive Random Access Memory (MRAM), Ferroelectric Random Access Memory (FRAM), Resistive Random Access Memory (RRAM), Read-Only Memory (ROM), Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), flash memory (or other memory technology), Compact Disc Read-Only Memory (CD-ROM) , Digital Versatile Disks (DVD) (or other optical disk storage), magnetic cassettes, magnetic tape, magnetic disk storage (or other magnetic storage devices), or any other equivalent medium capable of storing computer-readable instructions.

[0028] A radio communication network architecture such as a Long-Term Evolution (LTE) system, an LTE-Advanced (LTE-A) system, an LTE-Advanced Pro system, or a 5G NR Radio Access Network (RAN), 5G-Advanced (5G-A) system, or an open radio access network (O-RAN) may typically include at least one base station (BS), at least one UE, and one or more optional network elements that provide connection within a network. The BS and one or more optional network elements enable the UE to access a radio network. The UE may communicate with the network, such as a Core Network (CN), an Evolved Packet Core (EPC) network, an Evolved Universal Terrestrial RAN (E-UTRAN), a Next-Generation Core (NGC), a 5G Core (5GC), or an internet via a RAN established by one or more BSs and the network elements / functions.

[0029] A UE may include, but is not limited to, a mobile station, a mobile terminal or device, or a user communication radio terminal. The UE may be a portable radio equipment that includes, but is not limited to, a mobile phone, a tablet, a wearable device, a sensor, a vehicle, a virtual reality (VR) device, an augmented (AR) device, an Internet of Things (IoT) device, an unmanned aerial vehicle (UAV), or a Personal Digital Assistant (PDA) with wireless communication capability. The UE may be configured to receive and transmit signals over an air interface to one or more cells in a RAN. In some implementations, the UE may be an AI / ML-enabled device and / or an AI / ML capable device that is equipped with AI module(s) and / or ML module(s).

[0030] The BS may be configured to provide communication services according to at least a Radio Access Technology (RAT), such as Worldwide Interoperability for Microwave Access (WiMAX), Global System for Mobile communications (GSM) that is often referred to as 2G, GSM Enhanced Data rates for GSM Evolution (EDGE) RAN (GERAN), General Packet Radio Service (GPRS), Universal Mobile Telecommunication System (UMTS) that is often referred to as 3G based on basic Wideband-Code Division Multiple Access (W-CDMA), High-Speed Packet Access (HSPA), LTE, LTE-A, evolved / enhanced LTE (eLTE) that is LTE connected to 5GC, NR (often referred to as 5G), 5G-A, and / or LTE-A Pro. However, the scope of the present disclosure is not limited to these protocols.

[0031] The BS may include, but is not limited to, a node B (NB) in the UMTS, an evolved node B (eNB) in LTE or LTE-A, a radio network controller (RNC) in UMTS, a BS controller (BSC) in the GSM / GERAN, a next-generation eNB (ng-eNB) in an Evolved Universal Terrestrial Radio Access (E-UTRA) BS in connection with 5GC, a next-generation Node B (gNB) in the 5G-RAN or in the 5G Access Network (5G-AN), or any other apparatus capable of controlling radio communication and managing radio resources within a cell. The BS may serve one or more UEs via a radio interface. Although the gNB is used as an example in some implementations within the present disclosure, it should be noted that the disclosed implementations may also be applied to other types of base stations. In some implementations, the BS may be an AI / ML-enabled device and / or an AI / ML capable device that is equipped with AI module(s) and / or ML module(s).

[0032] The BS may be operable to provide radio coverage to a specific geographical area using multiple cells forming the RAN. The BS may support the operations of the cells. Each cell may be operable to provide services to at least one UE within its radio coverage.

[0033] Each cell (may often referred to as a serving cell) may provide services to one or more UEs within the cell’s radio coverage, such that each cell schedules the downlink (DL) (and optionally uplink (UL) resources) to at least one UE within its radio coverage for DL (and optionally UL packet transmissions from the UE). The BS may communicate with one or more UEs in the radio communication system via the cells.

[0034] A cell may allocate sidelink (SL) resources for supporting the Proximity Services (ProSe), LTE SL services, LTE / NR sidelink communication services, LTE / NR sidelink discovery services, and / or LTE / NR Vehicle-to-Everything (V2X) services. In addition, a cell may allocate DL and / or UL resources for supporting Multicast / Broadcast Service (MBS) services, Non-Terrestrial Networks (NTN) services, positioning services, power serving services and / or Network Energy Saving (NES) services.

[0035] In Multi-RAT Dual Connectivity (MR-DC) cases, the primary cell of a Master Cell Group (MCG) or a Secondary Cell Group (SCG) may be referred to as a Special Cell (SpCell). A Primary Cell (PCell) may include the SpCell of an MCG. A Primary SCG Cell (PSCell) may include the SpCell of an SCG. MCG may include a group of serving cells associated with the Master Node (MN), including the SpCell and optionally one or more Secondary Cells (SCells). An SCG may include a group of serving cells associated with the Secondary Node (SN), including the SpCell and optionally one or more SCells.

[0036] As discussed above, the frame structure for NR may support flexible configurations for accommodating various next generation (e.g., 5G) communication requirements, such as Enhanced Mobile Broadband (eMBB), Massive Machine Type Communication (mMTC), and Ultra-Reliable and Low-Latency Communication (URLLC), while fulfilling high reliability, high data rate, and low latency requirements. The Orthogonal Frequency-Division Multiplexing (OFDM) technology in the third generation partnership project (3GPP) may serve as a baseline for an NR waveform. The scalable OFDM numerology, such as adaptive sub-carrier spacing, channel bandwidth, and Cyclic Prefix (CP), may also be used.

[0037] Two coding schemes may be considered for NR, specifically, Low-Density Parity-Check (LDPC) code and Polar Code. The coding scheme adaption may be configured based on channel conditions and / or service applications.

[0038] At least the DL transmission data, a guard period, and UL transmission data should be included in a transmission time interval (TTI) of a single NR frame. The respective portions of the DL transmission data, the guard period, and the UL transmission data should also be configurable based on, for example, the network dynamics of NR. SL resources may also be provided in an NR frame to support ProSe services or V2X services.

[0039] Any two or more than two of the following paragraphs, (sub)-bullets, points, actions, behaviors, terms, or claims described in the present disclosure may be combined logically, reasonably, and properly to form a specific method.

[0040] Any sentence, paragraph, (sub)-bullet, point, action, behaviors, terms, or claims described in the present disclosure may be implemented independently and separately to form a specific method.

[0041] Dependency, e.g., “based on”, “more specifically”, “preferably”, “in one embodiment”, “in some implementations”, etc., in the present disclosure is just one possible example which would not restrict the specific method.

[0042] In some implementations, all the designs / embodiment / implementations introduced within this disclosure are not limited to be applied for dealing with the problems discussed within this disclosure. For example, the described embodiments may be applied to solve other problems that exist in the RAN of wireless communication systems. In some implementations, all of the numbers listed within the designs / embodiment / implementations introduced within this disclosure are just examples and for illustration, for example, of how the described methods are executed.

[0043] The terms, definitions, and abbreviations given in the present disclosure are either imported from existing documentation (e.g., European Telecommunications Standards Institute (ETSI), International Telecommunication Union (ITU), or elsewhere) or newly created by 3GPP experts whenever the need for precise vocabulary is identified.

[0044] Implementations in the present disclosure may be used, for example, in communication, a communication equipment (e.g., a mobile telephone apparatus, a base station apparatus, a wireless Local Area Network (LAN) apparatus, and / or a sensor device, etc.), an integrated circuit (e.g., a communication chip), and / or a program, etc.

[0045] Examples of some selected terms in the present disclosure are provided as follows.

[0046] User Equipment (UE): The UE may be referred to as the Physical (PHY), Medium Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP), or Service Data Adaptation Protocol (SDAP) entity. The PHY / MAC / RLC / PDCP / SDAP entity may also be referred to as the UE.

[0047] Radio Access Network (RAN) or Network (NW): The NW may be a network node, a Transmission Reception Point (TRP), a cell, an eNB, a gNB, and / or a base station, where the cell may include a Special Cell (SpCell), a Primary Cell (PCell), a Secondary Cell (SCell), and / or a Primary SCG Cell (PSCell).

[0048] Serving Cell: The serving cell may include a PCell, a PSCell, or an SCell. The serving cell may be an activated or a deactivated serving cell.

[0049] Special Cell (SpCell): For a Dual Connectivity operation, the term Special Cell may include the PCell of the MCG or the PSCell of the SCG depending on whether the MAC entity is associated with the MCG or the SCG, respectively. Otherwise, the term Special Cell may include the PCell. A Special Cell may support the Physical Uplink Control Channel (PUCCH) transmission and the contention-based Random Access and may be always activated.

[0050] Cell A: The term “Cell A” may represent a cell that is periodically transmitting at least its own SIB1.

[0051] NES Cell: The term “NES cell” may represent a cell that transmits the SIB1 in response to the UL WUS from a UE. In some implementations, the NES cell may transmit a Synchronization Signal Block (SSB), which may be referred to as “NES SSB.” The term “NES cell” may be also referred to as “OD-SIB1 cell” in the present disclosure.

[0052] Network energy saving (NES) is of great importance for environmental sustainability, to reduce environmental impact (e.g., greenhouse gas emissions), and for operational cost savings. As 5G is becoming pervasive across industries and geographical areas, handling more advanced services and applications requiring very high data rates (e.g., extended reality (XR)), networks are becoming denser and are using more antennas, larger bandwidths and more frequency bands. Novel solutions may be needed to improve network energy savings and mitigate the environmental impact of 5G.

[0053] One of the identified key techniques is on-demand SIB1. In legacy, SIB1 is always transmitted by at least every PCell and cannot be turned off. If SIB1 in a cell can be turned off, the cell can go to deep sleep mode, which can save much power. If there appears a UE in RRC_IDLE / RRC_INACTIVE state that needs SIB1, for, e.g., accessing the cell, the UE may send an UL WUS to the NW, e.g., through this cell, and the cell can transmit SIB1. This technique may be called “on-demand SIB1”.

[0054] One of the identified key techniques relates to on-demand SIB1. In legacy systems, SIB1 may always be transmitted by at least every PCell and may not be disabled. If SIB1 transmission in a cell may be turned off, the cell may enter a deep sleep mode, thereby allowing significant power savings. When a UE in the RRC_IDLE or RRC_INACTIVE state requires SIB1, for example, to access the cell, the UE may transmit an UL WUS to the network, such as via the cell, and the cell may then transmit SIB1. This technique may be referred to as “on-demand SIB1.”

[0055] Several scenarios may be considered for the OD-SIB1 for a UE in the idle or inactive state. In some implementations, the UE may obtain the UL WUS configuration from an NES cell, transmit a UL WUS to the NES cell, and receive the on-demand SIB1 from the NES cell. In some implementations, the UE may obtain the UL WUS configuration from a first cell (e.g., the Cell A), transmit a UL WUS to the NES cell, and receive the on-demand SIB1 from the NES cell. In some implementations, the UE may obtain the UL WUS configuration from the Cell A, transmit a UL WUS to the Cell A, and receive the on-demand SIB1 from the Cell A.

[0056] In some implementations, Cell A (e.g., Cell #1) may configure, transmit, or broadcast its own UL WUS configuration to UEs while still operating as Cell A. Cell #1 may later switch its NES functionality from Cell A to an NES cell, such that UEs may transmit a UL WUS to Cell #1 directly to request OD-SIB1. After receiving an OD-SIB1 request from a UE, Cell #1, operating as an NES cell at that time, may start broadcasting SIB1 within a given time period.

[0057] Table 1 illustrates parameters in an example WUS configuration, according to an example implementation of the present disclosure.

[0058] In some implementations, when a UE is not provided or configured with an RA search space for an RAR, the UE may use search space zero (SS#0) for RAR reception, where the RAR may be a response message to an UL-WUS transmission for the OD-SIB1. The UE may also use control resource set zero (CORESET#0) for PDCCH monitoring for RAR reception. Therefore, the UE may perform PDCCH monitoring for RAR reception based on SS#0 and CORESET#0, for example, when the UE is not provided with an RA search space for RAR reception or monitoring. In such case, when the UE detects a PDCCH candidate, DCI, a PDCCH occasion, or a PDCCH instance according to SS#0 and CORESET#0, the RNTI used for decoding the PDCCH candidate or the DCI may be an RA-RNTI, an SI-RNTI, or an RNTI used for scrambling a PDCCH for OD-SIB1. In some implementations, after transmitting the UL-WUS and before RAR reception, the UE may detect or decode a PDCCH candidate or a DCI according to SS#0 and CORESET#0 using the SI-RNTI or an RNTI used for scrambling the PDCCH for OD-SIB1.

[0059] If the UE successfully decodes a PDCCH candidate or a DCI according to SS#0 and CORESET#0 using an SI-RNTI or an RNTI used for scrambling a PDCCH for the OD-SIB1, the UE may not need to receive an RAR, or may not need to decode a PDCCH candidate or a DCI according to SS#0 and CORESET#0 using an RA-RNTI, since the UE may directly detect the PDCCH or DCI that schedules the OD-SIB1. Decoding a PDCCH candidate using multiple RNTIs may impose additional processing burden on the UE, and skipping RAR reception may reduce power consumption at the UE and the network, for example by avoiding transmission of an RAR or by reducing the number of RAR transmissions.

[0060] In some implementations, the UE may attempt to decode PDCCH candidates, PDCCH instances, or PDCCH occasions according to SS#0 and CORESET#0 using the SI-RNTI or an RNTI used for scrambling a PDCCH for OD-SIB1 as a higher-priority RNTI in an RNTI decoding sequence. The UE may attempt decoding the same PDCCH candidates / instances / occasions using an RA-RNTI, or an RNTI associated with the transmitted UL-WUS or the physical resource used to transmit the UL-WUS, only after the UE does not successfully obtain the intended OD-SIB1 based on decoding using the SI-RNTI or the RNTI used for scrambling the PDCCH for OD-SIB1. The RA-RNTI, or an RNTI specific to PDCCH decoding for RAR reception or UL-WUS response reception, may be treated as a lower-priority RNTI in the RNTI decoding sequence.

[0061] In some implementations, the UE behavior described above may be predefined in a 3GPP specification, preconfigured or stored in a memory module of the UE, or configured by a serving RAN via broadcasting system information (e.g., via an SI on-demand procedure), or via UE-specific control signaling (e.g., DL RRC signaling within a UL-WUS configuration).

[0062] In some implementations, a network may refrain from providing or configuring an RA search space or an RA search space set to a UE if the network does not transmit an RAR to the UE. Therefore, the UE may determine the applicable RNTI decoding and reception rules based on whether an RA search space is configured for the UE. In some implementations, the UE may expect an RAR or an UL-WUS response message to be transmitted when an RA search space is configured. In some implementations, the network may still configure an RA search space as SS#0 via explicit signaling. Under this condition, the UE may determine that the UE needs to monitor for an RAR or an UL-WUS response message first for receiving a downlink assignment configured by the network for subsequent OD-SIB1 reception, and the UE may also use CORESET#0 for PDCCH monitoring for RAR or UL-WUS response reception. In other words, when SS#0 is configured as the RA search space for RAR or UL-WUS response monitoring, the UE may refrain from using an SI-RNTI to perform initial decoding of SS#0.

[0063] The present disclosure describes mechanisms for performing PDCCH monitoring when a UE is not provided with an RA search space for RAR. In some implementations, when the UE is not provided with an RA search space for RAR, for example in an UL-WUS configuration received from Cell A, the UE may monitor or detect a PDCCH associated with RAR transmitted from an NES cell or an OD-SIB1 cell based on SS#0 or search space set zero. In some implementations, the UE may monitor or detect the PDCCH associated with RAR based on CORESET#0. In some implementations, when the UE is not provided with an RA search space for RAR in the UL-WUS configuration from Cell A, the UE may monitor or detect the PDCCH associated with RAR from the NES cell according to both SS#0 and CORESET#0.

[0064] In some implementations, when the UE is not provided with an RA search space for RAR, for example in the WUS configuration received from Cell A, the UE may skip RAR reception. In some implementations, the RAR reception may include at least one of the following operations: detecting a DCI having a Cyclic Redundancy Check (CRC) scrambled by an RA-RNTI or an RNTI used for scrambling a PDCCH associated with an RAR in response to the UL-WUS transmission, in a window; and receiving the RAR in the window based on the detected DCI with the CRC scrambled by the RA-RNTI or the RNTI used for scrambling the PDCCH associated with the RAR.

[0065] In some implementations, after the UE transmits an UL-WUS according to the WUS configuration to an NES cell or an OD-SIB1 cell, the UE may monitor or detect a PDCCH for RAR from the NES cell according to search space zero (or search space set zero) and CORESET zero when the UE is not provided with an RA search space for RAR in the WUS configuration received from Cell A. In some implementations, the UE may decode the PDCCH for an RAR, an UL-WUS response, or an OD-SIB1 response by first attempting decoding using an SI-RNTI or an RNTI used for scrambling a PDCCH associated with OD-SIB1, and may subsequently attempt decoding using an RA-RNTI or an RNTI used for scrambling a PDCCH associated with an RAR.

[0066] In some implementations, the UE may skip PDCCH monitoring for RAR, UL-WUS response, and / or OD-SIB1 after the UE transmits the UL WUS. In some implementations, after transmitting the UL-WUS, upon successful decoding of the PDCCH for RAR, UL-WUS response, and / or OD-SIB1 using the SI-RNTI or the RNTI used for scrambling the PDCCH associated with OD-SIB1, the UE may skip PDCCH monitoring for RAR and may skip RAR reception.

[0067] In some implementations, the UE may not monitor PDCCH for RAR and / or receive RAR after the UE transmits the UL WUS. In some implementations, after transmitting the UL WUS, upon successful decoding of the PDCCH using the SI-RNTI or the RNTI used for scrambling the PDCCH associated with OD-SIB1, the UE may not monitor the PDCCH for the RAR or receive the RAR. In some implementations, upon unsuccessful decoding of the PDCCH using the SI-RNTI or the RNTI used for scrambling the PDCCH associated with OD-SIB1, the UE may proceed to decode the PDCCH using the RA-RNTI or the RNTI used for scrambling the PDCCH associated with the RAR.

[0068] In some implementations, after the UE transmits a UL WUS (e.g., based on the WUS configuration) to the NES cell or OD-SIB1 cell, the UE may detect / monitor PDCCH for RAR (e.g., from the NES cell / OD-SIB1 cell) according to search space (set) zero and CORESET zero if the UE is not provided with an RA search space for RAR (e.g., in the WUS configuration from cell A). In some implementations, the UE may decode the PDCCH (for RAR) with an SI-RNTI (or an RNTI used for scrambling PDCCH for OD-SIB1) and an RA-RNTI (or an RNTI used for scrambling PDCCH for RAR). In some implementations, after transmitting the UL WUS, in response to successfully decoding the PDCCH for RAR with the SI-RNTI (or the RNTI used for scrambling PDCCH for OD-SIB1), the UE may skip PDCCH monitoring for RAR and / or the UE may skip RAR reception for the UL-WUS response message reception. In some implementations, after transmitting the UL WUS, the UE may not monitor PDCCH for RAR and / or receive RAR. In some implementations, after transmitting the UL WUS, in response to successfully decoding the PDCCH for RAR with the SI-RNTI (or the RNTI used for scrambling PDCCH for OD-SIB1), the UE may not monitor PDCCH monitoring for RAR and / or receive RAR within the same PDCCH.

[0069] In some implementations, in response to successfully decoding the PDCCH for RAR with the RA-RNTI (or the RNTI used for scrambling PDCCH for RAR), the UE may receive the RAR according to the PDCCH scheduling for the RAR with the RA-RNTI (or the RNTI used for scrambling PDCCH for RAR). In addition, the RAR message, which may be scrambled by the RA-RNTI, may include the DL assignment of the following Physical Downlink Shared Channel (PDSCH) for the OD-SIB1 reception. The UE may attempt decoding the DL assignment for OD-SIB1 reception accordingly. In some implementations, after transmitting a preamble (e.g., for the UL WUS), the UE may monitor PDCCH candidates in a PDCCH common search space set (e.g., Type0 or Type0A) on the primary cell of the MCG configured by the IE pdcch-ConfigSIB1 and / or IE searchSpaceZero in the WUS configuration.

[0070] In some implementations, after transmitting the UL WUS (e.g., based on the WUS configuration) to the NES cell or OD-SIB1 cell, the UE may detect / monitor PDCCH for RAR (e.g., from the NES cell) according to search space (set) zero and CORESET zero if the UE is not provided with an RA search space for RAR (e.g., in the WUS configuration from cell A). In some implementations, a UE may decode the PDCCH for RAR first with the SI-RNTI (or an RNTI used for scrambling PDCCH for OD-SIB1) and then decode the PDCCH for RAR with the RA-RNTI (or an RNTI used for scrambling PDCCH for RAR) if the UE supports a specific capability (e.g., a capability that allows skipping RAR reception).

[0071] In some implementations, after transmitting the UL WUS, in response to successfully decoding the PDCCH for RAR first with the SI-RNTI (or an RNTI used for scrambling PDCCH for OD-SIB1), the UE may skip PDCCH monitoring for RAR and / or skip RAR reception if the UE supports the specific capability. In some implementations, the UE may not monitor PDCCH for RAR and / or receive RAR after the UE transmits the UL WUS. In some implementations, after transmitting the UL WUS, in response to successfully decoding the PDCCH for RAR first with the SI-RNTI (or with an RNTI used for scrambling PDCCH for OD-SIB1), the UE may not monitor PDCCH for RAR and / or receive RAR if the UE supports the specific capability.

[0072] In some implementations, the UE may decode the PDCCH for RAR either with the SI-RNTI (or an RNTI used for scrambling PDCCH for OD-SIB1) first or with the RA-RNTI (or an RNTI used for scrambling PDCCH for RAR) first if the UE supports the specific capability (e.g., a capability that allows skipping RAR reception).

[0073] In some implementations, after transmitting the UL WUS (e.g., based on the WUS configuration) to the NES cell or OD-SIB1 cell, the UE may detect / monitor PDCCH for RAR (e.g., from the NES cell) according to search space (set) zero and CORESET zero if the UE is not provided with an RA search space for RAR (e.g., in WUS configuration from cell A). In some implementations, the UE may decode the PDCCH for RAR with the RA-RNTI (or an RNTI used for scrambling PDCCH for RAR) if the UE does not support the specific capability (e.g., a capability that allows skipping RAR reception). In some implementations, the UE may decode the PDCCH for RAR with the RA-RNTI (or an RNTI used for scrambling PDCCH for RAR) and may receive RAR according to the PDCCH if the UE does not support the specific capability.

[0074] In some implementations, if the UE is provided with the ra-SearchSpace in the WUS configuration, after transmitting the UL WUS, the UE may monitor PDCCH candidates in a PDCCH Common Search Space (CSS) set (e.g., Type1) configured by the ra-SearchSpace in the WUS configuration for a DCI (e.g., the DCI format 1_0) with CRC scrambled by the SI-RNTI or the RA-RNTI on the primary cell or the NES cell.

[0075] In some implementations, if the UE is provided with the ra-SearchSpace in the WUS configuration, after transmitting the UL WUS, the UE may monitor PDCCH candidates in a PDCCH CSS set (e.g., Type1) configured by the ra-SearchSpace in the WUS configuration for a DCI (e.g., the DCI format 1_0) with CRC scrambled by the SI-RNTI and with CRC scrambled by the RA-RNTI.

[0076] In some implementations, if the UE is provided with the ra-SearchSpace in the WUS configuration, after transmitting the UL WUS, the UE may monitor PDCCH candidates in a PDCCH CSS set (e.g., Type1) configured by the ra-SearchSpace in the WUS configuration for a DCI (e.g., the DCI format 1_0) with CRC scrambled by the SI-RNTI first and then by the RA-RNTI on the primary cell or the NES cell.

[0077] In some implementations, if the UE is provided with the ra-SearchSpace in the WUS configuration, after transmitting the UL WUS, the UE may attempt to monitor PDCCH candidates in a PDCCH CSS set (e.g., Type1) configured by the ra-SearchSpace in the WUS configuration for a DCI (e.g., the DCI format 1_0) with CRC scrambled by the SI-RNTI. The UE may subsequently attempt to monitor the PDCCH candidates in the PDCCH CSS set configured by the ra-SearchSpace in the WUS configuration for the DCI with CRC scrambled by the RA-RNTI on the primary cell or the NES cell.

[0078] In some implementations, if the UE detects the DCI format 1_0 with CRC scrambled by the corresponding SI-RNTI, and the Least Significant Bits (LSBs) of a System Frame Number (SFN) field in the DCI format 1_0, if included and applicable, match the corresponding LSBs of the SFN where the UE transmitted the Physical Random Access Channel (PRACH), the UE may receive a transport block in the corresponding PDSCH including at least the OD-SIB1.

[0079] In some implementations, if the UE detects the DCI format 1_0 with CRC scrambled by the corresponding SI-RNTI, and the LSBs of a SFN field in the DCI format 1_0, if included and applicable, match the corresponding LSBs of the SFN where the UE transmitted the PRACH, the UE may not receive a transport block in the corresponding PDSCH within the window, or the UE may stop receiving a transport block in the corresponding PDSCH within the window.

[0080] In some implementations, if the UE detects the DCI format 1_0 with CRC scrambled by the corresponding SI-RNTI, the UE may stop or skip the UL-WUS request procedure, including stopping or skipping the UL-WUS transmission. The UL-WUS request procedure may include at least one of the following actions: transmitting a preamble or UL-WUS to the NES cell; starting the ra-ResponseWindow, which may be configured in the rach-OccasionsSIB1, after transmitting the preamble or UL-WUS; detecting a DCI with CRC scrambled by the RA-RNTI or an RNTI used for scrambling a PDCCH for RAR in response to the UL-WUS transmission; and receiving a transport block in the corresponding PDSCH, which may include an RAR MAC Control Element (CE), within the RAR window according to the DCI with CRC scrambled by the RA-RNTI or the RNTI used for scrambling the PDCCH for RAR in response to the UL-WUS transmission.

[0081] In some implementations, if the UE detects the DCI format 1_0 with CRC scrambled by the corresponding RA-RNTI, and the LSBs of an SFN field in the DCI format 1_0, if included and applicable, match the corresponding LSBs of the SFN where the UE transmitted the PRACH, the UE may receive a transport block in a corresponding PDSCH within the window. The UE may send the transport block to higher layers (e.g., MAC entity or RRC entity). The higher layers may parse the transport block for a random access preamble identity (RAPID) associated with the PRACH transmission. If the higher layers identify the RAPID in RAR message(s) of the transport block, the higher layers may indicate an uplink grant to the physical layer. This may be referred to as an RAR UL grant in the physical layer. In some implementations, the UE may then detect the DCI (e.g., the DCI format 1_0) with CRC scrambled by the corresponding SI-RNTI (or an RNTI used for scrambling PDCCH for OD-SIB1), the UE may receive a transport block in a corresponding PDSCH, which may include at least the OD-SIB1, based on the DCI with CRC scrambled by the corresponding SI-RNTI (or the RNTI used for scrambling PDCCH for OD-SIB1).

[0082] In some implementations, the cell A may provide or transmit the ra-SearchSpace to the UE. In some implementations, the NES cell may transmit a DCI (e.g., the DCI format 1_0) with CRC scrambled by the corresponding RA-RNTI in the ra-SearchSpace in response to receiving the UL WUS. In some implementations, the NES cell may transmit the DCI (e.g., the DCI format 1_0) with CRC scrambled by the corresponding SI-RNTI in the ra-SearchSpace in response to receiving the UL WUS. In some implementations, the NES cell may transmit an RAR according to the DCI (e.g., the DCI format 1_0) with CRC scrambled by the corresponding SI-RNTI or RA-RNTI. In some implementations, the NES cell may transmit the OD-SIB1 based on the DCI (e.g., the DCI format 1_0) with CRC scrambled by the corresponding SI-RNTI. In some implementations, the NES cell may scramble a PDCCH with either the first RNTI (e.g., the SI-RNTI) or the second RNTI (e.g., the RA-RNTI). The NES cell may transmit the OD-SIB1 to the UE in response to scrambling the PDCCH with the first RNTI. The NES cell may transmit the RAR to the UE in response to scrambling the PDCCH with the second RNTI.

[0083] In some implementations, if the UE is provided with the ra-searchspace in the WUS configuration, after transmitting the UL WUS, the UE may monitor PDCCH candidates in a PDCCH CSS set (e.g., Type1) configured by the ra-SearchSpace in the WUS configuration for a DCI (e.g., the DCI format 1_0) with CRC scrambled by the SI-RNTI on the primary cell.

[0084] In some implementations, if the UE detects the DCI (e.g., the DCI format 1_0) with CRC scrambled by the corresponding SI-RNTI, and the LSBs of an SFN field in the DCI, if included and applicable, are the same as the corresponding LSBs of the SFN where the UE transmitted PRACH, the UE may receive a transport block in a corresponding PDSCH that includes at least the OD-SIB1. In some implementations, if the UE detects the DCI format 1_0 with CRC scrambled by the corresponding SI-RNTI, and the LSBs of the SFN field in the DCI format 1_0, if included and applicable, are the same as the corresponding LSBs of the SFN where the UE transmitted PRACH, the UE may not receive a transport block in a corresponding PDSCH within the window or the UE may stop receiving a transport block in a corresponding PDSCH within the window.

[0085] In some implementations, the cell A may provide or transmit the ra-SearchSpace to the UE. In some implementations, the NES cell may transmit a DCI (e.g., the DCI format 1_0) with CRC scrambled by the corresponding SI-RNTI in the ra-SearchSpace in response to receiving the UL WUS. In some implementations, the NES cell may transmit the OD-SIB1 according to the DCI (e.g., the DCI format 1_0) with CRC scrambled by the corresponding SI-RNTI. In some implementations, the NW may not transmit the DCI (e.g., the DCI format 1_0) with CRC scrambled by the corresponding RA-RNTI in the ra-SearchSpace in response to receiving the UL WUS. In some implementations, the NW may not transmit RAR according to the DCI (e.g., the DCI format 1_0) with CRC scrambled by the corresponding RA-RNTI in the ra-SearchSpace in response to receiving the UL WUS.

[0086] In some implementations, if the UE is not provided with the ra-searchspace in the WUS configuration, after transmitting the UL WUS, the UE may monitor PDCCH candidates in a PDCCH CSS set (e.g., Type0) configured by the searchSpaceZero in the WUS configuration or in the pdcch-ConfigSIB1 in Master Information Block (MIB) for a DCI (e.g., the DCI format 1_0) with CRC scrambled by the SI-RNTI or the RA-RNTI on the primary cell or the NES cell.

[0087] In some implementations, if the UE is not provided with the ra-SearchSpace in the WUS configuration, after transmitting the UL WUS,) the UE may monitor PDCCH candidates in a PDCCH CSS set (e.g., Type1) configured by the searchSpaceZero in the WUS configuration for a DCI (e.g., the DCI format 1_0) with CRC scrambled by the SI-RNTI and with CRC scrambled by the RA-RNTI.

[0088] In some implementations, if the UE is not provided with the ra-searchspace in the WUS configuration, after transmitting the UL WUS, the UE may monitor PDCCH candidates in a PDCCH CSS set (e.g., Type0) configured by the searchSpaceZero in the WUS configuration or in the pdcch-ConfigSIB1 in the MIB for a DCI (e.g., the DCI format 1_0) with CRC scrambled by the SI-RNTI first and then by the RA-RNTI on the primary cell.

[0089] In some implementations, if the UE is not provided with the ra-SearchSpace in the WUS configuration, after transmitting the UL WUS, the UE may attempt to monitor PDCCH candidates in a PDCCH CSS set (e.g., Type1) configured by the searchSpaceZero in the WUS configuration for a DCI (e.g., the DCI format 1_0) with CRC scrambled by the SI-RNTI, and then the UE may attempt to monitor the PDCCH candidates in the PDCCH CSS set (e.g., Type1) configured by the searchSpaceZero in the WUS configuration for the DCI (e.g., the DCI format 1_0) with CRC scrambled by the RA-RNTI on the primary cell or the NES cell.

[0090] In some implementations, if the UE detects the DCI (e.g., the DCI format 1_0) with CRC scrambled by the corresponding SI-RNTI, and the LSBs of an SFN field in the DCI, if included and applicable, are the same as the corresponding LSBs of the SFN where the UE transmitted PRACH, the UE may receive a transport block in a corresponding PDSCH that includes at least the OD-SIB1.

[0091] In some implementations, if the UE detects the DCI (e.g., the DCI format 1_0) with CRC scrambled by the corresponding SI-RNTI, and the LSBs of an SFN field in the DCI, if included and applicable, are the same as the corresponding LSBs of the SFN where the UE transmitted PRACH, the UE may not receive a transport block in a corresponding PDSCH within the window or the UE may stop receiving a transport block in a corresponding PDSCH within the window.

[0092] In some implementations, if the UE detects the DCI (e.g., the DCI format 1_0) with CRC scrambled by the corresponding RA-RNTI, and the LSBs of an SFN field in the DCI, if included and applicable, are the same as the corresponding LSBs of the SFN where the UE transmitted PRACH, the UE may receive a transport block in a corresponding PDSCH within the window. The UE may send the transport block to higher layers. The higher layers may parse the transport block for a RAPID associated with the PRACH transmission. If the higher layers identify the RAPID in the RAR message(s) of the transport block, the higher layers may indicate an uplink grant to the physical layer. This may be referred to as an RAR UL grant in the physical layer. In some implementations, the UE may then detect the DCI (e.g., the DCI format 1_0) with CRC scrambled by the corresponding SI-RNTI (or an RNTI used for scrambling PDCCH for OD-SIB1), the UE may receive a transport block in a corresponding PDSCH that includes at least the OD-SIB1 according to the DCI (e.g., the DCI format 1_0) with CRC scrambled by the corresponding SI-RNTI (or the RNTI used for scrambling PDCCH for OD-SIB1).

[0093] In some implementations, the cell A may not provide or transmit the ra-SearchSpace to the UE. In some implementations, the NES cell may transmit a DCI (e.g., the DCI format 1_0) with CRC scrambled by the corresponding RA-RNTI in the searchSpaceZero in response to receiving the UL WUS. In some implementations, the NES cell may transmit the DCI (e.g., the DCI format 1_0) with CRC scrambled by the corresponding SI-RNTI in the searchSpaceZero in response to receiving the UL WUS. In some implementations, the NES cell may transmit an RAR according to the DCI (e.g., the DCI format 1_0) with CRC scrambled by the corresponding SI-RNTI or RA-RNTI. In some implementations, the NES cell may transmit the OD-SIB1 according to the DCI (e.g., the DCI format 1_0) with CRC scrambled by the corresponding SI-RNTI. In some implementations, the NES cell may scramble a PDCCH with either the first RNTI (e.g., the SI-RNTI) or the second RNTI (e.g., the RA-RNTI). The NES cell may transmit the OD-SIB1 to the UE in response to scrambling the PDCCH with the first RNTI. The NES cell may transmit the RAR to the UE in response to scrambling the PDCCH with the second RNTI.

[0094] In some implementations, if the UE is not provided with the ra-searchspace in the WUS configuration, after transmitting UL WUS, the UE may monitor PDCCH candidates in a PDCCH CSS set (e.g., Type0) configured by the searchSpaceZero in the WUS configuration or in the pdcch-ConfigSIB1 in MIB for a DCI (e.g., the DCI format 1_0) with CRC scrambled by the SI-RNTI on the primary cell (e.g., the primary cell of the MCG).

[0095] In some implementations, if the UE detects the DCI (e.g., the format 1_0) with CRC scrambled by the corresponding SI-RNTI, and the LSBs of an SFN field in the DCI, if included and applicable, are the same as the corresponding LSBs of the SFN where the UE transmitted PRACH, the UE may receive a transport block in a corresponding PDSCH that includes at least the OD-SIB1. In some implementations, if the UE detects the DCI (e.g., the format 1_0) with CRC scrambled by the corresponding SI-RNTI, and the LSBs of an SFN field in the DCI, if included and applicable, are the same as the corresponding LSBs of the SFN where the UE transmitted PRACH, the UE may not receive a transport block in a corresponding PDSCH within the window or the UE may stop receiving a transport block in a corresponding PDSCH within the window.

[0096] In some implementations, the cell A may not provide or transmit the ra-SearchSpace to the UE. In some implementations, the NES cell may transmit a DCI (e.g., the DCI format 1_0) with CRC scrambled by the corresponding SI-RNTI in the searchSpaceZero in response to receiving the UL WUS. In some implementations, the NES cell may transmit the OD-SIB1 according to the DCI (e.g., the DCI format 1_0) with CRC scrambled by the corresponding SI-RNTI. In some implementations, the NW may not transmit a DCI (e.g., the DCI format 1_0) with CRC scrambled by the corresponding RA-RNTI in the searchSpaceZero in response to receiving the UL WUS. In some implementations, the NW may not transmit RAR according to the DCI (e.g., the DCI format 1_0) with CRC scrambled by the corresponding RA-RNTI in the searchSpaceZero in response to receiving the UL WUS.

[0097] In some implementations, the UE may be provided with more than one RNTIs (e.g., SI-RNTI, RA-RNTI, RNTI used for scrambling PDCCH for RAR, and / or RNTI used for scrambling PDCCH for OD-SIB1) for CORESET zero and search space (set) zero via the WUS configurations (e.g., from cell A). In some implementations, a set of PDCCH candidates for the UE to monitor may be defined in terms of PDCCH search space sets. A search space set may be a common search space (CSS) set or a UE-specific search space (USS) set.

[0098] In some implementations, the UE may monitor PDCCH candidates for a DCI format with CRC scrambled by one or more RNTIs (e.g., SI-RNTI, RA-RNTI, RNTI used for scrambling PDCCH for RAR, and / or RNTI used for scrambling PDCCH for OD-SIB1) on the primary cell in one or more of the following search spaces sets: a PDCCH CSS set configured by the ra-SearchSpace in the WUS configuration, a PDCCH CSS set configured by the searchSpaceZero in the WUS configuration, a PDCCH CSS set (e.g., Type0) on the primary cell (e.g., the primary cell of the MCG) configured by the pdcch-ConfigSIB1 in the MIB or the WUS configuration. The WUS configuration may be configured by cell A or by the OD-SIB1 cell itself before the OD-SIB1 cell switches from operating as cell A to operating as the OD-SIB1 cell.

[0099] In some implementations, after transmitting a UL WUS (e.g., a PRACH transmission, a preamble transmission, a UL WUS transmission to request the OD-SIB1), the UE may attempt to detect a DCI format 1_0 with CRC scrambled by a corresponding RA-RNTI (or an RNTI used for scrambling PDCCH for RAR in response to the UL WUS transmission) during a window. In some implementations, the detection may be applied when the PRACH transmission is not triggered by a PDCCH order that includes a Cell Indicator field with a non-zero value.

[0100] In some implementations, after transmitting a UL WUS (e.g., a PRACH transmission, a preamble transmission, a UL WUS transmission to request the OD-SIB1), the UE may attempt to detect a DCI format 1_0 with CRC scrambled by a corresponding SI-RNTI (or an RNTI used for scrambling PDCCH for OD-SIB1) during a window. In some implementations, the detection may be applied when the PRACH transmission is not triggered by a PDCCH order that includes a Cell Indicator field with a non-zero value.

[0101] In some implementations, the RA-RNTI associated with the PRACH occasion in which the Random Access Preamble is transmitted may be computed as: RA-RNTI = 1 + s_id + 14 × t_id + 14 × 80 × f_id + 14 × 80 × 8 × ul_carrier_id, where s_id is the index of the first OFDM symbol of the PRACH occasion (0≦ s_id < 14), t_id is the index of the first slot of the PRACH occasion in a system frame (0 ≦ t_id < 80), where the subcarrier spacing to determine t_id is based on the value of μ specified in clause 5.3.2 in the 3GPP TS 38.211 for μ = {0, 1, 2, 3}, and for μ = {5, 6}, t_id is the index of the 120 kHz slot in a system frame that contains the PRACH occasion (0 ≦ t_id < 80), f_id is the index of the PRACH occasion in the frequency domain (0 ≦ f_id < 8), and ul_carrier_id is the UL carrier used for Random Access Preamble transmission (e.g., 0 for NUL carrier, and 1 for SUL carrier).

[0102] In some implementations, the SI-RNTI may be set to a hexadecimal value of 0xFFFF.

[0103] In the present disclosure, multiple implementations are described to support RAR reception and on-demand SIB1 reception based on different RNTIs. Through the techniques described herein, on-demand SIB1 reception for network energy saving may be achieved.

[0104] In some implementations, a method performed by a UE may include: 　　　　transmitting a UL WUS to an NES cell; 　　　　monitoring a PDCCH for an RAR according to search space (set) zero and CORESET zero in a case that the UE is not provided with an RA search space for the RAR in a WUS configuration from cell A; 　　　　decoding the PDCCH for the RAR with an SI-RNTI or an RNTI used to scramble PDCCH for OD-SIB1; 　　　　receiving the OD-SIB1 according to the PDCCH for the RAR scrambled by an SI-RNTI or the RNTI used to scramble PDCCH for OD-SIB1 in a case that the UE successfully decodes the PDCCH for RAR with the SI-RNTI; 　　　　decoding the PDCCH for the RAR with an RA-RNTI or an RNTI used to scramble PDCCH for RAR; and 　　　　receiving the RAR according to the PDCCH for RAR scrambled by the RA-RNTI or the RNTI used to scramble PDCCH for RAR in a case that the UE unsuccessfully decodes the PDCCH for the RAR with the SI-RNTI.

[0105] In some implementations, a method performed by a UE may include: 　　　　transmitting a UL WUS to an NES cell; 　　　　monitoring a PDCCH for an RAR according to search space (set) zero and CORESET zero in a case that the UE is not provided with an RA search space for the RAR in a WUS configuration from cell A; 　　　　decoding the PDCCH for the RAR with an SI-RNTI or an RNTI used to scramble PDCCH for OD-SIB1; 　　　　in a case that the UE successfully decodes the PDCCH for the RAR with the SI-RNTI, receiving the OD-SIB1 according to the PDCCH for the RAR scrambled by the SI-RNTI or the RNTI used to scramble PDCCH for OD-SIB1; and 　　　　in a case that the UE unsuccessfully decodes the PDCCH for the RAR with the SI-RNTI, decoding the PDCCH for the RAR with an RA-RNTI or an RNTI used to scramble PDCCH for RAR and receiving the RAR according to the PDCCH for RAR scrambled by the RA-RNTI or the RNTI used to scramble PDCCH for RAR.

[0106] FIG. 1 is a flowchart illustrating a method / process 100 performed by a UE for performing a SIB1 request operation, according to an example implementation of the present disclosure. In the action 102, the process 100 may start by receiving, from a first cell (e.g., the cell A), a WUS configuration. In the action 104, the process 100 may transmit, to an NES cell, a UL WUS based on the WUS configuration to request an OD-SIB1. In the action 106, the process 100 may monitor a PDCCH in the NES cell. In the action 108, the process 100 may attempt to decode the PDCCH with a first RNTI. In the action 110, in response to determining that the PDCCH has been successfully decoded with the first RNTI, the process 100 may receive the OD-SIB1 based on the PDCCH scrambled by the first RNTI. In the action 112, in response to determining that the PDCCH has been unsuccessfully decoded with the first RNTI, the process 100 may attempt to decode the PDCCH with a second RNTI. In the action 114, in response to determining that the PDCCH has been successfully decoded with the second RNTI, the process 100 may receive an RAR based on the PDCCH scrambled by the second RNTI. The second RNTI may be different from the first RNTI. The process 100 may then end.

[0107] The steps / actions shown in FIG. 1 should not be construed as necessarily order dependent. The order in which the process is described is not intended to be construed as a limitation. Moreover, some of the actions shown in FIG. 1 may be omitted in some implementations and one or more actions shown in FIG. 1 may be combined.

[0108] The technical problem addressed by the method illustrated in FIG. 1 is how to achieve efficient control channel monitoring and reduce signaling overhead in on-demand SIB1 request procedures, particularly in scenarios where a UE transmits a UL WUS to request OD-SIB1. The advantageous technical effect achieved by the disclosed method is that the UE prioritizes PDCCH decoding using a first RNTI associated with OD-SIB1 scheduling, such as an SI-RNTI or an RNTI used for scrambling a PDCCH for OD-SIB1, before attempting decoding with a second RNTI associated with RAR reception. When the PDCCH is successfully decoded with the first RNTI, the UE directly receives the OD-SIB1 and refrains from decoding PDCCH candidates using the second RNTI or from receiving an RAR. This selective decoding behavior reduces the number of PDCCH decoding attempts, avoids unnecessary RAR reception, and lowers UE processing and power consumption, thereby improving the efficiency of on-demand SIB1 delivery and supporting network energy saving operations.

[0109] In some implementations, the WUS configuration may not include an RA search space. In some implementations, if the UE is not provided with an RA search space in the WUS configuration, in the action 106, the UE may monitor the PDCCH in the NES cell based on a search space zero (SS #0) and CORESET #0.

[0110] In some implementations, the WUS configuration may include an RA search space. In some implementations, if the UE is provided with the RA search space in the WUS configuration, in the action 106, the UE may monitor the PDCCH in the NES cell based on the RA search space provided in the WUS configuration.

[0111] In some implementations, the first RNTI may include an SI-RNTI. In some implementations, the first RNTI may correspond to an RNTI used for scrambling a PDCCH for the OD-SIB1.

[0112] In some implementations, the second RNTI may include an RA-RNTI. In some implementations, the second RNTI may correspond to an RNTI used for scrambling a PDCCH for an RAR.

[0113] FIG. 2 is a flowchart illustrating a method / process 200 performed by a BS for supporting a SIB1 request operation, according to an example implementation of the present disclosure. In some implementations, the process 200 may be performed by an NES cell. In the action 202, the process 200 may start by receiving, from a UE via an NES cell, an UL WUS requesting an OD-SIB1, where the UL WUS may be based on a WUS configuration provided by a first cell (e.g., the cell A). In the action 204, the process 200 may scramble a PDCCH with either a first RNTI or a second RNTI, where the second RNTI may be different from the first RNTI. In the action 206, the process 200 may transmit the OD-SIB1 to the UE in response to scrambling the PDCCH with the first RNTI. In the action 208, the process 20 may transmit an RAR to the UE in response to scrambling the PDCCH with the second RNTI. The process 200 may then end. The method illustrated in FIG. 2 is similar to that in FIG. 1, except that it is described from the perspective of the BS (instead of the UE).

[0114] In some implementations, the UE may monitor the PDCCH in the NES cell based on a SS #0 and a CORESET #0 in a case that the UE is not provided with an RA search space in the WUS configuration. In some implementations, the UE may monitor the PDCCH in the NES cell based on an RA search space provided in the WUS configuration. In some implementations, the first RNTI may include an SI-RNTI. In some implementations, the second RNTI may include an RA-RNTI.

[0115] FIG. 3 is a block diagram illustrating a node 300 for wireless communication, according to an example implementation of the present disclosure. As illustrated in FIG. 3, a node 300 may include a transceiver 320, a processor 328, a memory 334, one or more presentation components 338, and at least one antenna 336. The node 300 may also include a radio frequency (RF) spectrum band module, a BS communications module, a network communications module, and a system communications management module, Input / Output (I / O) ports, I / O components, and a power supply (not illustrated in FIG. 3).

[0116] Each of the components may directly or indirectly communicate with each other over one or more buses 340. The node 300 may be a UE or a BS that performs various functions disclosed with reference to FIGS. 1 and 2.

[0117] The transceiver 320 has a transmitter 322 (e.g., transmitting / transmission circuitry) and a receiver 324 (e.g., receiving / reception circuitry) and may be configured to transmit and / or receive time and / or frequency resource partitioning information. The transceiver 320 may be configured to transmit in different types of subframes and slots including, but not limited to, usable, non-usable, and flexibly usable subframes and slot formats. The transceiver 320 may be configured to receive data and control channels.

[0118] The node 300 may include a variety of computer-readable media. Computer-readable media may be any available media that may be accessed by the node 300 and include volatile (and / or non-volatile) media and removable (and / or non-removable) media.

[0119] The computer-readable media may include computer-storage media and communication media. Computer-storage media may include both volatile (and / or non-volatile media), and removable (and / or non-removable) media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules, AI / ML module(s), or data.

[0120] Computer-storage media may include RAM, ROM, EPROM, EEPROM, flash memory (or other memory technology), CD-ROM, Digital Versatile Disks (DVD) (or other optical disk storage), magnetic cassettes, magnetic tape, magnetic disk storage (or other magnetic storage devices), etc. Computer-storage media may not include a propagated data signal. Communication media may typically embody computer-readable instructions (e.g., computer-readable instructions related to AI module(s) and / or the ML module(s)), data structures, program modules, or other data in a modulated data signal, such as a carrier wave, or other transport mechanisms and include any information delivery media.

[0121] The term “modulated data signal” may mean a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. Communication media may include wired media, such as a wired network or direct-wired connection, and wireless media, such as acoustic, RF, infrared, and other wireless media. Combinations of any of the above listed components should also be included within the scope of computer-readable media.

[0122] The memory 334 may include computer-storage media in the form of volatile and / or non-volatile memory. The memory 334 may be removable, non-removable, or a combination thereof. Example memory may include solid-state memory, hard drives, optical-disc drives, etc. As illustrated in FIG. 3, the memory 334 may store a computer-readable and / or computer-executable instructions 332 (e.g., software codes) that are configured to, when executed, cause the processor 328 to perform various functions disclosed herein, for example, with reference to FIGS. 1 and 2. Alternatively, the instructions 332 may not be directly executable by the processor 328 but may be configured to cause the node 300 (e.g., when compiled and executed) to perform various functions disclosed herein.

[0123] The processor 328 (e.g., having processing circuitry) may include an intelligent hardware device, e.g., a Central Processing Unit (CPU), a microcontroller, an ASIC, etc. The processor 328 may include memory. The processor 328 may process the data 330 and the instructions 332 received from the memory 334, and information transmitted and received via the transceiver 320, the baseband communications module, and / or the network communications module. The processor 328 may also process information to send to the transceiver 320 for transmission via the antenna 336 to the network communications module for transmission to a CN.

[0124] One or more presentation components 338 may present data indications to a person or another device. Examples of presentation components 338 may include a display device, a speaker, a printing component, a vibrating component, etc.

[0125] In view of the present disclosure, it is obvious that various techniques may be used for implementing the disclosed concepts without departing from the scope of those concepts. Moreover, while the concepts have been disclosed with specific reference to certain implementations, a person of ordinary skill in the art may recognize that changes may be made in form and detail without departing from the scope of those concepts. As such, the disclosed implementations are to be considered in all respects as illustrative and not restrictive. It should also be understood that the present disclosure is not limited to the particular implementations disclosed and many rearrangements, modifications, and substitutions are possible without departing from the scope of the present disclosure.

Claims

1. A User Equipment (UE) for performing a System Information Block Type 1 (SIB1) request operation, the UE comprising: 　　　　at least one processor; and 　　　　at least one non-transitory computer-readable medium coupled to the at least one processor and storing one or more computer-executable instructions that, when executed by the at least one processor, cause the UE to: 　　　　　　　　receive, from a first cell, a Wake-Up Signal (WUS) configuration; 　　　　　　　　transmit, to a Network Energy Saving (NES) cell, an Uplink (UL) WUS based on the WUS configuration to request an On-Demand (OD)-SIB1; 　　　　　　　　monitor a Physical Downlink Control Channel (PDCCH) in the NES cell; 　　　　　　　　attempt to decode the PDCCH with a first Radio Network Temporary Identifier (RNTI); 　　　　　　　　in response to determining that the PDCCH has been successfully decoded with the first RNTI, receive the OD-SIB1 based on the PDCCH scrambled by the first RNTI; 　　　　　　　　in response to determining that the PDCCH has been unsuccessfully decoded with the first RNTI, attempt to decode the PDCCH with a second RNTI; and 　　　　　　　　in response to determining that the PDCCH has been successfully decoded with the second RNTI, receive a Random Access Response (RAR) based on the PDCCH scrambled by the second RNTI.

2. The UE of claim 1, wherein monitoring the PDCCH in the NES cell comprises: 　　　　monitoring the PDCCH in the NES cell based on a search space zero and a Control Resource Set (CORESET) zero in a case that the UE is not provided with a Random Access (RA) search space in the WUS configuration.

3. The UE of claim 1, wherein monitoring the PDCCH in the NES cell comprises: 　　　　monitoring the PDCCH in the NES cell based on a Random Access (RA) search space provided in the WUS configuration.

4. The UE of claim 1, wherein the first RNTI comprises a System Information (SI)-RNTI.

5. The UE of claim 1, wherein the second RNTI comprises a Random Access (RA)-RNTI.

6. A Base Station (BS) configured to support a System Information Block Type 1 (SIB1) request operation, the BS comprising: 　　　　at least one processor; and 　　　　at least one non-transitory computer-readable medium coupled to the at least one processor and storing one or more computer-executable instructions that, when executed by the at least one processor, cause the BS to: 　　　　　　　　receive, from a User Equipment (UE) via a Network Energy Saving (NES) cell, an Uplink (UL) Wake-Up Signal (WUS) requesting an On-Demand (OD)-SIB1, the UL WUS being based on a WUS configuration provided by a first cell; 　　　　　　　　scramble a Physical Downlink Control Channel (PDCCH) with either a first Radio Network Temporary Identifier (RNTI) or a second RNTI; 　　　　　　　　transmit the OD-SIB1 to the UE in response to scrambling the PDCCH with the first RNTI; and 　　　　　　　　transmit a Random Access Response (RAR) to the UE in response to scrambling the PDCCH with the second RNTI.

7. The BS of claim 6, wherein the UE monitors the PDCCH in the NES cell based on a search space zero and a Control Resource Set (CORESET) zero in a case that the UE is not provided with a Random Access (RA) search space in the WUS configuration.

8. The BS of claim 6, wherein the UE monitors the PDCCH in the NES cell based on a Random Access (RA) search space provided in the WUS configuration.

9. The BS of claim 6, wherein the first RNTI comprises a System Information (SI)-RNTI.

10. The BS of claim 6, wherein the second RNTI comprises a Random Access (RA)-RNTI.

11. A method performed by a User Equipment (UE) for performing a System Information Block Type 1 (SIB1) request operation, the method comprising: 　　　　receiving, from a first cell, a Wake-Up Signal (WUS) configuration; 　　　　transmitting, to a Network Energy Saving (NES) cell, an Uplink (UL) WUS based on the WUS configuration to request an On-Demand (OD)-SIB1; 　　　　monitoring a Physical Downlink Control Channel (PDCCH) in the NES cell; 　　　　attempting to decode the PDCCH with a first Radio Network Temporary Identifier (RNTI); 　　　　in response to determining that the PDCCH has been successfully decoded with the first RNTI, receiving the OD-SIB1 based on the PDCCH scrambled by the first RNTI; 　　　　in response to determining that the PDCCH has been unsuccessfully decoded with the first RNTI, attempting to decode the PDCCH with a second RNTI; and 　　　　in response to determining that the PDCCH has been successfully decoded with the second RNTI, receiving a Random Access Response (RAR) based on the PDCCH scrambled by the second RNTI.

Images