Patent Description:
<CIT> A1is concerned with identifying whether a DL BWP of a UE is configured with a common search space, and transmitting, to the UE, an updated system information in a dedicated signalling when the active DL BWP of the UE is not configured with the common search space.

<NPL> is concerned with on-demand SI for RRC_CONNECTED UE.

In the 3GPP Release <NUM> standards of the NR, the on-demand SI request is supported by the UE in an IDLE and an INACTIVE state. The Release <NUM> UE does not support the on-demand SI request in a CONNECTED state.

The invention is set out in the appended set of claims, wherein the figures and respective description relate to advantageous embodiments thereof.

The principal object of the embodiments herein is to provide a method for handling SI in a wireless communication system by a UE in an RRC connected mode.

This invention is illustrated in the accompanying drawings, throughout which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the drawings, in which:.

it may be advantageous to set forth definitions of certain words and phrases used throughout this patent document: the terms "include" and "comprise, " as well as derivatives thereof, mean inclusion without limitation; the term "or," is inclusive, meaning and/or; the phrases "associated with" and "associated therewith, " as well as derivatives thereof, may mean to include, be included within, interconnect with, contain, be contained within, connect to or with, couple to or with, be communicable with, cooperate with, interleave, juxtapose, be proximate to, be bound to or with, have, have a property of, or the like; and the term "controller" means any device, system or part thereof that controls at least one operation, such a device may be implemented in hardware, firmware or software, or some combination of at least two of the same.

As is traditional in the field, embodiments may be described and illustrated in terms of blocks which carry out a described function or functions. These blocks, which may be referred to herein as units or modules or the like, are physically implemented by analog or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, or the like, and may optionally be driven by firmware and software. The circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like. The circuits 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 to perform some functions of the block and a processor to perform other functions of the block. Each block of the embodiments may be physically separated into two or more interacting and discrete blocks without departing from the scope of the invention. Likewise, the blocks of the embodiments may be physically combined into more complex blocks without departing from the scope of the invention.

The accompanying drawings are used to help easily understand various technical features and it should be understood that the embodiments presented herein are not limited by the accompanying drawings. As such, the present disclosure should be construed to extend to any alterations, equivalents and substitutes in addition to those which are particularly set out in the accompanying drawings.

In the recent years, several broadband wireless technologies have been developed to meet the growing number of broadband subscribers and to provide more and better applications and services. A second generation wireless communication system has been developed to provide voice services while ensuring the mobility of users. A third generation wireless communication system supports not only the voice service but also a data service. In recent years, a fourth generation wireless communication system has been developed to provide high-speed data service. However, currently, the fourth generation wireless communication system suffers from lack of resources to meet the growing demand for high speed data services, so that a fifth generation wireless communication system is being developed to meet the growing demand for high speed data services, support ultra-reliability and low latency applications.

The fifth generation wireless communication system will be implemented not only in lower frequency bands but also in higher frequency (mmWave) bands, e.g., <NUM> to <NUM> bands, so as to accomplish higher data rates. In order to mitigate propagation loss of radio waves and increase the transmission distance, a beamforming, massive multiple-input multiple-output (MIMO), Full dimensional MIMO (FD-MIMO), array antenna, an analog beamforming, large scale antenna techniques are being considered in the design of the fifth generation wireless communication system. In addition, the fifth generation wireless communication system is expected to address different use cases having quite different requirements in terms of data rate, latency, reliability, mobility, etc. However, a design of an air-interface of the fifth generation wireless communication system would be flexible enough to serve user equipment's (UEs) having quite different capabilities depending on the use case and market segment the UE cater service to the end customer. For example, use cases the fifth generation wireless communication system wireless system are expected to address is enhanced mobile broadband (eMBB), massive machine type communication (m-MTC), ultra-reliable low latency communication (URLL), etc. The eMBB requirements like tens of Gbps data rate, low latency, high mobil ity and so on and so forth address the market segment representing the conventional wireless broadband subscribers needing internet connectivity everywhere, all the time and on the go. The m-MTC requirements like very high connection density, infrequent data transmission, very long battery life, low mobility address so on and so forth address the market segment representing the internet of things (IoT)/internet of everything (IoE) envisioning connectivity of billions of devices. The URLL requirements like very low latency, very high reliability and variable mobility and so on and so forth address the market segment representing the Industrial automation application,
vehicle-to-vehicle/vehicle-to-infrastructure communication foreseen as one of the enablers for autonomous cars.

In the fourth generation wireless communication system like long term evolution (LTE), enhanced node B (eNB) or a base station broadcasts system information in a cell. The system information is structured into a master information block (MIB) and a set of system information blocks (SIBs). The MIB consists of system frame number (SFN), Downlink System bandwidth, and physical hybrid automatic repeat request (ARQ) feedback indicator channel (PHICH) configuration. The MIB is transmitted every <NUM>. The MIB is repeated every <NUM> wherein a first transmission occurs in sub frame #<NUM> when the SFN mod <NUM> equals zero. The MIB is transmitted on a physical broadcast channel (PBCH). system information block type <NUM> (SIB1) carries cell identity, tracking area code, cell barring information, value tag (common for all scheduling units), and scheduling information of other SIBs. The SIB <NUM> is transmitted every <NUM> in subframe #<NUM> when the SFN mod <NUM> equals zero. The SIB <NUM> is repeated in subframe#<NUM> when the SFN mod <NUM> equals zero. The SIB <NUM> is transmitted on the physical downlink shared channel (PDSCH). Other SIBs (SIB <NUM> to SIB <NUM>) are transmitted in a SI message, wherein the scheduling information of the SIBs are indicated in the SIB <NUM>. Further, in the LTE system during a handover of a UE from a source eNB to a target eNB, the target eNB provides through the dedicated signaling the specific subsets of parameters of the MIB, SIB1, and SIB2 of the target cell in the handover command message to the UE. The RACH configuration and physical configuration of the target cell i.e., radioResourceConfigCommon is provided to the UE in the mobilitycontrolinfo through dedicated signaling. Similarly, if the UE is operating in a dual connectivity mode of an operation then the system information of the cells of the secondary eNB (SeNB) or secondary cell group (SCG) cells i.e., the RACH configuration and physical configuration of the SCG cells i.e., radioResourceConfigCommonPSCell is provided to the UE through a dedicated signaling. Another scenario where the UE is provided the dedicated system information is upon release with redirection wherein the SI of candidate cells i.e., system information in the CellInforGERAN and utra-BCCH-Container in the CellInfoUTRA for GSM edge radio access network (GERAN) and universal mobile telecommunications system (UMTS) respectively are provided to the UE in an RRCConnectionRelease message.

For the fifth generation wireless communication system i.e., NR system, in a <NUM> node B (i.e., gNB), the system information is delivered either through broadcast or delivered upon a UE request i.e., on-demand SI request. In the fifth generation wireless communication system, information is divided into minimum SI (MSI) and other SI (OSI). Similar to LTE system information the other SI can be structured into a set of SI-blocks (SIBs).

The MSI is periodically broadcasted. Other SI can be periodically broadcasted or provided on-demand based on a UE request. The minimum SI comprises basic information required for initial access to a cell and information for acquiring any other SI broadcast periodically or provisioned via the on-demand basis. The minimum SI includes at least SFN, list of public land mobile network (PLMN), cell ID, cell camping parameters, RACH parameters. If the network allows on a demand mechanism, parameters required for requesting other SI-block(s) (if any needed, e.g. RACH preambles for request) are also included in the MSI. The MSI comprises of at least the MIB and SIB1 which covers the parameters similar to LTE MIB, SIB1, and SIB2.

The scheduling information in the MSI includes an indicator which indicates whether the concerned SI-block is periodically broadcasted or provided on the demand. The scheduling information for the other SI includes SIB type, validity information, SI periodicity, and SI-window information. The scheduling information for the other SI is provided irrespective of whether the other SI is periodically broadcasted or not. If minimum SI indicates that the SIB is not broadcasted (i.e., the SIB is provided on demand), then the UE does not assume that this SIB is a periodically broadcasted in its SI-window at every SI period. Therefore, the UE may send an SI request to receive the SIB. For other SI provided on-demand, the UE can request one or more SI-block(s) or all SI-blocks in a single request.

The NR system can be deployed in standalone (SA) mode of operation (i.e., UE only connected to the NR) or a non-standalone mode of operation i.e., UE connected to both LTE and NR alike LTE dual connectivity, meaning the radio connection involves a master cell group control led by a master node and a secondary cell group controlled by a secondary node). In the standalone mode of operation, the MSI is always periodically broadcasted while the OSI can be provided on-demand basis or periodically broadcasted depending on network (or a base station) implementation. For non-standalone mode of operation where the LTE eNB is a master node and the NR gNB is a secondary node, the system information of the cells of the secondary node or NR SCG cells involves dedicated transfer of SI upon SCG cell addition or during the SCG change. In such scenario the network pushes the relevant SI of the NR SCG cells because the on-demand concept for requesting the relevant SI is not supported for the non-standalone mode of operation. In the 3GPP Release <NUM> standards of the NR, the on-demand SI request is supported by the UE in an IDLE and an INACTIVE state. The Release <NUM> UE does not support the on-demand SI request in a CONNECTED state.

There are a few UE requirements for storing the acquired SI regardless of the mode of operation is the standalone or the non-standalone. The UE shall store relevant SI acquired from the currently camped/serving cell. Storing SI other than the currently camped/serving cell is up to UE implementation. The UE may store several versions of SI based on its storage capability. The UE may indicate its storage capability to the network. Different from LTE, some NR SI acquired from/ provided by dedicated signaling for one cell may be valid in another cell also i.e., the information may be valid in an area covered by multiple cells. Like in LTE, a version of the SI that the UE acquires and stores remains valid only for a certain time. The UE may use such a stored version of the SI, e.g. after cell re-selection, upon return from out of coverage, after SI change indication or after SCG change. In typical UE implementation the SI storage management is typically referred as garbage collection wherein the stored information for the longest time is typically discarded. Stored SI normally does not change during the RRC connection unless garbage collection is invoked upon reception of new SI or validity timer associated with stored SI has expired or so called systeminfovaluetag or systemconfigurationindex associated with stored SI has changed.

In the NR system, the network (or a base station) should be able to provide SI required in the connected state upon the same UE mobility cases as in LTE (change of PCell, SCell addition). In addition, it may be beneficial for the network to provide the connected state UE with SI required if the UE active bandwidth part (BWP) is not configured with common search space as shown in the [Table <NUM>].

In case only essential parts of MSI are provided (some parameters of MIB and SIB1), during PCell mobility i.e., handover, the UE may subsequently obtain the missing parts by reading the MIB and SIB1 from the broadcast (if the UE is configured with the common search space) after the handover is completed. If the UE active BWP is not configured with common search space, then the UE is preferable to always transfer entire MIB (except SFN) and SIB1 to UE in a dedicated manner. This furthermore avoids the tedious efforts to determine the essential fields (fields urgently required upon UE mobility). The NR system has introduced support of dedicated transfer of SI to the reconfiguration message. SI may be provided in the same message commanding UE mobility i.e., to the NR reconfiguration message like the handover command message in LTE. For a UE in RRC_CONNECTED, the network can provide system information through dedicated signaling using the RRCReconfiguration message, e.g. if the UE has an active BWP with no common search space configured to monitor system information or paging. The entire SIB1 can be provided by the network to the UE through dedicated signaling using the field dedicatedSIB1-Delivery included in the RRCReconfiguration message. Any other SIB can be provided by the network to the UE through dedicated signaling using the field dedicatedSystemInformationDelivery included in the RRCReconfiguration message. In the Release16 of NR standardization, new features like vehicle to everything (V2X), positioning are introduced, and hence new SIBs associated with these features will be introduced. These new SIBs will be required by the UE in an RRC_CONNECTED state. Therefore, the on-demand concept of the SI request is also supported by UE in the RRC_CONNECTED state in Release-<NUM>. In the patent disclosure, the following aspects related to support of the SI request by the UE in RRC_CONNECTED state is disclosed:.

Accordingly, embodiments herein disclose a method for handling SI in a wireless communication system by a UE in an RRC connected mode. The method includes deciding, by the UE, that the UE requires at least one SIB from a plurality of SIBs indicated in a SI scheduling information broadcasted by a network. The method includes determining, by the UE, from the plurality of SIBs, that the UE does not have a stored SIB as required or a stored version of a required SIB exists but the stored version of the required SIB is not valid. Further, the method includes checking, by the UE, that the UE is allowed to send a SI request based on a network configuration. Further, the method includes sending, by the UE, the SI request for the required SIB in response to checking that the UE is allowed to send the SI request based on the network configuration.

In an embodiment, deciding, by the UE, that the UE requires the at least one SIB from the plurality of SIBs indicated in the scheduling information broadcasted by the network includes determining, by the UE, that an active BWP with a common search space is configured for the UE, detecting, by the UE, that a SIB1 is not acquired in a current modification period, and acquiring, by the UE, the SIB1 from the broadcast in response to detecting that the SIB1 is not acquired in the current modification period.

In an embodiment, acquiring the SIB1 from the broadcast includes storing, by the UE, the acquired SIB1 from the broadcast, and checking, by the UE, the SI scheduling information in the stored SIB1 and to determine a setting of a si-BroadcastStatus bit associated with the required SIB.

In an embodiment, acquiring the required SIB from the broadcast in response to determining that the active BWP with the common search space is configured for the UE includes acquiring, by the UE, the required SIB from the broadcast if, in the stored SIB1, the si-BroadcastStatus bit associated with the required SIB is set to Broadcasting status.

In an embodiment, sending, by the UE, the SI request for the required SIB includes determining, by the UE, that an active BWP with a common search space is configured for the UE, checking, by the UE, the SI scheduling information in a stored SIB1 and to determine a setting of a si-BroadcastStatus bit associated with the required SIB, and sending, by the UE, the SI request indicating the required SIB if, in the stored SIB1, the si-BroadcastStatus bit associated with the required SIB is set to NotBroadcasting status and the UE is allowed to send SI request based on the network configuration.

In an embodiment, sending, by the UE, the SI request for the required SIB includes determining, by the UE, that an active BWP without a common search space is configured for the UE, checking, by the UE, the SI scheduling information in a stored SIB1, and sending, by the UE, the SI request indicating the required SIB if the UE is allowed to send the SI request based on the network configuration.

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

Accordingly, embodiments herein disclose a UE for handling SI in a wireless communication system including the UE in an RRC connected mode and a network. The UE includes a processor coupled with a memory. The processor is conf igured to decide that the UE requires at least one SIB from a plurality of SIBs indicated in a SI scheduling information broadcasted by a network. Further, the processor is configured to determine, from the plurality of SIBs, that the UE does not have a stored SIB as required or a stored version of a required SIB exists but the stored version of the required SIB is not valid. Further, the processor is configured to check that the UE is allowed to send a SI request based on a network configuration. Further, the processor is configured to send the SI request for the required SIB in response to checking that the UE is allowed to send the SI request based on the network configuration.

Many changes and modifications may be made within the scope of the embodiments herein without departing from the spirit thereof, and the embodiments herein include all such modifications.

The embodiments herein achieve a method for handling SI in a wireless communication system by a UE in an RRC connected mode. The method includes deciding, by the UE, that the UE requires at least one SIB from a plurality of SIBs indicated in a SI scheduling information broadcasted by a network. The method includes determining, by the UE, from the plurality of SIBs, that the UE does not have a stored SIB as required or a stored version of a required SIB exists but the stored version of the required SIB is not valid. Further, the method includes checking, by the UE, that the UE is allowed to send a SI request based on a network configuration. Further, the method includes sending, by the UE, the SI request for the required SIB in response to checking that the UE is allowed to send the SI request based on the network configuration.

<FIG> shows various hardware components of a UE (<NUM>) for handling SI in the wireless communication system (<NUM>), according to embodiments as disclosed herein. The wireless communication system (<NUM>) includes the UE (<NUM>) and a network (<NUM>). The UE (<NUM>) can be, for example, but not limited to a cellular phone, a smart phone, 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 (<NUM>) includes a processor (<NUM>), a communicator (<NUM>), a memory (<NUM>), and a SI controller (<NUM>). The processor (<NUM>) is coupled with the communicator (<NUM>), the memory (<NUM>), and the SI controller (<NUM>).

The SI controller (<NUM>) is configured to decide that the UE (<NUM>) requires the at least one SIB from a plurality of SIBs indicated in a SI scheduling information broadcasted by the network (<NUM>). In an embodiment, the UE (<NUM>) requiring the at least one SIB from the plurality of SIBs indicated in the scheduling information broadcasted by the network (<NUM>) is decided by determining that an active BWP with a common search space is configured for the UE (<NUM>), detecting that a SIB1 is not acquired in a current modification period, and acquiring the SIB1 from the broadcast in response to detecting that the SIB1 is not acquired in the current modification period.

In an embodiment, the SIB1, is acquired from the broadcast, the acquired SIB1 from the broadcast is stored, and the SI scheduling information in the stored SIB1 is checked and a setting of a si-BroadcastStatus bit associated with the required SIB is determined. In an embodiment, acquiring the required SIB from the broadcast in response to determining that the active BWP with the common search space is configured for the UE (<NUM>) includes acquire the required SIB from the broadcast if, in the stored SIB1, the si-BroadcastStatus bit associated with the required SIB is set to Broadcasting status.

Further, the SI controller (<NUM>) is configured to determine, from the plurality of SIBs, that the UE (<NUM>) does not have a stored SIB as required or a stored version of a required SIB exists but the stored version of the required SIB is not valid. Further, the SI controller (<NUM>) is configured to check that the UE (<NUM>) is allowed to send a SI request based on a network configuration. The network configuration is received, from the network (<NUM>), by receiving an RRC reconfiguration message from the network (<NUM>) including an indication indicating one of: whether the UE (<NUM>) is allowed to send the SI request in the RRC connected mode and whether the UE (<NUM>) is not allowed to send the SI request in the RRC connected mode.

Further, the SI controller (<NUM>) is configured to send the SI request for the required SIB in response to checking that the UE (<NUM>) is allowed to send the SI request based on the network configuration. In an embodiment, the SI request for the required SIB is sent by determining that the active BWP with the common search space is configured for the UE (<NUM>), checking the SI scheduling information in the stored SIB1 and determining a setting of a si-BroadcastStatus bit associated with the required SIB, and sending the SI request indicating the required SIB if, in the stored SIB1, the si-BroadcastStatus bit associated with the required SIB is set to NotBroadcasting status and the UE (<NUM>) is allowed to send SI request based on the network configuration. In another embodiment, the SI request for the required SIB is sent by determining that the active BWP without the common search space is configured for the UE (<NUM>), checking the SI scheduling information in the stored SIB1, and sending the SI request indicating the required SIB if the UE (<NUM>) is allowed to send the SI request based on the network configuration.

The processor (<NUM>) is configured to execute instructions stored in the memory (<NUM>) and to perform various processes. The communicator (<NUM>) is configured for communicating internally between internal hardware components and with external devices via one or more networks.

The memory (<NUM>) also stores instructions to be executed by the processor (<NUM>). The memory (<NUM>) may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory (<NUM>) may, in some examples, be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term "non-transitory" should not be interpreted that the memory (<NUM>) is non-movable. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in random access memory (RAM) or cache).

Although the <FIG> shows various hardware components of the UE (<NUM>) but it is to be understood that other embodiments are not limited thereon. In other embodiments, the UE (<NUM>) may include less or more numbers of components. Further, the labels or names of the components are used only for illustrative purpose and does not limit the scope of the invention. One or more components can be combined together to perform same or substantially similar function to handle the SI in the wireless communication system (<NUM>).

<FIG> is a flow chart (S200) illustrating a method for handling SI in a wireless communication system (<NUM>), according to embodiments as disclosed herein. The operations (S202-S208) are performed by the processor (<NUM>).

At S202, the method includes deciding that the UE (<NUM>) requires the at least one SIB from the plurality of SIBs indicated in the SI scheduling information broadcasted by the network (<NUM>). At S204, the method includes determining, from the plurality of SIBs, that the UE (<NUM>) does not have the stored SIB as required or the stored version of the required SIB exists but the stored version of the required SIB is not valid. At S206, the method includes checking that the UE (<NUM>) is allowed to send the SI request based on the network configuration. At S208, the method includes sending the SI request for the required SIB in response to checking that the UE (<NUM>) is allowed to send the SI request based on the network configuration.

Method <NUM>: SI request in the connected state based on only checking schedulingInfo.

The triggering for the SI request in the connected state shall be possible whenever the UE (<NUM>) wants to receive the SIB (e.g. positioning is activated, V2X is activated, etc.) which can happen any time. In the Release <NUM>, a radio resource control (RRC) specification i.e., TS <NUM>, the trigger for the SI request is determined while the UE (<NUM>) is performing SIB1 processing i.e., clause <NUM>. <NUM> titled as 'actions upon reception of the SIB1'. This works for determining the SI request when the UE (<NUM>) is in an idle/inactive state. However, when the UE (<NUM>) is in the connected state, the UE's active BWP may not be configured with the common search space, so that when the UE (<NUM>) decides to acquire the SIB (e.g. SIBx associated with V2X), the UE (<NUM>) cannot re-acquire the SIB1 from broadcast. Further, the UE (<NUM>) can be argued whether the gNB will always provide SIB1 in dedicated manner to the UE (<NUM>) whenever the gNB changes the broadcast status bit if the UE BWP is not configured with the common search space. The gNB will not do so if the rest of the SIB1 content is not updated and only the status of the broadcast bit is changed. In this case, the UE (<NUM>) shall be able to trigger the SI request procedure in clause <NUM>. <NUM> titled 'Request for on demand system information' in TS <NUM>, without the need to re-acquire SIB1 and checking the contents of the field si-SchedulingInfo in the stored SIB1 ignoring the status of broadcast bit. The status of the broadcast bit does not matter because after receiving the SI request from the UE (<NUM>), the gNB cannot broadcast the requested SIB(s) since the active BWP is not configured with common search space. The gNB will deliver the requested SIB(s) in dedicated RRC signaling upon receiving the SI request from the UE (<NUM>). The following clause needs to be introduced in Release <NUM> version of RRC specification, to allow the UE (<NUM>) to send SI request without the need to re-acquire SIB1 and by checking the contents of the field si-SchedulingInfo in the stored SIB1, when the active BWP is not configured with common search space.

OnDemandSibRequest indicator is included in the RRC Reconfiguration message and indicates that the UE (<NUM>) is allowed to send the SI request in connected state. In an embodiment, the OnDemandSibRequest indicator can be included in the SIB1.

If the onDemandSibRequest indicator included in the SIB1 indicates FALSE i.e., the UE (<NUM>) cannot send SI request in RRC_CONNECTED state, then the UE (<NUM>) acquires the SIB(s) required in the connected state in advance when the UE (<NUM>) is in the idle/inactive state.

If the onDemandSibRequest indicator included in RRCReconfiguration message indicates FALSE i.e., the UE (<NUM>) cannot send SI request in the RRC_CONNECTED state, then the UE (<NUM>) acquires the SIB(s) required in the CONNECTED state when the UE (<NUM>) transition to the idle/inactive regardless of the service is activated or not.

The method can be used to trigger the SI request to acquire SIB in the RRC_CONNECTED state when the UE active BWP is not configured with common search space is depicted in the <FIG>. In an example, as shown in the <FIG>, at S302, the method includes detecting that the UE (<NUM>) is in the RRC_CONNECTED mode. At S304, the method includes determining that the UE active BWP is not configured with the common search space. At S306, the method includes determining that the UE (<NUM>) does not have stored SIB or stored version of required SIB is not valid. At S308, the method includes determining the si-schedulingInfo in stored SIB1 to determine at least one required SIB. At S310, the method includes sending the SI request for the required SIB.

Alternately, since the UE's active BWP is not configured with the common search space, the required SIB(s) cannot be broadcasted. The gNB provides the SIB(s) identified as required in the connected state and supported in the cell in dedicated signaling to the UE (<NUM>) in an unsolicited manner. If the unsolicited delivery of SIB(s) identified as required in connected state is supported by the network (<NUM>) (duringUE (<NUM>) transition from idle/inactive to connected andPCell mobility) then there is no need for the UE (<NUM>) to make SI request in the RRC_CONNECTED state.

Method <NUM>: SI request in the connected state based on checking schedulingInfo and status of broadcast bit.

In the Release <NUM>, the RRC specification i.e., TS <NUM>, the trigger for SI request is determined while the UE (<NUM>) is performing the SIB1 processing i.e., clause <NUM>. <NUM> titled as 'actions upon reception of the SIB1'. This works for determining the SI request when the UE (<NUM>) is in idle/inactive state and the connected state when the UE's active BWP is configured with the common search space, so that when UE (<NUM>) is processing the received SIB1, UE can decide to acquire the SIB (e.g. SIBx associated with V2X), by executing clause <NUM>.

For example, assume that at time instant t1 when the UE (<NUM>) acquired SIB1 (either broadcast or dedicated) the scheduling info included V2X SIB related info. Since the UE (<NUM>) was not interested in the V2X while executing clause <NUM>. <NUM> at time instant t1, the UE did not take any action. At time instant t1+T, the UE (<NUM>) is interested in the V2X service and the UE (<NUM>) requires the V2X SIB. If t1+T is within the modification period N in which the UE (<NUM>) has acquired SIB1 (i.e., t1 and t1+T corresponds to same modification period) then the stored SIB1 acquired at time instant t1 is still valid. The UE (<NUM>) can re-process the stored SIB1 acquired at time instant t1 to decide whether to trigger SI request. The triggering for SI request in the connected state shall be possible whenever the UE (<NUM>) wants to receive the SIB (e.g. positioning is activated, V2X is activated, etc.) which can happen any time during the modification N. However, according to Release-<NUM> RRC specification, checking of si-schedulingInfo for triggering the SI request is performed when the SIB1 is acquired by the UE (<NUM>) while executing clause <NUM>. So, there is a need to at least specify that before triggering SI request for required SIBs the UE (<NUM>) shall check the scheduling info in valid version of SIB1. In this case, the UE (<NUM>) shall be able to trigger SI request procedure in clause <NUM>. <NUM> titled 'Request for on demand system information' in TS <NUM>, by checking the contents of the field si-SchedulingInfo and the status of broadcast bit in the stored valid version of SIB1. The following clause needs to be introduced in Release <NUM> version of RRC specification to allow the UE (<NUM>) to send SI request by checking the contents of the field si-SchedulingInfo in the stored valid version of SIB1 to determine if the SIB is supported in the cell.

In an embodiment, <NUM>. 3x Actions upon the need to acquire SIB in the connected state.

This means the status can be changed from not broadcasting to broadcasting anytime within the modification period. If the status is changed to broadcasting, then the network (<NUM>) starts broadcasting the concerned SIB. However, this change in status of the broadcast bit does not result in SI change notification and hence there is no trigger for the UE (<NUM>) to re-acquire SIB1. If some UE (<NUM>) which had acquired SIB1 at time instance t1 when the status was notbroadcasting, that UE (<NUM>) will send SI request at time instance t1+T< N assuming acquired SIB1 is valid. There is no problem with this because the UE (<NUM>) after sending the SI request will acquire the concerned SIB from either broadcast or the gNB will deliver the SIB requested by the UE (<NUM>) in the dedicated RRC signaling.

This holds true for using stored SIB1 acquired in a modification period for deciding to send SI request in that modification period itself and there is no need to re-acquire SIB1. Therefore, if the UE (<NUM>) need a SIB in RRC_CONNECTED at any time during a modification period N, the UE (<NUM>) can check SIB1 acquired at the beginning of that modification period N to order to determine SI request transmission. However, with respect to broadcast bit, SIB1 acquired in modification period N is not valid for the SI request in the modification period N+<NUM> i.e., t1+T >N. For example, in modification period N, broadcast bit can be set to broadcasting. In modification period N+<NUM>, the broadcast bit is set to notBroadcasting. In the si-schedulingInfo if only broadcast bit is changed in modification period N+<NUM> compared to modification period N, the network (<NUM>) will neither send SI change notification nor SIB1 in dedicated manner to the UE (<NUM>). The UE (<NUM>) cannot use stored SIB1 acquired in modification period N to decide to send SI request because if it follows, the UE (<NUM>) will not send SI request as broadcast bit is set to broadcasting in modification period N and hence the UE (<NUM>) will fail to acquire required SIB as network is not broadcasting the desired SIB in modification period N+<NUM>. In such case the UE (<NUM>) shall re-acquire SIB1 from broadcast in modification period N+<NUM> and check broadcast status bit (i.e., at t1+T >N). This is possible for the case where common search space is configured. If common search space is not configured and the UE (<NUM>) has not previously acquired SIB1 in modification period N+<NUM>, it needs to send SI request without checking broadcast status bit based on the stored SIB1 acquired in modification period N (i.e., according to Method <NUM>).

The method can be used to trigger the SI request to acquire SIB in the RRC_CONNECTED state when the UE active BWP is configured with common search space is depicted in the <FIG>. In an example, as shown in the <FIG>, at S402, the method includes detecting that the UE (<NUM>) is in the RRC connected mode. At S404, the method includes determining that the UE active BWP is configured with common search space. At S406, the method includes determining that the UE (<NUM>) does not have stored SIB or stored version of required SIB is not valid. At S408, the method includes checking if the stored SIB1 is acquired in same modification period. If the stored SIB1 is not acquired in same modification period then, at S410, the method includes re-acquiring the SIB1 from broadcast. If the stored SIB1 is acquired in same modification period then, at S412, the method includes checking the Si-schedulingInfo and si-BroadcastStatus in stored SIB1. At S414, the method includes acquiring the required SIBs from broadcast if si- BroadcastStatus is 'broadcasting'. At S416, the method includes sending the SI request for the required SIB(s) if si- BroadcastStatus is 'notbroadcasting'.

The following updates needs to be introduced in clause <NUM>. <NUM> in Release <NUM> version of RRC specification to allow the UE (<NUM>) to re-acquire SIB1 when the UE's active BWP is configured with common search space and the UE (<NUM>) need to check the status of broadcast bit in modification period N+<NUM> if the stored SIB1 is acquired in modification N or earlier.

Alternately, the clause <NUM>. 3x actions upon the need to acquire SIB in the CONNECTED state, can be updated as follows:
The UE (<NUM>) shall:.

Alternately, the clause <NUM>. 3x, actions upon the need to acquire SIB in CONNECTED state, can be updated as follows.

Method <NUM>: Status of broadcast bit is notBroadcasting and FLAG in RRCReconfig is FALSE.

If common search space to receive the system information is configured on the active BWP, the UE (<NUM>) is in the RRC_CONNECTED checks whether the required on-demand SI is being broadcasted by reading SIB1 before transmitting the SI request, and transmits the SI request only when the required on-demand SI is not being broadcasted, as in RRC_IDLE/INACTIVE. In addition to the broadcast status bit in the SIB1, another explicit network indication (i.e., FLAG) is included RRCReconfiguration message in order to inform the UE (<NUM>) whether the on-demand SIB request in the RRC_CONNECTED is supported. The UE behavior when the active BWP is configured with common search space should be clear if the UE (<NUM>) receives the FLAG included RRCReconf igurat ion message and when UE (<NUM>) checks the broadcast status bit in SIB1.

The field description of si-BroadcastStatus bit states: "Indicates if the SI message is being broadcasted or not. Change of si-BroadcastStatus should not result in system information change notifications in Short Message transmitted with P-RNTI over DCI (see clause <NUM>). The value of the indication is valid until the end of the BCCH modification period when set to broadcasting".

The field description of onDemandSibRequest FLAG included in the RRCReconfiguration states: "Indicates whether the UE (<NUM>) is allowed to request SIBs on-demand while in RRC_CONNECTED state" as indicated in [Table <NUM>].

The UE behavior for cases <NUM>, <NUM> and <NUM> is shown in the <FIG>. In an example, as shown in the <FIG>, at S502, the method includes detecting that the UE (<NUM>) is in the RRC connected mode. At S504, the method includes determining that the UE active BWP is configured with common search space. At S506, the method includes determining that the UE (<NUM>) does not have stored SIB or stored version of required SIB is not valid. At S508, the method includes checking if the stored SIB1 is acquired in same modification period. If the stored SIB1 is not acquired in same modification period then, at S510, the method includes re-acquiring the SIB1 from broadcast. If the stored SIB1 is acquired in same modification period then, at S512, the method includes check Si-schedulingInfo and si-BroadcastStatus in stored SIB1. At S514, the method includes acquiring the required SIB(s) from broadcast if si-BroadcastStatus is 'broadcasting'. At S516, the method includes sending the SI request for the required SIB(s) if si-BroadcastStatus is 'notbroadcasting' AND onDemandSibRequest is 'TRUE''.

For the case when active BWP is not configured with common search space, the UE (<NUM>) sends the SI request according to method <NUM> if onDemandSibRequest FLAG included in RRCReconfiguration message is set as TRUE as depicted in the <FIG>. As shown in the <FIG>, at <NUM>, the method includes detecting that the UE (<NUM>) is in the RRC connected mode. At <NUM>, the method includes determining that UE active BWP is not configured with common search space. At <NUM>, the method includes determining that the UE (<NUM>) does not have stored SIB or stored version of required SIB is not valid. At <NUM>, the method includes checking si-schedulingInfo in stored SIB1 to determine at least one required SIB. At <NUM>, the method includes sending the SI request for the required SIB(s) if the onDemandSibRequest is TRUE.

The various actions, acts, blocks, steps, or the like in the flow diagrams (S200-S600) may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some of the actions, acts, blocks, steps, or the like may be omitted, added, modified, skipped, or the like without departing from the scope of the invention.

The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the elements.

Claim 1:
A method performed by a user equipment, UE, (<NUM>) in a wireless communication system, the method comprising:
receiving, from a base station, scheduling information associated with system information, SI;
receiving, from the base station, a radio resource control, RRC, reconfiguration message including an onDemandSibRequest indicator;
identifying whether an active bandwidth part, BWP, is not configured with a common search space;
identifying that the UE (<NUM>) has not stored a valid version of a system information block, SIB, from one or more SIBs; and
transmitting, to the base station, a request message to request required at least one SIB, in case that the active BWP is not configured with the common search space,
wherein the UE (<NUM>) is in a RRC connected state.