Patent Description:
Presently, 5th generation New Radio (NR) wireless systems, abbreviated <NUM> NR, offer improved wireless network technologies. <NUM> NR includes such technologies as millimeter wave bands, such as <NUM>, <NUM>, <NUM>, and <NUM> and can offer theoretical throughput as high as <NUM> gigabits per second, with median bandwidth being approximately <NUM> gigabits. <NUM> NR can utilize Multiple Input Multiple Output (MIMO), for example <NUM>-<NUM> antennas, to provide up to ten times the performance of <NUM>th generation (<NUM>) networks. To achieve such higher throughput, <NUM> NR aims to reduce signaling overhead. One such reduction occurs during initial interaction between a wireless device and a network entity within a cell. In order to reduce the signaling overhead for the provisioning of System Information (SI), the concept of so-called "minimum System Information" has been introduced for NR. The minimum System Information (SI) can contain basic information for initial access to the cell.

This includes a proposal as to the parameters that should be periodically broadcasted as minimum SI. <NPL> and describes a proposal for delivering on-demand system information. <NPL>is and continues to discuss the leftover issue from the SI phase as to the requesting scheme of on-demand SIB(s), i.e. Msg. <NUM> vs Msg.

Claim <NUM> defines a method and claim <NUM> defines an apparatus. In the following, any method and/or apparatus referred to as embodiments but nevertheless do not fall within the scope of the appended claims are to be understood as examples helpful in understanding the invention.

In order to describe the manner in which advantages and features of the disclosure can be obtained, a description of the disclosure is rendered by reference to specific embodiments thereof which are illustrated in the appended drawings. These drawings depict only example embodiments of the disclosure and are not therefore to be considered to be limiting of its scope. The drawings may have been simplified for clarity and are not necessarily drawn to scale.

Embodiments provide a method and apparatus for signaling of system information. According to a possible embodiment, minimum system information including at least cell access information to establish access with a cell can be received, the minimum system information also including at least one indication indicating whether particular system information listed in scheduling information in the minimum system information is being broadcasted or not being broadcasted. A system information request message requesting transmission of non-minimum system information if the at least one indication indicates the non-minimum system information is not being broadcasted can be transmitted, where the non-minimum system information is not included in the minimum system information. The non-minimum system information either in response to the transmitting of the system information request message or in response to the at least one indication indicating whether particular system information is being broadcasted can be received.

<FIG> is an example block diagram of a system <NUM>, according to a possible embodiment. The system <NUM> can include a User Equipment (UE) <NUM>, at least one of network entities <NUM> and <NUM>, such as a base station, and a network <NUM>. The UE <NUM> can be a wireless wide area network device, a user device, wireless terminal, a portable wireless communication device, a smartphone, a cellular telephone, a flip phone, a personal digital assistant, a personal computer, a selective call receiver, an Internet of Things (IoT) device, a tablet computer, a laptop computer, or any other user device that is capable of sending and receiving communication signals on a wireless network. The at least one of network entities <NUM> and <NUM> can be wireless wide area network base stations, can be NodeBs, can be enhanced NodeBs (eNBs), can be New Radio NodeBs (gNBs), such as <NUM> NodeBs, can be unlicensed network base stations, can be access points, can be base station controllers, can be network controllers, can be Transmission/Reception Points (TRPs), can be different types of base stations from each other, and/or can be any other network entities that can provide wireless access between a UE and a network.

The network <NUM> can include any type of network that is capable of sending and receiving wireless communication signals. For example, the network <NUM> can include a wireless communication network, a cellular telephone network, a Time Division Multiple Access (TDMA)-based network, a Code Division Multiple Access (CDMA)-based network, an Orthogonal Frequency Division Multiple Access (OFDMA)-based network, a Long Term Evolution (LTE) network, a 3rd Generation Partnership Project (3GPP)-based network, a satellite communications network, a high altitude platform network, the Internet, and/or other communications networks. In a possible embodiment, the network entity <NUM> and the UE <NUM> can be included in a cell <NUM>, the network entity <NUM> can be included in another cell <NUM>, and the network entities <NUM> and <NUM> can be coupled via the network <NUM>.

In operation, the UE <NUM> can communicate with the network <NUM> via the network entity <NUM>. For example, the UE <NUM> can send and receive control signals on a control channel and user data signals on a data channel.

The system <NUM> can reduce the signaling load for the provisioning of System Information, the concept of so-called "minimum System Information" which has been introduced for New Radio (NR). The minimum System Information (SI) <NUM> can contain basic information for initial access to the cell <NUM> and can include such information as Management Information Base (MIB) and can include SIB <NUM> information, such as Subframe Number (SFN), list of Public Land Mobile Network (PLMN), cell camping parameters, and Random Access Channel (RACH) parameters. The minimum SI <NUM> can be broadcast periodically in the cell <NUM>, whereas other "non-minimum" SI <NUM> does not necessarily need to be periodically broadcast, and the network <NUM> can decide whether such information is to be periodically broadcast. To obtain the non-minimum SI <NUM>, the UE <NUM> can transmit an SI request message <NUM> to the network <NUM>, via the network entity <NUM>, to request the non-minimum SI <NUM>. The network <NUM> can transmit, via the network entity <NUM>, the non-minimum SI <NUM> to the UE <NUM>. The non-minimum SI <NUM> can be provided on-demand to the UE <NUM>, that is the UE <NUM> can request the non-minimum SI <NUM> via the SI request message <NUM>. Delivery of the non-minimum SI <NUM> can also be done by broadcast or unicast manner. The minimum SI <NUM> can include system information scheduling information and can indicate whether a specific system information, such as an SI block (SIB) that can be periodically broadcasted or provided on-demand. The non-minimum SI <NUM> can include multiple SIBs. The particular system information (not SI) can be broadcast at least in a SIB and can also be broadcast in an SI message including at least one SIB. For example, one SI message can include one or more SIBs. The system information can be provided in a SIB or other system information message, such as a message that includes at least one SIB.

In order to obtain the one or more SIBs which are not periodically broadcasted and are provided on-demand, UE <NUM> can initiate an on-demand SI acquisition procedure. For SI required by the UE <NUM>, the UE <NUM> can know whether it is available in the cell <NUM> and whether the SI is broadcast or not before the UE <NUM> can send the SI request message <NUM>, that is the UE <NUM> can first acquire the minimum SI <NUM>. Scheduling information for other SI can be provided by the minimum SI <NUM>, such as in a SIB1, can include SIB type, validity information, periodicity, and an SI-window information. The UE <NUM> in idle and an inactive state can transmit the SI request message <NUM> requesting the non-minimum SI <NUM> without state transition using an MSG1 and/or MSG3-based approach. For a connected UE <NUM>, dedicated Radio Resource Control (RRC) signaling can be used for the SI request message <NUM> and delivery of the non-minimum SI <NUM>. In an example, the UE <NUM> can transmit the SI request message <NUM> in physical layer Random Access Preamble (RAP), in a Medium Access Control (MAC), or in an RRC message, for example as an MSG1 and/or MSG3, such as when the UE <NUM> is in the idle state, or when the UE <NUM> is in the connected state.

MSG1 based signaling can rely on association between one or more reserved preambles and a corresponding set(s) of SIB(s). To request multiple SIB(s) belonging to a different set, the UE <NUM> can transmit/initiate corresponding MSG1 transmissions.

The system <NUM> can provide a signaling-structure for requesting SIBs using an MSG3 and dedicated signaling. A poorly designed signaling-structure can run a risk of misinterpretation if certain SIBs' scheduling changes in-between the UE <NUM> transmission and the network <NUM> reception of the signaling-structure requesting the SIBs. This may not only delay the acquisition of certain SIB(s) in the UE <NUM> but also the network <NUM> can unnecessarily broadcast certain SIB(s) that were actually not even requested. Another fallout of a poorly designed signaling-structure could be that the signaling-structure itself is quite inefficient/ big and thereby result in a reduction of chances of a quick and successful transmission.

<FIG> is an example scenario <NUM> showing transmission of SI messages, according to a possible embodiment. In LTE, system information except MIB and SIB1 can be transmitted in so called SI messages. The SI messages can be transmitted within periodically occurring time domain windows, which can be referred to as SI-windows, using dynamic scheduling. Each SI message can be associated with an SI-window and the SI-windows of different SI messages may not overlap. That is, within one SI-window only the corresponding SI can be transmitted. The length of the SI-window can be common for all SI messages and can be configurable. Within the SI-window, the corresponding SI message can be transmitted a number of times. The UE <NUM> can acquire detailed time-domain scheduling, and can acquire other information, e.g. frequency-domain scheduling, used transport format, from decoding SI-Radio Network Temporary Identifier (RNTI) on a Physical Downlink Control Channel (PDCCH).

Further, in NR the scheduling information for SI can be provided by the minimum SI <NUM>, such as in SIB1, and may include SIB type, validity information, periodicity, SI-window information and an indication whether the particular SIB-type is broadcasted or not. Though the embodiments reference a SIB, the actual network may provide them in SI-messages, such as in LTE. Two schemes can be available as follows:
Scheme-<NUM>: Only one indication, such as a Boolean Flag, can be used to indicate if a particular SIB is being broadcasted by the cell <NUM> "now" or not. By "now", the UE <NUM> has some time/possibility to acquire the particular SIB after having received the Boolean Flag. If the UE <NUM> interested in the particular SIB sees from the Boolean Flag that the SIB is not broadcasted now, then the UE <NUM> can request, via the SI request message <NUM>, the particular SIB from the network <NUM>.

Scheme-<NUM>: This scheme can use two indications, such as two Boolean flags. The first of these two flags can indicate that the particular SIB is "regularly broadcasted" or provided "on-demand". The second flag in the Scheme-<NUM> can have the same meaning as the Boolean Flag in Scheme-<NUM> but can be applicable only to the on-demand SIBs as indicated by the first Flag of Scheme-<NUM>.

<FIG> is an example scenario <NUM> showing toggling of a "Broadcast Now" Boolean Flag, according to a possible embodiment. The network <NUM> can toggle the "Broadcasted now" flag in any schemes, such as Scheme-<NUM> and/or Scheme-<NUM>, upon receiving the SI request message <NUM> from the UE <NUM> to provide the SIB to indicate that the SIB is subsequently provided/broadcasted (e.g. Broadcasted Now = True). The network <NUM> can toggle the Boolean Flag back when the network <NUM> has provided/ broadcasted the SIB for a sufficiently long time, for example until an end of a current modification period as described by 3GPP TS <NUM>-e30 section <NUM>. <NUM>, such as by resetting the Broadcasted Now flag to False. In a possible embodiment, an indication can be used to indicate if a SIB or SI message is being broadcasted now in the current modification period. If the indication indicates that a particular SIB/SI message is broadcasted now, the network shall broadcast that SIB/SI until the end of the current modification period and the UE <NUM> thereby can have opportunities until the end of current modification period to acquire the SIB/SI. In an example embodiment, one indicator in SIB1 can indicate whether an SI message is currently being broadcast or not. The indication shall be valid until an end of the current modification period. For example, the network <NUM> can guarantee to the UE <NUM> that when a particular non-minimum SI is indicated as being broadcasted, the particular non-minimum SI <NUM> can be broadcasted until an end of the current modification period in which it is indicated as being broadcasted.

<FIG> is an example signaling structure <NUM> for requesting SIBs, such as a SIB or SI request, according to a possible embodiment. For a first solution, the UE <NUM> can request SIBs by listing each SIB-type separately, such as illustrated in signaling solution <NUM>. The system information can comprise a system information message, where the system information request message can comprise a list of one or more of a unique system information message for the requested non-minimum system information, such as the list illustrated in the signaling structure <NUM>. According to a possible embodiment, the SI request message <NUM> can include this signaling solution <NUM>. For example, if the maximum number of SIBs is <NUM>, but even if the UE <NUM> is requesting only <NUM> SIBs, the UE <NUM> would need to use <NUM>*<NUM> = <NUM> Bits (<NUM>^<NUM>=<NUM>). For example, the number of bits needed within the SI request message <NUM> for non-minimum SI <NUM> can be the number of requested SIBs multiplied by <NUM> due to the fact that <NUM>^<NUM>=<NUM> bits that are necessary to indicate each of the maximum number of <NUM> SIBs.

According to another possible embodiment, another signaling structure that can be included within the SI request message <NUM> for non-minimum SI <NUM>, such as a SIB or SI request can include use of a BITMAP. The UE <NUM> can send the SI request message <NUM> that includes the BITMAP to the network <NUM>.

In an example embodiment, bits in the BITMAP can represent either SIBs or SI messages. In a possible implementation, the bits of the BITMAP can represent SI messages and these bits can be the SI messages indicated in the scheduling information in SIB1 of the current cell. The UE <NUM> can determine the SI message(s) based for the SIB(s) that it needs based on the corresponding scheduling information in SIB1.

In another example implementation, the bits of the BITMAP can represent SIBs, sequentially. In this example embodiment, no indication is required in a broadcast message to indicate whether the other/non-minimum SIBs are provided via periodic broadcast basis or only on-demand basis. In this case, bits in the BITMAP represent SIBs sequentially starting with a first bit for the first SIB that is carried in SI Messages, such as SIB2, a second bit for the second SIB that is carried next in the same or next SI messages, such as SIB3, and so on.

In another example implementation, the bits of the BITMAP can represent SIBs,, sequentially, where the SIBs as numbered in the 3GPP specification <NUM> of future versions. As an example of this embodiment, if there are total <NUM> SIBs in NR, then BIT1 of the BITMAP can represent SIB2, BIT2 of the BITMAP can represent SIB3. , BIT24 of the BITMAP can represent SIB25.

In a further example embodiment, bits in the BITMAP can represent SIBs sequentially starting with a first bit for a first SIB that can be indicated as being provided on on-demand basis in the current cell, then a second bit for a second SIB that can be indicated as being provided on on-demand basis in the cell <NUM>, and so on. A length of the BITMAP can be set to a maximum number of specified SIBs or to the number of SI messages broadcasted in the cell <NUM>.

For example, the BITMAP can be a same length as number of SIBs defined in NR, can be a same length as number of SIBs supported in the cell <NUM>, can be the number of SI messages broadcasted in the cell <NUM> or can be a longer value, such as <NUM> bits to account for future SIBs and/ or SI messages. If the BITMAP is <NUM> bits but we only have a total of <NUM> SIBs in NR or <NUM> SI messages broadcasted in the cell, then BIT1 of the BITMAP represents SIB2/SI message1, BIT2 of the BITMAP represents SIB3/ SI message2. , BIT24 of the BITMAP represents SIB25/SI message24. The remaining bits, if any in the BITMAP, such as BIT25 to BIT40 in a <NUM>-bit BITMAP, can be set to '<NUM>' or '<NUM>' by the UE <NUM> and can be ignored by the network entity <NUM> in any of the embodiments.

According to another possible embodiment, the network <NUM> may configure the length of the BITMAP based on the SIB-types the network <NUM> can broadcast. In addition to these, the BITMAP length may have provision for some additional bits for future use. One bit in the BITMAP can correspond to one SIB request. The BITMAP may be interpreted by the network <NUM> from the left to right, or right to left, such that the first bit in the BITMAP can correspond to the lowest SIB-type being requested, a next bit in the BITMAP can correspond to a next higher SIB-type being requested, and so on. In another possible embodiment, the BITMAP may be interpreted by the network <NUM> from the left to right, or right to left, such that the first bit in the BITMAP can correspond to the highest SIB-type being requested, a next bit in the BITMAP can correspond to a next lower SIB-type being requested, and so on. With these principles in mind, the following three sub-solutions can be implemented by the network <NUM>.

BITMAP-Solution A: One bit can be included within the BITMAP for each SI-message irrespective of if particular SI messages are "regularly" broadcasted or transmitted on-demand by the network <NUM>.

BITMAP-Solution B: One bit can be included within the BITMAP only for each of those SI-messages that are indicated as to be provided on-demand, for example statically, such as irrespective of if these SI-messages are being provided/ broadcasted at a moment by the network <NUM>.

BITMAP-Solution C: One bit can be included within the BITMAP only for each of those SI-messages that are indicated as to be provided on-demand by the network <NUM> but are NOT being provided/ broadcasted at the moment, such as dynamic toggling of bits, by the network <NUM>.

The following tables can be used for Scheme-<NUM> and Scheme-<NUM>.

As can be seen from the above tables, the BITMAP-Solution A can avoid misinterpretation due to a time lag between initial transmission by the UE <NUM> and actual reception time at the network <NUM> after possibly more than <NUM> Hybrid Automatic Repeat Request. (HARQ) (re)transmissions and also can need only <NUM> Broadcast bit, for example, Scheme-<NUM> is sufficient.

For example, 3GPP can specify SIB1 to SIB10. SIB2-SIB10 can be provided by the network <NUM> in SI messages from the 3GPP perspective. Out of these <NUM> SIBs, the cell <NUM> may only provide/support SIBs <NUM>, <NUM>, <NUM>, <NUM> and <NUM>. This means that SIBs <NUM>, <NUM>, <NUM>, <NUM> may not be provided/supported by the cell <NUM>. Therefore, in the scheduling info in SIB1 only SIBs <NUM>, <NUM>, <NUM>, <NUM> and <NUM> are listed. Out of these, for example SIBs <NUM>, <NUM> and <NUM> can be indicated as being broadcasted or guaranteed to be broadcasted until the current modification period boundary and SIBs <NUM> and <NUM> can be indicated as not being broadcasted, such as when the flag-indication for both these is FALSE. The UE <NUM> may only request SIB <NUM> and SIB <NUM>. The UE <NUM> may not be allowed/supposed to request any of SIBs <NUM>, <NUM>, <NUM>, <NUM>.

For the network behavior associated with BITMAP-Solution A, the network <NUM> can regularly broadcast certain SIBs and the SI request message <NUM> can show these SIBs as "required". Then the SI request message <NUM> for such SIBs can be ignored by the network <NUM> since the network <NUM> may continue to regularly broadcast these SIBs. The on-demand SIBs including the non-minimum SI <NUM> that are not broadcasted can now be broadcasted subsequently.

For UE behavior associated with BITMAP-Solution A, the UE <NUM> can use a first 'N' bits in the BITMAP where N is the number of SIBs (or in practice the SI-message) indicated in the scheduling information. For SIBs that are indicated as "Broadcasted Now = true", the UE <NUM> can acquire the ones it needs. For other SIBs indicated as "Broadcasted Now = false", the UE <NUM> can determine which of these SIBs it needs and then set these bits to a predefined value, such as a true meaning requested, to indicate to the network <NUM> that these SIBs are requested. Upon confirmation/ feedback from the network <NUM> that these SIBs are provided, the UE <NUM> can acquire them.

As an additional enhancement for the MSG1 based SI request message <NUM>, if in a particular cell/network, SIBs A to H are provided on an on-demand basis and the network <NUM> configures four preambles to request the SIBs as follows:.

<FIG> is an example illustration of a second option <NUM> for a UE <NUM> to request its needed SIBs, according to a possible embodiment. In the second option <NUM> the feedback message, such as the RAR, is scheduled on one single common RNTI, such as a Random Access (RA)-RNTI, and carries a list of received preambles to indicate the corresponding SIBs that the network <NUM> is going to provide in response to possibly more than one requesting UE <NUM>.

In the second option <NUM>, the UE <NUM> need not send separate SI-requests/Preambles to request SI-messages grouped separately, saving uplink (UL) transmission/battery and optimizing UL interference/collisions. Moreover, the network <NUM> need not send a feedback/response to each of the requests, saving downlink (DL) transmission/resources. Furthermore, the second option <NUM> saves RNTIs space and further, RA-RNTI calculation may not be required. Also, compared against the MAC RAR, none of the fields in MAC RAR payload are required, that is none of timing advance command, UL grant, or temporary Cell (C)-RNTI. The system <NUM> can eliminate transmission of the MAC RAR and allows for DL signaling reduction.

The MSG2, that is feedback from MSG1, can consist of only Extension (E)/Type (T)/ Random Access Preamble IDentitfier (RAPID) MAC sub-header and some of reserved Preambles, such as RAPIDs, that are configured by the network <NUM> to be associated with a corresponding MAC RAR. In one example, Preamble <NUM> (= SIBs G, H) can be configured by the network <NUM> to be associated with a corresponding MAC RAR and when the MAC sub-header has RAPID = Premable <NUM>, then the UE <NUM> can further receive a MAC RAR, such as a Physical Downlink Shared Channel (PDSCH). This MAC RAR can contain part or whole of either/both SIBs G, H. The "part" could correspond to the new changes in that SIB compared to a previous transmitted version.

Additionally, instead of configuring some of the reserved Preamble for a MAC RAR reception, an explicit indication in the MAC sub-header itself can be used, such as a one-bit Boolean flag. This Boolean flag indicating if a MAC RAR is transmitted, signals the UE <NUM> to receive a corresponding MAC RAR, such as a PDSCH transmission. This MAC RAR can contain part or whole of the any one or more SIBs A to SIB H.

<FIG> is an example flowchart <NUM> illustrating operation of an apparatus such as a wireless communication device, for example the UE <NUM>, according to a claimed embodiment. At <NUM>, the minimum SI <NUM> including at least cell access information to establish access with a cell can be received. The minimum SI <NUM> can also include at least one indication indicating whether particular system information listed in scheduling information in the minimum SI <NUM> is being broadcasted or not being broadcasted. According to a possible embodiment, the at least one indication can be a Boolean flag. According to a possible embodiment, the at least one indication can include a first indication, and according to the claimed embodiment the minimum system information includes a second indication indicating whether the particular system information listed in the scheduling information in the minimum system information is regularly broadcast or provided to the user equipment on-demand. Transmitting the system information request message includes transmitting the system information request message in response to the second indication indicating that the particular on-demand system information not being currently broadcast and the second indication indicating the particular system information is provided on-demand. According to a possible embodiment, the system information can include a system information message, where the system information request message can include a list of one or more of a unique system information message for the requested non-minimum system information.

In the claimed embodiment, the SI request message <NUM> includes a BITMAP, where each bit in the BITMAP can each correspond to a unique system information message for the requested non-minimum system information. In a possible embodiment, each bit of the BITMAP can indicate a different system information message or a different system information block. In the claimed embodiment, a leftmost bit of the BITMAP corresponds to a lowest valued unique system information message type requested, a rightmost bit of the BITMAP corresponds to a highest valued unique system information message type requested, and bits ordered from the leftmost bit to the rightmost bit are ordered in accordance with increased valued minimum information requested. In a possible embodiment, each bit in the BITMAP can correspond to particular system information irrespective of if the particular system information is regularly broadcasted or on-demand. In a possible embodiment, each bit in the BITMAP can correspond to only particular system information that is indicated as being provided on-demand. In a possible embodiment, each bit in the BITMAP can correspond to only particular system information that is indicated as being provided on-demand and not being currently provided to the user equipment. In a possible embodiment, only selected bits of the BITMAP, where the selected bits indicate system information that is not being broadcast and required by the user equipment, can be set by the UE <NUM>.

At <NUM>, the SI request message <NUM> requesting transmission of the non-minimum SI <NUM> can be transmitted. According to a possible embodiment, this transmission can occur if the at least one indication indicates the non-minimum SI <NUM> is not being broadcasted, where the non-minimum SI <NUM> is not included in the minimum SI <NUM>. At <NUM>, the non-minimum SI <NUM> can be received either in response to the transmission of the SI request message <NUM> at <NUM> or in response to the at least one indication indicating whether particular SI is being broadcasted.

<FIG> is an example flowchart <NUM> illustrating operation of an apparatus such as a network entity, for example the network entity <NUM>, according to a possible embodiment. At <NUM>, the minimum SI <NUM> including at least cell access information to establish access with a cell can be transmitted. The minimum SI <NUM> can also include at least one indication indicating whether particular SI listed in the scheduling information in the minimum SI <NUM> is being broadcasted or not being broadcasted. According to a possible embodiment, the at least one indication can be a Boolean flag as described above and in <NUM>. In a possible embodiment, the SI request message <NUM> can comprise a BITMAP, as described above and in element <NUM> above.

At <NUM>, the SI request message <NUM> requesting transmission of the non-minimum SI <NUM> can be received. According to a possible implementation, this reception by the network entity <NUM> can occur if the at least one indication indicates the non-minimum SI <NUM> is not being broadcasted, where the non-minimum SI <NUM> is not included in the minimum SI <NUM>.

At <NUM>, the non-minimum SI <NUM> can be transmitted either in response to the receiving of the SI request message <NUM> at <NUM> or in response to the at least one indication indicating whether particular SI listed in the scheduling information in the minimum SI <NUM> is being broadcasted.

<FIG> is an example flowchart <NUM> illustrating another operation of the wireless communication device, for example the UE <NUM>, according to a possible embodiment. At <NUM>, the minimum SI <NUM> including at least cell access information to establish access with a cell can be received.

At <NUM>, the SI request message <NUM> requesting transmission of the non-minimum SI <NUM> can be transmitted, where the SI request message <NUM> can include a BITMAP. According to a possible implementation, each bit in the BITMAP can correspond to a unique SI message for the requested non-minimum SI <NUM>, where the non-minimum SI <NUM> is not included in the minimum SI <NUM>. In a possible embodiment, the BITMAP can include the features described above and in <NUM>.

At <NUM>, the non-minimum SI <NUM> can be received in response to the transmission of the SI request message including the BITMAP at <NUM>.

<FIG> is another example flowchart <NUM> illustrating another operation of a network entity, for example the network entity <NUM>, according to a possible embodiment. At <NUM>, the minimum SI <NUM> including at least cell access information to establish access with the cell <NUM> can be transmitted. According to a possible implementation, the minimum SI <NUM> can also include at least one indication indicating whether particular SI listed in scheduling information in the minimum SI <NUM> is being broadcasted or not being broadcasted.

At <NUM>, the SI request message <NUM> requesting transmission of the non-minimum SI <NUM> can be received. According to a possible implementation, the SI request message <NUM> can include a BITMAP where each bit in the BITMAP corresponds to a unique SI message for the requested non-minimum SI <NUM>, where the non-minimum SI <NUM> is not included in the minimum SI <NUM>. In a possible embodiment, the BITMAP can include the features described above and in <NUM>.

At <NUM>, the non-minimum SI <NUM> can be transmitted in response to the receiving of the SI request message <NUM> including the BITMAP at <NUM>.

<FIG> is an example block diagram of an apparatus <NUM>, such as the UE <NUM>, the network entity <NUM>, the network entity <NUM>, any of the entities within the network <NUM>, and/or any other wireless or non-wireless communication device disclosed herein, according to a possible embodiment. The apparatus <NUM> can include a housing <NUM>, a controller <NUM> coupled to the housing <NUM>, audio input and output circuitry <NUM> coupled to the controller <NUM>, a display <NUM> coupled to the controller <NUM>, a transceiver <NUM> coupled to the controller <NUM>, at least one antenna <NUM> coupled to the transceiver <NUM>, a user interface <NUM> coupled to the controller <NUM>, a memory <NUM> coupled to the controller <NUM>, and a network interface <NUM> coupled to the controller <NUM>. The apparatus <NUM> may not necessarily include all of the illustrated elements for different embodiments of the present disclosure. The apparatus <NUM> can perform the methods described in all the embodiments.

The display <NUM> can be a viewfinder, a Liquid Crystal Display (LCD), a Light Emitting Diode (LED) display, an Organic Light Emitting Diode (OLED) display, a plasma display, a projection display, a touch screen, or any other device that displays information. The transceiver <NUM> can be one or more transceivers that can include a transmitter and/or a receiver. The audio input and output circuitry <NUM> can include a microphone, a speaker, a transducer, or any other audio input and output circuitry. The user interface <NUM> can include a keypad, a keyboard, buttons, a touch pad, a joystick, a touch screen display, another additional display, or any other device useful for providing an interface between a user and an electronic device. The network interface <NUM> can be a Universal Serial Bus (USB) port, an Ethernet port, an infrared transmitter/receiver, an IEEE <NUM> port, a wireless transceiver, a WLAN transceiver, or any other interface that can connect an apparatus to a network, device, and/or computer and that can transmit and receive data communication signals. The memory <NUM> can include a Random Access Memory (RAM), a Read Only Memory (RON), an optical memory, a solid state memory, a flash memory, a removable memory, a hard drive, a cache, or any other memory that can be coupled to an apparatus.

The apparatus <NUM> or the controller <NUM> may implement any operating system, such as Microsoft Windows®, UNIX®, or LINUX®, Android™, or any other operating system. Apparatus operation software may be written in any programming language, such as C, C++, Java or Visual Basic, for example. Apparatus software may also run on an application framework, such as, for example, a Java® framework, a. NET® framework, or any other application framework. The software and/or the operating system may be stored in the memory <NUM> or elsewhere on the apparatus <NUM>. The apparatus <NUM> or the controller <NUM> may also use hardware to implement disclosed operations. For example, the controller <NUM> may be any programmable processor. Disclosed embodiments may also be implemented on a general-purpose or a special purpose computer, a programmed microprocessor or microprocessor, peripheral integrated circuit elements, an application-specific integrated circuit or other integrated circuits, hardware/electronic logic circuits, such as a discrete element circuit, a programmable logic device, such as a programmable logic array, field programmable gate-array, or the like. In general, the controller <NUM> may be any controller or processor device or devices capable of operating an apparatus and implementing the disclosed embodiments. Some or all of the additional elements of the apparatus <NUM> can also perform some or all of the operations of the disclosed embodiments.

In operation as a UE <NUM>, the transceiver <NUM> can transmit and receive the various signals described above. In a possible embodiment, for example the transceiver <NUM> can receive the minimum SI <NUM> including at least cell access information to establish access with the cell <NUM>. The minimum SI can also include at least one indication indicating whether particular SI listed in scheduling information in the minimum SI <NUM> is being broadcasted or not being broadcasted.

The transceiver <NUM> can transmit the SI request message <NUM> requesting transmission of non-minimum SI150 to the UE <NUM> if the at least one indication indicates the non-minimum SI <NUM> is not being broadcasted. The transceiver <NUM> can either in response to the transmission of the SI request message <NUM> or in response to the at least one indication indicating whether particular SI is being broadcasted receive the requested non-minimum SI <NUM>.

In operation as a network entity, the transceiver <NUM> can transmit and receive the various signals described above. In a possible embodiment, for example the transceiver <NUM> can transmit the minimum SI <NUM> including at least cell access information to establish access with a cell of the network entity <NUM>. The minimum SI <NUM> can also include at least one indication indicating whether particular SI listed in the scheduling information in the minimum SI <NUM> is being broadcasted or not being broadcasted.

The transceiver <NUM> can receive the SI request message <NUM> requesting transmission of the non-minimum SI <NUM> to the UE <NUM>. According to a possible implementation, this reception by the network entity <NUM> can occur if the at least one indication indicates the non-minimum SI <NUM> is not being broadcasted, where the non-minimum SI <NUM> is not included in the minimum SI <NUM>.

The transceiver <NUM> can transmit the non-minimum SI <NUM> either in response to the receiving of the SI request message <NUM> or in response to the at least one indication indicating whether particular SI listed in the scheduling information in the minimum SI <NUM> is being broadcasted.

In another operation as a UE, the transceiver <NUM> can receive the minimum SI <NUM> including at least cell access information to establish access with a cell of the network entity. The transceiver <NUM> can transmit the SI request message <NUM> requesting transmission of the non-minimum SI <NUM> to the UE <NUM> can be transmitted by the UE <NUM>, the SI request message <NUM> including a BITMAP. According to a possible implementation, each bit in the BITMAP can correspond to a unique SI message for the requested non-minimum SI <NUM>, where the non-minimum SI <NUM> is not included in the minimum SI <NUM>. The transceiver <NUM> can receive the non-minimum SI <NUM> in response to the transmission of the SI request message including the BITMAP at <NUM>.

In another operation as a network entity, the transceiver <NUM> can transmit the minimum SI <NUM> including at least cell access information to establish access with the cell <NUM> of the network entity <NUM>. According to a possible implementation, the minimum SI <NUM> can also include at least one indication indicating whether particular SI listed in scheduling information in the minimum SI <NUM> is being broadcasted or not being broadcasted.

The transceiver <NUM> can receive the SI request message <NUM> requesting transmission of non-minimum SI <NUM> to the UE <NUM>. According to a possible implementation, the SI request message <NUM> including a BITMAP where each bit in the BITMAP corresponds to a unique SI message for the requested non-minimum SI <NUM>, where the non-minimum SI <NUM> is not included in the minimum SI <NUM>.

The transceiver <NUM> can transmit the non-minimum SI <NUM> in response to the receiving of the SI request message <NUM> including the BITMAP at <NUM>.

While this disclosure has been described with specific embodiments thereof, it is evident that many alternatives, modifications, and variations will be apparent to those skilled in the art. For example, various components of the embodiments may be interchanged, added, or substituted in the other embodiments. Also, all of the elements of each figure are not necessary for operation of the disclosed embodiments. For example, one of ordinary skill in the art of the disclosed embodiments would be enabled to make and use the teachings of the disclosure by simply employing the elements of the independent claims. Accordingly, embodiments of the disclosure as set forth herein are intended to be illustrative, not limiting. Various changes may be made without departing from the scope of the disclosure.

Claim 1:
A method (<NUM>) performed by a user equipment, UE, (<NUM>), the method comprising:
receiving (<NUM>) minimum system information including at least cell access information to establish access with a cell, the minimum system information also including at least one indication indicating whether particular system information listed in scheduling information in the minimum system information is being broadcasted or not being broadcasted;
transmitting (<NUM>) a system information request message via dedicated radio resource control signaling, the system information message requesting transmission of non-minimum system information if the at least one indication indicates the non-minimum system information is not being broadcasted, where the non-minimum system information is not included in the minimum system information; and
receiving (<NUM>) the non-minimum system information either in response to the transmitting of the system information request message or in response to the at least one indication indicating whether particular system information is being broadcasted;
wherein the system information request message comprises a BITMAP, where each bit in the BITMAP corresponds to a unique system information message for the requested non-minimum system information;
wherein a leftmost bit of the BITMAP corresponds to a lowest valued unique system information message type requested, a rightmost bit of the BITMAP corresponds to a highest valued unique system information message type requested, and bits ordered from the leftmost bit to the rightmost bit being ordered in accordance with increased valued unique system information message type requested.