The preferred embodiment of the present invention is described herein after referring to the charts and drawings. However, it is to be noted that the technical scope of the present invention is not limited to the embodiments described below.
The plurality of call processing controllers 30 may be provided for each of a plurality of radio frequency bands (1.7 GHz band, 2 GHz band, etc.), or the plurality of call processing controllers 30 may be provided for a single radio frequency band in case of a redundant configuration being adopted or in case of divided accommodation of subscribers.
System data memory 10 stores system data, which are basic data necessary for operating the base station, and is constituting of a nonvolatile memory.
When a call processing controller corresponding to anew frequency band is additionally installed, upper-level apparatus updates the system data. In this case, the common data is updated, and also a proper data proper to the call processing controller for the above new frequency band is added.
The update of the common data relates to, for example, an item for recognizing the correspondence of the call processing controller operation ON/OFF to each frequency band. Assume a state of only a call processing controller for an X frequency band having been ON (in operation) until then is shifted to a state that the operation of another call processing controller for a new Y frequency band becomes also ON. Then, the common data is rewritten into the state of the call processing controller for the X frequency band: ON, and also the state of the call processing controller for the Y frequency band: ON. In
Referring back to
A bus controller 21 in maintenance & supervision controller 20 has an arbitration function of a common bus for data transmission and reception between each card mounted on maintenance & supervision controller 20. Bus controller 21 manages which card presently owns bus access right.
An external unit controller 22 controls external units accompanying the base station. Specifically, as external units, there are included a low-noise amplifier, station building facilities, and an antenna tilt controller. External unit controller 22 has interfaces for controlling the above external units. By interchanging control signals with the external units via the above interfaces, external unit controller 22 controls the external units. For example, external unit controller 22 confirms normal operation of the low-noise amplifier, confirms whether a door on the building facilities is not left open, and whether an air-conditioning unit is not out of order. Also, external unit controller 22 shifts an antenna tilt direction.
A database 23 is constituted of a memory for storing the state of call processing traffic.
A management controller 25 in maintenance & supervision controller 20 stores the call processing traffic state into database 23 according to an instruction from upper-level apparatus (operation center) which manages other function portions provided in maintenance & supervision controller 20. Also, at the time of either resetting only each call processing controller 30, or resetting on a card-by-card basis constituting call processing controller 30, management controller 25 transfers the system data to data memory 36 in call processing controller 30, as will be described later.
A file memory 24 includes a file memory for temporarily storing system data downloaded from system data memory 10, or a fault information data of the base station. According to an instruction from the upper-level apparatus (operation center), management controller 25 in maintenance & supervision controller 20 downloads the system data from system data memory 10, or uploads the fault information to the upper-level apparatus. File memory 24 temporarily keeps the above data.
Management controller 25 in maintenance & supervision controller 20 has a function of managing other function portions in maintenance & supervision controller 20, so as to perform management as the nucleus of maintenance & supervision controller 20. Further, management controller 25 performs supervision of the entire cards in the base station, report of the change of the card state to the upper-level apparatus, and execution of a control instruction from the upper-level apparatus and response thereto. As will be described later, management controller 25 collects from the entire cards the state information of each card by polling, and recognizes the reset or the reset control of each card (the reset of each card through the system reset, the controller reset, or the individual card reset).
Call processing controller 30 is a controller for controlling radio communication with a mobile communication terminal of a user. Similar to maintenance & supervision controller 20, call processing controller 30 is configured of a hardware unit (referred to as shelf) having mounted function portions stated below, each being realized as a board-type hardware unit (computer unit referred to as card).
A bus controller 31 in call processing controller 30 has an arbitration function of a common bus for performing data transmission and reception between each card mounted on call processing controller 30. Bus controller 31 manages which card presently owns bus access right.
A protocol terminator 32 extracts a specific signal from data signals transmitted from upper-level apparatus with a predetermined format, and converts a signal for transmitting to the upper-level apparatus into a predetermined format, and transmits the converted signal. Through a wired line between the base station and the upper-level apparatus, signal transmission/reception is performed using a predetermined format. According to a predetermined protocol, protocol terminator 32 extracts the specific signal from the above format. Also, according to the predetermined protocol, protocol terminator 32 converts a signal for transmission into a predetermined format.
A global memory 33 includes a memory for storing call processing information in operation. Call processing controller 30 has a redundant configuration to prevent influence upon users to a possible extent. In the redundant configuration, global memory 33 is constituted of two cards: an operating card and a standby card. The standby card works as operating card after being switched over from the operating card when the operating card becomes unable to continue services because of a failure, etc. At this time, it is necessary for the former standby card to succeed the call processing being performed in the former operating card. For this purpose, call processing information in operation is stored real time into the memory provided in the former standby card. Global memory 33 is the above memory provided in the former standby card, and is constituted of a volatile, high-speed accessible memory.
A baseband processor 34 performs baseband signal processing in the communication with a user mobile communication terminal. Between the base station and the mobile communication terminal, communication is performed by overlaying data on a high-frequency carrier wave in a radio frequency band (1.7 GHz, 2 GHz, etc.). In contrast, inside the base station, data is extracted from a radio frequency, and the signal processing is performed after downconverting the frequency to a low frequency band. Baseband processor 34 performs the above signal processing in the base band.
A management controller 35 in call processing controller 30 includes a function of managing other function portions provided in call processing controller 30, and manages the nucleus of call processing. Also, management controller 35 in call processing controller 30 communicates with management controller 25 in maintenance & supervision controller 20. Moreover, according to an instruction from the upper-level apparatus, management controller 35 performs communication control with the mobile communication terminal.
As will be described later, a data memory 36 in call processing controller 30 stores both a common data and a proper data of a frequency band handled by the self-call processing controller 30, among the system data stored in system data memory 10. For example, data memory 36 in call processing controller 30 for an X frequency band stores both the common data and the proper data proper to the call processing controller for the X frequency band. Similarly, data memory 36 in call processing controller 30 for a Y frequency band stores both the common data and proper data proper to the call processing controller for the Y frequency band. Maintenance & supervision controller 20 transfers necessary data from system data memory 10 to data memory 36 in each call processing controller 30.
The above data memory 36 is a memory area which is not reset at the time of resetting. As will be described later, at the time of an individual card reset, the reset is performed after necessary data are read in from data memory 36, not from system data memory 10.
The system data memory is constituted of either a volatile memory capable of high-speed data transfer such as SRAM and DRAM, or a nonvolatile memory such as flash memory preventing data from being erased even at the time of power off.
The reset cause indication register is not reset even when each card is reset, and each bit data therein is not erased. Accordingly, when resetting, each card is reset after the bit corresponding to a reset cause is set ON. At the time of restarting, each card recognizes the reset cause (reset type) by reading the bit data in the reset cause indication register of the card concerned. According to the reset type, each card modifies a readout location of the system data. After recognizing the reset cause, each card clears the bit data (set to OFF).
Specifically, in the case of the system reset, the common data and the proper data proper to the controller, having the card concerned as a configuration element, are read from the system data memory 10. In the case of the controller reset and the individual card reset, the common data and the proper data are read from data memory 36 inside the controller concerned.
On receiving a system reset instruction from upper-level apparatus 100, management controller 25 in maintenance & supervision controller 20 transfers the system reset instruction to the entire cards provided in maintenance & supervision controller 20 and call processing controllers 30X, 30Y, 30Z. Thereby, the system reset bit in the reset cause indication register is set ON (S100).
Triggered by the system reset bit switched ON, each card in maintenance & supervision controller 20 and call processing controllers 30X, 30Y, 30Z perform resetting and start initiation (S102). When the initiation is started, by referring to the reset cause indication register (S104), each card recognizes the system reset. Each card then accesses system data memory 10, and reads both the common data stored in system data memory 10 and the proper data proper to the controller having the card concerned as a configuration element (S106), and initiates (S108). On recognizing the reset type, each card clears the reset cause indication register.
After the initiation, management controller 25 in maintenance & supervision controller 20 receives an initiation notification from each card in each call processing controller 30. After the entire cards are initiated, management controller 25 transfers the data for call processing controller 20 stored in system data memory 10 to data memory 36 in each call processing controller 20 (S110). Then, data memory stores the received data (S112).
Specifically, management controller 25 in maintenance & supervision controller 20 transmits to call processing controller 30X both the common data and the proper data proper to call processing controller 30X, transmits to call processing controller 30Y both the common data and the proper data proper to call processing controller 30Y, and transmits to call processing controller 30Z both the common data and the proper data proper to call processing controller 30Z.
Data memory 36 in each call processing controller 25 realizes a backup function to system data memory 10. Even in the event of a failure to access system data memory 10, by accessing data memory 36 in each call processing controller 30, each card can read the common data (which may possibly be an old version before update) necessary for the initiation, as well as each proper data.
Further, even in the event of a fault in maintenance & supervision controller 20, which controls the controller reset and the individual card reset described later, by accessing data memory 36 in each call processing controller 30, each card of a reset object can read the common data (which may possibly be an old version before update) necessary for the initiation, as well as each proper data.
By an instruction from upper-level apparatus 100 (via supervision controller 20) or the depression of a reset button provided on call processing controller 30X, a reset of call processing controller 30X is instructed. By this, a controller reset (local or remote) bit in the reset cause indication register of each card of call processing controller 30X is set ON (S200).
When the controller reset bit is set ON, each card in call processing controller 30X issues a controller reset notification to maintenance & supervision controller 20 (S202). Thereafter, each card performs the reset, and starts initiation (S204).
On receipt of the controller reset notification from call processing controller 30X, management controller 25 in maintenance & supervision controller 20 accesses system data memory 10, reads out both the common data common to call processing controllers 30 and the proper data proper to call processing controller 30X, and transfers the readout data to a data memory 36X in call processing controller 30 (S206). Data memory 36X stores the received data (S208). By this, both the common data and the proper data proper to call processing controller 30X are updated.
Meanwhile, when the initiation is started, each card in call processing controller 30X refers to the reset cause indication register (S210). On recognizing the controller reset, the card waits for data transfer by maintenance & supervision controller 20 from the above system data memory 10 to data memory 36X of call processing controller 30X. After the lapse of a predetermined time, the card accesses data memory 36X and reads both the common data and the proper data proper to call processing controller 30X stored therein (S212), and performs initiation (S214).
In
For the above reason, in order to reset only call processing controller 30Y, the common data and the proper data proper to call processing controller 30Y are transferred from system data memory 10 to data memory 36 in call processing controller 30Y, under the control of maintenance & supervision controller 20. Call processing controller 30Y reads the common data and the proper data from data memory 36Y, and performs initiation. Thus, it is possible to perform the initiation without resetting the other call processing controller 30X.
Furthermore, a backup function can be realized by storing both the common data and the proper data for initiating the newly installed call processing controller 30Y in the internal data memory 36. Namely, even in the event that an access to system data memory 10 is disabled on the occurrence of a system reset or a fault in maintenance & supervision controller 20, by accessing data memory 36 in each call processing controller 30, each card can read the common data (which may possibly be an old version before update) necessary for the initiation, as well as each proper data.
By an instruction from upper-level apparatus 100 (via supervision controller 20) or the depression of a reset button provided on card 31X (bus controller 31X) of call processing controller 30X, a reset of card 31X in call processing controller 30X is instructed. By this, an individual card reset (local or remote) bit in the reset cause indication register of each card 31X is set ON (S300).
When the individual card reset bit becomes ON, card 31X in call processing controller 30X issues an individual card reset notification to maintenance & supervision controller 20 (S302), and thereafter, performs the reset and starts initiation (S304).
On receipt of the individual card reset notification from card 31X of call processing controller 30X, management controller 25 in maintenance & supervision controller 20 accesses system data memory 10, reads out only the proper data proper to call processing controller 30X, and transfers the readout data to data memory 36X in call processing controller 30 (S306). Data memory 36X stores the received data (S308). By this, only the proper data proper to call processing controller 30X is overwritten, whereas the common data is not updated.
Meanwhile, when the initiation is started, card 31X in call processing controller 30X refers to the reset cause indication register (S310). On recognizing the individual card reset, card 31X waits for data transfer from the above system data memory 10 to data memory 36X of call processing controller 30X. After the lapse of a predetermined time, card 31X accesses data memory 36X, and reads the common data stored therein (not updated) and the proper data proper to call processing controller 30X (S312), and performs the initiation (S314).
In case that a call processing controller 30Y for handling a new frequency band Y is additionally installed prior to the reset of card 31X, the common data stored in system data memory 10 is updated when call processing controller 30Y is installed.
When resetting card 31X, if card 31X accesses system data memory 10, card 31X reads the updated common data. Then, since cards other than the reset card in call processing controller 30X have read the common data before the update, different common data become existent in call processing controller 30X, causing malfunction or incorrect operation.
According to the reset on a card-by-card basis in the present invention, under the control of maintenance & supervision controller 20, only the proper data proper to call processing controller 30X is transferred to data memory 36 in call processing controller 30X without reading the common data from system data memory 10. Therefore, the common data in data memory 36 of call processing controller 30X is left intact without being updated. Further, since card 31X performs initiation after reading the common data and the proper data from data memory 36, the identical common data to the common data for other cards can be read in. Thus, malfunction and a failure of call processing controller 30 can be prevented.
The foregoing description of the embodiments is not intended to limit the invention to the one details of the examples illustrated. Any suitable modification and equivalents may be resorted to the scope of the invention. All features and advantages of the invention which fall within the scope of the invention are covered by the appended claims.
Number | Date | Country | Kind |
---|---|---|---|
2006-187432 | Jul 2006 | JP | national |