RU2767172C1 - Apparatus and method for obtaining system information on request in wireless communication - Google Patents

Abstract

FIELD: wireless communication.

SUBSTANCE: to achieve the technical result, the user equipment containing a processor, receiver and transmitter circuits, initiates the process of obtaining a system information block (SIB) of the first type. The SIB of the first type includes the scheduling information of a system information (SI) message containing an SIB of the second type and an indication of the broadcast status for the SI message indicating delivery on request. The user equipment accepts the SIB of the first type, transmits the SI request messages, and initiates the process of receiving the SI message.

EFFECT: reduced time of reception of system information, as well as reduced consumption rate of radio resources.

8 cl, 30 dwg, 2 tbl

Description

This application claims priority and benefit from U.S. Provisional Application 62/669,838, filed May 10, 2018, entitled APPARATUS AND METHOD FOR ACQUISITION OF ON-DEMAND SYSTEM INFORMATION IN WIRELESS COMMUNICATIONS, which is hereby incorporated by reference in its entirety.

FIELD OF TECHNOLOGY

[0001] The technology relates to wireless communications and, in particular, to methods, apparatus, and techniques for requesting, transmitting, updating, and using system information (SI) in wireless communications.

BACKGROUND OF THE INVENTION

[0002] In wireless communication systems, a radio access network typically includes one or more access nodes (such as a base station) that communicate over radio channels via an air or air interface with a plurality of wireless terminals. In some technologies, such a wireless terminal is also referred to as user equipment (UE). The group, known as the 3rd Generation Systems Partnership Project (3GPP), is committed to defining globally applicable technical specifications and producing technical reports for existing and future generations of wireless communication systems. The 3GPP Long Term Evolution (LTE) standard and 3GPP LTE-Advanced (LTE-A) are projects to improve the legacy Universal Mobile Telecommunications System (UMTS) standard for a mobile phone or device to meet future requirements.

[0003] In typical cellular mobile communication systems, a base station transmits over radio channels certain information that is required by mobile stations to access the network. In the Long Term Evolution (LTE) and LTE-Advanced (LTE-A) standard, this information is referred to as "system information" (SI). Each Access Node, such as an Evolved NodeB (eNB) or gNB in a 5G New Radio (NR) network, broadcasts such system information to its coverage area via a Service Information Block (MIB) and multiple System Information Blocks (SIBs) on the downlink radio resources allocated to the access node.

[0004] After entering the eNB or gNB coverage area, the wireless terminal (UE) must obtain all the MIB/SIBs necessary to access the system. For UEs in the coverage area, the eNB or gNB periodically broadcasts all MIB/SIBs relevant to the offered services, with each type of MIB or SIBs being transmitted in the dedicated radio resource(s) on its own predefined radio resource(s). adjustable frequency.

[0005] This broadcast-based periodic transmission method (eg, multicasting all SIBs, not just those needed for system access) is effective under the condition that many UEs are almost always in a coverage area (such as a macro cell). However, this approach can waste valuable radio resources when deploying small cells. Thus, more efficient methods for transmitting SIBs are required.

[0006] Therefore, there is a need for the methods, devices and techniques described in the example of the technology object in this document, which are necessary to obtain and / or update SIBs to / from another SI (SIBs of another SI), as well as to perform the determination failure in the process of receiving the SI message and the corrective processes for it.

SUMMARY OF THE INVENTION

[0007] In one exemplary aspect, the technology described herein relates to a wireless terminal that communicates over an air interface with a radio access network (RAN) access node and its method of operation. In a basic embodiment, a wireless terminal includes a receiver circuit, a processor circuit, and a transmitter circuit. The processor circuitry is configured to initiate a first type system information block (SIB) acquisition process to receive the first type SIB. The first type SIB contains system information (SI) message scheduling information, the SI message containing at least one second type SIB and an indication of the broadcast state for the SI message, the indication indicating on-demand delivery. The receiver circuitry is configured to receive a first type SIB. The transmitter circuitry is configured to send an SI request message to request an SI message. The processor circuitry is further configured to initiate the SI message acquisition process to receive the SI message and, in case the stored version of one of the at least one second type SIB is invalid, the first type SIB acquisition process is initiated when the SI message acquisition process fails.

[0008] In another exemplary aspect, the technology described herein relates to a base station device that communicates over an air interface with user equipment. The base station device includes a transmitter circuit, a receiver circuit, and a processor circuit. The transmitter circuit is configured to transmit a system information block (SIB) of the first type. The first type SIB contains scheduling information for a system information (SI) message, the SI message containing at least one SIB of the second type and an indication of the broadcast state for the SI message, the indication indicating on-demand delivery. The receiver circuitry is configured to receive an SI request message to request an SI message. The processor circuitry is configured to use the transmitter circuitry to deliver the SI message. If the user equipment fails to receive the SI message during the process of receiving the SI message, the user equipment reacquires the first type SIB if the version of one of the at least one second type SIBs stored in the user equipment is invalid.

[0009] In another exemplary aspect, the technology described herein refers to a method in a wireless terminal that communicates over an air interface with a radio access network (RAN) access node. In the main mode example, the method includes initiating a first type system information block (SIB) acquisition process to receive the first type SIB; reception of SIB of the first type; sending a system information request (SI) message; and initiating an SI message receiving process to receive the SI message. The first type SIB contains scheduling information for the SI message and an indication of the broadcast status for the SI message, the indication indicating delivery on request. The SI message contains at least one SIB of the second type. The process of obtaining the SIB of the first type is initiated upon failure in the process of obtaining the SI message in case the stored version of one of the at least one SIB of the second type is not valid.

[0010] In yet another exemplary aspect, the technology described herein relates to a method in the context of a radio access network (RAN) access node that communicates with a wireless terminal or user equipment over an air interface. In the main mode example, the method includes transmitting a system information block (SIB) of the first type; receiving a system information (SI) request message to request an SI message; and delivery of the SI message. The first type SIB contains scheduling information for the SI message and an indication of the broadcast status for the SI message, the indication indicating delivery on request. The SI message contains at least one SIB of the second type. If the user equipment fails to receive the SI message during the process of receiving the SI message, the user equipment reacquires the first type SIB if the version of one of the at least one second type SIBs stored in the user equipment is invalid.

BRIEF DESCRIPTION OF GRAPHICS

[0011] The above and other objects, features, and advantages of the technology described herein will be apparent from the following more detailed description of the preferred embodiments, as illustrated in the accompanying drawings, in which the same details in different views are shown by legend. The graphics are not necessarily drawn to scale, but instead focus is on illustrating the principles of the technology described herein.

[0012] In FIG. 1 is a schematic view showing radio resource control (RRC) state machine transients.

[0013] In FIG. 2 is a schematic view showing an example of a universal communication system comprising a radio access node and a wireless terminal, where the wireless terminal requests and the radio access node provides other system information (other SI) when the wireless terminal is in the RRC_CONNECTED state.

[0014] In FIG. 3 is a flowchart illustrating exemplary basic actions or steps performed by a wireless terminal of the exemplary exemplary communication system shown in FIG. 2.

[0015] In FIG. 4-7 are schematic diagrams illustrating different examples of system information block (SIB) formats that contain a minimum SI and that allow different system information (other SI) to be available.

[0016] In FIG. 8 is a schematic diagram illustrating an exemplary message flow of an on-demand SI acquisition procedure.

[0017] In FIG. 9A, FIG. 9B and FIG. 9C are diagrams illustrating three variations of the SI request procedure.

[0018] In FIG. 10 is a schematic diagram showing, for example, a SystemInformationRequest message in which the siRequest information element contains a bitmap.

[0019] In FIG. 11 is a schematic diagram illustrating an example of a message flow for a procedure for obtaining a periodic broadcast SI.

[0020] In FIG. 12 is a schematic diagram showing an example of an exemplary communication system comprising a wireless terminal capable of detecting a failure in the process of receiving an SI including a request SI message after the SI request is successfully completed.

[0021] In FIG. 13A-Fig. 13D are schematic representations of different implementations of SIB1 containing termination condition parameters.

[0022] In FIG. 14 is a schematic diagram illustrating an example of a message flow including an on-demand SI get procedure that failed.

[0023] In FIG. 15 is a flowchart showing an example of the main characteristic actions or steps performed by the wireless terminal shown in FIG. 12.

[0024] In FIG. 16 is a flowchart showing an example of the main characteristic actions or steps performed by the access node shown in FIG. 12.

[0025] In FIG. 17A is a schematic view of a system information retrieval failure detector that includes an SI window counter to determine if the SI message acquiring process has terminated.

[0026] In FIG. 17B is a schematic diagram of a system information retrieval failure detector that includes an SI message acquiring process timer for determining whether the SI message acquiring process has terminated.

[0027] In FIG. 18A is a schematic diagram showing a common termination condition for a plurality of SI messages.

[0028] In FIG. 18B is a schematic diagram showing different termination conditions for different SI messages.

[0029] In FIG. 19 is a schematic diagram showing an example of an exemplary communication system comprising a wireless terminal capable of detecting a failure in an SI reception process including a periodically broadcast SI message.

[0030] In FIG. 20 is a schematic diagram illustrating an example message flow including an unsuccessful SI acquisition procedure for a periodically broadcast SI message.

[0031] In FIG. 21 is a flowchart showing an example of the main characteristic actions or steps performed by the wireless terminal shown in FIG. 19.

[0032] In FIG. 22 is a flowchart showing an example of the main characteristic actions or steps performed by the access node shown in FIG. 19.

[0033] In FIG. 23 is a schematic view showing an example of electronic equipment, which may include node electronic equipment or terminal electronic equipment.

DETAILED DESCRIPTION

[0034] In the description below, for purposes of explanation, but not limitation, specific details are set forth, such as specific architectures, interfaces, techniques, etc., to provide a thorough understanding of the technology described herein. However, those skilled in the art will appreciate that the technology described herein may be practiced in other embodiments that are outside the scope of these specific details. This means that those skilled in the art will be able to come up with various designs that, while not explicitly described or shown herein, implement the principles of the technology described herein and do not depart from the spirit and scope of the present invention. In some instances, detailed descriptions of prior art devices, circuits, and methods have been omitted so as not to obscure the description of the technology described herein in unnecessary detail. All statements made herein that set forth principles, aspects, and embodiments of the technology described herein, as well as specific examples thereof, are intended to cover both their structural and functional equivalents. Further, such equivalents are intended to include both currently known equivalents and equivalents to be developed in the future, i.e., any elements developed that perform the same function regardless of structure.

[0035] Thus, for example, those skilled in the art will appreciate that the block diagrams provided herein may show conceptual representations of an illustrative circuit or other functional blocks in which the principles of the technology are applied. Likewise, it should be understood that any flowcharts, state transition diagrams, pseudocode, and the like represent various processes that can be substantially represented on a computer-readable medium, and therefore executed by a computer or processor, regardless of whether such a computer is depicted. or processor explicitly or not.

[0036] As used herein, the term "core network" may refer to a device, a group of devices, or a subsystem in a telecommunications network that provides services to users of the telecommunications network. Examples of services provided by the core network include aggregation, authentication, call switching, service invocation, gateways to other networks, etc.

[0037] As used herein, the term "wireless terminal" may refer to any electronic device used to transmit voice and/or data over a telecommunications system, such as (without limitation) a cellular network. Other terminology may be used to refer to wireless terminals and non-limiting examples of such devices, such as user equipment terminal (UE), UE, mobile station, mobile device, access terminal, subscriber station, mobile terminal, remote station, user terminal, terminal, indoor unit, cellular phones, smartphones, personal digital assistant (PDA), tablets, netbooks, electronic readers, wireless modems, etc.

[0038] As used herein, the terms "access node", "node", or "base station" may refer to any device or group of devices that facilitate wireless communication or otherwise provide an interface between a wireless terminal and a telecommunications system. A non-limiting example of a base station may, within the scope of the 3GPP specification, include a Node B (NB), an enhanced Node B (eNB), a home eNB (HeNB), a 5G (New Radio [NR]) gNB, or some other a similar term. Another non-limiting example of a base station is an access point. An access point may be an electronic device that allows a wireless terminal to access a data network such as (without limitation) a local area network (LAN), a wide area network (WAN), the Internet, etc. Although some examples of systems and methods described in herein may be described with reference to these standards (eg, 3GPP releases 8, 9, 10, 11, 12 and beyond), the scope of the present description should not be limited in this regard. At least some aspects of the systems and methods described herein can be used in other types of wireless communication systems.

[0039] As used herein, the term "telecommunication system" or "communication system" can refer to any network of devices used to transmit information. A non-limiting example of a telecommunications system is a cellular network or other wireless communication system.

[0040] As used herein, the term "cellular network" may refer to a network distributed over cells, with each cell served by at least one fixed transceiver, such as a base station. A "cell" can be any communication channel that is defined by standards or regulatory agencies for use in International Mobile Telecommunications Enhanced (IMTAdvanced). All or a subset of cells may be accepted within 3GPP as licensed bands (eg, frequency band) for use in communication between a base station, such as a Node B, and a UE. A cellular network using licensed frequency bands may include configured cells. The configured cells may include cells that the UE is aware of and has permission from the base station to transmit or receive information.

[0041] As used herein, the term "system information" (SI) may include a service information block (MIB) and multiple system information blocks (SIB) provided over downlink radio resources allocated to an access node. The system information may be broadcast, and some types of system information may be provided upon request, such as upon receiving a request for system information from a wireless terminal.

[0042] In various aspects of the technology described herein, system information is classified into numerous categories or types. In the exemplary embodiment and mode, the first type of system information is the minimum system information (minimum SI) containing the minimum amount of information required by UEs for initial network access periodically broadcast by each access node (e.g., eNB for LTE, gNB for 5G radio system) . In some configurations, the minimum system SI may consist of a MIB and a limited number of SIBs. The MIB may contain essential information for the radio system to help wireless terminals synchronize with the serving access point, and may contain an instruction to obtain at least one of the essential SIBs. The minimum SI may also be referred to as "essential SI" or first type system information.

[0043] The second type of system information, such as "other system information", "other SI", or second type system information, contains all other types of information, i.e., all types of system information, except for the minimum system information. Another SI may contain multiple System Information Blocks (SIBs) that are not classified as a minimum SI. Another SI may also be referred to as a "non-essential SI". However, type 2 system information should not be confused with a type 2 SIB, which is a specific (second) system information block (SIB) that may be included in the minimum system information or may be part of another SI.

[0044] In some embodiments and modes described herein, for each of the SIBs, the access node may choose to broadcast the SIB periodically, similar to the SIBs in the minimum SI. In an alternative embodiment, the access node may decide to refrain from transmitting the SIB prior to receiving a pull request from the UE. In this case, the access node may advertise the availability of on-demand delivery using the minimum SI.

[0045] As described herein, both the access node and the wireless terminal may control their respective radio resource control (RRC) state machines. RRC state machines transition between several RRC states, including RRC_IDLE, RRC_INACTIVE, and RRC_CONNECTED. On FIG. 1 shows a state transition diagram for RRC states. From the point of view of a wireless terminal, such as a user equipment (UE), RRC states can be briefly characterized as follows.

RRC_IDLE:

configurability of UE-specific DRX (discontinuous reception) by upper layers;

UE managed mobility based on network configuration;

UE device:

controls the paging channel;

performs neighbor cell measurements and cell selection (reselection);

gets system information.

RRC_INACTIVE:

UE-specific DRX may be configured by upper layers or RRC layer;

UE managed mobility based on network configuration;

storing the context of the access layer (AS) in the UE;

UE device:

controls the paging channel;

performs neighbor cell measurements and cell selection (reselection);

performs notification area updates based on the RAN when moving outside the notification area based on the RAN;

gets system information.

RRC_CONNECTED:

storing the AS context in the UE;

transmitting unicast data to/from the UE;

the ability to configure the UE at lower layers with UE-specific DRX;

network-managed mobility, i.e., intra-NR handover to/from E-UTRAN;

UE device:

controls the paging channel;

monitors control channels associated with the shared data channel to determine if data is scheduled for it;

provides channel quality information and feedback information;

performs neighbor cell measurements and measurement reports;

gets system information.

[0046] The technology described herein relates, for example, to apparatus, methods and procedures for obtaining and/or updating SIBs to/from another SI (SIBs of another SI), and also includes detecting a failure in the process of receiving an SI message and methods for correcting in such situation.

[0047] In FIG. 2 shows an exemplary communications system 20 in which the radio access node 22 communicates via an air interface or air interface 24 (e.g., a Uu interface) with a wireless terminal 26. As mentioned above, the radio access node 22 may be any node suitable for communicating with a wireless terminal. terminal 26, such as, for example, a base station node, or eNodeB (eNB), or gNB. Node 22 includes a node processor circuit (node processor 30) and a node transceiver circuit 32 . Node transceiver circuit 32 typically includes node transmitter circuit 34 and node receiver circuit 36, which are also referred to as node transmitter and node receiver, respectively.

[0048] The 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, which are also referred to as terminal transmitter 44 and terminal receiver 46, respectively. The wireless terminal 26 also typically includes a user interface 48. The user interface 48 of the terminal may be for both user input and output operations, and may also include (for example) a screen, such as a touch screen, which can either display information to the user, and receive information entered by the user. The user interface 48 may also include other types of devices such as, for example, a speaker, a microphone, or a haptic feedback device.

[0049] Both at the radio access node 22 and at the air interface 24, the respective transceiver circuits 22 include the antenna(s). The transmitter circuit 34 and the transmitter circuit 44 may include, for example, an amplifier(s), a modulation circuit, and other conventional transmission equipment. Receiver circuitry 36 and receiver circuitry 46 may include, for example, amplifier(s), demodulation circuitry, and other conventional receiver equipment.

[0050] In normal operation, the access node 22 and the wireless terminal 26 communicate with each other via the air interface 24 using predefined information configurations. As a non-limiting example, the radio access node 22 and the wireless terminal 26 may communicate over the air interface 24 using "frames" of information, which may be configured to include different channels. For example, in the Long Term Evolution (LTE) standard, a frame that may have both a downlink portion(s) and an uplink portion(s) may contain a set subframes, with each LTE subframe in turn divided into two slots. A frame can be conceptualized as a resource mesh (two-dimensional mesh) consisting of resource elements (REs). Each column of the 2D grid represents a symbol (eg, a downlink (DL) OFDM symbol from a node to a wireless terminal; an SC-FDMA symbol in an uplink (UL) frame from a wireless terminal to a node). Each grid line represents a subcarrier. The frame and subframe structure is just an example of a technique for formatting information to be transmitted over an air or air interface. It should be understood that "frame" and "subframe" may be used interchangeably, or may include or be implemented through other information formatting units, and as such they may be referred to by other terms (such as, for example, "blocks") .

[0051] As shown, in order to enable communication between the radio access node 22 and the wireless terminal 26 via the air interface 24, the node processor 30 and the terminal processor 40 in FIG. 2 contain the corresponding information handlers. In an implementation example in which information is transmitted via frames, the information handler for the radio access node 22 is shown as the node's frame/signal scheduler/handler 50, and the information handler for the wireless terminal 26 is shown as the terminal's frame/signal handler 52.

[0052] The processor 30 of the radio access node 22 also includes a system information (SI) generator 54 . As described above, at least a portion of the system information generated and provided by the system information (SI) generator 54 is the minimum system information (minimum SI), also known as the first type of system information, represented by the minimum SI handler 54M. The system information part may be another system information (other SI), also known as second type system information, represented by the other SI handler 540 in FIG. 2. The wireless terminal 26 uses system information (SI) generated by the radio access node 22. Some of the minimum SIs may inform wireless terminal 26 that another SI is available.

[0053] In FIG. 2 illustrates a generic 2-1 message by which the node radio resource controller 54 can provide the minimum SI to the wireless terminal 26. request as described in this document. 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.

[0054] The technology described herein relates, for example, to apparatus, methods, and procedures for obtaining and/or updating System Information Blocks (SIBs) to/from another SI (SIBs of another SI) upon request. Because at least some of the embodiments and modes described herein employ Radio Resource Control (RRC) procedures, FIG. 2 shows that the terminal processor 40 includes a node radio resource control (RRC) controller 60, such as an RRC node controller 60. The RRC node controller 60 may execute an instance of the RRC state machine for each wireless terminal with which the access node 20 communicates, with each instance keeping track of the RRC state transitions that the wireless terminal associated with the respective instance is in.

[0055] In FIG. 2 also shows a terminal processor 40 of a wireless terminal 26, including an RRC terminal controller 70 in addition to an SI terminal processor 56. The RRC terminal controller 70 includes or executes the RRC state machine described above, which goes through the RRC states (as described above and shown in FIG. 2) to communicate using the wireless terminal 26.

[0056] Thus, FIG. 2 shows that the access node 22 includes a node processor 30, such as a node processor circuit 30, a transmitter circuit 34, and a receiver circuit 36. The transmitter circuit 34 is configured to transmit the first type system information over the air interface, the first type system information including the availability of an SI message belonging to the second type system information. The receiver circuitry 36 is configured to receive a request message from the wireless terminal to request delivery of an SI message that is available upon request. The transmitter circuit 34 is further configured to transmit the SI message to the wireless terminal.

[0057] Thus, in FIG. 2 shows that wireless terminal 26 communicates over air interface 24 with access nodes, such as access node 22, of a radio access network (RAN). Wireless terminal 26 includes a receiver circuit 46, a transmitter circuit 44, and a terminal processor 40, such as a terminal processor circuit. The receiver circuit 46 is configured to receive the first type of system information over the air interface. The terminal processor circuitry is configured to generate a request message for requesting a second type SIB that is available upon request. The transmitter circuit 44 is configured to transmit a request message over the air interface while in an established connection state. The receiver circuit 46 is also configured to receive the SI message while in the connected state.

[0058] In FIG. 3 shows exemplary representative actions or steps performed in conjunction with the general operation of a radio access network (RAN) wireless terminal, such as wireless terminal 26 shown in FIG. 2. Step 3-1 includes receiving, eg, receiving, by the wireless terminal the minimum SI broadcast from the current serving access node, eg, access node 22 . The minimum SI may be broadcast in a message such as message 2-1 in FIG. 2. The minimum SI may contain information about the other SI, including the delivery method, such as periodic broadcast/demand transmission, scheduling information, validity information, etc. Based on this information, the wireless terminal in step 3-2 can determine which The SI message(s) should be obtained upon request. In step 3-3, the wireless terminal may send a request message (shown as message 2-2 in FIG. 2) to the access node, where the request message indicates the SI message(s) that the wireless terminal intends to receive. terminal. As part of step 3-4, the wireless terminal 26 may attempt to receive the requested SI message(s), which(s), for example, has been sent using message 2-3 in FIG. 2.

[0059] It has been stated above that the first type of system information includes the availability of an SI message belonging to the second type of system information, that the request message requests delivery of an SI message available on request, and the transmission of the SI message to the wireless terminal. It should be understood that reference herein to "an SI message belonging to the second type of system information" means one or more pieces of other system information (other SI), for example, one or more SI messages belonging to the second type of system information. In some exemplary situations, in fact, only one SI message may be declared available and, accordingly, periodically broadcast or requested on request. But in other exemplary situations, a plurality of SI messages (eg, a plurality of fragments of another SI) are advertised as available, some of which may be broadcast periodically and others may be requested on demand. In addition, it should be noted that in some configurations (eg, the configuration shown in Fig. 7 or Fig. 13A-D) availability may be included in the scheduling information (eg, schedulingInfoList, as described below).

[0060] In some configurations, availability and delivery information for SIBs of another SI may be included in the Type 1 SIB, one of the SIBs in the minimum SI. On FIG. Figure 4 shows an example of a type 1 SIB format, including schedulingInfoList, si-WindowLength, otherSIBInfoList , validity area identification ( si-AreaID ), and possibly other configuration options. otherSIBInfoList is a list of otherSIBInfo that contains SIB-Type, SIB ID, validityInfo and SIB validity information (value tag [ valueTag ] and other parameters like validity timer etc.).

[0061] SIBs other than SIB1 are conveyed in SystemInformation (SI) messages, and the mapping of SIBs to SI messages is flexibly configured via the schedulingInfoList included in SIB1, with the limitation that each SIB is only contained in a single SI message and only SIBs having the same scheduling requirement (periodicity given by si-periodicity ) can be matched with the same SI message. It is possible to send multiple SI messages at the same frequency.

[0062] In one configuration, each schedulingInfo element of the schedulingInfoList may represent a single SI message containing its periodicity ( si-Periodicity ), delivery method ( deliveryMethod ), indicating whether this SIB is periodically broadcast or to be transmitted when requested (on request), and corresponding SIB types (one or more SIB-Type ). The actual broadcast capability, eg in terms of timing/resources, of a given SI may be determined using a predefined or network configured formula as a function of at least an appropriate periodicity. At every opportunity, an SI message broadcast may occur within a window duration ( si-WindowLength ). Hereinafter, the broadcast capability is also referred to as an SI window. It is often possible to transmit more than one SIB in the same SI window.

[0063] In the configuration shown in FIG. 4, the si-AreaID is common to all SI messages or SIB types, which means that all SIBs have the same area of validity. In an alternative embodiment, in another configuration, each SI message may have an assigned validity area. On FIG. 5 shows an example of the SIB1 format for such a configuration, in which each SI message may have an assigned scope of validity. Further, in another configuration with an example format such as that shown in FIG. 6, each type of SIB may have an assigned scope of validity. Thus, in different implementations, the system information (SI) generator 54 shown in FIG. 2 operating with the node frame/signal scheduler/handler 50 generates the different formatted SI messages shown in FIG. 4, FIG. 5 and FIG. 6 to be transmitted by the node transmitter circuit 34 over the air interface 24.

[0064] In FIG. 7 shows an alternative format for SIB 1, logically equivalent to the format shown in FIG. 4. The si-BroadcastStatus information element shown in FIG. 7 may be functionally identical to the previously described deliveryMode information element. In one configuration, the sibValueTagList information element may contain a list of value tags for the available SIBs included in the schedulingInfoList , in the order of the SIB numbering scheme (eg, SIB2, SIB3, SIB4, SIB5, ....). In another configuration, sibValueTagList may contain a list of value tags for available SIBs (included in schedulingInfoList ) as well as unavailable SIBs (not included in schedulingInfoList ) in SIB numbering scheme order (e.g. SIB2, SIB3, SIB4, SIB5, ....). In this case, the preset value can be set to the value tag for the unavailable SIB. Accordingly, the si-BroadcastStatus information element may be used to indicate the state of the broadcast (eg, the broadcast state may be either periodic or on demand).

[0065] In FIG. 8 shows an example message flow diagram of the procedure for obtaining SI on request. As shown, in action 8-0, the wireless terminal 26, in either of the RRC_IDLE, RRC_INACTIVE, or RRC_CONNECTED states, stores the contents of SIB #A with validity information, valueTag= a, si-AreaID= 2, that the wireless terminal received previously. As part of step 8-1, the wireless terminal may receive SIB1 as the minimum SI from the current serving access node. As shown in FIG. 4, FIG. 5, Fig. 6 and FIG. 7, SIB1 includes a scheduleInfoList , which in turn may contain one or more schedulingInfo information elements. An example scheduleInfoList for this scenario is shown in Table 1, where the kth schedulingInfo indicates that the SI message associated with this schedulingInfo (hereinafter SI #k) containing SIB #A will be available on demand delivery. Moreover, otherSIBInfo corresponding to SIB #A indicates that the validity information of SIB #A is valueTag=b, si-AreaID=3 . It is assumed that each time the wireless terminal receives SIB1, it has already received the MIB in advance.

[0066] Table 1 … schedulingInfoList { … k-th schdulingInfo (SI No. k) { … deliveryMethod=on-demand SIB-type=A … } … } } … otherSIBInfoList { … otherISBInfo { SIB-type=A ValidityInfo { valueTag=b … } … } … } … si-AreaID=3 …

[0067] Given that the stored SIB #A is now invalid, the wireless terminal may decide to obtain a valid version of SIB #A and may initiate the SI request procedure represented by step 8-2 and described herein. Upon successful completion of the SI request procedure, the wireless terminal may begin the SI receive procedure, outlined as step 8-3 in FIG. 8. In the SI receiving procedure, the wireless terminal monitors the signals from the access node in the assigned SI windows received from the scheduling information ( scheduleInfo ) in SIB1, and thus tries to receive the requested SI #k. The SI windows are shown as dotted boxes in FIG. 8. In FIG. 8, act 8-3a shows the first transmission of requested SI #k that failed, and act 8-3b shows the second transmission of requested SI #k that succeeded. The tail of the downward vertical arrow in the description of the SI reception procedure in FIG. 8 is associated with the start of the SI reception procedure, while the pointer of the same downward vertical arrow is associated with the completion of the SI reception procedure (when SI No. k is successfully received). On FIG. 8 also shows in the form of action 8-4 that other transmissions of the requested system information can also be performed even after successful reception of the desired SI #k by the wireless terminal.

[0068] In one configuration, the wireless terminal may use a counter that increments by one with each SI window of a particular SI message, eg, SI #k. In this configuration, the SI receive procedure may terminate when the requested SI message(s) is successfully received or when the counter reaches the maximum counter value. In another configuration, the wireless terminal starts a timer at the beginning of the SI reception procedure. In this configuration, the SI receive procedure may terminate upon successful receipt of the requested SI message(s) or upon expiration of a timer. The maximum counter value, or timer value, which may be common to all SI messages or per SI message, may be pre-configured or configured by the network via system information. The conditions under which the wireless terminal must terminate the SI reception process are referred to herein as "termination conditions".

[0069] In FIG. 9A, FIG. 9B and FIG. 9C shows three variations of the SI request procedure. As shown in FIG. 9A, which can be applied to wireless terminals in any of the RRC states, a pull-on-delivery request for SI messages can be performed by sending a random access preamble that may contain a sequence selected from a set of available sequences configured by the access node with the minimum SI. This sequence defines the preamble index. When an access node detects a transmission of a preamble sequence, it may respond with a random access response that includes the preamble index corresponding to the sequence. Upon receipt, the wireless terminal may check if the preamble index in the random access response matches the index associated with the preamble sequence, and then send a SystemInformationRequest message to the access node containing the identifier of the SI messages (e.g., SI messages #k) that the wireless terminal intends to receive. . In response, the access node may send a Request Acknowledgment SystemInformation message indicating that the requested SI message(s) will be broadcast(s) in the next SI window scheduled for the requested SI(s).

[0070] In one configuration, the access node may include in the minimum SI a set of preamble indices, each of which is for requesting on-demand delivery of one or more specific SI messages. On FIG. 9B shows an example of an SI request procedure using this configuration, in which a wireless terminal in any RRC state can transmit a random access preamble sequence given by the preamble index associated with the SI message(s) selected by the wireless terminal. The wireless terminal, upon receiving the random access response including the preamble index, may consider that the request procedure was successful.

[0071] The SI request procedure in FIG. 9C may be applicable to wireless terminals in the RRC_CONNECTED state in which a SystemInformationRequest message is sent without a random access preamble/response.

[0072] In any of the three options described above, the wireless terminal may proceed to the SI receive procedure if the SI request procedure is successful. Otherwise, the wireless terminal may consider the serving cell (managed by the access node) as forbidden, resulting in cell reselection.

[0073] The SystemInformationRequest message shown in FIG. 9A or FIG. 9C may include an information element (eg, siRequest ) to indicate which SI message(s) the wireless terminal intends to receive. In one configuration, as shown in FIG. 10, the siRequest may comprise a bitmap in which each bit corresponds to a schedulingInfo information element in SIB 1 of the current serving cell, with the bits in the order of the schedulingInfo information elements. In this case, each bit of the bitmap can correspond to a particular SI message. In an alternative embodiment, the siRequest may contain a field indicating that the wireless terminal intends to receive at least one SI message on request. In this case, the access node may start broadcasting all SI messages on demand for a predetermined period of time. The SystemInformation message shown in FIG. 9A or FIG. 9C may include siAck , an information element for acknowledging a siRequest . In one configuration, the siAck may contain the same bitmap as in the SystemInformationRequest indicating the SI message(s) to be broadcast. In an alternative embodiment, the siAck may contain a single boolean field indicating whether the request was accepted.

[0074] In FIG. 11 shows an example message flow diagram for an SI acquisition procedure for an SI message periodically broadcast. Action 11-0 involves the wireless terminal 26 storing the contents of SIB #A with validity information, such as valueTag= a and si-AreaID= 2 in any of the RRC_IDLE, RRC_INACTIVE, or RRC_CONNECTED states. Step 11-1 includes receiving by the wireless terminal 26 from the current serving access node 22 SIB1 as the minimum SI, which, as understood from the previous description, includes one or more schedulingInfo information elements. In the scenario shown in Fig. 11, and also as shown in Table 2, the kth schedulingInfo indicates the periodic broadcast of the current SI message associated with this schedulingInfo (hereinafter SI #k) containing SIB #A. Moreover, SIB1 defines (see .table 2) that otherSIBInfo corresponding to SIB #A indicates that the validity information of SIB #A is now valueTag= b and si-AreaID = 3.

[0075] Based on the fact that the stored SIB #A is now incorrect, within step 11-3, the wireless terminal 26 starts an SI receive procedure in which the wireless terminal may attempt to receive an SI message (SI #k) in the SI windows specified in SIB1 . On FIG. 11, step 11-3a illustrates an unsuccessful attempt to receive an SI message in the first SI window for SI #k, followed by step 11-3b, which is a successful reception of the SI message in the second SI window for SI #k. Thus, as shown in FIG. 11, if an SI message is not received at the end of the SI window (as in the case of step 11-3a), the wireless terminal 26 may retry at the next SI window event for the corresponding SI message until it has successfully received the SI message (as was done in step 11-3b).

[0076] Table 2 … schedulingInfoList { … k-th schdulingInfo (SI No. k) { … deliveryMethod=broadcast SIB-type=A … } … } } … otherSIBInfoList { … otherISBInfo { SIB-type=A ValidityInfo { valueTag=b … } … } … } … si-AreaID=3 …

[0077] UNSUCCESSFUL ATTEMPT TO RECEIVE SYSTEM INFORMATION ON REQUEST

[0078] In FIG. 12 shows an exemplary communication system 20(12) comprising a wireless terminal 26(12) configured to detect a failure in the SI reception process, including an SI message on request, upon successful completion of the SI request. Access node 22(12) and wireless terminal 26(12) in FIG. 12 are substantially identical to the respective access point 22 and wireless terminal 26 in FIG. 2, except as noted in this document. With respect to similarity, for example, the radio access node 22(12) comprises a node processor 30 and a node transceiver circuit 32, the node processor 30 comprising, for example, a node frame/signal scheduler/handler 50, a system information (SI) generator 54, and a controller. 60 RRC node. Similarly, wireless terminal 26(12) includes a terminal processor 40, a terminal transceiver circuit 42 with a terminal processor 40 including a terminal frame/signal scheduler/handler 52, a system information (SI) processor 56, and a terminal RRC controller 70.

[0079] In FIG. 12 also shows that the wireless terminal 26(12) includes a system information retrieval failure detector 80. The terminal processor 40, and in particular the SI processor 56, may comprise or form a system information retrieval failure detector 80. The system information retrieval failure detector 80 is configured to detect a failure in the process of receiving the SI message. The failure detector 80 upon receiving system information may perform such failure determination based on the termination condition as explained herein.

[0080] The system information generator 54 of the radio access node 22(12) is configured to generate system information of the first type. For the embodiment and mode in FIG. 12 and in the non-limiting example of the method shown in FIG. 13, the first type system information includes (information elements or the like indicating): the availability of second type SI messages; scheduling information for each of the SI messages; a delivery method for each of the second type SI messages; and a configuration parameter for configuring at least one termination condition for determining a failure in the process of receiving the SI message for the second type of SI messages on request.

[0081] As understood herein, a second type SI message contains at least one system information block (SIB), and the delivery method may be a periodic broadcast or on-demand delivery. The transmitter circuit 36 of the radio access node 22(12) is configured to transmit the first type of system information over the air interface 24 to the wireless terminal 26(12), as shown by arrow 12-1 in FIG. 12.

[0082] As in the exemplary embodiment and mode in FIG. 2, the other SI request generator 72 may request at least one second type SI upon request of the wireless terminal 26(12) using a request message as indicated by arrow 12-2 in FIG. 12. The second type SI request message, shown by arrow 12-2, is received by the node receiver circuit 36. The node processor 30, and in particular the SI generator 54, generates a requested SI message (second type) in one or more transmission windows, with the transmission of the requested SI message indicated by arrow 12-3 in FIG. 12.

[0083] As mentioned above, the system information retrieval failure detector 80 may perform failure determination in the SI message acquisition process. Meanwhile, in the exemplary embodiment and mode, the terminal processor 40 operating in response to or with operation of the system information acquisition failure detector 80 is configured to trigger the acquisition of the first type of system information. Thus, the terminal processor 40 is configured to initiate the acquisition of the first type of system information, for example, to re-request the first type of system information (minimum SI) from the radio access node 22(12) after a failure in the process of receiving the SI message. On FIG. 12, such a first type system information request is indicated by an arrow 12-4.

[0084] In FIG. 13A shows an example of the SIB1 format based on the format shown in FIG. 7, with an additional information element si-MaxAcqAttempts . The si-MaxAcqAttempts information element provides a termination condition for the SI receive procedure by indicating the maximum number of SI message receive opportunities (eg, SI windows) allowed before the SI receive procedure terminates. On FIG. 13B shows an alternate SIB1 format in which the ue-TimersAndConstants information element includes a timer configuration (T#x) to be used as a termination condition for the SI receive procedure.

[0085] In FIG. 14 shows an example message flow diagram for an on-demand SI get procedure that encountered a failure to get system information. As shown, at act 14-0, the wireless terminal 26, in either of the RRC_IDLE, RRC_INACTIVE, or RRC_CONNECTED states, stores the content of SIB #A with validity information, valueTag=a, si-AreaID=2 , that the wireless terminal received previously. Within step 14-1, the wireless terminal may receive from the current serving access node SIB1 as the minimum SI, such as the first type of system information. The receipt of SIBI is indicated by arrow 12-1 in FIG. 12. As shown in FIG. 13, SIB1 includes a scheduleInfoList , which in turn may include one or more schedulingInfo information elements. An example scheduleInfoList for this scenario is shown in Table 1 described earlier, in which the kth schedulingInfo indicates that the SI message associated with this schedulingInfo (hereinafter SI #k) containing SIB #A will be available upon request delivery. Moreover, otherSIBInfo corresponding to SIB #A indicates that the validity information of SIB #A is valueTag=b, si-AreaID=3 . It is assumed that each time the wireless terminal receives SIB1, it has already received the MIB in advance.

[0086] Given that the stored SIB #A is now incorrect, the wireless terminal may decide to obtain a valid version of SIB #A and may initiate the SI request procedure represented by step 14-2 as described herein and indicated by arrow 12- 2 in FIG. 12. Upon successful completion of the SI request procedure, the wireless terminal may begin the SI receive procedure, outlined as step 14-3 in FIG. 14. In the SI reception procedure, the wireless terminal monitors the signals from the access node (shown by arrow 12-3 in FIG. 12) in the assigned SI windows obtained from the scheduleInfo in SIB1, and thus tries to obtain the requested SI #k . The SI windows are shown as dotted boxes in FIG. 14. In FIG. 14, within step 14-3a, step 14-3b, and step 14-3c, three successive transmissions of the requested SI #k are shown, all of which were unsuccessful. The tail of the downward vertical arrow in the description of the SI reception procedure in FIG. 14 is associated with the start of the SI reception procedure, while the same downward vertical arrow pointer is associated with the end of the SI reception procedure. On FIG. 14 shows an unsuccessful SI reception procedure. A failure in the SI receiving procedure defines a system information retrieval failure detector 80, which, as mentioned above, determines a failure in the SI message receiving process depending on the abort condition. The following are examples of termination conditions.

[0087] When a failure is detected in the SI message acquisition process, the terminal processor 40 initiates acquisition (reacquisition) of the first type of system information, such as MINIMUM SI or SIB1, as indicated by arrow 12-4 in FIG. 12. In this way, the wireless terminal 26(12) again tries to receive the first type of system information in the hope that after that the process of receiving the SI message can be repeated, and perhaps by repeating the process of receiving the SI message, the requested SI message will be received. In the exemplary implementation, the wireless terminal 26(12) may optionally reacquire the MIB before reacquiring the SIB1. Accordingly, in the absence of a valid version of the stored SIB, upon detecting a failure in the SI message acquisition process, the terminal processor 40 initiates acquisition (reacquisition) of the first type of system information.

[0088] In FIG. 15 shows exemplary, representative, basic actions or steps performed by the wireless terminal 26(12) shown in FIG. 12. Step 15-1 includes receiving system information (SI) of the first type from the base station device. As mentioned above, the first type system information includes: the availability of a second type SI message, wherein the second type SI message comprises at least one system information block (SIB); scheduling information for the SI message; indicating a delivery method for the second type SI message, wherein the delivery method is periodic broadcast or pull delivery, and at least one termination condition for determining a failure in the process of receiving the SI message for the second type SI message on demand. Step 15-2 includes sending an SI request message to request at least one SI message of a second type, indicated as delivery on request. Step 15-3 includes initiating the process of receiving the SI message. Step 15-4 includes determining a failure in the process of receiving an SI message. Action 15-5 upon failure in the SI message acquisition process includes initiating acquisition of the first type of system information.

[0089] In FIG. 16 is a flowchart showing an example of typical basic actions or steps performed by the access node 22(12) shown in FIG. 12. Step 16-1 includes the transmission of system information (SI) of the first type. The first type of SI is described above. Step 16-2 includes receiving an SI request message to request at least one SI message of the second type. Step 16-3 includes delivery of the requested SI message. As understood from the above, the requested SI message may be sent periodically, repeatedly transmitted at a predetermined interval within a predetermined period of time.

[0090] It has been mentioned above that, in one configuration, the wireless terminal may use a counter that is incremented by one with each SI window of a particular SI message, such as SI #k, and that the SI receive procedure may end when the requested message(s) ( -i) SI successfully received(s) or when the counter reaches the maximum value of the counter. In some configurations, the maximum value of the counter can be configured by SIB1 (eg, si-MaxAcqAttempts , shown in Fig. 13A). On FIG. 17A shows a system information retrieval failure detector 80 including a counter such as an SI window counter 82 . Thus, in one implementation of the embodiment and mode shown in FIG. 12, the termination condition may include an SI window counter 82 counting up to a maximum value or counting down from a preset value to zero. Such a maximum or preset value may be configured by the radio access node 22(12). The SI window counter 82 is incremented (or decremented) by one in case the requested SI message was not received at the end of one receive opportunity, eg, in the case where the requested SI message was not received at the end of the SI window.

[0091] In addition, it was mentioned above that in another configuration, the wireless terminal may start a timer at the beginning of the SI receive procedure and that the SI receive procedure may end when the requested SI message(s) is successfully received(s) or when the timer expires. In some configuration, the timer is configured with SIB1 (eg, timer configuration T#x in FIG. 13B). On FIG. 17B shows a system information retrieval failure detector 80 comprising such a timer: SI message acquisition process timer 84. Thus, in another implementation example of the embodiment and mode shown in FIG. 12, the termination condition may include expiration of the SI message acquisition process timer 84 configured by the base station device. The SI message acquisition process timer 84 is started at the start of the SI message acquisition process. The timer expiration value can be configured by the radio access node 22(12).

[0092] As is clear from the above, the other SI may contain one or more (other) SI messages, also known as second type SI messages. In one embodiment, as shown in FIG. 18A, the termination condition may be common to multiple, eg, all SI messages. Thus, in the embodiment shown in FIG. 18A, the maximum value of the counter in the case shown in FIG. 17A, or the timer value in the case shown in FIG. 17B may be common to all SI messages. In this case, the counter value configuration or timer configuration in the minimum SI (eg, si-MaxAcqAttempts in Fig. 13A or T No. x in Fig. 13B) may include a single parameter. In an alternative embodiment, as shown in the exemplary embodiment in FIG. 18B, the termination condition may be configured based on each SI message, for example, uniquely configured for one or more SI messages (another SI). In this case, the counter value configuration or timer configuration in the minimum SI (eg, si-MaxAcqAttempts in FIG. 13A or T#x in FIG. 13B) may contain a list of parameters, each of which configures a corresponding SI message. In the embodiments shown in FIG. 18A or FIG. 18B, termination condition(s), common(s) or non-generic(s), such as unique(s), may be pre-configured or configured by the network via system information. Here, the condition for the wireless terminal to end the SI reception process is referred to herein as a "termination condition".

[0093] The above is now considered in the context of a more general procedure for obtaining SI according to the 3GPP TS specification for a UE to obtain AS and NAS information. This additional procedure according to the 3GPP TS specification applies to UEs in the RRC_IDLE, RRC_IN ACTIVE and RRC_CONNECTED states. The UE in the RRC_IDLE and RRC_INACTIVE states must ensure that there is a valid version of (at least) the MIB, SIB1 and also SIB X to SIB Y (depending on the support of the RATs in question for UE-controlled mobility). A UE in the RRC_CONNECTED state must provide a valid version of (at least) the MIB, SIB1 , as well as SIB X (depending on mobility support with respect to the respective RATs).

[0094] In order to obtain the MIB and SIB 1, the UE must perform the following actions (with reference to any "section", "clause" or "subclause" refers to the corresponding section, clause or subclause of the 3GPP TS 38.331 specification).

1> if the cell is a PSCell: 2> get MIB ; 2> performing the actions specified in section 5.2.2.4.1; 1> otherwise: 2> get MIB ; 2> if the UE cannot obtain the MIB; 3> performance of actions according to clause 5.2.2.5; 2> otherwise: 3> performing the actions specified in section 5.2.2.4.1; 2> receive SIB 1 , 2> if UE cannot receive SIB 1 : 3> performance of actions according to clause 5.2.2.5; 2> otherwise: 3> performing the actions specified in section 5.2.2.4.2.

[0095] From the above, it is clear that the UE should apply the SI acquisition procedure according to the above definition when selecting a cell (for example, when powering on), reselecting a cell, when returning after being out of coverage, after changing the configuration with the end of synchronization, after entering the NR-RAN from another RAT, after receiving an indication that the system information has changed, after receiving a PWS notification, after receiving an SI message unsuccessfully, and whenever the UE does not have a valid version in the stored SI.

[0096] From the foregoing, it is clear that in the implementation example, upon receipt of an SI message, the UE may perform the following actions:

1> determining the start of the Si-window for the corresponding SI message. 1> if the receipt of the SI message is not triggered due to a UE request: 2> receiving the DL-SCH using SI-RNTI from the beginning of the SI window and continuing until the end of the SI window whose absolute length in time is given by the value of si-WindowLength or until receiving the SI message; 2> if the SI message was not received before the end of the SI window, re-accept in the next SI window event for the corresponding SI message; 1> else when triggering the receipt of an SI message due to a UE request: 2> setting the SI window counter 82 to 0 (or starting the SI message receiving process timer 84); 2> [FFS - receive DL-SCH using SI-RNTI from the beginning of the SI window and continue receiving until the end of the SI window whose absolute length in time is given by the value of si-WindowLength or until the reception of the SI message]; 2> [FFS - if SI message was not received before end of SI window, increment SI window counter 82, re-accept at next SI window event for corresponding SI message]; 2> if the SI window counter 82 is equal to the configured maximum value or counted down to zero (or the SI message receiving process timer 84 expires), 3> initiating the SI acquisition procedure.

[0097] When the UE receives a MIB or SIB 1 or an SI message in the current home/serving cell as described in 5.2.2.3, the UE must store the received SI. The SI version stored in the UE becomes obsolete after 3 hours. The UE may use such a stored version of the SI, for example, after cell reselection, when returning from being out of coverage, or after receiving an indication to change the SI. The storage and management of the stored SI in addition to the SI related to the current home/serving cell is left to the UE. The UE must:

1> delete any stored version of the SIB after 3 hours of successful validation; 1> if the UE has stored a version of any SIB: 2> for each SIB: 3> if the stored SIB is a coverage area-specific SIB and if the systemInfoAreaIdentifier and systemInfoValueTag included in the SIB 1 received from the current home/serving cell are identical to the systemInfoAreaIdentifler and systemInfoValueTag associated with the stored version of that SIB, or 3> if the stored SIB is cell-specific and if the systemInfoValueTag included in the SIB1 received from the current home/serving cell is identical to the systemInfoValueTag associated with the stored version of that SIB; 4> consider the stored SIB as valid for the cell; 3> otherwise: 4> receive (reacquire) the corresponding SI message as specified in 5.2.2.3. 1> if the UE does not have a saved SIB version: 2> receive (reacquire) the corresponding SI message as specified in 5.2.2.3.

[0098] FAILURE TO RECEIVE BROADCAST SYSTEM INFORMATION

[0099] The previous embodiments describe, for example, a procedure(s) for receiving a currently broadcast periodically SI message, wherein the wireless terminal may continue the SI reception procedure until successful completion. This operation may be valid if the corresponding SI message is assumed to be continuously broadcast. However, when using SI on demand, this assumption is not guaranteed to be true. For example, when a wireless terminal sees deliveryMode =broadcast in SIB1 for an SI message of interest, it becomes possible that the access node may temporarily broadcast the SI message in response to a request from another wireless terminal, and that the access node may eventually stop the periodic broadcast .

[000100] While the example communication system 20(12) depicted in FIG. 12 is mainly concerned with an unsuccessful attempt to receive system information on demand, in FIG. 19 shows an exemplary communication system 20(17) comprising a wireless terminal 26(17) capable of detecting a failure in an SI reception process using a periodically broadcast SI message. Access node 22(17) and wireless terminal 26(17) in FIG. 19 are substantially identical to the respective access point 22 and wireless terminal 26 in FIG. 2 and FIG. 12, except as noted herein. With respect to similarity, for example, the radio access node 22(17) comprises a node processor 30 and a node transceiver circuit 32, the node processor 30 comprising, for example, a node frame/signal scheduler/handler 50, a system information (SI) generator 54, and a controller. 60 RRC node. Similarly, the wireless terminal 26(17) includes a terminal processor 40, a terminal transceiver circuit 42 with a terminal processor 40 comprising a terminal frame/signal scheduler/handler 52, a system information (SI) processor 56, and a terminal RRC controller 70.

[000101] In Fig. 19 shows that the wireless terminal 26(17) also includes a system information retrieval failure detector 80. As in the case shown in FIG. 12, the terminal processor 40, and in particular the SI processor 56, may comprise or form a system information retrieval failure detector 80. The system information retrieval failure detector 80 is configured to detect a failure in the process of receiving the SI message. The failure detector 80 upon receiving system information may perform such failure determination based on the termination condition as explained herein.

[000102] As in the exemplary embodiment and mode in FIG. 12, the system information generator 54 of the radio access node 22(12) is configured to generate system information of the first type. For the embodiment and mode shown in FIG. 19 and in the non-limiting example of the method shown in FIG. 13, the first type system information includes (information elements or the like indicating): the availability of second type SI messages; scheduling information for each of the SI messages; a delivery method for each of the second type SI messages; and a configuration parameter for configuring at least one termination condition for determining a failure in the process of receiving the SI message for the second type of SI messages on request. As understood herein, the second type SI message contains at least one system information block (SIB), and the delivery method may be a periodic broadcast or on-demand delivery. The transmitter circuit 36 of the radio access node 22(17) is configured to transmit the first type of system information over the air interface 24 to the wireless terminal 26(17), as shown by arrow 19-1 in FIG. 19.

[000103] In the embodiment and mode shown in FIG. 19, it is assumed that the wireless terminal 26(17) is currently concerned with receiving a second type SI message for which the delivery method is a periodic broadcast. As such, the terminal processor 40 controls the terminal receiver 46 to initiate an SI message acquisition process for a periodically broadcast second type SI message. However, it may happen that after the initiation of the process of receiving the SI message, the expected periodically broadcast message(s) of the second type SI message(s) are not received(s). Non-receipt of the second type periodically broadcast SI message(s) may occur for any of several reasons, including the fact that the second type periodically broadcast SI message was broadcast at the request of another wireless terminal, wherein the wireless terminal 26 (17) has essentially acted as a third-party beneficiary of the broadcast, and the access node has by this time completed the broadcast of a second type SI message destined for another wireless terminal.

[000104] Thus, as in the exemplary embodiment and mode shown in FIG. 12, system information retrieval failure detector 80 can detect a failure in the SI message acquisition process. Meanwhile, in the exemplary embodiment and mode, the terminal processor 40 operating in response to or with operation of the system information acquisition failure detector 80 is configured to trigger the acquisition of the first type of system information. Thus, the terminal processor 40 is configured to initiate the acquisition of the first type of system information after a failure in the process of receiving the SI message using a periodically broadcast SI message of the second type, for example, to re-request the first type of system information (minimum SI) from the node 22(17 ) radio access. On FIG. 19, such a system information request of the first type is indicated by an arrow 19-4 (arrow 19-2 or arrow 19-3 is missing in FIG. 19).

[000105] In Fig. 20 shows an example message flow diagram for an SI acquisition procedure based on periodic broadcast upon detection of a failure in obtaining system information. As shown, at act 20-0, the wireless terminal 26, in either of the RRC_IDLE, RRC_INACTIVE, or RRC_CONNECTED states, stores the contents of SIB #A with validity information, valueTag= a, si-AreaID= 2, that the wireless terminal received previously. As part of step 20-1, the wireless terminal may receive from the current serving access node SIB1 as the minimum SI, such as the first type of system information. The receipt of SIBI is also indicated by arrow 19-1 in FIG. 19. As shown in FIG. 13, SIB1 includes a scheduleInfoList , which in turn may include one or more schedulingInfo information elements. An example scheduleInfoList for this scenario is shown in Table 2 described earlier, in which the k-th schedulingInfo indicates that the SI message associated with this schedulingInfo (hereinafter SI #k) containing SIB #A will be available via broadcast. Moreover, otherSIBInfo corresponding to SIB #A indicates that the validity information of SIB #A is valueTag=b, si-AreaID=3 . It is assumed that each time the wireless terminal receives SIB1, it has already received the MIB in advance.

[000106] Having received SIB1 as the minimum SI, such as first type system information, wireless terminal 26(17) knows when system information is expected to be broadcast for the desired second type SI, such as SIB #A, by radio access node 22(17). As such, the terminal processor 40 of the wireless terminal 26(17) starts the SI reception procedure (represented by step 20-3 in FIG. 20).

[000107] In the SI reception procedure 20-3, the wireless terminal monitors signals from the access node, trying to receive SI messages in the assigned SI windows obtained from the scheduleInfo in SIB1, and thus tries to receive the requested SI #k. The SI windows are shown as dotted boxes in FIG. 20. In FIG. 20, within step 20-3a, step 20-3b, and step 20-3c, three successive transmissions of the requested SI #k are shown, all of which were unsuccessful. The tail of the downward vertical arrow in the description of the SI reception procedure in FIG. 20 is associated with the start of the SI reception procedure, while the same downward vertical arrow pointer is associated with the end of the SI reception procedure. As shown in FIG. 20, the SI reception procedure 20-3 is extremely unsuccessful. A failure in the SI receiving procedure defines a system information retrieval failure detector 80, which, as mentioned above, determines a failure in the SI message receiving process depending on the abort condition. This document describes examples of termination conditions.

[000108] When a failure is detected in the SI message acquisition process, the terminal processor 40 initiates acquisition (reacquisition) of the first type of system information, such as MINIMUM SI or SIB1, as shown by arrow 20-4 in FIG. 20. In this way, the wireless terminal 26(14) again attempts to receive the first type of system information in the hope that after this the process of receiving the SI message can be repeated, and perhaps by repeating the process of receiving the SI message, the requested SI message will be received. In the exemplary implementation, the wireless terminal 26(14) may optionally reacquire the MIB before reacquiring the SIB1. Accordingly, in the absence of a valid version of the stored SIB, upon detecting a failure in the SI message acquisition process, the terminal processor 40 initiates acquisition (reacquisition) of the first type of system information.

[000109] In Fig. 21 is a flowchart showing an example of the main characteristic actions or steps performed by the wireless terminal shown in FIG. 19. Step 21-1 includes receiving system information (SI) of the first type from the base station device. As mentioned above, the first type system information includes: the availability of the second type SI message; scheduling information for the SI message; specifying a delivery method for the second type SI message, the delivery method being a periodic broadcast or on-demand delivery; and at least one termination condition for determining a failure in the process of receiving the SI message. Step 21-2 includes initiating an SI message acquisition process for a periodically broadcast second type SI message. Step 21-3 includes the determination of a failure in the process of receiving the SI message. Action 21-4 upon failure in the SI message acquisition process includes initiating acquisition of the first type of system information.

[000110] In Fig. 22 is a flowchart showing an example of the main characteristic actions or steps performed by the access node shown in FIG. 19. Step 22-1 includes the transmission of system information (SI) of the first type from the base station device. The first type system information includes, for example, configuration parameters for configuring at least one termination condition to determine a failure in the process of receiving the SI message. Step 22-2 turns on the transmission of periodic SI broadcast messages.

[000111] As with the embodiment and mode shown in FIG. 12, the wireless terminal 26(17) may use a counter that increments by one with each SI window of a particular message, such as SI #k, and may terminate the SI receive procedure upon successful receipt of the requested SI message(s) or upon when the counter reaches the maximum value of the counter. The system information retrieval failure detector 80 shown in FIG. 19 may include the above-mentioned SI window counter 82 shown in FIG. 17A, which can count up to the maximum value or count down from the preset value to zero. Such a maximum or preset value may be configured by the radio access node 22(17). The SI window counter 82 is incremented (or decremented) by one in case the requested SI message was not received at the end of one receive opportunity, eg, in the case where the requested SI message was not received at the end of the SI window.

[000112] In addition, as in the embodiment and mode shown in FIG. 12, the wireless terminal 26(17) may start a timer at the beginning of the SI receive procedure and may terminate the SI receive procedure upon successful receipt of the requested SI message(s) or upon expiration of the timer. The system information retrieval failure detector 80 shown in FIG. 19 may include the aforementioned SI message acquisition process timer 84 shown in FIG. 17B when the termination condition includes expiration of the timer 84 of the message acquisition process. The SI message acquisition process timer 84 is started at the start of the SI message acquisition process. The timer expiration value can be configured by the radio access node 22(17).

[000113] Thus, similar to the embodiments and modes shown in FIG. 2 and FIG. 12 to receive the periodic broadcast(s) SI message(s) as shown in FIG. 19, an additional mechanism may be used to complete the SI reception procedure. In one configuration, the wireless terminal may use a counter that increments by one with each SI window of a particular SI message (eg, SI#k). In this configuration, the receive initiated SI procedure may terminate when the requested SIB(s) are successfully received(s) or when the counter reaches the maximum counter value. (It should be understood that this implementation of the counter is logically identical to the alternative implementation in which the counter is set to the maximum value of the counter at the beginning of the SI receive procedure and decremented by one at the end of the SI window. In this implementation, the SI receive procedure may end when the counter reaches a preset value , such as zero). In another configuration, the wireless terminal starts a timer at the beginning of the SI reception procedure. In this configuration, the SIB reception procedure may terminate upon successful receipt of the requested SI message(s) or upon expiration of a timer. Similar to the embodiment shown in FIG. 12, and as is clear from FIG. 18A and FIG. 18B, the maximum counter value or timer value may be common to all SIB types, per SIB type, or per SI message, may be preconfigured, or configured by the network through system information.

[000114] In addition, it should be understood that the wireless terminal may attempt to receive some second type SI in a periodic broadcast and one or more other second type SIs in on-demand delivery. Thus, in a further embodiment and mode, the terminal processor 40 of a wireless terminal, such as wireless terminal 26(17), can be configured to both detect a failure in the process of receiving an SI message for a second type of broadcast system information, and to detect a failure in the process of receiving an SI message for system information of the second type on request. For this reason, the terminal processor 40 of the wireless terminal 26(17) is shown as a terminal processor 40 with an SI processor 56 in particular still containing a request generator 72 for another SI on request. Thus, in some modes it is possible to perform both processes shown as in FIG. 14 as well as in Fig. 19, essentially at this point in time.

[000115] When the wireless terminal 26 is capable of both detecting a failure in the process of receiving an SI message for broadcast type 2 system information and detecting a failure in the process of receiving an SI message for system information of the second type on demand, the wireless terminal 26 may have separate conditions termination for each process. For this reason, the wireless terminal 26 may include a plurality of SI window counters 82 and/or a plurality of SI message acquisition process timers 84. For example, the wireless terminal may comprise a first SI window counter 82(B) for a process of receiving an SI message for a second type of broadcast system information; and a second SI window counter 82(D) for a process of obtaining an SI message for the second type of system information on request. Or, for example, the wireless terminal may comprise a first SI message acquisition process timer 84(B) for an SI message acquisition process for the second type of broadcast system information; and a second SI message acquisition process timer 84(D) for the SI message acquisition process for the second type system information on request.

[000116] In addition, the configuration of the counter or the configuration of the timer to receive the periodic broadcast(s) message(s) SI can be configured by system information (for example, SIB1) separately from the configuration to receive the message(s) SI upon request. In this case, the SIB1 shown in FIG. 13C, with two separate counter configurations ( si-MaxAcqAttemptsOnDemand and si-MaxAcqAttemptsPeriodic ), or shown in FIG. 13D with two separate timer configurations (T#x for on-demand messages and T#y for periodic broadcast). In an alternative embodiment, a counter/timer configuration common to receive an on-demand SI message and a periodic broadcast SI message can be configured. In this case, the SIB1 shown in FIG. 13A (overall meter configuration) or FIG. 13B (general timer configuration).

[000117] The above more general 3GPP TS specification SI acquisition procedure for UEs to obtain AS and NAS information may be partially modified, for example, when receiving an SI message for the embodiment and mode depicted in FIG. 19 as shown below. As previously indicated, the counters (SI window counter 82(B) and SI window counter 82(D)) or timers (SI message receive process timer 84(B) and SI message receive process timer 84(D) may be identical or alternative implementation be configured separately.

Upon receipt of an SI message, the UE shall: 1> define the start of the SI window for the corresponding SI message as follows: 1> if the receipt of the SI message is not triggered due to a UE request: 2> set the SI window counter 82(B) counter to 0 (or start the SI message receiving process timer 84(B)); 2> receive the DL-SCH using the SI-RNTI from the beginning of the SI window and continue receiving until the end of the SI window whose absolute length in time is given by the value of si-WindowLength or until the receipt of the SI message; 2>if the SI message was not received before the end of the SI window, increment the counter 82(B) of the SI windows by one, repeat the reception at the next SI window event for the corresponding SI message; 2>if SI window counter 82(B) counter is equal to [configured maximum value] (or SI message receive process timer 84(B) expires), 3> initiate the procedure for obtaining SI according to paragraphs. 5.2.2.3. 1> else when triggering the receipt of an SI message due to a UE request: 2> set the SI window counter 82(D) counter to 0 (or start the SI message receiving process timer 84(D)); 2> [receive DL-SCH using SI-RNTI from the beginning of the SI window and continue receiving until the end of the SI window whose absolute time length is given by SI-WindowLength, or until the receipt of the SI message]; 2> [if the SI message was not received before the end of the SI window, increment the SI window counter 82(D), repeat reception at the next SI window event for the corresponding SI message]; 2>if the SI window counter 82(D) counter equals [configured maximum value] (or the SI message receive process timer 84(D) expires), 3> initiate the procedure for obtaining SI according to paragraphs. 5.2.2.3.

[000118] The features of each of the exemplary embodiments and modes described herein can be combined with each other. For example, the information elements described in connection with the embodiment and mode shown in FIG. 2 may also be used with other embodiments and modes described herein, including, without limitation, the embodiment and mode shown in FIG. 14 and FIG. 19. In addition, the features of the "examples" listed below in this document can also be used in combination with each other.

[000119] Certain blocks and functionality of node 22, node 22-12, node 22-17, wireless terminal 26, wireless terminal 26-14, and wireless terminal 26-17 in the exemplary embodiments are implemented using electronic equipment, computer and/or circuitry . For example, node processors 30 and terminal processors 40 according to the embodiments described herein and/or covered may be composed of the computer circuit shown in FIG. 23. In FIG. 23 shows that an example of such an electronic device or circuit, be it a node or a terminal, comprises one or more processor(s) circuits 190, a memory 192 for program instructions; other types of storage devices 194 (eg, RAM, cache, etc.); interfaces 196 input-output; peripheral interfaces 198; auxiliary circuits 199 and buses 200 for communication between the above elements.

[000120] The memory 192 for program instructions may contain encoded instructions, the execution of which by the processor(s) causes the execution of actions, including, without limitation, the actions described herein. Thus, it is understood that each node processor 30 and terminal processor 40, for example, includes a memory storing non-volatile instructions to be executed.

[000121] The storage device 194 or computer-readable medium may be one or more readily available types of storage devices, such as random access memory (RAM), read only memory (ROM), floppy disk, hard disk, flash memory, or any other form a digital storage device, local or remote, and preferably non-volatile. Auxiliary circuits 199 are coupled to processors 190 to support the processor in a standard manner. These circuits include cache, power supplies, clock circuits, I/O circuitry, subsystems, and so on.

[000122] Additionally, it should be understood that when referring to a processor or processor circuitry in conjunction with any of the previous embodiments and modes, it should be clear that the device hosting the processor, whether it be a wireless terminal or access point, may comprise at least one a processor and at least one storage device, including computer program code, wherein the storage device and computer program code (operating with at least one processor) are configured to provide the above-described functions of the host during operation.

[000123] Thus, the technology described herein solves problems in the field of telecommunications, including problems in telecommunications nodes such as wireless terminals and access nodes, as well as computers/processors and hardware containing such nodes. System information is extremely important for the functioning of telecommunications nodes, since it is possible for each node to obtain the necessary information about the network to coordinate and communicate with other nodes and perform the required functions. The system information is quite detailed and complex and can be changed/updated, for example, depending on the network and operating conditions. Efficient acquisition and use of system information is difficult, especially given the many other telecommunications functions that may be simultaneously and in-progress based on system information. The technology described herein solves the problem that can occur when SI messages are not received in a timely manner, for example, by shortening the procedures for receiving SIs and initiating corrective actions such as reacquiring SIB1. Thus, the technology described in this document avoids time consuming and unnecessary costs for processing resources.

[000124] The technology of the present application thus encompasses, without limitation, the following embodiments, feature examples, and advantage examples, where index D refers to on-demand implementation and index B refers to periodic broadcast implementation.

[000125] Example 1D implementation. A user equipment that communicates with a radio access network (RAN) base station device over an air interface, the user equipment comprising:

a receiver circuit configured to receive a first type system information (SI) from a base station device, the first type SI including:

the availability of a second type SI message, the second type SI message comprising at least one system information block (SIB);

scheduling information for the SI message;

specifying a delivery method for the second type SI message, the delivery method being a periodic broadcast or on-demand delivery; And

at least one termination condition for determining a failure in the process of receiving the SI message;

a transmitter circuit configured to transmit an SI request message to request at least one SI message of a second type, indicated as delivery on request;

processor circuit configured to:

using the receiver scheme to initiate the process of receiving the SI message;

determining a failure in the process of receiving the SI message depending on the termination condition; And

upon failure in the process of receiving the SI message, initiating the receipt of the first type of system information.

[000126] 2D implementation example. The user equipment of exemplary 1D, wherein the termination condition includes a counter reaching the maximum value configured by the base station device, the counter incrementing by one in case the requested SI message has not been received by the end of one receive opportunity.

[000127] 3D implementation example. The user equipment of the 2D exemplary embodiment, wherein the receive capability is an SI window configured by the base station apparatus.

[000128] Example 4D implementation. The user equipment of exemplary 1D, wherein the termination condition includes a counter reaching zero from a preset value configured by the base station device, the counter being decremented by one in case the requested SI message has not been received at the end of one reception opportunity.

[000129] Implementation example 5D. The user equipment of exemplary 4D, wherein the receive capability is an SI window configured by the base station apparatus.

[000130] Example 6D implementation. The user equipment of exemplary 1D, wherein the termination condition includes expiration of a timer configured by the base station device, the timer starting after the start of the SI message receiving process.

[000131] Example 7D implementation. A method for user equipment that communicates with a radio access network (RAN) base station device over an air interface, comprising:

receiving system information (SI) of the first type from the base station device, and the first type SI includes:

the availability of a second type SI message, the second type SI message comprising at least one system information block (SIB);

scheduling information for the SI message;

specifying a delivery method for the second type SI message, the delivery method being a periodic broadcast or on-demand delivery;

at least one termination condition for determining a failure in the process of obtaining an SI message for a second type SI message on request;

transmitting an SI request message to request at least one SI message of a second type, indicated as delivery on request;

initiating the process of receiving the SI message;

determining a failure in the process of receiving the SI message; And

after a failure in the process of receiving the SI message, initiating the receipt of the first type of system information.

[000132] Example 8D implementation. The method of exemplary 7D, wherein a failure in the process of receiving an SI message is determined by a counter reaching a maximum value configured by the base station device, wherein the counter is incremented by one in the case where the requested SI message has not been received by the end of one receive opportunity.

[000133] Implementation Example 9D. The method of exemplary 7D, wherein the receive capability is an SI window configured by the base station apparatus.

[000134] Example 10D implementation. The method of exemplary 7D, wherein a failure in the acquisition process is determined upon expiration of a timer configured by the base station device, wherein the timer starts after the acquisition process of the SI message is started.

[000135] Example 11D implementation. A radio access network (RAN) base station device that communicates with user equipment over an air interface, the base station device comprising:

a transmitter circuit configured to transmit system information (SI) of the first type, wherein the first type SI includes:

the availability of a second type SI message, the second type SI message comprising at least one system information block (SIB);

scheduling information for the SI message;

specifying a delivery method for the second type SI message, the delivery method being a periodic broadcast or on-demand delivery;

a configuration parameter for configuring at least one termination condition for determining a failure in the process of receiving the SI message for the second type of SI message on request;

a receiver circuit configured to receive an SI request message to request at least one second type SI message;

a processor circuit configured to use the transmitter circuit to deliver the requested SI message.

[000136] Example 12D implementation. The base station apparatus of exemplary 11D, wherein the termination condition includes a counter reaching a maximum value configured by the base station apparatus, the counter incrementing by one in case the requested SI message has not been received by the end of one receive opportunity.

[000137] Implementation Example 13D. The base station apparatus of exemplary 12D, wherein the receive capability is an SI window configured by the base station apparatus.

[000138] Example 14D implementation. The base station apparatus of exemplary 11D, wherein the termination condition includes expiration of a timer configured by the base station apparatus, wherein the timer starts after the SI message receiving process is started.

[000139] Example 15D implementation. A method for a radio access network (RAN) base station device that communicates with user equipment over an air interface, comprising:

transmission of system information (SI) of the first type, and the SI of the first type includes:

the availability of a second type SI message, the second type SI message comprising at least one system information block (SIB);

scheduling information for the SI message;

specifying a delivery method for the second type SI message, the delivery method being a periodic broadcast or on-demand delivery;

a configuration parameter for configuring at least one termination condition for determining a failure in the process of receiving the SI message for the second type of SI message on request;

receiving an SI request message to request at least one SI message of the second type;

delivery of the requested SI message.

[000140] Example 16D implementation. The method of exemplary 15D, wherein the termination condition includes a counter reaching a maximum value configured by the base station device, wherein the counter is incremented by one in case the requested SI message has not been received by the end of one receive opportunity.

[000141] Example 17D implementation. The method of exemplary 16D, wherein the receive capability is an SI window configured by the base station apparatus.

[000142] Example 18D implementation. The method of exemplary 15D, wherein the terminating condition includes expiration of a timer configured by the base station device, wherein the timer starts after the start of the SI message receiving process.

[000143] Example 19D implementation. A user equipment that communicates with a radio access network (RAN) base station device over an air interface, the user equipment comprising:

a processor circuit configured to initiate a first type system information block (SIB) acquisition process to receive the first type SIB, the first type SIB including:

scheduling information for a system information (SI) message, the SI message comprising at least one SIB of the second type; And

an indication of the broadcast status for the SI message, the indication indicating delivery on demand;

a receiver circuit configured to receive the first type SIB; And

a transmitter circuit configured to send an SI request message to request the SI message;

a processor circuit, further configured to initiate an SI message acquisition process to receive the SI message; and

in the event that the stored version of one of the at least one SIB of the second type is not valid, the process of obtaining the SIB of the first type is initiated on failure in the process of obtaining the SI message.

[000144] Example 20D implementation. The user equipment of exemplary 19D, wherein the processor circuitry is further configured to re-initiate the SI message acquisition process in response to the initiation of the first type SIB acquisition process when the SI message acquisition process fails.

[000145] Example 21D implementation. A method for user equipment that communicates with a radio access network (RAN) base station device over an air interface, the method comprising:

initiating a first type system information block (SIB) acquisition process to receive the first type SIB, the first type SIB including:

scheduling information for a system information (SI) message, the SI message comprising at least one SIB of the second type; And

an indication of the broadcast status for the SI message, the indication indicating delivery on demand;

reception of SIB of the first type;

transmitting an SI request message to request an SI message; And

initiating the process of receiving the SI message to receive the SI message, while

in the event that the stored version of one of the at least one SIB of the second type is not valid, the process of obtaining the SIB of the first type is initiated on failure in the process of obtaining the SI message.

[000146] Example 22D implementation. The method of embodiment 21D, further comprising re-initiating the SI message acquisition process in response to initiating the first type SIB acquisition process when the SI message acquisition process fails.

[000147] Example 23D implementation. A radio access network (RAN) base station device that communicates with user equipment over an air interface, the base station device comprising:

a transmitter circuit configured to transmit a first type system information block (SIB), wherein the first type SIB includes:

scheduling information for a system information (SI) message, the SI message comprising at least one SIB of the second type; And

an indication of the broadcast status for the SI message, the indication indicating delivery on demand;

a receiver circuit configured to receive the SI request message to request the SI message;

a processor circuit configured to use the transmitter circuit to deliver the SI message, wherein

if the user equipment fails to receive the SI message during the process of receiving the SI message, the user equipment reacquires the first type SIB if the version of one of the at least one second type SIBs stored in the user equipment is invalid.

[000148] Example 24D implementation. The base station apparatus of exemplary 23D, wherein the first type SIB reacquired by the user equipment is used by the user equipment to re-initiate the SI message acquisition process.

[000149] Example 25D implementation. A method for a radio access network (RAN) base station device that communicates with user equipment over an air interface, comprising:

transmission of a system information block (SIB) of the first type, and the SIB of the first type includes:

scheduling information for a system information (SI) message, the SI message comprising at least one SIB of the second type; And

an indication of a broadcast state for a second type SI message, the indication indicating delivery on demand;

receiving an SI request message to request an SI message;

delivery of the SI message; wherein

if the user equipment fails to receive the SI message during the process of receiving the SI message, the user equipment reacquires the first type SIB if the version of one of the at least one second type SIBs stored in the user equipment is invalid.

[000150] Example 26D implementation. The method of exemplary 25D, wherein the first type SIB reacquired by the user equipment is used by the user equipment to re-initiate the SI message acquisition process.

[000151] Example 1B implementation. A user equipment that communicates with a radio access network (RAN) base station device over an air interface, the user equipment comprising:

a receiver circuit configured to receive a first type system information (SI) from a base station apparatus, the first type system information including:

the availability of a second type SI message, the second type SI message comprising at least one system information block (SIB);

scheduling information for the SI message;

specifying a delivery method for the second type SI message, the delivery method being a periodic broadcast or on-demand delivery; And

at least one termination condition for determining a failure in the process of receiving the SI message;

processor circuit configured to:

using a receiver circuit to initiate a process for receiving an SI message for a periodically broadcast second type SI message;

determining a failure in the process of receiving the SI message depending on the termination condition; And

upon failure in the process of receiving the SI message, initiating the receipt of the first type of system information.

[000152] Example 2B implementation. The user equipment of exemplary 1B, wherein the termination condition includes a counter reaching the maximum value configured by the base station device, the counter incrementing by one in case the requested SI message has not been received by the end of one receive opportunity.

[000153] Embodiment 3B. The user equipment of Example 2B, wherein the receive capability is an SI window configured by the base station apparatus.

[000154] Example 4B implementation. The user equipment of exemplary 1B, wherein the termination condition includes expiration of a timer configured by the base station device, the timer starting after the SI message receiving process is started.

[000155] Example 5B implementation. The user equipment of exemplary 1B, wherein the termination condition is also used for the SI message acquisition process for second type SI messages on request.

[000156] Example 6B implementation. The user equipment of exemplary 1B, wherein the termination condition is for the process of receiving an SI message for periodically broadcast SI messages of the second type.

[000157] Example 7B implementation. The user equipment of exemplary 6B, wherein the first type SI further includes at least one termination condition for an SI message acquisition process for second type SI messages on request.

[000158] Example 8B implementation. A method for user equipment that communicates with a radio access network (RAN) base station device over an air interface, comprising:

receiving system information (SI) of the first type from the base station device, and the system information of the first type includes:

the availability of a second type SI message, the second type SI message comprising at least one system information block (SIB);

scheduling information for the SI message;

specifying a delivery method for the second type SI message, the delivery method being a periodic broadcast or on-demand delivery;

at least one termination condition for determining a failure in the process of receiving the SI message;

initiating an SI message acquisition process for the periodically broadcast second type SI message;

determining a failure in the process of receiving the SI message; And

if the process of receiving the SI message fails, initiating the receipt of the first type of system information.

[000159] Example 9B implementation. The method of exemplary 8B, in which a failure in the process of receiving an SI message is determined by a counter reaching the maximum value configured by the base station device, the counter incrementing by one in the case where the requested SI message has not been received by the end of one receive opportunity.

[000160] Example 10B implementation. The method of embodiment 9B, wherein the receive capability is an SI window configured by the base station apparatus.

[000161] Example 11B implementation. The method of exemplary 8B, wherein a failure of the acquisition process is determined upon expiration of a timer configured by the base station device, wherein the timer starts after the acquisition process of the SI message is started.

[000162] Example 12B implementation. The method of exemplary 8B, wherein the termination condition is for an SI message acquisition process for periodically broadcast second type SI messages.

[000163] Example 13B implementation. The method of exemplary 12B, wherein the first type SI further includes at least one termination condition for an SI message acquisition process for second type SI messages on request.

[000164] Example 14B implementation. A radio access network (RAN) base station device that communicates with user equipment over an air interface, the base station device comprising:

a transmitter circuit configured to transmit system information (SI) of the first type, wherein the first type SI includes:

the availability of a second type SI message, the second type SI message comprising at least one system information block (SIB);

scheduling information for the SI message;

specifying a delivery method for the second type SI message, the delivery method being a periodic broadcast or on-demand delivery;

configuration parameters for configuring at least one termination condition for determining a failure in the process of receiving the SI message;

a processor circuit configured to use a transmitter circuit to broadcast the periodic broadcast SI messages.

[000165] Example 15B implementation. The base station apparatus of exemplary 14B, wherein the termination condition includes a counter reaching a maximum value configured by the base station apparatus, the counter incrementing by one in case the requested SI message has not been received by the end of one receive opportunity.

[000166] Example 16B implementation. The base station apparatus of Example 15B, wherein the receive capability is an SI window configured by the base station apparatus.

[000167] Example 17B implementation. The base station apparatus of exemplary 14B, wherein the termination condition includes expiration of a timer configured by the base station apparatus, wherein the timer is started after the SI message receiving process is started.

[000168] Example 18B implementation. The base station apparatus of exemplary embodiment 14, wherein the termination condition is also used for the process of obtaining an SI message for the second type of SI messages on request.

[000169] Example 19B implementation. The base station apparatus of exemplary 14B, wherein the termination condition is for an SI message acquisition process for periodically broadcast second type SI messages.

[000170] Example 20B implementation. The base station apparatus of exemplary 19B, wherein the first type SI further includes at least one termination condition for an SI message acquisition process for second type SI messages on request.

[000171] Example 21B implementation. A method for a radio access network (RAN) base station device that communicates with user equipment over an air interface, comprising:

transmission of first type system information (SI) from the base station apparatus, the first type system information including:

the availability of a second type SI message, the second type SI message comprising at least one system information block (SIB);

scheduling information for the SI message;

specifying a delivery method for the second type SI message, the delivery method being a periodic broadcast or on-demand delivery;

configuration parameters for configuring at least one termination condition for determining a failure in the process of receiving the SI message;

transmission of periodic broadcast messages SI.

[000172] Example 22B implementation. The method of exemplary 21B, wherein the termination condition includes a counter reaching a maximum value configured by the base station device, wherein the counter is incremented by one in case the requested SI message has not been received by the end of one receive opportunity.

[000173] Example 23B implementation. The method of embodiment 22B, wherein the receive capability is an SI window configured by the base station apparatus.

[000174] Example 24B implementation. The method of Exemplary 21B, wherein the termination condition includes expiration of a timer configured by the base station device, wherein the timer starts after the SI message receiving process is started.

[000175] Example 25B implementation. The method of Exemplary 21B, wherein the termination condition includes expiration of a timer configured by the base station device, wherein the timer starts after the SI message receiving process is started.

[000176] Example 26B implementation. The method of exemplary 21B, wherein the terminating condition is also applied to the process of receiving an SI message upon request for SI messages of the second type.

[000177] Example 27B implementation. The method of exemplary 25B, wherein the termination condition is for an SI message acquisition process for periodically broadcast second type SI messages.

[000178] While the processes and methods of the described embodiments may be described as being implemented as a subroutine, some of the method steps that are described herein may be performed by the hardware as well as the processor running the software. Accordingly, embodiments may be implemented as software running on a computer system, as hardware such as an ASIC or other type of hardware implementation, or as a combination of software and hardware. The routines of the described embodiments are capable of executing on any computer operating system and are configured to use any CPU architecture. The instructions for such software are stored on non-volatile computer-readable media.

[000179] The functions of various elements, including functional blocks, including, without limitation, designated or described as "computer", "processor" or "controller", can be provided through the use of equipment, such as hardware circuitry and / or equipment , configured to be executed by software in the form of coded instructions stored on a computer-readable medium. Thus, it is to be understood that such functions and illustrated functional blocks are represented as being hardware-implemented and/or computer-implemented and hence computer-implemented.

[000180] In terms of hardware implementation, functional blocks may include or include, but are not limited to, digital signal processor (DSP) hardware, reduced instruction set processor, hardware (e.g., digital or analog) circuitry, including but not limited to , application-specific integrated circuit(s) [ASIC] and/or user-programmable gate array(s) (FPGA), and (where possible) finite machines capable of performing such functions.

[000181] In terms of computer implementation, a computer is generally considered to comprise one or more processors or one or more controllers, and the terms "computer", "processor", and "controller" may be used interchangeably herein. When provided by a computer or processor or controller, functions may be provided on a single dedicated computer or processor or controller, a single shared computer or processor or controller, or a plurality of separate computers or processors or controllers, some of which may be shared or distributed. Moreover, use of the term "processor" or "controller" should also be construed as referring to other equipment capable of performing such functions and/or running software, such as the equipment listed above by way of example.

[000182] The functions of various elements, including functional blocks, including, without limitation, designated or described as "computer", "processor" or "controller", can be provided through the use of equipment, such as hardware circuitry and / or equipment , configured to be executed by software in the form of coded instructions stored on a computer-readable medium. Thus, it is to be understood that such functions and illustrated functional blocks are represented as being hardware-implemented and/or computer-implemented and hence computer-implemented.

[000183] Nodes that communicate using the air interface also have a suitable radio scheme. Moreover, implementation of the technology entirely within any form of computer-readable memory, such as solid-state memory, magnetic disk, or optical disk, containing an appropriate set of computer instructions, such that the processor would be able to perform the techniques described herein, may further be considered.

[000184] It should be understood that the technology described herein is directed to solving problems related to wireless communication, and is necessarily based on computer technology and overcomes problems that arise specifically in the field of wireless data communication. Moreover, in at least one aspect, the technology described herein improves the operation of a core function of a wireless terminal and/or the node itself such that, for example, the wireless terminal and/or node can operate more efficiently with reasonable use of radio resources.

[000185] Although the above description contains many specific details, they should not be construed as limiting the scope of the technology described herein, but only as providing illustrations of some of the currently preferred embodiments of the technology described herein. Thus, the scope of the technology described herein is to be determined by the appended claims and their legal equivalents. Thus, it should be understood that the scope of the technology described herein is intended to fully encompass other embodiments that may become apparent to those skilled in the art, and that the scope of the technology described herein is accordingly not limited by anything other than the appended claims. , in which the reference to an element in the singular does not mean "one and only one", but "one or more", unless otherwise indicated. All structural, chemical and functional equivalents of the elements of the preferred embodiment described above that are known to those skilled in the art are expressly incorporated herein by reference and are considered to be covered by the present claims. Moreover, a device or method need not solve each and every one of the problems that the technology described herein is intended to solve in order to be included in the present claims. Additionally, no element, component, or method step herein is intended to be in the public domain, whether or not that element, component, or method step is explicitly listed in the claims. No claim herein shall be construed under the provisions of 35 U.S.C.C., paragraph 112, sixth paragraph, unless the element is expressly described by the phrase "means to."

Claims (30)

1. User equipment that communicates with a radio access network (RAN) base station device over an air interface, the user equipment comprising: a processor circuit configured to initiate a first type system information block (SIB) acquisition process to receive the first type SIB, the first type SIB including: scheduling information for a system information (SI) message, the SI message comprising at least one SIB of the second type; And an indication of the broadcast status for the SI message, the indication indicating delivery on request; a receiver circuit configured to receive the first type SIB; And a transmitter circuit configured to send an SI request message to request the SI message; a processor circuit, further configured to initiate an SI message acquisition process to receive the SI message; wherein, in the event that the stored version of one of the at least one SIB of the second type is invalid, the process for obtaining the SIB of the first type is initiated on failure in the process for obtaining the SI message. 2. The user equipment of claim 1, wherein the processor circuitry is further configured to re-initiate the SI message acquisition process in response to the initiation of the first type SIB acquisition process when the SI message acquisition process fails. 3. A method for user equipment that communicates with a radio access network (RAN) base station device over an air interface, the method comprising: initiating a first type system information block (SIB) acquisition process to receive the first type SIB, the first type SIB including: scheduling information for a system information (SI) message, the SI message comprising at least one SIB of the second type; And an indication of the broadcast status for the SI message, the indication indicating delivery on request; reception of SIB of the first type; transmitting an SI request message to request an SI message; And initiating an SI message acquisition process to receive the SI message, wherein in case the stored version of one of the at least one second type SIB is invalid, the first type SIB acquisition process is initiated when the SI message acquisition process fails. 4. The method of claim 3, further comprising re-initiating the SI message acquisition process in response to initiating the first type SIB acquisition process when the SI message acquisition process fails. 5. A radio access network (RAN) base station device that communicates with user equipment over an air interface, the base station device comprising: a transmitter circuit configured to transmit a first type system information block (SIB), wherein the first type SIB includes: scheduling information for a system information (SI) message, the SI message comprising at least one SIB of the second type; And an indication of the broadcast status for the SI message, the indication indicating delivery on request; a receiver circuit configured to receive the SI request message to request the SI message; a processor circuit configured to use the transmitter circuit to deliver the SI message, wherein if the user equipment fails to receive the SI message in the process of receiving the SI message, the user equipment reacquires the first type SIB if the version of one of the at least one second type SIB, stored in the user equipment is invalid. 6. The base station apparatus of claim 5, wherein the first type SIB reacquired by the user equipment is used by the user equipment to re-initiate the SI message acquisition process. 7. A method for a radio access network (RAN) base station device that communicates with user equipment over an air interface, including: transmission of a system information block (SIB) of the first type, and the SIB of the first type includes: scheduling information for a system information (SI) message, the SI message comprising at least one SIB of the second type; And an indication of a broadcast state for a second type SI message, the indication indicating delivery on request; receiving an SI request message to request an SI message; delivery of the SI message; wherein, if the user equipment fails to receive the SI message in the process of receiving the SI message, the user equipment reacquires the first type SIB if the version of one of the at least one second type SIB stored in the user equipment is invalid. 8. The method of claim 7, wherein the first type SIB reacquired by the user equipment is used by the user equipment to re-initiate the SI message acquisition process.

Images