Using Latency in Obtaining On-Demand System Information for Wireless Networks - Patent application

Abstract

A method is provided that includes receiving on-demand system information and transmitting on-demand system information. [Solution] The method includes, in a wireless network, a user device in idle mode sending a request to a base station for on-demand system information regarding one or more parameters that enable the user device to communicate within the wireless network during a random access process; receiving, by the user device, an indicator value used to determine a waiting time for the user device to wait to obtain the on-demand system information; and receiving, by the user device during the waiting time, the on-demand system information.

Description

Priority claim

[0001] This application claims priority to U.S. patent application Ser. No. 15 / 632,220, filed Jun. 23, 2017, entitled "USE OF WAIT PERIOD TO OBTAIN ON-DEMAND SYSTEM INFORMATION FOR WIRELESS NETWORKS," the disclosure of which is incorporated herein by reference in its entirety. [Technical field]

[0002] This disclosure relates to communications, and more particularly to using latency in obtaining on-demand system information for wireless networks.

[0003] A communication system may be any facility that allows communication between two or more nodes or devices, such as fixed devices or mobile communication devices. Signals may be transmitted by wired or wireless carriers.

[0004] The architecture currently being standardized by 3GPP® is an example of a cellular communication system. A recent innovation in this field is the Long Term Evolution (LTE) of the Universal Mobile Telecommunications System (UMTS) radio-access technology. E-UTRA (evolved UMTS Terrestrial Radio Access) is the air interface of 3GPP®'s LTE upgrade path to mobile networks. In LTE, base stations or access points (APs) are called enhanced Node APs (eNBs) and provide wireless access within a coverage area or cell. In LTE, mobile devices or mobile stations are called User Equipment (UEs). LTE has undergone a number of improvements or evolutions. Additionally, 5G (or fifth generation) wireless networks are also under development.

[0005] In LTE, the system may include an on-demand System Information (SI) transmission mechanism, which transmits on-demand SI to the UE. For example, when the UE is trying to access the network, it may request on-demand SI during a random access procedure. The UE receives a confirmation from the base station in response to the on-demand SI. The base station then transmits an SI message to the UE in an SI window, which may include one or more parameters as one or more blocks, allowing the UE to communicate in the wireless network. However, the base station does not always transmit an SI message when requested. For example, the base station may not be able to transmit an SI message promptly to the requesting UE in one or more subsequent SI windows due to downlink channel congestion or other transmissions being assigned a higher priority than the requested SI message. In such a case, the UE may retry the SI request. However, the base station may take some time to transmit the requested SI, and the re-request may be burdensome on the Random Access Channel (RACH).

[0006] In LTE, the backoff indication field can be signaled by the network as part of the Media Access Control (MAC) subheader in the Random Access Channel (RACH) response. For the value of the backoff indication, the UE may select a random backoff time according to a uniform distribution between 0 and the backoff parameter corresponding to the signaled backoff indication. The backoff time is applied only if the reception of a Random Access Response (RAR) is deemed unsuccessful. Specifically, the failure is declared if none of the received RARs contains a Random Access Preamble Identifier (RAPID) corresponding to the transmitted RA preamble. Therefore, the backoff indication cannot be applied to UEs that receive the RARs properly. In this case, a UE that receives an ACK in the RAR will attempt to decode the SI message in the next SI window. If the SI message is not sent, the UE will retransmit a new SI request, which may cause congestion in the network. Abstract

[0007] A method according to an example implementation may include, in a wireless network, a user device sending a system information request to a base station during a random access process for on-demand system information, the system information request being a request for one or more parameters that enable the user device to communicate within the wireless network; the user device receiving from the base station an indication of a waiting time the user device will wait until obtaining the on-demand system information; the user device waiting for the length of the waiting time; and, after the waiting time has elapsed, the user device monitoring a system information window in which a system information message having the on-demand system information is broadcast by the base station.

[0008] In some example implementations, the method may include any one or more of the following features (or any combination thereof): The system information request may be included in a random access preamble message. The method may further include the user device transmitting a random access preamble message to the base station, the user device receiving a random access response from the base station, and the user device transmitting a message to the base station in response to the random access response, the message including the system information request. The indication of the waiting time may be included in a confirmation message in response to the system information request. The method may include retransmitting the system information request after the waiting time. The indication of the waiting time may include an index value, and the user device may be configured to use the index value to retrieve the length of the waiting time from a waiting time table. The method may further include comparing the length of the waiting time to a threshold level, and the user device transmitting a new system information request to a different base station in a different cell, the new system information request corresponding to the length of the waiting time exceeding the threshold level. The indication of the waiting time may include the length of time, the length of time being expressed based on a unit of time or a system information interval.

[0009] An apparatus according to an exemplary implementation comprises at least one processor and at least one memory containing computer instructions which, when executed by the at least one processor, cause the apparatus to perform the following operations: in a wireless network, a user device sends to a base station a system information request for on-demand system information during a random access process, the system information request being a request for one or more parameters that enable the user device to communicate within the wireless network; receiving from the base station an indication of a waiting time during which the user device waits until the user device obtains the on-demand system information; the user device waits for the length of the waiting time; and, after the waiting time has elapsed, the user device monitors a system information window in which a system information message having the on-demand system information is broadcast by the base station.

[0010] In some example implementations, the apparatus may include any one or more of the features above and / or below (or any combination thereof). The indication of the waiting time may correspond to a number of SI messages such that the SI messages are delayed by the length of the waiting time. The computer instructions, when executed by the at least one processor, may cause the apparatus to: transmit a random access preamble message to the base station by the user device; receive a random access response from the base station by the user device; and transmit a message from the base station by the user device in response to the random access response, the message including the system information request. The indication of the waiting time may be included in a confirmation message in response to the system information request. The computer instructions, when executed by the at least one processor, may cause the apparatus to retransmit the system information request after the waiting time. The indication of the waiting time may include a bit indicating to the user device to wait, the length of the waiting time being indicated by minimum system information broadcast by the base station. The computer instructions, when executed by the at least one processor, may cause the apparatus to: compare the length of the waiting time to a threshold level; and the user device sending a new system information request to a different base station in a different cell, the new system information request corresponding to the length of the waiting time exceeding the threshold level. The indication of the waiting time may be included in minimum system information broadcast by the base station, and the user device may wait the length of the waiting time before sending the system information request to the base station. The indication of the waiting time may be included in a random access channel (RACH) response.

[0011] In an exemplary implementation, a computer program product includes a computer-readable storage medium storing executable code that, when executed by at least one processor, is configured to cause the at least one processor to perform the following: receiving, in a wireless network, a system information request from a base station during a random access process for on-demand system information from a user device, the system information request being a request for one or more parameters that enable the user device to communicate within the wireless network; determining a delay condition for the base station to transmit a system information message to one or more user devices; transmitting, to the user device, an indication of a waiting time that the base station will wait before broadcasting a system information message having the on-demand system information in response to determining the delay condition; and broadcasting, after the waiting time has elapsed, the system information message to the user device within a system information window.

[0012] In some example implementations, the computer program product may include any one or more of the features above and / or below (or any combination thereof). The system information request may be included in a random access preamble message, and the indication of the waiting time may be included in a confirmation of the random access preamble message. The executable code, when executed by the at least one processor, may be configured to cause the at least one processor to: receive, by the base station, a random access preamble message from the user device; transmit, by the base station, a random access response to the user device; and receive, by the base station, a message from the user device in response to the random access response, the message including the system information request, and the indication of the waiting time may be included in the confirmation of the message. The executable code, when executed by the at least one processor, may be configured to cause the at least one processor to periodically broadcast, within a system information window, minimum system information that may include the indication of the waiting time.

[0013] A method according to an exemplary implementation includes, in a wireless network, a user device sending a system information request to a base station during a random access process for on-demand system information, the system information request being a request for one or more parameters that enable the user device to communicate within the wireless network; receiving from the base station an indication of a waiting time the user device will wait until obtaining the on-demand system information; and the user device waiting for the waiting time during which the user device is expected to receive the on-demand system information. According to an example implementation, the method may include one or more of the above and / or below features (or any combination thereof). The method may include the user device retransmitting the system information request to the base station during the random access process after the waiting time. The system information request may be included in a random access preamble message. The method may further include the user device transmitting a random access preamble message to the base station, the user device receiving a random access response from the base station, and the user device transmitting a message to the base station in response to the random access response, the message including the system information request. The indication of the waiting time may be included in a confirmation message in response to the system information request. The indication of the waiting time may be included in minimum system information broadcast by the base station. The indication of the waiting time may be included in a random access channel (RACH) response. The indication of the waiting time may include an index value, and the user device may be configured to use the index value to retrieve the length of the waiting time from a waiting time table. The indication of the waiting time may include a length of time expressed based on a system information interval. The method may further include the user device deeming one cell of the wireless network inaccessible and camping on another cell.

[0014] The details of one or more example implementations are set forth in the accompanying drawings and the description below. Other features will be apparent from the description, drawings, and claims herein. [Brief description of the drawings]

[0015] [Figure 1] FIG. 1 is a block diagram of a wireless network in accordance with an example implementation.

[0016] [Diagram 2]FIG. 2 is a block diagram of a base station configured to perform random access and provide system information to user devices, according to an example implementation.

[0017] [Diagram 3] FIG. 3 illustrates an example of communication between a base station and a user device for providing system information, according to an example implementation.

[0018] [Figure 4] FIG. 4 illustrates an example of communication between a base station and a user device using a waiting time for a system information request based on MSG3, according to an example implementation.

[0019] [Diagram 5] FIG. 5 illustrates an example of communication between a base station and a user device using a waiting time for system information requests based on MSG1, according to an example implementation.

[0020] [Figure 6] FIG. 6 illustrates an example of communication between a base station and a user device using a waiting time for system information requests based on MSG1 or MSG3, according to an example implementation.

[0021] [Figure 7] FIG. 7 is a flowchart illustrating the operation of a user device according to an example implementation.

[0022] [Figure 8] FIG. 8 is a flow chart illustrating the operation of a base station according to an exemplary implementation.

[0023] [Figure 9] FIG. 9 is a flowchart illustrating the operation of a user device according to an example implementation.

[0024] [Figure 10] FIG. 10 is a block diagram of a wireless station according to an exemplary implementation. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0025] According to this exemplary implementation, the network configures the user device to back off sending a system information (SI) request for a predetermined period of time. This prevents the user device from sending multiple SI requests before the network plans to provide the SI. For example, according to an exemplary implementation, if the base station must delay sending a requested SI message, it communicates an indication of the waiting time to the user device, which indicates to back off (wait) for a predetermined period of time before monitoring the SI window for the requested SI message or retransmitting a new SI request. For example, the waiting time indicates that the requested SI will not be available until after the waiting time. And, upon receiving the waiting time, if the user device determines that the waiting time is longer than a threshold amount, the user device considers the cell inaccessible and sends a random access (RA) request / SI request to another base station in a different cell.

[0026] The base station may determine that the downlink is congested or that a higher priority information transmission should take precedence over the requested SI message transmission. If so, the base station may set a wait time for all SI messages, a group of SI messages, or an individual SI message. In some examples, the base station determines a length of time to wait for a delayed SI message for the user device and includes the length of time in the wait time indication. The length of time may be indicated in units of time (e.g., milliseconds) or may be based on an interval of SI. In some examples, the wait time indication includes an index value, and the user device determines the length of wait time based on a wait time table(s) and the index value specified in the specification. For example, an index of 1 may correspond to a wait time of x milliseconds. Knowing the wait time table and the index value, the user device can obtain the length of wait time. In some examples, the wait time indication includes a bit that indicates to the user device to wait, and the length of time may be indicated by a minimum SI broadcast by the base station.

[0027] The SI requested by the user device may be considered as on-demand SI (as it is made available upon SI request by the user device). For example, on-demand SI may consist of various information such as inter-frequency selection (or reselection) parameters, Multimedia Broadcast / Multicast Service (MBMS) parameters, positioning information, and / or configuration information for emergency / alarm systems. The SI may also include a minimum SI that the base station periodically broadcasts. The minimum SI may include parameters for initial access, such as RA parameters, and scheduling information for other system information block (SIB) types, such as SI interval and SI window information. The network may determine which SI to make available for on-demand provision and which to make available for periodic broadcast.

[0028] Before sending an SI request, the user device determines whether the SI it requests is available in the corresponding region and whether the SI is broadcast. For example, the scheduling information in the minimum SI may include an indication of whether the corresponding SI block is broadcast periodically or provided on demand. If the minimum SI indicates that the SI block is not broadcast, the user device determines that this SI block is not broadcast every SI interval in the SI window. Thus, the user device may send an SI request to obtain this SI block.

[0029] To obtain on-demand SI (e.g., SI that is not available via periodic broadcast), a user device may send an RA-based SI request for one or more SI messages (each SI message including a different set of SIBs). In some examples, the RA-based SI request is a request for a single SI message. In some examples, the RA-based SI request is a request for multiple SI messages.

[0030] In some examples, the RA-based SI request is a message 1 request (MSG1-based SI request). For example, during RA processing, the user device transmits a random access channel (RACH) preamble message (MSG1) with an embedded SI request. In some examples, one RACH preamble can be utilized to request multiple SI messages. In response, the user device receives an ACK RACH response with a wait time indication. The ACK RACH response is an ACK for acknowledging receipt of the RACH preamble message. The ACK RACH response may further include a RACH preamble identifier (e.g., an identifier corresponding to a preamble sequence that confirms that the response corresponds to the RA preamble / request), and may not include other typical RACH parameters. Typical RACH parameters include an uplink (UL) grant (e.g., grant resources for UL transmission by the user device), a CRNTI (e.g., allocation of a cell radio network temporary identifier), a TAI (e.g., a timing advance used by the user device for UL transmission), and / or a backoff indication, etc. In some examples, when a user device receives a NACK RACH response, it may ignore the wait time and retransmit the SI request. In another example, when a user device receives a NACK RACH response, it may apply the wait time, if one was indicated in the ACK RACH response (MSG2), before retransmitting the SI request.

[0031] In another example, the RA-based SI request is a message 3 request (MSG3-based SI request). For example, during RA processing, the user device typically transmits a RACH preamble message (MSG1) (e.g., does not include an SI request in the preamble) and receives a RACH response (MSG2) that includes typical RACH parameters such as a UL grant, a RA preamble ID, a TAI, and a CRNTI. The user device then transmits a message (MSG3) with an SI request. In some examples, the SI request message (MSG3) includes a bit-mapped SI message request that requests one or more SI messages. In response, the user device receives an ACK message (MSG4) that includes an indication of a waiting time. In some examples, when the user device receives a NACK message, it may ignore the waiting time and retransmit the SI request. In another example, when the user device receives a NACK message, it may apply the waiting time before retransmitting the SI request if a waiting time is indicated in the ACK message (MSG4).

[0032] During the waiting time, the user device does not monitor the SI window(s), but once the waiting time has elapsed, the user device monitors the next SI window in anticipation of receiving the requested SI. In some examples, after the waiting time has elapsed, the user device may retransmit its SI request (e.g., an MSG1-based SI request or an MSG3-based SI request). In another example, upon receiving an indication of the waiting time, the user device may compare the length of the waiting time to a threshold level. If the length of the waiting time exceeds the threshold level, the user device considers the cell inaccessible and transmits an RA-based SI request to another base station in a different cell.

[0033] In some examples, the base station broadcasts the minimum SI (including the scheduling information) with an indication of the waiting time. For example, the base station may broadcast the waiting time within the SI window, determining that the waiting time applies to all SI requests, a subset of SI requests, or a particular type of SI requested by the user device. In this case, the user device may respond similarly upon receiving the waiting time indication, e.g., wait for the waiting time to elapse and wait for the requested SI, retransmit the SI request, and / or send a new SI request to a different cell as the cell is inaccessible. In another example, if the minimum SI that the user device must check before sending the SI request indicates a waiting time, the user device may wait to send the SI request. That is, the user device may refrain from sending the first SI request if the waiting time is indicated in the minimum SI. This approach is effective in preventing the user device from sending any SI request if the network cannot send the SI until the waiting time has elapsed.

[0034] Therefore, introducing a latency period for on-demand SI may reduce the amount of congestion on the RACH, provide a means to control the amount of SI requested by user devices, and enable a more flexible scheduling framework for on-demand SI messages.

[0035] FIG. 1 is a block diagram of a wireless network 130 according to an example implementation. In the wireless network 130 of FIG. 1, user devices 131, 132, 133, and 135, also referred to as mobile stations (MS) or user equipment (UE), may connect (communicate) with base stations (BS), also referred to as access points (AP), enhanced node Bs (eNBs), or network nodes. At least some of the functionality of an access point (AP), base station (BS), or (enhanced) node B (eNB) may be performed by any node, server, or host that may be operatively connected to a transceiver, such as a remote radio head. A BS (or AP) 134 provides wireless coverage within a cell 136 that includes user devices 131, 132, 133, and 135. Although only four user devices are shown connected or associated with the BS 134, any number of user devices may be provided. The BS 134 is also connected to a core network 150 via an S1 interface 151. This is just one example of a wireless network and other configurations may be used.

[0036] A user device (user equipment, user terminal (UE)) may refer to a portable computing device including wireless mobile communication devices operating with or without a subscriber identity module (SIM). Examples include, but are not limited to, the following types of devices: mobile stations (MS), mobile phones, feature phones, smartphones, personal digital assistants (PDAs), handsets, devices using wireless modems (alarms, measuring devices, etc.), laptops and / or touch screen computers, tablets, phablets, gaming consoles, notebooks, multimedia devices, etc. It will further be appreciated that a user device may be an almost entirely uplink only device. Examples of this include cameras or video cameras that upload still and video images to the network. A user device (UE) may also be an Internet of Things (IoT) user device / UE, for example a Narrowband Internet of Things (NB-IoT) device.

[0037] As an example, in LTE, the core network 150 may be referred to as an Evolved Packet Core (EPC), which may be a Mobility Management Entity (MME) that may handle or assist with mobility / handover of user devices between BSs, one or more gateways that forward data and control signals between BSs, packet data networks, or the Internet, or other control functions or blocks.

[0038] The various exemplary implementations may be applied to a variety of wireless technologies or wireless networks, i.e., LTE, LTE-A, 5G, cmWave and / or mmWave band networks, or any other wireless network. LTE, 5G, cmWave and mmWave band networks are merely examples, and the various exemplary implementations may be applied to any other wireless technology / wireless network.

[0039] FIG. 2 is a block diagram of a BS 134 according to an example implementation configured to perform random access (RA) 105 and broadcast or signal system information (SI) 111 to enable a UE 131 to access a mobile network and transmit information thereon.

[0040] In LTE, RA105 is used for initial access during radio link establishment (e.g., transition from RRC_IDLE to RRC_CONNECTED), for radio link re-establishment in case of radio link loss, for handover when uplink synchronization needs to be set up for a new cell, and / or to set uplink synchronization when uplink or downlink data is sent if the device is RRC_CONNECTED and uplink synchronization is not established.

[0041] According to RA 105, at the time of configuration, UE 131 uses a random access channel (RACH) (e.g., an initial uplink access channel) to access the network. In some examples, RA 105 has four main steps. In the first step, UE 131 selects one of 64 available RACH preambles and transmits the selected RACH preamble (e.g., MSG1) in, for example, a broadcast RACH window. The main purpose of the preamble transmission is to indicate to base station 134 that random access is being attempted so that base station 134 can estimate the delay between base station 134 and UE 131. The RACH preamble may include a preamble sequence and a cyclic prefix. In the second step, base station 134 transmits a RACH response (e.g., MGS2) on the downlink shared channel (DL-SCH). In some examples, the RACH response may include an UL grant (e.g., grant resources for UL transmission by the UE 131), a CRNTI (e.g., allocation of a cell radio network temporary identifier), a TAI (timing advance used by the UE 131 for UL transmission), and may also include a backoff indication. In a third step, the UE 131 transmits an RRC connection request message (e.g., MSG3) to the base station 134 using an uplink shared channel (UL-SCH). The RRC connection request message may include a UE identifier and a connection establishment reason. In a fourth step, the base station 134 transmits a contention resolution message (e.g., MSG4) to the UEs 131 whose transmitted message was properly received in the third step. The contention resolution message may include a new CRNTI to be used for further communication. In some examples, by performing the RA 105, the UE 131 may transition from an idle (e.g., RRC_idle) state to a connected state (e.g., RRC_connected) with respect to the base station 134. RRC stands for Radio Resource Control.

[0042] The base station 134 is configured to broadcast or signal the SI 111 to the UE 131. In LTE, the SI 111 is transmitted on the Broadcast Control (BCCH) logical channel. Typically, the BCCH message is transmitted on the DL-SCH and on the Physical Downlink Shared Channel (PDSCH). The SI 111 includes multiple system information blocks (SIBs). Each SIB includes a set of parameters. For example, SIB1 may include information about UE cell access and define the schedule of the other SIBs. SIB2 may include radio resource configuration information common to all UEs. SIB3 may include intra-frequency, inter-frequency, and / or inter-RAT cell reselection. SIB4 may include intra-frequency neighbor cell information for intra-LTE intra-frequency cell reselection. SIB5 may include neighbor cell related information for intra-LTE inter-frequency cell reselection. However, these types of SIBs are merely examples and the set of SIBs may include various parameters.

[0043] A particular SI message broadcast by the base station 134 may include one or more SIBs. The set of SIBs transmitted varies depending on the SI message. The SI messages may be broadcast within an SI window. For example, an SI window is provided for each SI message, and the interval of each window is configurable. In one example, the base station 134 may broadcast an SI message with SIB1 periodically (e.g., 80 ms).

[0044] 3 is a diagram illustrating an example of communication between the base station 134 and the UE 131 for transmitting the SI 111. In some examples, the SI 111 includes a minimum SI 113 and another SI 115. In some examples, the minimum SI 113 includes parameters required for initial access to the cell 136, RA parameters, scheduling information for the SI 111 that is periodically broadcast or provided on demand, an SI window length, an SI interval, and an SIB type. In some examples, the another SI 115 may be periodically broadcast or obtained on demand. The another SI 115 obtained on demand may also be referred to as an on-demand SI. The another SI 115 may include inter-frequency selection (or reselection) parameters, Multimedia Broadcast / Multicast Service (MBMS) parameters, positioning information, and / or configuration information for an emergency / alarm system.

[0045] In operation 302, the base station 134 may periodically broadcast the minimum SI 113 to the UE 131. In operation 304, the base station 134 may periodically (and optionally) broadcast one or more SI parameters of the alternative SI 115 to the UE 131. In operation 306, the UE 131 transmits an SI request, and in response to the SI request, the base station 134 may broadcast one or more SI parameters of the alternative SI 115 (on-demand SI) or transmit the on-demand SI in dedicated signaling. A UE 131 in RRC_IDLE or RRC_INACTIVE state transmits an SI request for on-demand SI without state change. For a UE 131 in RRC_CONNECTED state, dedicated RRC signaling can be used to request and transmit the on-demand SI. Whether the alternative SI 115 is broadcast or transmitted in dedicated UE-specific RRC signaling is determined by the network. In some examples, to obtain on-demand SI (e.g., SI that is not available in a periodic broadcast), the UE 131 may send an RA-based SI request for one or more SI messages. In some examples, the RA-based SI request is a request for one SI message. In some examples, the RA-based SI request is a request for multiple SI messages.

[0046] FIG. 4 is a diagram illustrating an example of communication between a base station 134 and a UE 131 using a waiting time for SI requests based on a RA MSG3, according to an example implementation.

[0047] In RA 105, UE 131 transmits a normal RACH preamble message (MSG1) in operation 402 and receives a RACH response (MSG2) containing typical RACH parameters such as UL grant, RA preamble ID, TAI, CRNTI, potential backoff indication, etc. In operation 406, UE 131 transmits a message (MSG3) with an embedded SI request. In some examples, the SI request message (MSG3) includes a bit-mapped SI message request requesting one or more SI messages. In response, UE 131 receives an ACK message (MSG4) containing an indication of a waiting time in operation 408. In some examples, upon receiving a NACK message, UE 131 may ignore the waiting time and retransmit the SI request.

[0048] For example, the base station 134 may determine that it is unable to provide the requested on-demand SI for a predetermined period of time. Specifically, the base station 134 may determine that the downlink is congested or that a higher priority information transmission takes precedence over the transmission of the requested SI message. Based on the determination, the base station 134 may set a wait time for all SI messages, for a group of SI messages, or for a particular SI message. In some examples, the base station 134 may determine a predetermined amount of time for the UE 131 to wait for a delayed SI message and include an indication of the amount of time in the wait time. In some examples, the amount of time may be expressed in terms of an explicit unit of time (e.g., wait x milliseconds) or based on an SI interval (e.g., wait for x SI windows).

[0049] In some examples, the indication of the waiting time may include an SI-request backoff indication in the ACK message. In some examples, the SI-request backoff indication is an index value. The UE 131 may obtain the length of time (expressed based on a specific unit of time or SI interval) corresponding to the SI-request backoff indication. For example, the UE 131 may define or have access to a waiting time table defined in the specification. The waiting time table may include a set of different lengths of time. Each length of time corresponds to a different index value. Based on the waiting time table and the SI-request backoff indication, the UE 131 may obtain the appropriate waiting time length. In some examples, the indication of the waiting time may include only a single bit that instructs the UE 131 to back off SI request transmission during the waiting time. In this example, the backoff setting may be defined in the specification. For example, in response to receiving the backoff bit, the UE 131 may automatically determine the length of time from the specification (e.g., in response to receiving the backoff bit, wait x milliseconds before attempting to retry the request, or wait for a scheduled period). In another example, the base station 134 may broadcast the length of the wait time, within the minimum SI 113. When the UE 131 receives the backoff bit (e.g., in an ACK message), the UE 131 waits for the amount of time broadcast by the base station 134.

[0050] If no wait time is communicated to UE 131 (but the transmission of the requested SI message is delayed), UE 131 may attempt to retransmit the SI request based on the RA, which may load the RACH. Alternatively, if a wait time is sent, UE 131 may back off retrying the SI request. During the wait time, UE 131 may not wait or monitor the SI window for the requested SI message(s), in operation 410. Also, during the wait time, UE 131 may not attempt to repeat the SI request, in operation 410.

[0051] In some examples, once the waiting time has elapsed, in operation 412, the base station 134 broadcasts an SI message specific to the UE's request in the next scheduled SI window. For example, the SI message is broadcast within the SI window. For example, there is a separate SI window for each SI message, and the interval of each window is configurable. In operation 414, the UE 131 may monitor the SI window to obtain the requested on-demand SI. In some examples, after the waiting time has elapsed, in operation 416, the UE 131 may resend the SI request (e.g., an SI request based on MSG3). In another example, upon receiving an indication of the waiting time, the UE 131 may compare the length of the waiting time to a threshold level. If the length of the waiting time exceeds the threshold level, the UE 131 may transmit an RA-based SI request to another base station of a different cell, assuming that the cell is inaccessible.

[0052] As mentioned above, the RACH response may include a back-off indication different from the waiting time of the SI request. For example, if a relatively large number of UEs are trying to access the wireless medium (e.g., RACH) at the same time, collisions may occur. Therefore, the back-off indication may be used to reduce collisions / interference on the RACH. The back-off time of the RACH response is applied only if the RACH response is failed. Note that a failure is indicated if none of the received RACH responses contains a random access preamble identifier (RAPID) corresponding to the transmitted RA preamble. Therefore, the back-off indication cannot be applied to UEs that properly receive the RACH response. In this case, a UE that receives an ACK in the RACH response will attempt to decode the SI message in the next SI window. If the SI message is not sent, the UE will retransmit a new SI request. Therefore, the existing back-off indication does not necessarily solve the problem of unnecessary repetition of SI requests.

[0053] FIG. 5 illustrates an example of communication between a base station 134 and a UE 131 using a waiting period for SI requests based on MSG1, according to an example implementation.

[0054] For example, in RA 105, UE 131 selects a dedicated RACH preamble for SI request in operation 502 and transmits the selected RACH preamble with SI request embedded therein. In some examples, each RACH preamble is associated with a different SIB. In some examples, a single RACH preamble can be used to request multiple SI messages. In operation 504, UE 131 receives an ACK RACH response including an indication of the waiting time. The ACK RACH response is an ACK that acknowledges receipt of the RACH preamble message. The ACK RACH response may further include a RACH preamble identifier (e.g., an identifier corresponding to a preamble sequence that acknowledges that the response corresponds to a RA preamble / request) and may not include other typical RACH parameters such as a UL grant, CRNTI, TAI, backoff indication, etc. In some examples, when UE 131 receives a NACK RACH response, it may ignore the waiting time and retransmit the SI request based on MSG1.

[0055] 4, the indication of the waiting time may be indicated in one of several different options as described above. For example, the indication of the waiting time in the RACH response may include a waiting time length (e.g., based on units of time or SI intervals), an index value whose corresponding time length is specified in a waiting time table accessible to the UE 131, or a one-bit backoff indication.

[0056] During the waiting time, the UE 131 may not wait or monitor the SI window for the requested SI message(s), in operation 506. Also, during the waiting time, the UE 131 may not attempt to repeat the SI request, in operation 506. In some examples, once the waiting time has elapsed, the base station 134 may broadcast an SI message specific to the UE's request in the next scheduled SI window, in operation 508. The UE 131 may monitor the SI window, in operation 510, to obtain the requested on-demand SI. In some examples, once the waiting time has elapsed, the UE 131 may resend the SI request, e.g., an SI request based on MSG1, in operation 512. In another example, upon receiving an indication of the waiting time, the UE 131 may compare the length of the waiting time to a threshold level. If the length of the waiting time exceeds the threshold level, the UE 131 may transmit an RA-based SI request to another base station in a different cell, as the cell is inaccessible.

[0057] FIG. 6 illustrates an example of communication between a base station 134 and a UE 131 utilizing latency for SI requests based on MSG1 or MSG3, according to an example implementation.

[0058] In operation 602, the UE 131 transmits an SI request based on MSG1 or MSG3 (as described above with reference to Figs. 4 and 5). In operation 604, the UE 131 may receive an ACK message acknowledging receipt of the SI request. In operation 606, instead of providing an indication of the waiting time in the ACK message, the base station 134 may broadcast an indication of the waiting time at the time of broadcasting the minimum SI 113. The base station 134 may broadcast the waiting time in the SI window, if it determines that the waiting time applies to all SI requests, a subset of the SI requests, or a particular type of SI requested by the UE 131. In this case, the UE may respond similarly upon receiving the indication of the waiting time. For example, it may wait for the waiting time to elapse and wait for the requested SI (operation 612), retransmit the SI request (operation 610), or transmit a new SI request to a different cell as the cell is inaccessible (operation 614).

[0059] Example 1. Figure 7 is a flow chart 700 illustrating the operation of a user device / user terminal (UE) according to an example implementation.

[0060] Operation 702 includes a user device in a wireless network sending to a base station a system information request for on-demand system information during a random access procedure, the system information request being a request for one or more parameters that enable the user device to communicate within the wireless network. Operation 704 includes the user device receiving from the base station an indication of a wait time the user device will wait to obtain the on-demand system information. Operation 706 includes the user device waiting for the length of the wait time. Operation 708 includes the user device monitoring a system information window after the wait time has elapsed for a system information message broadcast by the base station that has the on-demand system information.

[0061] Example 2. According to an example implementation of the method of Example 1 and / or Figure 7, the system information request is included in a random access preamble message.

[0062] Example 3. According to an example implementation of the method of Examples 1 or 2 and / or the method of FIG. 7, the method further includes: the user device sending a random access preamble message to the base station; the user device receiving a random access response from the base station; and the user device sending a message to the base station in response to the random access response, the message including the system information request.

[0063] Example 4. According to an example implementation of the method of any of Examples 1-3 and / or the method of FIG. 7, the indication of the waiting time is included in a confirmation message in response to the system information request.

[0064] Example 5. According to an example implementation of the method of any of Examples 1-4 and / or the method of FIG. 7, the method further includes retransmitting the system information request after the waiting period.

[0065] Example 6. According to an example implementation of the method of any of Examples 1-5 and / or the method of FIG. 7, the indication of the wait time includes an index value, and the user device is configured to use the index value to retrieve the length of the wait time from a wait time table.

[0066] Example 7. According to an example implementation of the method of any of Examples 1-6 and / or the method of FIG. 7, the method further includes comparing the length of the waiting time to a threshold level and the user device sending a new system information request to a different base station in a different cell corresponding to the length of the waiting time exceeding the threshold level.

[0067] Example 8. According to an example implementation of the method of any of Examples 1-7 and / or the method of FIG. 7, the indication of the waiting time includes the length of time, the length of time being expressed based on units of time or system information intervals.

[0068] Example 9. An apparatus according to an example implementation comprises at least one processor and at least one memory containing computer instructions that, when executed by the at least one processor, are configured to cause the apparatus to perform the method of any of Examples 1-8 and / or the method of FIG. 7 (and / or one or more operations / features described herein).

[0069] Example 10. A computer program product according to an example implementation comprises a computer-readable storage medium storing executable code that, when executed by at least one processor, is configured to cause the at least one processor to perform the method of any of Examples 1-8 and / or the method of FIG. 7 (and / or one or more operations / features described herein).

[0070] Example 11. An apparatus comprising means for carrying out the method of any of Examples 1 to 8 and / or the method of FIG. 7 (and / or one or more operations / features described herein).

[0071] Example 12. An apparatus according to another example implementation comprises at least one processor and at least one memory containing computer instructions that, when executed by the at least one processor, cause the apparatus to: transmit a system information request to a base station in a wireless network during a random access procedure by a user device for on-demand system information, the system information request being a request for one or more parameters that enable the user device to communicate within the wireless network; receive from the base station an indication of a wait time during which the user device waits to obtain the on-demand system information; wait the length of the wait time by the user device; and, after the wait time has elapsed, monitor a system information window during which a system information message having the on-demand system information is broadcast by the base station by the user device.

[0072] Example 13. According to an example implementation of Example 12, the indication of the latency corresponds to a number of SI messages such that the SI messages are delayed by the amount of the latency.

[0073] Example 14. According to the example implementation described in Example 12 or 13, the computer instructions, when executed by the at least one processor, cause the apparatus to: send a random access preamble message to the base station by the user device; receive a random access response from the base station by the user device; and send a message to the base station by the user device in response to the random access response, the message including the system information request.

[0074] Example 15. According to an example implementation of any of Examples 12-14, the indication of the latency is included in a confirmation message in response to the system information request.

[0075] Example 16. According to an example implementation of any of Examples 12-15, the computer instructions, when executed by the at least one processor, cause the device to retransmit the system information request after the waiting time.

[0076] Example 17. According to example implementations of any of Examples 12-16, the computer instructions, when executed by the at least one processor, cause the apparatus to: compare the length of the latency to a threshold level; and transmit new system information requests to different base stations in different cells by the user device corresponding to the length of the latency exceeding the threshold level.

[0077] Example 18. According to an example implementation of any of Examples 12-17, the indication of the waiting time includes a bit that indicates to the user device to wait, and the length of the waiting time is indicated by minimum system information broadcast by the base station and is the length of time the user device waits before retrying a system information request.

[0078] Example 19. According to an example implementation of any of Examples 12 to 18, the indication of the waiting time is included in minimum system information broadcast by the base station, and the user device waits the length of the waiting time before sending the system information request to the base station.

[0079] Example 20. According to an example implementation of any of Examples 12-19, the indication of the waiting time is included in a random access channel (RACH) response.

[0080] Example 21. Figure 8 is a flow chart 800 illustrating the operation of a base station (BS) / eNB according to an example implementation.

[0081] Operation 802 includes a base station receiving a system information request from a user device in a wireless network for on-demand system information during a random access procedure, the system information request being a request for one or more parameters that enable the user device to communicate in the wireless network. Operation 804 includes the base station determining a delay condition for transmitting a system information message to one or more user devices. Operation 806 includes the base station transmitting to the user device an indication of a waiting time the base station will wait before broadcasting a system information message having the on-demand system information in response to determining the delay condition. Operation 808 includes the base station broadcasting the system information message to the user device within a system information window after the waiting time has elapsed.

[0082] Example 22. According to an example implementation of the method of Example 21 and / or the method of FIG. 8, the system information request is included in a random access preamble message, and the indication of the waiting time is included in a confirmation of the random access preamble message.

[0083] Example 23. According to an example implementation of the method of Example 21 or 22 and / or the method of FIG. 8, the method includes: the base station receiving a random access preamble message from the user device; the base station sending a random access response to the user device; and the base station receiving a message from the user device in response to the random access response, the message including the system information request, wherein the indication of the waiting time is included in the confirmation of the message.

[0084] Example 24. According to an example implementation of the method of any of Examples 21-23 and / or the method of FIG. 8, the method includes, within a system information window, the base station periodically broadcasting minimum system information including the indication of the latency period.

[0085] Example 25. An apparatus according to an example implementation comprises at least one processor and at least one memory containing computer instructions that, when executed by the at least one processor, cause the apparatus to perform the method of any of Examples 21-24 and / or the method of FIG. 8 (and / or one or more operations / features described herein).

[0086] Example 26. A computer program product according to an example implementation comprises a computer-readable storage medium storing executable code that, when executed by at least one processor, causes the at least one processor to perform the method of any of Examples 21-24 and / or the method of FIG. 8 (and / or one or more operations / features described herein).

[0087] Example 27. An apparatus comprising means for carrying out the method of any of Examples 21-24 and / or the method of FIG. 8 (and / or one or more operations / features described herein).

[0088] Example 28. Figure 9 is a flow chart 900 illustrating the operation of a user device / user terminal (UE) according to an example implementation.

[0089] Operation 902 includes a user device in a wireless network sending to a base station a system information request for on-demand system information during a random access procedure, the system information request being a request for one or more parameters that enable the user device to communicate within the wireless network. Operation 904 includes the user device receiving from the base station an indication of a waiting time during which the user device will wait to obtain the on-demand system information. Operation 906 includes the user device waiting for the waiting time during which the user device is expected to receive the on-demand system information. In this aspect, the user device may receive the indication of the waiting time (according to one or more examples described above) during which the user device may expect to receive the on-demand system information from the base station. For example, in this aspect, the waiting time is an amount of time for which the base station is configured to deliver the on-demand system information.

[0090] Example 29. According to the method of Example 28 and / or the method example implementation of FIG. 9, the method may include, after the waiting time, the user device retransmitting the system information request to the base station during the random access process.

[0091] Example 30. According to an example implementation of the method of Example 28 or 29 and / or the method of FIG. 9, the system information request may be included in a random access preamble message.

[0092] Example 31. According to an example implementation of the method of any of Examples 28 to 30 and / or the method of FIG. 9, the method further includes: the user device sending a random access preamble message to the base station; the user device receiving a random access response from the base station; and the user device sending a message to the base station in response to the random access response, the message including the system information request.

[0093] Example 32. According to an example implementation of the method of any of Examples 28-31 and / or the method of FIG. 9, the indication of the waiting time may be included in a confirmation message in response to the system information request.

[0094] Example 33. According to an example implementation of the method of any of Examples 28-32 and / or the method of FIG. 9, the indication of the waiting time may be included in minimum system information broadcast by the base station.

[0095] Example 34. According to an example implementation of the method of any of Examples 28-33 and / or the method of FIG. 9, the indication of the waiting time may be included in a random access channel (RACH) response.

[0096] Example 35. According to an example implementation of the method of any of Examples 28-34 and / or the method of FIG. 9, the indication of the wait time may include an index value, and the user device may be configured to use the index value to retrieve the length of the wait time from a wait time table.

[0097] Example 36. According to an example implementation of the method of any of Examples 28-35 and / or the method of FIG. 9, the indication of the waiting time may include a length of time expressed based on a system information interval.

[0098] Example 37. An apparatus according to an example implementation comprises at least one processor and at least one memory containing computer instructions that, when executed by the at least one processor, cause the apparatus to perform the method of any of Examples 28-36 and / or the method of FIG. 9 (and / or one or more operations / features described herein).

[0099] Example 38. A computer program product according to an example implementation comprises a computer-readable storage medium storing executable code that, when executed by at least one processor, causes the at least one processor to perform the method of any of Examples 28-36 and / or the method of FIG. 9 (and / or one or more operations / features described herein).

[0100] Example 39. An apparatus comprising means for carrying out the method of any of Examples 28 to 36 and / or the method of FIG. 9 (and / or one or more operations / features described herein).

[0101] 10 is a block diagram of a wireless station (e.g., AP or user device) 1000 according to an example embodiment. The wireless station 1000 may, for example, comprise one or two RF (radio frequency) or wireless transceivers 1002A, 1002B. Each wireless transceiver comprises a transmitter and a receiver for transmitting and receiving signals, respectively. The wireless station further comprises a processor or control unit / entity (controller) 1004 for executing instructions or software to control the transmission and reception of signals, and a memory 1006 for storing data and / or instructions.

[0102] The processor 1004 also performs decisions, generates frames, packets, or messages to be transmitted, decodes received frames or messages for further processing, and performs other tasks or functions described herein. The processor 1004 may be a baseband processor, generating, for example, messages, packets, frames, or other signals to be transmitted via the wireless transceiver 1002A or 1002B. The processor 1004 may control the transmission of signals or messages over a wireless network, and may control the reception of signals or messages over a wireless network (e.g., downconverted by the wireless transceiver 1002). The processor 1004 may be programmable and capable of executing software or other instructions stored in a memory or other computer medium, thereby performing various tasks or functions described above, such as one or more of the tasks or methods described above (e.g., any of the operations in the illustrated timing diagrams and flow charts). The processor 1004 may be (or may include) hardware, programmable logic, a programmable processor executing software or firmware, and / or any combination thereof. The processor 1004 may include one or more processors coupled to a substrate. In other words, for example, the processor 1004 and the transceiver 1002 together may be considered a wireless transceiver system.

[0103] 10, a controller (or processor) 1008 may execute software and instructions to provide overall control of the wireless station 1000, as well as control of other systems such as input / output devices (e.g., display, keypad) not shown in FIG. 10, and / or execute software for one or more applications that may be present on the wireless station 1000, such as an email program, an audio / video application, a word processor, a voice over IP (VoIP) application, or other application or software.

[0104] Additionally, the storage medium may include instructions stored thereon that, when executed by a controller or processor, cause the processor 1004 or another controller or processor to perform one or more of the functions or tasks described above.

[0105] In another example implementation, the RF or wireless transceiver(s) 1002A / 1002B may receive and / or transmit signals or data, and the processor 1004 (and possibly also the transceiver 1002A / 1002B) controls the RF or wireless transceiver 1002A or 1002B to receive, transmit, or broadcast signals or data.

[0106] It should be noted that the embodiment is not limited to the system described as an example, and those skilled in the art can apply the solution to other communication systems. Another example of a suitable communication system is the 5G concept. The network architecture of 5G is said to be very similar to that of LTE Advanced. 5G is likely to use multiple input-multiple output (MIMO) antennas, many more base stations or nodes than LTE (the so-called small cell concept), including macro sites working in cooperation with smaller stations, and possibly employing various radio technologies to improve coverage and data transfer speeds.

[0107] Of course, future networks will almost certainly make use of Network Functions Virtualization (NFV), a network architecture concept that proposes virtualizing network node functions into "building blocks" or entities that can be operatively connected or linked to provide services. A Virtualized Network Function (VNF) may comprise one or more virtual machines that run computer program code using standard or generic servers rather than custom hardware. Cloud computing and data storage may also be utilized. In the case of wireless communications, this may mean that at least some of the node operations are performed on a server, host, or node that is operatively connected to a remote radio head. It is also possible that the node operations are distributed among multiple servers, nodes, or hosts. Furthermore, it is of course possible that the division of labor between core network operations and base station operations may be different from that of LTE, or even non-existent.

[0108] The implementation of the various techniques described herein may be implemented in digital electronic circuitry, computer hardware, firmware, software, or a combination thereof. They may be realized as computer program products, i.e. computer programs tangibly embodied on an information carrier (e.g., a machine-readable storage device or a propagated signal), which perform or control the operation of a data processing device, which may be a programmable processor (e.g., a processor connected to a board), a computer, or multiple computers. Furthermore, they may be implemented on a computer-readable medium or a computer-readable storage medium, which may be a non-transitory medium. The various techniques may be implemented by a transitory signal or medium, and / or by a program and / or software (downloadable over the Internet or other (one or more wired and / or wireless) networks). Furthermore, implementation by machine type communication (MTC) or even IoT is possible.

[0109] The computer program may be in the form of source code, object code or any intermediate form and may be stored on any kind of carrier, distribution medium or computer readable medium, which may be any entity or device capable of carrying a program. Such carriers include, for example, recording media, computer memories, read-only memories, optical-electrical and / or electrical carrier signals, telecommunication signals and software distribution packages. Depending on the processing power required, the computer program may be executed in a single electronic digital computer or distributed among several computers.

[0110] Furthermore, implementations of the various techniques described herein may also be applied to Cyber-Physical Systems (CPS), which are systems of cooperating computational elements that control physical entities. CPS may enable the implementation and use of a vast amount of interconnected ICT devices (sensors, actuators, processors microcontrollers, etc.) embedded in physical objects at various locations. Mobile cyber-physical systems, where the physical system has inherent mobility, are a subcategory of cyber-physical systems. Examples of mobile physical systems include mobile robotics and electronic devices carried by people or animals. The popularity of smartphones has led to an increased interest in mobile cyber-physical systems. Thus, various implementations of the techniques described herein may be provided using one or more of these technologies.

[0111] A computer program, such as the computer program(s) described above, may be written in any programming language, including compiled or interpreted languages, and may be deployed in any form, such as a stand-alone program, a module, component, subroutine, or other unit, or as any portion thereof suitable for use in a computing environment. A computer program may be deployed to be executed by one or more computers at a single site or may be distributed across multiple sites and interconnected by a communications network.

[0112] The method steps may be implemented by one or more programmable processors (e.g., one or more processors coupled to the board) executing computer programs or portions of computer programs, which perform functions by operating in such a way that input data is processed and output is obtained. The method steps and apparatus may also be implemented in special purpose logic circuitry, such as a Field Programmable Gate Array (FPGA) or an Application Specific Integrated Circuit (ASIC).

[0113] Examples of processors suitable for executing computer programs include general and special purpose microprocessors, any one or more processors of any kind of digital computer, chip, or chipset. Typically, a processor receives instructions and data from a ROM, a RAM, or both. Elements of a computer may include at least one processor for executing instructions and one or more memory devices for storing instructions and data. Typically, a computer may further include one or more mass storage devices for storing data, and may be operatively connected thereto for transmitting and receiving data. Examples include magnetic, magneto-optical, or optical disks. Information carriers suitable for carrying computer program instructions and data include all types of non-volatile media. These include, for example, semiconductor memory devices (e.g., EPROM, EEPROM, and flash memory devices), magnetic disks (e.g., internal hard disks or removable disks), magneto-optical disks, CD-ROM, and DVD-ROM disks. The processor and memory may be supplemented by or included in special purpose logic circuitry.

[0114] For user interaction, the implementation may be realized on a computer having a display device, such as a cathode ray tube (CRT) or liquid crystal display (LCD) monitor, to display information to the user, and a user interface, such as a keyboard and a pointing device (e.g., a mouse or trackball) to allow the user to provide input to the computer. Other types of devices may be used to achieve user interaction. For example, the feedback provided to the user may be any sensory feedback, such as visual, auditory, or tactile feedback. User input may also be received in any form, such as sound, voice, or tactile input.

[0115] For example, each implementation may be realized by a computer system including back-end elements such as a data server, a computer system including middleware elements such as an application server, a computer system including front-end elements such as a client computer having a GUI or web browser through which a user can interact with the system, or any combination thereof. The elements may be interconnected by any form or medium of digital data communication (e.g., a communications network). Examples of communications networks include a local area network (LAN) or a wide area network (WAN), such as the Internet.

[0116] While certain features of the implementations described herein have been illustrated, various modifications, substitutions, changes, and equivalents will be apparent to those skilled in the art, and it is therefore understood that the appended claims are intended to cover all such modifications and alterations that do not depart from the spirit of the various embodiments.

Claims

1. transmitting, by a user device in a wireless network, a system information request, the system information request being a request for on-demand system information during a random access procedure, the system information request being a request for one or more parameters that enable the user device to communicate within the wireless network; receiving, by the user device prior to acquiring the on-demand system information, an indicator value used to determine an amount of time the user device will wait to acquire the on-demand system information; receiving, by the user device, the on-demand system information during the length of time in response to the system information request; wherein the indicator value is included in minimum system information broadcast by a base station.

2. The method of claim 1 , further comprising waiting, by the user device, for the length of time that the user device expects to receive the on-demand system information.

3. The method of claim 1 , wherein the system information request is included in a random access preamble message.

4. receiving, by a base station in a wireless network, a system information request from a user device, the system information request being a request for on-demand system information during a random access procedure, the request being for one or more parameters that enable the user device to communicate within the wireless network; transmitting from the base station to the user device an indicator value used to determine a length of time for which the base station is configured to deliver the on-demand system information; transmitting the on-demand system information from the base station to the user device during the period of time in response to the system information request; wherein the indicator value is included in minimum system information broadcast by the base station.

5. The method of claim 4 , wherein the system information request is included in a random access preamble message.

6. 1. An apparatus comprising at least one processor and at least one memory containing computer instructions that, when executed by the at least one processor, cause the apparatus to at least: transmitting a system information request, the system information request being a request for on-demand system information during a random access procedure, the request being for one or more parameters that enable the device to communicate in a wireless network; receiving, prior to acquiring the on-demand system information, an indicator value used to determine an amount of time the device will wait to acquire the on-demand system information; receiving the on-demand system information during the length of time in response to the system information request; wherein the indicator value is included in minimum system information broadcast by a base station.

7. 7. The apparatus of claim 6, wherein the at least one processor and the at least one memory containing computer instructions provide the apparatus with: the device waits the amount of time that the device expects to receive the on-demand system information.

8. The apparatus of claim 6 , wherein the system information request is included in a random access preamble message.

9. 1. An apparatus comprising at least one processor and at least one memory containing computer instructions that, when executed by the at least one processor, cause the apparatus to at least: receiving a system information request from a user device, the system information request being a request for on-demand system information during a random access procedure and for one or more parameters that enable the user device to communicate within a wireless network; transmitting to the user device an indicator value used to determine a length of time for which the apparatus is configured to deliver the on-demand system information; transmitting the on-demand system information to the user device during the period of time in response to the system information request; wherein the indicator value is included in minimum system information broadcast by the device.

10. The apparatus of claim 9 , wherein the system information request is included in a random access preamble message.

11. 1. A computer-readable storage medium storing executable instructions that, when executed by at least one processor of a device, cause the device to: transmitting a system information request, the system information request being a request for on-demand system information during a random access procedure, the request being for one or more parameters that enable the device to communicate in a wireless network; receiving, prior to acquiring the on-demand system information, an indicator value used to determine an amount of time the device will wait to acquire the on-demand system information; receiving the on-demand system information during the length of time in response to the system information request; wherein the indicator value is included in minimum system information broadcast by a base station.

12. The computer-readable storage medium of claim 11 , further comprising executable instructions for causing the device to wait the amount of time in anticipation of receiving the on-demand system information.

13. The computer-readable storage medium of claim 11 , wherein the system information request is included in a random access preamble message.

14. A method according to any preceding claim, comprising determining the duration by applying the index value to a duration table.

15. The method according to claim 4 or 5, wherein the index value is used in the user device to determine the duration by applying it to a duration table.

16. 9. Apparatus according to any of claims 6 to 8, arranged to determine the length of time by applying the index value to a length of time table.

17. 11. The apparatus according to claim 9 or 10, wherein the index value is used in the user device to determine the duration by applying it to a duration table.

18. 14. The computer-readable storage medium of claim 11, wherein the executable instructions, when executed by at least one processor of a device, are configured to cause the device to determine the length of time by applying the index value to a length of time table.

Images