Apparatus and method for updating on-demand system information in wireless communication

Abstract

A wireless terminal includes receiver circuitry and processor circuitry. The receiver circuitry is configured to receive, from a base station apparatus, a first type system information (SI) block including scheduling information for configuring a SI window, the SI window being a periodic broadcast occasion for one or more second type system information blocks (SIBs) corresponding. The processor circuitry is configured to determine the SI window based on the scheduling information. The receiver circuitry is further configured to perform a reception procedure to attempt to receive at least one of the second type SIBs within the SI window for a current modification period. In a case that the at least one of the second type SIBs is not received within the SI window, the receiver circuitry is configured to continue the reception procedure in the current modification period.

Description

[0001] This application claims priority and benefit to U.S. Provisional Application 62 / 616,260, filed January 11, 2018, the full text of which is incorporated herein by reference. Technical Field

[0002] The present invention relates to wireless communication, and more particularly to methods, apparatus and techniques for requesting, transmitting, updating and using system information (SI) in wireless communication. Background Technology

[0003] In wireless communication systems, a radio access network typically includes one or more access nodes (such as base stations) that communicate with multiple wireless terminals via radio or air interfaces over radio channels. In some technologies, such wireless terminals are also referred to as user equipment (UEs). The group known as the 3rd Generation Partnership Project (“3GPP”) has committed to defining globally applicable technical specifications and technical reports for current and next-generation wireless communication systems. 3GPP Long Term Evolution (“LTE”) and 3GPP Advanced LTE (LTE-A) are projects that improve upon earlier Universal Mobile Telecommunications System (“UMTS”) mobile phone or device standards to meet future needs.

[0004] In a typical cellular mobile communication system, base stations broadcast certain information required for mobile stations to access the network on radio channels. In Long Term Evolution (LTE) and LTE-Advanced (LTE-A), this information is called "System Information" ("SI"). Each access node, such as an evolved NodeB ("eNB") or a gNB in ​​a 5G New Radio (NR) system, broadcasts this System Information to its coverage area via the Master Information Block (MIB) and several System Information Blocks (SIBs) on the downlink radio resources allocated to the access node.

[0005] Upon entering the coverage area of ​​an eNB or gNB, the wireless terminal (“UE”) needs to acquire all the MIBs / SIBs required for accessing the system. For the UE within coverage, the eNB or gNB periodically broadcasts all MIBs / SIBs related to the services provided, with each type of MIB or SIB being transmitted in designated radio resources at its own predetermined / configurable frequency.

[0006] This periodic delivery method based on full broadcast (e.g., collective broadcasting of all SIBs, not just those required for system access) is effective under conditions where many UEs almost always flow into coverage areas (such as macro cells). However, this method can lead to a waste of valuable radio resources in small cell deployments. Therefore, a more efficient SIB transmission method is needed.

[0007] Therefore, exemplary objectives of the techniques disclosed herein are methods, apparatuses, and techniques for more efficiently transmitting System Information Blocks (SIBs). Summary of the Invention

[0008] In one aspect of the exemplary aspects of the present invention, the technology disclosed herein relates to a wireless terminal including receiver circuitry and processor circuitry. The receiver circuitry is configured to receive a first type of system information (SI) block from a base station device. The first type of SI block includes scheduling information for configuring an SI window, which is a periodic broadcast opportunity for corresponding one or more second type of system information blocks (SIBs). The processor circuitry is configured to determine the SI window based on the scheduling information. The receiver circuitry is further configured to perform a reception process to attempt to receive at least one of the second type of SIBs within the SI window of the current modification period. If at least one of the second type of SIBs is not received within the SI window, the receiver circuitry is configured to continue the reception process within the current modification period.

[0009] In exemplary implementations and modes, the current modification period is one of a plurality of modification periods configured by the base station device, which are recurring time periods.

[0010] In exemplary embodiments and modes, the receiver circuitry is further configured to abort the reception process in the next modification cycle.

[0011] In exemplary embodiments and modes, the receiver circuitry is configured to continue receiving the process during the current modification cycle, even if the receiver circuitry receives a notification message that notifies one or more of the contents of a first type of system information (SI) block or a second type of system information block (SIB).

[0012] In another aspect of the exemplary aspects of the invention, the technology disclosed herein relates to a base station apparatus including processor circuitry and transmitter circuitry. The processor circuitry is configured to generate a first type of System Information (SI) block, the first type of SI block including scheduling information for configuring SI windows, the SI windows being periodic broadcast opportunities for corresponding one or more second type of System Information (SIBs). The SI window of the current modification period is configured such that a wireless terminal can attempt to receive at least one of the second type of SIBs during a reception process performed by the wireless terminal, and if at least one of the second type of SIBs is not received within one or more SI windows, the wireless terminal can continue the reception process in the current modification period. The transmitter circuitry is configured to transmit the first type of System Information (SI) block and one or more second type of System Information (SIBs) to the wireless terminal.

[0013] In exemplary implementations and modes, the current modification period is one of a plurality of modification periods configured by the base station device, which are recurring time periods.

[0014] In another aspect of the exemplary aspects of the invention, the technology disclosed herein relates to a method in a wireless terminal. In a basic mode, the method includes receiving a first type of system information (SI) block from a base station device, the first type of SI block including scheduling information for configuring an SI window, the SI window being a periodic broadcast opportunity for corresponding one or more second type of system information blocks (SIBs); determining the SI window based on the scheduling information; and performing a reception process to attempt to receive at least one of the second type of SIBs within the SI window of a currently modified period. The method further includes continuing the reception process within the current modified period if the at least one of the second type of SIBs is not received within the SI window.

[0015] In exemplary implementations and modes, the current modification period is one of a plurality of modification periods configured by the base station device, which are recurring time periods.

[0016] In exemplary implementations and patterns, the method further includes suspending the receiving process in the next modification cycle.

[0017] In exemplary implementations and patterns, the method further includes continuing the receiving process during the current modification cycle, even if a notification message is received notifying of changes to the content of the first type SI block or the second type SIB.

[0018] In yet another exemplary embodiment and mode, the technology disclosed herein relates to a method in a base station apparatus. In a basic mode, the method includes sending a first type of system information (SI) block to a wireless terminal, the first type of SI block including scheduling information for configuring an SI window, the SI window being a periodic broadcast opportunity for corresponding one or more second type of system information blocks (SIBs); wherein the SI window is determined by the wireless terminal based on the scheduling information. The wireless terminal performs a reception process to attempt to receive at least one of the second type of SIBs within the SI window of the current modification period. If the at least one of the second type of SIBs is not received within the SI window, the wireless terminal continues the reception process within the current modification period.

[0019] In exemplary implementations and modes, the current modification period is one of a plurality of modification periods configured by the base station device, which are recurring time periods. Attached Figure Description

[0020] The foregoing and other objectives, features, and advantages of the technology disclosed herein will become apparent from the more detailed description of the preferred embodiments shown below, as illustrated in the accompanying drawings, in which reference numerals in various views refer to the same parts. The drawings are not necessarily drawn to scale, but rather focus on illustrating the principles of the technology disclosed herein.

[0021] Figure 1 This is a graphical view showing the transition states of the Radio Resource Control (RRC) state machine.

[0022] Figure 2 This is a schematic diagram illustrating an exemplary general communication system including a radio access node and a wireless terminal, wherein when the wireless terminal is in the RRC_CONNECTED state, the wireless terminal requests additional system information (another SI) and the radio access node provides the other SI.

[0023] Figure 3 It is shown by Figure 2 A flowchart illustrating an exemplary basic exemplary action or step performed by a wireless terminal of an exemplary general communication system.

[0024] Figure 4 This is a diagrammatic view of an exemplary format of a System Information Block (SIB) that includes the minimum SI and carries other system information (other SIs).

[0025] Figure 5 This is a diagrammatic view illustrating an exemplary message flow of a video-on-demand (VOD) SIB acquisition process.

[0026] Figure 6A , Figure 6B and Figure 6C This is a diagrammatic view showing the three options for the SIB request process.

[0027] Figure 7 It is a graphical view of a series of modification cycles, showing the generation and transmission of system information messages during the modification cycle, as well as the generation and transmission of notification messages during the "current" modification cycle.

[0028] Figure 8A This is a graphical view illustrating an exemplary format of a paging message that includes a bitmap.

[0029] Figure 8B This is a diagrammatic view illustrating an exemplary format of a paging message, which includes a list of identifiers for system information blocks with changed content.

[0030] Figure 9 This is a diagrammatic view showing an exemplary message flow of SIB updates notified via paging messages.

[0031] Figure 10It is a flowchart that describes the basic actions or steps of a wireless terminal when receiving the minimum SI.

[0032] Figure 11 It is a flowchart that describes the basic actions or steps of a wireless terminal receiving a paging message.

[0033] Figure 12 This is a flowchart illustrating exemplary basic actions or steps performed by an access node when it receives a video-on-demand (SIB) delivery request from a wireless terminal.

[0034] Figure 13 This is a flowchart illustrating exemplary representative actions performed by the access node when a wireless terminal is notified of an upcoming SIB change.

[0035] Figure 14 This is a schematic diagram illustrating a first embodiment of a communication system including a radio access node and a wireless terminal, wherein the wireless terminal waits for a modified period boundary to initiate an SIB request process for a pay-as-you-go SIB.

[0036] Figure 15 It is shown Figure 14 A diagrammatic view of an exemplary message flow implementation.

[0037] Figure 16 It is shown by Figure 14 A flowchart illustrating exemplary representative actions or steps performed by a wireless terminal when receiving a paging message.

[0038] Figure 17 This is a schematic diagram illustrating a second embodiment of a communication system including a radio access node and a wireless terminal, wherein the wireless terminal initiates an SIB request process without waiting for the next modification cycle boundary, but waits for the next modification cycle boundary after the SIB request process is successfully completed to begin the SIB reception process.

[0039] Figure 18 It is shown Figure 17 A diagrammatic view of an exemplary message flow implementation.

[0040] Figure 19 It is shown by Figure 17 A flowchart illustrating exemplary representative actions or steps performed by a wireless terminal when receiving a paging message.

[0041] Figure 20 It is shown by Figure 17 A flowchart illustrating exemplary basic actions or steps performed by an access node to receive a video-on-demand (SIB) delivery request from a wireless terminal.

[0042] Figure 21This is a schematic diagram illustrating a third embodiment of a communication system including a radio access node and a wireless terminal, wherein the radio access node and the wireless terminal agree that whenever the on-demand SIB is updated, the access node can notify the wireless terminal in the current modification cycle, and automatically transmit the updated SIB in one or more corresponding SI windows from the next modification cycle, without the wireless terminal sending a request.

[0043] Figure 22 It is shown Figure 21 A diagrammatic view of an exemplary message flow implementation.

[0044] Figure 23 It is shown by Figure 21 A flowchart illustrating exemplary representative actions or steps performed by a wireless terminal when receiving a paging message.

[0045] Figure 24 It is shown by Figure 21 A flowchart illustrating exemplary basic actions or steps performed by an access node to receive a video-on-demand (SIB) delivery request from a wireless terminal.

[0046] Figure 25 This is a schematic diagram illustrating a third embodiment of a communication system including a radio access node and a wireless terminal, wherein the wireless terminal is configured to initiate both an SIB request process and an SIB reception process for on-demand SIBs when appropriate without waiting for the next modification cycle boundary.

[0047] Figure 26 It is shown Figure 25 A diagrammatic view of an exemplary message flow implementation.

[0048] Figure 27 It is shown by Figure 25 A flowchart illustrating exemplary representative actions or steps performed by a wireless terminal when receiving a paging message.

[0049] Figure 28 It is shown by Figure 25 A flowchart illustrating exemplary basic actions or steps performed by an access node to receive a video-on-demand (SIB) delivery request from a wireless terminal.

[0050] Figure 29 This is a schematic diagram illustrating a third embodiment of a communication system including a radio access node and a wireless terminal, wherein a paging message notifying of a change in the on-demand SIB is received after an SIB request process that requests the same on-demand SIB.

[0051] Figure 30 It is shown Figure 29 A diagrammatic view of an exemplary message flow implementation.

[0052] Figure 31 It is shown by Figure 29 A flowchart illustrating exemplary representative actions or steps performed by a wireless terminal when receiving a paging message.

[0053] Figure 32 It is shown by Figure 29 A flowchart illustrating exemplary basic actions or steps performed by an access node to receive a video-on-demand (SIB) delivery request from a wireless terminal.

[0054] Figure 32 This is a schematic diagram of a sixth embodiment of a communication system including a radio access node and a wireless terminal, wherein a paging message notifying the minimum SI of a change in membership is received after an SIB request process that requests the same on-demand SIB, and the wireless terminal suspends the SIB receiving process upon receiving the paging message.

[0055] Figure 33A It is shown Figure 32 A diagrammatic view of the message flow in an exemplary first scenario of the implementation scheme.

[0056] Figure 33B It is shown Figure 32 A diagrammatic view of an exemplary second-scenario message flow implementation.

[0057] Figure 34 It is shown by Figure 32 A flowchart illustrating exemplary representative actions or steps performed by a wireless terminal when receiving a paging message.

[0058] Figure 35 It is shown by Figure 32 A flowchart illustrating exemplary basic actions or steps performed by an access node to receive a video-on-demand (SIB) delivery request from a wireless terminal.

[0059] Figure 36 This is a schematic diagram of a seventh embodiment of a communication system including a radio access node and a wireless terminal, wherein a paging message notifying the minimum SI of a change in membership is received after an SIB request process that requests the same on-demand SIB, and the wireless terminal may suspend or not suspend the SIB reception process at the next modification cycle boundary.

[0060] Figure 37A It is shown Figure 36 A diagrammatic view of the message flow in an exemplary first scenario of the implementation scheme.

[0061] Figure 37B It is shown Figure 36 A diagrammatic view of an exemplary second-scenario message flow implementation.

[0062] Figure 37C It is shown Figure 36A diagrammatic view of an exemplary second-scenario message flow implementation.

[0063] Figure 38 It is shown by Figure 36 A flowchart illustrating exemplary representative actions or steps performed by a wireless terminal when receiving a paging message.

[0064] Figure 39 It is shown by Figure 36 A flowchart illustrating exemplary basic actions or steps performed by an access node to receive a video-on-demand (SIB) delivery request from a wireless terminal.

[0065] Figure 40 This is a schematic view illustrating an exemplary electromechanical device, which may include node electromechanical devices or terminal electromechanical devices. Detailed Implementation

[0066] For ease of explanation and not limitation, specific details such as specific architectures, interfaces, and technologies are set forth in the following description to provide a thorough understanding of the technologies disclosed herein. However, it will be apparent to those skilled in the art that the technologies disclosed herein can be implemented in other embodiments different from these specific details. That is, those skilled in the art can conceive of various arrangements, which, although not explicitly described or shown herein, embody the principles of the technologies disclosed herein and are included within their spirit and scope. In some cases, detailed descriptions of well-known devices, circuits, and methods have been omitted to prevent the description of the technologies disclosed herein from becoming obscure due to unnecessary details. All statements herein describing the principles, aspects, and implementations of the technologies disclosed, and their specific examples, are intended to cover their structural and functional equivalents. Furthermore, it is intended that such equivalents include both currently known equivalents and future-developed equivalents, i.e., any elements developed that perform the same function, regardless of their structure.

[0067] Therefore, for example, those skilled in the art will understand that the block diagrams herein can represent conceptual views of exemplary circuits or other functional units embodying technical principles. Similarly, it should be understood that any flowchart, state transition diagram, pseudocode, etc., represents various processes that can be substantially represented in a computer-readable medium and thus executed by a computer or processor, whether or not such computer or processor is explicitly shown.

[0068] As used herein, the term "core network" can refer to a device, group of devices, or subsystem within a telecommunications network that provides services to users of that network. Examples of services provided by the core network include aggregation, authentication, call handover, service invocation, and gateways to other networks.

[0069] As used herein, the term "wireless terminal" can refer to any electronic device used to transmit voice and / or data via telecommunications systems, such as (but not limited to) cellular networks. Other terms used to refer to wireless terminals and non-limiting examples of such devices may include user equipment terminal, UE, mobile station, mobile device, access terminal, subscriber station, mobile terminal, remote station, user terminal, terminal, user unit, cellular phone, smartphone, personal digital assistant ("PDA"), laptop computer, netbook, e-reader, wireless modem, etc.

[0070] As used herein, the terms “access node,” “node,” or “base station” can refer to any device or group of devices that facilitates wireless communication or, in other words, provides an interface between a wireless terminal and a telecommunications system. In 3GPP specifications, non-limiting examples of base stations may include Node B (“NB”), Enhanced Node B (“eNB”), Home eNB (“HeNB”), 5G (New Radio [NR]) gNB, or some other similar terms. Another non-limiting example of a base station is an access point. An access point can be an electronic device that enables a wireless terminal to access a data network such as (but not limited to) a local area network (“LAN”), a wide area network (“WAN”), the Internet, etc. While some examples of the systems and methods disclosed herein may be described relative to a given standard (e.g., 3GPP Release 8, 9, 10, 11, and / or 12), the scope of this disclosure should not be limited thereto. At least some aspects of the systems and methods disclosed herein can be used in other types of wireless communication systems.

[0071] As used herein, the terms "telecommunications system" or "communication system" can refer to any network of devices used for transmitting information. A non-limiting example of a telecommunications system is a cellular network or other wireless communication system.

[0072] As used herein, the term "cellular network" can refer to a network distributed across cells, each cell being served by at least one location-fixed transceiver such as a base station. A "cell" can be any communication channel designated by a standardization or regulatory body for International Mobile Telecommunications Advanced ("IMTA Advanced"). All or part of the cells may be adopted by 3GPP as licensed frequency bands (e.g., frequency zones) to be used for communication between a base station (such as a Node B) and a UE terminal. Cellular networks using licensed frequency bands may include configured cells. Configured cells may include cells that the UE terminal is aware of and that are permitted by the base station to transmit or receive information.

[0073] As used herein, “System Information” (“SI”) may include a Master Information Block (MIB) and several System Information Blocks (SIBs) provided on downlink radio resources allocated to an access node. System Information may be broadcast, and some types of System Information may be provided as needed, for example, upon receiving a request for System Information from a radio terminal.

[0074] In various aspects of the techniques disclosed herein, system information is categorized into several classes or types. In exemplary embodiments and modes, the first type of system information is minimal system information (minimum SI), which contains the minimum amount of information required for the UE's initial access to the network and is periodically broadcast by each access node (e.g., an eNB for LTE, a gNB for a 5G radio system). In some configurations, the minimum system SI may consist of a MIB and a limited number of SIBs. The minimum SI may also be referred to as the "basic SI" or first type of system information.

[0075] The second category of system information, such as "Other System Information," "Other SI," or other system information, includes all other types of information, i.e., all types of system information except for the minimum system information. Other SIs may include several System Information Blocks (SIBs) that are not classified as the minimum SI. Other SIs may also be referred to as "Non-Basic SIs." However, the second category of system information should not be confused with SIB type 2, which is a specific (second) system information block (SIB) that can be included in the minimum system information.

[0076] In some exemplary implementations and modes described herein, for each of the SIBs belonging to other SIs, the access node may choose to periodically broadcast the SIB, similar to the SIB in the minimum SI. Alternatively, the access node may choose to avoid transmitting the SIB until it receives a request for on-demand delivery from the UE. In this case, the access node may use the minimum SI to announce the availability of on-demand delivery.

[0077] As described in this article, both access nodes and wireless terminals can manage the corresponding Radio Resource Control (RRC) state machines. The RRC state machine transitions between several RRC states, including RRC_IDLE, RRC_INACTIVE, and RRC_CONNECTED. Figure 1 A state transition diagram of the RRC states is depicted. From the advantageous position of the wireless terminal, such as the user equipment (UE), the RRC states can be simply represented as follows:

[0078] RRC_IDLE:

[0079] • UE-specific DRX (Discontinuous Receiver) can be configured by the upper layer;

[0080] • UE-controlled mobility based on network configuration;

[0081] ·UE:

[0082] monitor the paging channel;

[0083] Perform neighboring cell measurements and cell (re)selection;

[0084] Obtain system information.

[0085] RRC_INACTIVE:

[0086] • UE-specific DRX can be configured by the upper layer or the RRC layer;

[0087] • UE-controlled mobility based on network configuration;

[0088] • UE stores access layer (AS) context;

[0089] ·UE:

[0090] monitor the paging channel;

[0091] Perform neighboring cell measurements and cell (re)selection;

[0092] When moving outside the RAN-based notification area, perform a RAN-based notification area update;

[0093] Obtain system information.

[0094] RRC_CONNECTED:

[0095] • UE stores AS context.

[0096] • Transmit unicast data to / from the UE.

[0097] • At lower layers, the UE can be configured with UE-specific DRX;

[0098] • Network-controlled mobility, i.e., handover within the NR and to / from the E-UTRAN;

[0099] ·UE:

[0100] monitor the paging channel;

[0101] Monitor the control channel associated with the shared data channel to determine whether data has been scheduled for it;

[0102] Provides channel quality and feedback information;

[0103] Perform neighboring cell measurements and measurement reports;

[0104] Obtain system information.

[0105] The technology disclosed herein relates to, for example, apparatus, methods, and processes for on-demand acquisition and / or updating of SIBs in other SIs (other SISIBs) or SIBs in other SIs (other SI SIBs), and specifically, but not exclusively, to timing for initiating / stopping SIB requests and / or SIB reception processes.

[0106] Figure 2 An example communication system 20 is shown, in which a radio access node 22 communicates with a wireless terminal 26 via an air or radio interface 24 (e.g., a Uu interface). As described above, the radio access node 22 can be any suitable node for communicating with the wireless terminal 26, such as a base station node, or an eNodeB (“eNB”) or gNB. Node 22 includes node processor circuitry (“node processor 30”) and node transceiver circuitry 32. Node transceiver circuitry 32 typically includes node transmitter circuitry 34 and node receiver circuitry 36, also referred to as a node transmitter and a node receiver, respectively.

[0107] Wireless terminal 26 includes a terminal processor 40 and a terminal transceiver circuit 42. The terminal transceiver circuit 42 typically includes a terminal transmitter circuit 44 and a terminal receiver circuit 46, also referred to as terminal transmitter 44 and terminal receiver 46, respectively. Wireless terminal 26 also typically includes a user interface 48. The terminal user interface 48 is used for user input and output operations and may include, for example, a screen such as a touchscreen that can display information to the user and receive user input. The user interface 48 may also include other types of devices, such as speakers, microphones, or haptic feedback devices.

[0108] For both radio access node 22 and radio interface 24, the corresponding transceiver circuit 32 includes an antenna. Transmitter circuits 34 and 44 may include, for example, one or more amplifiers, modulation circuits, and other conventional transmitting devices. Receiver circuits 36 and 46 may include, for example, amplifiers, demodulation circuits, and other conventional receiver devices.

[0109] In general operation, node 22 and wireless terminal 26 communicate with each other via radio interface 24 using predefined information configurations. As a non-limiting example, radio access node 22 and wireless terminal 26 may communicate via radio interface 24 using information “frames” that can be configured to include various channels. In Long Term Evolution (LTE), for example, a frame, which may have both downlink and uplink portions, may include multiple subframes, where each LTE subframe is sequentially divided into two time slots. The frame can be conceptualized as a resource grid (two-dimensional grid) composed of resource elements (REs). Each column of the two-dimensional grid represents a symbol (e.g., OFDM symbols on the downlink (DL) from the node to the wireless terminal; SC-FDMA symbols in the uplink (UL) frame from the wireless terminal to the node). Each row of the grid represents a subcarrier. The frame and subframe structures are merely examples of formatting techniques for information transmitted via the radio interface or air interface. It should be understood that “frame” and “subframe” are used interchangeably or may include or be implemented by other information formatting units, and therefore may include other terms (such as block).

[0110] To enable information transmission between radio access node 22 and wireless terminal 26 via radio interface 24 Figure 2 The node processor 30 and terminal processor 40 are shown to include corresponding information processing programs. For an exemplary embodiment in which information is transmitted via frames, the information processing program for the radio access node 22 is shown as node frame / signal scheduler / processor 50, while the information processing program for the wireless terminal 26 is shown as terminal frame / signal processor 52.

[0111] The node processor 30 of radio access node 22 also includes a system information (SI) generator 54. As described above, at least some of the system information generated and provided by the node radio resource controller 60 is minimal system information (minimal SI) represented by a minimal SI processing program 54M, also referred to as first-class system information. Some of the system information may be generated by... Figure 2 Other system information (other SIs), also known as second-class system information, is represented by other SI processing procedures 54O. The wireless terminal 26 uses the system information (SIs) generated by the radio access node 22. Some of the minimum SIs can notify the wireless terminal 26 of the availability of other SIs. Figure 2 A general message 2-1 is shown, through which the node radio resource controller 54 provides a minimum SI to the wireless terminal 26. In some exemplary embodiments, due to message 2-1, when the availability of other SIs is known, for example, the wireless terminal 26 specifically requests other system information on demand, as described herein. The terminal processor 40 of the wireless terminal 26 includes, for example, an SI processor 56 to facilitate the acquisition and use of system information.

[0112] The technology disclosed herein relates to, for example, apparatus, methods, and processes for on-demand acquisition and / or updating of SIBs in other SIs (Other SI System Information Blocks (SIBs)) / SIBs in other SIs (Other SI System Information Blocks (SIBs)), and specifically, but not exclusively, to timing for initiating / stopping SIB requests and / or SIB reception processes. Since the technology disclosed herein relates to Radio Resource Control (RRC) processes in at least some of the exemplary embodiments and modes, therefore... Figure 2 Each of the node processors 30 is shown as including a node radio resource control (RRC) controller 60, such as a node RRC controller 60. The node RRC controller 60 can execute an instance of an RRC state machine for each wireless terminal communicating in the access node 22, wherein each instance records the RRC state transitions experienced by the wireless terminal associated with the corresponding instance.

[0113] Figure 2 It is also shown that, in addition to the terminal SI processor 56, the terminal processor 40 of the wireless terminal 26 also includes a terminal RRC controller 70. The terminal RRC controller 70 includes or executes the RRC state machine discussed above, which is in an RRC state (as described above and as...) Figure 2 The switching between (as shown) is used for communication involving wireless terminal 26.

[0114] therefore, Figure 2 The access node 22 is shown to include a node processor 30 (e.g., node processor circuitry 30), a transmitter circuitry 34, and a receiver circuitry 36. The transmitter circuitry 34 is configured to transmit first-type system information via a radio interface, the first-type system information including the availability of second-type system information blocks (SIBs). The receiver circuitry 36 is configured to receive a request message from a wireless terminal requesting the delivery of an available second-type SIB. The transmitter circuitry 34 is further configured to transmit the second-type SIB to the wireless terminal.

[0115] therefore, Figure 2 The diagram illustrates a wireless terminal 26 communicating with an access node, such as access node 22, of a radio access network (RAN) via a radio interface 24. The wireless terminal 26 includes receiver circuitry 46, transmitter circuitry 44, and a terminal processor 40, such as terminal processor circuitry. Receiver circuitry 46 is configured to receive first-type system information via the radio interface. Terminal processor circuitry is configured to generate a request message requesting the availability of a second-type SIB. Transmitter circuitry 44 is configured to transmit the request message via the radio interface when in a connected state. Receiver circuitry 46 is also configured to receive second-type SIBs when in a connected state.

[0116] Figure 3 This illustrates a wireless terminal (such as) that integrates with an operating radio access network (RAN). Figure 2 The following are representative examples of actions or steps performed by the general method of the wireless terminal 26. Action 3-1 includes the wireless terminal receiving a minimum SI broadcast from the current serving access node (e.g., access node 22). The minimum SI can be found in messages such as... Figure 2 The minimum SI is broadcast in message 2-1. The minimum SI may contain information about other SIs, including delivery method (periodic broadcast / on-demand), scheduling information, validity information, etc. Based on this information, the wireless terminal in action 3-2 can determine which SIBs it wants to on-demand. As action 3-3, the wireless terminal can send a request message to the access node (e.g., ...). Figure 2 (As depicted in message 2-2), this request message indicates the SIB that the wireless terminal wishes to acquire. As an action 3-4, the wireless terminal 26 may attempt to receive the requested SIB (using...). Figure 2 (Messages 2-3 sent).

[0117] As mentioned above, the first type of system information includes the availability of a second type of system information block (SIB), a request message requests the delivery of an available second type of SIB, and the second type of SIB is sent to the wireless terminal. It should be understood that the references herein to "second type of system information block (SIB)" or "second type of SIB" refer to one or more other system information items (other SIs), such as one or more second type of system information blocks (SIBs). In some exemplary cases, only one second type of SIB may actually be advertised as available and therefore requested for delivery. However, in other exemplary cases, multiple second type of SIBs (e.g., multiple other SIs) may be advertised as available and requested for delivery.

[0118] In some configurations, information about the availability and delivery methods of other SI SIBs can be included in SIB Type 1, which is one of the SIBs in the minimum SI. Figure 4 The example format for SIB type 1 is shown, including schedulingInfoList, si-WindowLength, otherSIBInfoList, and other possible configuration parameters. otherSIBInfoList is a list of otherSIBInfo, which in turn includes SIB-Type, the SIB identifier, validityInfo, SIB validity information (valueTag, areaID, and other parameters such as validity timers), and deliveryMethod indicating whether the SIB is periodically broadcast or transmitted upon request (on-demand).

[0119] The `schedulingInfoList` contains a list of scheduling information elements, each including a periodicity and a corresponding SIB type (si-Periodicity and one or more SIB-Types). The actual broadcast opportunity (i.e., timing / resource) for a given SIB can be determined by a predetermined or network-configured formula that is a function of at least the corresponding periodicity. At each opportunity, the broadcast of the SIB can occur for a duration of the window length (si-WindowLength). Hereinafter, broadcast opportunities are also referred to as SI windows. More than one SIB may be transmitted within the same SI window.

[0120] Figure 5 This is an exemplary message flow diagram of the on-demand-delivered SIB acquisition process. As shown in Action 5-0, the wireless terminal 26, in the RRC_IDLE, RRC_INACTIVE, or RRC_CONNECTED state, stores the content of SIB#k with valueTag=a, which the wireless terminal has previously received. As Action 5-1, the wireless terminal can acquire SIB1 as the minimum SI from the currently serving access node, indicating that SIB#k with valueTag=b is available via on-demand delivery. In the following, it is assumed that whenever the wireless terminal receives SIB1, it has already received the MIB. By knowing that the stored SIB#k is now outdated (because it has valueTag=a), the wireless terminal can decide to acquire the latest version of SIB#k and can initiate the SIB request process represented by Action 5-2 and described herein. After the SIB request process is successful, the wireless terminal can begin the SIB receiving process, which is roughly as follows: Figure 5 Action 5-3 is shown in the diagram. During SIB reception, the wireless terminal uses the specified SI window (derived from the scheduling information (scheduleInfo) in SIB1) to retrieve the information. Figure 5 (The dotted rectangle in the diagram shows the process of monitoring signals from the access node in an attempt to receive the requested SIB#k.) Figure 5 Action 5-3a shows the first transmission of the requested SIB# (which failed), and action 5-3b shows the second transmission of the requested SIB# (which succeeded). Figure 5 In the depiction of the SIB reception process, the tail of the vertically downward-pointing arrow is associated with the start of the SIB reception process, while the head of the same vertically downward-pointing arrow is associated with the end of the SIB reception process (upon successful reception of SIB#k). Figure 5Action 5-4 further illustrates that even after the wireless terminal has successfully received the searched SIB#k, other transmissions of the requested system information can still be performed. Therefore, if SIB#k is not successfully received within the SI window during the SIB reception process, the wireless terminal can re-receive SIB#k at the next SI window.

[0121] In one configuration, the wireless terminal may use a counter that increments at each SI window for a specific SIB (e.g., SIB#k). In this configuration, the SIB reception process may terminate when the requested SIB is successfully received or when the counter reaches its maximum value. In another configuration, the wireless terminal starts a timer at the beginning of the SIB reception process. In this configuration, the SIB reception process may terminate when the requested SIB is successfully received or when the timer expires. The maximum counter value or timer value may be pre-configured or configured by the network via system information, and may be general to all SIB types or per SIB type. The condition under which the wireless terminal terminates the SIB reception process is referred to herein as the "termination condition".

[0122] Figure 6A , Figure 6B and Figure 6C Three options for the SIB request process are shown. These are applicable to wireless terminals in any of the RRC states. Figure 6A As shown in Action 6a-1, a request for on-demand delivery of other SI SIBs can be made by sending a random access preamble, which may include a sequence selected from a set of available sequences configured by the access node via a minimum SI. The given sequence is identified by a preamble index. When the access node detects the transmission of the preamble sequence, it can respond to it with a random access response, which includes the preamble index corresponding to the sequence (see Action 6a-2). Upon receiving the random access response, the wireless terminal can verify whether the preamble index in the random access response matches the preamble index associated with the preamble sequence, and then, as Action 6a-3, send a SystemInformationRequest message to the access node including the identity identifier (e.g., SIB#k) of the SIB that the wireless terminal wishes to receive. In response, as Action 6a-4, the access node can send a SystemInformation message acknowledging the request, indicating that the requested SIB will be broadcast from the next SI window scheduled for the requested SIB.

[0123] In one configuration, an access node may include a set of leading indices in the minimum SI, each leading index being specified for requesting on-demand delivery of one or more specific other SI SIBs. Figure 6BAn exemplary SIB request procedure using this configuration is illustrated, wherein a radio terminal in any RRC state can transmit a random access preamble sequence given by a preamble index associated with the SIB already selected by the radio terminal (as shown in Action 6b-1). The request procedure can be considered successful when the radio terminal receives a random access response including the preamble index (Action 6b-2).

[0124] Figure 6C The SIB request procedure in the RRC_CONNECTED state can be applied to wireless terminals, in which a SystemInformationRequest message of action 6c-1 is sent without a random access preamble / response.

[0125] In any of the three options disclosed above, if the SIB request process is successful, the wireless terminal can proceed to the SIB reception process. Otherwise, the wireless terminal may assume that the serving cell (controlled by the access node) is disabled, which will trigger cell reselection.

[0126] Figure 7 This is a diagrammatic view of exemplary operations and patterns for updating the content of at least one periodically broadcast SIB. Figure 7 The generation and transmission of system information messages are depicted by solid vertical arrows. Each solid vertical arrow represents a separate system information message containing at least one specific type of SIB. System information messages are... Figure 7 This is shown as generation along the horizontal axis of depicting time, specifically across the three "modification cycles." Modification cycles occur between modification cycle boundaries. Modification cycle boundaries are... Figure 7 The middle part is depicted by vertical dashed lines. Figure 7 Specifically, four modification cycle boundaries are shown: the first or leftmost modification cycle boundary, which marks or depicts the start of the "previous" modification cycle; the second (from...)... Figure 7 The first modification cycle boundary is marked by the left side of the first modification cycle, signifying the end of the "previous" modification cycle and the beginning of the "current" modification cycle; the second modification cycle boundary is marked by the left side of the first modification cycle, signifying the end of the "current" modification cycle and the beginning of the "next" modification cycle; and the third modification cycle boundary is marked by the left side of the first modification cycle, signifying the end of the "next" modification cycle. It should be understood that other modification cycles may have occurred before the "previous" modification cycle, and may occur after the "next" modification cycle during future modifications.

[0127] "Modification period" can be any predefined time period established by any predetermined agreement. For example, a modification period can be the same as or similar to the concept of a modification period defined for LTE in 3GPP TS 36.304 and 36.331, both of which are incorporated herein by reference. It is anticipated that similar time depictions can be used for future technologies, such as fifth-generation, and therefore the modification period used herein includes such similar time periods, whether or not explicitly marked as "modification period".

[0128] Figure 7 The system information messages are shown as periodic, with six system information messages transmitted between adjacent modification cycle boundaries (for illustrative purposes). The number of system information messages between modification cycle boundaries is not limited to or restricted to six, as more or fewer system information messages can be transmitted. Figure 7 The system information messages for the "previous" and "current" modification periods are described as "SIB XMT," while the system information messages for the "next" modification period are described as "SIB'XMT." The unfilled references to the system information messages for the "previous" and "current" modification periods reflect the fact that the content of the system information blocks in these system information messages does not change during the "previous" and "current" modification periods. For example, if any system information message in the "previous" and "current" modification periods carries content of class SIB2 (SIB2), the content of each transmission of SIB#2 is the same as other transmissions of SIB2. Similarly, if any system information message in the "previous" and "current" modification periods carries content of SIB3, the content of each transmission of SIB#3 is the same as other transmissions of SIB3. Of course, different numbers of system information blocks may have different contents, but similarly numbered system information blocks... Figure 7 The "previous" modification cycle and the "current" modification cycle each contain the same content.

[0129] Figure 7 The system information message for the "next" modification cycle is described differently as "SIB'XMT". The padding symbol "SIB'" indicates that the content of at least one system information block carried in at least one system information message has changed since the previous modification cycle, for example, since Figure 7Since the current "modification cycle" in the scenario. For example, in the "next" modification cycle, the content of system information block SIB2 may change from the content of a similarly numbered system information block SIB2 in the "current" modification cycle. A change in the content of any field or information element of SIB2 results in a "modified" SIB2. Furthermore, when the content of one type of system information block changes (e.g., SIB2), the content of another system information block (e.g., SIB4) may also have changed.

[0130] The wireless terminal may be able to detect or understand that the content of a system information block has changed even after the content has actually changed, such as after transmitting a system information message that includes changes to the system information block. For example, in Figure 7 After the start of the "next" modification cycle, the wireless terminal may be able to determine or detect changes to the content of one or more System Information Blocks (SIBs). However, such retrospective or reactive detection of changes to the content of SIBs and switching to the new SIB content may require additional power consumption on the wireless terminal. In contrast, the access node may broadcast a notification message configured to indicate a change in the content of at least one of the SIBs. The node processor 30 of access node 22 includes a notification message generator 55. The notification message generator 55 generates a notification message configured to indicate a change in the content of at least one of the SIBs. The notification message generator 55 generates a notification message NM that warns one or more wireless terminals that the content of one or more SIBs will change at the boundary of the next modification cycle. The notification message NM warns one or more wireless terminals that the content of one or more SIBs will change at the boundary of the next modification cycle. Preferably, the notification message generator 55 is configured to schedule the transmission of multiple notification messages. For example, in Figure 7 In this context, the access node transmits a notification message NM during the "current" modification period, thereby warning one or more wireless terminals that a change in the content of one or more system information blocks will occur, for example, at the boundary of the next modification period of the "next" modification period. The notification message NM may be generated before a predetermined modification period boundary, before the initial modification period boundary of the "next" modification period. In such cases, the predetermined modification period boundary marks the beginning of the period in which the content of at least one system information block changes from the previous modification period. The notification message NM is generated by... Figure 7 The vertical dashed arrow in the diagram is shown. For illustration, Figure 7 Five such notification messages NM are shown, but more or fewer can be generated.

[0131] The notification message NM may also be referred to herein as a "paging message," and therefore the notification message generator may also be referred to as paging generator 55. Thus, in some exemplary embodiments and modes, the notification message NM may take the form of a regular paging message as understood in 3GPP. However, the notification message NM is not limited to a regular paging message and does not need to take the form of any particular type of message. In at least some exemplary embodiments and modes, the notification message NM may be a broadcast message, not necessarily directed to or limited to any particular wireless terminal, and not necessarily intended to be propagated to multiple wireless terminals served by the access node. Furthermore, it should be understood that (as with regular paging messages), the radio resources on which the access node can transmit paging messages may be predetermined and periodic. In practice, whether the access node actually transmits on such scheduled resources (e.g., at a specific time) depends on the access node: if there is no content to be transmitted, the access node may not transmit anything at that specific time. In some configurations, there is an agreement between the access node and the wireless terminal regarding the resources that the access node 22 uses to send paging messages (if any) to that particular wireless terminal. Furthermore, in some exemplary implementations and patterns, it is assumed that the wireless terminal at least monitors agreed-upon resources (paging timing) to see if a paging message addressed to that particular wireless terminal exists. For example, in Figure 7 In the example scenario, a specific wireless terminal knows through a pre-arranged agreement that it should monitor notification messages represented by an asterisk, i.e., notification messages NM*.

[0132] In some configurations, the notification message (NM) can specifically indicate which SIBs need to be updated. For example, in an implementation where the notification message NM includes a paging message (PM), the systemInfoModification information element in the paging message can specifically indicate which SIBs need to be updated. Figure 8A An exemplary format of a paging message including a bitmap is shown. Members of the bitmap correspond to corresponding system information block numbers and indicate, via binary values ​​(e.g., "1" or "0"), whether a change in the content of the corresponding system information block exists at the boundary of the next modification cycle. Alternatively, the notification message may include fields (e.g., systemInfoModification) that are expected to identify (e.g., by name or SIB block number or SIB identifier) ​​a specific system information block that will have changed content. For example, in Figure 8B In the exemplary paging message P, the information element systemInfoModification lists those with identifiers sibid=b, sibid=e, and sibid=x in the system information block with modified content.

[0133] Figure 9This is an exemplary message stream for SIB updates notified via paging messages, where the SIB#j to be updated is broadcast periodically. As reflected in action 9-1, before receiving the paging message, any of the radio terminals in the RRC state has already acquired the latest minimum SI, indicating that SIB#j with valueTag=p is being broadcast periodically. The radio terminal eventually receives the paging message of action 9-2, which notifies the radio terminal of the upcoming change on SIB#j after the next modification cycle boundary. The radio terminal may wait for the next modification cycle boundary and then begin the SIB reception process, which includes monitoring the SI window of SIB#j (indicated by the scheduleInfo of the minimum SI) until one of the aforementioned termination conditions. The SIB reception process is represented by a vertical arrow, the tail of which marks the start of the SIB reception process and the head of which marks the end of the SIB reception process, which ends upon successful reception of SystemInformation message 9-3b.

[0134] Figure 10 The procedure for wireless terminal 26 upon receiving the minimum SI is illustrated. Wireless terminal 26, in either of the RRC states, receives the minimum SI from the currently serving access node via signaling messages, as shown, for example, in action 10-2. For each SIB type required by the wireless terminal for the desired service, the corresponding value tag in the minimum SI is compared with the stored SIB value tag (if any) (see action 10-3). If the two value tags match, no action is taken (proceed to step 10-10). Otherwise, at action 10-4, it is checked whether the SIB is a demand SIB. If the SIB is a demand SIB, the aforementioned SIB request procedure can be initiated as action 10-5. If the SIB reception procedure is successful, the wireless terminal can proceed to the aforementioned SIB reception procedure as action 10-7. If the check in action 10-4 is negative, the wireless terminal can also enter the SIB reception procedure. If the SIB reception procedure checked at action 10-6 is unsuccessful, the wireless terminal may consider the serving cell to be blocked, resulting in a cell reselection procedure (action 10-9). During the SIB reception process (Action 10-7), the wireless terminal monitors one or more SI windows of the requested SIB that occur after the SIB request process ends (see [link to SIB request process]). Figure 9 This continues until one of the aforementioned termination conditions is met (e.g., the SIB receiving process is considered successful at action 10-8).

[0135] Figure 11An exemplary operation of a wireless terminal 26 receiving a paging message is shown (as shown in action 11-2). As action 11-3, the wireless terminal checks whether the paging message indicates an incoming call to the wireless terminal. If so, the wireless terminal can proceed to RRC connection establishment (action 11-8). Otherwise, as action 11-4, the wireless terminal can further check whether the message indicates any SIB change to be scheduled. If it is determined at action 11-4 that at least one SIB type will change, as action 11-5, the wireless terminal can wait until the next modification cycle boundary, and then begin the SIB reception process at that time (as action 11-6), as previously disclosed. Figure 11 This operation is for periodically broadcast SIBs; the following implementation discloses an operation for on-demand based SIBs.

[0136] Figure 12 This is an exemplary operation flowchart of access node 22 receiving a request for on-demand SIB delivery from a wireless terminal when periodically broadcasting the minimum SI. If, as action 12-1, access node 22 receives a request for SIB#k, access node 22 can proceed to the on-demand SIB transmission process as shown in action 12-3. As shown in action 12-2, access node 22 can wait for the next SI window for SIB#k, and then (as shown in action 12-3) broadcast SIB#k in that window. The access node can repeat the broadcast multiple times in subsequent SIB#k SI windows until the repetition ends (as shown in action 12-4). The number of repetitions can be pre-configured, or equal to the aforementioned maximum counter value configured to the wireless terminal via system information.

[0137] Figure 13 This is an exemplary flowchart illustrating how an access node notifies a wireless terminal of an upcoming SIB change. This operation can begin at the boundary of each modification cycle. The access node periodically transmits a paging message at each paging time. Figure 13 Action 13-1 shows a check to determine whether any SIBS should be updated from the next modification cycle. When no SIB changes are scheduled, as shown in Action 13-2, the systemInfoModification message is cleared (no indication of change). Afterward, a paging message can be transmitted as shown in Action 13-3. When the access node decides to change some of the SIB types, as shown in Action 13-5, it can be based on... Figure 8A or Figure 8BThe format described in the document sets information elements accordingly to indicate the SIB type to be changed. The access node can continue sending paging messages with the set of information elements (as shown in Action 13-6) until the end of the current modification cycle (as determined in Action 13-7). At the boundary of the next modification cycle, if the SIB change is valid, the access node can update the SIB content, as shown in Action 13-8.

[0138] First exemplary implementation scheme

[0139] Figure 14 An exemplary communication system is illustrated, wherein wireless terminal 26-14 waits for a modification period boundary to initiate an SIB request process for a on-demand SIB. Therefore, terminal processor 40 includes a request generator 72-14 configured to initiate an SIB request process for the on-demand SIB after waiting for the modification period boundary. That is, wireless terminal 26-14 initiates a request for the changed SIB after the modification period boundary. As illustrated herein, the SIB processor 56 of wireless terminal 26-14 is also configured to receive the requested SIB during the next modification period. Other elements and functions of wireless terminal 26-14 and access node 22 are similar. Figure 2 The foregoing description and from Figure 2 As understood from the preceding description.

[0140] Figure 15 This illustrates, for example, the interaction between access node 22 and wireless terminal 26-14. Figure 14 The exemplary representative actions or steps performed in the communication network, and the exemplary messages transmitted therein. For the first exemplary embodiment and mode, the wireless terminal may be in any of the RRC states and (as shown in action 15-0) has already stored the content of SIB#k with valueTag = a. In this example, the wireless terminal may receive an SIB1 indicating that SIB#k will be delivered on demand, and the current latest version (value tag) of SIB#k is valueTag = a. Since the wireless terminal has already stored the same version of SIB#k, it does not need to take any action regarding the acquisition of SIB#k.

[0141] Finally, as shown in action 15-2, wireless terminal 26-14 receives the paging message (corresponding to...). Figure 7The paging message (NM*) indicates that SIB#k will be updated from the next modification period. Wireless terminal 26-14 can wait for the next modification period boundary, and after the next modification boundary, it can then initiate an SIB request procedure (represented as action 15-3) to request on-demand delivery of SIB#k. If the SIB request procedure succeeds, the access node can transmit SIB#k in one or more SI windows associated with it as part of the SIB reception procedure. The SIB reception procedure has [a specific function / mechanism]. Figure 15 The vertical arrow indicates the duration, with the tail of the arrow indicating the start of the SIB reception process and the head indicating the end of the SIB reception process. Actions 15-4a and 15-4b include actions of the SIB reception process performed as a result of the SIB request process. Action 15-4a indicates that SIB#k was not successfully received; action 15-4b indicates that SIB#k was successfully received. Wireless terminal 26-14 may monitor such an SIB window until one of the aforementioned termination conditions is met. For example, upon successfully receiving the SystemInformation message of action 15-4, wireless terminal 26-14 may terminate its SIB reception process because a search for SIB#k with valueTag=b has been received.

[0142] Figure 16 Exemplary actions or steps performed by the wireless terminal 26-14 upon receiving a paging message from the first embodiment are shown. Figure 16 Similar to Figure 11 However, it includes additional steps to handle situations where SIB updates are scheduled on some on-demand SIBs. Figure 16Action 16-2 shows that wireless terminal 26-14 receives a paging message. As action 16-3, the wireless terminal checks whether the paging message indicates an incoming call to the wireless terminal. If so, the wireless terminal can proceed to RRC connection establishment (action 16-8). Otherwise, the wireless terminal can further check whether the message indicates any SIB change to be scheduled. Two checks can be performed: as action 16-4a, wireless terminal 26-14 can check whether the paging message indicates an SIB update for a pay-as-you-go SIB; as action 16-4b, wireless terminal 26-14 can check whether the paging message indicates an SIB update for a broadcast SIB. If the paging message is not for a pay-as-you-go SIB, for example, if the decision of action 16-4a is negative, then the check of action 16-4b is performed. Furthermore, if the decision in action 16-4b is affirmative, for example, if the paging message is for a broadcast SIB, then as action 16-5a, the radio terminal can wait until the next modification cycle boundary, and then begin the SIB reception procedure (as action 16-6), as previously disclosed. If it is determined at action 16-4a that the paging message indicating the SIB change is for a pay-as-you-go SIB, then radio terminal 26-14 waits for the next modification cycle boundary (action 16-5b). After the next modification cycle boundary occurs, as action 16-11, radio terminal 26-14 can begin executing the SIB request procedure (action 16-11). If the SIB request procedure in action 16-11 is successful, then radio terminal 26-14 can begin the SIB reception procedure for a pay-as-you-go SIB (action 16-6). If the SIB request procedure in action 16-11 is unsuccessful, or if it is determined (at action 16-7) that the SIB reception procedure is unsuccessful, then cell reselection is performed (action 16-9). If the SIB reception process is successful, then Figure 16 The process terminates (Action 16-10).

[0143] Therefore, Figure 16 In this case, the wireless terminal can wait for the next modification cycle boundary before initiating the SIB request procedure (Action 16-12). When the SIB request procedure is successfully completed, it can proceed to the SIB reception procedure (Action 16-7).

[0144] It should be understood that Figure 10 , Figure 12 and Figure 13 The concepts and processes are applicable to the first implementation scheme.

[0145] Second exemplary implementation scheme

[0146] Figure 17An exemplary communication system is illustrated, in which wireless terminal 26-17 initiates an SIB request process without waiting for the next modification cycle boundary, but after the SIB request process is successfully completed, wireless terminal 26-17 waits for the next modification cycle boundary to begin the SIB reception process. Therefore, terminal processor 40 includes a request generator 72-17 configured to initiate an SIB request process for a pay-as-you-go SIB without waiting for the next modification cycle boundary. As illustrated herein, the SIB processor 56 of wireless terminal 26-17 can be configured to wait for the next modification cycle boundary to begin the SIB reception process. In one exemplary embodiment, wireless terminal 26-17 and access node 22 may agree to begin the SIB reception process after the modification cycle boundary when the pay-as-you-go SIB will be updated in the next modification cycle. Such an agreement may be pre-configured or may be configured by the network (e.g., via access node 22) using, for example, system information. Other elements and functions of wireless terminal 26-17 and access node 22 are similar. Figure 2 The foregoing description and from Figure 2 As understood from the preceding description.

[0147] Figure 18 This illustrates, for example, the interaction between access node 22 and wireless terminals 26-17. Figure 14 The exemplary representative actions or steps performed in the communication network, and the exemplary messages transmitted therein. For the second exemplary embodiment and mode, the wireless terminal may be in any of the RRC states and (as shown in action 18-0) has already stored the content of SIB#k with valueTag = a. In this example, as shown in action 18-1, the wireless terminal may receive SIB1 indicating that SIB#k will be delivered on demand, and the current latest version (value tag) of SIB#k is valueTag = a. Since the wireless terminal has already stored the same version of SIB#k, it does not need to take any action regarding the acquisition of SIB#k.

[0148] Finally, as shown in action 18-2, the wireless terminal 26-17 receives the paging message (corresponding to...). Figure 7 The paging message (NM*) indicates that SIB#k will be updated from the next modification period. Wireless terminals 26-17 do not wait for the next modification period boundary, but instead initiate an SIB request procedure (represented as action 18-3) before the next modification period boundary to request on-demand delivery of SIB#k. If the SIB request procedure succeeds, the access node can transmit SIB#k in one or more SI windows associated with it as part of the SIB reception procedure after the next modification period boundary. The SIB reception procedure has [a specific function / mechanism]. Figure 18The vertical arrow indicates the duration, with the tail of the arrow indicating the start of the SIB reception process and the head indicating the end of the SIB reception process. Actions 18-4a and 18-4b include actions of the SIB reception process performed as a result of the SIB request process. Action 18-4a indicates that SIB#k was not successfully received; action 18-4b indicates that SIB#k was successfully received. Wireless terminal 26-17 may monitor such an SIB window until one of the aforementioned termination conditions is met. For example, upon successfully receiving the SystemInformation message of action 18-4, wireless terminal 26-17 may terminate its SIB reception process because a search for SIB#k with valueTag=b has been received.

[0149] Figure 19 It shows the result of Figure 17 The exemplary actions or steps performed by the wireless terminals 26-17 are also used as exemplary operation flowcharts of the wireless terminals in the second embodiment. Figure 19 Similar to Figure 16 The difference is that the SIB request process is initiated before the next modification cycle boundary. Figure 19Action 19-2 shows that wireless terminal 26-17 receives a paging message. As action 19-3, the wireless terminal checks whether the paging message indicates an incoming call to the wireless terminal. If so, the wireless terminal can proceed to RRC connection establishment (action 19-8). Otherwise, the wireless terminal can further check whether the message indicates any SIB change to be scheduled. Two checks can be performed: as action 19-4a, wireless terminal 26-17 can check whether the paging message indicates an SIB update for a pay-as-you-go SIB; as action 19-4b, wireless terminal 26-17 can check whether the paging message indicates an SIB update for a broadcast SIB. If the paging message is not for a pay-as-you-go SIB, for example, if the decision of action 19-4a is negative, then the check of action 19-4b is performed. Furthermore, if the decision in action 19-4b is affirmative, for example, if the paging message is for a broadcast SIB, then as action 11-5a, the radio terminal can wait until the next modification cycle boundary, and then begin the SIB reception procedure (as action 11-6), as previously disclosed. If it is determined at action 19-4a that the paging message indicating an SIB change is for a pay-as-you-go SIB, then radio terminal 26-17 does not wait for the next modification cycle boundary, but instead begins the SIB request procedure (action 19-11). If the SIB request procedure in action 19-11 is successful (action 19-12), then radio terminal 26-17 waits for the next modification cycle boundary (action 19-5b). After the next modification cycle boundary occurs, radio terminal 26-17 can begin the SIB reception procedure for the pay-as-you-go SIB (action 19-6). If the SIB request procedure in action 19-11 is unsuccessful, or if it is determined (at action 19-7) that the SIB reception procedure is unsuccessful, then cell reselection is performed (action 19-9). If the SIB reception process is successful, then Figure 19 The process terminates (actions 19-10).

[0150] Therefore, Figure 19 In this regard, the wireless terminal does not wait for the next modification cycle boundary before initiating the SIB request procedure, but instead initiates the SIB request procedure before the next modification cycle boundary (Action 19-11). When the SIB request procedure is successfully completed, the wireless terminal 26-17 can proceed to the SIB reception procedure (Action 19-7).

[0151] Figure 20 It shows the result of Figure 17 The exemplary representative actions or steps performed by access nodes 22-17. Figure 17 The operation of access nodes 22-17 is similar to Figure 2 Node 22, and its action is similar to Figure 12 Those, but with such Figure 20The additional action shown. Specifically, if, as action 20-1a, access node 22-17 determines that it has not yet received a request for the on-demand SIB, then access node 22-17 can terminate. Figure 20 The process (Action 20-5). However, if access node 22-17 has already received a request for a requested SIB (e.g., SIB#k), then as Action 20-1b, access node 22-17 next determines whether the content of the requested requested SIB will change from the next modification cycle. If the content of the requested SIB will not change from the next modification cycle, access node 22-17 can proceed to the SIB transmission process, as shown in Action 20-3. As shown in Action 20-2, access node 22 can wait for the next SI window for SIB#k, and then (as shown in Action 20-3) broadcast SIB#k in that window. The access node can repeat the broadcast multiple times in subsequent SIB#k SI windows until the repetition ends (as shown in Action 20-4). The number of repetitions can be pre-configured, or equal to the aforementioned maximum counter value configured to the wireless terminal via system information. However, if the content of the requested on-demand SIB will change from the next modification cycle, then as action 20-6, access node 22-17 waits for the modification cycle boundary before performing the on-demand SIB transmission process, which includes actions 20-2, 20-3, and 20-4.

[0152] Therefore, as Figure 20 The actions of the access nodes 22-17 shown are based on Figure 12 However, this includes, for example, adding an action to wait for the next modification boundary when the requested SIB is to change at the next modification boundary. The update of the content of "SIB#k" at the modification boundary is... Figure 13 It is executed in the action "Update SIB" (Action 13-8).

[0153] It should be understood that Figure 10 and Figure 13 The process and actions are applicable to the second implementation plan.

[0154] Third Exemplary Implementation

[0155] Figure 21 An exemplary communication system is illustrated, wherein wireless terminals 26-21 and access nodes 22-21 have an agreement: whenever a playable SIB is updated, access node 22-21 may notify the wireless terminals in the current modification cycle and automatically transmit the updated SIB at one or more corresponding SIB windows from the next modification cycle, without requiring the wireless terminals to send a request. Therefore, terminal processor 40 includes an SIB processor 56-21 configured to automatically receive (without a terminal request) the updated playable SIB from the next modification cycle. Figure 21This automatic transmission of updated SIBs is shown as message 2-3-21. Access node 22-21 includes function 50-21, which, when permitted and / or agreed upon, automatically transmits the on-demand SIB without terminal request. Other elements and functions of wireless terminal 26-21 and access node 22-21 are similar to and can be understood from the foregoing description, for example... Figure 2 The description.

[0156] In one exemplary implementation and configuration, the protocol can be pre-configured in wireless terminals 26-21 and access nodes 22-21. In another configuration, information elements indicating whether automatic transmission of the on-demand SIB can occur from the next modification cycle are present in the signaling message from access node 22-21. In one implementation, such information elements can be in paging messages, such as... Figure 22 The paging message in action 22-2 can be used, or it can be used in the minimum SI (e.g., MIB, SIB1, etc.).

[0157] Figure 22 This illustrates, for example, the use of access nodes 22-21 and wireless terminals 26-21 in... Figure 21 The exemplary representative actions or steps performed in the communication network, and the exemplary messages transmitted therein. For the third exemplary embodiment and mode, the wireless terminal may be in any of the RRC states and (as shown in action 22-0) has already stored the content of SIB#k with valueTag = a. In this example, as shown in action 22-1, the wireless terminal may receive an SIB1 indicating that SIB#k will be delivered on demand, and the current latest version (value tag) of SIB#k is valueTag = a. Since the wireless terminal has already stored the same version of SIB#k, it does not need to take any action regarding the acquisition of SIB#k.

[0158] Finally, as shown in action 22-2, the wireless terminal 26-22 receives the paging message (which can correspond to a certain extent to...). Figure 7 The paging message (NM*) can instruct SIB#k to be updated from the next modification cycle. As mentioned above, the paging message of action 22-2 can include an indication (e.g., an information element) specifying that the requested SIB will be automatically broadcast upon update. Therefore, based on the fact that SIB#k will be updated from the next modification cycle and based on the NM* in the Paging Message, the Paging Message can instruct SIB#k to be updated from the next modification cycle. Figure 22 In the exemplary implementation and mode, the updated SIB will be automatically provided without requesting it from wireless terminals 22-21. Wireless terminals 26-21 can begin the SIB reception process after the next modification cycle boundary without having to request the update. The SIB reception process has the following characteristics: Figure 22The vertical arrow indicates the duration, with the tail of the arrow indicating the start of the SIB reception process and the head indicating the end of the SIB reception process. Actions 22-4a and 22-4b include actions of the SIB reception process performed as a result of the SIB request process. Action 22-4a indicates that SIB#k was not successfully received; action 22-4b indicates that SIB#k was successfully received. Wireless terminal 26-21 may monitor such an SIB window until one of the aforementioned termination conditions is met. For example, upon successfully receiving the SystemInformation message of action 22-4, wireless terminal 26-21 may terminate its SIB reception process because a search for SIB#k with valueTag=b has been received.

[0159] Figure 23 It shows the result of Figure 21 The exemplary actions or steps performed by the wireless terminals 26-21 are also used as exemplary operation flowcharts of the wireless terminals in the second embodiment. Figure 23 Similar to Figure 19 It has additional actions. Figure 23 If the SIB update notified by the paging message is on demand, and the eNB indicates that the automatic broadcast of the SIB will occur after the next modification cycle boundary, the wireless terminal can simply wait for that boundary and begin the SIB reception process at that time.

[0160] Figure 23 Action 23-2 shows that wireless terminal 26-23 receives a paging message. As action 23-3, the wireless terminal checks whether the paging message indicates an incoming call to that wireless terminal. If so, the wireless terminal can proceed to RRC connection establishment (action 23-8). Otherwise, the wireless terminal can further check whether the message indicates any SIB change to be scheduled. Two checks can be performed: as action 23-4a, wireless terminal 26-23 can check whether the paging message indicates an SIB update for a pay-as-you-go SIB; as action 23-4b, wireless terminal 26-23 can check whether the paging message indicates an SIB update for a broadcast SIB. If the paging message is not for a pay-as-you-go SIB, for example, if the decision of action 23-4a is negative, then the check of action 23-4b is performed. Furthermore, if the decision of action 23-4b is affirmative, for example, if the paging message is for a broadcast SIB, then as action 23-5a, the wireless terminal may wait until the next modification cycle boundary and then begin the SIB reception process (as action 23-6), as previously disclosed.

[0161] If, at action 23-4a, it is determined that the paging message indicating an SIB change is for a demand SIB, then as action 23-13, wireless terminal 26-23 checks whether there is an agreement or understanding regarding an automatic broadcast for the demand SIB at the time of update. If the check in action 23-13 is affirmative, i.e., if access node 22-23 can and does provide such an automatic broadcast and wireless terminal 26-23 can accept such an automatic broadcast, then wireless terminal 26-23 performs action 23-5b to wait for the next modification cycle boundary, and then begins the SIB reception process (action 23-6) after such a boundary. If the check in action 23-13 is negative, i.e., if access node 22-23 does not provide or cannot provide such an automatic broadcast, then as action 23-11, wireless terminal 26-23 may begin the SIB request process. If, at action 23-12, it is determined that the SIB request process of action 23-11 is successful, then wireless terminal 26-17 waits for the next modification cycle boundary (action 23-5a). After the next modification cycle boundary occurs, the wireless terminal 26-17 may begin the SIB reception process for the on-demand SIB (Action 23-6). If the SIB request process in Action 23-11 fails, or if it is determined (at Action 23-7) that the SIB reception process has failed, then cell reselection is performed (Action 23-9). If the SIB reception process succeeds, then... Figure 23 The process terminates (Action 23-10).

[0162] Figure 24 This is an exemplary operation flowchart of the access node in this implementation scheme notifying wireless terminals of upcoming SIB changes, which is based on Figure 13 This involves additional steps. At the start of each modification cycle, as action 24-1, access node 22-21 can check whether the change to the on-demand SIB has been notified in the previous modification cycle. If so, as action 24-2, access node 22-21 can initiate... Figure 12 The on-demand SIB transmission process is shown, and then proceeds to... Figure 13 The notification operation shown is as follows: Figure 24 Action 24-3 is shown. Otherwise, if the determination of action 24-1 is negative, then access node 22-21 can proceed directly to... Figure 13 The operation is shown. It should be understood that the on-demand SIB transmission process and notification operation can be performed in parallel.

[0163] It should be understood that Figure 10 The procedures and actions can be applied to the third implementation scheme.

[0164] Fourth exemplary implementation

[0165] Figure 25An exemplary communication system is illustrated, wherein when a request for a requested SIB is received and the requested SIB will change after the next modification cycle boundary, access nodes 22-25 are permitted (if possible (e.g., if an SI window is scheduled before the boundary)) to transmit the requested SIB with updated content and a new value tag before the next modification cycle boundary. Before the next modification cycle boundary, the wireless terminal in this embodiment and mode can initiate the SIB request process after receiving a paging message notifying of the change in the requested SIB, and can also initiate the SIB reception process after the SIB request process has successfully completed. This may cause the wireless terminal to monitor the SI window of the requested SIB even before the boundary, and end the SIB reception process upon successfully receiving the requested SIB with the new value tag. Therefore, Figure 25 The terminal processor 40 is shown to include request generators 72-25, which are configured to initiate both the SIB request process and the SIB reception process for on-demand SIBs when appropriate, without waiting for the next modification cycle boundary.

[0166] Figure 25 Access nodes 22-25 are further illustrated as including the SIB update advance feature 80. As described above, in the fourth exemplary embodiment and mode, access nodes 22-25 can transmit the requested SIB with updated content and a new value tag before the next modification cycle boundary. It should be understood that the updated content of the SIB does not take effect until the next modification cycle boundary, and cannot be utilized by the wireless terminal 26-25 until the next modification cycle boundary. However, to facilitate processing by the wireless terminal 26-25, access nodes 22-25 and their SIB update advance feature 80 can provide the updated SIB content to the requesting wireless terminal 26-25 before the actual change that will occur at the modification cycle boundary. Therefore, in this context, "updated" does not necessarily imply that the content is currently available, but rather that it will be available at the next modification cycle boundary.

[0167] Other components and functions of wireless terminals 26-25 and access node 22 are similar to and understood from the foregoing description, including, but not limited to, those included in the foregoing description. Figure 2 , Figure 14 , Figure 17 and Figure 21 The description.

[0168] Figure 26 This illustrates, for example, the use of access nodes 22-25 and wireless terminals 26-25 in... Figure 25 Exemplary representative actions or steps performed in a communication network, and exemplary messages transmitted therein. Specifically, Figure 26This is an exemplary case where wireless terminals 26-25 successfully terminate the SIB reception process before the next modification cycle boundary. In some cases, the SIB reception process may continue beyond this boundary until one of the aforementioned termination conditions is met.

[0169] For the fourth exemplary implementation and mode, the wireless terminal can be in any of the RRC states and (as shown in action 26-0) has already stored the content of SIB#k with valueTag = a. In this example, as shown in action 26-1, the wireless terminal can receive SIB1 indicating that SIB#k will be delivered on demand, and the current latest version (value tag) of SIB#k is valueTag = a. Since the wireless terminal has already stored the same version of SIB#k, it does not need to take any action regarding the acquisition of SIB#k.

[0170] Finally, as shown in action 26-2, wireless terminal 26-25 receives the paging message (corresponding to...). Figure 7 The paging message (NM*) indicates that SIB#k will be updated from the next modification period. Wireless terminals 26-25 do not wait for the next modification period boundary, but instead initiate an SIB request procedure (represented as action 26-3) before the next modification period boundary to request on-demand delivery of SIB#k. If the SIB request procedure succeeds without waiting for the next modification period boundary, the access node can transmit SIB#k in one or more SI windows associated with it as part of the SIB reception procedure. The SIB reception procedure has [a certain structure / function]. Figure 26 The vertical arrow indicates the duration, with the tail of the arrow indicating the start of the SIB reception process and the head indicating the end of the SIB reception process. Without waiting for the next modification cycle boundary, wireless terminals 26-25 can monitor such an SIB window until one of the aforementioned termination conditions is met. For example, upon successfully receiving the SystemInformation message of action 26-4a, wireless terminal 26-25 can terminate its SIB reception process because a search for SIB#k with valueTag=b has been received.

[0171] Figure 27 It shows the result of Figure 25 The exemplary actions or steps performed by the wireless terminals 26-25 are also used as an exemplary operation flowchart of the wireless terminal in the fourth embodiment. Figure 27 Similar to Figure 19 The difference is that both the SIB request process and the SIB receive process can be initiated before the next modification cycle boundary. Figure 19Action 27-2 shows that wireless terminal 26-25 receives a paging message. As action 27-3, the wireless terminal checks whether the paging message indicates an incoming call to that wireless terminal. If so, the wireless terminal can proceed to RRC connection establishment (action 27-8). Otherwise, the wireless terminal can further check whether the message indicates any SIB change to be scheduled. Two checks can be performed: as action 27-4a, wireless terminal 26-17 can check whether the paging message indicates an SIB update for a pay-as-you-go SIB; as action 27-4b, wireless terminal 26-25 can check whether the paging message indicates an SIB update for a broadcast SIB. If the paging message is not for a pay-as-you-go SIB, for example, if the decision of action 27-4a is negative, then the check of action 27-4b is performed. Furthermore, if the decision of action 27-4b is affirmative, for example, if the paging message is for a broadcast SIB, then as action 11-5a, the wireless terminal may wait until the next modification cycle boundary and then begin the SIB reception process (as action 27-6), as previously disclosed.

[0172] If it is determined at action 27-4a that the paging message indicating SIB change is for a pay-as-you-go SIB, then radio terminal 26-25 does not wait for the next modification cycle boundary but begins the SIB request procedure (action 27-11). Then, if the SIB request procedure of action 27-11 succeeds, radio terminal 26-17 can begin the SIB reception procedure for the pay-as-you-go SIB (action 27-6) without waiting for the modification cycle boundary. If the SIB request procedure of action 27-11 fails, or if it is determined (at action 27-7) that the SIB reception procedure fails, then cell reselection is performed (action 27). If the SIB reception procedure succeeds, then... Figure 19 The process terminates (Action 27-10).

[0173] Therefore, Figure 27 In contrast, the wireless terminal does not wait for the next modification cycle boundary before starting the SIB request process, and if the SIB request process is successful, it does not even need to wait for the modification cycle boundary used to perform the SIB receive process.

[0174] Figure 28 This is an exemplary operation flowchart of access nodes 22-25 in this implementation scheme notifying wireless terminals of upcoming SIB changes, which is similar to... Figure 13 However, the difference is that the on-demand SIB to be updated is updated without waiting for the current modification boundary to end. This allows access nodes to send such on-demand SIBs with updated content upon request, even before the next modification boundary. Figure 28Action 28-1 shows a check to determine whether any SIBS should be updated after the next modification cycle. When no SIB changes are scheduled, as shown in Action 28-2, the systemInfoModification message is cleared (no indication of change). Afterward, a paging message can be transmitted as shown in Action 28-3. When the access node decides to change some of the SIB types, as shown in Action 28-5, it can be based on... Figure 8A or Figure 8B The format described in the diagram sets information elements accordingly to indicate the SIB type to be changed. Access nodes 22-25 can continue sending paging messages with a set of information elements (as shown in action 28-6) until the end of the current modification cycle (as determined in action 28-8). As shown in action 28-7, access nodes 22-25 can update the on-demand SIB before the boundary of the next modification cycle. At the boundary of the next modification cycle, if the SIB change takes effect, the access node can update the periodically broadcast SIB for the next modification cycle, as shown in action 28-9.

[0175] It should be understood that Figure 10 and Figure 12 The process and actions can be applied to the fourth implementation plan.

[0176] Fifth exemplary implementation

[0177] Figure 29 An exemplary communication system is illustrated, which handles the situation where a paging message notifying of a change in the on-demand SIB is received after an SIB request process that requests the same on-demand SIB. Therefore, Figure 29 The terminal processor 40 is shown to include request generators 72-29, which are configured to, after the SIB reception process begins and before the next modification cycle boundary, suspend the SIB reception process for the on-demand SIB if a paging message indicating that the same on-demand SIB will be updated (further) at the next modification cycle boundary is received. Other elements and functions of the wireless terminals 26-29 and access nodes 22-29 are similar to and understood from the foregoing description, including, but not limited to, those included in the foregoing description. Figure 2 , Figure 14 , Figure 17 , Figure 21 and Figure 25 The description.

[0178] Figure 30 This illustrates, for example, the use of access nodes 22-29 and wireless terminals 26-29 in... Figure 29 Exemplary representative actions or steps performed in a communication network, and exemplary messages transmitted therein. Figure 30In the exemplary message flow shown, wireless terminal 26-29 initiates the SIB request procedure of action 30-2 to request SIB#k because (as shown in action 30-0) wireless terminal 26-29 previously received and stored SIB#k with valueTag=a, and then recently (as shown in action 30-1) received SIB1 indicating that valueTag=b is the currently valid version of SIB#k. Therefore, the SIB request procedure of action 30-2 aims to obtain SIB1 with valueTag=b. After the SIB request procedure of action 30-2 succeeds, it references... Figure 30 The first SIB reception process is depicted by the top vertical arrow. The first SIB reception process begins at the time corresponding to the tail of the top vertical arrow. However, during the first SIB reception process, for example, in the middle of the SIB reception process after the successful completion of the SIB request process, wireless terminal 26-29 has already received the paging message of action 30-3. The paging message of action 30-3 indicates that SIB#k will be updated at the next modification cycle boundary. As a result of receiving the paging message of action 30-3, wireless terminal 26-29 may abort the first SIB reception process at approximately the time indicated by the head of the top vertical arrow. Then, wireless terminal 26-29 waits until the next modification cycle boundary, and thereafter... Figure 30 The second vertical arrow at the tail of the second SIB reception process restarts. During the second (restarted) SIB reception process, wireless terminals 26-29 are shown as having successfully received the systemInformation message of actions 30-41, which includes the SIB with valueTag=c. Therefore, by aborting the first SIB reception process that only provides the SIB with valueTag=b, wireless terminals 26-29 have been able to switch to obtaining the most recently updated SIB with valueTag=c, thus saving both time and processing power.

[0179] Figure 31 An exemplary operation flowchart of the wireless terminal of this embodiment is shown when it receives a paging message, wherein if the paging message indicates that an upcoming update of one or more on-demand SIBs is being attempted to be obtained by the ongoing SIB receiving process, an additional action is added to the previous process to abort the ongoing SIB receiving process. Figure 23Action 31-2 shows that wireless terminal 26-29 receives a paging message. As action 31-3, the wireless terminal checks whether the paging message indicates an incoming call to that wireless terminal. If so, the wireless terminal can proceed to RRC connection establishment (action 31-8). Otherwise, the wireless terminal can further check whether the message indicates any SIB change to be scheduled. Two checks can be performed: as action 31-4a, wireless terminal 26-31 can check whether the paging message indicates an SIB update for a pay-as-you-go SIB; as action 31-4b, wireless terminal 26-31 can check whether the paging message indicates an SIB update for a broadcast SIB. If the paging message is not for a pay-as-you-go SIB, for example, if the decision of action 31-4a is negative, then the check of action 31-4b is performed. Furthermore, if the decision of action 31-4b is affirmative, for example, if the paging message is for a broadcast SIB, then as action 31-5a, the wireless terminal may wait until the next modification cycle boundary and then begin the SIB reception process (as action 31-6), as previously disclosed.

[0180] If, at action 31-4a, it is determined that the paging message indicating an SIB change is for a pay-as-you-go SIB, then as action 31-13, wireless terminal 26-31 checks whether there is an ongoing SIB reception for the (same) pay-as-you-go SIB. If the check in action 31-13 is affirmative, then as action 31-14, wireless terminal 26-31 aborts the ongoing SIB reception for the (same) pay-as-you-go SIB. Then, as action 31-5a, wireless terminal 26-31 waits for the next modification cycle boundary. After such a boundary, wireless terminal 26-29 performs the SIB reception procedure (action 31-6). If the check in action 31-13 is negative, i.e., if there is no ongoing SIB reception for the (same) pay-as-you-go SIB, then wireless terminal 26-31 continues the waiting in action 31-5b and then begins the SIB request procedure (action 31-11). If the SIB request procedure in action 31-11 fails, or if it is determined (at action 31-7) that the SIB reception procedure has failed, then cell reselection is performed (action 31-9). If the SIB reception procedure succeeds, then... Figure 31 The process terminates (actions 31-10).

[0181] It should be understood that Figure 11 , Figure 13 and Figure 20 The process and actions are applicable to the fifth implementation plan.

[0182] Sixth exemplary implementation scheme

[0183] The techniques disclosed in the sixth and seventh exemplary embodiments and modes relate to apparatus, methods, and processes for, for example, acquiring and / or updating SIBs in other SIs (Other SI SIBs), and particularly when a wireless terminal has received notification of a change in the minimum SI. For example, a change in the minimum SI may include a change in the type of system information (including a first type SIB or SIB1), such as a change in the format or content of a first system information block SIB1, or a change in the values ​​of parameters included in SIB1. Such parameters may be, for example, instructions on how to transmit specific system information (e.g., via periodic broadcasting or on-demand). Both the sixth and seventh exemplary embodiments and modes address situations where such notification of a change in the minimum SI is received after a wireless terminal has initiated an SIB request process to request (at least previously existing) an on-demand SIB. In the sixth and seventh exemplary embodiments and modes, a wireless terminal that has received notification of a change in the minimum SI is at least warned of the possibility that the change in the minimum SI may affect the already requested on-demand SIB. In other words, the wireless terminal is at least warned of the possibility that the searched on-demand SIB could (due to a change in the minimum SI) be converted from an on-demand SIB to a periodically broadcast SIB. If the previously searched on-demand SIB is indeed converted to a periodically broadcast SIB, the wireless terminal knows that the searched SIB will subsequently be broadcast, thus eliminating the need for a special request for the searched SIB. Similarly, a change in the minimum SI can affect the transmission timing of the requested on-demand SIB. In this case, the wireless terminal may need to adjust its receive schedule accordingly.

[0184] Figure 32 An exemplary communication system of a sixth exemplary embodiment and mode is shown, which handles the situation where, after an SIB request process requesting a SIB, a paging message notifying a change in the minimum SI (e.g., SIB1) is received, and wireless terminals 26-32 can suspend the ongoing SIB receiving process upon receiving the paging message. Therefore, Figure 32 The diagram illustrates access nodes 22-32 including a paging message generator 82 that generates paging messages, and a change in the minimum SI function 84. When a change in the minimum SI occurs, the minimum SI function 84 causes the paging message generator 82 to include a notification of the change in the paging message. An example paging message is shown in... Figure 32 The information is shown as messages 2-4. Figure 32The terminal processor 40 is also shown to include request generators 72-32, which are configured to abort the SIB reception process for the on-demand SIB upon receiving a paging message, if the paging message indicates a change in the minimum SIB after the SIB reception process has commenced. Other elements and functions of the wireless terminals 26-32 and access nodes 22-32 are similar to and understood from the foregoing description, including, for example, including but not limited to, those described above. Figure 2 , Figure 14 , Figure 17 , Figure 21 , Figure 25 and Figure 29 The description.

[0185] Figure 33A and Figure 33B This process handles situations where a paging message notifying of a change in the minimum SI (e.g., SIB1) is received after the SIB request process for requesting a SIB. Figure 33A and Figure 33B As shown, wireless terminal 26-32 can suspend the ongoing SIB reception process upon receiving a paging message, wait for the next modification boundary, and then reacquire the updated minimum SI. This updated minimum SI may include delivery and scheduling information of the SIB that the wireless terminal requested during the previous SIB request process. This information may be the same as or different from the information included in the previously received minimum SI. Therefore, wireless terminal 26-32 can use the information included in the updated minimum SI. For example, as... Figure 33A As shown, if the delivery method of the requested SIB (SIB#k) remains unchanged (on-demand), wireless terminals 26-32 can re-initiate the SIB request process using the scheduling information of the SI window included in the updated minimum SI, and then initiate the SIB reception process. On the other hand, if the updated minimum SI indicates that the requested SIB (SIB#k) will now be broadcast periodically, such as... Figure 33B As shown, wireless terminals 26-32 can directly proceed to initiate the SIB reception process.

[0186] Figure 33A This illustrates, for example, the use of access nodes 22-32 and wireless terminals 26-32 in... Figure 32 Exemplary representative actions or steps performed in a communication network, and exemplary messages transmitted therein. Figure 33AIn the exemplary message flow shown, wireless terminal 26-32 initiates the SIB request procedure of action 33A-2 to request SIB#k because (as shown in action 33A-0) wireless terminal 26-32 previously received and stored SIB#k with valueTag=a, and then recently (as shown in action 33A-1) received SIB1 indicating that valueTag=b is the currently valid version of SIB#k. Therefore, the SIB request procedure of action 33A-2 aims to obtain SIB1 with valueTag=b. However, when wireless terminal 26-32 attempts to perform the first SIB reception procedure after the SIB request procedure of action 33A-2, wireless terminal 26-32 receives paging message 33A-3, which indicates a change in the minimum SI, i.e., SIB1 will be updated. Therefore, upon receiving paging message 33A-3, wireless terminal 26-32 aborts the SIB reception procedure (in Figure 33A The head of the vertical arrow at the top of the screen approximates the time. At this point, wireless terminals 26-32 learn of the possibility that the searched SIB#k, which has become a demand SIB, can subsequently be converted into SIB1, for example, subsequently a periodically broadcast SIB. It turns out that in Figure 33A In the scenario shown, the searched SIB#k has not changed to a periodically broadcast SIB, as shown in SIB1 message 33A-4 broadcast after the next modification period boundary. Knowing that the searched SIB#k is still a demand SIB, as action 33A-2-2, the wireless terminal 26-32 begins a second SIB request procedure to request the SIB#k. If the second SIB request procedure of action 33A-2-2 is successful, a second SIB reception procedure begins. The second SIB reception procedure has... Figure 33A The lower vertical arrow indicates the duration, with the arrow tail indicating the start of the second SIB reception process and the arrow head indicating the end of the second SIB reception process. Actions 33A-5a and 33A-5b include actions of the SIB reception process performed as a result of the SIB request process. Action 33A-5a indicates that SIB#k was not successfully received; action 33A-5b indicates that SIB#k was successfully received. Wireless terminal 26-32 can monitor such SIB windows until one of the aforementioned termination conditions is met. For example, upon successfully receiving the SystemInformation message of action 33A-5b, wireless terminal 26-32 can terminate its SIB reception process because a search for SIB#k with valueTag=b has been received.

[0187] and Figure 33A Different scenarios, in Figure 33BIn this scenario, the searched SIB#k changes to a periodically broadcast SIB, as shown in SIB1 message 33B-4 broadcast after the next modification period boundary. Knowing that the searched SIB#k is now a periodically broadcast SIB, the wireless terminal 26-32 does not need to initiate a second SIB request procedure to request the SIB#k, but can immediately enter the second SIB reception procedure, in which the searched SIB#k will be broadcast. The second SIB reception procedure has [a certain characteristic]. Figure 33B The lower vertical arrow indicates the duration, with the arrow tail indicating the start of the second SIB reception process and the arrow head indicating the end of the second SIB reception process. Similar to... Figure 33A Actions 33B-5a and 33B-5b include actions in the second SIB reception process, where action 33B-5a indicates that SIB#k has not been successfully received, and action 33B-5b indicates that SIB#k has been successfully received. Wireless terminal 26-32 can monitor such SIB windows until one of the aforementioned termination conditions is met. For example, upon successfully receiving the SystemInformation message of action 33B-5b, wireless terminal 26-32 can terminate its SIB reception process because the searched SIB#k with valueTag=b has been received. Based on the expected broadcast of SIB#k now including SIB1, Figure 33B Therefore, this scenario does not require a second SIB request process. This occurs before the cycle boundary is modified. Figure 33B The action is similar to Figure 33A The action.

[0188] Figure 34 An exemplary operation flowchart of the wireless terminal of this embodiment is shown when it receives a paging message, wherein if the paging message indicates a change in the minimum SI, an additional action is added to the previous process to abort the ongoing SIB reception process. Figure 34 Action 34-2 illustrates wireless terminal 26-32 receiving a paging message. As action 34-3, the wireless terminal checks whether the paging message indicates an incoming call to that wireless terminal. If yes, wireless terminal 26-32 can proceed to RRC connection establishment (action 34-4). Otherwise, as action 34-5, wireless terminal 26-32 checks whether the minimum SI has changed, i.e., whether there has been any SIB update to the minimum SI. If not, as shown in symbol 34-6, wireless terminal 26-32 continues with the procedures described herein. Figure 16 , Figure 19 , Figure 23 , Figure 27 or Figure 31The logic associated with and follows any appropriate action described as "SIB update for on-demand SIB?". If the minimum SI has changed, as action 34-7, wireless terminal 26-32 checks whether there is an ongoing SIB reception for the on-demand SIB. In other words, wireless terminal 26-32 determines whether it is in the process of attempting to receive an on-demand SIB that wireless terminal 26-32 has requested. If there is an ongoing SIB reception process, as action 34-8, the ongoing SIB reception process is aborted. If there is no ongoing SIB reception process, or after aborting the ongoing SIB reception process at action 34-8, action 34-9 is executed. Action 34-9 involves wireless terminal 26-32 waiting for the next modification cycle boundary. Thereafter, as action 34-10, wireless terminal 26-32 obtains the minimum SI, as referenced. Figure 10 As I understand it.

[0189] therefore, Figure 34 This shows how to obtain paging messages (such as...) Figure 33B When paging message 33B-3 is received, additional condition checks are added to action 34-5 to check whether the change in minimum SI will occur at the boundary of the next modification cycle. If not, wireless terminal 26-34 can fall back to one of the previous implementations, specifically proceeding to, as in... Figure 16 , Figure 19 , Figure 23 , Figure 27 or Figure 31 The appropriate step shown in the diagram is "Request SIB update?". Otherwise, wireless terminals 26-32 can abort the ongoing SIB reception process (if any), wait for the next modification cycle boundary, and then attempt to obtain the updated minimum SI, such as... Figure 10 As shown.

[0190] Figure 35 This is an exemplary operation flowchart of access nodes 22-32 receiving a request for on-demand SIB delivery from a wireless terminal, and includes a step (action 35-2) to check whether to schedule a change in the minimum SI from the next modification period. If so, access nodes 22-32 can postpone the transmission of the requested SIB, even if an SI window for that SIB exists before the next modification boundary. After the next modification boundary, the access nodes re-evaluate the delivery method of the requested SIB; if on-demand delivery is maintained, the access nodes can wait for new requests from the wireless terminal; otherwise, the access nodes can initiate periodic broadcasts of the SIB, including repeating the transmission of the SIB in each specified SI window.

[0191] Specifically, as action 35-1, access node 22-32 determines that it has not yet received a request for the on-demand SIB, and access node 22-32 can terminate the process. Figure 35 The process (Action 35-8). As Action 35-2, Access Node 22-32 determines that there will be a change in the minimum SI (i.e., the minimum SI will change from the next modification cycle boundary). The network (e.g., Access Node 22-32) may decide when and how to change the configuration parameters in the minimum SI (SIB1) based on factors such as changes in the operating environment, network configuration, network traffic, network congestion, etc. If there is no change in the minimum SI, then as Action 35-3, Access Node 22-32 next determines whether the content of the requested on-demand SIB will change from the next modification cycle. If the content of the requested on-demand SIB does not change from the next modification cycle, Access Node 22-32 can proceed to the on-demand SIB transmission process, where Access Node 22-32 may (as Action 35-5) wait for the next SI window for SIB#k, and then (as Action 35-6) transmit SIB#k in that window. Access Node 22-32 may repeat the transmission multiple times in subsequent SIB#k SI windows until the repetition ends (as shown in Action 35-7). The number of repetitions can be pre-configured or equal to the aforementioned maximum counter value configured to the wireless terminal via system information. However, if the content of the requested on-demand SIB will change from the next modification cycle, as action 35-4, access node 22-32 waits for the modification cycle boundary before executing the on-demand SIB transmission process including actions 35-5, 35-6, and 35-7. But if a change in the minimum SI is determined at action 35-2, access node 22-32 executes actions 35-9 and 35-10. Action 35-9 involves access node 22-32 waiting for the next modification cycle boundary. Action 35-10 involves access node 22-32 making a determination regarding whether the requested SIB is on-demand. If the requested SIB is not on-demand, the requested SIB is periodically broadcast, as roughly as shown in action 35-11. If the requested SIB is on-demand, the loop returns to action 35-1.

[0192] It should be understood that Figure 10 and Figure 13 The process and actions can be applied to the sixth implementation plan.

[0193] Seventh Exemplary Implementation

[0194] Figure 36An exemplary communication system, illustrating a seventh exemplary embodiment and mode, is shown that handles situations where, after an SIB request process requesting a requested SIB, a paging message notifying a change in the minimum SI (e.g., SIB1) is received, and wireless terminals 26-36 can abort the ongoing SIB reception process at a modification cycle boundary. Therefore, Figure 36 The diagram illustrates access nodes 22-36 including a paging message generator 82 that generates paging messages, and a change in the minimum SI function 84. When a change in the minimum SI occurs, the minimum SI function 84 causes the paging message generator 82 to include a notification of the change in the paging message. An example paging message is shown in... Figure 36 The information is shown as messages 2-4. Figure 36 The terminal processor 40 is also shown to include request generators 72-36, which are configured to abort the SIB reception process for the on-demand SIB at the next modification cycle boundary when appropriate, if a paging message indicates a change in the minimum SI after the start of the SIB reception process. Other elements and functions of the wireless terminals 26-36 and access nodes 22-36 are similar to and understood from the foregoing description, including, but not limited to, those included in the foregoing description. Figure 2 , Figure 14 , Figure 17 , Figure 21 , Figure 25 , Figure 29 and Figure 32 The description.

[0195] Therefore, the seventh implementation scheme is a variation of the sixth implementation scheme and mode, in which wireless terminals 26-36 continue the SIB reception process even after receiving a paging message indicating that the minimum SI has changed from the next modification cycle. If Figure 36 The implementation schemes and modes of wireless terminals 26-36 during the current modification cycle (e.g., occurring when...) Figure 37A If the requested SIB is not successfully received within the modification period preceding the modification boundary depicted in the diagram, the SIB receiving process may be aborted at the next modification period boundary. At the next modification period boundary, Figure 36 The wireless terminals 26-36 may then attempt to obtain an updated minimum SI, which may include delivery and scheduling information of the SIB that the wireless terminal has requested during a previous SIB request process. As described in the sixth embodiment, the wireless terminals 26-36 may use the information included in the updated minimum SI.

[0196] Figure 37A The updated minimum SI indicates that the previously requested SIB (e.g., SIB#k) is on demand, which can cause the wireless terminal to restart the SIB request process and then begin the SIB reception process. Figure 37AThis illustrates, for example, the use of access nodes 22-36 and wireless terminals 26-36 in... Figure 36 Exemplary representative actions or steps performed in a communication network, and exemplary messages transmitted therein. Figure 37A In the exemplary message flow shown, wireless terminal 26-36 initiates the SIB request procedure of action 37A-2 to request SIB#k because (as shown in action 37A-0) wireless terminal 26-36 previously received and stored SIB#k with valueTag=a, and then recently (as shown in action 37A-1) received SIB1 indicating that valueTag=b is the currently valid version of SIB#k. Therefore, the SIB request procedure of action 37A-2 aims to obtain SIB1 with valueTag=b. However, when wireless terminal 26-36 attempts to perform the first SIB reception procedure after the SIB request procedure of action 37A-2, wireless terminal 26-36 receives paging message 37A-3, which indicates a change in the minimum SI, i.e., SIB1 will be updated. However, unlike the sixth exemplary embodiment and mode, wireless terminal 26-36 does not immediately suspend the SIB reception procedure upon receiving paging message 37A-3. Instead, as... Figure 37A Other actions prior to the occurrence of the modification cycle boundary are illustrated, for example, during the current modification cycle, wireless terminals 26-36 continue to attempt to... Figure 37A The vertical arrow at the top indicates the SIB reception process, during which the searched SIB#k is acquired until the next modification cycle. Coincidentally, in... Figure 37A During the SIB reception process shown, wireless terminals 26-36 failed to successfully receive the searched SIB#k, as indicated by the failed SystemInformation message 37A-4. The SIB reception process is then aborted only at the boundary of the next modification cycle, as described above, if... Figure 36 If the wireless terminals 26-36 of the implementation scheme and mode fail to successfully receive the requested SIB, they can abort the SIB reception process at the next modification cycle boundary. Then, after the modification cycle boundary occurs, the wireless terminals 26-36 receive the SIB1 message 37A-5 broadcast after the next modification cycle boundary. Figure 37A In this context, SIB1 message 37A-5 indicates that the searched SIB#k is still on-demand, meaning that the searched SIB#k has not changed to a periodic broadcast SIB. Knowing that the searched SIB#k is still an on-demand SIB, as action 37A-6, the wireless terminal 26-36 begins a second SIB request procedure to request that SIB#k. If the second SIB request procedure of action 37A-6 is successful, a second SIB reception procedure begins. The second SIB reception procedure has... Figure 37AThe lower vertical arrow indicates the duration, with the arrow tail indicating the start of the second SIB reception process and the arrow head indicating the end of the second SIB reception process. Actions 37A-7a and 37A-7b include actions of the SIB reception process performed as a result of the SIB request process. Action 37A-7a indicates that SIB#k was not successfully received; action 37A-7b indicates that SIB#k was successfully received. Wireless terminals 26-36 may monitor such SIB windows until one of the aforementioned termination conditions is met. For example, upon successfully receiving the SystemInformation message of action 37A-7b, wireless terminal 26-36 may terminate its SIB reception process because a search for SIB#k with valueTag=b has been received.

[0197] and Figure 37A Different scenarios, in Figure 37B In this scenario, the searched SIB#k changes to the minimum SI, as shown in SIB1 message 37B-5 broadcast after the next modification cycle boundary. Knowing that the searched SIB#k is now a periodically broadcast SIB, wireless terminals 26-36 do not need to initiate a second SIB request procedure to request the SIB#k, but can immediately enter the second SIB reception procedure, in which the searched SIB#k will be broadcast. The second SIB reception procedure has [a certain structure / function]. Figure 37B The lower vertical arrow indicates the duration, with the arrow tail indicating the start of the second SIB reception process and the arrow head indicating the end of the second SIB reception process. Similar to... Figure 37A Actions 37B-7a and 37B-7b include actions in the second SIB reception process, where action 37B-7a indicates that SIB#k has not been successfully received, and action 37B-7b indicates that SIB#k has been successfully received. Wireless terminals 26-36 can monitor such SIB windows until one of the aforementioned termination conditions is met. For example, upon successfully receiving the SystemInformation message of action 37B-7b, wireless terminal 26-36 can terminate its SIB reception process because a searched SIB#k with valueTag=b has been received. Therefore, based on the expected broadcast of SIB#k now including SIB1, Figure 37B The scenario does not require a second SIB request process. This occurs before the cycle boundary is modified. Figure 37B The action is similar to Figure 37B The action.

[0198] therefore, Figure 37B This refers to the case where the requested SIB delivery method changes from on-demand to periodic broadcast at the modified period boundary. In this case, wireless terminals 26-36 can proceed directly to the SIB reception process.

[0199] If wireless terminals 26-36 successfully receive the requested SIB just before the next modification cycle boundary, then wireless terminals 26-36 can terminate the SIB reception process, such as... Figure 37C As shown. Specifically, in Figure 37C In this scenario, after executing the SIB request process of action 37C-2, wireless terminals 26-36 perform the following... Figure 37C The top arrow indicates the SIB reception process. During the SIB reception process, wireless terminals 26-36 receive a paging message from action 37C-3, which indicates that SIB1 will be updated. Figure 37A and Figure 37B In this scenario, wireless terminals 26-36 do not suspend the SIB receiving process, but continue the SIB receiving process to attempt to receive the searched SIB#k in the current modification cycle. Figure 37C Scene and Figure 37A and Figure 37C The difference in the scenarios is that, Figure 37C During SIB reception, wireless terminals 26-36 successfully receive the searched SIB#k within the current modification period (e.g., before the modification period boundary), as shown in action 37C-4. After the modification period boundary, wireless terminals 26-36 can continue to receive other SIB1 messages, as shown in message 37C-5. Figure 37C In this scenario, wireless terminals 26-36 can eventually obtain the updated minimum SI and make decisions about further actions (if any) based on the content of the updated minimum SI.

[0200] Figure 38 An exemplary operation flowchart of the wireless terminal of this embodiment is shown when it receives a paging message, wherein if the paging message indicates a change in the minimum SI, an additional action is added to the previous process to abort the ongoing SIB reception process. Figure 38 Action 38-2 shows that wireless terminal 26-36 receives a paging message. As action 38-3, the wireless terminal checks whether the paging message indicates an incoming call to the wireless terminal. If yes, wireless terminal 26-36 can proceed to RRC connection establishment (action 38-4). Otherwise, as action 38-5, wireless terminal 26-36 checks whether the minimum SI has changed, i.e., whether there has been any SIB update to the minimum SI. If not, as shown in symbol 38-6, wireless terminal 26-36 continues to perform the actions described herein. Figure 16 , Figure 19 , Figure 23 , Figure 27 or Figure 31The logic associated with any appropriate action described as "SIB update for on-demand SIB?" is followed. If the minimum SI has changed, then as action 38-7, wireless terminal 26-36 checks whether there is an ongoing SIB reception for the on-demand SIB. In other words, wireless terminal 26-36 determines whether it is in the process of attempting to receive an on-demand SIB that wireless terminal 26-36 has requested.

[0201] If an ongoing SIB reception process exists, wireless terminal 26-36 will not immediately suspend the ongoing SIB reception process. Instead, as action 38-8A, wireless terminal 26-36 adds a termination condition: the SIB reception process will end at the next modification cycle boundary. As action 38-8B, it then checks whether the searched SIB#k has been acquired before the next modification cycle boundary. If the searched SIB#k has been acquired before the next modification cycle boundary, wireless terminal 26-36 waits for the next modification cycle boundary (action 38-9) and then performs minimum SI acquisition (action 38-10). If the searched SIB#k has not been acquired before the next modification cycle boundary, wireless terminal 26-36 performs minimum SI acquisition (action 38-10). If no ongoing SIB reception process exists, as action 38-9, wireless terminal 26-36 performs action 38-9 and then performs minimum SI acquisition (action 38-10).

[0202] therefore, Figure 38 The diagram illustrates that, upon receiving a paging message, after checking for an incoming call to the wireless terminal, an additional step (action 38-5) is added to check whether the paging message indicates an upcoming change in the minimum SI from the next modification cycle. If not, similar to the sixth embodiment, the process can proceed to... Figure 16 , Figure 19 , Figure 23 , Figure 27 or Figure 31 The appropriate step shown in the diagram is “SIB update for on-demand SIB?”. Otherwise, wireless terminals 26-36 further check whether there is any ongoing SIB reception process for the on-demand SIB (Action 38-7). If not, the wireless terminal can simply wait for the next modification cycle (Action 38-9) and then begin acquiring the minimum SIB at that time (Action 38-10), as... Figure 10As shown. Otherwise, wireless terminals 26-36 can continue the ongoing SIB reception process, where a new termination condition (action 38-8A) is now added to the aforementioned termination condition: the SIB reception process ends at the next modification cycle boundary. Therefore, if wireless terminals 26-36 fail to receive the requested SIB before the modification cycle boundary, it may not have successfully terminated the ongoing SIB reception process. After the (successful or unsuccessful) SIB reception process terminates, if the SIB reception was before the boundary, the wireless terminal can wait for the next modification cycle boundary (action 38-9) and proceed to... Figure 9 The minimum SI acquisition is shown, or if the SIB reception is already beyond the boundary, the wireless terminal proceeds directly to the minimum SI acquisition (Action 38-10).

[0203] Figure 39 This is an exemplary operation flowchart of access nodes 22-36 receiving on-demand SIB delivery requests from wireless terminals, which is based on Figure 12 The process involves an additional action (action 39-3) after waiting for the next SI window for the requested SIB (e.g., SIB#k) to check if it is now in a new modification cycle. If so, access nodes 22-36 can further check if the minimum SI has changed in that modification cycle (action 39-7). If not, the process can resume the ongoing (repeating) transmission cycle of the requested SIB. Otherwise, the transmission cycle terminates, and the access node can further check if the requested SIB has remained on demand after the minimum SI changed (action 39-8). If this is the case, the access node can wait for the next request (action 39-1). On the other hand, if the delivery method of the requested SIB has changed to periodic broadcast, the access node can initiate a periodic broadcast process, such as relative to, for example... Figure 35 What I know.

[0204] Specifically, as action 39-1, if access node 22-36 determines that it has not yet received a request for the on-demand SIB, then access node 22-36 can terminate the process. Figure 39The process (Action 39-8) is as follows: If a request for a requested SIB has been received, as Action 39-2, the wireless terminal 26-36 waits for the next SI window for the requested SIB (e.g., SIB#k), and then, as Action 39-3, checks to see if it is currently in a new modification cycle. If it is not a new modification cycle, as Action 39-7, the access node 22-36 can proceed to the requested SIB transmission process, whereby the access node 22-36 can (as Action 39-4) transmit SIB#k in that window. The access node 22-36 can repeat the transmission multiple times in subsequent SIB#k SI windows until the repetition ends (as shown in Action 39-5). The number of repetitions can be pre-configured or equal to the aforementioned maximum counter value configured for the wireless terminal via system information. If it is a new modification cycle, as Action 39-7, the access node 22-36 determines whether there will be a change in the minimum SI (i.e., the minimum SI will change from the boundary of the next modification cycle). As described above, the network (e.g., access nodes 22-32) can decide when and how to change the configuration parameters in the minimum SI (SIB1) based on factors such as changes in the operating environment, network configuration, network traffic, and network congestion. If there is no change to the minimum SI, then as action 39-3, access nodes 22-36 can proceed to the on-demand SIB transmission process, whereby access nodes 22-36 can (as action 39-4) transmit SIB#k in this window, as described above. If there is a change to the minimum SI, then as action 39-8, access nodes 22-36 determine whether the requested SIB is on-demand. If the requested SIB is not on-demand, then the requested SIB is broadcast periodically, as roughly as shown in action 39-9. If the requested SIB is on-demand, then the loop returns to action 39-1.

[0205] It should be understood that Figure 10 and Figure 13 The process and actions can be applied to the seventh implementation plan.

[0206] In an exemplary embodiment, certain elements and functions of node 22 and wireless terminal 26 are implemented by electromechanical systems, computers, and / or circuits. For example, Figure 32 The computer circuitry may include the node processor 30 and terminal processor 40 of the exemplary embodiments described and / or included herein. Figure 32 An example of such electromechanical or circuitry, whether a node or a terminal, is shown, comprising one or more processor circuits 190, a program instruction memory 192; other memories 194 (e.g., RAM, cache, etc.); an input / output interface 196; a peripheral device interface 198; support circuitry 199; and a bus 200 for communication between the aforementioned units.

[0207] The program instruction memory 192 may include encoded instructions that, when executed by the processor, perform actions including, but not limited to, those described herein. Therefore, it should be understood that each of the node processor 30 and the terminal processor 40 includes, for example, memory storing non-transitory instructions for execution.

[0208] The memory 194 or computer-readable medium may be one or more of readily available memory such as random access memory (RAM), read-only memory (ROM), floppy disk, hard disk, flash memory, or any other form of digital memory (local or remote), and preferably has non-volatile characteristics. Support circuitry 199 is coupled to the processor 190 to support the processor in a conventional manner. This circuitry includes caches, power supplies, clock circuits, input / output circuits, and subsystems, etc.

[0209] Furthermore, it should be understood that when referring to a processor or processor circuit in connection with any of the foregoing exemplary embodiments and patterns, it should be understood that the device hosting the processor, whether a wireless terminal or an access node, may include at least one processor and at least one memory including computer program code configured to work with the at least one processor to enable the host device to perform the foregoing functions.

[0210] In the first embodiment, a first exemplary implementation and mode of the wireless terminal 26-14 includes at least one processor and at least one memory including computer program code, the memory and the computer program code being configured to work with the at least one processor to cause the wireless terminal to wait for a modified cycle boundary to initiate an SIB request process for the on-demand SIB.

[0211] In the second embodiment, the second exemplary implementation and mode of the wireless terminal 26-17 includes at least one processor and at least one memory including computer program code, the memory and computer program code being configured to work with the at least one processor to enable the wireless terminal to initiate an SIB request process without waiting for the next modification cycle boundary, but after the SIB request process is successfully completed, to wait for the next modification cycle boundary to begin the SIB reception process.

[0212] For the third embodiment, a third exemplary implementation and mode of the wireless terminal 26-21 includes at least one processor and at least one memory including computer program code, the memory and the computer program code being configured to work with the at least one processor to enable the wireless terminal to: whenever the on-demand SIB is updated, receive an automatic transmission of the updated SIB from the access node in one or more corresponding SI windows from the next modification cycle, without requiring the wireless terminal to send a request.

[0213] For the fourth embodiment, the fourth exemplary implementation and mode of the wireless terminals 26-25 includes at least one processor and at least one memory including computer program code, the memory and computer program code being configured to work with the at least one processor to enable the wireless terminal to initiate both an SIB request process and an SIB reception process for on-demand SIBs when appropriate, without waiting for the next modification cycle boundary.

[0214] For the fifth embodiment, the fifth exemplary implementation and mode of the wireless terminals 26-29 includes at least one processor and at least one memory including computer program code, the memory and the computer program code being configured to work with the at least one processor to cause the wireless terminal to: suspend the ongoing SIB request process when it receives a paging message notifying of a change in the on-demand SIB after initiating an ongoing SIB request process that requests the same on-demand SIB.

[0215] For the sixth embodiment, a sixth exemplary implementation and mode of the wireless terminal includes at least one processor and at least one memory including computer program code configured to work with the at least one processor to cause the wireless terminal to suspend an ongoing SIB reception process upon receiving a paging message indicating a change in the minimum SI.

[0216] For the seventh embodiment, a seventh exemplary implementation and mode of the wireless terminal includes at least one processor and at least one memory including computer program code, the memory and computer program code being configured to work with the at least one processor to enable the wireless terminal to continue an ongoing SIB reception process at least until the next modification cycle boundary upon receiving a paging message indicating a change in the minimum SI.

[0217] Therefore, the techniques disclosed herein address problems in the telecommunications field, including those in telecommunications nodes (such as wireless terminals and access nodes) and in the computers / processors and hardware that include such nodes. System information is crucial for the operation of telecommunications nodes, enabling each node to acquire the necessary network information to coordinate and communicate with other nodes and to perform its required functions. System information is quite extensive and complex, and can change / update, for example, due to network and operating conditions. Effectively acquiring and using system information is challenging, especially considering the many other telecommunications functions that can be performed simultaneously based on system information. The techniques disclosed herein provide communication nodes with computerized configurations and other configurations to acquire system information earlier and more efficiently, thereby avoiding wasted time and processing resources.

[0218] Therefore, the technology of this application includes, but is not limited to, the following exemplary embodiments, exemplary features, and exemplary advantages:

[0219] Exemplary Implementation Scheme 1: A wireless terminal that communicates with an access node of a radio access network (RAN) via a radio interface, the wireless terminal comprising:

[0220] A receiver circuit configured to receive first-type system information from an access node, the first-type system information including the availability of second-type system information blocks (SIBs) and an indication of the delivery mode for each available second-type SIB, the delivery mode being either periodically broadcast or on demand.

[0221] The processor circuit is configured as follows:

[0222] Receive a notification message indicating the identity of the second type SIB to be played, the content of which will be updated at the next boundary of the repetition time period configured by the access node;

[0223] Initiate a receiving process to attempt to receive some of the updated on-demand Class 2 SIBs.

[0224] Exemplary Implementation 2: The wireless terminal according to Exemplary Implementation 1, wherein the receiving process ends when the updated on-demand Type II SIB is successfully received.

[0225] Exemplary Implementation 3: The wireless terminal according to Exemplary Implementation 1, wherein the receiving process ends after the maximum number of receiving attempts for the updated on-demand second type SIB.

[0226] Exemplary Implementation 4: The wireless terminal according to Exemplary Implementation 1, wherein the receiving process ends after the timer expires.

[0227] Exemplary Implementation 5: The wireless terminal according to Exemplary Implementation 1, wherein the wireless terminal is configured to transmit a request message to the access node to request an update of the broadcast of the on-demand second type SIB.

[0228] Exemplary Implementation 6: The wireless terminal according to Exemplary Implementation 5, wherein the wireless terminal is further configured to transmit a request message after the next boundary.

[0229] Exemplary Implementation 7: The wireless terminal according to Exemplary Implementation 5, wherein the wireless terminal is further configured to initiate a reception process after the next boundary.

[0230] Exemplary Implementation 8: The wireless terminal according to Exemplary Implementation 1, wherein the wireless terminal further receives configuration information from the access node, the configuration information indicating that the updated on-demand Type II SIB will be broadcast by the access node after the next boundary in the absence of a request message.

[0231] Exemplary Implementation 9: The wireless terminal according to Exemplary Implementation 8, wherein the configuration information is applicable to all SIBs to be updated after the next boundary.

[0232] Exemplary Implementation 10: A wireless terminal according to Exemplary Implementation 8, wherein configuration information selectively indicates the type of SIB to be broadcast in the absence of a request message.

[0233] Exemplary Implementation 11: The wireless terminal according to Exemplary Implementation 8, wherein configuration information is included in a notification message.

[0234] Exemplary Implementation 12: The wireless terminal according to Exemplary Implementation 8, wherein configuration information is included in a first type of system information.

[0235] Exemplary Implementation 13: According to the wireless terminal of Exemplary Implementation 1, when a notification message is received, if the notification message indicates that the on-demand second type SIB needs to be updated in the next boundary, the wireless terminal suspends the process of attempting to acquire the on-demand second type SIB.

[0236] Exemplary Implementation 14: The wireless terminal according to Exemplary Implementation 13, wherein the wireless terminal is further configured to restart the reception process of on-demand Type II SIBs after the next boundary.

[0237] Exemplary Implementation 15: A method in a wireless terminal communicating with an access node of a radio access network (RAN) via a radio interface, the method comprising:

[0238] Receive first type of system information from the access node, which includes the availability of second type of system information blocks (SIBs) and an indication of the delivery mode for each available second type of SIB, which is either periodically broadcast or on demand;

[0239] Receive a notification message indicating the identity of the second type SIB to be played, the content of which will be updated at the next boundary of the repetition time period configured by the access node;

[0240] Initiate a receiving process to attempt to receive some of the updated on-demand Class 2 SIBs.

[0241] Exemplary Implementation 16: The method according to Exemplary Implementation 15, wherein the receiving process ends when the updated on-demand second type SIB is successfully received.

[0242] Exemplary Implementation 17: The method according to Exemplary Implementation 15, wherein the receiving process ends after the maximum number of receiving attempts for the updated on-demand second type SIB.

[0243] Exemplary Implementation 18: The method according to Exemplary Implementation 15, wherein the receiving process ends after the timer expires.

[0244] Exemplary Implementation 19: The method according to Exemplary Implementation 15 includes transmitting a request message to an access node to request an update of the broadcast of the on-demand second type SIB.

[0245] Exemplary Implementation 20: The method according to Exemplary Implementation 19, further comprising transmitting a request message after the next boundary.

[0246] Exemplary Implementation 21: The method according to Exemplary Implementation 19 further includes initiating a receiving process after the next boundary.

[0247] Exemplary Implementation 22: The method according to Exemplary Implementation 15 further includes receiving configuration information from an access node, the configuration information indicating that the updated on-demand second type SIB will be broadcast by the access node after the next boundary in the absence of a request message.

[0248] Exemplary Implementation 23: The method according to Exemplary Implementation 22, wherein the configuration information applies to all SIBs to be updated after the next boundary.

[0249] Exemplary Implementation 24: The method according to Exemplary Implementation 22, wherein the configuration information selectively indicates the type of SIB to be broadcast in the absence of a request message.

[0250] Exemplary Implementation 25: The method according to Exemplary Implementation 22, wherein configuration information is included in the notification message.

[0251] Exemplary Implementation 26: The method according to Exemplary Implementation 22, wherein the configuration information is included in the first type of system information.

[0252] Exemplary Implementation 26: The method according to Exemplary Implementation 15 includes, upon receiving a notification message, suspending the process of attempting to acquire the on-demand second-type SIB if the notification message indicates that the on-demand second-type SIB is to be updated in the next boundary.

[0253] Exemplary Implementation 27: The method according to Exemplary Implementation 26, wherein the wireless terminal is further configured to restart the reception process of on-demand Type II SIBs after the next boundary.

[0254] Exemplary Implementation 28: An access node of a radio access network, comprising:

[0255] The transmitter circuit is configured to transmit first-type system information and second-type system information via a radio interface. The first-type system information includes the availability of second-type system information blocks (SIBs) and an indication of the delivery mode for each available second-type SIB, which is either periodic broadcast or on-demand.

[0256] The processor circuit is configured as follows:

[0257] Transmit a notification message indicating the identity of the second type SIB to be played, the content of which will be updated at the next boundary of the repetition period configured by the access node;

[0258] Broadcast updated on-demand Category 2 SIBs at one or more broadcast times.

[0259] Exemplary Implementation 29: The access node according to Exemplary Implementation 28, wherein the access node is configured to trigger a broadcast update of a second type SIB when a request message is received from a wireless terminal.

[0260] Exemplary Implementation 30: Access Node According to Exemplary Implementation 29 Error! Reference source not found. The access node is configured to begin broadcasting updated on-demand Type II SIBs after the next boundary.

[0261] Exemplary Implementation 31: The access node according to Exemplary Implementation 29, wherein the access node further sends configuration information to the wireless terminal, the configuration information indicating that the updated on-demand Type II SIB will be broadcast after the next boundary in the absence of a request message.

[0262] Exemplary Implementation 32: The access node according to Exemplary Implementation 31, wherein the configuration information is applicable to all SIBs to be updated after the next boundary.

[0263] Exemplary Implementation 33: The access node according to Exemplary Implementation 31, wherein the configuration information selectively indicates the type of SIB to be broadcast in the absence of a request message.

[0264] Exemplary Implementation 34: The access node according to Exemplary Implementation 33, wherein configuration information is included in the notification message.

[0265] Exemplary Implementation 35: The access node according to Exemplary Implementation 33, wherein configuration information is included in the first type of system information.

[0266] Exemplary Implementation 36: A method in an access node of a radio access network, comprising:

[0267] First-class system information and second-class system information are transmitted via a radio interface. The first-class system information includes the availability of second-class system information blocks (SIBs) and an indication of the delivery mode for each available second-class SIB, which is either periodic broadcast or on demand.

[0268] Transmit a notification message indicating the identity of the second type SIB to be played, the content of which will be updated at the next boundary of the repetition period configured by the access node;

[0269] Broadcast updated on-demand Category 2 SIBs at one or more broadcast times.

[0270] Exemplary Implementation 37: The method according to Exemplary Implementation 36 Error! Reference source not found. This includes on-demand Type II SIBs that broadcast updates when a request message is received from a wireless terminal.

[0271] Exemplary Implementation 38: The method according to Exemplary Implementation 37 Error! Reference source not found. This includes on-demand Category 2 SIBs that begin broadcasting updates after the next boundary.

[0272] Exemplary Implementation 39: The method according to Exemplary Implementation 36 further includes sending configuration information to a wireless terminal, the configuration information indicating that the updated on-demand Type II SIB will be broadcast after the next boundary in the absence of a request message.

[0273] Exemplary Implementation 40: The method according to Exemplary Implementation 39, wherein the configuration information applies to all SIBs to be updated after the next boundary.

[0274] Exemplary Implementation 41: The method according to Exemplary Implementation 39, wherein the configuration information selectively indicates the type of SIB to be broadcast in the absence of a request message.

[0275] Exemplary Implementation 42: The method according to Exemplary Implementation 39, wherein configuration information is included in the notification message.

[0276] Exemplary Implementation 43: The access node according to Exemplary Implementation 39, wherein the configuration information is included in the first type of system information.

[0277] Exemplary Implementation 44: A wireless terminal that communicates with an access node of a radio access network (RAN) via a radio interface, the wireless terminal comprising:

[0278] A receiver circuit configured to receive first-type system information from an access node, the first-type system information including the availability of second-type system information blocks (SIBs) and an indication of the delivery mode for each available second-type SIB, the delivery mode being either periodically broadcast or on demand.

[0279] The processor circuit is configured as follows:

[0280] Initiate a reception process that includes one or more attempts to receive on-demand Type 2 SIBs.

[0281] While running the ongoing reception process, a notification message including at least one identity of a first type SIB is received, the content of which will be updated at the next boundary of the repetition period configured by the access node.

[0282] The receiving process is aborted.

[0283] Exemplary Implementation 45: The wireless terminal according to Exemplary Implementation 44, wherein prior to the receiving process, the wireless terminal is configured to perform a request process, the request process including sending a request message to request on-demand delivery of at least one second type SIB.

[0284] Exemplary Implementation 46: The wireless terminal according to Exemplary Implementation 44, wherein the wireless terminal is configured to suspend an ongoing receiving process upon receiving a notification message.

[0285] Exemplary Implementation 47: The wireless terminal according to Exemplary Implementation 44, wherein the wireless terminal is configured to suspend the ongoing reception process at the next boundary.

[0286] Exemplary Implementation 48: A method in a wireless terminal communicating with an access node of a radio access network (RAN) via a radio interface, the method comprising:

[0287] Receive first type of system information from the access node, which includes the availability of second type of system information blocks (SIBs) and an indication of the delivery mode for each available second type of SIB, which is either periodically broadcast or on demand;

[0288] Initiate a reception process that includes one or more attempts to receive on-demand Type 2 SIBs;

[0289] While running the ongoing reception process, a notification message including at least one identity of a first type SIB is received, the content of which will be updated at the next boundary of the repetition period configured by the access node.

[0290] The receiving process is aborted.

[0291] Exemplary Implementation 49: The method according to Exemplary Implementation 48 further includes performing a request process prior to the receiving process, the request process including sending a request message to request on-demand delivery of at least one second type SIB, and receiving an acknowledgment from the access node.

[0292] Exemplary Implementation 50: The method according to Exemplary Implementation 48 further includes suspending the ongoing receiving process upon receiving a notification message.

[0293] Exemplary Implementation 51: The method according to Exemplary Implementation 48 further includes suspending the ongoing receiving process at the next boundary.

[0294] Exemplary Implementation 52: An access node of a radio access network, comprising:

[0295] The transmitter circuit is configured to transmit first-type system information and second-type system information via a radio interface. The first-type system information includes the availability of second-type system information blocks (SIBs) and an indication of the delivery mode for each available second-type SIB, which is either periodic broadcast or on-demand.

[0296] The processor circuit is configured as follows:

[0297] The transmission includes a notification message containing at least one identifier of a Type I SIB, the content of which will be updated at the next boundary of a recurring time period configured by the access node.

[0298] Receive a message from a wireless terminal requesting on-demand delivery of at least one Type 2 SIB;

[0299] Scheduling includes one or more broadcast opportunities for requested Class II SIB broadcasts.

[0300] Exemplary Implementation 53: The access node according to Exemplary Implementation 52, wherein the access node is configured to postpone the broadcast of the second type of SIB until the next boundary.

[0301] Exemplary Implementation 54: The access node according to Exemplary Implementation 36, wherein at the boundary, the delivery method of the second type of SIB changes from on-demand to periodic broadcast, and the broadcast of the second type of SIB begins after the next boundary.

[0302] Exemplary Implementation 55: The access node according to Exemplary Implementation 36, wherein the access node is configured to start broadcasting a second type of SIB if a message is received from a wireless terminal after the next boundary.

[0303] Exemplary Implementation 56: The access node according to Exemplary Implementation 52, wherein the access node is configured to start broadcasting a second type of SIB upon receiving a request message and stop broadcasting after the next boundary.

[0304] Exemplary Implementation 57: A method in an access node of a radio access network, comprising:

[0305] First-class system information and second-class system information are transmitted via a radio interface. The first-class system information includes the availability of second-class system information blocks (SIBs) and an indication of the delivery mode for each available second-class SIB, which is either periodic broadcast or on demand.

[0306] The transmission includes a notification message containing at least one identifier of a Type I SIB, the content of which will be updated at the next boundary of a recurring time period configured by the access node.

[0307] Scheduling includes one or more broadcast opportunities for requested Class II SIB broadcasts.

[0308] Exemplary Implementation 58: The method according to Exemplary Implementation 57 further includes delaying the broadcast of the second type of SIB until the next boundary.

[0309] Exemplary Implementation 59: The method according to Exemplary Implementation 41 further includes, at the boundary, changing the delivery method of the second type of SIB from on-demand to periodic broadcast, and the broadcast of the second type of SIB begins after the next boundary.

[0310] Exemplary implementation 60: The method according to exemplary implementation 41 further includes starting to broadcast a second type of SIB if a message is received from a wireless terminal after the next boundary.

[0311] Exemplary implementation 61: The method according to exemplary implementation 57 further includes starting the broadcast of the second type of SIB upon receiving a request message and stopping the broadcast after the next boundary.

[0312] Exemplary Implementation 62: A wireless terminal, comprising:

[0313] A receiver circuit configured to receive a first type of system information (SI) block from a base station device, the first type of SI block including scheduling information for configuring an SI window, the SI window being a periodic broadcast opportunity for a corresponding one or more second type of system information blocks (SIBs);

[0314] A processor circuit configured to determine the SI window based on scheduling information;

[0315] The receiver circuitry is further configured to perform a reception process to attempt to receive at least one of the second type SIBs within the SI window of the current modification period;

[0316] In the event that at least one of the second type of SIBs is not received within the SI window, the receiver circuitry is configured to continue the receiving process during the current modification period.

[0317] Exemplary Implementation 63: The wireless terminal according to Exemplary Implementation 62, wherein the current modification period is one of a plurality of modification periods configured by the base station device, the plurality of modification periods being repeated time periods.

[0318] Exemplary Implementation 64: The wireless terminal according to Exemplary Implementation 62, wherein the receiver circuitry is further configured to abort the reception process in the next modification cycle.

[0319] Exemplary Implementation 65: The wireless terminal according to Exemplary Implementation 62, wherein the receiver circuitry is configured to continue receiving the process during the current modification cycle, even if the receiver circuitry receives a notification message that notifies one or more of the content of a first type of system information (SI) block or a second type of system information block (SIB).

[0320] Exemplary Implementation 66: A base station apparatus, comprising:

[0321] A processor circuit is configured to generate a first type of system information (SI) block, the first type of SI block including scheduling information for configuring an SI window, the SI window being a periodic broadcast opportunity for a corresponding one or more second type of system information blocks (SIBs); wherein the SI window of the current modification period is configured to enable a wireless terminal to attempt to receive at least one of the second type of SIBs during a reception process performed by the wireless terminal, and if at least one of the second type of SIBs is not received within one or more SI windows, the wireless terminal may continue the reception process in the current modification period;

[0322] A transmitter circuit configured to transmit a first type of system information (SI) block and one or more second type of system information blocks (SIB) to a wireless terminal.

[0323] Exemplary Implementation 67: The base station according to Exemplary Implementation 66, wherein the current modification period is one of a plurality of modification periods configured by the base station device, the plurality of modification periods being repeated time periods.

[0324] Exemplary Implementation 68: A method in a wireless terminal, comprising:

[0325] Receive a first type of system information (SI) block from the base station device. The first type of SI block includes scheduling information for configuring SI windows, which are periodic broadcast opportunities for one or more corresponding second type of system information blocks (SIBs).

[0326] The SI window is determined based on scheduling information;

[0327] Execute the receive procedure to attempt to receive at least one of the second type SIBs within the SI window of the current modification period; and

[0328] If at least one of the second type of SIBs is not received within the SI window, the receiving process continues in the current modification cycle.

[0329] Exemplary Implementation 69: The method according to Exemplary Implementation 68, wherein the current modification period is one of a plurality of modification periods configured by the base station device, the plurality of modification periods being repeated time periods.

[0330] Exemplary Implementation 70: The method according to Exemplary Implementation 68 further includes suspending the receiving process in the next modification cycle.

[0331] Exemplary Implementation 71: The method according to Exemplary Implementation 68 includes continuing the receiving process during the current modification cycle, even if a notification message is received notifying of changes to the content of a first type SI block or a second type SIB.

[0332] Exemplary Implementation 72: A method for a base station apparatus, comprising: transmitting a first type of system information (SI) block to a wireless terminal, the first type of SI block including scheduling information for configuring an SI window, the SI window being a periodic broadcast timing for corresponding one or more second type of system information blocks (SIBs); wherein

[0333] The SI window is determined by the wireless terminal based on scheduling information;

[0334] The receiving process is performed by the wireless terminal to attempt to receive at least one of the second type SIBs within the SI window of the current modification period; and

[0335] If at least one of the second type of SIBs is not received within the SI window, the wireless terminal continues the reception process in the current modification period.

[0336] Exemplary Implementation 73: The method according to Exemplary Implementation 72, wherein the current modification period is one of a plurality of modification periods configured by the base station device, the plurality of modification periods being repeated time periods.

[0337] While the processes and methods of the disclosed embodiments can be discussed as being implemented as software routines, some of the disclosed method steps can be executed in hardware and by a processor running the software. Therefore, these embodiments can be implemented in software form as executed on a computer system, in hardware form as implemented as an application-specific integrated circuit or other type of hardware, or in a combination of software and hardware. The software routines of the disclosed embodiments are executable on any computer operating system and can be executed using any CPU architecture. The instructions for such software are stored on a non-transitory computer-readable medium.

[0338] The functionality of various elements, including function blocks (including, but not limited to, those labeled or described as "computer," "processor," or "controller"), may be provided using hardware such as circuit hardware and / or hardware capable of executing software in the form of programming instructions stored on a computer-readable medium. Therefore, such functionality and illustrated function blocks should be understood as hardware-implemented and / or computer-implemented, and thus machine-implemented.

[0339] In terms of hardware implementation, a functional block may include or encompass, but is not limited to, digital signal processor (DSP) hardware, reduced instruction set processor, hardware (e.g., digital or analog) circuitry, including but not limited to one or more application-specific integrated circuits (ASICs) and / or one or more field-programmable gate arrays (FPGAs), and (where appropriate) state machines capable of performing such functions.

[0340] In terms of computer implementation, a computer is generally understood to include one or more processors or one or more controllers, and the terms computer, processor, and controller are used interchangeably herein. When provided by a computer, processor, or controller, these functions may be provided by a single dedicated computer, processor, or controller, by a single shared computer, processor, or controller, or by multiple individual computers, processors, or controllers (some of which may be shared or distributed). Furthermore, the use of the terms “processor” or “controller” should also be interpreted as referring to other hardware capable of performing such functions and / or executing software, such as the example hardware described above.

[0341] The functionality of various elements, including function blocks (including, but not limited to, those labeled or described as "computer," "processor," or "controller"), may be provided using hardware such as circuit hardware and / or hardware capable of executing software in the form of programming instructions stored on a computer-readable medium. Therefore, such functionality and illustrated function blocks should be understood as hardware-implemented and / or computer-implemented, and thus machine-implemented.

[0342] Nodes communicating via an air interface also have suitable radio communication circuitry. Furthermore, this technology can also be considered as being fully embodied in any form of computer-readable storage, such as solid-state memory, disk, or optical disk containing a suitable set of computer instructions that would enable a processor to execute the technology described herein.

[0343] It should be understood that the techniques disclosed herein are intended to solve problems centered on radio communications and must be rooted in computer technology to overcome problems particularly present in radio communications. Furthermore, in at least one aspect thereof, the techniques disclosed herein improve the functionality of the fundamental functions of the wireless terminal and / or node itself, enabling the wireless terminal and / or node to operate more efficiently, for example, through the careful use of radio resources.

[0344] While the foregoing description contains numerous specific details, these should not be construed as limiting the scope of the technology disclosed herein, but merely as illustrations of some currently preferred embodiments of the technology disclosed herein. Therefore, the scope of the technology disclosed herein should be determined by the appended claims and their legal equivalents. It should be understood that the scope of the technology disclosed herein fully encompasses other embodiments that may become apparent to those skilled in the art, and thus the scope of the technology disclosed herein is defined solely by the appended claims, wherein reference to an element in the singular does not mean "only one" (unless expressly stated otherwise), but rather "one or more". All structural, chemical, and functional equivalents of the elements of the above preferred embodiments known to those skilled in the art are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, an apparatus or method does not necessarily solve every problem sought to be addressed by the technology disclosed herein, as will be covered by the claims. Additionally, the elements, components, or method steps of this disclosure are not intended to be offered to the public, regardless of whether such elements, components, or method steps are expressly stated in the claims. Unless explicitly stated using the phrase "for a means of...", the elements of the claims herein are not to be interpreted in accordance with paragraph 6 of 35 U.SC112.

Claims

1. A wireless terminal, comprising: A receiver circuit is configured to receive a minimum system information (SI) block from a base station device. The minimum SI block includes scheduling information for configuring one or more SI windows, where the one or more SI windows are periodic broadcast opportunities corresponding to one or more other system information blocks (SIBs). as well as The processor circuitry is configured to determine the one or more SI windows based on the scheduling information. The receiver circuitry is also configured to perform a reception process to attempt to receive at least one of the other SIBs within one or more SI windows of the current modification period, wherein The receiving process ends if at least one of the other SIBs is successfully received, and continues until the end of the current modification period if at least one of the other SIBs is not received within any of the one or more SI windows of the current modification period.

2. A method in a wireless terminal, comprising: The minimum system information (SI) block is received from the base station device. The minimum SI block includes scheduling information for configuring one or more SI windows. The one or more SI windows are periodic broadcast opportunities for corresponding to one or more other system information blocks (SIBs). The one or more SI windows are determined based on the scheduling information; Perform a receive procedure to attempt to receive at least one of the other SIBs within one or more SI windows of the current modification period, and The receiving process ends if at least one of the other SIBs is successfully received, and continues until the end of the current modification period if at least one of the other SIBs is not received within any of the one or more SI windows of the current modification period.

Images