Patent Description:
The following abbreviations are herewith defined, at least some of which are referred to within the following description.

The following abbreviations are herewith defined, at least some of which are referred to within the following description: Third Generation Partnership Project ("3GPP"), Fifth-Generation Core ("5GC"), Access and Mobility Management Function ("AMF"), Access Point Name ("APN"), Access Stratum ("AS"), Bandwidth Adaptation ("BA"), Bandwidth Part ("BWP"), Binary Phase Shift Keying ("BPSK"), Block Error Rate ("BLER"), Carrier Aggregation ("CA"), Cell-Specific Radio Network Temporary Identifier ("C-RNTI"), Clear Channel Assessment ("CCA"), Cyclic Prefix ("CP"), Common Search Space ("C-SS"), Control Element ("CE"), Cyclical Redundancy Check ("CRC"), Channel State Information ("CSI"), Common Search Space ("C-SS"), Data Radio Bearer ("DRB," e.g., carrying user plane data), Demodulation Reference Signal ("DM-RS"), Discontinuous Reception ("DRX"), Discrete Fourier Transform Spread ("DFTS"), Downlink Control Information ("DCI"), Downlink ("DL"), Downlink Pilot Time Slot ("DwPTS"), Enhanced Clear Channel Assessment ("eCCA"), Evolved Node B ("eNB"), Evolved Packet Core ("EPC"), Evolved UMTS Terrestrial Radio Access Network ("E-UTRAN"), Guard Period ("GP"), General Packet Radio Service ("GPRS"), Global System for Mobile Communications ("GSM"), Hybrid Automatic Repeat Request ("HARQ"), Internet-of-Things ("IoT"), Listen-Before-Talk ("LBT"), Logical Channel ("LCH"), Long Term Evolution ("LTE"), Master Information Block ("MIB"), Medium Access Control ("MAC"), Master Cell Group ("MCG"), Modulation Coding Scheme ("MCS"), Machine Type Communication ("MTC"), Mobility management Entity ("MME"), Multiple Input Multiple Output ("MIMO"), Multi User Shared Access ("MUSA"), Narrowband ("NB"), Next Generation (e.g., <NUM>) Node-B ("gNB"), Next Generation Radio Access Network ("NG-RAN"), New Radio ("NR", e.g., <NUM> radio access), New Data Indicator ("NDI"), Non-Orthogonal Multiple Access ("NOMA"), Orthogonal Frequency Division Multiplexing ("OFDM"), Packet Data Convergence Protocol ("PDCP"), Primary Cell ("PCell"), Physical Broadcast Channel ("PBCH"), Packet Data Network ("PDN"), Protocol Data Unit ("PDU"), Physical Downlink Control Channel ("PDCCH"), Physical Downlink Shared Channel ("PDSCH"), Physical Hybrid ARQ Indicator Channel ("PHICH"), Physical Random Access Channel ("PRACH"), Physical Resource Block ("PRB"), Physical Uplink Control Channel ("PUCCH"), Physical Uplink Shared Channel ("PUSCH"), Quality of Service ("QoS"), Quadrature Phase Shift Keying ("QPSK"), Radio Link Control ("RLC"), Radio Resource Control ("RRC"), Random-Access Procedure ("RACH"), Radio Network Temporary Identifier ("RNTI"), Reference Signal ("RS"), Reference Signal Received Power ("RSRP"), Remaining Minimum System Information ("RMSI"), Resource Block Assignment ("RBA"), Round Trip Time ("RTT"), Receive ("RX"), Signaling Radio Bearer ("SRB," e.g., carrying control plane data), Single Carrier Frequency Division Multiple Access ("SC-FDMA"), Secondary Cell ("SCell"), Secondary Cell Group ("SCG"), Shared Channel ("SCH"), Signal-to-Interference-Plus-Noise Ratio ("SINR"), Service Data Unit ("SDU"), Sequence Number ("SN"), Session Management Function ("SMF"), System Information ("SI"), System Information Block ("SIB"), Synchronization Signal ("SS"), Transport Block ("TB"), Transport Block Size ("TBS"), Time-Division Duplex ("TDD"), Time Division Multiplex ("TDM"), Time Division Orthogonal Cover Code ("TD-OCC"), Transmission Time Interval ("TTI"), Transmit ("TX"), Uplink Control Information ("UCI"), User Entity/Equipment (Mobile Terminal) ("the UE"), Uplink ("UL"), User Plane ("UP"), Universal Mobile Telecommunications System ("UMTS"), Uplink Pilot Time Slot ("UpPTS"), Wireless Local Area Network ("WLAN"), and Worldwide Interoperability for Microwave Access ("WiMAX"). As used herein, "HARQ-ACK" may represent collectively the Positive Acknowledge ("ACK") and the Negative Acknowledge ("NACK"). ACK means that a TB is correctly received while NACK (or NAK) means a TB is erroneously received.

In mobile communication networks, a bandwidth part ("BWP") consisting of a group of contiguous physical resource blocks ("PRBs") is used in 3GPP New Radio ("NR") to support at least: reduced user equipment ("UE") bandwidth ("BW") capability, UE BW adaptation, frequency division multiplexing ("FDM") of multiple numerologies (e.g., subcarrier spacings), and use of non-contiguous spectrum. A connected mode UE may be configured, e.g., UE-specifically and semi-statically, with a single or multiple active BWP(s) for a single carrier. The bandwidth of a BWP is smaller than or equal to the maximum UE bandwidth capability. However, the bandwidth of a BWP is at least as large as a bandwidth of a SS/PBCH block (e.g., a synchronization signal / physical broadcast channel block), wherein the SS/PBCH block comprises primary and secondary synchronization signals and PBCH.

3GPP standard specification <NUM> V15. <NUM> provides an overview and overall description of the NG-RAN and focuses on the radio interface protocol architecture of NR connected to 5GC.

<NPL>, and discusses the bandwidth part for a UE not capable of supporting the carrier bandwidth and resource allocation for the mixed numerologies.

Claim <NUM> defines a method of a user equipment and claim <NUM> defines a user equipment. The embodiment depicted in <FIG> and <FIG> falls under the scope of the claims. All the other embodiments do not fall under the scope of the claims. They are however retained as useful examples to better understand the invention.

Methods for SI delivery in a wideband carrier are disclosed. Apparatuses and systems also perform the functions of the methods. The methods may also be embodied in one or more computer program products comprising executable code.

In one embodiment falling under the scope of the claims, a first method for SI delivery in a wideband carrier includes acquiring a system information block for a first cell in an initial active DL BWP and establishing a RRC connection with the first cell based on the acquired SIB. The first method includes transmitting an indication of one or more SIBs necessary for UE operation to a network entity and switching to a first DL BWP. Here, the first DL BWP is different from the initial active DL BWP. Also, the indication of the one or more SIBs necessary for remote unit operation may be transmitted via higher layer signaling.

In another embodiment not falling under the scope of the claims, , a second method for SI delivery in a wideband carrier includes receiving one or more paging occasion configurations in a SIB and determining a paging frame and a paging occasion identity within the paging frame based on at least one of a UE identity and a discontinuous reception ("DRX") cycle length. The second method includes selecting a paging occasion configuration from the received one or more paging occasion configurations. Here, the selected paging occasion configuration is associated with the determined paging occasion identity. The second method also includes determining a paging slot and a paging symbol within the determined paging slot based on the selected paging occasion configuration. The second method also includes decoding a PDCCH carrying paging DCI on the determined paging symbol within the determined paging slot of the determined paging frame.

This code may be provided to a processor of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the schematic flowchart diagrams and/or schematic block diagrams.

The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other devices to produce a computer implemented process such that the code which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the schematic flowchart diagrams and/or schematic block diagram.

As noted above, <NUM> NR supports BWP, namely a group of contiguous PRBs whose collective bandwidth is smaller than or equal to the maximum UE bandwidth capability, but at least as large as a bandwidth of a SS/PBCH block. Different UEs' BWPs may fully or partially overlap, and it is up to a network entity, e.g., a gNodeB ("gNB") or other suitable RAN node, to coordinate scheduling of different UEs' BWPs. Configuration parameters of a BWP may include numerology (e.g., subcarrier spacing), a frequency location (e.g., center frequency), and a bandwidth (e.g., number of PRBs). A given BWP may or may not contain a SS/PBCH block.

Multiple SS/PBCH blocks can be transmitted within a bandwidth of a carrier. However, from UE perspective, a cell is associated with a single SS/PBCH block in frequency domain. Further, a cell-defining SS/PBCH block has an associated essential system information block(s), for example, System Information Block Type1 ("SIB1") and/or System Information Block Type2 ("SIB2") which includes, so called, `remaining minimum system information ("RMSI")', system information not included in a master information block ("MIB") but essential to accessing to a cell. Multiple cell-defining SS/PBCH blocks associated with a common NE and transmitted in the bandwidth of the carrier may or may not have common system information.

System information ("SI") messages, each of which includes at least one system information block, may be transmitted within periodically occurring time domain windows (referred to as SI-windows) using dynamic scheduling. Each SI message is associated with a SI-window and the SI-windows of different SI messages may or may not overlap. A SI-window length may be configurable and may or may not be common for all SI messages. Within a given SI-window, a corresponding SI message can be transmitted a number of times. UE can acquire detailed time and frequency domain scheduling and other information from decoding physical downlink control channel ("PDCCH") addressed by a system information-radio network temporary identifier ("SI-RNTI"). For a secondary cell ("SCell"), a network entity provides UE with the required SI by dedicated signaling. Upon change of relevant SI, the network entity releases and adds back the concerned SCell with the updated SI for the UE. However, signaling of updated SI via cell release and addition procedures may not be suitable for a primary cell ("PCell") or primary secondary cell ("PSCell").

Disclosed herein are methods, apparatuses, systems, and computer-program products to perform (re)-acquiring system information ("SI") within a wideband carrier, wherein the wideband carrier refers to a carrier which includes one or more cell-defining SS/PBCH blocks associated with a common network entity (e.g., a base station).

<FIG> depicts a wireless communication system <NUM> for receiving system information at a UE, according to embodiments of the disclosure. In one embodiment, the wireless communication system <NUM> includes at least one remote unit <NUM>, a radio access network ("RAN") <NUM>, and a mobile core network <NUM>. The RAN <NUM> and the mobile core network <NUM> form a mobile communication network. The RAN <NUM> may be composed of a base unit <NUM> with which the remote unit <NUM> communicates using wireless communication links <NUM>. Even though a specific number of remote units <NUM>, base units <NUM>, wireless communication links <NUM>, RANs <NUM>, and mobile core networks <NUM> are depicted in <FIG>, one of skill in the art will recognize that any number of remote units <NUM>, base units <NUM>, wireless communication links <NUM>, RANs <NUM>, and mobile core networks <NUM> may be included in the wireless communication system <NUM>.

In one implementation, the wireless communication system <NUM> is compliant with the <NUM> system specified in the 3GPP specifications. More generally, however, the wireless communication system <NUM> may implement some other open or proprietary communication network, for example, LTE or WiMAX, among other networks.

In one embodiment, the remote units <NUM> may include computing devices, such as desktop computers, laptop computers, personal digital assistants ("PDAs"), tablet computers, smart phones, smart televisions (e.g., televisions connected to the Internet), smart appliances (e.g., appliances connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), vehicle on-board computers, network devices (e.g., routers, switches, modems), or the like. Moreover, the remote units <NUM> may be referred to as the UEs, subscriber units, mobiles, mobile stations, users, terminals, mobile terminals, fixed terminals, subscriber stations, user terminals, wireless transmit/receive unit ("WTRU"), a device, or by other terminology used in the art.

The remote units <NUM> may communicate directly with one or more of the base units <NUM> in the RAN <NUM> via uplink ("UL") and downlink ("DL") communication signals. Furthermore, the UL and DL communication signals may be carried over the wireless communication links <NUM>. Here, the RAN <NUM> is an intermediate network that provides the remote units <NUM> with access to the mobile core network <NUM>.

In some embodiments, the remote units <NUM> communicate with an application server <NUM> via a network connection with the mobile core network <NUM>. For example, an application <NUM> (e.g., web browser, media client, telephone/VoIP application) in a remote unit <NUM> may trigger the remote unit <NUM> to establish a PDU session (or other data connection) with the mobile core network <NUM> via the RAN <NUM>. The mobile core network <NUM> then relays traffic between the remote unit <NUM> and the application server <NUM> in the packet data network <NUM> using the PDU session. Note that the remote unit <NUM> may establish one or more PDU sessions (or other data connections) with the mobile core network <NUM>. As such, the remote unit <NUM> may concurrently have at least one PDU session for communicating with the packet data network <NUM> and at least one PDU session for communicating with another data network (not shown).

The base units <NUM> may be distributed over a geographic region. In certain embodiments, a base unit <NUM> may also be referred to as an access terminal, an access point, a base, a base station, a Node-B, an eNB, a gNB, a Home Node-B, a relay node, or by any other terminology used in the art. The base units <NUM> are generally part of a radio access network ("RAN"), such as the RAN <NUM>, that may include one or more controllers communicably coupled to one or more corresponding base units <NUM>. These and other elements of radio access network are not illustrated but are well known generally by those having ordinary skill in the art. The base units <NUM> connect to the mobile core network <NUM> via the RAN <NUM>.

The base units <NUM> may serve a number of remote units <NUM> within a serving area, for example, a cell or a cell sector, via a wireless communication link <NUM>. The base units <NUM> may communicate directly with one or more of the remote units <NUM> via communication signals. Generally, the base units <NUM> transmit DL communication signals to serve the remote units <NUM> in the time, frequency, and/or spatial domain. Furthermore, the DL communication signals may be carried over the wireless communication links <NUM>. The wireless communication links <NUM> may be any suitable carrier in licensed or unlicensed radio spectrum. The wireless communication links <NUM> facilitate communication between one or more of the remote units <NUM> and/or one or more of the base units <NUM>.

In one embodiment, the mobile core network <NUM> is a <NUM> core ("5GC") or the evolved packet core ("EPC"), which may be coupled to a packet data network <NUM>, like the Internet and private data networks, among other data networks. A remote unit <NUM> may have a subscription or other account with the mobile core network <NUM>. Each mobile core network <NUM> belongs to a single public land mobile network ("PLMN").

The mobile core network <NUM> includes several network functions ("NFs"). As depicted, the mobile core network <NUM> includes multiple user plane functions ("UPFs") <NUM>. The mobile core network <NUM> also includes multiple control plane functions including, but not limited to, an Access and Mobility Management Function ("AMF") <NUM> that serves the RAN <NUM>, a Session Management Function ("SMF") <NUM>, and a Policy Control Function ("PCF") <NUM>. In certain embodiments, the mobile core network <NUM> may also include an Authentication Server Function ("AUSF"), a Unified Data Management function ("UDM") <NUM>, a Network Repository Function ("NRF") (used by the various NFs to discover and communicate with each other over APIs), or other NFs defined for the 5GC.

Although specific numbers and types of network functions are depicted in <FIG>, one of skill in the art will recognize that any number and type of network functions may be included in the mobile core network <NUM>. Moreover, where the mobile core network <NUM> is an EPC, the depicted network functions may be replaced with appropriate EPC entities, such as an MME, S-GW, P-GW, HSS, and the like. In certain embodiments, the mobile core network <NUM> may include a AAA server.

In various embodiments, the mobile core network <NUM> supports different types of mobile data connections and different types of network slices, wherein each mobile data connection utilizes a specific network slice. Here, a "network slice" refers to a portion of the mobile core network <NUM> optimized for a certain traffic type or communication service. In certain embodiments, the various network slices may include separate instances of network functions, such as the SMF <NUM> and UPF <NUM>. In some embodiments, the different network slices may share some common network functions, such as the AMF <NUM>. The different network slices are not shown in <FIG> for ease of illustration, but their support is assumed.

While <FIG> depicts components of a <NUM> RAN and a <NUM> core network, the described embodiments for SI delivery <NUM> in a wideband carrier apply to other types of communication networks, including IEEE <NUM> variants, UMTS, LTE variants, CDMA <NUM>, Bluetooth, and the like. For example, in an LTE variant, the AMF <NUM> may be mapped to an MME, the SMF <NUM> may be mapped to a control plane portion of a PGW, the UPF <NUM> may be mapped to a STW and a user plane portion of the PGW, etc..

A base unit <NUM>, one example of a network entity, may periodically broadcast all or part of system information blocks (SIBs) in an initial active downlink (DL) BWP of a cell. A remote unit <NUM> initially acquires relevant SIBs for a PCell (or PSCell) in the initial active DL BWP either from broadcast signaling or from on-demand SI request procedure. If the initial active DL BWP is an active DL BWP for the remote unit <NUM>, the remote unit <NUM> continues acquiring SI for the PCell (PSCell) in the initial active DL BWP. In one example, the base unit <NUM> sends short paging messages (e.g., a systemInfoModification message, a Commercial Mobile Alert Service (CMAS)-Indication, an Earthquake and Tsunami Warning System (ETWS)-Indication, etc.) in paging downlink control information (DCI) and the remote unit <NUM> (re)-acquires updated SI for the PCell (or PSCell) (and/or an urgent notification after) by receiving the paging DCI carrying the short paging messages.

At a given time, if none of active DL BWP(s) for the remote unit <NUM> is same as the initial active DL BWP of the PCell (or PSCell), then the remote unit <NUM> employs one or more of the below described procedures for (re)-acquiring the broadcast SIBs. In various embodiments, a common search space ("C-SS"), which includes a set of PDCCH candidates wherein the set of PDCCH candidates may include PDCCHs for a group of UEs in a cell, or all the UEs in the cell, is configured in an active DL BWP. In other embodiments, no C-SS is configured for any of the active DL BWP(s). These scenarios are discussed in detail below.

Note that in the C-SS, PDCCHs which are supposed to be received/decoded by a group of UEs in a cell, or all the UEs in the cell, can be transmitted. In contrast, in a UE-specific search space ("U-SS"), PDCCHs which are supposed to be received/decoded only by the specific UE can be transmitted. In some embodiments, during (or after) radio resource control ("RRC") connection establishment, the remote unit <NUM> informs (and later updates) the base unit <NUM> of which SIBs it is interested in via a higher layer signaling, e.g., using a RRC message or a medium access control (MAC) bitmap.

<FIG> depicts a network <NUM> used for SI delivery, according to embodiments of the disclosure. The network <NUM> includes a UE <NUM> and a RAN node <NUM> (e.g., a transmission and reception point ("TRP")). The network <NUM> depicts a simplified embodiment of the wireless communication system <NUM>. The UE <NUM> may be one embodiment of the remote unit <NUM>, while the RAN node <NUM> may be one embodiment of the base unit <NUM>. Here, the RAN node <NUM> may be a gNB or other suitable base station. Although only one UE <NUM> is depicted, in other embodiments the RAN node <NUM> may serve a plurality of the UEs <NUM>.

<FIG> illustrates exemplary deployment <NUM> of TRP and UE association used for SI delivery, according to embodiments of the disclosure. <FIG> illustrates exemplary wideband carriers of the deployment <NUM> of <FIG>. The deployment <NUM> depicts a simplified embodiment of the wireless communication system <NUM>. The deployment <NUM> includes at least a first UE ("UE1") <NUM>, a second UE ("UE2") <NUM>, and a third UE ("UE3") <NUM>, as well as at least a first TRP ("TRP1") <NUM>, a second TRP ("TRP2") <NUM>, and a third ("TRP3") TRP <NUM>. In other embodiments, different numbers of UEs <NUM> and gNBs <NUM> may exist in the deployment <NUM>.

The UEs <NUM>, <NUM>, and <NUM> may be embodiments of the UE <NUM> and/or the remote unit <NUM>. The TRPs <NUM>, <NUM>, and <NUM> may be embodiments of the RAN node <NUM> and/or the base unit <NUM>. Here, the TRPs <NUM>, <NUM>, and <NUM> may be a gNB or other suitable base station. Although each TRP is depicted as serving only one UE, in other embodiments each of the TRPs <NUM>, <NUM>, and <NUM> may serve a plurality of UEs <NUM>. The TRPs <NUM>, <NUM>, and <NUM> operate in the same wideband carrier (see operating bandwidth <NUM>). Here, the TRPs <NUM>, <NUM>, and <NUM> provide different spatial coverage and transmit respective cell-defining SS/PBCH blocks in different frequency locations of the wideband carrier, as shown in <FIG>.

According to <FIG> and <FIG>, the first UE <NUM> (e.g., UE1) is associated with SS/PBCH block1 <NUM>, such that the first TRP <NUM> transmits SS/PBCH block1 <NUM> to the first UE <NUM>. Similarly, the second UE <NUM> (e.g., UE2) is associated with SS/PBCH block2 <NUM>, such that the second TRP <NUM> transmits SS/PBCH block2 <NUM> to the second UE <NUM>. Likewise, the third UE <NUM> (e.g., UE3) is associated with SS/PBCH block3 <NUM>, such that the third TRP <NUM> transmits SS/PBCH block3 <NUM> to the third UE <NUM>.

<FIG> depicts wideband carrier operation <NUM>, in the deployment <NUM>. TRP1 transmission <NUM> include the SS/PBCH Block1 <NUM> and transmissions to the first UE <NUM>. TRP2 transmission <NUM> include the SS/PBCH Block2 <NUM> and transmissions to the second UE <NUM>. TRP3 transmission <NUM> include the SS/PBCH Block3 <NUM> and transmissions to the third UE <NUM>. An initial active DL BWP of the first UE <NUM> includes the SS/PBCH Block1 <NUM>. An initial active DL BWP of the second UE <NUM> includes the SS/PBCH Block2 <NUM>. An initial active DL BWP of the third UE <NUM> includes the SS/PBCH Block3 <NUM>. <FIG> also depicts a C-SS <NUM> for SS/PBCH Block1, a C-SS <NUM> for SS/PBCH Block2, and a C-SS <NUM> for SS/PBCH Block3.

As depicted in <FIG>, the first UE <NUM> has switched active DL BWPs from its initial DL BWP (e.g., default DL BWP) to DL BWP <NUM>. Likewise, the second UE <NUM> has switched active DL BWPs from its initial DL BWP (e.g., default DL BWP) to DL BWP <NUM>. Thus, the current active BWPs for the first UE <NUM> and the second UE <NUM> no longer contain the SS/PBCH blocks for their respected cells (e.g., SS/PBCH Block1 <NUM> and SS/PBCH Block2 <NUM>, respectively). However, the active DL BWP <NUM> for the third UE <NUM> includes the SS/PBCH Block3 <NUM> (and C-SS <NUM> for SS/PBCH Block3 <NUM>) and is assumed to be the initial DL BWP.

Note that the first UE <NUM> is configured with C-SS for SS/PBCH Block1 <NUM> in its active DL BWP <NUM> (e.g., DL BWP <NUM> includes C-SS <NUM>). However, the second UE is not configured with C-SS for SS/PBCH Block2 <NUM> in its active DL BWP <NUM> (e.g., DL BWP <NUM> does not include C-SS <NUM>). In some embodiments, the first TRP <NUM> may transmit all or a part of SIBs associated with SS/PBCH block! in the active DL BWP for UE1 <NUM>. In certain embodiments, the first UE <NUM> monitors the C-SS <NUM> for a paging message indicating updated SI. If the first UE <NUM> receives (in the C-SS <NUM> of the active DL BWP <NUM>) paging DCI and/or a paging PDSCH indicating SI modification, two approaches are possible:.

In a first approach, the first UE <NUM> switches to the initial active DL BWP after reception of paging DCI and/or the paging PDSCH indicating SI modification. The first UE <NUM> also updates itself with the changed SI of the PCell or PSCell by receiving SIB(s) transmitted on the initial active DL BWP. That is, the first TRP <NUM> broadcasts SIB(s) of the cell only on the initial active DL BWP of the cell (e.g., which includes SS/PBCH Block1 <NUM>), in order to minimize the system overhead for SI delivery. This approach is discussed in further detail below with reference to <FIG>.

In a second approach, the first UE <NUM> attempts to blindly decode PDCCH addressed by SI-RNTI in the C-SS <NUM> of the active DL BWP <NUM> during a modification period following the one in which the SI change notification was received in the C-SS <NUM>. The first UE <NUM> further receives SI messages according to DCI in the decoded PDCCH. The PDCCH addressed by SI-RNTI in the C-SS <NUM> of the active DL BWP <NUM> indicates PDSCH carrying the SI message transmitted either in the initial active DL BWP or in a DL BWP different from the initial active DL BWP. For example, if a decoded common PDCCH indicates a common PDSCH carrying a SI message is transmitted in the initial active DL BWP associated with SS/PBCH block1, the first UE <NUM> retunes to its initial active DL BWP and receives the corresponding SI message. This approach is discussed in further detail below with reference to <FIG>.

In some embodiments, the second TRP <NUM> may transmit all or a part of SIBs associated with SS/PBCH Block2 in the active DL BWP for UE2 <NUM>. In certain embodiments, the second UE <NUM> may periodically switch back to its initial DL BWP (e.g., containing SS/PBCH Block2) according to a DL gap pattern. During the gaps of the DL gap pattern, no DL data/messages are to be sent to the second UE <NUM> in the DL BWP <NUM>. Thus, during the DL gaps the second UE <NUM> is able to retune to its initial DL BWP to monitor for a message indicating updated SI. If the second UE <NUM> receives an indication of SI modification (e.g., indicating updated SI), the second UE <NUM> proceeds to acquire one or more SIBs or SI messages carrying the updated SI, as discussed in further detail below with reference to <FIG> and <FIG>.

Note that because the third UE <NUM> has an active DL BWP that includes the SS/PBCH Block3 and the associated C-SS <NUM>, the third TRP <NUM> may transmit all or a part of SIBs associated with SS/PBCH block in the active DL BWP <NUM>. Thus, the third TRP <NUM> may send updated SI over the initial active DL BWP of the third UE <NUM> and the third UE <NUM> does not need to switch DL BWP in order to receive the updated SI.

<FIG> is a diagram illustrating one embodiment of a procedure <NUM> for initial SI acquisition, e.g., in a wideband carrier. The procedure <NUM> may be implemented by a remote unit <NUM>, such as the UE <NUM>, the first UE <NUM>, the second UE <NUM>, and/or the third UE <NUM>. The remote unit <NUM> acquires at least one SIB for a first cell in an initial active DL BWP (see block <NUM>). The first cell may be associated with a specific base unit <NUM>, such as the RAN node <NUM>, the first TRP <NUM>, the second TRP <NUM>, and/or the third TRP <NUM>. Further, the first cell may be a primary cell of the remote unit <NUM>. Here, the SIB(s) may be essential system information block(s) associated with a cell-defining SS/PBCH block. As discussed above, the SIB may be broadcast periodically by the base unit <NUM>. The remote unit <NUM> may also acquire one or more SIBs using an on-demand SI request procedure. The system information acquired here by the remote unit <NUM> is referred to as "initial system information.

Having received the at least one SIB, the remote unit <NUM> establishes an RRC connection with the first cell (see block <NUM>). Here, the remote unit <NUM> establishes the RRC connection based on the acquired initial system information. After establishing the RRC connection, the base unit <NUM> configures the remote unit <NUM> with at least one DL BWP of the first cell (see block <NUM>). Here, the base unit <NUM> may use higher layer signaling (e.g., RRC messages, MAC control elements, etc.) to send the DL BWP configuration.

During RRC connection establishment, the remote unit <NUM> may inform the base unit <NUM> of one or more SIBs it is interested in, e.g., SIBs necessary for UE operation (see block <NUM>). Alternatively, the remote unit <NUM> may inform the base unit <NUM> of the one or more SIBs necessary for UE operation after RRC connection establishment. The one or more SIBs necessary for UE operation are referred to as "needed SIBs. " In various embodiments, the remote unit <NUM> uses higher layer signaling, such as an RRC message or MAC bitmap, to indicate the needed SIBs.

Moreover, the remote unit <NUM> may further receive an indication of a first DL BWP selected from the configured BWP(s) of the first cell to be an active DL BWP for the remote unit <NUM>. Regarding reacquisition of SI, for example acquiring updated SI of the first cell, the remote unit <NUM> determines whether the active DL BWP is the same as the initial DL BWP (see decision block <NUM>). If the active DL BWP is the same as the initial DL BWP, then the remote unit <NUM> monitors system information change and continues acquiring the updated system information in the initial DL BWP (see block <NUM>). Here, the base unit <NUM> may send short paging messages, such as systemInfoModification, in paging DCI in the initial DL BWP.

However, if the active DL BWP is different from the initial DL BWP, then the remote unit <NUM> monitors for an indication of updated system information and acquires the updated system information (see block <NUM>) according to one or more of the procedures discussed below with reference to <FIG>.

<FIG> depicts a first procedure <NUM> for acquiring modified SI when common search space ("C-SS") is configured for the active DL BWP, according to embodiments of the disclosure. The first procedure <NUM> is one embodiment of step <NUM> in the procedure <NUM> and allows for acquisition of (e.g., modified) system information when the active DL BWP for the remote unit <NUM> is not the initial DL BWP. The first procedure <NUM> corresponds to the use case where a C-SS is configured in the active DL BWP of the remote unit <NUM>. Referring to <FIG> and <FIG>, the first procedure <NUM> may be implemented by the first UE <NUM> because the active BWP <NUM> of the first UE <NUM> includes the C-SS <NUM> for SS/PBCH Block1.

In the first use case, a common search space ("C-SS") is configured in an active DL BWP for a remote unit <NUM>, such as the first UE <NUM>. Here, the C-SS is UE-specifically configured in a given active DL BWP. Here, the given active DL BWP is referred to as a "first DL BWP. " However, note that the "first DL BWP" is different than the initial active DL BWP. When so configured, the remote unit <NUM> monitors the C-SS configured in the first DL BWP.

The base unit <NUM> implicitly or explicitly configures one or more DL gap patterns. As used herein, a "DL gap pattern" refers to a pattern of recurring DL gaps. During a DL gap, the remote unit <NUM> is not expected to receive any DL signal/channel in the current active DL BWP. Said otherwise, the TRP (here the base unit <NUM>) may not transmit any DL message or data to the remote unit <NUM> in the first DL BWP during a DL gap. The base unit <NUM> configures each of the one or more DL gap patterns taking into account one or more SI-window (e.g., periodically occurring time domain windows) configurations for broadcast SIBs. In various embodiments, the base unit <NUM> broadcasts SIBs of the cell only on the initial active DL BWP of the cell in order to minimize system overhead for SI delivery. In such embodiments, the remote unit <NUM> must retune to the initial active DL BWP (or default DL BWP) to receive updated SI.

The remote unit <NUM> monitors a C-SS configured in the first DL BWP (see block <NUM>). The remote unit <NUM> determines whether paging message is received (e.g., via paging DCI or paging PDSCH in the C-SS in the first DL BWP) indicating SI modification (see decision block <NUM>). As discussed above, SI modification may be indicated using a short paging message, such as "systemInfoModification.

Upon receiving indication of SI modification, the remote unit <NUM> determines which DL gap pattem(s) it needs to employ in the first DL BWP (see block <NUM>). Here, selection of the DL gap pattern(s) may be based on the SIBs that it has to re-acquire (e.g., the needed SIBs previously indicated to the base unit <NUM>). Note that the base unit <NUM> is also able to determine which DL gap pattern(s) the remote unit <NUM> needs to employ, as the remote unit <NUM> transmits an indication of the needed SIBs (e.g., via higher layer signaling) during the initial acquisition procedure discussed above with reference to <FIG>.

Having identified the appropriate DL gap pattern(s), the remote unit <NUM> switches (e.g., retunes its receiver) to the initial active DL BWP (or default DL BWP) during a DL gap (see block <NUM>). In various embodiments, the DL gap is the first occurring DL gap in the selected DL gap pattern after the indication of SI modification is received (e.g., the next occurring DL gap after the paging DCI or paging PDSCH). Also, during the DL gap, the remote unit <NUM> receives one or more updated SIBs in the initial active DL BWP (see block <NUM>). Because the base unit <NUM> has identified which DL gap pattern(s) the UE <NUM> will employ for SI re-acquisition, during the DL gap of the first DL BWP the base unit <NUM> can transmit to the remote unit <NUM> (and the remote unit <NUM> can receive) UE-specific PDCCH and PDSCH (in addition to common PDCCH and PDSCH) in the initial active DL BWP.

In one example, the remote unit <NUM> applies a determined DL gap pattern on slot 'n+k' or later if receiving paging DCI or paging PDSCH indicating SI modification on slot 'n'.

Here, the value 'k' may be pre-defined, UE-specifically configured, or cell-specifically configured. Further, the remote unit <NUM> assumes that the actual DL gap for the first DL BWP occurs in a modification period following the one in which the SI change notification was received.

In another example, a remote unit <NUM> using a DRX cycle shorter than or equal to the modification period, verifies that stored system information remains valid by applying a default DL gap pattern for the first DL BWP, receiving SystemInformationBlockType1 in the initial active DL BWP after the modification period boundary, and checking systemInfoValueTag in the received SystemInformationBlockType1. Here, the default DL gap pattern is configured for allowing the UE <NUM> to receive SystemInformationBlockType1.

In various embodiments, at the end of the DL gap the remote unit <NUM> switches back to the first DL BWP (see block <NUM>). The remote unit <NUM> may continue monitoring the C-SS for further indications of SI modification.

<FIG> depicts a second procedure <NUM> for acquiring modified SI when common search space ("C-SS") is configured for the active DL BWP, according to embodiments of the disclosure. The second procedure <NUM> is another embodiment of step <NUM> in the procedure <NUM> and allows for acquisition of (e.g., modified) system information when the active DL BWP for the remote unit <NUM> is not the initial DL BWP. The second procedure <NUM> corresponds to an alternative approach to the first use case discussed above, where a C-SS is configured in the active DL BWP of the remote unit <NUM>. Referring to <FIG> and <FIG>, the second procedure <NUM> may be implemented by the first UE <NUM> because the active BWP <NUM> of the first UE <NUM> includes the C-SS <NUM> for SS/PBCH Block1.

Upon receiving indication of SI modification, the remote unit <NUM> decodes (e.g., attempts to blindly decode) PDCCH addressed by SI-RNTI in the C-SS of the first DL BWP during the modification period following the one in which the SI change notification was received (see block <NUM>). In certain embodiments, PDCCH addressed by SI-RNTI in the C-SS of the active DL BWP (e.g., the first DL BWP) indicates PDSCH carrying the SI message transmitted in a second DL BWP. Here, the second DL BWP may be the initial active DL BWP or a DL BWP different from the initial active DL BWP. In one embodiment, the second DL BWP is the same as the first DL BWP. In other embodiments, the second DL BWP is different than the first DL BWP.

In one example, the base unit <NUM> transmits PDSCH(s) carrying SI messages only in the initial active DL BWP for system overhead reduction. In another example, the base unit <NUM> transmits multiple PDSCH(s) carrying the same SI message in the frequency domain, at least including the first DL BWP, so that the remote unit <NUM> does not have to retune from the first DL BWP to the initial active DL BWP. In yet another example, some SI messages are transmitted only in the initial active DL BWP of the cell, and other SI messages are transmitted multiple instances in the frequency domain (e.g., transmitted in both the first DL BWP and the initial active DL BWP).

Additionally, the remote unit <NUM> uses the PDCCH addressed by SI-RNTI in the C-SS of the first DL BWP to identify one or more slots in which PDSCH(s) carrying the SI messages are transmitted on the second DL BWP (see block <NUM>). Note that in the embodiments of <FIG>, the remote unit <NUM> does not need to be configured with DL gap patterns nor does the remote unit <NUM> need to identify which DL gap pattern to employ. Instead, the PDCCH addressed by SI-RNTI is used to identify when the SI messages containing modified/updated SI are to be delivered.

Where the second DL BWP is different than the first DL BWP, the remote unit <NUM> switches (e.g., retunes) to the second DL BWP at an appropriate time based on the identified one or more slots (see block <NUM>). The time at which the remote unit <NUM> retunes to the second DL BWP may be based on the capabilities of the remote unit <NUM>.

Additionally, the remote unit <NUM> receives at least one PDSCH (e.g., receives messages on one or more PDSCH) in the second DL BWP carrying SI messages during the identified slot(s) (see block <NUM>). Because the base unit <NUM> is able to identify which slots the remote unit <NUM> will tune to in the second DL BWP (unless remote unit <NUM> misses the DL resource assignment(s) for PDSCH(s) carrying the SI messages of interest), the base unit <NUM> can transmit UE-specific PDCCH and/or UE-specific PDSCH to the remote unit <NUM> in the second DL BWP during the identified slot(s). For those slots, the remote unit <NUM> may monitor UE-specific PDCCH and potentially receive UE-specific PDSCH in addition to reception of PDSCH(s) carrying the SI messages in the second DL BWP. Moreover, the base unit <NUM> does not transmit any DL signal/channel for the remote unit <NUM> in the first DL BWP during the identified slot(s).

In various embodiments of the second procedure <NUM>, the remote unit <NUM> switches back to the first DL BWP after receiving a modified system information (see block <NUM>). The remote unit <NUM> may continue monitoring the C-SS for further indications of SI modification.

In various embodiments of the first procedure <NUM> and/or second procedure <NUM>, the system information change indication in paging message or paging DCI includes an indication of at least a portion of the one or more SIBs (or SI messages) that will change. The change of specific SIBs (or SI messages) may be indicated by a SI message-specific value tag (e.g., systemInfoValueTag/systemInfoConfigurationIndex) and/or an area ID (e.g., systemInfoAreaIdentifier) associated with the SIB (or SI message). Here, the remote unit <NUM> may receive only the SIBs or SI messages containing modified SI.

However, if the SI change indication on the active/first DL BWP in a modification period: a) does not include any information of which SIBs (or SI messages) have changed or b) indicates that SIB1 needs to be reacquired, then the remote unit <NUM> may retune to a second DL BWP at the next modification period boundary to acquire the changes to the SI. The second DL BWP may be an initial active DL BWP or a second DL BWP which may be configured by the gNB for SI reception. In one embodiment, the second DL BWP used to re-acquire SI may be indicated in the SI change indication.

In one example, the remote unit <NUM> retunes to the second DL BWP for a duration equal to the modification period. In the context of the first procedure <NUM>, the DL gap includes the modification period and may also include the retuning time (one or more OFDM symbols or slots) for switching between the first DL BWP and the second DL BWP. The remote unit <NUM> may not be expected to receive DL in a portion of the slot corresponding to the BWP retuning time at the end of the preceding modification period and at the start of the subsequent modification period (e.g., following the modification period in which updated SI is provide).

In one example, the remote unit <NUM> acquires updated SI information corresponding to the SIBs provided via periodic broadcast basis as indicated in SIB1 on the second DL BWP and updated SI corresponding to the SIBs provided via only on-demand basis on the first DL BWP by performing SI request on the first DL BWP. Information for the remote unit <NUM> to perform SI request on the first DL BWP may be indicated in the SIB1 or configured to the remote unit <NUM>, e.g., during a BWP configuration procedure.

In some examples, following reacquiring of SIB1 (if needed) which includes time-domain scheduling information (e.g., periodicity, SI-window size) of SI messages, information on the availability of other SIBs and to which SI-message a particular SIB is mapped to (a SI-message may carry one or more SIBs), to reacquire an SI-message with updated SIB(s) SI information, the UE <NUM> may retune/switch to the second DL BWP at the start of the SI-window corresponding to the SI-message to receive the SI-message. Here, the duration of the switch/retuning to the second DL BWP may be the duration of the SI-window.

If the remote unit <NUM> requires more than one SI-message with SI-windows in close proximity (e.g., having a gap between the SI-window occasions of different SI-message of less than a certain number of slots/subframes), the duration of the switch/retuning to the second DL BWP may last from the beginning of the earliest SI-window to the end of the latest SI-window of the SI-windows corresponding to the more than one SI-message. Here, the number of slots/subframes may be pre-configured (e.g., hard-coded in specification) or configured to the remote unit <NUM> (e.g., based on UE capability).

In some examples, the remote unit <NUM> may accumulate SI-Message transmissions across several SI-Windows within the Modification Period. Here, the number of SI-windows to accumulate may be pre-configured/hard-coded in specification or configured to the remote unit <NUM>, e.g., based on UE capability and may be relative to the start of the modification period. The number of SI-windows the remote unit <NUM> may monitor for SI message reception may be different for periodic broadcast SI-messages (SI message acquisition not triggered due to UE request) than for on-demand SI-messages (SI message acquisition triggered due to UE request). The remote unit <NUM> may take the number of SI-windows to accumulate for a SI-message into account to determine the number of retuning /DL gap periods and the retuning/gap period the remote unit <NUM> is allowed for switching to the second DL BWP to acquire updated SI information.

In one example, a remote unit <NUM> receives an indication that the first DL BWP is different than the second DL BWP on which SI information is transmitted for at least periodic broadcast SIBs, thereby requiring the remote unit <NUM> to retune/switch to the second DL BWP to receive at least the updated periodic broadcast SIBs (due to SI change indication). Here, the remote unit <NUM> may, after acquiring the updated SI information for all the required SIBs (or at least the periodic broadcast SIBs on the second DL BWP), indicate/acknowledge to the base unit <NUM> successful completion of the SI update procedure for all the required SIBs (or at least the periodic broadcast SIBs on the second DL BWP). This acknowledgement may be sent on the first DL BWP and may correspond to a dedicated SR signal, a PRACH signal, or a SI acknowledgement higher layer signaling (e.g., MAC CE) sent on PUSCH. During the retuning/switch/gap period on the second DL BWP, the remote unit <NUM> may receive UE-specific PDCCH and PDSCH in the second DL BWP.

<FIG> depicts a third procedure <NUM> for acquiring modified SI when common search space ("C-SS") is not configured for the active DL BWP, according to embodiments of the disclosure. The third procedure <NUM> is another embodiment of step <NUM> in the procedure <NUM> and allows for acquisition of (e.g., modified) system information when the active DL BWP for the remote unit <NUM> is not the initial DL BWP. The third procedure <NUM> corresponds to a first approach to a second use case, where a C-SS is not configured in the active DL BWP of the remote unit <NUM>. Referring to <FIG> and <FIG>, the third procedure <NUM> may be implemented by the second UE <NUM> because the active BWP <NUM> of the second UE <NUM> does not include the C-SS <NUM> for SS/PBCH Block2.

The remote unit <NUM> receives a DL gap pattern (see block <NUM>). In the second use case, C-SS is not configured for any of active DL BWP(s) of the remote unit <NUM>, thus the remote unit <NUM> cannot monitor a C-SS for paging messages related to SI modification. In one embodiment, the base unit <NUM> (e.g., the second TRP <NUM>) may configure the remote unit <NUM> (e.g., the second UE <NUM>) with a first DL gap pattern for at least one active DL BWP. In certain embodiments, the remote unit <NUM> may be configured with a second DL BWP for reception of paging messages and/or SI messages. In various embodiments, the second DL BWP is the initial active DL BWP of the remote unit <NUM>. Here, the first DL gap pattern is used by the remote unit <NUM> for reception of paging messages (or paging DCI) indicating the SI modification in a second DL BWP of the cell. Based on reported UE capability information, the base unit <NUM> may command the remote unit <NUM> to apply the signaled first DL gap pattern for all active BWPs without C-SS or for some selected active BWPs.

Accordingly, the remote unit <NUM> switches to the second DL BWP based on the first DL gap pattern (see block <NUM>). As discussed above, the DL gap pattern indicates time periods in which no DL channels/signals are transmitted to the remote unit <NUM> on the first DL BWP (e.g., active DL BWP). Note that the base unit <NUM> may transmit DL channels/signals to other served units during a DL gap of the remote unit <NUM>. Similarly, other base units <NUM> sharing the same wideband carrier may also transmit DL channels/signals to other serve units during a DL gap of the remote unit <NUM>.

During at least a part of the DL gap, the remote unit <NUM> monitors the second DL BWP for reception of paging messages indicating SI modification (see block <NUM>). Note that the DL gap may include time for the remote unit <NUM> to retune its receiver to the second DL BWP (and additional time to retune the receiver to the first DL BWP). If no paging messages indicating SI modification are received in the second DL BWP, the remote unit <NUM> switches back to the first DL BWP (see block <NUM>). Note that the remote unit <NUM> may again switch to the second DL BWP based on the first DL gap pattern to monitor for paging messages indicating SI modification.

In certain embodiments, the remote unit <NUM> is configured with a third DL BWP for receiving SI messages. In some embodiments, the third DL BWP is different than the second DL BWP use for receiving paging messages indicating SI modification. In one embodiment, the third DL BWP may be the initial active DL BWP. Alternatively, the third DL BWP may be different than the initial active DL BWP.

Moreover, the remote unit <NUM> may be configured with a second DL gap pattern used for reception of SI messages that the remote unit <NUM> is interested in. The second DL gap pattern may have a different arrangement of DL gaps and/or different duration of DL gaps than the first DL gap pattern. In various embodiments, the remote unit <NUM> applies the second DL gap pattern for reception of the SI messages, only if remote unit <NUM> receives paging DCI or a paging message indicating SI modification (see block <NUM>). During the DL gap in the at least one active DL BWP (e.g., of the first or second DL gap pattern), the remote unit <NUM> can receive UE-specific PDCCH and PDSCH in the initial active DL BWP or the (second) DL BWP configured for reception of the SI messages (see block <NUM>).

In various embodiments of the third procedure <NUM>, the remote unit <NUM> switches back to the first DL BWP after receiving the modified system information (see block <NUM>). The remote unit <NUM> may continue switching to the second DL BWP to monitor for further indications of SI modification based on the first DL gap pattern.

<FIG> depicts a third procedure <NUM> for acquiring modified SI when common search space ("C-SS") is not configured for the active DL BWP, according to embodiments of the disclosure. The third procedure <NUM> is another embodiment of step <NUM> in the procedure <NUM> and allows for acquisition of (e.g., modified) system information when the active DL BWP for the remote unit <NUM> is not the initial DL BWP. The third procedure <NUM> corresponds to a second approach to the second use case, where a C-SS is not configured in the active DL BWP of the remote unit <NUM>. Referring to <FIG> and <FIG>, the third procedure <NUM> may be implemented by the second UE <NUM> because the active BWP <NUM> of the second UE <NUM> does not include the C-SS <NUM> for SS/PBCH Block2.

The remote unit <NUM> receives a DL gap pattern (see block <NUM>). In some embodiments, the base unit <NUM> (e.g., the second TRP <NUM>) may configure the remote unit <NUM> (e.g., the second UE <NUM>) with a first DL gap pattern for at least one active DL BWP. In certain embodiments, the remote unit <NUM> may be configured with a second DL BWP for reception of paging messages and/or SI messages. In various embodiments, the second DL BWP is the initial active DL BWP of the remote unit <NUM>.

Here, the first DL gap pattern is used by the remote unit <NUM> for reception of System Information Block Type1 (SIB1), e.g., in the initial active DL BWP, after the modification period boundary. Based on reported UE capability information, the base unit <NUM> may command the remote unit <NUM> to apply the signaled first DL gap pattern for all active BWPs without C-SS or for some selected active BWPs. Accordingly, the remote unit <NUM> switches to the second DL BWP (e.g., initial active DL BWP) based on the first DL gap pattern (see block <NUM>).

During at least a part of the DL gap, the remote unit <NUM> receives the SIB1 on the second DL BWP (see block <NUM>). In various embodiments, SIB1 is transmitted in the initial active DL BWP, thus the remote unit <NUM> switches to the initial active DL BWP based on the first DL gap pattern to receive SIB1. Additionally, the remote unit <NUM> determines whether the SIB1 indicates SI modification (see block <NUM>).

In various embodiments, the remote unit <NUM> checks a systemInfoValueTag in the received SIB1 to determine whether to update the stored system information or not. For example, the remote unit <NUM> may determine whether the existing stored system information is not valid any more based on checking of systemInfoValueTag in the received SIB1. The remote unit <NUM> may also check the area ID (systemInfoAreaIdentifier) in the received SIB1. In one embodiment, the value tag and area ID may be common for all SIBs and SI-messages such that the remote unit <NUM> is informed about changes in system information with change to the value tag and/or area ID, but no further details are provided e.g. regarding which system information will change. In another embodiment, the value tag and area ID may be SIB1 and SI-message specific indicating SI change for SIB1 and/or for the specific SI-message.

If SIB1 does not indicate SI modification, then the remote unit <NUM> may switch back to the first DL BWP (see block <NUM>). Note that the remote unit <NUM> may again switch to the second DL BWP based on the first DL gap pattern to monitor for paging messages indicating SI modification.

In certain embodiments, the remote unit <NUM> is configured with a third DL BWP for receiving SI messages. In some embodiments, the third DL BWP is different than the second DL BWP use for receiving SIB1 indicating SI modification. In one embodiment, the third DL BWP may be the initial active DL BWP. Alternatively, the third DL BWP may be different than the initial active DL BWP.

Moreover, the remote unit <NUM> may be configured with a second DL gap pattern used for reception of SI messages that the remote unit <NUM> is interested in. The second DL gap pattern may have a different arrangement of DL gaps and/or different duration of DL gaps than the first DL gap pattern. In various embodiments, the remote unit <NUM> applies the second DL gap pattern for reception of the SI messages, only if the remote unit <NUM> identifies that the existing stored system information is not valid any more, e.g., based on checking of systemInfoValueTag in the received SIB1. The remote unit <NUM> may also check the area ID (systemInfoAreaIdentifier) in the received SIB1, as discussed above. During the DL gap in the at least one active DL BWP (e.g., of the first or second DL gap pattern), the remote unit <NUM> can receive UE-specific PDCCH and PDSCH in the initial active DL BWP or the (second) DL BWP configured for reception of the SI messages (see block <NUM>).

In other embodiments of step <NUM> of <FIG>, the base unit <NUM> may send the updated SI messages via dedicated signaling (e.g. UE-specific PDCCH and/or PDSCH) to the remote unit <NUM> operated in an active DL BWP different from the initial active DL BWP. In one example, the base unit <NUM> pushes all SI messages when any change happens or when ETWS or CMAS becomes available. In another example, the base unit <NUM> pushes SIBs in which the remote unit <NUM> is interested, only when necessary, e.g. a change of these SIBs occur or some of these SIBs become available. In both examples, the base unit <NUM> is responsible to maintain or send the up-to-date system information to the UE. Thus, the remote unit <NUM> does not treat the cell(s) as barred if the base unit <NUM> did not provide some essential SIB(s) but may repeat the SI/ SIB requests. Further, the base unit <NUM> may send only the updated system information, i.e. information elements which are different from the previous values, to reduce the signaling overhead.

For UE demanded SIBs (e.g. use-case specific system information), the remote unit <NUM> requests for a specific SIB(s) and the base unit <NUM> provides the requested SIB(s) via dedicated signaling. Alternatively, the remote unit <NUM> may indicate which SIB(s) it needs to (re)-acquire via higher layer signaling (e.g. RRC or MAC) and expects that during specific SIB acquisition (i.e. SI-window corresponding to the specific SIB) the base unit <NUM> will transmit scheduling information for DL and/or uplink (UL) channels in the initial active (or default) DL BWP.

For a SCell, the remote unit <NUM> may not be configured with the C-SS for any of configured DL BWP(s) of the SCell. In one example, the base unit <NUM> provides the remote unit <NUM> with the required SI initially and the updated SI later by dedicated signaling. In another example, an RRC procedure for the remote unit <NUM> which removes and adds back the SCell along with the updated SI or which reconfigures one or more DL BWP(s) along with the updated SI is used to update the SI.

<FIG> depicts one example of a paging-SearchSpace information element <NUM>, according to embodiments of the disclosure. A remote unit <NUM>, such as the UE <NUM>, uses the information element <NUM> to determine PDCCH monitoring symbols/slots, e.g., to receive a paging message. In 3GPP NR, a paging occasion is defined as a number of slots where the UE <NUM> has to monitor the PDCCH carrying paging DCI. The UE <NUM> may compute its own paging frame and paging occasion within the paging frame based on its UE identity and a discontinuous reception (DRX) cycle length.

A control resource set (CORESET) configuration for paging DCI can be the same as the CORESET configuration for PDCCH carrying RMSI scheduling information, while PDCCH monitoring symbols/slots can be different and separately configured with the higher layer parameter 'paging-SearchSpace. ' Note that the CORESET configuration may include at least one of: subcarrier spacing, a CP length, a number of consecutive resource blocks, a number of consecutive symbols, resource element group (REG) bundle size, and control channel element (CCE) to REG mapping type.

The UE <NUM> determines a number of consecutive resource blocks and a number of consecutive symbols for the control resource set of Type0-PDCCH common search space (for a DCI format with cyclic redundancy code (CRC) scrambled by a SI-RNTI on a primary cell) from the first four bits of RMSI-PDCCH-Config and determines PDCCH monitoring occasions from the second four bits of RMSI PDCCH Config. The allowed PDCCH configurations for PDCCH carrying RMSI scheduling information include the following three different multiplexing types for a SS/PBCH block and a corresponding CORESET (i.e. the CORESET which is spatially quasi-co-located with the SS/PBCH block): Type <NUM>, Type <NUM>, and Type <NUM>.

For Type <NUM>, the SS/PBCH block and the corresponding RMSI CORESET occur in different time instances, and a SS/PBCH block transmit bandwidth and the initial active DL BWP containing RMSI CORESET overlap.

For Type <NUM>, the SS/PBCH block and the RMSI CORESET occur in different time instances, and the SS/PBCH block transmit bandwidth and the initial active DL BWP containing RMSI CORESET do not overlap.

For Type <NUM>, the SS/PBCH block and the RMSI CORESET occur in the same time instance, and the SS/PBCH block transmit bandwidth and the initial active DL BWP containing RMSI CORESET do not overlap.

The configuration framework of RMSI CORESET monitoring occasions defined for Type <NUM> multiplexing can be easily extended to define multiple sets of CORESET monitoring occasions for all RMSI/paging CORESETs defined for Type <NUM>/<NUM>/<NUM> multiplexing, wherein each set of CORESET monitoring occasions corresponds to one paging occasion. In one example, at least one paging occasion may be the same as RMSI monitoring occasions.

In various embodiments, the information element <NUM> may have the following components: pagingOccasionList, pagingFrameDuration, and PagingOccasion. The pagingOccasionList is a list of one or more paging occasion configurations. In one embodiment, the number of paging occasions per paging frame is determined by the number of paging occasion configurations. In certain embodiments, the first paging occasion is always same as RMSI monitoring occasions (i.e., Type0-PDCCH common search space) and the configuration for the first paging occasion is not explicitly signaled. The pagingFrameDuration indicates the length of a paging frame. In one embodiment, the value of pagingFrameDuration indicates <NUM> radio frame. In another embodiment, the value of pagingFrameDuration indicates <NUM> radio frames.

The PagingOccasion parameter may include a plurality of components. The parameter groupOffset (O) is based on the subcarrier spacing of the SS/PBCH block. In the depicted embodiment, the groupOffset is selected from possible values {<NUM>, <NUM>, <NUM>, <NUM>} when subcarrier spacing of SS/PBCH block is <NUM> or <NUM> and is selected from possible values {<NUM>, <NUM>, <NUM>, <NUM>} when subcarrier spacing of SS/PBCH is <NUM> or <NUM>. The parameter nrofSearchSpaceSetsPerSlot (N) indicates the number of search space sets and, in the depicted embodiment, is selected from possible values {<NUM>, <NUM>}. The parameter slotIncrementStep (M) indicates an incremental step size and, in the depicted embodiment, is selected from possible values {<NUM>/<NUM>, <NUM>, <NUM>}. The parameter startOFDMsymbol indicates a starting symbol of the paging occasion and, in the depicted embodiment, is selected from possible values {<NUM>, <NUM>, <NUM>, <NUM>,. , <NUM>, <NUM>}. The parameter slotOffset (K) indicates a slot offset and, in the depicted embodiment, is selected from possible values {<NUM>, <NUM>}.

Referring to <FIG> and <FIG>, for SS/PBCH block with index i and a given `PagingOccasion' configuration, a UE <NUM> can determine an index of the paging occasion slot n<NUM> in a paging frame using equation <NUM>, below: <MAT>.

Here O is a group offset, M is a slot increment step, K is a slot offset, as defined above, µ is subcarrier spacing (in kHz) of paging PDCCH normalized by <NUM>, and <MAT> is the number of slots per paging frame in the paging PDCCH subcarrier spacing, µ.

In certain embodiments, one or more of the paging occasion parameters, such as the slotIncrementStep (M), slotOffset (K), and/or the paging search-space set in the paging occasion slot n<NUM>, may be dependent on the UE-ID.

<FIG> depicts one embodiment of a user equipment apparatus <NUM> that may be used for SI delivery in a wideband carrier, according to embodiments of the disclosure. The user equipment apparatus <NUM> may be one embodiment of the remote unit <NUM> and/or the UE <NUM>, described above. Furthermore, the user equipment apparatus <NUM> may include a processor <NUM>, a memory <NUM>, an input device <NUM>, an output device <NUM>, a transceiver <NUM> for communicating with one or more base units <NUM>.

As depicted, the transceiver <NUM> may include a transmitter <NUM> and a receiver <NUM>. The transceiver <NUM> may also support one or more network interfaces <NUM>, such as the Uu interface used to communicate with a gNB. In some embodiments, the input device <NUM> and the output device <NUM> are combined into a single device, such as a touchscreen. In certain embodiments, the user equipment apparatus <NUM> may not include any input device <NUM> and/or output device <NUM>.

In some embodiments, the processor <NUM> acquires at least one system information block for a first cell in an initial active DL BWP. Moreover, the processor <NUM> controls the transceiver <NUM> to establish an RRC connection with the first cell based on the acquired at least one system information block. The transceiver <NUM> receives a configuration including at least one DL BWP of the first cell via higher layer signaling and further receives an indication of a first DL BWP selected from the configured at least one BWP of the first cell as an active DL BWP. Moreover, the processor <NUM> controls the transceiver to transmit via higher layer signaling an indication of one or more SIBs necessary for UE operation to a network entity, wherein the first DL BWP is different from the initial active DL BWP.

In certain embodiments, the first cell is a primary cell of a primary cell group or a primary secondary cell of a secondary cell group. In some embodiments, the at least one system information block is acquired from at least one of broadcast signaling and an on-demand SI request procedure. In one embodiment, the indication of the one or more SIBs necessary for UE operation is transmitted via at least one of an RRC message and a MAC bitmap.

In some embodiments, the transceiver <NUM> receives a C-SS configuration of the first DL BWP. In such embodiments, the transceiver <NUM> receives an indication of at least one DL gap pattern of the first DL BWP and receives a paging message indicating system information modification, wherein the paging message indicating system information modification is included in a PDCCH of the configured C-SS. Moreover, the processor <NUM> selects a DL gap pattern from the indicated at least one DL gap pattern of the first DL BWP based on the one or more SIBs necessary for UE operation and re-tunes to the initial active DL BWP based on the selected DL gap pattern of the first DL BWP to re-acquire updated system information of the first cell in the initial active DL BWP. Here, the user equipment apparatus is expected to receive a DL signal/channel not in the first DL BWP but in the initial active DL BWP during a DL gap of the selected DL gap pattern of the first DL BWP.

Additionally, when receiving a C-SS configuration of the first DL BWP, the processor <NUM> may decode a PDCCH in the configured C-SS of the first DL BWP, wherein a CRC of the decoded PDCCH is scrambled by SI-RNTI and identify at least one slot, where at least one PDSCH carrying the one or more SIBs necessary for UE operation is transmitted by the network entity on a second DL BWP, based on the decoded PDCCH. The processor <NUM> further re-tunes to the second DL BWP, and re-acquiring updated system information of the first cell in the second DL BWP on the identified at least one slot, wherein the second DL BWP is different from the first DL BWP and the UE is expected to receive a DL signal/channel not in the first DL BWP but in the second DL BWP on the identified at least one slot.

In further embodiments, the transceiver <NUM> may receive a paging message indicating system information modification in the configured C-SS of the first DL BWP, before the processor <NUM> attempts to decode in the configured C-SS of the first DL BWP the PDCCH whose CRC is scrambled by SI-RNTI. In one embodiment, the second DL BWP is same as the initial active DL BWP. In another embodiment, the second DL BWP is different from the initial active DL BWP.

In some embodiments, the transceiver <NUM> may receive updated system information via dedicated signaling in the first DL BWP. In one embodiment, the processor <NUM> controls the transceiver <NUM> to maintain the RRC connection with the first cell when the updated system information corresponding to one or more essential SIB(s) is not provided by the network entity (e.g., a RAN node <NUM>, such as a gNB) and send a request for the updated system information. In certain embodiments, the updated system information includes one or more information elements, wherein values of the one or more information elements are different from the previous values.

In various embodiments, the transceiver <NUM> may receive a configuration for a first DL gap pattern and a second DL gap pattern, wherein the processor <NUM> re-tunes to a second DL BWP based on the first DL gap pattern and determining in the second DL BWP whether system information will be or has been modified or not, and re-tunes to a third DL BWP based on the second DL gap pattern and receiving updated system information in the third DL BWP, if it is determined that the system information will be or has been modified. Here, a C-SS of the first DL BWP is not configured, the second and third DL BWP(s) are different from the first DL BWP, and the user equipment apparatus <NUM> is expected to receive a DL signal/channel not in the first DL BWP, but in the second DL BWP during a DL gap of the first DL gap pattern and in the third DL BWP during a DL gap of the second DL gap pattern.

In one such embodiment, the first DL gap pattern may be used for receiving a paging message indicating SI modification in the second DL BWP. In another such embodiment, the first DL gap pattern may be used for receiving a SystemInformationBlockType1 (SIB1) in the second DL BWP, wherein systemInfoValueTag in the SIB1 is used to determine whether to update stored system information or not. In one embodiment, the second DL BWP is same as the third DL BWP. In another embodiment, the second DL gap pattern is based on the one or more SIBs necessary for UE operation.

In certain embodiments, the transceiver <NUM> receives one or more paging occasion configurations in a system information block and the processor <NUM> determines at least one paging frame and at least one paging occasion identity within the at least one paging frame based on at least one of a UE identity and a discontinuous reception (DRX) cycle length. Moreover, the processor <NUM> may select at least one paging occasion configuration from the received one or more paging occasion configurations (the selected at least one paging occasion configuration being associated with the determined at least one paging occasion identity) and determine at least one paging slot and at least one paging symbol within the determined at least one paging slot based on the selected at least one paging occasion configuration. Further, the processor <NUM> attempts to decode a PDCCH carrying paging DCI on the determined at least one paging symbol within the determined at least one paging slot of the determined at least one paging frame.

In one embodiment, each of the received one or more paging occasion configurations is associated with a paging occasion identity. In certain embodiments, determining the at least one paging frame is to determine a starting radio frame index of the at least one paging frame. In some embodiments, the transceiver <NUM> further receives an indication of a paging frame duration. In one embodiment, the paging frame duration is longer than one radio frame duration.

In certain embodiments, the determined paging slot is in a paging occasion, wherein the paging occasion is determined based on the paging occasion configuration selected from the one or more paging occasion configurations and comprises a plurality of paging slots. In some embodiments, the processor <NUM> selects a synchronization signal / physical broadcast channel block ("SS/PBCH block") from a plurality of SS/PBCH blocks, wherein the determined paging slot and the paging symbol within the determined paging slot are dependent on the selected SS/PBCH block.

In some embodiments, each of the one or more paging occasion configurations includes information used for determining a plurality of paging slots. In one embodiment, the information used for determining the plurality of paging slots includes information related to a starting paging slot of the plurality of paging slots. In another embodiment, the information used for determining the plurality of paging slots includes information related to a slot increment step of the plurality of paging slots. In certain embodiments, each of the one or more paging occasion configurations includes information related to a paging search space within a paging slot, wherein the paging symbol is determined based on the paging search space.

In some embodiments, the memory <NUM> stores data relating to SI delivery in a wideband carrier. For example, the memory <NUM> may store scheduling data, uplink data, logical channel mappings, and the like. In some embodiments, the memory <NUM> also stores program code and related data, such as an operating system or other controller algorithms operating on the remote unit <NUM> and one or more software applications.

In certain embodiments, the input device <NUM> may include a camera for capturing images or otherwise inputting visual data.

The output device <NUM>, in one embodiment, may include any known electronically controllable display or display device. The output device <NUM> may be designed to output visual, audible, and/or haptic signals. In some embodiments, the output device <NUM> includes an electronic display capable of outputting visual data to a user.

The transceiver <NUM> communicates with base units <NUM> of a mobile communication network. The transceiver <NUM> may include one or more transmitters <NUM> and one or more receivers <NUM>. As discussed above, the transceiver <NUM> may support one or more the network interface <NUM> for communicating with the base unit <NUM>.

<FIG> is a schematic flow chart diagram illustrating one embodiment of a method <NUM> for SI delivery in a wideband carrier, according to embodiments of the disclosure. In some embodiments, the method <NUM> is performed by a remote unit, such as the remote unit <NUM>, the UE <NUM>, the first UE <NUM>, the second UE <NUM>, the third UE <NUM>, and/or the user equipment apparatus <NUM>. In certain embodiments, the method <NUM> may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

The method <NUM> begins and acquires <NUM> a SIB for a first cell in an initial active DL BWP.

The method <NUM> includes establishing <NUM> a RRC connection with the first cell based on the acquired at least one system information block.

The method <NUM> includes transmitting <NUM> an indication of one or more SIBs necessary for UE operation to a network entity.

The method <NUM> includes switching <NUM> to a first DL BWP, wherein the first DL BWP is different from the initial active DL BWP. The method <NUM> ends.

<FIG> is a schematic flow chart diagram illustrating one embodiment of a method <NUM> for receiving a paging message, according to embodiments of the disclosure. In some embodiments, the method <NUM> is performed by a remote unit, such as the remote unit <NUM>, the UE <NUM>, the first UE <NUM>, the second UE <NUM>, the third UE <NUM>, and/or the user equipment apparatus <NUM>. In certain embodiments, the method <NUM> may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

The method <NUM> begins and receives <NUM> one or more paging occasion configurations in a system information block.

The method <NUM> includes determining <NUM> a paging frame and a paging occasion identity within the paging frame based on at least one of: a UE identity and a discontinuous reception (DRX) cycle length.

The method <NUM> includes selecting <NUM> a paging occasion configuration from the received one or more paging occasion configurations, wherein the selected paging occasion configuration is associated with the determined paging occasion identity.

The method <NUM> includes determining <NUM> a paging slot and a paging symbol within the determined paging slot based on the selected paging occasion configuration.

The method <NUM> includes decoding <NUM> a PDCCH carrying paging DCI on the determined paging symbol within the determined paging slot of the determined paging frame. The method <NUM> ends.

Disclosed herein is a first apparatus for system information delivery. The first apparatus may be a user terminal, such as the remote unit <NUM>, the UE <NUM>, the first UE <NUM>, the second UE <NUM>, the third UE <NUM>, and/or the user equipment apparatus <NUM>. The first apparatus includes a processing unit (e.g., a processor <NUM>) that acquires a system information block ("SIB") for a first cell using an initial active downlink bandwidth part ("DL BWP") and establishes a radio resource control ("RRC") connection with the first cell based on the acquired SIB. The first apparatus includes a transceiver that transmits an indication of one or more SIBs necessary for remote unit operation to a network entity and switches to a first DL BWP, wherein the first DL BWP is different from the initial active DL BWP. Note that the processing unit may control the transceiver to acquire the SIB and establish the RRC connection. Here, the indication of the one or more SIBs necessary for remote unit operation may be transmitted via higher layer signaling.

In some embodiments, the first cell is one of: a primary cell of a primary cell group and a primary secondary cell of a secondary cell group. In certain embodiments, the SIB is acquired from at least one of: broadcast signaling and an on-demand system information ("SI") request procedure. In some embodiments, the indication of the one or more SIBs necessary for remote unit operation is transmitted via at least one of: an RRC message and a media access control ("MAC") bitmap.

In some embodiments, the processing unit receives (e.g., via the transceiver) a common search space ("C-SS") configuration of the first DL BWP and the transceiver receives a paging message indicating system information modification, wherein the paging message indicating system information modification is included in a physical downlink control channel ("PDCCH") of the configured C-SS. In such embodiments, the processing unit tunes to a second DL BWP different from the first DL BWP and acquires updated system information of the first cell in the second DL BWP.

In some such embodiments, the processing unit receives (e.g., via the transceiver) an indication of a DL gap pattern of the first DL BWP and selects a DL gap pattern from the indicated DL gap pattern of the first DL BWP. Here, the selection may be based on the one or more SIBs necessary for UE operation. Moreover, the second DL BWP may be the initial active DL BWP. Further, tuning to the second DL BWP and acquiring the updated system information occurs based on the selected DL gap pattern.

In other such embodiments, the processing unit decodes a PDCCH in the configured C-SS of the first DL BWP in response to receiving the paging message and identifying a slot for receiving SI based on the decoded PDCCH. Here, acquiring updated system information of the first cell in the second DL BWP may include receiving a physical downlink shared channel ("PDSCH") carrying the one or more SIBs necessary for remote unit operation on the identified slot. In certain embodiments, the second DL BWP is different from the initial active DL BWP.

In some embodiments, the processing unit receives (e.g., via the transceiver) a configuration for a first DL gap pattern and a second DL gap pattern, wherein no C-SS is configured for the first DL BWP and tuning to a second DL BWP based on the first DL gap pattern, the second DL BWP being different than the first DL BWP. Here, the processing unit receives in the second DL BWP (e.g., via the transceiver) an indication of whether SI is modified and receives (e.g. via the transceiver) updated SI based on the second DL gap pattern in response to the SI being modified.

In such embodiments, receiving updated SI may include the apparatus tuning to a third DL BWP based on the second DL gap pattern, wherein the third DL BWP is different than both the second DL BWP and the first DL BWP. In other embodiments, the second DL BWP is same as the third DL BWP. In certain embodiments, the first DL gap pattern is used for receiving a paging message indicating SI modification in the second DL BWP. In other embodiments, the first DL gap pattern is used for receiving a first SIB in the second DL BWP, wherein the first SIB includes the indication of whether SI is modified. In various embodiments, the second DL gap pattern is based on the one or more SIBs necessary for remote unit operation.

In still other embodiments, the processing unit receives (e.g., via the transceiver) updated SI via dedicated signaling in the first DL BWP. In such embodiments, the processing unit may control the transceiver to send a request for the updated SI in response to receiving an indication of updates SI and in response to one or more essential SIBs not being provided by the network entity. Here, the network entity sends the updated SI via dedicated signaling in the first DL BWP in response to the request for updated SI.

Disclosed herein is a first method for system information delivery. The first method may be performed by a user terminal, such as the remote unit <NUM>, the UE <NUM>, the first UE <NUM>, the second UE <NUM>, the third UE <NUM>, and/or the user equipment apparatus <NUM>. The first method includes acquiring a system information block ("SIB") for a first cell using an initial active downlink bandwidth part ("DL BWP") and establishing a radio resource control ("RRC") connection with the first cell based on the acquired SIB. The first method includes transmitting an indication of one or more SIBs necessary for remote unit operation to a network entity and switching to a first DL BWP, wherein the first DL BWP is different from the initial active DL BWP. Here, the indication of the one or more SIBs necessary for remote unit operation may be transmitted via higher layer signaling.

In some embodiments, the first method further includes receiving a common search space ("C-SS") configuration of the first DL BWP, receiving a paging message indicating system information modification, wherein the paging message indicating system information modification is included in a physical downlink control channel ("PDCCH") of the configured C-SS, tuning to a second DL BWP, wherein the second DL BWP is different from the first DL BWP, and acquiring updated system information of the first cell in the second DL BWP.

In some such embodiments, the first method may include receiving an indication of a DL gap pattern of the first DL BWP and selecting a DL gap pattern from the indicated DL gap pattern of the first DL BWP based on the one or more SIBs necessary for UE operation. Here, the second DL BWP is the initial active DL BWP and tuning to the second DL BWP and acquiring the updated system information occurs based on the selected DL gap pattern.

In other such embodiments, the first method may include decoding a PDCCH in the configured C-SS of the first DL BWP in response to receiving the paging message and identifying a slot for receiving SI based on the decoded PDCCH. Here, acquiring updated system information of the first cell in the second DL BWP may include receiving a physical downlink shared channel ("PDSCH") carrying the one or more SIBs necessary for remote unit operation on the identified slot. In certain embodiments, the second DL BWP is different from the initial active DL BWP.

In some embodiments, the first method includes receiving a configuration for a first DL gap pattern and a second DL gap pattern, wherein no C-SS is configured for the first DL BWP and tuning to a second DL BWP based on the first DL gap pattern, the second DL BWP being different than the first DL BWP. Here, the first method further includes receiving, in the second DL BWP, an indication of whether SI is modified and receiving updated SI based on the second DL gap pattern in response to the SI being modified.

In such embodiments, receiving updated SI may include tuning to a third DL BWP based on the second DL gap pattern, wherein the third DL BWP is different than both the second DL BWP and the first DL BWP. In other embodiments, the second DL BWP is same as the third DL BWP. In certain embodiments, the first DL gap pattern is used for receiving a paging message indicating SI modification in the second DL BWP. In other embodiments, the first DL gap pattern is used for receiving a first SIB in the second DL BWP, wherein the first SIB includes the indication of whether SI is modified. In various embodiments, the second DL gap pattern is based on the one or more SIBs necessary for remote unit operation.

In still other embodiments, the first method includes comprising receiving updated SI via dedicated signaling in the first DL BWP. In such embodiments, the first method may include sending a request for the updated SI in response to receiving an indication of updates SI and in response to one or more essential SIBs not being provided by the network entity.

Disclosed herein is a second apparatus for receiving a paging message. The second apparatus also may be a user terminal, such as the remote unit <NUM>, the UE <NUM>, the first UE <NUM>, the second UE <NUM>, the third UE <NUM>, and/or the user equipment apparatus <NUM>. The second apparatus includes a processing unit (e.g., a processor <NUM>) and a transceiver (e.g. transceiver <NUM>) that receives one or more paging occasion configurations in a system information block. The processing unit determines a paging frame and a paging occasion identity within the paging frame based on at least one of: a UE identity and a discontinuous reception cycle length and selects a paging occasion configuration from the received one or more paging occasion configurations, wherein the selected paging occasion configuration is associated with the determined paging occasion identity. Moreover, the processing unit determines a paging slot and a paging symbol within the determined paging slot based on the selected paging occasion configuration and decodes a physical downlink control channel ("PDCCH") carrying paging downlink control information ("DCI") on the determined paging symbol within the determined paging slot of the determined paging frame.

In certain embodiments, each of the received one or more paging occasion configurations is associated with a paging occasion identity. In some embodiments, determining the paging frame comprises determining a starting radio frame index of the paging frame. In certain embodiments, the transceiver further receives an indication of a paging frame duration. In various embodiments, the paging frame duration is longer than one radio frame duration.

In certain embodiments, the determined paging slot is in a paging occasion, wherein the paging occasion is determined based on the paging occasion configuration selected from the one or more paging occasion configurations and comprises a plurality of paging slots. In some embodiments, the processing unit further selects a synchronization signal / physical broadcast channel block ("SS/PBCH block") from a plurality of SS/PBCH blocks, wherein the determined paging slot and the paging symbol within the determined paging slot are dependent on the selected SS/PBCH block.

Disclosed herein is a second method for receiving a paging message. The second method may be performed by a user terminal, such as the remote unit <NUM>, the UE <NUM>, the first UE <NUM>, the second UE <NUM>, the third UE <NUM>, and/or the user equipment apparatus <NUM>. The second method includes receiving one or more paging occasion configurations in a system information block and determining a paging frame and a paging occasion identity within the paging frame based on one or more of: a UE identity and a discontinuous reception cycle length. The second method includes selecting a paging occasion configuration from the received one or more paging occasion configurations and determining a paging slot and a paging symbol within the determined paging slot based on the selected paging occasion configuration, wherein the selected paging occasion configuration is associated with the determined paging occasion identity. The second method also includes decoding a physical downlink control channel ("PDCCH") carrying paging downlink control information ("DCI") on the determined paging symbol within the determined paging slot of the determined paging frame.

In some embodiments, each of the received one or more paging occasion configurations is associated with a paging occasion identity. In certain embodiments, determining the paging frame comprises determining a starting radio frame index of the paging frame. In some embodiments, the second method further includes receiving an indication of a paging frame duration. In certain embodiments, the paging frame duration is longer than one radio frame duration.

In certain embodiments, the determined paging slot is in a paging occasion, wherein the paging occasion is determined based on the paging occasion configuration selected from the one or more paging occasion configurations and comprises a plurality of paging slots. In some embodiments, the second method further includes selecting a synchronization signal / physical broadcast channel block ("SS/PBCH block") from a plurality of SS/PBCH blocks, wherein the determined paging slot and the paging symbol within the determined paging slot are dependent on the selected SS/PBCH block.

Embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is indicated by the appended claims.

Claim 1:
A method (<NUM>) performed by a user equipment, UE, the method (<NUM>) comprising:
acquiring (<NUM>) a system information block "SIB" for a first cell defined by a base station using an initial active downlink bandwidth part "DL BWP";
establishing (<NUM>) a radio resource control "RRC" connection with the first cell based on the acquired SIB;
receiving (<NUM>) a configuration of at least one DL BWP of the first cell;
transmitting (<NUM>) an indication of one or more SIBs necessary for UE operation to the base station; and
switching to an active DL BWP among the at least one DL BWP configured by the base station;
determining (<NUM>) whether the active DL BWP is the same as the initial DL BWP;
if the active DL BWP is the same as the initial DL BWP, monitoring (<NUM>) system information change and continues acquiring the updated system information in the initial DL BWP;
if the active DL BWP is different from the initial DL BWP, receiving configuration of a DL gap pattern, monitoring (<NUM>) for an indication of updated system information and acquires the updated system information during a configured DL gap.