Methods and apparatus for processing system information in wireless communication systems

Abstract

This disclosure relates to a communication method and system for aggregating communication between a 5G communication system supporting higher data rates than 4G systems and Internet of Things (IoT) technology. This disclosure can be applied to smart services based on 5G communication technology and IoT-related technologies, such as smart homes, smart buildings, smart cities, smart cars, connected cars, healthcare, digital education, smart retail, security, and safety services. Therefore, embodiments herein disclose a method for a UE (100) to process an SI in an RRC connection mode within a wireless communication system (1000). The method includes determining that the UE (100) requires at least one SIB from a plurality of SIBs indicated in SI scheduling information broadcast by the network (200). The method includes determining from the plurality of SIBs that the UE (100) does not have the required stored SIB or that a stored version of the required SIB exists but the stored version of the required SIB is invalid. Furthermore, the method includes checking, based on network configuration, whether the UE (100) is permitted to send an SI request. In addition, the method includes sending an SI request for the required SIB in response to a network configuration check that the UE (100) is allowed to send an SI request.

Description

Technical Field

[0001] This disclosure relates to wireless communication systems, and more specifically to a method and apparatus for transmitting and receiving system information. Background Technology

[0002] To meet the increased demand for wireless data services since the deployment of 4G communication systems, efforts have been focused on developing an improved 5G or near-5G communication system. Therefore, 5G or near-5G communication systems are also referred to as "super-4G networks" or "post-LTE systems." 5G communication systems are considered to be implemented in higher frequency (millimeter wave) bands (e.g., the 60GHz band) to achieve higher data rates. To reduce radio wave propagation loss and increase transmission distance, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive MIMO technologies are discussed in 5G communication systems. Furthermore, in 5G communication systems, development is underway for system network improvements based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, coordinated multipoint (CoMP), and receiver interference cancellation. In 5G systems, hybrid FSK and FQAM modulation and sliding window superposition coding (SWSC) have been developed as advanced coding and modulation (ACM), as well as filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) as advanced access technologies.

[0003] The Internet, a human-centric network in which humans generate and consume information, has now evolved into the Internet of Things (IoT), in which distributed entities (such as things) exchange and process information without human intervention. The Internet of Everything (IoE) has emerged, a combination of IoT technology and big data processing technology connected to cloud servers. Because the concrete implementation of IoT requires technological elements such as sensing technology, wired / wireless communication and network infrastructure, service interface technology, and security technology, recent research has focused on sensor networks, machine-to-machine (M2M) communication, and machine-type communication (MTC). Such IoT environments can provide intelligent Internet technology services that create new value for human life by collecting and analyzing data generated between connected things. IoT can be applied to a variety of fields through the convergence and combination of existing information technology (IT) with various industrial applications, including smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart appliances, and advanced medical services.

[0004] Therefore, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine-type communication (MTC), and machine-to-machine (M2M) communication can be implemented using beamforming, MIMO, and array antennas. Cloud radio access network (RAN) applications, as a big data processing technology, can also be seen as an example of the convergence between 5G and IoT technologies. Summary of the Invention

[0005] Technical issues

[0006] In NR's 3GPP Release 15 standard, on-demand System Information (SI) requests are supported by UEs in idle and inactive states. Release 15 UEs do not support on-demand SI requests in connected states.

[0007] Solution to the problem

[0008] In one embodiment, a method performed by a user equipment (UE) in a wireless communication system includes: receiving from a base station scheduling information of system information (SI) associated with a plurality of system information blocks (SIBs); identifying that the UE requires at least one of the plurality of SIBs indicated in the scheduling information; determining that the UE does not have the required stored SIB, or that a stored version of the required SIB exists but the stored version of the required SIB is invalid; and sending an SI request for the required SIB to the base station.

[0009] In another embodiment, a user equipment (UE) in a wireless communication system includes: a transceiver; and a processor configured to: receive, via the transceiver, scheduling information of system information (SI) associated with a plurality of system information blocks (SIBs) from a base station; identify at least one SIB among the plurality of SIBs indicated in the scheduling information that the UE requires; determine that the UE does not have the required stored SIB, or that a stored version of the required SIB exists but the stored version of the required SIB is invalid; and send an SI request for the required SIB to the base station via the transceiver.

[0010] Beneficial effects of the invention

[0011] The main objective of the embodiments described herein is to provide a method for a UE to process system information in a wireless communication system via an RRC connection mode. Attached Figure Description

[0012] The following discussion Figures 1 to 6The various embodiments used to describe these principles of the disclosure in this patent document are merely illustrative and should not be construed in any way as limiting the scope of the disclosure. Those skilled in the art will understand that the principles of this disclosure can be implemented in any suitably arranged system or apparatus.

[0013] The invention is illustrated in the accompanying drawings, in which the same reference numerals indicate corresponding portions in the figures. Embodiments herein will be better understood from the following description with reference to the accompanying drawings, in which:

[0014] Figure 1 This is a block diagram illustrating a UE for processing system information in a wireless communication system according to embodiments disclosed herein;

[0015] Figure 2 This is a flowchart illustrating a method for processing SI in a wireless communication system according to embodiments disclosed herein;

[0016] Figures 3 to 5 This is an exemplary flowchart illustrating various operations for triggering an SI request in an RRC_CONNECTED connection according to embodiments disclosed herein; and

[0017] Figure 6 This is a flowchart illustrating an embodiment as disclosed herein, wherein, for the case where the active BWP is not configured with a public search space, the UE sends an SI request if the onDemandSibRequest flag included in the RRCReconfiguration message is set to true. Detailed Implementation

[0018] It may be advantageous to define certain words and phrases used throughout this patent document: the term “comprising” and its derivatives mean including but not limited to; the term “or” is inclusive, meaning and / or; the phrases “associated with” and “associated with” and their derivatives may mean including, contained within, interconnected with, including, included in, connected to or connected to, coupled to or coupled to, capable of communicating with, cooperating with, interleaved, parallel, proximate, bound to or bound to, having, possessing the nature of, etc.; and the term “controller” means any device, system, or part thereof that controls at least one operation, which may be implemented in hardware, firmware, or software, or at least a combination of two thereof. It should be noted that the functionality associated with any particular controller may be centralized or distributed, local or remote.

[0019] Furthermore, the various functions described below can be implemented or supported by one or more computer programs, each computer program being formed by computer-readable program code and embodied in a computer-readable medium. The terms "application program" and "program" refer to one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, instances, associated data, or portions thereof suitable for implementation in appropriate computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of media accessible by a computer, such as read-only memory (ROM), random access memory (RAM), hard disk drive, optical disc (CD), digital video disc (DVD), or any other type of storage. "Non-transitory" computer-readable media excludes wired, wireless, optical, or other communication links that transmit transient electrical signals or other transient signals. Non-transitory computer-readable media includes media capable of permanently storing data, as well as media capable of storing data and subsequently rewriting it, such as rewritable optical discs or erasable memory devices.

[0020] Throughout this patent document, definitions of certain words and phrases are provided, and those skilled in the art will understand that, in many instances (if not most), such definitions apply to the past and future use of the words and phrases so defined.

[0021] The embodiments described herein, along with their various features and advantageous details, are illustrated in the accompanying drawings and described in detail below. Descriptions of well-known components and processing techniques have been omitted to avoid unnecessarily obscuring the embodiments herein. Furthermore, the various embodiments described herein are not necessarily mutually exclusive, as some embodiments may be combined with one or more other embodiments to form new embodiments. The term "or" as used herein means non-exclusive, or unless otherwise specified. The examples used herein are merely to facilitate understanding of how the embodiments described herein can be practiced, and further to enable those skilled in the art to practice the embodiments described herein. Therefore, these examples should not be construed as limiting the scope of the embodiments described herein.

[0022] As is conventional in the art, embodiments can be described and illustrated based on blocks that perform one or more described functions. These blocks (which may be referred to herein as units or modules, etc.) are physically implemented by analog and digital circuitry, such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuitry, etc., and may optionally be driven by firmware and software. The circuitry may be embodied, for example, in one or more semiconductor chips, or on a substrate support such as a printed circuit board. The circuitry constituting a block may be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuitry), or by a combination of dedicated hardware for performing some functions of the block and the processor, and a processor for performing other functions of the block. Without departing from the scope of the invention, each block of an embodiment may be physically divided into two or more interacting discrete blocks. Similarly, without departing from the scope of the invention, the blocks of an embodiment may be physically combined into more complex blocks.

[0023] The accompanying drawings are provided to aid in the easy understanding of the various technical features, and it should be understood that the embodiments presented herein are not limited to the drawings. Therefore, this disclosure should be construed as extending to any changes, equivalents, and substitutions other than those specifically listed in the drawings. While the terms “first,” “second,” etc., may be used herein to describe various elements, these elements should not be limited by these terms. These terms are generally used only to distinguish one element from another.

[0024] In recent years, several broadband wireless technologies have been developed to meet the growing number of broadband users and provide more and better applications and services. Second-generation wireless communication systems have been developed to provide voice services while ensuring user mobility. Third-generation wireless communication systems support not only voice services but also data services. Fourth-generation wireless communication systems have been developed in recent years to provide high-speed data services. However, current fourth-generation wireless communication systems lack the resources to meet the increasing demand for high-speed data services; therefore, fifth-generation wireless communication systems are under development to meet this growing demand and support ultra-reliable and low-latency applications.

[0025] Fifth-generation (5G) wireless communication systems will be implemented not only in lower frequency bands but also in higher frequency (mmWave) bands, such as the 10 GHz to 100 GHz band, to achieve higher data rates. To mitigate radio wave propagation loss and increase transmission distance, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and large antenna technology are considered in the design of 5G wireless communication systems. Furthermore, 5G wireless communication systems are expected to address diverse use cases with significantly different requirements in terms of data rate, latency, reliability, and mobility. However, the air interface design of 5G wireless communication systems will be flexible enough to serve UEs with considerably different capabilities depending on the use case and the market segment of the user equipment (UE) catering to end customers. For example, the use cases for 5G wireless communication systems are expected to address issues such as enhanced mobile broadband (eMBB), massive machine-type communication (m-MTC), and ultra-reliable low latency communication (URLL). eMBB requirements (such as tens of Gbps data rates, low latency, and high mobility) address the market segment representing regular wireless broadband subscribers who actively require internet connectivity anytime, anywhere. m-MTC requirements (such as extremely high connection density, infrequent data transfer, ultra-long battery life, and low-mobility addresses) address the market segment representing the connectivity of billions of devices envisioned for the Internet of Things (IoT) / Internet of Everything (IoE). URLL requirements (such as extremely low latency, extremely high reliability, and variable mobility) address the market segment representing industrial automation applications (i.e., vehicle-to-vehicle / vehicle-to-infrastructure communication, which is foreseeable as one of the driving forces behind autonomous vehicles).

[0026] In fourth-generation wireless communication systems, such as in Long Term Evolution (LTE), Enhanced Node Bs (eNBs) or base stations broadcast system information within the cell. This system information is constructed into a set of Master Information Blocks (MIBs) and System Information Blocks (SIBs). The MIB consists of the System Frame Number (SFN), downlink system bandwidth, and Physical Hybrid Automatic Repeat Request (ARQ) Feedback Indicator Channel (PHICH) configuration. The MIB is transmitted every 40 ms. The MIB is repeated every 10 ms, with the first transmission occurring in subframe #0 when SFN mod 4 equals zero. The MIB is transmitted on the Physical Broadcast Channel (PBCH). System Information Block Type 1 (SIB1) carries the cell identifier, tracking area code, cell prohibition information, value flags (common to all scheduling units), and other scheduling information for the SIBs. SIB1 is transmitted every 80 ms in subframe #5 when SFN mod 8 equals zero. SIB1 is repeated in subframe #5 when SFN mod 2 equals zero. SIB 1 is transmitted on the Physical Downlink Shared Channel (PDSCH). Other SIBs (SIB 2 to SIB 21) are transmitted in the SI message, with SIB 1 indicating the scheduling information for the SIB. Further, in the LTE system, when the UE hands over from the source eNB to the target eNB, the target eNB provides the UE with a specific subset of the parameters of the target cell's MIB, SIB 1, and SIB 2 in the handover command message via dedicated signaling. The RACH configuration and physical configuration of the target cell, i.e., the radioResourceConfigCommon, are provided to the UE in the mobility control information (mobilitycontrolinfo) via dedicated signaling. Similarly, if the UE is operating in dual-connectivity mode, the system information of the secondary eNB (SeNB) or secondary cell group (SCG) cell, i.e., the SCG cell's RACH configuration and physical configuration, i.e., the radioResourceConfigCommonPSCell, are provided to the UE via dedicated signaling. Another scenario for providing dedicated system information to the UE is with a redirection at release, where the system information in the candidate cell's SI, CellInforGERAN, and the utra-BCCH-Container in CellInfoUTRA for GSM Edge Radio Access Network (GERAN) and Universal Mobile Telecommunications System (UMTS) are provided to the UE in the RRC Connection Release message, respectively.

[0027] For fifth-generation wireless communication systems, i.e., NR systems, in a 5G Node B (i.e., gNB), system information is delivered either via broadcast or upon UE request (i.e., on-demand SI request). In fifth-generation wireless communication systems, information is divided into Minimal SI (MSI) and other SIs (OSI). Similar to LTE system information, other SIs can be constructed into a set of SI blocks (SIBs).

[0028] The Minimum SI is broadcast periodically. Other SIs can be broadcast periodically upon UE request or provided on demand. The Minimum SI includes basic information required for initial cell access and information for periodically obtaining any other SIs broadcast or provided on demand. The Minimum SI includes at least the SFN, a list of Public Land Mobile Networks (PLMNs), the cell ID, cell camping parameters, and RACH parameters. If the network allows an on-demand mechanism, parameters required to request other SI blocks (such as the requested RACH preamble if needed) are also included in the MSI. The MSI includes at least the MIB and SIB1, which cover parameters similar to those in the LTE MIB, SIB1, and SIB2.

[0029] The scheduling information in the MSI includes an indicator that the relevant SI block is broadcast periodically or provided on demand. Scheduling information for other SIs includes SIB type, validity information, SI periodicity, and SI window information. Scheduling information for other SIs is provided regardless of whether they are broadcast periodically. If the minimum SI indicator SIB is not broadcast (i.e., the SIB is provided on demand), the UE does not assume that the SIB is broadcast periodically in each SI period within its SI window. Therefore, the UE can send an SI request to receive the SIB. For other on-demand SIs, the UE can request one or more SI blocks or all SI blocks in a single request.

[0030] NR systems can be deployed in standalone (SA) operating mode (i.e., the UE is only connected to NR) or non-standalone operating mode (i.e., the UE is connected to both LTE and NR, similar to LTE dual connectivity, meaning the radio connection includes a primary cell group controlled by the primary node and a secondary cell group controlled by the secondary node). In standalone operating mode, MSI is always broadcast periodically, while OSI can be provided on demand or broadcast periodically depending on the network (or base station) implementation. For non-standalone operating mode where the LTE eNB is the primary node and the NR gNB is the secondary node, system information for the secondary node's cell or NR SCG cell involves dedicated transmissions of SIs when an SCG cell is added or during SCG changes. In this scenario, the network pushes the relevant SIs for the NR SCG cell because non-standalone operating mode does not support the on-demand concept of requesting relevant SIs. In the 3GPP Release 15 standard for NR, on-demand system information (SI) requests are supported by UEs in idle and inactive states. UEs in Release 15 do not support on-demand SI requests in connected states.

[0031] Regardless of whether the operating mode is standalone or non-standalone, there are certain UE requirements for storing acquired SIs. The UE should store relevant SIs acquired from the currently camped / serving cell. Storing SIs other than those from the currently camped / serving cell depends on the UE implementation. The UE can store multiple versions of SIs based on its storage capacity. The UE can indicate its storage capacity to the network. Unlike LTE, some NR SIs acquired / provided from dedicated signaling in one cell may also be valid in another cell; that is, the information may be valid in an area covered by multiple cells. As with LTE, the version of the SI acquired and stored by the UE remains valid only for a specific period. The UE can use such a stored SI version, for example, after cell reselection, upon returning from outside coverage, after an SI change indication, or after an SCG change. In typical UE implementations, SI storage management is often referred to as garbage collection, where the longest-stored information is typically discarded. Stored SIs generally do not change during RRC connections unless garbage collection is invoked upon receiving a new SI, the validity timer associated with the stored SI has expired, or the so-called system information value tag or system configuration index associated with the stored SI has changed.

[0032] In NR systems, the network (or base station) should be able to provide the required SI in the connected state under the same UE mobility conditions as in LTE (changing the PCell, adding the SCell). Furthermore, if the UE's active bandwidth portion (BWP) does not have a common search space configured, as shown in [Table 1], it may be beneficial for the network to provide the required SI to the connected UE.

[0033] [Table 1]

[0034]

[0035] With only the necessary parts of the MSI (some parameters of MIB and SIB1) provided, during PCell mobility (i.e., handover), the UE can retrieve the lost parts after handover by reading the MIB and SIB1 from the broadcast (if the UE has a common search space configured). If the UE's active BWP is not configured with a common search space, then the UE should ideally always transmit the entire MIB (except SFN) and SIB1 to the UE in a dedicated manner. This further avoids the tedious work of determining the essential fields (fields urgently needed for UE mobility). The NR system has introduced support for dedicated SI transmission of reconfiguration messages. The SI can be provided in the same message commanding UE mobility, i.e., provided to the NR reconfiguration message, just like the handover command message in LTE. For UEs in RRC_CONNECTED, the network can provide system information via dedicated signaling using the RRCReconfiguration message, for example, if the UE has an active BWP and is not configured to monitor system information or the common search space for paging. The entire SIB1 can be provided to the UE by the network using dedicated signaling with the field `dedicatedSIB1-Delivery` included in the RRC reconfiguration message. Any other SIBs can be provided to the UE by the network using dedicated signaling with the field `dedicatedSystemInformationDelivery` included in the RRC reconfiguration message. In Release 16 of the NR standard, new features such as Vehicle-to-Everything (V2X) and location services are introduced, and therefore new SIBs associated with these features will be introduced. UEs in the RRC_connected state will require these new SIBs. Therefore, UEs in the RRC_connected state in Release 16 also support the on-demand concept of SI requests. The patent disclosure discloses the following aspects related to UEs in the RRC_connected state supporting SI requests:

[0036] 1. If the UE's active BWP is not configured with a common search space, the UE will send an SI request for the required SIB in the RRC_connected state by only checking the scheduling information (schedulinginfo) in the stored SIB1.

[0037] 2. If a common search space is configured for the UE's active BWP, and if an SIB in the RRC_connected state is required at any time during modification period N, the UE checks the scheduling information in the stored SIB1 obtained at the start of modification N to determine whether the UE can trigger an SI request.

[0038] 3. If a common search space is configured for the UE's active BWP, and if the SIB in the RRC_connected state is required at any time during the modification period N+1, then the UE is allowed to reacquire SIB1 if the stored SIB1 was acquired at the start of modification N or earlier.

[0039] 4. UE behavior is defined by the setting of the si-broadcaststatus bit in SIB1 and the status of FLAG (i.e., the ondemandSibRequest sent in the RRC reconfiguration message) to trigger the SI request of RRC_connection state for the UE.

[0040] Therefore, embodiments of this document disclose a method for a UE to process system information in a wireless communication system via RRC connection mode. The method includes the UE determining at least one SIB from a plurality of SIBs indicated in SI scheduling information broadcast by the network. The method includes the UE determining from the plurality of SIBs that it does not have the required stored SIB or that a stored version of the required SIB exists but the stored version of the required SIB is invalid. Furthermore, the method includes the UE checking, based on network configuration, whether it is permitted to send an SI request. Additionally, the method includes, in response to checking that the network configuration permits the UE to send an SI request, the UE sending an SI request for the required SIB.

[0041] In one embodiment, the UE determines that it needs to acquire at least one of a plurality of SIBs indicated in the scheduling information broadcast by the network, including: the UE determining that the active BWP with a common search space is configured for the UE, the UE detecting that SIB1 has not been acquired in the current modification period, and the UE acquiring SIB1 from the broadcast in response to detecting that SIB1 has not been acquired in the current modification period.

[0042] In one embodiment, obtaining SIB1 from a broadcast includes the UE storing the SIB1 obtained from the broadcast, and the UE checking the SI scheduling information in the stored SIB1 and determining that the setting of the si-BroadcastStatus bit is associated with the desired SIB.

[0043] In one embodiment, obtaining a required SIB from a broadcast in response to determining that an active BWP with a common search space has been configured for the UE includes: if the si-broadcast status bit associated with the required SIB is set to broadcast status in stored SIB1, the UE obtains the required SIB from the broadcast.

[0044] In one embodiment, the UE sending an SI request for a desired SIB includes the UE determining that an active BWP with a common search space is configured for the UE, the UE checking the SI scheduling information in the stored SIB1 and determining the setting of the si-broadcast status bit associated with the desired SIB, and if the si-broadcast status bit associated with the desired SIB in the stored SIB1 is set to a non-broadcast state and the UE is allowed to send an SI request based on the network configuration, the UE sending an SI request indicating the desired SIB.

[0045] In one embodiment, the UE sending an SI request for a required SIB includes the UE determining that an active BWP without a common search space is configured for the UE, the UE checking the SI scheduling information stored in SIB1, and if the network configuration allows the UE to send an SI request, then the UE sending an SI request indicating the required SIB.

[0046] In one embodiment, network configuration is received from the network by the UE receiving an RRC reconfiguration message from the network, the RRC reconfiguration message including an indication of one of the following: whether the UE is allowed to send an SI request in RRC connection mode, and whether the UE is not allowed to send an SI request in RRC connection mode.

[0047] Therefore, embodiments of this document disclose a UE for processing SI in a wireless communication system including a UE in RRC connection mode and a network. The UE includes a processor coupled to a memory. The processor is configured to determine that the UE needs at least one SIB from a plurality of SIBs indicated in SI scheduling information broadcast by the network. Furthermore, the processor is configured to determine from the plurality of SIBs that the UE does not have the required stored SIB or that a stored version of the required SIB exists but the stored version of the required SIB is invalid. Furthermore, the processor is configured to check whether the UE is permitted to send an SI request based on network configuration. Furthermore, the processor is configured to send an SI request for the required SIB in response to checking that the UE is permitted to send an SI request based on network configuration.

[0048] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and accompanying drawings. However, it should be understood that the following description is given as illustrative rather than limiting, although preferred embodiments and their many specific details are indicated. Many variations and modifications can be made within the scope of the embodiments herein without departing from the spirit of the embodiments herein, and the embodiments herein include all such modifications.

[0049] The embodiments of this document implement a method for a UE to process SI (System Injection) in a wireless communication system via RRC (Relational Routing Control) connection mode. The method includes the UE determining at least one SIB (System Injection Block) from a plurality of SIBs indicated in SI scheduling information broadcast by the network. The method includes the UE determining from the plurality of SIBs that it does not have the required stored SIB, or that a stored version of the required SIB exists but the stored version of the required SIB is invalid. Furthermore, the method includes the UE checking, based on network configuration, whether sending an SI request is permitted. Additionally, the method includes, in response to checking that the network configuration permits the UE to send an SI request, the UE sending an SI request for the required SIB.

[0050] Now refer to the accompanying drawings, and more specifically to... Figures 1 to 6 Similar reference numerals are consistently used to denote corresponding features in all figures, wherein preferred embodiments are shown.

[0051] Figure 1 Various hardware components of a UE (100) for processing SI in a wireless communication system (1000) according to embodiments disclosed herein are shown. The wireless communication system (1000) includes the UE (100) and a network (200). The UE (100) may be, for example, but not limited to, a cellular phone, a smartphone, a personal digital assistant (PDA), a tablet computer, a laptop computer, an Internet of Things (IoT), a virtual reality device, and an immersive system. The UE (100) includes a processor (110), a communicator (120), a memory (130), and an SI controller (140). The processor (110) is coupled to the communicator (120), the memory (130), and the SI controller (140).

[0052] The SI controller (140) is configured to determine at least one of a plurality of SIBs indicated in the SI scheduling information broadcast by the network (200) that the UE (100) needs. In one embodiment, the determination is made by determining that an active BWP with a common search space is configured for the UE (100), detecting that SIB1 has not been acquired in the current modification period, and acquiring SIB1 from the broadcast in response to detecting that SIB1 has not been acquired in the current modification period.

[0053] In one embodiment, SIB1 is obtained from a broadcast, the obtained SIB1 is stored, and the SI scheduling information in the stored SIB1 is checked to determine the setting of the si-broadcast status bit associated with the desired SIB. In one embodiment, in response to determining that an active BWP with a common search space is configured for the UE (100), obtaining the desired SIB from the broadcast includes: if the si-broadcast status bit associated with the desired SIB is set to broadcast status in the stored SIB1, obtaining the desired SIB from the broadcast.

[0054] Furthermore, the SI controller (140) is configured to determine from a plurality of SIBs that the UE (100) does not have the required stored SIB or that a stored version of the required SIB exists but the stored version of the required SIB is invalid. Additionally, the SI controller (140) is configured to check whether the UE (100) is permitted to send SI requests based on network configuration. Network configuration is received from the network (200) by receiving an RRC reconfiguration message from the network (200) including an indication of one of the following: whether the UE (100) is permitted to send SI requests in RRC connection mode, and whether the UE (100) is not permitted to send SI requests in RRC connection mode.

[0055] Furthermore, the SI controller (140) is configured to send an SI request for a desired SIB in response to detecting that the UE (100) is allowed to send an SI request based on network configuration. In one embodiment, the SI request for a desired SIB is sent by: determining that an active BWP with a common search space is configured for the UE (100), checking the SI scheduling information in the stored SIB1 and determining the setting of the si-broadcast status bit associated with the desired SIB, and if the si-broadcast status bit associated with the desired SIB in the stored SIB1 is set to a non-broadcast state and the UE (100) is allowed to send an SI request based on network configuration, sending an SI request indicating the desired SIB. In another embodiment, the SI request for a desired SIB is sent by: determining that an active BWP without a common search space is configured for the UE (100), checking the SI scheduling information in the stored SIB1, and if the UE (100) is allowed to send an SI request based on network configuration, sending an SI request indicating the desired SIB.

[0056] The processor (110) is configured to execute instructions stored in memory (130) and perform various processes. The communicator (120) is configured to communicate internally between internal hardware components and to communicate with external devices via one or more networks.

[0057] The memory (130) also stores instructions to be executed by the processor (110). The memory (130) may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard disks, optical disks, floppy disks, flash memory, or various forms of electrically programmable memory (EPROM) or electrically erasable programmable memory (EEPROM). Furthermore, in some examples, the memory (130) may be considered a non-transitory storage medium. The term "non-transitory" may mean that the storage medium is not specifically implemented in a carrier wave or a propagated signal. However, the term "non-transitory" should not be construed as meaning that the memory (130) is immovable. In some examples, a non-transitory storage medium may store data that may change over time (e.g., in random access memory (RAM) or a cache).

[0058] although Figure 1 Hardware components of the UE (100) are shown, but it should be understood that other embodiments are not limited thereto. In other embodiments, the UE (100) may include fewer or more components. Furthermore, the designations or names of components are for illustrative purposes only and do not limit the scope of this disclosure. One or more components may be combined to perform the same or substantially similar functions to process SI in the wireless communication system (1000).

[0059] Figure 2 This is a flowchart (S200) illustrating a method for processing SI in a wireless communication system (1000) according to embodiments disclosed herein. Operations (S202 to S208) are performed by a processor (110).

[0060] At S202, the method includes determining that the UE (100) requires at least one of a plurality of SIBs indicated in the SI scheduling information broadcast by the network (200). At S204, the method includes determining from the plurality of SIBs that the UE (100) does not have the required stored SIB or that a stored version of the required SIB exists but the stored version of the required SIB is invalid. At S206, the method includes checking whether the UE (100) is allowed to send an SI request based on network configuration. At S208, the method includes sending an SI request for the required SIB in response to checking that the UE (100) is allowed to send an SI request based on network configuration.

[0061] Method 1: SI requests in the connected state are based solely on checking scheduling information.

[0062] Whenever the UE (100) wants to receive an SIB (e.g., location is activated, V2X is activated, etc.) (which may happen at any time), triggering of an SI request in the connected state should be possible. In the Radio Resource Control (RRC) specification, version 15, TS38.331, triggering of an SI request is determined when the UE (100) performs SIB1 processing, specifically clause 5.2.2.4.2 entitled “Actions when receiving SIB1”. This is used to determine the SI request when the UE (100) is in an idle / inactive state. However, when the UE (100) is in the connected state, the UE's active BWP may not have a common search space configured, so when the UE (100) determines to acquire an SIB (e.g., an SIBx associated with V2X), the UE (100) cannot reacquire SIB1 from the broadcast. Furthermore, if the UE BWP is not configured with a common search space, the UE (100) can argue whether the gNB always provides SIB1 to the UE (100) in a dedicated manner whenever the gNB changes the broadcast status bit. The gNB will not do so if the rest of the SIB1 content is not updated and only the broadcast status bit has changed. In this case, the UE (100) should be able to trigger the SI request procedure in Clause 5.2.2.3.3 of TS 38.331, entitled “Request for System Information on Demand,” without having to reacquire the SIB1 and check the contents of the si-SchedulingInfo field in the stored SIB1 ignoring the broadcast status bit. The broadcast status bit is irrelevant because the gNB cannot broadcast the requested SIB after receiving the SI request from the UE (100) since the active BWP is not configured with a common search space. The gNB will deliver the requested SIB in dedicated RRC signaling after receiving the SI request from the UE (100). The following clause needs to be introduced in version 16 of the RRC specification to allow the UE (100) to send an SI request without reacquiring SIB1 and by checking the contents of the si-scheduling information field in the stored SIB1 when the active BWP is not configured with a common search space.

[0063] 5.2.2.3.3x Actions when SIB needs to be obtained in a connected state

[0064] UE(100) should:

[0065] 1> If the UE (100) is in an RRC connection, the active BWP has a common search space that is not configured by the search space SIB1 and the paging search space, and the UE (100) does not store a valid version of a required SIB that conforms to sub-clause 5.2.2.2.1 in one or more required SIBs that conform to sub-clause 5.2.2.2.

[0066] 2> For SI messages that contain at least one required SIB based on the si-scheduling information stored in SIB1.

[0067] 3> Trigger a request to retrieve the SI message as defined in sub-clause 5.2.2.3.3.

[0068] Alternatively, UE(100) should:

[0069] 1> If the UE (100) is in an RRC_ connection, the active BWP has a common search space that is not configured by the search space SIB1 and the paging search space, and the UE (100) does not store a valid version of a SIB that conforms to sub-clause 5.2.2.2.1 in one or more required SIBs that conform to sub-clause 5.2.2.2.

[0070] 2> For the required SIB that is mapped to the SI message based on the si-scheduling information stored in SIB1.

[0071] 3> Trigger a request to obtain the required SIB as defined in sub-clause 5.2.2.3.3.

[0072] Alternatively, UE(100) should:

[0073] 1> If the UE (100) is in an RRC_ connection, the active BWP has a common search space that is not configured by the search space SIB1 and the paging search space, and the onDemandSibRequest is set to true (TRUE), and the UE (100) does not store a valid version of a SIB that conforms to sub-clause 5.2.2.2.1 from one or more required SIBs that conform to sub-clause 5.2.2.2.

[0074] 2> For SI messages that contain at least one required SIB based on the si-scheduling information stored in SIB1.

[0075] 3> Trigger a request to retrieve the SI message as defined in sub-clause 5.2.2.3.3.

[0076] The OnDemandSibRequest indicator is included in the RRC reconfiguration message and indicates that the UE (100) is allowed to send an SI request in the connected state. In one embodiment, the OnDemandSibRequest indicator may be included in SIB1.

[0077] If the on-demand Sib request indicator contained in SIB1 indicates FALSE, that is, the UE (100) cannot send an SI request in the RRC_connected state, then the UE (100) will obtain the SIB required in the connected state in advance when the UE (100) is in the idle / inactive state.

[0078] If the On-Demand Sib Request Indicator included in the RRC Reconfiguration Message indicates false, meaning that the UE (100) cannot send an SI request in the RRC_connected state, then the UE (100) will obtain the SIB required in the connected state when the UE (100) transitions to idle / inactive (regardless of whether the service is active).

[0079] This method can be used to trigger an SI request to obtain an SIB in the RRC_connected state when the UE's active BWP is not configured with a common search space, such as... Figure 3 As depicted in [the text]. In one example, such as [example]... Figure 3 As shown, at S302, the method includes detecting that the UE (100) is in RRC_connection mode. At S304, the method includes determining that the UE's active BWP is not configured with a common search space. At S306, the method includes determining that the UE (100) has not stored a SIB or that the version of the desired SIB stored is invalid. At S308, the method includes determining the si-scheduling information in the stored SIB1 to determine at least one desired SIB. At S310, the method includes sending an SI request for the desired SIB.

[0080] Alternatively, since the UE's active BWP does not have a public search space configured, it cannot broadcast the required SIBs. The gNB proactively provides the UE (100) with dedicated signaling the SIBs identified as required in the connected state and supported in the cell. If the network (200) supports the proactive delivery of SIBs identified as required in the connected state (during the UE (100) transition from idle / inactive to connected and PCell mobility), the UE (100) does not need to make an SIB request in the RRC_connected state.

[0081] Method 2: SI requests in the connected state are based on checking scheduling information and broadcast status bits.

[0082] In the RRC specification of version 15, namely TS 38.331, the triggering of the SI request is determined when the UE (100) performs SIB1 processing, specifically clause 5.2.2.4.2 entitled "Actions when receiving SIB1". This is used to determine the SI request when the UE (100) is in an idle / inactive state and the connection state when the UE's active BWP is configured with a common search space, so that when the UE (100) is processing the received SIB1, the UE can determine to obtain the SIB (e.g., SIBx associated with V2X) by performing clause 5.2.2.4.2.

[0083] For example, suppose that at time t1, when UE (100) acquires SIB1 (broadcast or dedicated), the scheduling information includes V2X SIB-related information. Since UE (100) is not interested in V2X when executing clause 5.2.2.4.2 at time t1, UE (100) takes no action. At time t1+T, UE (100) becomes interested in V2X services and requires the V2X SIB. If t1+T is within the modification period N of when UE (100) has already acquired SIB1 (i.e., t1 and t1+T correspond to the same modification period), the stored SIB1 acquired at time t1 remains valid. UE (100) can reprocess the stored SIB1 acquired at time t1 to determine whether to trigger an SI request. Whenever UE (100) wants to receive an SIB (e.g., location is activated, V2X is activated, etc.) (which may occur at any time during modification N), triggering of an SI request in the connected state should be possible. However, according to the RRC specification version 15, when the UE (100) acquires SIB1 while executing clause 5.2.2.4.2, it performs a check of the si-scheduling information used to trigger an SI request. Therefore, it needs to be specified that the UE (100) should check the scheduling information in the valid version of SIB1 before triggering an SI request for the desired SIB. In this case, by checking the content of the si-scheduling information field and the broadcast status bit in the stored valid version of SIB1, the UE (100) should be able to trigger the SI request procedure in clause 5.2.2.3.3 entitled “Request for System Information on Demand” in TS 38.331. In version 16 of the RRC specification, the following clause needs to be introduced to allow the UE (100) to send an SI request by checking the content of the si-scheduling information field in the stored valid version of SIB1 to determine whether the SIB is supported in the cell.

[0084] 5.2.2.3.3x Actions when SIB needs to be obtained in a connected state

[0085] UE(100) should:

[0086] 1> If the UE (100) is in RRC_CONNECTED, the active BWP has a common search space that is not configured by search space SIB1 and paging search space, and the UE (100) has not stored a valid version of the SIB complying with subclause 5.2.2.2.1 among one or more required SIBs complying with subclause 5.2.2.1:

[0087] 2> For an SI message that includes at least one required SIB according to the si-scheduling information in the stored SIB1:

[0088] 3> Trigger a request to acquire the SI message as defined in subclause 5.2.2.3.3:

[0089] 1> Otherwise, if the UE (100) is in RRC_CONNECTED, the active BWP has a common search space configured by search space SIB1 and paging search space, and the UE (100) has not stored a valid version of the SIB complying with subclause 5.2.2.2.1 among one or more required SIBs complying with subclause 5.2.2.1:

[0090] 2> For an SI message that includes at least one required SIB according to the si-scheduling information in the stored SIB1, and for an SI message with si-BroadcastStatus set to broadcast:

[0091] 3> Acquire the SI message defined in subclause 5.2.2.3.2;

[0092] 2> For an SI message that includes at least one required SIB according to the si-scheduling information in the stored SIB1, and for an SI message with si-broadcast status set to not broadcasting:

[0093] 3> Trigger a request to acquire the SI message as defined in subclause 5.2.2.3.3:

[0094] If the time instant t1+T when the UE (100) intends to acquire the SIB is within the modification period N, that is, (t1+T<N), then the stored SIB1 acquired at time instant t1 is still valid; otherwise, the UE (100) needs to re-acquire SIB1 from the broadcast.

[0095] In one embodiment, 5.2.2.3.3x Actions when a SIB is required to be acquired in connected mode The UE (100) shall:

[0096] 1> If UE (100) is in an RRC_ connection, the active BWP has a common search space not configured by search space SIB1 and paging search space, and onDemandSibRequest is set to TRUE, and UE (100) does not store a valid version of a SIB conforming to sub-clause 5.2.2.2.1 from one or more required SIBs conforming to sub-clause 5.2.2.2.

[0097] 2> For SI messages that contain at least one required SIB based on the si-scheduling information stored in SIB1:

[0098] 3> Trigger a request to retrieve the SI message as defined in sub-clause 5.2.2.3.3:

[0099] 1> Otherwise, if the UE (100) is in an RRC_ connection, the active BWP has a common search space configured by the search space SIB1 and the paging search space, and the on-demand Sib request is set to true (TRUE), and the UE (100) does not store a valid version of a SIB conforming to sub-clause 5.2.2.2.1 from one or more required SIBs conforming to sub-clause 5.2.2.1:

[0100] 2> For SI messages that contain at least one required SIB based on the si-scheduling information stored in SIB1, and for SI messages that set the si-broadcast status to broadcast:

[0101] 3> Obtain the SI message defined in sub-clause 5.2.2.3.2;

[0102] 2> For SI messages that contain at least one required SIB based on the si-scheduling information stored in SIB1, and for SI messages that set the si-broadcast status to non-broadcast:

[0103] 3> Trigger a request to retrieve the SI message as defined in sub-clause 5.2.2.3.3:

[0104] If the time t1+T is not within the modification period for acquiring SIB1 (i.e., t1+T>N), the stored SIB1 acquired at time t1 may be invalid, thereby making it impossible to correctly determine the SI request. The UE (100) needs to re-acquire SIB1 from the broadcast at time t2. Generally, the UE (100) applies previously acquired or received SI and also applies the SI acquired or received when the SI has been updated. In other words, before the UE (100) manages to obtain new SI, the UE (100) will continue to use the previous version of SI (if valid). This general behavior does not apply to determining an SI request based on the broadcast bit status in SIB1. The reasons why the stored SIB1 acquired at time t1 may be invalid are as follows:

[0105] According to the RRC specification of Release 15, if the required SIB is supported and the broadcast status is set to not broadcast, the UE (100) requests SI. If a UE BWP is configured with a common search space, it can be argued whether the gNB always provides SIB1 to the UE (100) in a dedicated manner whenever the eNB changes the broadcast status bit. The gNB will not do this if the remaining SIB1 content is not updated and only the broadcast status bit changes, so when a common search space is configured in the active BWP, the UE (100) shall re-acquire SIB1 and check the broadcast status bit. The field description of the si-BroadcastStatus bit states:

[0106] Indicates whether an SI message is being broadcast. A change in si-BroadcastStatus shall not result in a system information change notification in a short message sent with P-RNTI on downlink control information (DCI) (see clause 6.5). When set to broadcast, the indicated value is valid until the end of the BCCH modification period.

[0107] This means that the status can be changed from not broadcasting to broadcasting at any time during the modification period. If the status is changed to broadcasting, the network (200) starts broadcasting the relevant SIB. However, such a change to the broadcast status bit does not generate an SI change notification, and therefore does not trigger the UE (100) to re-acquire SIB1. If a UE (100) has acquired SIB1 at time t1 when the status is not broadcasting, the UE (100) will send an SI request at time t1+T<N (assuming the acquired SIB1 is valid). This is not problematic, because after sending the SI request, the UE (100) will acquire the relevant SIB from the broadcast, or the gNB will deliver the SIB requested by the UE (100) in dedicated RRC signaling.

[0108] This applies to using the stored SIB1 acquired during the modification period to determine if an SI request is sent within that modification period itself and if reacquiring SIB1 is not required. Therefore, if the UE (100) needs an SIB in the RRC_connection at any time during modification period N, the UE (100) can check the SIB1 acquired at the beginning of modification period N to determine if an SI request transmission is needed. However, the SIB1 acquired in modification period N is invalid for SI requests in modification period N+1, i.e., t1+T>N, relative to the broadcast bit. For example, in modification period N, the broadcast bit can be set to broadcast. In modification period N+1, the broadcast bit is set to not broadcast. In the si-scheduling information, if only the broadcast bit has changed in modification period N+1 compared to modification period N, the network (200) will neither send an SI change notification nor a SIB1 to the UE (100) in a dedicated manner. UE (100) cannot use the stored SIB1 acquired in modification period N to determine whether to send an SI request because if it does so, UE (100) will not send an SI request, since the broadcast bit is set to broadcast in modification period N, and therefore UE (100) will not be able to acquire the required SIB, as the network does not broadcast the required SIB in modification period N+1. In this case, UE (100) will reacquire SIB1 from the broadcast in modification period N+1 and check the broadcast status bit (i.e., at t1+T>N). This is possible if a common search space is configured. If no common search space is configured and UE (100) has not previously acquired SIB1 in modification period N+1, it needs to send an SI request based on the stored SIB1 acquired in modification period N (i.e., according to method 1) without checking the broadcast status bit.

[0109] This method can be used to trigger an SI request to obtain an SIB in the RRC_connected state when the UE's active BWP is configured with a common search space, such as... Figure 4 As depicted in [the text]. In one example, such as [example]... Figure 4As shown, at S402, the method includes detecting that the UE (100) is in RRC connection mode. At S404, the method includes determining that the UE's active BWP is configured with a common search space. At S406, the method includes determining that the UE (100) has not stored an SIB or that the version of the required SIB stored is invalid. At S408, the method includes checking whether the stored SIB1 was acquired in the same modification period. If the stored SIB1 was not acquired in the same modification period, then at S410, the method includes reacquiring the SIB1 from the broadcast. If the stored SIB1 was acquired in the same modification period, then at S412, the method includes checking the Si-scheduling information and Si-broadcast status in the stored SIB1. At S414, the method includes acquiring the required SIB from the broadcast if the Si-broadcast status is "broadcast". At S416, the method includes sending an SI request for the required SIB if the Si-broadcast status is "not broadcast".

[0110] The following update needs to be introduced in clause 5.2.2.3.1 of version 16 of the RRC specification to allow UE (100) to reacquire SIB1 when the UE's active BWP is configured with a common search space, and if the stored SIB1 was acquired at modification N or earlier, UE (100) needs to check the broadcast status bit in modification period N+1.

[0111] 5.2.2.3.1 Obtaining MIB and SIB1

[0112] UE(100) should:

[0113] 1> Apply the specified BCCH configuration defined in 9.1.1.1;

[0114] 1> If UE(100) is in RRC_Idle or RRC_Inactive; or

[0115] 1> If the UE (100) is in an RRC connection during T311 operation:

[0116] 2> Obtain the MIB scheduled according to the specifications in TS 38.213;

[0117] 2> If UE(100) cannot obtain the MIB;

[0118] 3> Perform the actions specified in Clause 5.2.2.5;

[0119] 2> Otherwise:

[0120] 3> Perform the actions specified in Clause 5.2.2.4.1.

[0121] 1> If the UE (100) is in an RRC_ connection, the active BWP has a common search space configured by the search space SIB1 and the paging search space, and has received an indication of a change in system information; or

[0122] 1> If UE (100) is in an RRC_connection, the active BWP has a common search space configured by the search space SIB1 and the paging search space, and UE (100) needs to check the si-broadcast status in modification period N+1, where the stored SIB1 was acquired in modification period N or earlier; or

[0123] 1> If UE(100) is in RRC_Idle or RRC_Inactive; or

[0124] 1> If the UE (100) is in an RRC connection during T311 operation:

[0125] 2> If the SSB-SubcarrierOffset indicates that SIB1 is being transmitted in the cell (TS38.213) and if the UE needs to obtain SIB1:

[0126] 3> Obtain SIB1 that is scheduled according to the specifications in TS 38.213;

[0127] 3> If UE(100) cannot obtain SIB1:

[0128] 4. Perform the actions specified in Clause 5.2.2.5;

[0129] 3> Otherwise:

[0130] 4> After obtaining SIB1, perform the actions specified in Clause 5.2.2.4.2.

[0131] 2> Otherwise, if UE (100) needs to acquire SIB1 and the ssb-subcarrier offset indicates that SIB1 is not scheduled in the cell:

[0132] 3> Perform the actions specified in Clause 5.2.2.5.

[0133] Alternatively, UE(100) should:

[0134] 1> Apply the specified BCCH configuration defined in 9.1.1.1;

[0135] 1> If the UE (100) is in an RRC_Idle or RRC_Inactive state; or

[0136] 1> If the UE (100) is in an RRC connection during T311 operation:

[0137] 2> Obtain the MIB scheduled according to the specifications in TS 38.213;

[0138] 2> If UE(100) cannot obtain the MIB;

[0139] 3> Perform the actions specified in Clause 5.2.2.5;

[0140] 2> Otherwise:

[0141] 3> Perform the actions specified in Clause 5.2.2.4.1.

[0142] 1> If the UE (100) is in an RRC_ connection, the active BWP has a common search space configured by the search space SIB1 and the paging search space, and has received an indication of a change in system information; or

[0143] 1> If UE (100) is in an RRC_connection, the active BWP has a common search space configured by search space SIB1 and paging search space, and UE (100) does not store a valid version of a SIB conforming to sub-clause 5.2.2.2.1 from one or more required SIBs, and UE (100) does not acquire SIB1 in the current modification period; or

[0144] 1> If UE(100) is in RRC_Idle or RRC_Inactive; or

[0145] 1> If the UE (100) is in an RRC connection during T311 operation:

[0146] 2> If the SSB-subcarrier offset indicator SIB1 is transmitted in the cell (TS 38.213) and if the UE (100) needs to obtain SIB1:

[0147] 3> Obtain SIB1 that is scheduled according to the specifications in TS 38.213;

[0148] 3> If UE(100) cannot obtain SIB1:

[0149] 4. Perform the actions specified in Clause 5.2.2.5;

[0150] 3> Otherwise:

[0151] 4> After obtaining SIB1, perform the actions specified in Clause 5.2.2.4.2.

[0152] 2> Otherwise, if UE (100) needs to acquire SIB1 and the ssb-subcarrier offset indicates that SIB1 is not scheduled in the cell:

[0153] 3> Perform the actions specified in Clause 5.2.2.5.

[0154] Alternatively, UE(100) should:

[0155] 1> Apply the specified BCCH configuration defined in 9.1.1.1;

[0156] 1> If UE(100) is in RRC_Idle or RRC_Inactive; or

[0157] 1> If the UE (100) is in an RRC connection during T311 operation:

[0158] 2> Obtain the MIB scheduled according to the specifications in TS 38.213;

[0159] 2> If UE(100) cannot obtain the MIB;

[0160] 3> Perform the actions specified in Clause 5.2.2.5;

[0161] 2> Otherwise:

[0162] 3> Perform the actions specified in Clause 5.2.2.4.1.

[0163] 1> If the UE (100) is in an RRC_ connection, the active BWP has a common search space configured by the search space SIB1 and the paging search space, and has received an indication of a change in system information; or

[0164] 1> If UE (100) is in an RRC_connection, the active BWP has a common search space configured by search space SIB1 and paging search space, and the on-demand Sib request is set to true, and UE (100) does not store a valid version of a SIB conforming to sub-clause 5.2.2.2.1 from one or more required SIBs, and UE (100) does not acquire SIB1 in the current modification period; or

[0165] 1> If UE(100) is in RRC_Idle or RRC_Inactive; or

[0166] 1> If the UE (100) is in an RRC connection during T311 operation:

[0167] 2> If the SSB-subcarrier offset indication is transmitting SIB1 in the cell (TS 38.213

[13] ), and if the UE (100) needs to obtain SIB1:

[0168] 3> Obtain SIB1 that is scheduled according to the specifications in TS 38.213;

[0169] 3> If UE(100) cannot obtain SIB1:

[0170] 4. Perform the actions specified in Clause 5.2.2.5;

[0171] 3> Otherwise:

[0172] 4> After obtaining SIB1, perform the actions specified in Clause 5.2.2.4.2.

[0173] 2> Otherwise, if the UE requires SIB1 and the SSB-Subcarrier Offset Indicator SIB1 is not scheduled in the cell:

[0174] 3> Perform the actions specified in Clause 5.2.2.5.

[0175] Alternatively, the action required in Clause 5.2.2.3.3x when obtaining the SIB in the connected state can be updated as follows:

[0176] UE(100) should:

[0177] 1> If the UE (100) is in an RRC_connection, the active BWP has a common search space that is not configured by the search space SIB1 and the paging search space, and the UE (100) does not store a valid version of an SIB that conforms to sub-clause 5.2.2.2.1 in one or more required SIBs:

[0178] 2> For SI messages that contain at least one required SIB based on the si-scheduling information stored in SIB1:

[0179] 3> Trigger a request to retrieve the SI message as defined in sub-clause 5.2.2.3.3:

[0180] 1> Otherwise, if the UE (100) is in an RRC_ connection, the active BWP has a common search space configured by the search space SIB1 and the paging search space, and the UE (100) does not store a valid version of an SIB conforming to sub-clause 5.2.2.2.1 from one or more required SIBs:

[0181] 2> If SIB1 was already stored and acquired during the current modification cycle:

[0182] 3> For SI messages that contain at least one required SIB based on the si-scheduling information stored in SIB1, and for SI messages that set the si-broadcast status to broadcast:

[0183] 4> Obtain the SI message defined in sub-clause 5.2.2.3.2;

[0184] 3> For SI messages that contain at least one required SIB based on the si-scheduling information stored in SIB1, and for SI messages that set the si-broadcast status to non-broadcast:

[0185] 4> Trigger a request to retrieve the SI message as defined in sub-clause 5.2.2.3.3:

[0186] 2> Otherwise:

[0187] 3> Obtain SIB1;

[0188] Alternatively, the action required in Clause 5.2.2.3.3x when obtaining the SIB in the connected state can be updated as follows.

[0189] UE(100) should:

[0190] 1> If UE (100) is in an RRC_ connection, the active BWP has a common search space not configured by search space SIB1 and paging search space, and the on-demand Sib request is set to true (TRUE), and UE (100) does not store a valid version of a SIB conforming to sub-clause 5.2.2.2.1 from one or more required SIBs:

[0191] 2> For SI messages that contain at least one required SIB based on the si-scheduling information stored in SIB1:

[0192] 3> Trigger a request to retrieve the SI message as defined in sub-clause 5.2.2.3.3:

[0193] 1> Otherwise, if the UE (100) is in an RRC_ connection, the active BWP has a common search space configured by the search space SIB1 and the paging search space, and the on-demand Sib request is set to true (TRUE), and the UE (100) does not store a valid version of a SIB conforming to sub-clause 5.2.2.2.1 from one or more required SIBs conforming to sub-clause 5.2.2.1:

[0194] 2> If SIB1 was already stored and acquired during the current modification cycle:

[0195] 3> For SI messages that contain at least one required SIB based on the si-scheduling information stored in SIB1, and for SI messages that set the si-broadcast status to broadcast:

[0196] 4> Obtain the SI message defined in sub-clause 5.2.2.3.2;

[0197] 3> For SI messages that contain at least one required SIB based on the si-scheduling information stored in SIB1, and for SI messages that set the si-broadcast status to non-broadcast:

[0198] 4> Trigger a request to retrieve the SI message as defined in sub-clause 5.2.2.3.3:

[0199] 2> Otherwise:

[0200] 3> Obtain SIB1;

[0201] Method 3: The broadcast status bit is set to "not broadcasting" and the flag in RRC Reconfiguration is set to "false".

[0202] If a common search space for receiving system information is configured on the active BWP, the UE (100) in an RRC_connection checks whether a required on-demand SI is being broadcast by reading SIB1 before sending an SI request, and sends the SI request only if the required on-demand SI is not being broadcast, as in RRC_idle / inactive. In addition to the broadcast status bit in SIB1, the RRC reconfiguration message also contains another explicit network indication (i.e., a flag) to inform the UE (100) whether on-demand SIB requests are supported in an RRC_connection. If the UE (100) receives an RRC reconfiguration message containing the flag and checks the broadcast status bit in SIB1, the UE's behavior should be explicit when a common search space is configured on the active BWP.

[0203] The field description for the si-broadcast status bit states: "Indicates whether an SI message is being broadcast. Changes in the si-broadcast status should not result in a notification of system information change in a short message sent on the DCI along with the P-RNTI (see Clause 6.5). When set to broadcast, the indicated value is valid until the end of the BCCH modification cycle."

[0204] The field description of the On-Demand SIB Request flag included in the RRC reconfiguration states: "Indicates whether the UE (100) is allowed to request SIB on demand while in the RRC_connected state", as shown in [Table 2].

[0205] [Table 2]

[0206]

[0207]

[0208] UE behaviors for scenarios 1, 2, and 3 are as follows Figure 5 As shown. In one example, such as Figure 5As shown, at S502, the method includes detecting that the UE (100) is in RRC connection mode. At S504, the method includes determining that the UE's active BWP is configured with a common search space. At S506, the method includes determining that the UE (100) has not stored an SIB or that the version of the required SIB stored is invalid. At S508, the method includes checking whether the stored SIB1 was acquired in the same modification period. If the stored SIB1 was not acquired in the same modification period, then at S510, the method includes reacquiring the SIB1 from the broadcast. If the stored SIB1 was acquired in the same modification period, then at S512, the method includes checking the Si-scheduling information and Si-broadcast status in the stored SIB1. At S514, the method includes acquiring the required SIB from the broadcast if the Si-broadcast status is "broadcast". At S516, the method includes sending an SI request for the required SIB if the Si-broadcast status is "not broadcast" and the on-demand SiB request is "true".

[0209] If the active BWP is not configured with a common search space, and the On-Demand Sib Request flag included in the RRC reconfiguration message is set to true, then the UE (100) sends an SI request according to method 1, such as... Figure 6 As described. For example Figure 6 As shown, at 602, the method includes detecting that the UE (100) is in RRC connected mode. At 604, the method includes determining that the UE's active BWP is not configured with a common search space. At 606, the method includes determining that the UE (100) has not stored a SIB or that the version of the desired SIB stored is invalid. At 608, the method includes checking the si-scheduling information in the stored SIB1 to determine at least one desired SIB. At 610, the method includes sending an SI request for the desired SIB if the on-demand SiB request is true.

[0210] The various actions, behaviors, modules, steps, etc. in the flowchart (S200 to S600) can be executed in the presented order, in different orders, or simultaneously. Furthermore, in some embodiments, actions, behaviors, boxes, steps, etc., can be omitted, added, modified, or skipped without departing from the scope of the invention.

[0211] The embodiments disclosed herein can be implemented by at least one software program that runs on at least one hardware device and performs network management functions to control the elements.

[0212] The foregoing description of specific embodiments will fully reveal the general nature of the embodiments herein, enabling others to readily modify and / or adapt such specific embodiments to various applications by applying present knowledge without departing from the general conception, and therefore, such adaptations and modifications should and will be understood to fall within the meaning and scope of equivalents of the disclosed embodiments. It should be understood that the wording or terminology used herein is for descriptive purposes and not for limitation. Therefore, although the embodiments herein have been described according to preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modifications within the spirit and scope of the embodiments described herein.

[0213] Although this disclosure has been described with reference to various embodiments, various changes and modifications will be apparent to those skilled in the art. It is intended that this disclosure cover such changes and modifications that fall within the scope of the appended claims.

Claims

1. A method performed by a user equipment (UE) in a wireless communication system, the method comprising: Obtain scheduling information associated with system information (SI) from the base station; The UE receives a Radio Resource Control (RRC) reconfiguration message from the base station, including an onDemandSibRequest indicator, wherein the onDemandSibRequest indicator indicates that the UE is permitted to request at least one System Information Block (SIB) on demand in the RRC connected state. Identify whether the UE is in the RRC connection state and has an active bandwidth portion (BWP) configured with a common search space, and whether the UE has stored one or more valid versions of the required SIBs; When the UE is in the RRC connected state and has the active BWP that is not configured with the public search space, and the UE has not yet stored the valid version of the one or more required SIBs, the UE sends a request message to the base station requesting at least one required SIB based on the onDemandSibRequest indicator.

2. The method as described in claim 1, wherein obtaining the scheduling information includes: If the UE is in the RRC connection state and has an active BWP configured with a common search space for System Information Block Type 1 (SIB1) and the UE has not yet stored a valid version of the one or more required SIBs, identify whether the UE has acquired the SIB1 in the current modification cycle; If the UE does not obtain the SIB1 during the current modification period, it obtains the SIB1, which includes the scheduling information, from the base station. as well as Store the obtained SIB1.

3. The method of claim 2, further comprising: The scheduling information in the stored SIB1 is examined to determine the at least one required SIB.

4. The method of claim 1, further comprising: When the UE is in the RRC connected state and has the active BWP configured with the common search space, and the UE has not yet stored a valid SIB version of the one or more required SIBs. Identify whether the si-BroadcastStatus indicator included in the scheduling information is set to broadcast or not broadcast; and When the si-BroadcastStatus indicator is set to broadcast, the at least one required SIB is obtained from the base station.

5. The method of claim 4, wherein, Sending the request message includes: When the si-BroadcastStatus indicator is set to not broadcast, a request message requesting the at least one required SIB is sent to the base station.

6. A user equipment (UE) in a wireless communication system, the UE comprising: transceiver; as well as The processor, coupled to the transceiver, is configured to: Obtain scheduling information associated with the System Information (SI) from the base station. The UE receives a Radio Resource Control (RRC) reconfiguration message from the base station, including an onDemandSibRequest indicator, which indicates that the UE is permitted to request at least one SIB on demand in the RRC connected state. Identify whether the UE is in the RRC connection state and has an active bandwidth portion (BWP) configured with a common search space, and whether the UE has stored one or more valid versions of the required SIBs; When the UE is in the RRC connected state and has the active BWP that is not configured with the public search space, and the UE has not yet stored the valid version of the one or more required SIBs, the UE sends a request message to the base station requesting at least one required SIB based on the onDemandSibRequest indicator.

7. The UE according to claim 6, wherein, The processor is also configured to: If the UE is in the RRC connection state and has an active BWP configured with a common search space for System Information Block Type 1 (SIB1) and the UE has not yet stored a valid version of the one or more required SIBs, identify whether the UE has acquired the SIB1 in the current modification cycle; If the UE does not obtain the SIB1 during the current modification period, it obtains the SIB1, which includes the scheduling information, from the base station. as well as Store the obtained SIB1.

8. The UE according to claim 7, wherein, The processor is also configured to: The scheduling information in the stored SIB1 is examined to determine the at least one required SIB.

9. The UE according to claim 6, wherein, The processor is also configured to: When the UE is in the RRC connected state and has the active BWP configured with the common search space, and the UE has not yet stored a valid SIB version of the one or more required SIBs. Identify whether the si-BroadcastStatus indicator included in the scheduling information is set to broadcast or not broadcast; and When the si-BroadcastStatus indicator is set to broadcast, the at least one required SIB is obtained from the base station.

10. The UE according to claim 9, wherein, The processor is also configured to: When the si-BroadcastStatus indicator is set to not broadcast, a request message requesting the at least one required SIB is sent to the base station.

Images